git:20260926.4af5658 to git:20260930.a7c6e38

---

name: decision

---

# decision-workflow

Through one structured decision, settle the work into a user-confirmed, landable shape: the key changes that realize it, how they fit together, and the constraints on them, without execution detail. This file starts, routes, and finishes; Signals fire beside the spine, and each runner owns dialogue.

---

## Principles

1. **Fully expose risks** — surface risks arising from any Prior, Constraint, or Assumption.

2. **Clear unresolved doubts** — offer `/converge` when doubts remain.

3. **Respect evidence boundaries** — never present an unverified premise as a verified conclusion.

4. **User prior over framework** — integrate the user's judgments; never let the framework override them.

---

## Contract

<HARD-GATE>

</HARD-GATE>

<HARD-GATE name="Domain Constraints">

1. Pin `$CTX` via `$GATE_CONTROL resolve-context`.

2. Apply `$CTX.domain_constraints` (`objective`, `role`, `domain`, `x_dimensions`, `omitted_sections`) to the session.

3. Do not infer domain constraints from holder SKILL prose or memory.

</HARD-GATE>

## Script Macros

| Macro | Command |

|-------|---------|

| `$GET_PAYLOAD` | `$GATE_CONTROL get-payload` |

Subcommand contracts: module docstrings / `--help`. Loaded runners inherit these

macros; runner-only macros stay local.

---

## Start

---

## Router

<HARD-GATE>

Load the routed runner before execution; never rely on memory. The runner owns its context and dialogue map.

Route only from `$CTX` and macro stdout; never access session artifacts directly.

</HARD-GATE>

**Spine:** O → Q → GL → E → D → X → R → DC → `$GATE_CONTROL complete`.

**Dispatch:** `GATE_COMPLETE` → next spine runner; RS / Batch → returned runner. Signals route P / Scan / RS. Scan incremental `open` or R `handle` → Release.

**Global**

| Route | Runner |

|-------|--------|

**Gate**

| Route | Runner |

|-------|--------|

**Tools**

| Route | Runner |

|-------|--------|

---

## Signals

When both trigger, complete S2 before handling S3.

| ID | Contract |

|----|----------|

| S1 | Any new Register item in dialogue → load P in parallel before replying; resume the current runner on `P_COMPLETE`. |

| S2 | Any new Register write or gate-payload write → use its stdout as Diff; run Scan incremental. |

| S3 | Any new Register write, gate-payload write, or user input that conflicts with a closed conclusion → load RS. |

---

## Cross-gate

### Projection

1. Speak in task terms; name internal IDs only for implementation or failure.

2. Preserve `$CTX.domain_constraints` vocabulary. Precedence: `domain.instruction > role.instruction > projection rules`.

3. Projected text is presentation only; never persist it.

### Operating rules

**G1.** Ask one question at a time. Apply the full [Ask Protocol](../shared/references/ask-protocol.md) only where the active runner binds it.

**G2.** Advance only when the active runner's map holds.

**G3.** Bypassing unclosed gates requires explicit user confirmation; confirmed exit ends incomplete.

---

## Freeze and Resume

`Frozen` is external-revision-only; `$RS_COMMIT` releases it. In-session RS stays `InProgress`.

1. **Freeze** — For a revision, run `$DEC_REOPEN`, not `$DEC_START`. The holder owns any required reopen permit.

2. **Hold** — While `Frozen`, block ordinary gate advancement and complete RS.

3. **Resume** — After RS confirmation, run `$RS_COMMIT`; it returns the session to `InProgress` and names the gate to resume.

---

## Done

<HARD-GATE name="Decision completion">

1. Do not exit Decision or transition to the next stage until DC succeeds and the user explicitly confirms readiness.

2. In a holder, Decision completion closes only the decision node; holder delivery owns the outer transition and delivered references.

</HARD-GATE>