SIMPLESTATES / DIAGRAM ARTIFACTS

Diagrams

PURPOSE

These diagrams explain the decision evidence boundary: applications read state, make decisions, emit evidence, and StateMirror preserves that evidence for later integrity verification.

STATEMIRROR BLUEPRINT

APPLICATION FLOW / EVIDENCE PRESERVATION

StateMirror preserves decision-time evidence. The application reads state, applies business logic, owns the decision and action and submits an evidence snapshot for later inspection. Logs, traces, databases and Stripe state remain post-hoc reconstruction sources.

EXTERNAL

External systems may emit observed state, such as Stripe subscription events

PROTOTYPE READ

SignalRelay is an experimental sensor layer for stale-aware local reads. It is not authoritative and is not part of the StateMirror evidence ledger.

READ

Application reads PlanSignal, DenySignal, ExpirySignal, and app state

DECIDE

Application owns business logic and outcome

PRESERVE

StateMirror preserves the submitted evidence snapshot

VERIFY

Later integrity verification covers payload/hash/chain continuity only

BLUEPRINT

SIMPLESTATES / STATEMIRROR BLUEPRINT
============================================================

CORE BOUNDARY

  State is queried.
  Decisions are made.
  Actions remain application-owned.


APPLICATION
------------------------------------------------------------

  [1] Application reads state
      - PlanSignal: plan, tier, entitlement, commercial state
      - DenySignal: explicit denial state
      - ExpirySignal: validity and expiration state
      - SignalRelay: prototype external state observer / sensor only
      - Application state: local records, context, user input

  [2] Application applies business logic
      - Evaluates the facts it queried
      - Applies product rules and local decision logic
      - Owns the decision outcome

  [3] Application owns action
      - Grants, denies, charges, pauses, approves, rejects, or routes
      - Handles failures, retries, fallbacks, and user experience
      - Keeps application behavior outside StateMirror

                         |
                         | submits evidence snapshot
                         v


STATEMIRROR
------------------------------------------------------------

  [4] StateMirror preserves submitted evidence
      - Stores the submitted snapshot payload
      - Preserves submitted facts and timestamps
      - Maintains immutable snapshot records
      - Treats payload meaning as application-owned

  [5] Later inspection / integrity verification
      - Retrieve evidence by reference
      - Inspect what the application submitted
      - Verify payload/hash/chain integrity
      - Verification does not prove decision correctness


PROTOTYPE SENSOR LAYER
------------------------------------------------------------

  External systems -> SignalRelay -> Application
  Application -> decision -> evidence -> StateMirror

  SignalRelay observes external state and exposes it locally for
  application consumption. It does not define decisions or system
  truth. It is an experimental sensor layer, not part of the
  StateMirror evidence ledger.

  Freshness is evidence. Risk tolerance is application logic.
  SignalRelay is not authoritative, not decision-making, not
  production core, not available for procurement, and not a
  replacement for Stripe.


OPTIONAL EVIDENCE LANES
------------------------------------------------------------

  PlanEvidence
      Optional canonical shape for submitted plan evidence.

  DenialEvidence
      Optional canonical shape for submitted denial evidence.

  ExpiryEvidence
      Optional canonical shape for submitted expiry evidence.

  Evidence Lanes are useful inside submitted snapshot payloads.
  They are not required formats. StateMirror does not validate,
  enforce, or interpret them as policy.


EXPLICIT NON-CAPABILITIES
------------------------------------------------------------

  StateMirror does not:
      - decide
      - enforce
      - evaluate policy
      - execute workflows
      - replace observability
      - own application behavior
      - prove the application made the correct decision


SUMMARY
------------------------------------------------------------

  Application reads state.
  Application makes decision.
  Application emits evidence.
  StateMirror preserves snapshot.
  Verification checks integrity only.
  Actions remain application-owned.

COMPOSITION

READ-TIME FACTS / WRITE-TIME EVIDENCE

PlanSignal     -> plan / entitlement fact (read-time)
DenySignal     -> denial fact (read-time)
ExpirySignal   -> temporal validity fact (read-time)
SignalRelay    -> external state sensor (prototype / not authoritative)

StateMirror    -> decision-time evidence preservation (write-time)

External system -> SignalRelay -> Application
Application -> decision -> evidence -> StateMirror

Application queries and composes state.
Application owns decisions, actions, and outcomes.

State is queried. Decisions are made. Actions remain application-owned. StateMirror does not decide, enforce, evaluate policy, execute workflows, replace observability, or own application behavior.