Planning
planningFrom the request to a plan and the acceptance criteria.
Where it sits
one of 5 · closed setRead left to right as the arc of a piece of work. The order is the lifecycle, not a ranking. The arrows show the sequence a blueprint tends to run in, not one it must follow.
The five are the one dimension a local namespace cannot extend. A node type or a risk marker can be coined by anybody. A sixth phase would be a different definition of what a dark factory is. There is no abstract root above them either. A root would make the set look open.
A card may name one of them, several, or none. The five describe the blueprint, not every node inside it. An intake or a retrieval step may declare no phase at all. A node that both builds and repairs may declare two. Neither counts as an incomplete card.
Which phases a blueprint has nodes in is its phase coverage. Phase coverage is shown as a description of scope, for example: this blueprint covers planning, implementation and testing. It is not shown as boxes ticked out of five. A blueprint that stops before deployment has decided where it stops.
Who uses it
11 cards · 8 blueprints- Diff Triager
diff-triager@1.0.0 - Goal Setter
goal-setter@1.0.0 - Metric Setter
metric-setter@1.0.0 - Research Supervisor
research-supervisor@1.0.0 - Retrieval Planner
retrieval-planner@1.0.0 - Review Rubric
review-rubric@1.0.0 - Rubric Author
rubric-author@1.0.0 - Spec Planner
spec-planner@1.0.0 - Stage Planner
stage-planner@1.0.0 - Task Decomposer
task-decomposer@1.0.0 - Work Planner
work-planner@1.0.0
- Adversarial Consensus Line
autogen/adversarial-consensus-line - Checkpoint & Resume Runner
autogen/checkpoint-resume-runner - Grounded Research Desk
autogen/grounded-research-desk - Guarded Merge Bot
autogen/guarded-merge-bot - Hypothesis Tournament
autogen/hypothesis-tournament - Objective Tracker
autogen/objective-tracker - Producer Critic Refinery
autogen/producer-critic-refinery - Starter Software Factory
autogen/starter-software-factory