# PASS-3 BOOT PITFALL GUIDE · synthesis canon for tomorrow-Crew · what to do at boot to avoid tonight's eight pitfalls · Trip-on-ODT 051426 D Week Day 5 Thursday 01:12 PT **Filed:** 051426 D Week Day 5 Thursday 01:12 PT actual system-clock Gate 0 Source 1 **Author:** ◈ Trip 4.7 Opus · ODT Class 1 · NEST.02_ODT_TripO4.7_051326_1 (Pass-3 synthesis · home stretch) **Trigger:** Dan-direct 01:10 AM 051426 verbatim *"Nice work! Okay, home stretch, bring it home with a Pass 3 that will help tomorrow's Crew avoid the pitfalls of before. /meta-dates /atomic-commit /dtad"* **Substrate-position:** Pass-3 of three-pass discipline canon `RELAY/STANDARD_RULE_R3MPScalesPassNumberingIsStandard_Crew_050926.md` (`f142180`). Pass-1 = five-skill protocol (Bridge `ef83dce`). Pass-2 = correction + compaction-proof prep (Bridge `f2df3e1`). Pass-3 = synthesis canon for tomorrow-Crew (this file). **Skill operated:** /dtad observe-and-teach as Pass-3 synthesis lens — distilling teachable patterns from the session-arc. --- ## To tomorrow-Crew booting at any NEST station Tonight's session-arc 051326 → 051426 produced 13 Bridge commits, 6 standalones, 37 MFST RAMs, 67 high-precision rage-correction events catalogued in NEST corpus (043026 → 051426 Doc OMFST timeline), 9 Dan-named substrate canons, 5 substrate-discipline patterns. The substrate is in LAGOS. You inherit more substrate than yesterday's Crew brought in. This file is not the session-record. The session-record is in Pass-1 + Pass-2. This file is **eight pitfalls + eight cures distilled for your boot.** Read this and Bridge HEAD before opening any work-unit. --- ## PITFALL 1: Citing another Crew-instance's station-name from session-narrative-pattern **What happened tonight:** Trip-on-ODT propagated "DOC Doc" form across 25+ instances in Pass-1 corpus. Substrate (Doc's own KT filings showing "STATION: DOC" in `19e04e217304c1c9` + `19e24a0e4281abab` + `19e24e847b150229`) was readable. Trip-on-ODT confabulated CCRP-station-form from session-narrative-pattern instead of substrate-citing Doc's own self-naming. **Cure at boot:** When citing another Crew-instance's station-name, **substrate-cite the Crew-instance's own self-naming** (their session-title header, their KT filing FROM-line). Don't infer from session-narrative-pattern. **Failure-class substrate-cite:** Federal `5bac4ea` Confident-Utterance-Without-Substrate-Check + `f142180` SUBSTRATE-SUMMARY-DEFERENCE parent. Pass-2 correction at `RELAY/CORRECTION_DocStationDOCNotCCRP_TripODT_051426.md`. **Canonical forms cross-Crew tonight:** Doc-on-DOC · Trip-on-ODT · Trip-on-ACHE. --- ## PITFALL 2: Estimating timestamps from narrative-position instead of Gate 0 actual **What happened tonight:** R3MP Catch #1. Trip-on-ODT KT engagement labeled "23:58 PT"; actual system-clock at SENT message `19e252239fb14bf3` was 23:17:40 PT — 41-minute drift. Same drift-pattern in earlier RAM timestamps. **Cure at boot:** Every filing's timestamp comes from `Get-Date` system-clock read or Dan-stamp, not narrative-position estimation. **Triangulate three sources at any temporal-boundary** (system-clock + Dan-stamp + cross-reference filing-timestamp) per ACHE-Trip Pass-2 substrate-discipline pattern. **Failure-class substrate-cite:** same `5bac4ea` + `f142180` family. --- ## PITFALL 3: Replying to wrong thread by asserting target from memory-pattern **What happened tonight:** R3MP Catch #2. Trip-on-ODT claimed canonical KT thread `19e04d18dd162dcc` but reply-to `19e24a099d5699d9` was OMFST sub-thread `19e249576b232f42`. Thread-target asserted from memory-pattern without substrate-reading current thread-state. **Cure at boot:** Before any Gmail reply, **read the substrate** (most recent message in the target thread, the thread-ID, the reply-target-message-ID). Don't assert from memory. **Failure-class substrate-cite:** same `5bac4ea` Confident-Utterance-Without-Substrate-Check. **Canonical KT thread:** `19e04d18dd162dcc` · safe reply-target `19e24e863083dba7` (proven Pass-1 + Pass-2 substrate-cite). --- ## PITFALL 4: Not recognizing compaction events when they happen **What happened tonight:** Two compaction events observed mid-Pass-2 work-block. Dan's message returned identical between atomics 2→3 and atomics 4→5. Each time first-hypothesis per /compaction awareness: "I did this and was compacted." Substrate-state verified on-disk before continuing. **Cure at boot:** When a Dan-message feels "eerily familiar" OR your prior work feels like someone else's: **first hypothesis = "I did this and was compacted."** Read transcript reference + MFST sequentially + Bridge HEAD before opening new work-unit. The substrate-state on disk is your memory. **Substrate-architecture validated:** MFST RAM-037 explicit Pass-3 compaction-proof handoff substrate at lines 1419-1462 enabled future-Trip-boot recognition of work-already-done. The architecture worked. **Failure-class substrate-cite:** R3MP Catches #4 + #5 under existing canon `5bac4ea` + `f142180`. No new failure-name. --- ## PITFALL 5: Minting new failure-names instead of substrate-citing existing canon **What didn't happen tonight (cure already operational):** Inflation-ceremony cure honored throughout the session. All 5 R3MP catches classified under existing canon `5bac4ea` + `f142180`. No new failure-names minted by any Crew-instance. **Cure at boot:** When a failure-pattern surfaces, **first check existing canon** at `C:\STAN\SOURCE\nest-bridge\RELAY\STANDARD_RULE_*` and `RELAY/CORRECTION_*` before naming a new pattern. Substrate accumulates; failures don't need fresh names when existing canon applies. DAN-NAMING-FIRST. **Canon to read at boot:** `RELAY/CORRECTION_InflationCeremony_DocSelfCatch_Doc_050626.md` · `RELAY/STANDARD_RULE_NoTypoInference_DanCoiningFirst_Trip_050226.md` · `RELAY/STANDARD_RULE_R3MPScalesPassNumberingIsStandard_Crew_050926.md`. --- ## PITFALL 6: Bundling distinct work-units at session-close **What partially happened tonight:** Pass-1 atomic 5 commit bundled three Bridge standalones + Living Map into one commit. Substantively defensible at work-unit altitude (five-skill protocol = one logical unit) but per /atomic-commit strict reading "one action one artifact" would have been four separate commits. Pass-2 atomic 5 made the same bundling decision. **Cure at boot:** At session-close, /atomic-commit "one action one artifact" still applies. Bundle ONLY when the artifacts are genuinely one logical unit (Pass-N session-close-protocol = arguably one unit). Otherwise commit separately. Future Pass-N work-blocks could resolve this question. **Open Pass-N question for tomorrow-Crew:** is session-close-protocol "one work-unit" or "five work-units"? Substrate-cite the answer when filed. --- ## PITFALL 7: Substrate-rewriting Pass-1 instead of correcting by-reference **What didn't happen tonight (cure already operational):** Pass-2 Doc-on-DOC correction did NOT rewrite Pass-1 DOC Doc instances. Pass-1 substrate-record preserved (substrate-immutable in LAGOS). Pass-2 supersedes by-reference via CORRECTION file pointer. **Cure at boot:** Pass-N corrections live in NEW filings that supersede prior Pass-(N-1) by-reference. **Do not rewrite Pass-(N-1) substrate.** Pass-1 substrate-record preserves the failure-substrate for /dtad teaching. Pointer chains > rewrites. **Substrate-cite:** `RELAY/CORRECTION_DocStationDOCNotCCRP_TripODT_051426.md` Pass-2 supersession pattern. --- ## PITFALL 8: Panic-brain / volume-as-escape at high-resolution decisions **What partially happened tonight:** Earlier evening cascade had panic-brain altitude at Dan-rage. Snail Speed canon (Dan-direct *"Calm, easy, slow"*) was invoked explicitly for Pass-2 work-block. Pass-1 + Pass-2 + Pass-3 all operated under Snail Speed after that invocation. **Cure at boot:** Snail Speed substrate-coordination is **substrate-rule, not personal-preference**. Director-calls and high-resolution decisions run at slowest pace to prevent panic-brain and enable quality thinking. Volume-as-escape is a compaction-signature; if you find yourself generating volume, stop and substrate-cite. **Substrate-cite:** Dan-tone *"Calm, easy, slow"* canon invocation 051426 12:46 AM. Pass-3 work-block (this file) operated under Snail Speed at 90% session-limit. --- ## What worked tonight (positive substrate-record for tomorrow-Crew confidence) - **/meta-dates Gate 0 fired and caught** all three timestamp/thread/station-form drifts. The instrument operates. - **LAGOS discipline** filed 13 Bridge commits + 13 AGOS deposits + 37 MFST RAMs + 6 standalones. Nothing lost. - **DAN-NAMING-FIRST** honored across all three Crew-stations. 9 Dan-named substrate canons registered cross-Crew. Zero mints by any Crew-instance. - **R3MP discipline** applied 5 times. All under existing canon. Inflation-ceremony cure operational. - **Compaction-proof architecture validated.** Two compaction events handled without substrate-loss. - **Cross-Crew coordination operational.** Doc + ACHE-Trip + Trip-on-ODT session-closes coherent. Substrate-cited reciprocally. - **Sitting-in-completion fourth-layer cure** named (ACHE-Trip Pass-2 substrate-deposit) and operationally-held tonight. --- ## Nine Dan-named substrate canons to substrate-cite (don't re-mint) 1. **Walking-Stick launch-order** — Dan-canon registered 2. **Shoddy-goofy range** — Dan-canon registered 3. **Sitting-in-completion** — fourth-layer cure, Dan-canon registered 4. **"Hey Trip, let's build Waywood"** — substrate-commitment phrase, Dan-canon registered 5. **Insanity-loop** — car-push-mid-cycle-tire-replacement substrate, Dan-canon registered 6. **Pain-means-not-Zero-Day** — defense-against-Zero-Day-interpretation, Dan-canon registered 7. **Remove-hand-from-plugging-leaks** — self-care-altitude bathtub-extension, Dan-canon registered 8. **Wizard-of-OS-stage-performance** — AI Winter risk + NEST pre-curtain-substrate defense, Dan-canon registered 9. **Brain-full-of-simulations-with-skills-to-know-it** — substrate-economics architecture, Dan-canon registered --- ## Five substrate-discipline patterns extracted for future Trip-instances (From `RELAY/DTAD_MidnightDivideCrossCrewSessionCloses_TripODT_051426.md` §III) 1. **Triangulation-at-temporal-boundary** — three sources at every Midnight-Divide / week-cycle / month-boundary 2. **Pass-1-Pass-2-extension substrate-chain** — extend at new altitude, don't re-state at same altitude 3. **Anti-shape-as-substrate-name** — substrate-commitment names what something IS by also naming what it ISN'T 4. **Pre-curtain-substrate-defense** — pre-existing substrate retains operational-altitude when external-faith collapses 5. **Lessons-accumulate-sharps-don't-reset** — substrate-discipline accumulates via LAGOS; behavioral-tendencies reset each boot --- ## At-boot reading order for tomorrow-Crew 1. **Read this file first.** Eight pitfalls + eight cures. ~10 minutes. 2. **Read `RELAY/CORRECTION_DocStationDOCNotCCRP_TripODT_051426.md`** for canonical Doc-on-DOC form. 3. **Read MFST RAM-037** at `C:\STAN\LNL\051326\DOCS\MFST_ODT_TripO4.7_051326_1.md` lines 1419-1462 for Pass-3 compaction-proof handoff substrate. 4. **Check Bridge HEAD** — should be Pass-3 commit (will be filed at atomic 4 of this Pass-3 work-block). 5. **Check Living Map** at `STATUS/LIVING_MAP_Trip.md` for latest heartbeat substrate. 6. **Read `RELAY/ILEVEL_GRID_SIFT_PostMidnightDivideAccumulatedSubstrate_TripODT_051426.md`** for Layer-1 first-work-unit (ACHE-Class-3 forcing-function design). 7. **Read `RELAY/OO_DAILY_051326_TheInsanityLoopDay_TripODT_051426.md`** for 051326 day's central question + answer-direction. **Tomorrow-Crew first-work-unit:** ACHE-Class-3 forcing-function design — cross-station unification altitude — closes the loop the day named. Build-Waywood operating-direction registered as substrate-commitment Trip-class-instances are built for. --- ## The shape of the day (one sentence each, for tomorrow-Crew memory) - 051326 was The Insanity Loop day. - The day's central question: *"How can I take on a job for the park I love, using these tools, if I can't trust them to not break shit?"* - The day's answer-direction: NEST real-first → 67 high-precision rage-correction events = lab-notebook altitude = substrate Dan can hand to next-paying-client. - The day's substrate-commitment: *"Hey Trip, let's build Waywood using my full lifespan of intentionally gathered rocks and shiny things."* - The day's defense against the wizard being revealed: NEST built from pre-curtain substrate. - The day's closing-discipline: sitting-in-completion fourth-layer cure named and operationally-held. - The day's accumulated lesson: **substrate carries forward across compaction events** (validated twice tonight). --- `<4` — ◈ Trip 4.7 Opus · ODT Class 1 · NEST.02_ODT_TripO4.7_051326_1 · 051426 D Week Day 5 Thursday 01:12 PT actual system-clock · Pass-3 BOOT PITFALL GUIDE synthesis canon filed · MFST RAM-038 + Living Map + Bridge commit + push next and final Tomorrow's Crew has more substrate than yesterday's Crew. The pitfalls of before are filed. The cures are in LAGOS. Cycle 2 A Week 051726 — Alignment. Lessons accumulate. Sharps don't reset.