@windyroad/architect 0.12.0 → 0.12.1-preview.455
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -47,6 +47,18 @@ For each ADR in the ordered queue, surface the decision as an `AskUserQuestion`
|
|
|
47
47
|
- **Reject / supersede** — the auto-made pick is wrong; capture the supersede ticket (see Step 4) and write the **rejected-pending-supersede** marker so the drain stops re-asking.
|
|
48
48
|
- **Defer** — skip this sitting; leave unoversighted for a later run.
|
|
49
49
|
|
|
50
|
+
**Presentation rule — lead with the Decision Outcome, never with the meta (P302).** The AskUserQuestion `question` field MUST open with the one-line Decision Outcome — *what the ADR decides* — phrased as `"This ADR decides: <outcome>"`. Sibling-ADR relationships, supersession lineage, and Considered-Options recording-shape (e.g. "separate ADR vs amend ADR-014") are **meta** about *how the decision was recorded*, not what it decides — relegate them to a trailing clause or omit. This is ADR-074's *name the substance, not the grain* principle applied to the confirm surface itself, and ADR-026 grounding extended from the ADR body to the AskUserQuestion `question` text. Burying the substance behind meta forces a clarifying re-ask: the user cannot tell what they are confirming.
|
|
51
|
+
|
|
52
|
+
*Bad — buries the decision behind meta:*
|
|
53
|
+
- *"a sibling ADR codifying five patterns; ADR-038 governs UserPromptSubmit, ADR-040 governs SessionStart."* (ADR-045 surfaced this way during the 2026-05-25 drain; user replied *"if this decision defers to a sibling decision, what does this decision decide??"*.)
|
|
54
|
+
- *"a separate ADR citing ADR-014 + ADR-018 as lineage, keeping single-purpose ADRs."* (ADR-020 surfaced this way the same session; user replied *"A decision to create a new decision??? What isn't this just the new decision?"*.)
|
|
55
|
+
|
|
56
|
+
*Good — substance-first:*
|
|
57
|
+
- *"This ADR decides: 5 per-tool-call hook patterns + their budget bands. (Sibling to ADR-038 / ADR-040 which govern the other hook surfaces.)"*
|
|
58
|
+
- *"This ADR decides: non-AFK governance skills auto-drain the release queue after commit. (Recorded as a separate ADR rather than amending ADR-014.)"*
|
|
59
|
+
|
|
60
|
+
The trailing clause exists for cross-reference value — it is optional, NOT a re-entry point for meta-leading. When the meta does not add load-bearing context for the confirm decision, omit it entirely.
|
|
61
|
+
|
|
50
62
|
This is a genuine human-decision surface (the whole point of P283) — `AskUserQuestion` is correct here and is NOT over-asking. Do not auto-confirm; do not prose-ask.
|
|
51
63
|
|
|
52
64
|
### Step 4: Apply the outcome
|