OPAQUE gives away the agent audit receipt and sells the machine that prints it

The commercial logic here is legible without any help from the press release. A signed record is only worth something if a party that did not run the workload can check it, and checking needs a verifier, a trust anchor, and rules about who may issue and revoke. OPAQUE contributed the format; according to the source, the project's own documents show governance and verification work is unfinished ^[4], with the technical track moving to the Coalition for Secure AI ^[2]. Until that settles, a Trust Record is a well-formed artifact whose validation path is a matter of trust in whoever produced it.

What makes the format plausible is that it is mostly an envelope. TRACE composes existing specifications, including RATS, EAT, SLSA, SCITT, SPIFFE and EAR ^[6], so the underlying attestations, provenance statements and workload identities are things cloud platforms, chip vendors and policy engines already emit. That is the argument for cross-vendor uptake: no cloud or agent framework has to adopt a competitor's definition of proof to interoperate ^[15]. It is also why the interesting design question is not the schema but the verifier.

The adoption figure deserves less weight than its size suggests. Nearly 135,000 PyPI downloads in the ten weeks after the June debut ^[7] works out to roughly 13,500 a week ^[16], which is the shape of continuous integration traffic and casual evaluation as much as deployment. The Linux Foundation itself labels it a company-reported package count rather than evidence of production use ^[7], and the package identifies TRACE as a developer preview ^[8]. Anyone writing "TRACE record" into a control framework this quarter is designing an audit around preview software.

The lineage is more informative than the download chart. Imran Siddique built Microsoft's Agent Governance Toolkit for agent identity, permissions and runtime behavior before joining OPAQUE ^[9]; TRACE pushes the same concerns into an after-the-fact artifact that names the model, the location, the active policy, the class of data touched and the tools called ^[10]. That is the correct list of fields for an incident review. It is also, conveniently, the list of things you can only capture if you control the runtime, which is the product OPAQUE sells ^[3].

One detail worth holding onto: Intel co-developed TRACE with AMD, Microsoft and the Technology Innovation Institute ^[2], and Intel Capital took part in the $24 million Series B that valued OPAQUE at about $300 million post-money ^[11]. The same company sits on the standards side and the cap table ^[17]. That is normal in confidential computing, where the hardware root of trust and the vendor ecosystem are the same small set of names, but it is a reason to read the verifier rules closely rather than to treat neutral hosting as neutrality already achieved.

The test of whether this is a standard or a product feature with a foundation logo is narrow and checkable: a Trust Record emitted by a runtime OPAQUE did not build, validated by a party that sells neither.