Portable Evidence
A public-safe presentation of one bounded execution capture, designed to show what was recorded, what can be concluded, and what remains unknown without exposing task content or private runtime identities.
The interactive HTML and downloadable JSON are derived from the same allow-listed public projection.
A concise record identity, generation context, final determination, Governability summary, authority timeline and checksum orient the reviewer before the detailed annex.
Expandable operations, stages, measurements, scoped gate outcomes, relationships and evidence gaps preserve depth without forcing every detail onto the front sheet.
Embedded and downloadable JSON use the same bounded record. Report-local aliases replace private actor, process, thread and resource identifiers.
Generation references and non-secret correlation values support review and comparison. Historical records do not gain identities or metadata that were never retained.
Admission, observed changes, holds, release and terminal evidence can be summarised without replacing the underlying receipts.
Authority observations are tied to the operation and boundary where they were recorded. Tool permission, proposal approval and whole-execution authority remain different claims.
Available invocation, executor and CPU evidence can be presented with its scope. Shared execution infrastructure does not establish causal ownership.
Unknown, conflicting, unavailable and historically unrecorded facts remain visible rather than being inferred from successful output or nearby telemetry.
The record is an unsigned project evidence artifact. Its checksum supports internal consistency of the presented projection; it does not independently authenticate system origin, prevent third-party recreation, prove atomic enforcement, certify Governance, or establish that every relevant transition was captured.
