Published notes
2entries
Public documentation publication log
Publication notes
Dated changes to the public documentation.
This is a publication log, not an audit system or evidence ledger. A product-control status changes only when the trust center and its underlying evidence are updated together.
Latest update
Sep 28, 2026
Cross-organization story and status refresh
What this is not
Not an audit
Control maturity stays in the trust center
Publication feed
What changed in the public surface.
Each note records documentation publication only. Status labels for platform controls remain governed by the trust center.
Publication note Cross-organization story and status refresh
Adds a status-labelled explanation of cross-organization federated identity for people and AI agents, and aligns developer-surface and comparison wording with the canonical status registry.
The home page and developer documentation now show how two organizations, each with its own trust anchor, can exchange verifiable requests between a person and an AI agent. Cross-organization federation and agent identity remain designed.
Console, CLI, MCP, and package statements now carry explicit status: Console and CLI exist only in limited scope, MCP is planned, and no public package has been released.
The managed-cloud comparison cell now reads limited pilot rather than available.
No control maturity was raised by this note.
Publication note Preview documentation baseline
Introduces audience-led documentation, a public status registry, preview routes, and a crawler-ready semantic publication surface.
This publication note does not change the maturity of any platform control.
Control status remains sourced from the trust center and the canonical standards registry.
No generally available SDK, sandbox, deployment package, certification, or independently validated control is announced here.
Keep reading
Status lives in the trust center.
Use the documentation for how the platform is designed, and the trust center for the labeled maturity of each control.