Some checks failed
validation / verify (push) Failing after 10s
A new Deliverable in the packaging Phase, produced by a delivery planner after validation. - The planner writes the plan as data: work packages that name the Elements they deliver, and activities with days, what each follows, and whether the team or the customer owns it. - Code checks the plan against the design: every Element belongs to a work package, and the activities can be scheduled. - Code computes the schedule, with no more of the team's activities at once than the team has people, and the critical path. - Code writes the WBS dictionary (a work package is done when the Checks on its Elements pass), the activity sequence and a timeline on a relative axis from Day 0. - The plan is checked against the delivery window from the agreed scope; over it, the Deliverable says by how much and names the critical path. - With a start date it also gives calendar dates and a Mermaid Gantt chart. - The timeline is added to the solution guide, and the plan's length is in execution.json and the packaging Approval. Not run with real models. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Plan Map
Iteration: 10, Work breakdown structure Intent: Deliver a plan for building the Target architecture: work packages traced to its Elements and Checks, activities in sequence, and a timeline on a relative day axis that code computes and draws. Status: steps 1 to 4 built on 2026-10-11, without milestones; not run with real models This directory covers: steps 1 to 4
Sources of truth
.scratch/scoping-and-work-breakdown/spec.md, section "The work breakdown structure".docs/adr/0005-the-target-architecture-is-an-explicit-graph.md: the ids it traces to.- Iteration 9 step 1: the scope spec's
deliverysection (team size, window, commercial model).
Status
| Step | What | Status |
|---|---|---|
| 1 | The Deliverable, its Specialist and its data file; every Element in a work package, checked in code | built 2026-10-11 (steps/step-1-to-4.md) |
| 2 | The schedule computed in code: start and finish day, critical path, team size as a limit | built 2026-10-11 (steps/step-1-to-4.md) |
| 3 | The three views written by code: WBS dictionary, activity sequence list, timeline on a relative axis | built 2026-10-11 (steps/step-1-to-4.md) |
| 4 | The delivery window checked; assumptions the plan depends on shown on the timeline; milestones | built 2026-10-11, without milestones (steps/step-1-to-4.md) |
Decisions the owner accepted on 2026-10-11: after validation, in the packaging Phase; grouped by component; the technical build only.