Learn the database in working increments.
Begin with one transaction. Then add a checkpoint, process teardown, a second family, and publication recovery. Each step keeps the earlier behavior and introduces one new responsibility.
Build from a write to a recovered database.
The maintained Files walkthrough executes the complete path. These chapters explain the same path in the order an application encounters it.
- Create, write, and read one value
Build the source, run the maintained example, and understand the smallest transaction lifecycle.
- Checkpoint and reopen
Publish an explicit checkpoint, close every owner, and recover from the authoritative object graph.
- Add a family and maintain runs
Extend a recovered registry, write to the new family, checkpoint changed families, and select compaction deliberately.
- Resolve an unknown commit
Keep the original receipt, reconcile through reads, and carry Commit resolution authority across process teardown.
Apply the database boundary to your system.
Use these sections after the learning path. They collect the limits and ownership rules that remain application policy.
Choose persisted bounds, bind a provider, preserve borrowed owners, and select synchronous or composable operations.
ArchitecturePublication, isolation, LSM state, and recoveryFollow the immutable object graph and the exact metadata transition that makes a complete history visible.
Support boundaryEvidence, providers, omissions, and current statusSeparate executed evidence from product policy and from capabilities that the experimental profile does not provide.