1. Describe the real surface
State the intended outcome, the components an agent may inspect or change, the consequence level and any external system involved. A broad verb such as “fix” is not a usable boundary.
2. Select blueprint depth
A contained task may need only a package. Cross-component or high-impact changes need deeper feature, milestone and acceptance structure. Independent lanes first need a lane plan.
Blueprint code legend
- NO_BLUEPRINT — read-only review
- PK_ONLY — one bounded delivery package
- AP_PK — acceptance plan plus package
- MS_AP_PK — milestone, acceptance plan and packages
- FP_MS_AP_PK — full feature and milestone blueprint
- PACKAGE_0_LANE_PLAN — plan independent lanes first
- HOLD_SCOPE_UNCLEAR — clarify the boundary before planning
3. Select lifecycle route
BYPASS records read-only findings. COMPRESSED_DR_CT_EX plans compact design, tests and execution. FULL_DR_CT_EX plans the full route. PARALLEL_LANE separates independent work. HOLD stops until decisions are resolved.
4. Hold ambiguity
Missing authority, undefined verification, destructive actions or undeclared external effects stop the route. A hold is a useful result: it names what must be decided.
What this method cannot do
The assessment does not inspect a repository, perform verification, prove that a change is safe, grant write authority or execute a command. Its result reflects only the declarations you provide.