MapGraphSeamsCalendarIntroductionDisclosureMethodFor agents and tools

Updated weekly, new versions on Mondays · Corrections: open an issue

TRACE (Trust, Runtime Attestation and Compliance Evidence)

Linux Foundationspecificationcontext entry

Verified 2026-10-13. Status as of 2026-10-13. All entries.

Status

Specification version 0.2, described in its text as "0.2: Draft" with status "RFC: Request for Comments"; the repository README calls it a Developer Preview launched on 23 June 2026, and the Python package agentrust-trace 0.11.0 was released on 2026-09-25. The README states that the specification is hosted at the Linux Foundation as "TRACE Specification, a Series of LF Projects, LLC", and a Linux Foundation press release of 2026-08-25 announces the contribution of TRACE from OPAQUE. Reading of 2026-10-13: the README of the repository now says "a proposal to bring it into the Agentic AI Foundation as a Sandbox project is in progress" and points to aaif/project-proposals issue #42, which is open with the label Under Review, 8 comments and a last update on 2026-10-02; the specification stays at v0.2 ("Spec v0.2 is current"), main is at commit 8562b09 (2026-10-13, 00:33 UTC), and the latest release objects are conformance-v0.6.2 (2026-10-03, the conformance test package) and v0.11.0 (2026-09-25). The folder spec/ also holds a draft named mcp-profile-v0.3-draft.md, not read.

Relevance

The specification says "This is the rulebook for TRACE: it defines the Trust Record (a signed receipt describing one AI agent run), how records are anchored in a" The README describes TRACE as "an open format for a signed receipt of an AI agent run: what ran, where, under which rules, on what kind of data, and which" and states its limit: "A v0.2 signature proves who made a record and that it has not changed.

It does not prove the hardware claims inside it". The specification text is under the Community Specification License 1.0 and the code under Apache 2.0 (LICENSE and README); GitHub's repository metadata reports the licence as NOASSERTION. MAINTAINERS.md lists as Project Lead Imran Siddique (AgenTrust-io), as spec editors Rishabh Poddar and Aaron Fulkerson (OPAQUE Systems), and two repository maintainers listed in the same file.

The Linux Foundation press release says "The Linux Foundation will provide vendor-neutral governance for TRACE to support sustainability and long-term growth." In the AAIF Identity and Trust work TRACE is the format cited by the shared runner of agentrust-io/integrations, which validates "reference shapes" of the released package agentrust-trace 0.11.0, a reference package, not a version of the specification, which is v0.2 (see aaif-identity-trust).

Committed next

None declared in the sources read.

Sources

Overlaps

AAIF Identity and Trust group, issue

Neighbours in the map

Neighbours of TRACE (Trust, Runtime Attestation and Compliance Evidence) in the map Each circle is an entry of the map and links to its page; the colour is the kind of body behind it, a filled circle is a core entry and a dashed circle a context entry. The entry in the middle, with the entries it overlaps and the entries named by the same seams. Overlaps (1)Share a seam (0)AAIF Identity and Trust group, issue (AAIF, context)AAIF Identity and Trust… TRACE

Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.

Evidence and coverage

Read
On 2026-10-13: the README of trace-spec (status paragraph), the repository metadata, the three latest commits, the release list and the file list of spec/, and the state, labels and description of aaif/project-proposals issue #42 (its comments were not read).
Not read
The rest of the specification (980 lines), the schema, the conformance suite, the roadmap and governance files, the limitations file.