Statesman documentation

Statesman makes the composition root the authoritative declaration of application state. The runtime created from that declaration handles acquisition, transitions, observation, history, freshness, and persistence without binding callers to one UI architecture or storage system.

Start with Getting started. The architecture document explains the model and invariants, while the implementation plan maps the path from this first vertical slice to a stable distributed-capability platform.

Read by task

• I need to adopt Statesman in an existing application: Migration guide
• I need to combine several endpoints into one state: Loaders
• I need controlled typed transitions: Interactions
• I need independent tenants, users, devices, or documents: Boundaries and partitions
• I need several authorities in one process: Multiple roots
• I need to understand fresh, current, cached, and conflict behavior: Consistency
• I need durable history: Ledger and providers
• I need process-local subscriptions: Observation
• I need hosted polling and secure inspection: Hosting
• I need architectural enforcement: Analyzers
• I need deterministic tests: Testing
• I need API or diagnostic details: Public API, manifest, and diagnostics
• I am preparing a production deployment: Observability and production readiness
• I need the repository and release automation checklist: Repository release readiness

See the glossary, ADRs, and repository roadmap for vocabulary and design history.