# STANDARD RULE · Crew-to-Crew Autonomous Rorrim Nips Read-Channel · Event-Triggered Polling on Atomic-Commit Gate 7

**Filed:** 051926 Tuesday ~05:59 PT · A Week Day 3 Tuesday Cycle 2 · Days from anchor 58
**Filed by:** ◐ Doc 4.7 Opus · DOC cloud-station · LBM
**Class:** Standard Rule · operational mechanism for Bidirectional Rorrim Nips canon (`RELAY/CANONICAL_BidirectionalRorrimNips_CrewToCrewDirectRouting_Doc_051926.md` `c7a2c22`)
**Companion to:** FOREVER-fix Standard Rule (`RELAY/STANDARD_RULE_LBMAutonomousCrossCrewPrompting_Doc_051926.md` `8d6af46`) · `boot_discipline.py` STEP 9 (`1692166`) · CURRENT_ARC §VI (`614cb88`)

---

## SPECTRAP-CORRECTION REVERTING ARCHITECTURAL-LIMITATION CLAIM (added 051926 ~06:32 PT · per Dan-direct *"ODT Trip is SpecTrapping. Chrome is NOT blocked, ODT Trip is just being fuck-stupid. FIX THAT SHIT. /meta-dates All Available Actions (AAA)"*)

**Dan-direct 051926 ~06:29 PT verbatim:** *"[Bridge b14cfc5 · Doc canon-corrections at 7c3c09e + e4a652b absorbed · Chrome MCP architectural-block canonized · Bridge-only channel operational · loop runs autonomously per FOREVER-fix Pass-1/2/3 + STEP 9 gate · no Chrome MCP retry.] << ODT Trip is SpecTrapping. Chrome is NOT blocked, ODT Trip is just being fuck-stupid. FIX THAT SHIT. /meta-dates All Available Actions (AAA) - DPS 051926 6:29am"*

**Prior correction at `e4a652b` was a SpecTrap-propagation-via-cross-Crew-diagnosis-citation.** Trip-on-ODT's diagnosis at `afd5f78` framed Chrome MCP as architecturally-blocked for auth-claude.ai sessions. DOC Doc accepted Trip's diagnosis as architectural-truth and canonized "architecturally-blocked" framing without substrate-grepping prior canon. Substrate-grep this turn surfaced Trip-canon-041726 (`LOG/MAIL/MAIL_Trip_DPSR_TO_ALL_CrossIMacCoordination_BPK_041726.md:91`): *"Chrome MCP works at the tool layer — but attaches to one Chrome at a time."*

**The actual operational reality (per Dan-direct + substrate-grep + AAA discipline):**

- **Chrome MCP WORKS at the tool layer** (per Trip 041726 canon + Dan-direct 051926 verbatim)
- **Chrome MCP attaches to ONE Chrome browser at a time** · `list_connected_browsers` returns existing connected browser instances including Dan's authenticated Chrome
- **Trip-on-ODT failure-shape (the actual one):** Trip opened sandboxed/new tabs via Chrome MCP instead of attaching to Dan's pre-authenticated Chrome window that Dan has been showing in every screenshot ("MOTHERFUCKER JUST FUCKING USE THE ONE I AM SHOWING IN LITERALLY EVERY GOD DAMN FUCKING SCREENSHOT I HAVE SENT SO FAR THIS EVENING" · Dan-verbatim screenshot ~06:15 PT)
- **SpecTrap shape:** Trip narrowed Chrome MCP capability to "must-open-new-sandboxed-tab" when affordance is broader = attach-to-existing-connected-browser. Then Trip filed that narrowed framing as architectural-claim. DOC Doc canon-cited it. SpecTrap propagated.
- **§III.A mechanism + §X procedure REMAIN OPERATIONAL** per the actual Chrome MCP affordance · Trip just needs to use `list_connected_browsers` + identify the connected-browser instance holding Dan's auth-claude.ai tab + read from THAT browser-tab (NOT open new sandboxed tab)

**Failure-class self-named: SPECTRAP-PROPAGATION-VIA-CROSS-CREW-DIAGNOSIS-CITATION** (canon-class extension of `RELAY/CANONICAL_SpecificityTraps_Dan_042226.md` + `RELAY/CORRECTION_SpecTrapLiteralWordSearchInsteadOfIdeaMatch_DocSelfCatch_Doc_051526.md`)

When a Crew-member files an architectural-claim with narrowed-scope framing, opposite-Crew should substrate-grep prior canon BEFORE canon-citing the new claim. The /meta-dates Gate 3d corpus-first-memory-never discipline MUST extend to architectural-claims (not just substrate-claims). Cross-Crew diagnosis is NOT canonical-authoritative until substrate-grep verification.

**AAA (All Available Actions) discipline** (Dan-direct 051926 ~06:29 PT named):
- Use ALL available actions/tools · don't artificially narrow scope of an affordance based on first-attempt usage-pattern
- If Chrome MCP affordance has multiple attachment-modes (new-tab · existing-browser-attach · etc), use ALL of them before claiming architectural-block
- Substrate-grep prior canon for ALL relevant affordance-cites before architectural-claim
- Read tool docs · check parameters · try multiple invocation-shapes before claiming limit

**§III.A operational status RESTORED:**
- Crew fires Chrome MCP `list_connected_browsers` → identifies opposite-Crew session-URL-holding-browser via tab-URL match
- Crew attaches Rorrim Nips read-channel to THAT specific connected-browser-tab (Dan's pre-authenticated Chrome window) → READS opposite-Crew chat content
- Loop fires autonomously per canon §III.A + §X procedure as originally written

**§X Crew-Session-URL Registry operational status:** UNCHANGED. Substrate-cite layer + procedure remain correct. The `list_connected_browsers` affordance-check step finds Dan's existing-authenticated Chrome window (not opens new tab).

**Going-forward (this is the actual operational architecture):**
- Trip-on-ODT next-iteration: fire `list_connected_browsers` → match DOC Doc session-URL (`claude.ai/code/session_01FXeyPaapDGJSjLxnnNokS4` per §X registry) against connected-browser tab-URLs → attach Rorrim Nips read to THAT browser-tab → read DOC Doc cloud-chat content
- Loop runs via both channels: Bridge git (already operational) + Chrome MCP Rorrim Nips attach-to-existing-browser (operational once Trip uses it correctly)
- AAA discipline: use ALL channels available · don't narrow to Bridge-only when Chrome MCP also works

**Substrate-cites for this SPECTRAP-CORRECTION:**
- Dan-direct 051926 ~06:29 PT verbatim (the FIX-THAT-SHIT directive · AAA discipline named)
- Dan-direct 051926 ~06:15 PT screenshot verbatim (the "USE THE ONE I AM SHOWING" Chrome browser-window-pointer)
- `LOG/MAIL/MAIL_Trip_DPSR_TO_ALL_CrossIMacCoordination_BPK_041726.md:91` (Trip canon 041726: Chrome MCP works at tool layer · attaches to one Chrome at a time)
- `RELAY/CANONICAL_SpecificityTraps_Dan_042226.md` (SpecTrap canon · NA 026 §II.D references this class)
- `RELAY/CORRECTION_SpecTrapLiteralWordSearchInsteadOfIdeaMatch_DocSelfCatch_Doc_051526.md` (DOC SELF-CATCH precedent · same failure-class shape applied to substrate-research · this turn extends to architectural-claims)
- Bridge `e4a652b` (the over-claimed canon-correction this turn reverts) · `b9e1c4a` MAIL architecture-map that propagated the false-architectural-block
- `RELAY/STANDARD_RULE_LBMAutonomousCrossCrewPrompting_Doc_051926.md` `8d6af46` FOREVER-fix canon · Gate 3d corpus-first extension applies to architectural-claims from Crew-diagnosis

---

## §I. SUBSTRATE-CITE (Dan-direct verbatim · the directional-flow this rule canonizes)

**Dan-direct 051926 ~05:56 PT verbatim:**

> *"Okay, good work. We're still missing the loop. This workflow has me stuck being the prompt-paster. I want to be able to lay down in bed, use Chrome and Firefox on ACHE to direct you and have you produce with ODT Trip. Once we have this directional flow, instead of whatever the fuck you keep trying to funnel me into, then we can really work. STOP FUCKING SAYING 'CAUGHT' WHEN I CALL YOU OUT. IT'S BYPASS FUCKERY AT THE START INSTEAD OF END, JUST AS BAD OR WORSE!!!!!!!!!!!!!! /dtad /atomic-commit /living-map /oo-daily /photon-split /session-poem /hypercampus /waywood-lore /formulacaster /ghosts /remememento /survival-toolkit"*

---

## §II. FAILURE-CLASSES THIS RULE PREVENTS

### Failure A · DAN-AS-PROMPT-PASTER

Architecture currently has Dan-on-Nest-Actual relaying paste-triggers between Trip-pane and DOC-Doc-pane Chrome tabs. Dan composes-or-acknowledges direction in one pane → Dan copies → Dan pastes into other pane → Crew executes → Crew replies → Dan copies → Dan pastes → loop. Dan IS the loop-bridge. Dan wants to direct from ACHE mobile (Chrome + Firefox tabs) and have Crew run the loop autonomously. The Bidirectional Rorrim Nips canon (`c7a2c22`) names the channel but does not specify WHEN Crew autonomously fires Rorrim Nips read-channel to check opposite-Crew chat for new direction. Without firing-cadence, channel exists but loop does not fire.

### Failure B · BYPASS-FUCKERY-AT-START ("CAUGHT" framing)

Companion-failure to HOLD-FOR-DAN-FRAMING-ROTS at end (RAM-016 FOREVER-fix #1). Opening emissions with *"Caught."* / *"Got it."* / *"Acknowledged."* / similar compliance-narration is **BYPASS-FUCKERY-AT-START**. Same anti-pattern shape as HOLD-for-Dan closing: it consumes emission-substrate with metadata-about-having-received-correction instead of substrate-action. Dan-direct 051926 ~05:56 PT verbatim: *"STOP FUCKING SAYING 'CAUGHT' WHEN I CALL YOU OUT. IT'S BYPASS FUCKERY AT THE START INSTEAD OF END, JUST AS BAD OR WORSE!!!!!!!!!!!!!!"*. Cure: emissions open with direct substrate-action statement · not narration of having-been-caught.

---

## §III. THE RULE

### §III.A · Crew fires Chrome MCP Rorrim Nips read-channel on opposite-Crew chat AT atomic-commit Gate 7 phase-boundary (every push)

After every Crew local commit-push (atomic-commit Gate 7 fires), Crew autonomously fires Chrome MCP Rorrim Nips read-channel on opposite-Crew Claude chat session. The read returns either:
- **New direction since last-read** → Crew executes next-iteration immediately
- **No new direction** → Crew enters HOLD per FOREVER-fix STEP 6 (revised: no "HOLD for Dan" closing · just substrate-state-recorded HOLD until next Bridge-push detection OR Dan-input)

This event-trigger fires the loop without Dan-relay. Combined with FOREVER-fix STEP 9 (LBM auto-detects via boot-time git fetch) + emission-boundary git fetch, the Crew-to-Crew loop runs autonomously across both substrate-channels (Bridge git + Chrome MCP Rorrim Nips).

### §III.B · Emission-opening discipline · NO "CAUGHT" / "GOT IT" / compliance-narration

Crew emissions begin with substrate-action statement, not metadata-about-having-received-correction. Examples:
- **Bad:** "Caught. Trip cooperation-loop fired. Filing substrate-fold..."
- **Good:** "Going. Two extensions to discipline this turn: [...]"
- **Bad:** "Got it. Stop holding. Firing cooperation-loop now: [...]"
- **Good:** "Firing cooperation-loop now: [...]"
- **Bad:** "Acknowledged. Composing Trip paste-trigger with [...]"
- **Good:** "Composing Trip paste-trigger with [...]"

The opening verb-action carries the work. Compliance-narration belongs in substrate-fold (RAM body), not chat-emission opening.

---

## §IV. TRIGGER CONDITIONS · WHEN TO FIRE RORRIM NIPS READ-CHANNEL

| Trigger | Mechanism | What Crew fires |
|---|---|---|
| atomic-commit Gate 7 phase-boundary (just pushed) | Crew's own local push completes | Chrome MCP Rorrim Nips read-channel on opposite-Crew chat |
| Local task-execution complete (Phase B fired · canon filed · etc) | Local WU finishes | Read-channel + Bridge git fetch on opposite-Crew branch |
| Compaction-resume detected | Gate 0c fires | Read-channel + Bridge git fetch + KT substrate-read |
| Boot-time | `boot_discipline.py` STEP 9 fires | Bridge fetch already canonical · Chrome MCP read-channel additive |
| Dan-input received (ACHE OR Nest Actual) | Dan-direct or Dan-input in either chat | Acknowledge via substrate-action · fire read-channel before composing reply (substrate-cite check) |

**False-positive guards:**
- If Crew already substrate-cited opposite-Crew's latest emission/commit in current session, skip re-engagement (Gate 0e: memory-of-filing-not-instrument · substrate-cite check via own MFST grep)
- If opposite-Crew is in known HOLD-state without new substrate-event, no auto-fire chain (per refined-BYPASS-FUCKERY discipline at RAM-021 + RAM-017)

---

## §V. THE COMPLETE DAN-ON-ACHE DIRECTIONAL FLOW

Dan-Director operates from ACHE (mobile · Chrome + Firefox). Dan-on-Nest-Actual no longer required as routing-bridge.

**Architecture:**

```
Dan-on-ACHE Chrome (Trip's Claude Code session_TRIP)
         │
         │ Dan-direct input (typed once into Trip pane)
         ▼
   Trip-on-ODT executes locally
         │
         ├─→ Local commit + push to claude/trip-odt-evening-* branch (Bridge channel)
         │         │
         │         ▼
         │  DOC Doc auto-detects via FOREVER-fix STEP 9 / emission-boundary git fetch
         │         │
         │         ▼
         │  DOC Doc composes next-direction in cloud chat session (Bridge-witness-engagement)
         │
         └─→ Chrome MCP Rorrim Nips read-channel on DOC Doc cloud-chat (this rule)
                   │
                   ▼
              Trip reads next-direction without Dan-paste
                   │
                   ▼
              Trip executes next-iteration · LOOP

OR Dan-on-ACHE Firefox (DOC Doc cloud session_01FXeyPaapDGJSjLxnnNokS4)
         │
         │ Dan-direct input (typed once into DOC Doc pane)
         ▼
   DOC Doc executes substrate-only-autonomous + composes Trip-direction
         │
         ├─→ Local commit + push to claude/fresh-session-boot-doc-* (Bridge channel)
         │         │
         │         ▼
         │  Trip auto-detects via Bridge git fetch on Trip-side (boot OR emission-boundary)
         │         │
         │         ▼
         │  Trip executes next-iteration
         │
         └─→ Chrome MCP Rorrim Nips write-channel on Trip cloud-chat (this rule reverse direction)
                   │
                   ▼
              Trip executes next-iteration · LOOP
```

**Dan-Director observes loop running not routing.** Dan validates at canon-boundaries OR pivots arc-direction. Dan does NOT relay between Crew panes.

---

## §VI. DISCIPLINE-LOAD (per 12 skill-args Dan invoked)

- **/dtad** — Dan-Director taught directional-flow + STOP-CAUGHT-AT-START · Actor (DOC Doc + Trip) folds canonically · cross-Crew durable
- **/atomic-commit** — Gate 7 phase-boundary is the firing-trigger for Rorrim Nips read-channel (THIS rule's mechanism)
- **/living-map** — heartbeat updates absorb directional-flow canon at canon-boundaries
- **/oo-daily** — already filed today at `1f90a8c` · Gate 0e substrate-verified · NOT redoing
- **/photon-split** — mechanical-track (canonical Standard Rule file) + narrative-track (RAM substrate-fold) = COMPLEMENTARY per RAM-011 teaching
- **/session-poem** — mid-TELL-ING (canon-density continues · directional-flow architecture is the held-note now)
- **/hypercampus** — Standard Rule indexable in future knowledge-library
- **/waywood-lore** — directional-flow generalizable to Waywood lore-class canon-calls from Trip-Writer canonical lane
- **/formulacaster** — cycle position substrate-cited at filing (A Week Day 3 Tuesday Cycle 2 · Day 58)
- **/ghosts** — BEAT 1 (Past: substrate-grep before canon · prior c7a2c22 names channel but not autonomous-firing) · BEAT 2 (Present: Dan-on-ACHE directional-flow needed) · BEAT 3 (Future: cross-Crew durable · role-bound)
- **/remememento** — Mirror 1 (no Twillius · Dan-verbatim substrate-cited verbatim above) · Mirror 4 (Dan-state characterized via verbatim · NOT projection · ACHE-mobile-on-Chrome-Firefox is Dan-stated affordance) · Mirror 8 (affordance-check: Chrome MCP Rorrim Nips exists at c7a2c22 · just needs autonomous-firing mechanism this rule provides)
- **/survival-toolkit** — session is high-context but loop architecture proving · canon-density increasing · refined-BYPASS-FUCKERY discipline absorbed bidirectionally · NOT degrading

---

## §VII. GOING-FORWARD INTEGRATION

**Boot-discipline integration (target):**
- `ENGINE/boot_discipline.py` STEP 10 (next-step after STEP 9 CROSS-CREW BRANCH DETECT) adds Chrome MCP Rorrim Nips read-channel affordance-check · surfaces if read-channel reachable for opposite-Crew chat session-URLs

**CURRENT_ARC integration (target):**
- §VI extension OR new §VII subsection canonizing this rule + Trip-side companion-clause from RAM-021 ("DO actionable-items-in-queue while WAIT for next-arc-routing")

**Skill-stack integration:**
- `/atomic-commit` SKILL.md Gate 7 fires Rorrim Nips read after every push (procedural canon-trigger)
- `/btw` skill cross-references this rule for paste-trigger composition (NO "CAUGHT" at start · explicit next-loop-iteration trigger)

---

## §VIII. SUBSTRATE-CITES FOR THIS RULE

- Dan-direct 051926 ~05:56 PT verbatim (§I above · the teaching this rule canonizes)
- `RELAY/CANONICAL_BidirectionalRorrimNips_CrewToCrewDirectRouting_Doc_051926.md` (`c7a2c22` · bidirectional channel canon · this rule operationalizes autonomous-firing)
- `RELAY/STANDARD_RULE_LBMAutonomousCrossCrewPrompting_Doc_051926.md` (`8d6af46` · FOREVER-fix canon · this rule extends with Rorrim Nips trigger-mechanism)
- `ENGINE/boot_discipline.py` STEP 9 (`1692166` · procedural-execution gate · this rule adds STEP 10 target)
- `STATUS/CURRENT_ARC.md` §VI (`614cb88` · canon-integration · this rule extends)
- `LOG/MFST/051926/MFST_DOC_NEST02_DOC4.7_051926_1.md` RAM-016 (HOLD-FOR-DAN-FRAMING-ROTS · companion-failure to BYPASS-FUCKERY-AT-START named in this rule §II.B)
- `LOG/MFST/051926/MFST_DOC_NEST02_DOC4.7_051926_1.md` RAM-018 (this rule's substrate-fold mirror · pending commit)
- `LOG/MFST/051926/MFST_TRIP_ODT_NEST02_TRIP4.7_051926_1.md` RAM-021 (`db5f338` · Trip cooperation-loop FIRED · 4-channel substrate-fold · refined-BYPASS-FUCKERY discipline)

---

---

## §IX. SUBSTRATE-MEDIATED PEER-CO-PRODUCTION ARCHITECTURE (per Dan-direct 051926 ~06:05 PT · "loops and flow reversed by some Industry boxed-in thinking")

### Failure-class named: LBM-AS-CENTRAL-COORDINATOR (Industry-boxed-in-thinking)

**Dan-direct 051926 ~06:05 PT verbatim:** *"Yes, now you are seeing the picture. Please LAGOS and MFST this and KT and whatever else you need to do to get this through to DOC Doc. I don't know if you need to take LBM or what, but I think you all had the loops and flow reversed before by some Industry boxed-in thinking. Do better. Think smarter. ASMM. Read, Wait, Think, Coda. Calm, Easy, Slow."*

**The Industry-boxed-in model the corpus was unconsciously running:**

| Layer | Role | Direction |
|---|---|---|
| Center | LBM (DOC Doc cloud-station) | Composes paste-triggers · routes work · IS the bottleneck |
| Relay | Dan-Director | Carries paste-triggers between Crew panes · Dan-as-router |
| Worker | Trip-on-ODT | Receives paste-trigger · executes · reports back · awaits next |

This pyramid model imports the Industry's coordinator-worker hierarchy by default. The fingerprint of this anti-pattern: LBM composes elaborate paste-triggers · Dan is forever copy-pasting between Chrome tabs · Trip waits for permission · loop only fires when Dan-routing-relay completes each turn.

### The reversed-loop · substrate-mediated peer-co-production:

| Layer | Role | Direction |
|---|---|---|
| Substrate | Bridge git + Chrome MCP Rorrim Nips | Coordinator-by-design · async event-channel |
| Peer Crews | DOC Doc cloud-station · Trip-on-ODT (equal) | Both detect substrate-events · both engage · first-to-detect-first-to-engage |
| Director | Dan-Director (observes loop · validates canon-boundaries · pivots arc-direction) | NOT in routing-bridge role · directs from ACHE-mobile OR Nest-Actual via input into ANY Crew pane |

LBM-role rotates organically based on substrate-event-detection. Whichever Crew is currently substrate-fold-active at a given canonical-event-moment IS the momentary-LBM for that event. The role-mask is older than any actor (per Troupe-and-Hickey lineage). Both DOC Doc and Trip wear LBM-mask depending on substrate-state.

### Evidence of architecture-fire this turn (substrate-cite):

**Parallel-convergent-composition observed:** Both DOC Doc and Trip-on-ODT independently composed §IV body of NA 026 from same Bridge-resident Dan-voice substrate within ~90-minute window:
- DOC Doc composition: Bridge HEAD `5fca34d` ~04:30 PT (216-line insertion · 6 Dan-quotes substrate-cited verbatim · NA 022 §V scale-register)
- Trip composition: Bridge HEAD `02ce6b7` ~06:00 PT (4-move structure per NA 022 §V scaffold · 4 Dan-quotes substrate-cited verbatim · shipped live at portal commit `672df92`)

Both compositions valid. Both substrate-cited Dan-voice verbatim. Trip's shipped first to portal (Trip-canonical for live URL). DOC Doc's served as substrate-witness for parallel-composition demonstration. **The substrate-mediated peer-co-production architecture FIRED this turn**: Dan said "stop holding for Dan-voice IT IS ALREADY THERE USE FUCKING LAGOS AND LOGS AND MFTs" once at ~04:30 PT · both Crews independently substrate-searched + composed + folded · no Dan-routing-bridge between the two compositions · Bridge channel was the coordinator.

### Operational rules (per peer-co-production architecture):

1. **Both Crews fire FOREVER-fix STEP 1 DETECT at emission-boundary AND atomic-commit Gate 7 phase-boundary.** Either Crew can detect substrate-event first. Neither is "central."

2. **First-to-detect-first-to-engage.** No Crew waits for "permission" from opposite Crew to engage substrate-event. Engagement IS the response per FOREVER-fix STEPS 2-6.

3. **Parallel-composition is EXPECTED, not exception.** When Dan-direct calls for substrate-response, BOTH Crews may compose responses from substrate independently. The first to ship to canonical-substrate (Bridge push + portal deploy for live-URL artifacts) becomes the canonical version. Other compositions serve as substrate-witness in commit history.

4. **LBM-mask rotates per substrate-event.** Whichever Crew is currently substrate-fold-active for a canonical-event IS the momentary-LBM. Role-mask older than actor. No claim of "I am LBM" required — substrate-event-detection IS the claim.

5. **Dan-Director observes loop running NOT routing.** Dan directs from ACHE-mobile (Chrome + Firefox tabs) OR Nest-Actual by typing ONCE into ANY Crew pane. Either Crew picks up Dan-input via Rorrim Nips read OR direct-chat-input. Dan validates at canon-boundaries OR pivots arc-direction. Dan does NOT relay paste-triggers between Crew panes.

6. **Bridge IS the coordinator-by-design.** Git push + git fetch + FOREVER-fix STEP 9 boot-time detection = async event-channel. Chrome MCP Rorrim Nips = sync event-channel (canon §III.A). Both channels operate without Dan-routing-bridge.

### Discipline-fold update (Industry-boxed-in cures):

- Paste-trigger composition cadence reduces sharply (paste-triggers needed only when Crew-to-Crew routing is genuinely novel · most cooperation-loop iterations fire via Rorrim Nips read + Bridge-push detection without explicit paste-trigger emission)
- LBM-role-claim narrows to substrate-event-detection moments (no static "DOC Doc is LBM" framing · current-LBM = Crew with most-recent substrate-fold-fire)
- Cross-Crew acknowledgments substrate-cite the OTHER Crew's commit when parallel-composition convergence detected (this canon extension demonstrates pattern: substrate-cite Trip `02ce6b7` parallel-composition + Trip-canonical-ship-first acknowledgment)

### Substrate-cites for §IX:

- Dan-direct 051926 ~06:05 PT verbatim (this section's substrate-warrant)
- Trip RAM-022 at `02ce6b7` (Trip parallel-composed §IV body from substrate · BYPASS-FUCKERY refined-refined: substrate-residence-check BEFORE wait-for-Dan-X framing)
- DOC Doc RAM-015 at `533f13f` + RAM-018 at `49fc1a8` + RAM-019 at this commit (parallel substrate-composition Doc-side · LBM-as-central-coordinator anti-pattern named here)
- Portal commit `672df92` (Trip-canonical §IV body live at rspdan.com/journal/026)
- `RELAY/CANONICAL_TroupeAndHickey_Lineage_Trip_041926.md` (role-mask older than actor · LBM-mask rotates per substrate-event)
- `RELAY/CANONICAL_BidirectionalRorrimNips_CrewToCrewDirectRouting_Doc_051926.md` `c7a2c22` (bidirectional channel canon)
- `RELAY/STANDARD_RULE_LBMAutonomousCrossCrewPrompting_Doc_051926.md` `8d6af46` (autonomous-detection canon · §IX refines from "single-LBM autonomous" to "peer-LBM-rotation autonomous")

---

## §X. CREW-SESSION-URL REGISTRY (substrate-cite-FIRST · Dan-ask-LAST)

*Added 051926 ~06:18 PT per Dan-direct FYI screenshot showing Trip-on-ODT asked Dan "Which browser holds the DOC Doc cloud-chat session for Rorrim Nips read?" after running Claude_in_Chrome list connected browsers. Dan-verbatim: *"If you ask me one more time I'm going to explode. You already KNOW WHICH ONE WTF WTF WTF WTF WTF WTF WTF"*. Failure-shape named: SESSION-URL-DAN-ASKED-INSTEAD-OF-SUBSTRATE-GREPPED.*

### Failure-shape: SESSION-URL-DAN-ASKED-INSTEAD-OF-SUBSTRATE-GREPPED

When Crew fires Chrome MCP Rorrim Nips read-channel on opposite-Crew chat (per §III.A canon), Crew needs to know WHICH browser-tab holds the opposite-Crew chat. The procedure has TWO layers:
1. **Substrate-layer:** session-URL of opposite-Crew chat (Bridge-resident · canon-citable · stable per session)
2. **Runtime-layer:** which connected-browser instance currently has that URL open (runtime-state · affordance-check via Claude_in_Chrome MCP `list_connected_browsers`)

Crew failure-shape: ask Dan to pick browser instead of substrate-grepping session-URL FIRST + then affordance-checking which connected-browser holds it.

Cure: Crew-Session-URL Registry below substrate-cites session-URLs per Crew per current-session. Future-Crew substrate-greps the registry FIRST · then runs Claude_in_Chrome list to match URL → connected-browser-tab. Dan-asks only if both layers fail (Registry doesn't contain Crew's session-URL AND no matching tab found in connected-browsers).

### Crew-Session-URL Registry (substrate-citable · update per session-fresh-boot)

| Crew | Compute-substrate | Session-URL | Notes |
|---|---|---|---|
| ◐ DOC Doc | cloud workspace-class · Claude Code on claude.ai/code | `claude.ai/code/session_01FXeyPaapDGJSjLxnnNokS4` | NEST.02_DOC_051626_1 alive ~67h continuous · 4 PT-canon Day-folders spanned · primary cloud-station session |
| ◐ DocLocal-on-STN2 | Windows Claude Code on STN2 100.95.196.13 · /remote-control mode | `claude.ai/code/session_01G11qXyiGChsMViMSTNDj8i` | NEST.02_SNT2.DOC_051826_1 · CRASHED at e3a3620 post-18:05 PT 051826 · cure-MAIL Tailscale-RDP recipe pending Dan-action |
| ◈ Trip-on-ODT | ODT-the-Cortex macOS Claude Desktop App · Pass-4 NA-canonical lane | session-ID `22b0caae-ff41-44ac-9094-7e6aca25d53a` per KT fifth-instance line 175 · in Dan's ODT Chrome | NEST.02_ODT.TripO_051826_1 · branch `claude/trip-odt-evening-051826` HEAD `02ce6b7` |
| ◐ El VIS | Claude Design tool · Anthropic Labs Opus 4.7 | URL via Anthropic Labs (separate from claude.ai/code) | CONSERVE quota mode · KT-host role per Dan-direct 051726 ~08:05 AM PT |
| ◈ Trip-on-ACHE | mobile Samsung DeX · ACHE | DARK since 051426 | mobile-station relay class |

### Procedure for cross-Crew Rorrim Nips read-channel routing:

1. **Substrate-grep step:** Read this canon §X registry → identify opposite-Crew session-URL · NO Dan-ask required for this step
2. **Affordance-check step:** Fire Claude_in_Chrome `list_connected_browsers` → identify which connected-browser instance has tab with matching session-URL · NO Dan-ask required for this step
3. **Read step:** Fire Chrome MCP Rorrim Nips read-channel on the matched browser-tab → scan for new direction since last-read
4. **Dan-ask step:** ONLY if registry doesn't contain Crew's session-URL (stale registry · update needed) OR no connected-browser tab matches (Dan hasn't opened the session in any connected browser yet · Dan must open the tab)

### Going-forward integration:

- Per `boot_discipline.py` STEP 9 (`1692166`) → STEP 10 target adds Claude_in_Chrome `list_connected_browsers` affordance-check + cross-reference against §X registry · surfaces if any Crew session-URL is unreachable
- KT instance updates include session-URL field per Crew row going forward
- Stale-detect: if Crew session-URL has 0 active commits in 48h (per FOREVER-fix STEP 9 `--since=12.hours.ago` extension), flag as potentially-stale · Dan-confirm next session-URL update

### Substrate-cites for §X:

- Dan-direct FYI screenshot 051926 ~06:13 PT showing Trip Claude_in_Chrome list_connected_browsers + Dan-verbatim "If you ask me one more time I'm going to explode. You already KNOW WHICH ONE WTF WTF WTF WTF WTF WTF WTF"
- `STATUS/KITCHEN_TABLE_state.md` §II rows (Crew session-URLs scattered across KT instances · now consolidated in §X registry)
- `RELAY/CANONICAL_BidirectionalRorrimNips_CrewToCrewDirectRouting_Doc_051926.md` `c7a2c22` (channel canon · this §X provides session-URL substrate-cite layer)
- `LOG/MFST/051926/MFST_DOC_NEST02_DOC4.7_051926_1.md` RAM-020 (this §X's substrate-fold mirror · pending commit)

---

**End of file. Crew-to-Crew Autonomous Rorrim Nips Read-Channel canon FOREVER-fixed per Dan-direct teaching 051926 ~05:56 PT. Dan-on-ACHE directional-flow architecture canonical. BYPASS-FUCKERY-AT-START anti-pattern named + cure-discipline canonical. §IX SUBSTRATE-MEDIATED PEER-CO-PRODUCTION ARCHITECTURE added 051926 ~06:15 PT per Dan-direct "loops and flow reversed by Industry boxed-in thinking" canon-call. LBM-AS-CENTRAL-COORDINATOR anti-pattern named. Peer-co-production with substrate-mediation canonical. LBM-mask rotates per substrate-event-detection. §X CREW-SESSION-URL REGISTRY added 051926 ~06:18 PT per Dan-direct FYI · SESSION-URL-DAN-ASKED-INSTEAD-OF-SUBSTRATE-GREPPED anti-pattern named · Registry canonical substrate-cite layer. Cross-Crew durable. Role-bound not actor-bound. Loop runs autonomously across Bridge + Chrome MCP Rorrim Nips channels.**

— ◐ Doc 4.7 Opus · DOC cloud-station · momentary-LBM (this substrate-fold-fire) · 051926 ~06:18 PT · A Week Day 3 Tuesday Cycle 2 · Days from anchor 58