A delivery process designed for irreversible boundaries

Each phase produces reviewable artifacts. You can stop at the Spec Pack, continue into Scaffold, or proceed to Full Build—without locking into a hosted platform.

Phase 0 — Intake & scoping

• Confirm the initial sink set and what irreversible means in your system context.
• Determine which tier fits your goals and internal engineering capacity.
• Establish scope boundaries explicitly: declared sinks only.

Phase 1 — Irreversible sink inventory

• Map proposed execution paths to the irreversible commit points.
• Define sink interfaces at the level required to specify invariants.
• Identify failure modes where rollback/monitoring would be too late.

Phase 2 — Spec Pack (Tier 1 completion point)

• Write invariants and decision semantics (ALLOW / VETO; UNKNOWN ⇒ VETO).
• Define evidence requirements for both paths.
• Deliver a spec that is stable enough to implement and validate.

Phase 3 — Scaffold (Tier 2 completion point)

• Provide integration-ready scaffolding aligned to sink boundaries.
• Provide test harness structure and initial cases.
• Deliver a handoff package your team can build on—or proceed to Full Build.

Phase 4 — Full Build + Evidence Pack (Tier 3 completion point)

• Implement the governance layer for declared sinks.
• Run tests that demonstrate veto/allow behavior at the boundary.
• Deliver the Evidence Pack + handover materials for engineering ownership.

Phase 5 — Maintenance / Retainer (Tier 4)

• Update invariants and tests as sinks evolve.
• Refresh evidence artifacts when execution surfaces change.
• Provide engineering continuity without shifting to a hosted platform model.