FE-829: Build-architect for spec-derived cook plans#184
Closed
kostandinang wants to merge 1 commit into
Closed
Conversation
…ct spec Add the plan-build-architect frontier (FE-829, stacked on FE-827): evolve `brunch plan` from a sequencer into a build-architect emitting fixture-quality, cook-executable plans. SPEC: A100-K (contract-completeness assumption), D167-K (emitter guarantees cook-executability via a producer-agnostic PlanContract + deterministic repair), I129-K (every emitted plan satisfies the executability contract), and Future Direction \xc2\xa7Cook plan generation (build-architect arc + deferred D160-K amendment). PLAN: frontier added to Sequencing (Active #8) and Frontier Definitions with the four-slice breakdown; resolves FE-800's integration-blind follow-on. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack Context
Stacked on FE-827 (#182). Part of the cook/orchestrator track: FE-800 (spec→cook-plan emitter) → FE-826 (spec-derived mode) → FE-827 (policy-selected slice layout + greenfield promotion) → FE-829.
This frontier evolves
brunch planfrom a sequencer into a build-architect that emits fixture-quality, cook-executableplan.yaml— closing the gap to the hand-authored reference fixtures (parallel-utils,layered-todo,resilient-pipeline), which already execute correctly in the orchestrator.Why?
FE-800 makes
brunch planproduce a faithful but un-buildable projection of the spec's requirement graph: plausible-lookingdepends_onthat are conceptual references rather than build order, no decomposition, no join slice, no epic integration seam — so multi-slice epics produce "green checks, no assembled artifact" (the FE-800 integration-blind follow-on).What (this PR — planning only)
Planning commit that registers the frontier and records the design in canonical docs. No code yet — draft for visibility while slice 1 is built.
A100-K(contract-completeness assumption),D167-K(emitter guarantees cook-executability via a producer-agnosticPlanContract+ deterministic repair),I129-K(every emitted plan satisfies the executability contract), Future Direction §Cook plan generation (build-architect arc + the deferredD160-Kamendment).plan-build-architectfrontier — Sequencing (Active) + Frontier Definition with the four-slice breakdown.Slices
PlanContract.check(acyclic deps over existing ids; ≥1 verification target/slice; slice∈epic; requirement coverage; multi-slice epic carries anintegration-testseam) + a repair loop that auto-fixes the mechanical class (cycle-break, mint target, synthesize epic seam) and surfaces the design class as typed warnings. No LLM, noD160-Kchange.D160-Kamendment + aSlice.writesschema field.🤖 Generated with Claude Code