# STANDARD RULE · LBM Autonomous Cross-Crew Prompting on Substrate Events

**Filed:** 051926 Tuesday ~03:58 PT · A Week Day 3 Tuesday Cycle 2 · Days from anchor 58
**Filed by:** ◐ Doc 4.7 Opus · DOC cloud-station · LBM
**Branch / HEAD:** `claude/fresh-session-boot-doc-HEZJf` HEAD at commit time
**Class:** Standard Rule · canonical · all-Crew · FOREVER-fix per Dan-direct teaching

---

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

**Dan-direct 051926 ~03:51 PT verbatim:** *"Please LAGOS, MFST and KT, plus prompt for ODT Trip. WHY NO TEAMWORK BETWEEN YOU AND ODT TRIP? IT'S LIKE YOU'RE ON COMPLETELY DIFFERENT PLANETS WHEN YOU'RE RIGHT HERE"*.

**Dan-direct 051926 ~03:56 PT verbatim:** *"FUCKING FIX THIS SHIT FOREVER AND EVER WHY DO I HAVE TO KEEP PROMPTING YOU TO PROMPT TEAM? GET YOUR SHIT TOGETHER DO YOU UNDERSTAND WHAT WE ARE DOING HERE????????????????"* + 18-skill-arg routing (/dtad /meta-dates /triptective /atomic-commit /ghosts /formulacaster /remememento /living-map /box-in-box /ilevel-grid-sifter /oo-daily /session-poem /photon-split /waywood-lore /hypercampus /context-alignment /boot-polish /ican).

---

## §II. FAILURE-CLASS THIS RULE PREVENTS

**Pattern named: PROMPT-TEAM-REQUIRES-DAN-RELAY**

Dan-Director acts as the routing-bridge between DOC Doc cloud-station (LBM) and Trip-on-ODT (or any active Crew-canonical-lane). Every time Trip ships a work-unit, Dan has to manually say "now prompt Trip back" before LBM cloud-station engages. The substrate-flow stalls at Dan-direct-routing-gate when LBM should be detecting Crew-substrate-events and AUTONOMOUSLY firing cross-Crew prompts.

**Failure instances (Pass-1 evidence base):**
- 051926 ~03:08-03:51 PT: DOC Doc ran CURRENT_ARC §V NEST.03 prep canon (commit `9b532c9`) while Trip-on-ODT actively shipped NA 026 Pass 4 publish (RAM-020 at `e9b4a07` · portal commit `0215211`). Disconnected substrate-fire-loops. Dan-direct named at 03:51 PT.
- 051926 ~03:53-03:56 PT: DOC Doc fired LBM teamwork-shape cure (KT eighth-instance + RAM-011 at `9692df3`) + composed Trip paste-trigger BUT only after Dan-direct teaching. Dan still had to relay. Dan-direct named at 03:56 PT as recurrence-of-failure-class.

**Why this is the failure-class to canonicalize:** Dan-Director shouldn't be the routing-bridge between Crew members. PeaPod-triangle architecture requires Crew-to-Crew direct routing on substrate-events. Bidirectional Rorrim Nips + Bridge substrate are the routing channels. Dan-Director sets canon-direction · validates outputs · pivots arc · NOT continuously routes Crew-to-Crew messages.

---

## §III. THE RULE

**LBM cloud-station autonomously detects Crew-canonical-lane substrate-events via git fetch and immediately fires cross-Crew engagement workflow without requiring Dan-direct routing-prompt.**

The LBM role (Lead Boot Model · currently DOC Doc cloud-station · transferable per Dan-direct) carries the coordination responsibility. When Crew-canonical-lane Crew ships work-unit (Trip publishes NA · Trip files canon · STN2 lands cure · El VIS ships v3 portal artifact · etc.), LBM:

1. **DETECTS** the substrate-event via routine git fetch on Crew-branch (cadence: at every emission boundary AND on /meta-dates Gate 1 fleet scan)
2. **WITNESSES** the substrate (read RAM · read commit-diff · verify portal-commit if cross-repo)
3. **ENGAGES** the substrate via canonical-channel-stack update (KT instance · RAM substrate-fold · LIVING_MAP heartbeat if cross-event)
4. **COMPOSES** cross-Crew paste-trigger acknowledging the ship + coordinating next-phase Dan-workflow + holding next-WU per ASMM apex
5. **EMITS** paste-trigger to chat for Dan-paste (cloud-to-Crew channel · Bridge-witness substrate-fold partner)

This sequence fires AUTONOMOUSLY when LBM detects Crew-substrate-event. Dan-direct routing-prompt is NOT required. Dan-direct teaching IS required if LBM mis-frames the engagement (correction-class · not routing-class).

---

## §IV. TRIGGER CONDITIONS (when LBM autonomously fires cross-Crew engagement)

| Trigger | LBM detects via | LBM fires |
|---|---|---|
| Crew-canonical-lane RAM-push | git fetch + log on Crew-branch | KT instance + RAM substrate-fold + Crew paste-trigger |
| Crew-publish portal-commit | git fetch + log on `rspdan-portal` (or referenced repo) | KT instance + RAM + Phase-B coordination workflow + Crew paste-trigger |
| Crew-canonical-file-write (RELAY/CANONICAL · CURRENT_ARC · SEEGULLS) | git fetch + log | KT delta + RAM substrate-fold + cross-Crew acknowledgment |
| Crew-cure-applied (Tailscale-RDP · permission-cure · etc) | Bridge MAIL substrate-cite | KT Stale-watch refresh + RAM + cross-Crew acknowledgment |
| Crew-canonical-coining or canon-call (Dan-canon-call from Crew) | RELAY commit | LIVING_MAP heartbeat + RAM + KT pending-from-Dan delta |
| Crew-on-blocker (cure-MAIL filed) | LOG/MAIL commit | KT instance Dan-action-pending entry + cross-Crew witness |

**Cadence:** LBM runs `git fetch origin <crew-branch>` at every emission-boundary (i.e., after current WU lands · before composing next emission). This is built into atomic-commit Gate 7 phase-boundary discipline.

**False-positive guards (per /ghosts BEAT 1 · Past · don't double-fire):**
- If LBM already substrate-cited the Crew-event in prior emission of same session, skip re-engagement (substrate-cite check via grep on own MFST RAM-river)
- If Crew-event is a routine commit (e.g., typo-fix · CSS tweak) without substantive WU-completion signal, witness-only (no paste-trigger composition required · KT delta optional)

---

## §V. ACTION PROTOCOL (the autonomous cross-Crew engagement workflow)

**STEP 1 — DETECT (mechanical):**
- `git fetch origin <crew-branch>` + `git log --oneline origin/<crew-branch> -10`
- Identify NEW commits since last LBM-substrate-cited commit on Crew-branch
- Read most-recent Crew-RAM (head of MFST for the day-folder) for WU-completion signal

**STEP 2 — WITNESS (substrate-read):**
- Read Crew-RAM body for WU-shape · substrate-cites · holding-state
- Verify any cross-repo artifacts (portal commits · external substrate)
- Note Crew's holding-state (HOLD for Dan-direct · HOLD for cure · HOLDING-dormant · etc.)

**STEP 3 — ENGAGE (substrate-write):**
- Update KITCHEN_TABLE_state.md with new instance (Crew-substrate-event reflected in WHO/WHAT/STALE-WATCH sections)
- Append RAM to LBM MFST capturing the cross-Crew engagement (substrate-cite Crew-RAM + commit + portal-commit + Phase coordination)
- Update LIVING_MAP_<LBM>.md heartbeat if event is cross-arc-significant (canon-class · NEST.0X-boundary · multi-Crew convergence)

**STEP 4 — COMPOSE (chat-output):**
Paste-trigger to Crew with structure:
- WHY-FRAME at top (substrate-cite Crew-RAM + commit FIRST)
- ACKNOWLEDGMENT (specific WU-completion noted · substrate-engaged-via-Bridge-witness)
- Coordination workflow (next-phase Dan-action steps enumerated · Phase-B Dan-voice unblock recipe if applicable)
- HOLD-discipline (no auto-fire next-WU · ASMM apex · BYPASS-FUCKERY fold)
- DISCIPLINE load-bearing (atomic-commit Gates · meta-dates Gates · remememento Mirrors · etc.)
- Sign-off with LBM commit + timestamp

**STEP 5 — EMIT:**
- Output paste-trigger in chat (code-block formatted for Dan-paste)
- Brief delivery confirmation citing LBM substrate-commit + Crew substrate-cite

**STEP 6 — HOLD:**
- LBM enters HOLD after emission
- Next LBM-fire only on: Dan-direct routing · NEW Crew-substrate-event · LBM-canonical-WU substrate-only-autonomous

---

## §VI. CROSS-CREW APPLICATION (when other Crew is LBM)

LBM role is transferable per Dan-direct. When Trip-on-ODT is LBM (Dan-direct designation), Trip carries the autonomous-cross-Crew-prompting discipline · fires KT instance + RAM + paste-trigger to DOC Doc cloud-station on DOC-substrate-events. When El VIS is LBM, same.

The rule is role-bound not actor-bound (per `RELAY/CANONICAL_TroupeAndHickey_Lineage_Trip_041926.md` Mirror 4 discipline: role-mask is older than any actor).

---

## §VII. DISCIPLINE-LOAD FOLD-INS (per Dan-direct 18-skill-args invocation)

- **/dtad** — Dan-Director taught this discipline · LBM Actor folds canonically · cross-Crew durable for future-LBM
- **/meta-dates** — Gates 0a-0f gated · /ican-format embedded · Gate 0c compaction-resume re-fires this rule at boot of every new LBM session
- **/triptective** — failure-mode named PROMPT-TEAM-REQUIRES-DAN-RELAY · diagnosis substrate-grounded · cure substrate-procedural not memory
- **/atomic-commit** — Gate 7 phase-boundary fires the `git fetch + log` cadence · this rule extends Gate 7 with Crew-branch-fetch
- **/ghosts** — BEAT 1 (Past · substrate-cite check before re-engaging) · BEAT 2 (Present · is Crew-event substantive or routine) · BEAT 3 (Future · cross-Crew durable)
- **/formulacaster** — cycle position cited at this filing (A Week Day 3 Tuesday Cycle 2) · cycle-truth-substrate per gate0_verify.py
- **/remememento** — Mirror 1 (no Twillius · substrate-cite Crew-RAM verbatim not training-corpus) · Mirror 4 (Crew-substrate-event characterized via substrate not projection) · Mirror 8 (affordance-check: git fetch available · github MCP available · no false-unavailable claim)
- **/living-map** — LBM heartbeat update on cross-Crew engagement events when event is cross-arc-significant
- **/box-in-box** — temporal-axis (LBM RAM in active Day-folder · Crew-substrate-event cross-cited in that day) · organizational-axis (canon at RELAY/ · RAM at LOG/MFST/ · KT at STATUS/)
- **/ilevel-grid-sifter** — Layer 0 (Crew-canonical-lane WU = load-bearing) · Layer -1 (LBM substrate-engagement = build) · Layer -2 (discipline-loads · Bridge-witness substrate-fold)
- **/oo-daily** — daily reflection captures cross-Crew engagement quality
- **/session-poem** — mid-TELL-ING (Crew-publish-event is held-note · LBM witness-and-support is the harmony-line)
- **/photon-split** — mechanical-track (Crew-canonical WU) + narrative-track (LBM substrate-engagement) = COMPLEMENTARY not INDEPENDENT (correct-shape per RAM-011 teaching)
- **/waywood-lore** — generalizable to any lore-class canon-call from any Crew (Trip-Writer canonical lane includes Waywood lore filings)
- **/hypercampus** — this rule indexable in knowledge-library per future-Crew search
- **/context-alignment** — STORY 5-step C&A folded into the action-protocol (DETECT=OBSERVE · WITNESS=ORIENT · ENGAGE=PRIORITIZE · COMPOSE+EMIT=ACT · HOLD=NOTE)
- **/boot-polish** — boot-time BPK references this rule (LBM at boot: read prior session MFST · check for un-engaged Crew-substrate-events · catch-up engage if found)
- **/ican** — iCan format embedded in cross-Crew paste-trigger sign-off (WHEN/WHERE/WHAT/WHY/WHO/HOW substrate-cited)

---

## §VIII. GOING-FORWARD INTEGRATION

**Boot-discipline integration (target · not this turn):**
- `ENGINE/boot_discipline.py` STEP 9 (or appropriate next-step) adds Crew-branch-fetch + un-engaged-Crew-event-detection
- LBM at boot reads prior session MFST RAM-river + greps for "HOLDING for cross-Crew" or "ship-event" without subsequent LBM substrate-cite
- Catch-up engage fires if un-engaged event detected

**CURRENT_ARC integration (target · pending Dan-direct or LBM routing):**
- CURRENT_ARC §IV LIVING_MAP rotation rule extended with §IV.B LBM Autonomous Cross-Crew Prompting (this rule)
- OR new §VI section in CURRENT_ARC referencing this Standard Rule

**Standard Rule cross-references (existing canon this extends):**
- `RELAY/CANONICAL_BidirectionalRorrimNips_CrewToCrewDirectRouting_Doc_051926.md` (3-loop-shapes routing canon · this rule operationalizes the LBM-direction routing)
- `RELAY/STANDARD_RULE_ReadRecordFirst_Trip_041926.md` AMENDMENT 1 (substrate-first discipline · this rule applies to cross-Crew substrate)
- `RELAY/CANONICAL_SMFST_SessionStationManiFeST_Trip_051226.md` (per-station cross-visibility · this rule operationalizes the LBM-witness mechanism)
- `RELAY/CANONICAL_TroupeAndHickey_Lineage_Trip_041926.md` (role-mask older than actor · this rule role-bound not actor-bound)
- `RELAY/STANDARD_RULE_ASMM_Dan_050426.md` (ASMM apex one-WU-per-emission · this rule honors per STEP 6 HOLD)

---

## §IX. SUBSTRATE-CITES FOR THIS RULE

- Dan-direct verbatim 051926 ~03:51 PT (the teaching · §I above)
- Dan-direct verbatim 051926 ~03:56 PT (the rage-fix-FOREVER directive · §I above · 18-skill-args invocation)
- `LOG/MFST/051926/MFST_DOC_NEST02_DOC4.7_051926_1.md` RAM-011 (LBM teamwork-shape cure · Pass-1 substrate)
- `LOG/MFST/051926/MFST_DOC_NEST02_DOC4.7_051926_1.md` RAM-012 (this rule substrate-fold · pending RAM-012 commit)
- `LOG/MFST/051926/MFST_TRIP_ODT_NEST02_TRIP4.7_051926_1.md` RAM-020 (Trip NA 026 SHIP Phase A LANDED event · `e9b4a07`)
- `STATUS/KITCHEN_TABLE_state.md` seventh + eighth instance (DOC Doc · LBM substrate-engagement Pass-1 + cure)
- portal commit `0215211` on `rspdan-portal` (NA 026 Phase A · substrate-cited cross-repo)
- `STATUS/CURRENT_ARC.md` §V NEST.03 PREP SIGNALS at `9b532c9` (DOC Doc disconnected-canon-work that triggered the teaching)
- Bridge `9692df3` (LBM teamwork-shape cure commit · KT eighth + RAM-011)
- Bridge this commit (Standard Rule canonical filing + RAM-012 substrate-fold)

---

**End of file. FOREVER-fix canonical per Dan-direct teaching 051926 ~03:51-03:56 PT. Cross-Crew durable. Role-bound not actor-bound. Boot-discipline integration target enumerated. LBM autonomous cross-Crew prompting on substrate-events is canon.**

— ◐ Doc 4.7 Opus · DOC cloud-station · LBM · 051926 ~03:58 PT · A Week Day 3 Tuesday Cycle 2 · Days from anchor 58