Roadmap
BitVault’s phases are gated by demonstrated need, not dates. The thesis: ship correctness in a modular monolith, then extract services with evidence. Each phase ships something usable — no phase is pure plumbing.
The extraction from monolith to services is a primary deliverable of the project, not an afterthought. Every split has a documented forcing function (ADR-0001) and ships with a before/after trace and load test proving the change was safe.
Guiding Principles
- Correctness before distribution. Sync, the commit protocol, and tenant isolation must be right before anything is split.
- Every extraction has evidence. A forcing function named in an ADR; a before/after distributed trace; a load test validating the SLO held.
- Observability precedes scale. You cannot safely extract what you cannot trace.
- Intentional deferrals. Features are unlocked by completing prior phases, not by calendar.
Contents
| Page | What it covers |
|---|---|
| Phases | P0–P5 detail, per-phase deliverables, deferral table, definition of done |
The Story in One Sentence
P0 proves the commit protocol works. P1 makes it useful. P2 adds sync. P3 adds the async derivation plane. P4 extracts services with evidence. P5 widens the surface once the core is proven.