SIMPLESTATES / DECISION EVIDENCE

SIMPLESTATES

FLAGSHIP PRODUCT

StateMirror preserves submitted decision-time evidence: what the application knew when it acted, packaged so it can be inspected and integrity-verified later.

[ Start with StateMirror ][ Inspect Core on GitHub ][ View example ]

STATEMIRROR

FLAGSHIP / DECISION EVIDENCE LEDGER

When a production decision is questioned later, logs and database rows often help reconstruct what might have happened. StateMirror preserves the evidence package the application submitted when it made the decision.

PROBLEM

A customer is denied access even though their plan was active yesterday. The question is not only whether the denial happened. It is what the application knew when it acted.

PRESERVES

Submitted decision-time evidence, hash and chain metadata, capture time and enough context to inspect the decision later without pretending current state is historical state.

BOUNDARY

The application decides and executes outcomes. StateMirror preserves submitted evidence. Verification proves the preserved evidence has not changed.

ONE EXAMPLE

ACCESS DENIAL / DECISION-TIME PACKAGE

A customer says their plan was active yesterday. The application denied access at 18:22 UTC. StateMirror keeps the submitted evidence package from that decision moment.

Application -> decision -> submitted evidence -> StateMirror
Verification -> payload/hash/chain integrity only

{
  "customer_id": "cust_123",
  "plan_status": "active",
  "entitlement_state": "seat_limit_reached",
  "operator_hold": false,
  "trial_expiry": "2026-06-15T18:00:00Z",
  "rule_version": "access-rules@2026.06.12",
  "captured_at": "2026-06-15T18:22:31Z",
  "decision_outcome": "deny"
}

Logs may show the denial happened.
Database rows may show current state later.
StateMirror preserves the submitted evidence package from then.

COMPARE

LOGS / ROWS / AUDIT / OBJECTS / STATEMIRROR

LOGS

Useful for events and traces, but not necessarily the complete decision context.

DATABASE ROWS

Useful for current or queried state, but mutable rows may not prove what was consulted at the decision moment.

AUDIT LOGS

Useful for activity trails, but often not the full evidence bundle the application used.

OBJECT SERIALIZATION

Captures object shape. StateMirror is about a canonical, idempotent, append-only, verifiable evidence record with integrity metadata.

STATEMIRROR

Preserves submitted decision-time evidence and verifies that the preserved evidence has not changed.

SIGNALS

SECONDARY / STRUCTURED INPUT FACTS

PlanSignal, DenySignal, and ExpirySignal are companion primitives for reading focused facts before the application decides. They can also be useful evidence shapes inside submitted StateMirror snapshots.

PlanSignal   -> plan, tier, entitlement, commercial state
DenySignal   -> holds, restrictions, operator denials
ExpirySignal -> trials, licenses, temporary access, validity

Signals emit/read facts.
Applications decide and execute outcomes.

BOUNDARY

APPLICATION-OWNED OUTCOME

State is queried. Decisions are made. Actions remain application-owned. StateMirror does not decide, enforce policy, execute workflows, prove upstream truth, prove decision correctness, or own application behavior.

GITHUB

OPEN SOURCE CORE v1.0.0

[ StateMirror Core ] [ Core v1.0.0 ] [ StateMirror Product ] [ Products ]

State is queried. Decisions are made. Actions remain application-owned. Verification only proves preserved evidence integrity.