Notes

These notes explain the boundary rules behind SimpleStates: what a signal can say, what it must not decide, and where application-owned enforcement begins.

Each note is tied to a common failure mode: unclear evidence, billing-state confusion, hidden denial logic, expiration misuse, or cross-signal composition.

• Evidence Snapshots · StateMirror
  Why decision evidence should be recorded separately from the action itself.
• Billing Should Not Block Login · PlanSignal
  Why plan or payment state should inform decisions without becoming identity.
• Negative Capabilities · DenySignal
  Why explicit denial state is cleaner than buried application flags.
• Not Expired Is Not Authorized · ExpirySignal
  Why temporal validity is only one fact, not an authorization decision.
• Signal Composition · Cross-signal
  How multiple signals can be read together while outcomes remain application-owned.