Writing from the Cognous team on what changes when AI stops assisting and starts acting — authority, evidence, and the architecture required to prove an action was allowed.
A replay bundle is only useful if it reproduces a decision exactly. Walking through the minimum record set — proposal, policy version, evaluation trace, authority context, and outcome — and the fields removed after they proved redundant.
Governance records get read years after they are written, often by people without the runtime that produced them. Notes on schema versioning, forward compatibility, and why every record carries its own schema reference.
Most systems record what happened. The refusals — what an agent proposed and was not permitted to do — carry more governance signal than the successes, and they are the hardest records to reconstruct after the fact.
Evidence packs frequently leave the boundary they were produced in. How field-level redaction interacts with signing, and the approach taken so a redacted bundle can still be verified against its original.
Manifest, control plane, replay bundle, evidence pack. Why these are separate record types with defined inputs and outputs rather than one monolithic governance object, and what each layer is responsible for.
The first public preview of the reference implementation — schemas, a filesystem adapter, deterministic policy gating, and a CLI. What is included, what is explicitly out of scope, and how to run the examples.
Posts explain the reasoning behind the work. The open reference implementations carry the record.