feat: a work breakdown structure with a computed timeline (iteration 10)
Some checks failed
validation / verify (push) Failing after 10s
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:
@@ -35,6 +35,7 @@ from app.workflows.chain import (
|
||||
)
|
||||
from app.workflows.changes import check_requirement_changes
|
||||
from app.workflows.target_architecture import GRAPH_ATTACHMENT
|
||||
from app.workflows.work_breakdown import WORK_BREAKDOWN_FILE, check_work_breakdown
|
||||
|
||||
|
||||
class PhaseId(StrEnum):
|
||||
@@ -62,6 +63,8 @@ class DeliverableKind(StrEnum):
|
||||
ARCHITECTURE_DESCRIPTION = "architecture_description"
|
||||
DEPLOYMENT_GUIDANCE = "deployment_guidance"
|
||||
VALIDATION_RESULTS = "validation_results"
|
||||
# The plan for building what was designed and validated (iteration 10).
|
||||
WORK_BREAKDOWN = "work_breakdown"
|
||||
SOLUTION_GUIDE = "solution_guide"
|
||||
|
||||
|
||||
@@ -200,6 +203,16 @@ DEPENDENCY_GRAPH: Mapping[DeliverableKind, DeliverableSpec] = {
|
||||
attachments=(VERDICTS_FILE,),
|
||||
working_copy=_K.DEPLOYMENT_GUIDANCE,
|
||||
),
|
||||
DeliverableSpec(
|
||||
_K.WORK_BREAKDOWN,
|
||||
PhaseId.PACKAGING,
|
||||
"delivery-planner",
|
||||
depends_on=(_K.VALIDATION_RESULTS,),
|
||||
sections=("Approach",),
|
||||
attachments=(WORK_BREAKDOWN_FILE,),
|
||||
# A plan covers the design and how it is built: the graph and the code.
|
||||
reads_in_full=(_K.TARGET_ARCHITECTURE, _K.DEPLOYMENT_GUIDANCE),
|
||||
),
|
||||
DeliverableSpec(
|
||||
_K.SOLUTION_GUIDE,
|
||||
PhaseId.PACKAGING,
|
||||
@@ -234,6 +247,7 @@ DATA_CHECKS: Mapping[
|
||||
_K.TARGET_ARCHITECTURE: (GRAPH_ATTACHMENT, check_target_architecture),
|
||||
_K.DEPLOYMENT_GUIDANCE: (IMPLEMENTATION_FILE, check_implementation),
|
||||
_K.VALIDATION_RESULTS: (VERDICTS_FILE, check_verdicts),
|
||||
_K.WORK_BREAKDOWN: (WORK_BREAKDOWN_FILE, check_work_breakdown),
|
||||
}
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user