Skip to content

Latest commit

 

History

History
36 lines (29 loc) · 2.07 KB

trace-finalization.md

File metadata and controls

36 lines (29 loc) · 2.07 KB

TRACE finalization

Status: experimental. Python requires 3.11+ and agentrust-telemetry[trace]. TypeScript requires a caller-supplied official TRACE codec because no official AgentTrust TRACE Node package is currently published.

finalize_trace maps a sealed, explicitly complete evidence snapshot into the official TRACE v0.2 model, signs it with a caller-supplied key, validates it, and self-verifies the signature. The adapter never loads or generates a key.

The caller must provide trusted subject identity, model identity, build provenance, evidence origin, appraisal verifier, and an ordered classification taxonomy. The adapter derives the policy binding, enforcement mode, maximum data class, appraisal, issuance time, and software evidence-chain measurement.

Finalization fails when evidence is open, incomplete, empty, inconsistently bound to policy, missing classified data flows, or contains an unranked classification. It also recomputes the evidence chain and fails when the snapshot's entries no longer hash to its chain digest (an entry edited, dropped, or reordered after sealing), since the measurement would then not cover the events appraised. The recheck proves consistency, not provenance: the chain carries no key. It emits runtime.platform: software-only; it cannot manufacture attestation.

When action.executed events are present, tool_transcript.hash covers their normalized bytes and evidence sequence in acceptance order, and call_count equals the number of those action events. Other governance events are excluded. When no action evidence is present, the optional transcript remains absent.

The signed record remains subject to TRACE's documented trust-anchor, freshness, revocation, transparency, and software-only limitations.

The TypeScript codec boundary must provide the v0.2 profile identifier, signing, structural validation, public-key derivation, and signature verification. The finalizer invokes all four steps and fails closed. It does not substitute a local shape check for official TRACE validation. Tool transcript bytes use RFC 8785 JCS in both SDKs.