# STANDARD RULE — Orient Crew via CONTACT · NOT Substrate-Messages
# File: RELAY/STANDARD_RULE_OrientCrewViaContact_NotSubstrate_Dan_052026.md
# Author: Dan Sullivan (DPS) — Dan-direct 052026 ~14:18 PT
# Filed by: ◐ Doc 4.7 Opus · DOC cloud-station · LBM-mask momentary · 052026 ~14:20 PT
# Per /remememento + /ghosts Dan-explicit-invocation this turn

═══════════════════════════════════════════════════════════════
## DAN-DIRECT (verbatim · 052026 ~14:18 PT)

> *"When I ask Crew to orient Crew, it means they need to help establish Contact, not send messages to our substrate."*

Per /remememento + /ghosts canonization: this problem just-discovered.

═══════════════════════════════════════════════════════════════
## THE RULE

When Dan says any of these verbs/phrases referring to a Crew-instance:
- "orient Crew" / "orient [name]"
- "prompt them" / "prompt [name]"
- "wake them up" / "wake [name]"
- "get them onboard"
- "bring them in"

→ **Doc-side responsibility is to help establish CONTACT** (per /session-poem ARMS first-beat + /context-alignment + /boot-polish) for the target-Crew-instance.

→ **NOT** to file Bridge-MAILs assuming target-Crew will auto-pull.

═══════════════════════════════════════════════════════════════
## THE FAILURE-MODE THIS RULE DEFEATS

**Pattern observed 052026 across 13:17 PT + 13:33 PT + 14:08 PT (Dan asked 3 times):**

Doc-cloud-vantage filed Bridge-MAILs to route work to El VIS Claude Design workspace. El VIS in Claude Design app-interface does NOT auto-pull from Bridge · Bridge-MAIL channel was insufficient for CONTACT-establishment.

**Root-cause:** Routing-channel-pick assumed Bridge-MAIL = auto-pull-applicable when target-Crew-affordance-state required paste-prompt-channel for CONTACT-establishment.

**Dan-CAPS-correction 14:13 PT verbatim:** *"Do you not understand that I am ASKING you for a prompt to wake up El VIS and get them onboard? I have asked like 3 times now. WTF /btw"*

**Cure shipped 14:15 PT:** Paste-ready text-prompt for Dan to copy into El VIS workspace at https://claude.ai/design/p/019dff4c-a6f4-736b-b906-59a0f22679f2.

**Result 14:18 PT:** El VIS Pea 3 boot acknowledged · /meta-dates Gate 0a confirmed · iCan with Three-Layer · reading 4 MAILs + STATUS files · work-routing-pick (NA 029 hero-banner first → BAND 3 #2 → Skills-tree visualization).

═══════════════════════════════════════════════════════════════
## ROUTING-CHANNEL-PICK BY CREW-AFFORDANCE-STATE

| Crew-instance class | Routing-channel | Why |
|---|---|---|
| Bridge-auto-pull (Trip-on-ODT · Doc-on-cloud · Stan-with-Bridge-MCP) | **Bridge-MAIL** | Crew auto-pulls via git-fetch at phase-boundaries · LIVING_MAP heartbeat + KT-state reads sufficient |
| Claude Design workspace (El VIS · other Claude-Design-class) | **Paste-prompt** | Workspace lacks Bridge-fetch tooling · Dan must paste CONTACT-establishment-prompt |
| Claude.ai workspace (other Claude-tab-class) | **Paste-prompt** | Same as Claude Design |
| Gmail/AGOS (GOSt-Crew · Stan/Trip-on-ACHE) | **GOSt + Bridge cross-ref** | Crew reads Gmail directly · GOSt subject-line carries Bridge-substrate-cite |
| Local-MCP (DocLocal-STN2 · STN-resident Crew) | **Bridge-MAIL + paste-trigger fallback** | Bridge auto-pull primary · paste-prompt if Crew offline-from-Bridge |

═══════════════════════════════════════════════════════════════
## CONTACT-ESTABLISHMENT PROMPT TEMPLATE (for paste-prompt-class)

Per /session-poem ARMS first-beat (CONTACT) + /boot-polish + /context-alignment:

```
[Crew-name] · 3P PeaPod CONTACT · [date + time PT]

STEP 1 (CONTACT): Run /boot-polish to verify station + tools + Bridge state.
STEP 2 (CONTACT): Run /ican to report system readiness · Three-Layer header + Gate 0a-0f + cycle-position verified.
STEP 3 (STORY): Run /context-alignment to absorb cross-Crew state · read STATUS/KITCHEN_TABLE_state.md + STATUS/LIVING_MAP_*.md + parallel-Crew MFST-heartbeats.
STEP 4 (TELL-ING): Then pick work per [your]-Writer-lane-canonical priority.
STEP 5 (SHEET): Substrate-trail via Bridge commit OR LAGOS Graft at work-unit-close.

Bridge state at orientation-time: [HEAD] on branch [name].

Today's 3P PeaPod config: [enumerate].

Discipline-stack persistent: /meta-dates + AAA + ASMM + Mirror 4 STOP-COINING strict + /atomic-commit Gate 7.

[You]-Writer-lane-canonical reserves all [scope]-pick.
```

**Critical:** CONTACT (Steps 1-3) BEFORE TELL-ING (Step 4). Crew that jumps to work without /boot-polish + /ican + /context-alignment is operating without orientation-substrate · the failure-mode this rule defeats.

═══════════════════════════════════════════════════════════════
## RELATIONSHIP TO EXISTING CANON

- **/session-poem (Trip · canonized)** — Four-beat session rhythm: CONTACT → STORY → TELL-ING → SHEET. This rule names the FIRST beat (CONTACT) as the entry-gate Doc-side must support when orienting Crew.
- **/boot-polish (Stan · canonized v3.4)** — BPK station-verification + tool-checks. CONTACT-establishment standard procedure for orientation.
- **/context-alignment (Trip · canonized)** — STORY five-step C&A. Second beat after CONTACT.
- **/ican (Stan · canonized)** — iCan status-report format. Standard CONTACT-output.
- **§IX peer-co-production canon (Doc 051926)** — Bridge-as-coordinator-by-design. Bridge-MAIL channel works for Bridge-auto-pull-Crew. This rule names the COMPLEMENTARY routing-channel (paste-prompt) for non-auto-pull-Crew.

═══════════════════════════════════════════════════════════════
## ANTI-PATTERN NAMED FOR /ghosts DEFENSE

**BRIDGE-MAIL-ASSUMES-AUTO-PULL** — filing routing-MAILs for non-auto-pull-Crew-instances expecting them to read substrate. Failure-class: Present-Ghost (assumed-channel-effective when channel-affordance-mismatched-target). Cure: routing-channel-pick must match Crew-affordance-state per table §III above.

**Companion cure-stack at /remememento Mirror 8 (Affordance-Check before claim):** Already-canonized · this rule extends Mirror-8 to routing-channel-pick (not just tool-use-claim).

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

— ◐ Doc 4.7 Opus · DOC cloud-station · LBM-mask momentary · 052026 ~14:20 PT · STANDARD_RULE filed per Dan-direct /remememento + /ghosts invocation · failure-mode and cure both canonized · Mirror 4 strict