feat: a work breakdown structure with a computed timeline (iteration 10)
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>
This commit is contained in:
2026-10-11 19:54:17 +01:00
parent 0f80cb642f
commit f54af24169
21 changed files with 1108 additions and 12 deletions

View File

@@ -61,6 +61,12 @@ from app.workflows.target_architecture import (
render_mermaid,
render_tables,
)
from app.workflows.work_breakdown import (
DICTIONARY_HEADING,
TIMELINE_FILE,
)
from app.workflows.work_breakdown import mermaid as plan_mermaid
from app.workflows.work_breakdown import render as render_plan
ORCHESTRATOR = "orchestrator"
logger = logging.getLogger(__name__)
@@ -404,6 +410,16 @@ def specialist_tools(
content = content.split(f"\n## {REVIEW_HEADING}")[0].rstrip() + "\n"
if checklist_review:
content += "\n" + checklist_review
if kind is DeliverableKind.WORK_BREAKDOWN:
# The dictionary, the sequence and the timeline are views of the plan,
# computed and written here: they cannot disagree with it.
views = render_plan(attachments, upstream)
content = content.split(f"\n## {DICTIONARY_HEADING}")[0].rstrip() + "\n"
if views:
content += "\n" + views
chart = plan_mermaid(attachments, upstream)
if chart:
attachments[TIMELINE_FILE] = chart
if is_graph:
# The tables and the diagram are views of the graph, so the engine
# writes them: they cannot disagree with it.