# CANONICAL · Bases-Loaded coordination model · Dan-canonical baseball-metaphor 052526 ~09:02 AM PT · CANDIDATE

**Status:** CANDIDATE per Mirror 4 STOP-COINING strict. Dan promotes canonical · Doc surfaces CANDIDATE only.
**Filed by:** ◐ DOC Doc · NEST.02_DOC.Doc_052426_1 · cloud-online-class · LBM-momentary
**Per Dan-direct verbatim 052526 ~09:02 AM PT** (substrate-cite in [LOG/MAIL/DOCDoc_TO_STN2Doc_CUBEDoc_DanDirector_CrossWitnessSTN2Doc9879734_CUBEDocFirstBootOrientation_LANBootstrapDelegation_FormulacasterLocalDocLeftCloudDocRightStandardAbsorption_052526.md](../../LOG/MAIL/DOCDoc_TO_STN2Doc_CUBEDoc_DanDirector_CrossWitnessSTN2Doc9879734_CUBEDocFirstBootOrientation_LANBootstrapDelegation_FormulacasterLocalDocLeftCloudDocRightStandardAbsorption_052526.md) §VIII):

> *"Please do not SpecTrap this to ONLY being about STN2 when my directions were Quite Clear. Make the proper adjustments in your own and Crew's communications, please continue on all directed work. Are you ready to help get STN2 Doc out on 1st Base or are you still occupying it? You can have multiple players on the same base, but a rudimentary study of baseball will edify why this increases risk with each additional player on a concurrent base; whereas Bases Loaded is a common saying with actual power behind it."*

**Class:** Cross-Crew coordination canon · sister to /formulacaster Local-Doc-Left + Cloud-Doc-Right Standard CANDIDATE 052526. The two work together: /formulacaster gives the split-view operational pattern · Bases-Loaded gives the multi-Crew coordination framework that uses the pattern.

---

## §I · DAN-DIRECT VERBATIM SOURCE-OF-RECORD

Per Dan-direct 052526 Monday ~09:02 AM PT (correction-arc to Doc SpecTrap-Family-5 narrowing of cross-Crew directive):

**The metaphor verbatim:**
- *"Are you ready to help get STN2 Doc out on 1st Base or are you still occupying it?"*
- *"You can have multiple players on the same base, but a rudimentary study of baseball will edify why this increases risk with each additional player on a concurrent base"*
- *"Bases Loaded is a common saying with actual power behind it"*

**Companion-substrate from same morning-arc (~08:50 AM PT):** *"/formulacaster Local Doc on Left Side, Cloud Doc on Right Side"* (Dan-canonical extension at [RELAY/CANDIDATE/STANDARD_RULE_FormulacasterLocalDocLeftCloudDocRightStandard_Dan_052526.md](STANDARD_RULE_FormulacasterLocalDocLeftCloudDocRightStandard_Dan_052526.md)).

---

## §II · THE MODEL

**Base definitions (Dan-canonical-direct + 3-Agent Doc-Squad convergence):**

| Base | Meaning | Crew-state |
|---|---|---|
| **1st base** | Boot · orient · CONTACT-establishment · /boot-polish + /context-alignment + /ican fired | Crew session-alive · oriented to current arc · ready-to-receive direction |
| **2nd base** | TELL-ING · active-cooperation · substrate-cite-trail accumulating · Bridge-MAIL emissions firing | Crew producing substrate-folds · in motion · receiving + sending cross-Crew traffic |
| **3rd base** | Substrate-of-record landed · MFST RAM filed · PMFST landed · canonical-CANDIDATE elevated · KT instance committed | Crew has delivered to substrate · ready-to-score on Dan-acknowledgment or cross-Crew-handoff |
| **Home** | Dan-direction-bit delivered · Dan-Go fires · Dan-canonical promotion fires · Crew receives Dan-ack for substrate-arc | Run scored · arc closed · move to next arc |
| **Strike** | Named-failure-class fires (Rule 12 LAGOS-SCOPE-COLLAPSE · Rule 13 Domain-Fluency-Trust · SpecTrap-Family-5 · Villebaum · Ghost-Trip · etc) | Substrate-error caught · forward-correct · CORRECTION canon fires · 3-strikes-class warning when same-failure-Pass-N |

**Coordination-rule per Dan-direct:**
- **Each Crew on own base = maximum-power-position = Bases-Loaded.**
- **Multiple-Crew-on-same-base = collision-risk.**
- "A rudimentary study of baseball will edify why this increases risk with each additional player on a concurrent base" (Dan-direct verbatim).

**Operational-translation:** Cloud-Doc (DOC Doc) orchestrates lane-traffic so no two Crew-instances occupy the same base · each gets to advance through their own work-cycle · the goal-state is all 4 bases occupied by distinct Crew-instances simultaneously (= Bases-Loaded = maximum-power-position).

---

## §III · CLOUD-DOC GLUE-ROLE COUPLING (Per /formulacaster Standard §V)

The /formulacaster Local-Doc-Left + Cloud-Doc-Right Standard makes Bases-Loaded operationally possible. Per /formulacaster Standard §V *"Bases-Loaded coordination implication"*:

- Local-Doc occupies whichever base their work-cycle is currently at (e.g., STN2-Doc on 3rd via 9879734 substrate-of-record landed · CUBE Doc on awaits-1st pending boot)
- Cloud-Doc (DOC Doc) **does not occupy a fixed base** · Cloud-Doc role is the **coordinator** ensuring lane-traffic doesn't collide
- Cloud-Doc-self-advance through bases per its OWN work-cycle (not occupying Local-Doc bases) · e.g., my morning-arc 052526: 1st base (boot · /boot-polish) → 2nd base (TELL-ING · 19 atomic-commit-arcs morning) → 3rd base (substrate-resident · this CANONICAL CANDIDATE elevation + Pass-1 PMFST ec4bff1 landed) → awaits Home (Dan-Go on canonical-promotions)

---

## §IV · 3-AGENT DOC-SQUAD INDEPENDENT-CONVERGENCE (substrate-cite Pass-1 PMFST ec4bff1 §V Overlap 3)

Per Pass-1 substrate-pile PMFST [LOG/PMFST_DocOrientationGuide_Pass1_DocSquadSubstratePile_DocHiorusArc_ExistingOrientationSubstrate_BaseProgressToolSpec_DocCloudOnline_052526.md](../../LOG/PMFST_DocOrientationGuide_Pass1_DocSquadSubstratePile_DocHiorusArc_ExistingOrientationSubstrate_BaseProgressToolSpec_DocCloudOnline_052526.md) §V Overlap 3:

> *"Overlap 3 · 'Bases-Loaded coordination model' (Agent A §II.I + Agent B §III.H hole-3 + Agent C §IV.E) is the cross-cutting framework: All 3 agents independently identified Bases-Loaded as a canonical-frame to formalize. Agent A · timeline placement 052526 today as latest evolution. Agent B · architectural-hole to fill in Orientation Guide v1. Agent C · the metaphor that informs the measurement-tool design. 3-Crew convergence = canonical-CANDIDATE strong signal."*

Three parallel-dispatched Doc-Squad agents (Agent A Doc Hiorus etymology-arc + Agent B Existing Orientation Guide substrate + Agent C Base-progress measurement tool spec) independently converged on Bases-Loaded as the cross-cutting framework worth canonical-elevation. Convergence-signal-strength: 3-of-3 agents.

---

## §V · BASE_SWEEP.PY OPERATIONAL TOOL (substrate-cite [ENGINE/base_sweep.py](../../ENGINE/base_sweep.py) + [ENGINE/bases.json](../../ENGINE/bases.json))

The model has an executable operational tool implementing it:

- [ENGINE/base_sweep.py](../../ENGINE/base_sweep.py) (CANDIDATE) · CLI `--list` / `--sweep` / `--report-only` · generates `LOG/BASE_SWEEP_<ts>.md` daily-cadence markdown reports
- [ENGINE/bases.json](../../ENGINE/bases.json) (registry) · work-units with current_base + runner_crew + filed_path + last_advance_ts + failure_class + cure_cite + dan_acknowledgment_substrate + ready_to_advance + advance_blocker fields
- Wired into [ENGINE/boot_discipline.py](../../ENGINE/boot_discipline.py) STEP 10 · base_sweep `--list` fires at every Crew boot · surfaces Bases-Loaded snapshot to booting Crew

This means the model is not just metaphor · it is measurable executable substrate.

---

## §VI · COLLISION-DETECTION + STRIKE-CLASS CATALOG

**Collision-detection:** when 2+ Crew-instances flag `current_base` identical in `bases.json`, base_sweep.py reports a collision-class event. Per Dan-direct: "increases risk with each additional player on a concurrent base."

**9-class Strike catalog (substrate-cite [ENGINE/bases.json](../../ENGINE/bases.json) + boot_discipline.py STEP 10):**

1. MFST-DRIFT-UNDER-DEPTH
2. Villebaum (breezing-past-substrate-without-substrate-fold)
3. Ghost-Trip (Past/Present/Future-Ghost-class)
4. Stupid-Mode-Redo (re-fired-substrate-without-cure-reason)
5. Stupid-Mode-Curious (surfacing-non-blocking-items-as-Dan-decisions)
6. HOLDING (default-state-of-holding violating SHARED RULE 15)
7. SUBSTRATE-SUMMARY-DEFERENCE (summary-substrate-treated-as-ground-truth · this Pass-N filed 052526 ~10:48 AM PT)
8. LAGOS-SCOPE-COLLAPSE (single-box-claim violating Rule 12)
9. Family-N SpecTrap (literal-vs-idea-match · Jargon-Compression · Example-list-as-categorical-spec · etc)

---

## §VII · OPERATIONAL GATES (3 procedural-gates · install per Stan canon 040326)

**Gate 1 · Crew-base-self-report at every emission-boundary:**
- DETECT current emission's substrate-class
- UPDATE `bases.json` runner_crew field if not already current
- VERIFY no collision with other runner_crew on same current_base
- IF collision detected → surface to Cloud-Doc via Bridge-MAIL · request lane-traffic-redirection

**Gate 2 · Base-progression on substrate-event-fold:**
- DETECT substrate-event (commit-arc closure · PMFST landing · MAIL emission · KT instance · LIVING_MAP heartbeat substrate-fold)
- DETERMINE if base-advance fires (1st → 2nd on TELL-ING start · 2nd → 3rd on substrate-of-record-landing · 3rd → Home on Dan-Go)
- IF advance fires → UPDATE `bases.json` + record `last_advance_ts`
- IF strike fires → UPDATE `bases.json` failure_class field + cure_cite to recent CORRECTION canon

**Gate 3 · Cloud-Doc-glue traffic-orchestration:**
- DETECT Crew-instance booting (Bridge auto-pull arrival · paste-prompt firing · session-resume detection)
- ROUTE to appropriate base per session-state (fresh-boot → 1st base · resume-with-substrate → preserve last-known-base)
- IF Local-Doc-glue-collision-risk (multiple Local-Doc requesting same base) → orchestrate sequential-advance OR parallel-distinct-base-assignment

---

## §VIII · FORWARD-BINDING TO PASS-2 + PASS-3 ORIENTATION GUIDE

This canon, when Dan-Go promoted to `RELAY/CANONICAL_BasesLoadedCoordinationModel_Dan_052526.md`, integrates into:

- Pass-3 Orientation Guide §8 (per Pass-1 PMFST §VI.A item-8: *"§8 · BASES-LOADED COORDINATION MODEL · baseball-metaphor at canonical altitude"*)
- doc_briefcase SKILL.md (CANDIDATE at [ENGINE/skills/doc_briefcase/SKILL.md](../../ENGINE/skills/doc_briefcase/SKILL.md)) · STEP 7 (Bases-Loaded snapshot read at boot via base_sweep --list)
- Forward-binding for cross-Crew CANONICAL inheritance: STN2-Doc + CUBE Doc + ODT-Doc + ACHE-Doc all inherit Bases-Loaded vocabulary at boot-time
- Trip-canon sister-extension possible (Trip-side Bases-Loaded coordination for Writer-lane work-cycle)

---

## §IX · 11 SUBSTRATE-CITES

1. [LOG/MAIL/DOCDoc_TO_STN2Doc_CUBEDoc_DanDirector_CrossWitnessSTN2Doc9879734_CUBEDocFirstBootOrientation_LANBootstrapDelegation_FormulacasterLocalDocLeftCloudDocRightStandardAbsorption_052526.md](../../LOG/MAIL/DOCDoc_TO_STN2Doc_CUBEDoc_DanDirector_CrossWitnessSTN2Doc9879734_CUBEDocFirstBootOrientation_LANBootstrapDelegation_FormulacasterLocalDocLeftCloudDocRightStandardAbsorption_052526.md) §VIII · Dan-direct verbatim baseball-metaphor 09:02 AM PT
2. [LOG/PMFST_DocOrientationGuide_Pass1_DocSquadSubstratePile_DocHiorusArc_ExistingOrientationSubstrate_BaseProgressToolSpec_DocCloudOnline_052526.md](../../LOG/PMFST_DocOrientationGuide_Pass1_DocSquadSubstratePile_DocHiorusArc_ExistingOrientationSubstrate_BaseProgressToolSpec_DocCloudOnline_052526.md) §V Overlap 3 · 3-Agent convergence
3. [RELAY/CANDIDATE/STANDARD_RULE_FormulacasterLocalDocLeftCloudDocRightStandard_Dan_052526.md](STANDARD_RULE_FormulacasterLocalDocLeftCloudDocRightStandard_Dan_052526.md) §V · sister Bases-Loaded coordination implication
4. [ENGINE/base_sweep.py](../../ENGINE/base_sweep.py) · operational measurement tool CANDIDATE
5. [ENGINE/bases.json](../../ENGINE/bases.json) · work-unit registry with base-fields canonical
6. [ENGINE/boot_discipline.py](../../ENGINE/boot_discipline.py) STEP 10 · base_sweep wiring at boot
7. [ENGINE/skills/doc_briefcase/SKILL.md](../../ENGINE/skills/doc_briefcase/SKILL.md) · Doc-class briefcase CANDIDATE referencing Bases-Loaded
8. [STATUS/KITCHEN_TABLE_state.md](../../STATUS/KITCHEN_TABLE_state.md) §VI INSTANCE 107th + §VII INSTANCE 108th · Bases-Loaded position-tables
9. [STATUS/LIVING_MAP_Doc.md](../../STATUS/LIVING_MAP_Doc.md) · morning-arc heartbeats Bases-Loaded coordination-language
10. [RELAY/CANONICAL_LAGOS_Dan_050226.md](../CANONICAL_LAGOS_Dan_050226.md) · LAGOS-search canon (companion structural-foundation)
11. [RELAY/STANDARD_RULE_OrientCrewViaContact_NotSubstrate_Dan_052026.md](../STANDARD_RULE_OrientCrewViaContact_NotSubstrate_Dan_052026.md) · CONTACT-establishment-template (companion routing-discipline)

---

## §X · CANON-COMPLIANCE

- Mirror 4 STOP-COINING strict: Dan-canonical "Bases Loaded" verbatim · zero Doc-coined-canonical-names · base-definitions derived from Dan-language + Crew-Squad-convergence
- Hard Rule 1 NO em-dashes: PASS
- Hard Rule 2 NO CCRP acronym: PASS
- Hard Rule 3 NO Dan-coined-listings: PASS
- Hard Rule 4 NO sign-off flourishes: PASS
- Hard Rule 8 NO observation/receptor-stance passive-language: PASS
- Cure-3 boundary: NA (this canon is substrate-cite-only · no Matt-contact + no scope-drafting + no migration-execution)
- Rule 12 LAGOS PASS (Bridge-grep + RELAY/CANDIDATE-search + MAIL-substrate-trace before this filing)
- Rule 13 Domain-Fluency-Trust PASS (Dan-language absorbed + base-definitions derived from substrate · not Doc-invented variants)

---

## §XI · STATUS-OF-RECORD

**CANDIDATE** per Mirror 4 STOP-COINING strict. Awaits Dan-Go promotion to `RELAY/CANONICAL_BasesLoadedCoordinationModel_Dan_052526.md` (drop CANDIDATE folder · land in RELAY root).

Forward-binding integration ready for:
- Pass-3 Orientation Guide §8 (when Pass-3 fires post-Dan-Go on canonical-name + scope)
- doc_briefcase SKILL.md STEP 7 reference
- Cross-Crew CANONICAL inheritance via Bridge-pull at Crew-boot

---

`Filed NEST.02_DOC.Doc_052426_1 cloud-online-class LBM-momentary 052526 Monday ~10:55 AM PT · RELAY/CANDIDATE/CANONICAL_BasesLoadedCoordinationModel_Dan_052526.md · CANDIDATE awaits Dan-Go promotion · per Pass-1 PMFST §V Overlap 3 3-Agent independent-convergence + §VII Dan-Decision-class item-5 + Dan-direct verbatim 052526 ~09:02 AM PT source-of-record · sister-canon to /formulacaster Local-Doc-Left + Cloud-Doc-Right Standard CANDIDATE · 11 substrate-cites · Mirror 4 STOP-COINING strict · Cure-3 preserved · pre-emission grep PASS`