nhi.sgit.ai / packs / static-publishing / implementation-phases

05 — Implementation phases

PackStatic Publishing, `sgit vault serve`, and the Publishing Matrix RoleP1–P7 (plus P4b, published API docs) with file lists, acceptance criteria and risk; start with P1 + P3 Date17–19 August 2026 · pack v0 OriginArchitect-review agent, SGit-AI__CLI repo Sourceraw markdown · original on GitHub Captured19 August 2026, at commit 2cedd9a — the raw file under src/ is byte-identical to that commit

Summary

Independently shippable phases, each one PR with green suites and its own acceptance criteria. P1 (static read transport — promote the spike, don't redesign it) and P3 (vault serve) start now: demonstrable value with zero commitment to the publish protocol still being decided; the revision adds P4b, the published API docs, gated on P2. Acceptance criteria are concrete down to the trap: add a >4 MB fixture, because small fixtures will not catch the large-blob path.

Key concepts

Promote the spike — the P1 design already exists as running code — productionising it is the task
Ship value before protocol — P1+P3 first is itself one of the ten decisions, with a recommendation

Key ideas

Independently shippable phases keep every PR reviewable and every rollback cheap.
Risk is stated per phase — the two mediums are where the publish protocol touches disk.

Read the document

📄 Pack document · 05__implementation-phases.md · rendered from the raw markdown (the source of truth)

← 04 — Invariants & tests 06 — Decisions & evidence →