StateMirror (Artifact v1.0.0) [ID: STM-01]
StateMirror is a self-hosted, immutable evidence snapshot ledger.
When your application makes a decision, it can submit the exact computed state used at that moment. StateMirror preserves the snapshot faithfully for later inspection, dispute resolution, and audit workflows.
StateMirror does not decide outcomes, enforce rules, or alter application behavior.
It records facts only. Your code owns the decision and the action.
What it records
- Computed state at decision time (opaque JSON payload)
- A stable decision reference (your evidence_ref)
- Capture and receipt timestamps
- Integrity hashes for tamper-evident storage
What it does NOT do
- Does not compute state
- Does not interpret payload meaning
- Does not enforce allow/deny outcomes
- Does not provide search/analytics over payload contents
- Does not replace logging, tracing, or event sourcing
Typical use
Immediately before executing an outcome (allow/deny, grant/revoke, approve/reject), your application submits a snapshot of the computed state. Later, support retrieves it by snapshot_id or evidence_ref.
Important
Recorded facts are not enforcement.
StateMirror preserves what you submit. Your system owns outcomes.
If snapshots are missing or cannot be written, your application must handle the outcome explicitly.
Self-hosted. Read-only retrieval. No SLAs. No emergency support.
Failure modes
- Snapshot not submitted at decision time → no record exists later
- Payload is incomplete → snapshot is faithful but insufficient
- Idempotency not used → retries can create duplicate records
- Clock skew → captured_at and received_at differ (expected)
- Database/network failure → ingest or retrieval can fail or time out
- Misusing snapshots as authorization proof → unsafe application behavior