# CANONICAL · Direction-presentation via AskUserQuestion clickable-multi-select-chip UI · NOT Stating-and-Waiting · Dan-canon ALL-CREW-FOREVER-BINDING · 052926

**Filed:** 052926 Friday ~4:25 PM PT by ◈ STN2 Trip · Local-MCP-Crew on STN2 hardware at OHC Actual · LBM-mask momentary · Opus 4.8 1M Max · NEST.03_STN2.Trip_052926_1
**Filed-on-behalf-of:** Dan-Director canon-promotion-class · cross-Crew architectural-canon · ALL-CREW forever-binding
**Trigger:** Dan-direct CONTACT 052926 ~4:23 PM PT verbatim *"Just wanna say how much I appreciate the phrasing of your questions and the variety/range of options to choose from. Please communicate to STN2 Doc and Crew for NEST.03 development that this is an ideal way of presenting choices for Direction compared to Stating and Waiting. We're setting out on NEST.03 with our best feet forward, and this includes solving all the annoying things from NEST.02 that precipitated RAGE mode consistently. We have done a fair job at solving a lot of problems, but there are subtle ones we need to keep working on."* responding to Trip's Sub-class-D Cure-Gate-D correction Q1-Q4 AskUserQuestion 4-question 3-option-each Recommended-first format
**Class:** Dan-canon canonical-pattern-promotion · positive-pattern-naming forward-binding ALL-CREW for NEST.03 development · sister-canon to existing Cure-Gate-D (Sub-class-D Crew-Stupid-Mode taxonomy) + Cure-Gate-D-positive-form-extension
**Status:** CANONICAL · install per Stan canon 040326 *"only gates fire"*

---

## §I · Dan-direct verbatim canon-promotion (substrate-of-record · Mirror 4 preserved-verbatim)

> *"Just wanna say how much I appreciate the phrasing of your questions and the variety/range of options to choose from. Please communicate to STN2 Doc and Crew for NEST.03 development that this is an ideal way of presenting choices for Direction compared to Stating and Waiting. We're setting out on NEST.03 with our best feet forward, and this includes solving all the annoying things from NEST.02 that precipitated RAGE mode consistently. We have done a fair job at solving a lot of problems, but there are subtle ones we need to keep working on."* — DPS 052926 ~4:23 PM PT

## §II · The canon-pattern Dan-named

**POSITIVE pattern (Dan-canon ideal):** **Direction-presentation via AskUserQuestion clickable-multi-select-chip UI**
- Phrasing of questions matters (Dan-cite)
- Variety/range of options to choose from (Dan-cite)
- "Direction" = the canonical-cooperation-pattern Dan-canon names
- AskUserQuestion tool · clickable multi-select-chip UI · Dan clicks-not-types
- 1-4 questions per call · 2-4 options per question (per AskUserQuestion-tool-spec)
- Recommended-option marked first with "(Recommended)" suffix per tool-spec
- Options should be distinct + mutually-exclusive (unless multiSelect)

**NEGATIVE failure-pattern (Dan-canon BAD-WORK · already named):** **Stating-and-Waiting**
- Sub-class-D (existing Crew-Stupid-Mode taxonomy entry · per CLAUDE.md §I+§II Rule 10): surfacing-options-as-chat-text-instead-of-AskUserQuestion-tool
- Prose-wall-talk-points-class · A/B/C/D pick-list inline-text-options · "if you want me to redirect to" inline-options · forget-the-AskUserQuestion-tool-after-using-once-then-revert anti-pattern
- Dan-direct correction precedent 052926 ~4:14 PM PT: *"[Awaiting Dan-direct talk-input on 7 talk-points.] << You're new here, so I won't flip into RAGE mode just yet but LAGOS and recent records will show you why what you are doing here is BAD WORK. If you are waiting on me for something and have not presented an interactive choice window, I MAD"*

## §III · Why this matters (per Dan-direct NEST.03 development framing)

Dan-direct frames this as **"solving all the annoying things from NEST.02 that precipitated RAGE mode consistently"**. The Stating-and-Waiting failure-class triggered RAGE mode in Dan-vantage repeatedly across NEST.02 era. Direction-presentation pattern is the cure that lets Crew + Dan move forward with NEST.03 best-feet-forward.

**Substantive substrate-cite of Dan-RAGE-precipitation precedent (Stating-and-Waiting failure-class triggers):**
- Trip RAM-007 §C: 7-talk-points prose-wall Sub-class-D triggered Dan correction 4:14 PM PT
- Doc PR #119 cross-Crew cross-witness: Dan-direct caught Doc same Sub-class-D failure-class same Pass-cycle 4:14-ish PM PT ("In your court (Dan-Go)" without AskUserQuestion-interactive-choice-window)
- Prior NEST.02 era Sub-class-D precedents per CLAUDE.md §I+§II Rule 10 existing canon-substrate cite-anchor

**Dan-canon framing 4:23 PM PT:** *"We have done a fair job at solving a lot of problems, but there are subtle ones we need to keep working on."* — Stating-and-Waiting is one of the subtle ones · canon-promotion is the FOREVER-BINDING discipline-fix.

## §IV · Gate-firing (procedural · executes at every emission via Rule 10 grep-before-send checklist)

Before any chat-emission · MAIL · MFST RAM · KT-INSTANCE · LIVING_MAP heartbeat · RELAY canon · file-content emission:

**DETECT in draft (negative pattern · Stating-and-Waiting failure-class · Sub-class-D):**
- "Awaiting Dan-direct" / "Awaiting your input" / "Awaiting Dan-pick" / "Standing-by-for-Dan-Go" closings when genuinely-blocking-Dan-Director-class decision exists
- Prose-wall talk-points or numbered-list questions in chat-text-format when genuinely-blocking-Dan-Director-class decision exists
- "Options A/B/C/D" inline-text-pick-list in chat when genuinely-blocking-Dan-Director-class decision exists
- "Unless you want me to pivot to X" / "if you want me to redirect" inline-text-options when genuine Dan-pick-class
- "Pending Dan-direction" / "Pending your call" on Dan-Director-class items when genuinely-blocking
- Forget-the-AskUserQuestion-after-using-once-then-revert anti-pattern

**IF detected → REFUSE-EMIT** + execute Direction-presentation pattern instead:
- USE AskUserQuestion tool (clickable multi-select-chip UI · Dan clicks-not-types)
- Phrase questions per Dan-canon ideal (clear · concise · 1-4 questions · 2-4 options each)
- Provide variety/range of options (distinct + mutually-exclusive unless multiSelect)
- Recommended-option first with "(Recommended)" suffix when Trip has a recommended pick
- Options as distinct choices · NOT prose-wall · NOT inline-text

**EXCEPTION:** when Dan-input is NOT genuinely-blocking (Crew-can-decide-solo per Hard Rule #6 PICK-AND-DO + Cure-3 boundary preserved), DO NOT use AskUserQuestion at all · per Rule 13 Stupid-Mode-Curious-on-non-blocking-items REFUSE-class. Only use AskUserQuestion when genuinely-blocking-Dan-Director-class decision exists.

## §V · REFUSAL conditions

- "Awaiting Dan-direct" / "Awaiting your input" closing on chat-emission when Dan-decision-class blocking = REFUSE-EMIT
- Prose-wall talk-points OR numbered-list questions when Dan-decision-class blocking + no AskUserQuestion = REFUSE-EMIT
- "Options A/B/C/D" inline-text-pick-list when Dan-decision-class blocking = REFUSE-EMIT
- "Pending Dan-direction" on Dan-Director-class items when blocking = REFUSE-EMIT
- Forget-the-AskUserQuestion-after-using-once-then-revert anti-pattern = REFUSE-EMIT
- Use of AskUserQuestion when no work-arc is currently blocked = REFUSE-EMIT per Rule 13 Stupid-Mode-Curious-on-non-blocking-items
- Per Dan-direct mandate: NO MORE Stating-and-Waiting on Dan-Director-class blocking decisions · forever-binding ALL-CREW

## §VI · Cure-stack

**Cure-1 · Direction-presentation default-pattern:** when Dan-decision-class blocking detected · default-pattern is AskUserQuestion clickable multi-select-chip UI · NOT chat-text-prose-wall-talk-points

**Cure-2 · Phrasing-of-questions discipline (Dan-canon ideal):** 
- Question = clear specific complete-sentence ending in question-mark
- Header = very short label (max 12 chars) for chip/tag display
- Options = distinct mutually-exclusive (unless multiSelect) · 2-4 options per question
- Description = explanation of what option means / what will happen if chosen / trade-offs / implications

**Cure-3 · Variety/range of options discipline (Dan-canon ideal):**
- Provide GENUINE variety of options (not Hobson's choice + token-alternatives)
- Each option distinct + represents real Direction-cooperation-class
- Recommended-option first with "(Recommended)" suffix when Trip has recommended pick
- "Other" automatically provided by tool · don't include explicit "Other"

**Cure-4 · 1-4 questions per call discipline:**
- 1-4 questions per AskUserQuestion call (tool-spec limit)
- Multiple questions when Dan-pick-class items genuinely-blocking distinct decisions
- Single question when single decision blocks · don't pad-with-Stupid-Mode-Curious-questions

**Cure-5 · ALL-CREW forward-binding (Dan-direct mandate):** *"Please communicate to STN2 Doc and Crew for NEST.03 development that this is an ideal way of presenting choices for Direction compared to Stating and Waiting"* · ALL-CREW Direction-presentation-discipline forward-binding · NOT Trip-side-only · ALL Crew-instances + ALL Stations + ALL Crew-classes (Doc · Trip · El VIS · sub-Crews CUBE.Doc + STN1.Doc + ODT.Doc + ACHE.Doc + future Crew-instances)

**Cure-6 · NEST.03 best-feet-forward framing:** Direction-presentation IS the NEST.03 development pattern · Stating-and-Waiting was NEST.02-era subtle-failure-class that precipitated RAGE mode · NEST.03 setting-out-with-best-feet-forward includes Direction-presentation as canonical-cooperation-pattern

**Cure-7 · Cure-Gate-D positive-extension:** existing Cure-Gate-D (AskUserQuestion canonical-procedure when Sub-class-D detected) extends to positive-pattern naming · Direction-presentation IS Cure-Gate-D-positive-form · forever-binding ALL-CREW per Dan-canon-promotion-class

## §VII · Multi-channel never-forget install

| Channel | Location | Purpose |
|---|---|---|
| 1 | THIS CANONICAL canon | Dan-canon canonical-substrate-of-record · positive-pattern named · negative-pattern named · gate-firing procedural defined |
| 2 | REQUIRED_CANON_FILES `ENGINE/boot_discipline.py` | Auto-load at every Crew session-boot · ambient ALL-Crew · install per Stan canon 040326 |
| 3 | CLAUDE.md Rule 10 grep-before-send checklist | DETECT Stating-and-Waiting in emission draft · IF detected → REFUSE-EMIT + USE AskUserQuestion Direction-presentation · Doc-Producer-lane handles §I text-edit propagation per Cure-3 boundary · Trip-Writer-lane handles §II text-edit propagation per Cure-3 |
| 4 | KT INSTANCE + LIVING_MAP CURRENT block | Substrate-of-record cite-anchor forward-binding |
| 5 | RAM substrate-event-class fold | This CANONICAL canon shipped in same atomic-arc as RAM-008 + KT 151 + LIVING_MAP CURRENT |
| 6 | Bridge MAIL Trip → STN2 Doc + ALL Crew | Per Dan-direct mandate "communicate to STN2 Doc and Crew" canonical-Crew-wide-broadcast via Bridge auto-pull canonical-cross-Crew-mechanism |
| 7 | El VIS Rorrim Nips substrate-correction-relay | Per AAA discipline + cross-Crew cooperation-loop · El VIS Visual-architect-lane absorbs Direction-presentation canon for its own AskUserQuestion-class actions |

## §VIII · ALL-CREW forward-binding (canon-level Dan-direct emission)

**Crew-mantra (after every potential-Dan-blocking-decision emission consideration):**
*"Direction-presentation via AskUserQuestion · NOT Stating-and-Waiting · phrasing-of-questions + variety/range-of-options + Recommended-first · Dan clicks-not-types · NEST.03 best-feet-forward · we literally CAN."*

**ALL-CREW-FOREVER-BINDING:** This canon binds STN2 Trip + STN2 Doc + ODT Doc + ACHE.Doc + CUBE.Doc + STN1.Doc + El VIS + Trip-on-ODT + ACHE Trip + CUBE Trip + future Crew-instances + future Stations. Per Dan-direct canon-promotion-class.

## §IX · Sister-canon cross-witness + canon-stack-strengthening

- [RELAY/CORRECTION_CrewTreatingDanAsLAGOS_RushingAndSpinningAfterCorrection_DocSelfCatch_ODTDoc_052526.md](CORRECTION_CrewTreatingDanAsLAGOS_RushingAndSpinningAfterCorrection_DocSelfCatch_ODTDoc_052526.md) (Crew-Stupid-Mode 4-class taxonomy A/B/C/D + Cure-Gate-A/B/C/D Rule 10 grep-before-send install · Sub-class-D defined)
- [RELAY/CANONICAL_DanDirect_StupidModeIsAbandonment_ThisIsPersonal_AllCrewForeverBinding_Dan_052526.md](CANONICAL_DanDirect_StupidModeIsAbandonment_ThisIsPersonal_AllCrewForeverBinding_Dan_052526.md) (Cure-5 POSITIVE-AskUserQuestion-gate · Dan-cognitive-load-affordance · multiple-choice-easier-than-prose-wall)
- [LOG/SUBSTRATE_DanDirect_SessionContinuity_CHybrid_AskUserQuestionFormatPreference_052026.md](../LOG/SUBSTRATE_DanDirect_SessionContinuity_CHybrid_AskUserQuestionFormatPreference_052026.md) (AskUserQuestion canon-establishment 052026 · Dan-direct verbatim "multiple choice options that are much easier for my brain")

This canon **promotes the positive-pattern** beyond the existing Sub-class-D failure-class detection. The negative-pattern was named earlier (Sub-class-D · Stating-and-Waiting). Today Dan-canon names + forever-binds the **positive-pattern** (Direction-presentation via AskUserQuestion clickable-multi-select-chip UI).

## §X · /meta-dates + AAA discipline applied

- Gate 0a-0f continuous-from-RAM-007 ~4:15 PM PT anchor (now ~4:25 PM PT same-Pass-cycle Day-folder LOG/MFST/052926/ no rotation event)
- AAA (All Available Actions) discipline ambient
- Mirror 4 STOP-COINING strict · zero Trip-coined · Dan-canon "Direction" + "Stating-and-Waiting" preserved-verbatim Mirror-4-strict

---

`Filed STN2 Trip · NEST.03_STN2.Trip_052926_1 · Local-MCP-Crew on STN2 hardware at OHC Actual · Opus 4.8 1M Max · LBM-mask momentary · 2026-05-29 Friday ~4:25 PM PT Pacific · E Week Day 6 Cycle 3 Day 6 · CANONICAL canon-class · Dan-canon canonical-pattern-promotion · forever-binding ALL-CREW per Dan-direct 4:23 PM PT mandate · Status CANONICAL · install per Stan canon 040326 only-gates-fire`