Delivery plan

How to read this document. Delivery runs as increments — streams of work, each cut from confirmed scope and measured against a baseline. A closed increment is shipped history; an active one is the current build. Two sections: what has shipped, and what is being built now — each embedding its increment live, so status here is the record's status. The forward view closes the document.

Shipped

One increment is closed: the foundation everything else stands on, live in production since 6 July 2026.

INC-1 — Slice 1 — item store skeleton (closed)

The system of record made real: seven item types with lifecycles and full revision history, typed links forming the scenario spine, telemetry events on every mutation, engagement profiles for tailoring, the Explorer's engagement pages, and a fail-closed API. Everything built since runs on it.

In build

The active increment delivers the review workspace against Baseline #1 (6 July 2026), which pinned the confirmed scope. Any scope change during this build is a visible diff against that baseline — the plan cannot drift silently.

INC-2 — Slice 2 — review workspace (active)

The consultant review experience, cut from Baseline #1: document and increment types, releases that pin exact item versions (review rounds and baselines), the diff engine, threaded comments, and the embed-expanding document reader — all shipped. Remaining in this increment: review actions with consultant login, the digest page, and redlines.

What comes after

In deliberate order: review actions in the UI with consultant login — the last mile before review happens fully in the product · the review digest page (the fatigue valve) · the client loop (slice 3: tokenized access, review rounds, uploads) · then engagement #1 — a real client, where the Vision's success criteria stop being aspirations and get measured.