Cogitator Witness Protocol This draft documents the current Cogitator reference implementation for tamper-evident AI-agent run records. It defines schema versions, commitment boundaries, and witness-root recomputation semantics.
Status Draft; reference implementation protocol snapshot.
Schema constants Trace schema version is 3, witness manifest schema version is 3, and tool transcript schema version is 4.
Canonicalization Witnessed material uses a strict deterministic canonical JSON subset (JCS-style/I-JSON constrained, integer-only witnessed numbers). This draft does not claim full RFC 8785 conformance for all JSON artifacts.
Witness root algorithm The authoritative root is computed by a domain-separated BLAKE3 linear chain over canonical witnessed metadata, then per-step agent-trace witness entries, then per-step tool operations ordered by tool_call_idx (including phantom/intercepted entries). Manifest file hashes and bundle hash are diagnostic self-consistency values and are not witness-root authority.
Hashing diagnostics Artifact hashes and bundle hash in witness manifests are SHA-256 self-consistency diagnostics in the current implementation.
Verification model Verification supports bundle self-consistency checks, semantic witness recompute, and anchored comparison when an external expected root is supplied. A co-located witness_root.txt is not external anchoring.
Path confinement Manifest artifact paths must be bundle-relative. Absolute paths, canonical escapes, and symlink escapes are rejected.
Threat model limits The protocol detects post-hoc mutation of committed contents against an expected root and rejects malformed/incomplete transcripts. It does not attest hardware/runtime environment and does not prove occurrence without external anchoring.