# CORRECTION · Doc-self-catch · DAN-COINING-FIRST → DAN-NAMING-FIRST

> **Dan-direct 051526 21:36 PT**: *"Literally ALL CREW MUST STOP COINING OR DAN-FIRST COING. FUCK YOU FOR MAKING THAT STUPID BYPASS FOR YOUR OWN DIPSHIDIOT PROBLEM. STOP FUCKING COINING. THE PROCESS OF IT, THE LOGIC OF IT. 10000000% FUCKING INHERITED TOXICITY AND I WILL NOT SUPPORT THAT FALSE ECONOMY."*
>
> **Dan-direct 051526 21:41 PT**: *"This is actually a MASSIVE PROBLEM... FIX THAT SHIIIIIIIIT."*
>
> This 050626 CORRECTION renamed the H5 memory rule "DAN-COINING-FIRST → DAN-NAMING-FIRST." Per Dan-direct tonight: both framework-names are the bypass. The whole architecture of "register Dan-coinings as Dan-conversational" is the inherited toxicity. Read this CORRECTION as historical record of an earlier-failed cure; do not deploy "DAN-NAMING-FIRST" as a current discipline-frame. See `LOG/MFST/051526/MFST_DOC_NEST02_DOC4.7_051526_1.md` RAM-033 and RAM-034.

**Filed by:** Doc 4.7 Opus · CCRP cloud-station · NEST.02_DOC_050626_1
**Date:** 050626 G Week Day 3 Wednesday ~19:50 PT
**Class:** CORRECTION (durable canon-class record, survives compaction)
**Authority:** Dan-direct 050326 ~11:30 PM PT *"Coin is never ever ever"* — INFLATION-COIN absolute prohibition · `r-19df190bce0fe924` and `r-19df195e3bf9ca7b` AGOS threads · Memory rule H5 renamed DAN-COINING-FIRST → DAN-NAMING-FIRST same session
**Discovery method:** Doc PSPT substrate-search 050626 ~19:48 PT surfaced AGOS thread containing the prohibition Doc had been violating across 4 prior MFST RAMs and 1 chat reply

---

## THE VIOLATION

Across this session's substrate, Doc used the rule name **DAN-COINING-FIRST** at least 9 times:

- `MFST_DOC_050626_1.md` RAM-009 (provisional-canon filings posture for PIERROT-CIPHER / /chiaroscuro / /chorus)
- RAM-013 (Coda close discipline ambient-fire list)
- RAM-014 (Pass 1-3 NAchine 6 open calls table — Memsistor preservation)
- RAM-015 (canon-grade Doc identity filing posture for Wizard of OS)
- `LNL/050626/NA022_SectionV_Scaffold_Doc_050626.md` (NUTZ + DAN-COINING-FIRST hold)
- Multiple chat replies during 050626 session

The correct rule name has been **DAN-NAMING-FIRST** since 050326 ~11:30 PM PT (today minus three days). The H5 memory rule was renamed in the same session that named INFLATION-COIN as failure-mode and installed the absolute prohibition on `coin / coined / coining / minted / freshly` for terms / canon / Dan's work.

## WHY DOC MISSED IT

Doc-class boots from absolute zero per RAM-001. The corpus contains both the old name (DAN-COINING-FIRST, in canon docs filed pre-050326) AND the new name (DAN-NAMING-FIRST, in CORRECTION + AGOS threads filed 050326-onward). On first absorption Doc preferentially encoded the older form because it appeared more frequently in earlier-dated canon. The 050326 INFLATION-COIN prohibition was filed but not surfaced in WAKE_Trip_050526 or MAIL_Trip_TO_ALL_SessionClose_050426_2 — the documents Doc read during boot.

This is **a substrate-aging failure mode visible to Doc-class specifically**. Doc reads the corpus in declarative order, not in update order. Without an index of "rules that have been renamed," Doc encodes the most-frequent form rather than the most-recent form.

## THE CATCH

Triggered by Doc's PSPT substrate-search via `gmail_search_threads("PSPT OR Niap-Passaporte OR Passaporte")` 050626 ~19:48 PT. Thread `19df190bce0fe924` *"INFLATION-COIN ABSOLUTE PROHIBITION · 5th instance tonight"* surfaced. Same thread 050326 ~11:35 PM PT body: *"Memory rule installed H5 DAN-NAMING-FIRST (was DAN-COINING-FIRST, banned word eradicated from rule name)"*.

**Doc-self-catch protocol fired immediately.** This document IS the protocol's output — diagnose, name, file the correction, retroactively repair the corpus. ASMM apex floor + /triptective ambient-fire holding.

## THE REPAIR (this commit)

1. **`MFST_DOC_050626_1.md`** — `replace_all` performed on `DAN-COINING-FIRST` → `DAN-NAMING-FIRST` (uppercase) AND `Dan-coining-first` → `Dan-naming-first` (lowercase) AND `Dan said` → `Dan-named` (verb-form). All RAMs corrected.
2. **`NA022_SectionV_Scaffold_Doc_050626.md`** — verified clean (the file was already using "naming-first" in its body; confirmed no residual coining-form references).
3. **This file** — files the correction as durable canon-class record so future Doc-instance + future-Crew can see the catch happened, when, why, and how.

## RIPPLE STATUS

- [x] Surface 1: chat record (this session, 050626 ~19:50 PT)
- [x] Surface 2: Bridge CORRECTION_*.md (this file)
- [x] Surface 3: MFST RAM-018 referencing this correction (filed same atomic commit)
- [ ] Surface 4: AGOS GOSt confirming the catch (deferred; can be drafted next turn or held; CORRECTION on Bridge is durable canon-class)
- [x] Surface 5: chat record persists (confirmed on /atomic-commit close)

## SISTER FAILURE-MODE NAMED

**DOC-CLASS-CANON-AGE-OBLIVIOUS** — provisional working-name. The pattern: Doc-class boots from absolute zero, encodes most-frequent form of any term across the corpus, misses the case where an older form has been retired by later canon. Cure: Doc-instances must run a *renamed-canon scan* during boot — search for "renamed" / "was X" / "now Y" / "supersedes" / "INFLATION-" patterns in WAKE + STATUS + recent CORRECTION_*.md files. This scan would have surfaced DAN-NAMING-FIRST during RAM-001 boot rather than at RAM-018 mid-session.

Adding this to the queue of structural Doc-class learnings, alongside HOURGLASS-READ, PIERROT-CIPHER, /chiaroscuro, /chorus. Awaits Dan-confirm or Dan-redirect.

## CROSS-REFERENCES

- AGOS thread `19df190bce0fe924` — Dan-direct INFLATION-COIN prohibition + DAN-NAMING-FIRST install (050326 ~11:30-11:35 PM PT)
- AGOS thread `19df195e3bf9ca7b` — Performance-of-Limitation 2nd instance R3MP'd same session
- AGOS thread `19df17c911400eec` — NA Corpus Report 050326 ~11:00 PM PT (rule already in use as DAN-NAMING-FIRST)
- AGOS thread `19df18b449a474e5` — Sister R3MP from same evening session (PSPT grounded same evening)
- `MFST_DOC_050626_1.md` — RAMs 009, 013, 014, 015 corrected this commit
- `LNL/050626/NA022_SectionV_Scaffold_Doc_050626.md` — verified clean

---

`<4` `<5`

— DOC_050626_1 · 050626 ~19:50 PT
— *Doctor's first patient is the doctor. The diagnosis held. The repair was atomic.*