feat: start an Execution from a scope spec (ADR-0008, iteration 9 step 1)
Some checks failed
validation / verify (push) Failing after 10s
Some checks failed
validation / verify (push) Failing after 10s
A scope spec is a YAML file of what the customer wants and the facts a design depends on, complete or partly filled. It sits beside the Intent, which stays in the customer's words. - skills/scoping holds a provider-neutral catalogue of 63 fields; the Cloud provider's bundle supplies the values it allows for the fields left to it. - app/scope.py reads a spec against the catalogue with no model: it refuses an unknown field or a value of the wrong type, and yields what is stated, what is left to the agent, what is unknown and how pressing each gap is. A field may say ask, decide or not_applicable. - ExecutionEngine.start(scope=...), /generate, A2A metadata and evaluation cases accept one. Its statement is the request, its engagement reference names the Customer case, and its run options apply. A pre-approved start is refused when an essential field is not settled. - The spec as supplied is kept unaltered beside a completed copy with assumptions, gaps, provenance, readiness and a status. - Every Specialist is shown the spec and given the Skill: a stated choice binds, exclusions are out of scope. - Covers workloads and platform foundations; case-08-landing-zone starts from a benchmark spec. Plans for scoping (iteration 9) and the work breakdown structure (iteration 10, nothing built), and the design spec they come from. Not run with real models. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
23
.agents/plans/iter-10-work-breakdown/MAP.md
Normal file
23
.agents/plans/iter-10-work-breakdown/MAP.md
Normal file
@@ -0,0 +1,23 @@
|
||||
# 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:** planned; nothing built
|
||||
**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 `delivery` section (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 | planned |
|
||||
| 2 | The schedule computed in code: start and finish day, critical path, team size as a limit | planned |
|
||||
| 3 | The three views written by code: WBS dictionary, activity sequence list, timeline on a relative axis | planned |
|
||||
| 4 | The delivery window checked; assumptions the plan depends on shown on the timeline; milestones | planned |
|
||||
|
||||
Decisions the owner accepted on 2026-10-11: after validation, in the packaging Phase; grouped by component; the technical build only.
|
||||
Reference in New Issue
Block a user