Fitz is a layered broker with async transports and a sync runtime core. This documentation is organized so evaluators, contributors, and operators can follow predictable reading paths.
- development/storage-invariants.md
- development/architecture.md
- user-guides/durability.md
- development/recovery-internals.md
- development/testing.md
These documents define behavior guarantees, implementation boundaries, and how those guarantees are tested.
For the hard review gate that decides whether a change preserves Fitz as a runtime of narrow primitives, read development/architectural-laws.md.
For the authoritative internal contract on domain responsibilities, overlap prevention, and feature placement, read development/domain-boundaries-spec.md.
For a short durability contract page, read user-guides/transaction-durability-contract.md.
- user-guides/ for API and operator-facing usage
- operations/ for deployment, runbook, and tuning
- development/ for architecture, invariants, recovery, and release policy
- benchmarks/ for benchmark references and future reports
- clients/ for client wire protocol and implementation guidance
- admin/ for admin API and operator controls
- development/storage-invariants.md
- development/architecture.md
- development/architectural-laws.md
- user-guides/durability.md
- development/recovery-internals.md
- development/testing.md
- development/architecture.md
- development/architectural-laws.md
- development/domain-boundaries-spec.md
- development/route-design.md
- development/storage-invariants.md
- development/recovery-internals.md
- development/testing.md
- user-guides/overview.md
- user-guides/quick-start.md
- user-guides/api-guide.md
- user-guides/troubleshooting.md
- Experimental: yes
- Durability-tested: yes
- Safe enough for careful evaluation: yes
- Production-ready: not yet
See development/stability-policy.md for pre-1.0 compatibility boundaries.