Organized by what you’re trying to do (Diataxis):
| Read this | When | |
|---|---|---|
| Tutorial | Your first ledger | You’re new — zero to a funded, streaming ledger in seven steps |
| How-to | Run on Postgres | You’re deploying — compose, auth, LB readiness, multi-instance, metrics |
| How-to | Run on the append-log store | You’re deploying single-node — no database, embedded log storage, backups |
| How-to | Use the Rust SDK | You’re integrating from a service — retries, idempotency, streaming |
| How-to | Integrate via an AI agent | Your coding agent is doing the integration — dense rules, drift-tested endpoint table, verification recipe |
| Reference | HTTP API | You need the exact wire contract — routes, shapes, errors, config |
| Explanation | Architecture & design | You want to know why — gapless sequences, group commit, the failure story |
| Explanation | The append-log store | Why the embedded backend works — group commit at the fsync, ack-after-fsync, recovery |
Shorter summaries live in the project README; per-crate READMEs cover each crate’s surface. The interactive API reference is served by any running instance at /docs. For LLM consumers, llms.txt indexes this set at the docs-site root.
Workflow note:
docs/superpowers/holds untracked working documents (specs/plans) — not part of this documentation set.