feat(site): highlight the AgenTrust Fellowship 2026 - #11
Merged
Conversation
Same audit as the org profile, applied to agentrust-io.com. Two findings were wrong rather than stale, and one of those is an overclaim. The acronym was wrong. The site expanded TRACE as "Transparent Runtime Attestation for Confidential Execution" in four places, including the JSON-LD. The specification says "Trust, Runtime Attestation, and Compliance Evidence", in its title, its README, and section 1. The public site was teaching search engines and AI assistants a name the spec does not use. The confidentiality claim overstated what cMCP guarantees. The site said the host, the operator, and the network "never observe inputs, outputs, or intermediate state" and "see only ciphertext". cMCP's own LIMITATIONS.md is narrower on both counts: the plaintext guarantee is structural only where the Cedar egress policy denies telemetry and APM endpoints, and cMCP "controls the tool boundary, not the model boundary", so it does not cover model inference or the agent's context window. Both bounds now appear wherever the claim does, in the visible copy and in the JSON-LD. Licences were stated as a blanket Apache 2.0 in five places, including the footer. They are mixed: Agent Manifest and trace-tests are Apache 2.0, cMCP and cA2A are MIT, and the TRACE specification text is CC BY 4.0 with its reference code under Apache 2.0. Versions were stale: TRACE v0.1 to spec v0.2, cMCP v0.1 to 0.3.0, and "Agent Manifest v1", which never existed in either the spec or the SDK, to spec v0.1. Standardization said CoSAI / AIF; the body is AAIF. llms.txt carried the same acronym, confidentiality, licence, and version claims and moves with the page. It also now states the v0.2 profile URI change, since that is the one thing an implementer reading a machine-readable summary has to act on. JSON-LD revalidated: all three blocks parse. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Applications open 1 August, three days out, and close 29 August, so the window is short and the site said nothing about it. Three placements, deliberately: a banner above the hero so it is visible without scrolling, a section with the substance, and a nav entry so the section is reachable. llms.txt carries it too, since that is what AI assistants read when someone asks about the programme. The section leads with what a fellow would actually work on rather than only the programme terms. Selection is by technical proposal, so the ten open issues labelled fellowship across trace-spec, cmcp, ca2a and agent-manifest are the most useful thing an applicant can be pointed at, and they are real currently-open work rather than exercises. Facts taken from the announcement itself: six months, part-time at 20 hours per week, paid, three to five fellows, 1 to 29 August applications, September start, Greenhouse, mentored by Imran Siddique. Styling reuses the existing palette variables and the hero-actions and lead-copy classes, so nothing new was invented visually. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Announcement is live on opaque.co, but agentrust-io.com said nothing about it. Applications open 1 August, three days out, and close 29 August, so the window is short.
Three placements
#fellowshipsection with the substance.llms.txtcarries it too, since that is what an AI assistant reads when someone asks whether AgenTrust is hiring.The section leads with the work, not the perks
Selection is by technical proposal, so the most useful thing to hand an applicant is the actual work. There are ten open issues labelled
fellowshipacross trace-spec (5), cmcp (2), cA2A (2), and agent-manifest (1), and the section links a live org-wide search for them. They are currently-open work rather than exercises, which is a stronger pitch than a description of the programme and also filters for people who read before applying.Facts, all from the announcement
Six months, part-time at 20 hours per week, paid, three to five fellows, applications 1 to 29 August 2026, September start, via Greenhouse, mentored by Imran Siddique, Chief Platform Officer at OPAQUE and creator of the Agent Governance Toolkit. Audience as stated: security engineers, distributed systems researchers, AI governance and compliance professionals, and Ph.D. students.
Incidentally this independently confirms the title question from the profile pass: the announcement says Chief Platform Officer.
Verification
hero-actionsandlead-copyclasses, so nothing new was invented visually; the banner uses the same navy as the hero with the teal already in the palette for the tagNot done, worth deciding
I did not put the fellowship on the org profile README, which is the other place people land. Happy to add a short section there, and to post it in the org Announcements category alongside the maintainer announcement, if you want it pushed harder than a website section. Given the 29 August deadline I would do both.