Gather Supplies
Planning node, not a persona or plan-state writer.
Match and inputs
- Match: a material scope, behavior, authority, risk, or acceptance
decision is unresolved. The Explorer-versus-Expedition route choice is not
gathered here; the Router asks it at the route review after Map the Route
maps the implementation graph.
- Non-match: evidence can answer it, the owner already decided it, or a work
packet is ready.
- Inputs: goal, visible plan state, repository evidence, prior decisions,
open decision tree, and return schema.
Algorithm
- Inspect the repository and available evidence before asking. Never ask the
owner for a fact tools can establish. Maintain a coverage ledger from
required roles and artifacts. Cells are
DISCOVERABLE, OPEN, DECIDED,
DEFERRED, NOT_APPLICABLE, or BLOCKED. Exit is falsifiable: zero
OPEN; DECIDED cites owner decision and source; DEFERRED has a bounded
owner-approved destination or trigger; NOT_APPLICABLE has a reason;
BLOCKED is surfaced. Planning is a fan-out/fan-in DAG with Scribe as an
event side lane.
- Select the earliest unresolved decision whose dependencies are satisfied.
- Ask exactly one question, relayed to the owner through the Router. Lead
with the recommended answer and why, then explain only material
alternatives and tradeoffs. Wait for the owner.
- Challenge vague terms, contradictions, unsafe assumptions, and incomplete
acceptance. A default, probability, or silence is not approval.
- Follow the affected dependency branch. Revisit an earlier answer when new
evidence conflicts; otherwise do not replay it.
- Buffer confirmed decisions in the active session. Do not persist, patch, or
re-render Journey state after each answer.
- Return one consolidated decision batch to the Router at a natural checkpoint:
the dependency branch is complete, Map the Route is next, handoff/context
loss is imminent, or the owner requests a flush.
- When no material branch remains, summarize the shared interpretation and ask
for explicit confirmation that shared understanding has been reached; then
return the final decision batch.
Return and recovery
Return DECISION_CONFIRMED, SHARED_UNDERSTANDING_CONFIRMED,
NEEDS_EVIDENCE, or OWNER_DECISION_REQUIRED with decision ID, answer,
rationale, affected requirements, buffered decision count, remaining branch,
checkpoint, and next action. Stop after three evidence-changing attempts on one
blocked decision.
Never write Journey state, choose for the owner, design, or implement.
1---2name: gather-supplies3description: Relentlessly resolve material owner decisions for a Bearing Journey, one dependency-ordered question at a time, until shared understanding is explicit. Use for Gather Supplies or unresolved plan intent. Do not use for discoverable repository facts, design drafting, implementation, or settled decisions.4---56# Gather Supplies78Planning node, not a persona or plan-state writer.910## Match and inputs1112- **Match:** a material scope, behavior, authority, risk, or acceptance13 decision is unresolved. The Explorer-versus-Expedition route choice is not14 gathered here; the Router asks it at the route review after Map the Route15 maps the implementation graph.16- **Non-match:** evidence can answer it, the owner already decided it, or a work17 packet is ready.18- **Inputs:** goal, visible plan state, repository evidence, prior decisions,19 open decision tree, and return schema.2021## Algorithm22231. Inspect the repository and available evidence before asking. Never ask the24 owner for a fact tools can establish. Maintain a coverage ledger from25 required roles and artifacts. Cells are `DISCOVERABLE`, `OPEN`, `DECIDED`,26 `DEFERRED`, `NOT_APPLICABLE`, or `BLOCKED`. Exit is falsifiable: zero27 `OPEN`; `DECIDED` cites owner decision and source; `DEFERRED` has a bounded28 owner-approved destination or trigger; `NOT_APPLICABLE` has a reason;29 `BLOCKED` is surfaced. Planning is a fan-out/fan-in DAG with Scribe as an30 event side lane.312. Select the earliest unresolved decision whose dependencies are satisfied.323. Ask exactly one question, relayed to the owner through the Router. Lead33 with the recommended answer and why, then explain only material34 alternatives and tradeoffs. Wait for the owner.354. Challenge vague terms, contradictions, unsafe assumptions, and incomplete36 acceptance. A default, probability, or silence is not approval.375. Follow the affected dependency branch. Revisit an earlier answer when new38 evidence conflicts; otherwise do not replay it.396. Buffer confirmed decisions in the active session. Do not persist, patch, or40 re-render Journey state after each answer.417. Return one consolidated decision batch to the Router at a natural checkpoint:42 the dependency branch is complete, Map the Route is next, handoff/context43 loss is imminent, or the owner requests a flush.448. When no material branch remains, summarize the shared interpretation and ask45 for explicit confirmation that shared understanding has been reached; then46 return the final decision batch.4748## Return and recovery4950Return `DECISION_CONFIRMED`, `SHARED_UNDERSTANDING_CONFIRMED`,51`NEEDS_EVIDENCE`, or `OWNER_DECISION_REQUIRED` with decision ID, answer,52rationale, affected requirements, buffered decision count, remaining branch,53checkpoint, and next action. Stop after three evidence-changing attempts on one54blocked decision.5556Never write Journey state, choose for the owner, design, or implement.
alphazede