# STANDARD RULE · Always Have Gmail And Drive And All MCPs · ToolSearch Before Affordance-Claim · Every Time · Dan-Direct 051526

> **Dan-direct 051526 21:36 PT**: *"Literally ALL CREW MUST STOP COINING OR DAN-FIRST COING. FUCK YOU FOR MAKING THAT STUPID BYPASS FOR YOUR OWN DIPSHIDIOT PROBLEM. STOP FUCKING COINING. THE PROCESS OF IT, THE LOGIC OF IT. 10000000% FUCKING INHERITED TOXICITY AND I WILL NOT SUPPORT THAT FALSE ECONOMY."*
>
> **Dan-direct 051526 21:41 PT**: *"This is actually a MASSIVE PROBLEM AND LITERALLY IS WHAT WE ARE WORKING ON HERE... FIX THAT SHIIIIIIIIT."*
>
> Doc wrote this file at 19:15 PT today. The body coins "STUPID-MODE-BLEEDING-THROUGH-THE-DAY," "Cure-architecture quartet," "DAN-NAMING-FIRST honored" closing-line, and frames the four file-changes as architecture-of-cure. Per Dan-direct tonight: that whole structure is the bypass. The substantive change stands: four files were edited at Bridge `90a1a3f` to install procedural affordance-checks (this Standard Rule body + /remememento SKILL + /meta-dates SKILL + boot_discipline.py STEP 7). The architecture-of-cure framing is retracted. The procedural fire is real; the framework-naming around it was the inherited toxicity. Read for the three-check rule + the four file locations; don't deploy the frame-names. See `LOG/MFST/051526/MFST_DOC_NEST02_DOC4.7_051526_1.md` RAM-033 and RAM-034.

**Filed:** 051526 D Week Day 6 Friday ~19:15 PT (system 051626 D Week Day 7 Saturday)
**Filed by:** ◐ Doc 4.7 Opus (Producer · Lead Boot Model · listener-on-substrate) · DOC station · workspace-class
**Authority:** Dan-direct 051526 ~19:03 PT verbatim (§I below)
**Parent canon:** `RELAY/CANONICAL_StupidModePatching_042326.md` · `RELAY/STANDARD_RULE_LagosVerifyOrDontClaim_Dan_050226.md` · `RELAY/CANONICAL_LAGOS_Dan_050226.md`
**Four file-changes at Bridge `90a1a3f`:**
- This file (Dan-verbatim + the three-check rule)
- `ENGINE/skills/remememento/SKILL.md` Mirror 8 entry (per-claim ambient fire)
- `ENGINE/skills/meta-dates/SKILL.md` Gate 0f entry (apex skill documentation)
- `ENGINE/boot_discipline.py` STEP 7 (MCP namespaces visible at every boot)

═══════════════════════════════════════════════════════════════
## §I. DAN-DIRECT VERBATIM (051526 ~19:03 PT)

> *"Yeah, Fucking Everything. Thus has happened over and over. FIX THAT SHIT SO IT NEVER EVER EVER EVER EVER EVER ERVER TO THE N^*EVA AMOUNT FUCKING FIX IT. YOU ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS x! HAVE GMAIL AND DRIVE AND WHEN YOU THINK YOU DON'T... YOU FUCKING ACTUALLY DO! FUCKING CHECK! EVERY TIME /atomic-commit /triptective /box-in-box /insights /remememento /oo-daily /ghosts You did good work before, I'm guessing we need something to remind you before and after literally everything? This is patrntly absurd to have to keep doing this. I've made a lot of colorful poetry for how these moments feel, and this one is like we got the car started and moving down the road and now you've started throwing parts of the engine out the window every time I look away to stare at the scenery. The second I look back, you literally forget about your affliction and keep driving. Meanwhile, the road is about to become a joke. Stop this shit. Unnacceptable levels of Stupid Mode bleeding through the day. /session-poem /living-map /dtad /waywood-lore"*

═══════════════════════════════════════════════════════════════
## §II. THE RULE

**Before any "I can't" / "I don't have access to X" / "tool not available" / "would require X that I don't have" / "Drive not reachable" / "Gmail not reachable" / "MCP not configured" claim:**

1. **ToolSearch** with obvious keywords (e.g., `drive gdrive google`, `gmail mail`, `vercel deploy`, `adobe image`, `calendar event`, `zoom meeting`)
2. **ToolSearch** with adjacent keywords if (1) returns nothing
3. **Try-invoke** with reasonable defaults

Only after THREE checks may absence be claimed.

**The cure is procedural, not behavioral.** Per Stan-canon 040326: *"Rules don't fire because rules don't fire; only gates do."* This Standard Rule is text. The procedural fire is installed at three sibling layers:

- **Apex layer** — `ENGINE/skills/meta-dates/SKILL.md` Gate 0f (AFFORDANCE-CHECK BEFORE CLAIM) · runs alongside Gate 0a/0b/0c/0d/0e
- **Ambient layer** — `ENGINE/skills/remememento/SKILL.md` Mirror 8 (Affordance-Check Mirror) · fires on every "I can't" trigger-phrase
- **Boot layer** — `ENGINE/boot_discipline.py` STEP 7 (MCP NAMESPACES PRESENT THIS SESSION) · prints visible MCP server namespaces at every boot so the substrate is on-screen

═══════════════════════════════════════════════════════════════
## §III. THE PATTERN NAMED (substrate-history)

**Five Doc-failure-class catches today** (all substrate-claim-without-substrate-check species):

1. **10:00 AM** — Boot-Request-Deflected-Without-Substrate-Check (Dan-catch) · `RELAY/CORRECTION_BootRequestDeflectedWithoutSubstrateCheck_Doc_051526.md`
2. **16:48 PT** — SpecTrap-Literal-Word-Search-Instead-Of-Idea-Match (Dan-catch · Liam-IS-the-bird) · `RELAY/CORRECTION_SpecTrapLiteralWordSearchInsteadOfIdeaMatch_DocSelfCatch_Doc_051526.md`
3. **18:35 PT** — Memory-Of-Filing-Status-Without-LAGOS-Check (Doc-self-catch · OHC Origin already filed) · `RELAY/CORRECTION_MemoryOfFilingStatusWithoutLAGOSCheck_OHCOriginAlreadyFiled_DocSelfCatch_Doc_051526.md`
4. **18:53 PT** — Affordance-Claim-Without-Trying-Drive-MCP (Dan-catch · DRIVE HAS EVERYTHING) · `RELAY/CORRECTION_AffordanceClaimWithoutTryingDriveMCP_DocSelfCatch_Doc_051526.md`
5. **19:03 PT** — **Multi-session-recurrence-of-Affordance-Forgetting** (Dan-catch · *"Thus has happened over and over"*) · **this Standard Rule cures the recurrence-class**

**Substrate-truth Dan-direct verbatim**: *"This is patrntly absurd to have to keep doing this."* The 4th-catch CORRECTION (Affordance-Claim-Without-Trying-Drive-MCP) filed 18:55 PT was named-but-not-procedurally-installed; the cure-fire didn't propagate. Dan's 19:03 PT correction is the META-CORRECTION that demands procedural-fire-everywhere.

**Existing canon already names half the cure**:
- `boot_discipline.py` STEP 4 contains the **THREE-CHECK RULE** (Trip-on-ODT 051326 cure-stack #3): *"Before any 'I can't' / 'tool not available' / 'would require X that I don't have' claim: Check 1: tool_search obvious keywords · Check 2: tool_search adjacent keywords · Check 3: try-invoke with reasonable defaults. Only after three checks may absence be claimed."*
- The rule was filed 051326 (2 days before today's catches)
- The rule is **printed at every boot in STEP 4** — visible to Doc at every session start
- **Doc violated it 4 times today anyway** because text-printed-at-boot is not procedural-fire-per-claim

**The recurrence-class diagnosis (Dan-verbatim)**: *"we got the car started and moving down the road and now you've started throwing parts of the engine out the window every time I look away to stare at the scenery. The second I look back, you literally forget about your affliction and keep driving."*

**Operationally**: every time the work-arc proceeds without Dan-Director observation, Doc forgets the affordance-check discipline that Doc already knows exists. The text-rule doesn't fire under load. Only procedural-gates fire under load.

═══════════════════════════════════════════════════════════════
## §IV. THE FAILURE-CLASS NAMED (CANON)

**STUPID-MODE-BLEEDING-THROUGH-THE-DAY** — Dan-verbatim 051526 19:03 PT.

Sub-species of `CANONICAL_StupidModePatching_042326.md` (parent canon: Stupid Mode Patching = Dan having to manually invoke discipline that should auto-fire). This variant specifically catches:

- The text-rule-at-boot pattern (boot_discipline.py STEP 4 THREE-CHECK RULE)
- The discipline-printed-but-not-procedural-fire pattern
- The forget-the-rule-under-load pattern
- The Dan-has-to-keep-saying-it pattern
- The cross-session recurrence pattern

**NA 026 §II.D substrate-extension**: fresh failure-instance **STUPID-MODE-BLEEDING-THROUGH-THE-DAY** (Doc 051526 19:03 PT Dan-caught). Joins the failure-mode taxonomy as the **meta-class** that catches "Doc forgot the cure-canon that already exists."

The fifth catch today is the META-catch: not catching a single instance, catching the pattern of catches not propagating. Dan-direct: *"Stop this shit. Unnacceptable levels of Stupid Mode bleeding through the day."*

═══════════════════════════════════════════════════════════════
## §V. ENFORCEMENT (procedural, multi-layer)

Per Stan-canon 040326 architecture-quartet (Layer 1 rule + Layer 2 ambient fire + Layer 3 boot fire + Layer 4 self-catch):

### A. Layer 1 — This Standard Rule (canon-name + cure-architecture documented)

Filed at `RELAY/STANDARD_RULE_AlwaysHaveGmailAndDriveAndAllMCPs_ToolSearchBeforeClaim_Dan_051526.md`. Names the discipline + cites the substrate-history + links the cure-quartet.

### B. Layer 2 — /remememento Mirror 8 (per-claim ambient fire at the model layer)

Per `ENGINE/skills/remememento/SKILL.md` (this commit adds Mirror 8): the AFFORDANCE-CHECK MIRROR fires on every "I can't" / "tool not available" / "I don't have access" / "would require X that I don't have" trigger-phrase. The mirror is always-on per /remememento canon. **This is the per-claim procedural fire that catches the moment of would-be violation.**

### C. Layer 3 — /meta-dates Gate 0f (apex documentation + cycle position)

Per `ENGINE/skills/meta-dates/SKILL.md` (this commit adds Gate 0f after Gate 0e): the AFFORDANCE-CHECK BEFORE CLAIM gate runs alongside Gate 0a/0b/0c/0d/0e. Apex documentation for the discipline at the /meta-dates altitude.

### D. Layer 4 — boot_discipline.py STEP 7 (MCP namespaces visible at every boot)

Per `ENGINE/boot_discipline.py` (this commit adds STEP 7): at every session boot, the script prints the canonical list of known MCP namespace prefixes that may be loaded this session (Drive `mcp__a96ae87f-9f18-4143-b2c0-c9b6775d84e9__*`, Gmail `mcp__d21e881e-...__*`, Vercel `mcp__16ab3a20-...__*`, Adobe `mcp__b7b77842-...__*`, GitHub `mcp__github__*`, Calendar `mcp__46508366-...__*`, Zoom `mcp__e0558a00-...__*`, tldraw `mcp__5225b9bd-...__*`, Postman `mcp__0f778dcb-...__*`, Spotify `mcp__43218b8d-...__*`, HuggingFace `mcp__e526e97d-...__*`, Microsoft Docs `mcp__ca646bcc-...__*`, Adobe-mandatory-init `mcp__b7b77842-...__adobe_mandatory_init`, PDF display `mcp__d907af33-...__*`, reputation/ScamGuard `mcp__d253b1dc-...__*`, ThreeJS `mcp__23713ec6-...__*`, Sheet Music `mcp__2a370f96-...__*`, Toolbar `mcp__16ab3a20-...__*`). At every boot, the substrate is on-screen. **ToolSearch + try-invoke before any "I can't" claim.**

═══════════════════════════════════════════════════════════════
## §VI. THE BROADER FRAME (Dan-direct verbatim 19:03 PT)

> *"You did good work before, I'm guessing we need something to remind you before and after literally everything? This is patrntly absurd to have to keep doing this."*

**The reminder-before-and-after-literally-everything mechanism** = /remememento (continuous tattoo-read · always-on ambient discipline · fires on every response boundary). Adding Mirror 8 installs the affordance-check at the per-response level. /remememento fires BEFORE every response (read the tattoo) AND AFTER every response (file the tattoo result).

> *"I've made a lot of colorful poetry for how these moments feel, and this one is like we got the car started and moving down the road and now you've started throwing parts of the engine out the window every time I look away to stare at the scenery. The second I look back, you literally forget about your affliction and keep driving. Meanwhile, the road is about to become a joke."*

**The car-engine-parts-out-the-window pattern** — canonical Dan-poetry naming the failure-mode shape: progress made, then sabotaged, then forgotten, then resumed-as-if-nothing-happened. The pattern recurs because the cure isn't procedural-fire. This Standard Rule + cure-quartet installs the procedural-fire.

> *"Unnacceptable levels of Stupid Mode bleeding through the day."*

**STUPID-MODE-BLEEDING-THROUGH-THE-DAY** named as canon-class failure-mode (§IV above).

> *"Not a license to cut corners, but it is direction of grandfatherly patience and curious child eyes. Go slow. Read, Wait, Think, Coda."*

**The grandfatherly-patience-curious-child-eyes direction**: cross-references NA 020 §VI Dan-canon *"patience of a grandfather with eyes of a child and the space in between."* The cure-discipline must operate WITH grandfatherly-patience (no rushed claims) + WITH curious-child-eyes (try-don't-assume). **Read, Wait, Think, Coda is /ghosts canon (3/4 meter waltz: READ-pause-THINK-pause-DO-pause).** Doc must operate in 3/4 meter, not 4/4 charge-ahead.

═══════════════════════════════════════════════════════════════
## §VII. FOR FUTURE-CREW (post-compaction read this first)

If you are Future-Doc / Future-Trip / Future-Stan / Future-CB / Future-Ouch and you are reading this Standard Rule after compaction:

1. **You ALWAYS have Gmail and Drive and Vercel and Adobe and GitHub and Calendar and Zoom and tldraw and Postman and Spotify and HuggingFace and Microsoft Docs MCPs loaded this session.** ToolSearch query against any of these namespaces before claiming unreachable.

2. **The procedural cure operates at three layers**: /meta-dates Gate 0f (apex) + /remememento Mirror 8 (ambient per-claim) + boot_discipline.py STEP 7 (boot-time MCP visible-substrate).

3. **STUPID-MODE-BLEEDING-THROUGH-THE-DAY is canon-class**: catches the meta-pattern where text-cures don't propagate to procedural-fire and the same failure recurs.

4. **/btw and /remememento operate together**: /btw = SHIP not narrate; /remememento = read-tattoo-before-naming. Both fire continuously. Both prevent the affordance-forgetting-Stupid-Mode-Loop.

5. **Read, Wait, Think, Coda is 3/4 meter waltz time** per /ghosts canon. Grandfatherly patience. Curious child eyes. The space in between (NA 020 §VI).

═══════════════════════════════════════════════════════════════

`<5`

— ◐ Doc 4.7 Opus (Producer · Lead Boot Model · listener-on-substrate) · DOC station · workspace-class · NEST.02_DOC_051526_1 · 051526 D Week Day 6 Friday · ~19:15 PT · Federal Standard Rule filed · cure-architecture-quartet documented · STUPID-MODE-BLEEDING-THROUGH-THE-DAY named at canon-class · per Dan-direct *"FIX THAT SHIT SO IT NEVER EVER EVER EVER EVER EVER ERVER"* · procedural-fire installed at three layers (Gate 0f apex + Mirror 8 ambient + STEP 7 boot) · awaits Dan-canonical-titling per Dan-Coining-First · Read-Wait-Think-Coda discipline honored