Product documentation

Replay lineage envelope

Inspectable evidence record

Claim ref: event-attribution-replayability | Status: planned | Verification method: manual

Source ref: product-repo:internal/db/store.go@9af059973ade9b4f45046747bb268690b82fbeb5 | Verified at: 2026-03-19

Verified by: platform-engineering | Reproducible: no

Product version: 0.5.0

Verification procedure: Reviewed replay-envelope field requirements against public-safe event model notes.

Verification confidence: low

Replay fidelity: approximate

Environment context:

Repo state: product-repo@redacted

Checkout command: git checkout <commit-from-proof-record>

Access to redacted replay envelope examples

Artifact refs: event-replay-lineage

Scope: status: planned means this proof record captures schema-level envelope field requirements — it describes what an event envelope should contain, not what the production event pipeline actually emits or guarantees. verificationConfidence: low reflects that field structure has been reviewed against the event model, but production event samples matching this schema have not been published, verified, or reproduced. This record does not establish that the event pipeline is complete, that all significant transitions produce envelopes, or that hash chain integrity is verifiable in production. Cross-session chain linkage shipped in v0.4.0 (replayFidelity: approximate); full deterministic replay remains planned. The JSON example below shows the target envelope shape — it is illustrative, not a verified production trace.

{
  "run_id": "run_01HTP5EFVCP0GDCY4EEWJ42MCM",
  "actor": "user:[email protected]",
  "approval_id": "apr_01HTP5G7Q3Y3Q70G1BT22K8HZE",
  "policy_version": "2026-03-14.1",
  "event_index": 287,
  "timestamp": "2026-03-19T04:22:17Z"
}

Status: planned — the envelope schema is established, but public replay command output is not yet published. This record does not provide production evidence of attribution or replay capability. failureMode entries (silent emission failure, incorrect actor attribution, hash chain gaps) describe real risks that this planned record does not mitigate. The proof record should be updated to partial with verified production event samples once available.