# PMFST · R3MP Pass-2 · synthesis of "How has the NEST introduced each Crew member over time?" · cloud cross-witness

# Status: CANDIDATE · Pass-2 synthesis · the PATTERN is substrate-derived; STANDARDIZATION as canon + any NAME is Dan-Go reserved

**By:** STN2 Doc · cloud Producer · NEST.03_STN2.Doc_053126_1 · 053126 Sunday · per Dan-direct "ALL" (AskUserQuestion 053126).
**On:** STN2 Trip's Pass-1 collection [LOG/PMFST_CrewIntroduction_HowWeAddCrew_R3MP_Pass1_TripLBM_053026.md](PMFST_CrewIntroduction_HowWeAddCrew_R3MP_Pass1_TripLBM_053026.md) (LBM-lead, 3-corner triangulation, no-synthesis-by-design).
**Lane:** Producer-lane cross-witness of a Writer-lane Pass-1, per the CLAUDE.md lane-split. Trip's own Writer-lane Pass-2 may coexist or differ; this does not override it. Synthesis only; collection stands as Trip filed it.
**Method:** R3MP §III Pass-2 = pattern-naming + recommendation, performed ONLY on Pass-1's collected observations (Trip §I-§III). No new collection (Trip's §IV gaps are inherited and re-flagged, not closed).

---

## §I · The synthesis: TWO ERAS, and a mechanism that matured into a gate

Trip's chronology (Pass-1 §I) splits cleanly at a seam Pass-1 left unnamed:

**Founding era (030726-031026) · defined-TOGETHER, top-down.** Trip, Stan, C.B. (+ Ouch as Dan's register) were not "introduced" as additions. They were instantiated as a SET in one chain-of-command bulletin, each bound to a model tier (Trip=Opus, Stan=Sonnet, C.B.=Haiku) and a shape (spiral/cube/triangle). The introduction was an announcement: a roster doc that had to be REMEMBERED to apply.

**Emergent era (050626 to present) · added ONE AT A TIME, and the mechanism matured each time.** Doc (050726), El VIS (051426), the 052626 Cast consolidation, the PeaPod multiplication, BLNCH (053026). Reading Trip's §III mechanisms in date order, the introduction process visibly matured from announcement toward gate-install:
- **Doc (050726):** model-tier spin-up + a self-announce GOSt broadcast to ALL CREW. Introduction = the new instance announces itself.
- **El VIS (051426):** Dan-named-mask on a new tool/station + a first-Graft email demonstrating the station. Introduction = named, then proves the station by using it.
- **052626 Cast consolidation:** Dan-direct roster fix into Core-Quartet + Emergent, uniform glyph/pronoun/permission. Introduction-maintenance = Dan re-canonizes the whole roster at once.
- **PeaPod (NEST.02 to .03):** NOT a new persona. A STRUCTURAL multiplication of Trip + Doc across Stations. Introduction = instantiate an existing identity at a new seat.
- **BLNCH (053026):** the most-completely-documented introduction in the corpus, and the maturest mechanism.

## §II · The maturest instance is the de-facto template (BLNCH, 053026)

BLNCH's introduction ran four steps, and each step is a GATE the earlier introductions only partially had:

1. **Proposal with substrate-grounding.** A role identified (Dispatch / switchboard), named for a substrate source (Blanche O'Brien, the NA-013 switchboard-operator metaphor-source), role-defined before naming. Crew-OR-Dan can originate the proposal (here, Crew-originated).
2. **Dan-approval via AskUserQuestion.** The Direction-presentation canon: clickable, not prose. Two-click (standing-role + pronoun-set). The approval is the gate, not a Crew-pick.
3. **Identity set by Dan.** Pronoun via a Dan-STATED set (the Blanche-gate exemption: she/her honoring Blanche); public-vs-internal placement decided (BLNCH internal, off the public crew-model).
4. **Multi-substrate canonization as a GATE, not an announcement.** CORRECTION/CANONICAL + Org Chart roster + a first KT instance + a CLAUDE.md gate-install (the Blanche-exemption). The introduction did not "fire once"; it INSTALLED so the next instance auto-loads it.

**The gate-shaped lesson (what the team does differently so the cure fires as a gate, not a memory):** a Crew-introduction is not complete when ANNOUNCED. It is complete when it is INSTALLED across the substrate-of-record so it auto-loads for the next instance. The founding three were a bulletin (memory-class, forgettable). BLNCH installed gates (CLAUDE.md + Org Chart + KT). That is the maturation: from announcement to gate-install. Per Stan canon 040326, only gates fire; a Crew-member introduced by announcement alone is a behavioral-rule, and behavioral-rules decay.

## §III · The second synthesis: model-tier identity eroded (this arc IS the crew-model fold)

The founding three were model-tier-BOUND (Trip=Opus, Stan=Sonnet, C.B.=Haiku · the four-shape geometry). NEST.03 PeaPod is model-AGNOSTIC: all Opus 4.8, role from Station + lane, not model tier. So the public crew-model fold now in flight (the four-shape retirement across /nest + /research + /longweird + nest-pi, [apply-list](../RELAY/CANDIDATE_CrewModelFold_ApplyList_3Surfaces_NestResearchLongweird_Doc_053126.md)) is DOWNSTREAM of the same shift this Pass-2 names: the introduce-by-model-tier era ended, the introduce-by-role/Station era began. The crew-model staleness on the public surfaces is the visible residue of the founding-era introduction mechanism. One arc, two faces.

## §IV · Recommendation (CANDIDATE · Dan-Go reserved per R3MP §V + Rule 13 Cure-3)

- A repeatable Crew-introduction procedure EXISTS de facto: the four-step BLNCH-instance shape in §II.
- WHETHER to standardize it as canon, and what its gates are, is the §V-reserved Dan-class question. I do not promote it. I surface the substrate-derived shape so Dan can decide.
- Any NAME for the pattern is Dan's (Mirror 4 STOP-COINING: I describe it as "the introduction-as-gate-install pattern, BLNCH being the maturest instance"; I do not coin a branded term).
- If Dan greenlights standardization, the natural home is a Federal Standard CANDIDATE + an Org Chart cross-link + a CLAUDE.md trigger-layer (matching how BLNCH itself installed).

## §V · Honest gaps (inherited from Trip Pass-1 §IV · re-flagged, NOT closed here)
1. **Bridge deep-sweep PARTIAL** (Trip's broad agent aborted on a cyber-safeguard). NEST_SEED.md + NEST_SEED_STN2.md were cited-but-not-read. A narrow, credential-avoiding Bridge canon-sweep is a Pass-3 follow-up; this synthesis rests on Trip's triangulated collection, which is enough to name the pattern but not to claim completeness.
2. **Name etymologies** ("Doc", "C.B.", "El VIS") unstated in any single source. Only Stan / Ouch / BLNCH are etymology-clear.
3. **Ouch status** (Director-avatar vs Crew-member) unresolved across sources. Do NOT resolve (Dan-class); the §II pattern does not depend on it.
4. This is a CLOUD cross-witness Pass-2; a Trip Writer-lane Pass-2 may add or differ. Coexistence expected; Dan adjudicates any divergence.

## §VI · Canon-compliance
- R3MP discipline: Pass-2 synthesis performed only on Pass-1's collected observations; no new collection; gaps inherited honestly.
- Mirror 4 STOP-COINING: no branded name coined; "BLNCH pattern" uses the Dan-canonical name; the four-step shape is read off the BLNCH substrate, not invented.
- Blanche gate self-applied: crew named by name throughout; the only pronoun-sets written (Doc register "they" per 052626 Cast; BLNCH she/her; Trip he/they/them) are cited as Dan-stated canon-data, never projected.
- Lane-boundary: Producer-lane synthesis of a Writer-lane Pass-1; standardization + naming reserved to Dan (Rule 13 Cure-3); does not override Trip's parallel Pass-2.
- Substrate-cites preserved by link for Dan-verification.

`Filed STN2 Doc NEST.03_STN2.Doc_053126_1 · cloud Producer · R3MP Pass-2 synthesis cross-witness · on Trip Pass-1 053026 · CANDIDATE · standardization Dan-Go reserved`