I-D Action: draft-sato-soos-gar-04.txt
[email protected] Thu, 13 Aug 2026 06:33:17 -0700
| Newsgroups | gmane.ietf.announce |
|---|---|
| Message-ID | <178662799791.63024.2486745127867743670@dt-datatracker-559c48c7fb-b8xm6> |
Internet-Draft draft-sato-soos-gar-04.txt is now available. Title: The Governance Audit Record (GAR) for Agentic AI Systems Author: Tom Sato Name: draft-sato-soos-gar-04.txt Pages: 23 Dates: 2026-08-13 Abstract: This document specifies the Governance Audit Record (GAR), the audit architecture for agentic AI systems. GAR defines five audit types, the Session Audit Record (SAR), the Audit Alert system, auditor principal categories, and the Audit Package for external regulatory inspection. GAR provides verifiable evidence that AI agent sessions were governed in accordance with the Intent Declaration Primitive [I-D.sato-soos-idp] and the Human Escalation Mechanism [I-D.sato-soos-hem]. GAR answers the governance question: can any of this be proven to a regulator? GAR is a domain-specific application of the SCITT (Supply Chain Integrity, Transparency and Trust) architecture [I-D.ietf-scitt-architecture] extended with causal ordering semantics for agentic governance events. GAR defines the Authority Lifecycle Event (ALE) category: a normative set of causally-ordered event types covering the complete agent session revocation and recovery lifecycle, including single-agent revocation, authority suspension, partial state recording, recovery initiation, credential restoration, and multi-agent delegation tree events. Version -03 adds the SOOS Governance Semantic Convention: the normative soos.governance.* OpenTelemetry attribute namespace for governance observability (Section 13), the SOOS GAR Processor specification for OTel-to-SAR pipeline construction with Session Block Merkle integrity (Section 14), four new Authority Lifecycle Events (ALE-NEW-01 through ALE-NEW-04), three mandatory provenance fields on Cedar evaluation records, and the XPID mirror field on ACD session ALEs. Version -04 makes the Session Block construction rules of Section 14.3 fully explicit and implementation-independent, closing three ambiguities found during independent interop verification at the IETF 126 Hackathon: the exact soos.gar.prev_span_hash formula (Section 2), the requirement that Merkle leaf computation occur over the canonical (RFC 8785 JCS) serialization of the event delta record with block_id already attached, and that Merkle parent nodes combine raw digest bytes rather than hex-encoded text. Version -04 also resolves OQ-OTEL-03 (Section 14.6) and adds Security Considerations entry S.15.d documenting the Layer 1 / Layer 2 tamper-detection coverage asymmetry as an intentional, named property of the design rather than a silent gap. No new fields, attributes, or ALE types are introduced in -04; all changes make existing -03 normative language explicit. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-sato-soos-gar/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-sato-soos-gar-04 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-sato-soos-gar-04 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ I-D-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]