docs: record the first run of the work breakdown structure and of stated choices reaching Checks
Some checks failed
validation / verify (push) Failing after 10s

Case 08: a plan of 9 work packages and 15 activities, 7.2 weeks against a
10-week window, with the customer's carrier circuit on the critical path. The
stated topology was built this time. The owner keeps the estimates as they
are: one experienced engineer, no contingency.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-11 21:04:28 +01:00
parent f54af24169
commit b66d18fe94
2 changed files with 24 additions and 0 deletions

View File

@@ -26,3 +26,18 @@ Differs from the spec:
Durations are a model's estimates. The Deliverable says so.
Tests: `tests/execution/test_work_breakdown.py` (16).
## First run with real models, 2026-10-11
`case-08-landing-zone`, results `20261011T185421Z`. The delivery planner made one model request, about $0.32.
- **The plan:** 9 work packages under one parent and 15 activities. Every one of the design's Elements is in a work package, and each work package lists the Checks that make it done.
- **The schedule:** 36 working days, 7.2 weeks, with the team of 3 the scope states. Inside the 10-week window with 2.8 weeks to spare.
- **The critical path is the customer's:** ordering the interconnect circuits, 30 days, then the routers and attachments, then validation in the three environments the scope names. The team's own work is done by about Day 13 and waits.
- **The timeline was added to the solution guide** and its numbers are in `execution.json`.
To look at:
- **The estimates look short for an enterprise landing zone.** Two days for the hub and spoke networks, one for the pipeline and state, two for the resource hierarchy. The planner was told to estimate for one engineer who knows the provider and not to pad, and it did. Whether to ask for a contingency, or a range, is the owner's call.
- **The plan's length rests on one assumed number,** the 30-day carrier lead time, which the planner chose. It is shown as the customer's and as an assumption.
- No start date was in the spec, so there are no calendar dates and no Mermaid chart.