Skip to content
SELF-HOSTED DECISION EVIDENCE

StateMirror

[ Run StateMirror locally ][ Read the specification ][ GitHub ↗ ]

StateMirror preserves the evidence your application submits when it acts. Retrieve that context later, after rules and operational state have changed.

Preserve, verify and inspect

#

StateMirror preserves structured decision evidence at the moment your application acts. Your application submits the evidence payload. StateMirror preserves it as a snapshot with integrity metadata. After successful ingest, the service interface does not expose snapshot updates or deletion.

PRESERVE
Store the evidence payload your application submitted by reference.
VERIFY
Check payload/hash/chain integrity. Verification does not prove decision correctness, policy correctness or upstream truth. See verification respond to modified evidence →
INSPECT
Retrieve the preserved snapshot when support or engineering needs to answer what the application knew when it acted.
EXPORT
Export evidence for support tickets, internal reviews or offline inspection.

When this matters

#
ACCESS
A customer disputes an access denial, downgrade, restriction or expired entitlement after current state has moved on.
REVIEW
Support, risk, finance or engineering needs to inspect what the application submitted when it acted.
AUTOMATION
An automated workflow needs its input context reviewed after rules or upstream state have changed.

Evidence example

#
FIG 01 / JSONTX_EVIDENCE
{
  "subject": "customer_123",
  "inputs": {
    "plan_status": "active",
    "seats_used": 10,
    "seat_limit": 10,
    "read_at": "2026-06-15T18:22:30.000Z"
  },
  "rule_version": "access-rules@2026.06.12",
  "decision": "deny",
  "reason": "seat_limit_reached",
  "correlation_id": "request_001"
}
Application-submitted state_payload.

StateMirror accepts application-defined JSON; this site uses one consistent example shape for demonstration. This is state_payload content; the quickstart shows the full envelope and required headers.

Why not use logs or database history?

Logs record what the system emitted. Current rows show what is true now. History tables and event streams can help reconstruct earlier state. The remaining question is which facts the application actually consulted.

Compare logs, audit logs, databases and event systems →

StateMirror Core

#

StateMirror Core v1.0.0 is the complete, free Apache-2.0 product. Run it on your own infrastructure with capture, retrieval, integrity verification, inspection and export.

Current paid Standard and Commercial packages are optional versioned artifact and license packages. They do not unlock additional StateMirror runtime capabilities.

Use Core directly when Apache-2.0 and the repository distribution model fit your organization. Choose a paid package when you specifically need its packaged artifact or license terms.

StateMirror Production is a planned maintained lifecycle offering and is not currently available. Compare packaging, licensing and product direction →

Application ownership

#

Your application queries state, evaluates policy and owns decisions and actions. StateMirror preserves submitted evidence; it does not enforce outcomes or execute workflows. Verification checks evidence integrity and cannot establish upstream truth or decision correctness.

Evidence scenarios → · Download datasheet →