From 0a075ea8d4b8f9b31ebbf4ba78193bf9f1bcf8ad Mon Sep 17 00:00:00 2001 From: Imran Siddique Date: Sat, 8 Aug 2026 10:06:07 -0700 Subject: [PATCH] docs(profile): TRACE goes to the LF as its own series, not to AAIF Correction to the previous commit, which named AAIF as the single standards home. That is not where TRACE is going. It is being formed as "TRACE Specification, a Series of LF Projects, LLC": its own LF series, not co-hosted under CoSAI and not under the LF entity hosting MCP. Formation is in progress with the LF standards team and trace-spec#127 brings GOVERNANCE.md into the required shape. The badge, the Principles bullet, and the one-pager all named AAIF. All three now name the LF series and say formation is in progress rather than implying a filed submission. Co-Authored-By: Claude Opus 5 (1M context) --- profile/README.md | 4 ++-- profile/technical-one-pager.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/profile/README.md b/profile/README.md index 7ed4649..7e75f99 100644 --- a/profile/README.md +++ b/profile/README.md @@ -17,7 +17,7 @@ agentrust-io is the open trust layer built to close it: replacing "we have guard The specifications, SDKs, and conformance tests are free and open. Begin in software; advance to hardware-backed and post-quantum assurance as requirements demand. [![License](https://img.shields.io/badge/License-Apache_2.0_%2F_MIT_%2F_CC_BY_4.0-blue.svg)](#projects) -[![AAIF](https://img.shields.io/badge/Targeting-AAIF_%2F_Linux_Foundation-6366f1)](https://agenticai.foundation) +[![Linux Foundation](https://img.shields.io/badge/TRACE-Linux_Foundation_series_(in_formation)-6366f1)](https://www.linuxfoundation.org/) [![CC Summit](https://img.shields.io/badge/Launched-CC_Summit_Jun_2026-7c3aed)](https://confidentialcomputingsummit.com) > **The 2-minute version:** [technical one-pager](technical-one-pager.md). @@ -51,7 +51,7 @@ The specifications, SDKs, and conformance tests are free and open. Begin in soft These projects are developed in the open. We intend to propose them to recognized open standards bodies; we're inviting the ecosystem to shape them: -- **TRACE**: we intend to submit it to the **Agentic AI Foundation (AAIF) under the Linux Foundation**, where OPAQUE is a member and participates in the Observability and Traceability working group. The submission has not been filed yet; this page will name the date when it is. Founding co-editor seats are open now. +- **TRACE**: going to the **Linux Foundation as its own series**, "TRACE Specification, a Series of LF Projects, LLC". Formation is in progress with the LF standards team; governance has been brought into the shape LF requires ([trace-spec#127](https://github.com/agentrust-io/trace-spec/pull/127)). This supersedes the earlier plan to co-host under CoSAI or under the LF entity hosting MCP. Founding co-editor seats are open now. - **Agent Manifest**: we intend to submit it through CoSAI under OASIS Open, building on CoSAI Workstream 4. - **AGT (Agent Governance Toolkit)**: the runtime governance engine this stack builds on, created by Imran Siddique (Chief Platform Officer, OPAQUE) while at Microsoft and released under the MIT license: [microsoft/agent-governance-toolkit](https://github.com/microsoft/agent-governance-toolkit). diff --git a/profile/technical-one-pager.md b/profile/technical-one-pager.md index 9a281d1..0a65f9d 100644 --- a/profile/technical-one-pager.md +++ b/profile/technical-one-pager.md @@ -31,7 +31,7 @@ The stack runs at one of four conformance levels (L0–L3): software-only → TE ## TRACE — the envelope that ties it together -TRACE (Trust Runtime Attestation and Compliance Evidence) is the portable governance record at the center of the stack: a single attestation envelope (EAT/JWT, per the IETF RATS model) that **carries the other standards' evidence** — build provenance (SLSA), workload identity (SPIFFE SVID), model inventory (AIBOM), a cryptographic bill of materials (CBOM — the crypto libraries and algorithms in use), and the agent's tool-call transcript — cryptographically bound and anchored in an append-only transparency log. One verifiable record that proves **what an agent was** and **what it did**, reconstructable after the fact and confirmable by a party with no reason to trust the operator. Open spec; we intend to submit it to AAIF. +TRACE (Trust Runtime Attestation and Compliance Evidence) is the portable governance record at the center of the stack: a single attestation envelope (EAT/JWT, per the IETF RATS model) that **carries the other standards' evidence** — build provenance (SLSA), workload identity (SPIFFE SVID), model inventory (AIBOM), a cryptographic bill of materials (CBOM — the crypto libraries and algorithms in use), and the agent's tool-call transcript — cryptographically bound and anchored in an append-only transparency log. One verifiable record that proves **what an agent was** and **what it did**, reconstructable after the fact and confirmable by a party with no reason to trust the operator. Open spec, going to the Linux Foundation as its own series. ## About OPAQUE