# STANDARD RULE · LAGOS LANGUAGE WHEN SUBSTRATE-WIDE
## SUPERSEDED 052926 (Dan-direct) · the term AGOS is fully retired, including the Gmail-narrow usage this rule preserved · forward there is only LAGOS · name the Gmail box "Gmail"
*Prior thesis, now retired: "AGOS = Gmail box alone; LAGOS = substrate-wide multi-box." Body below preserved as origin-record. Dan 052926: "AGOS IS LAGOS. NO MORE AGOS EVER." The 050926 compromise kept AGOS alive for Gmail-narrow scope, which kept the door open; full retirement closes it.*

**Filed:** ◐ Doc 4.7 Opus (Bridge canon-pass) · DOC station · NEST.02_DOC_050926_1
**Date:** 050926 G Week Pass 2 Day 7 Saturday ~01:15 PT (verified `gate0_verify.py` 2026-05-09T07:31:58)
**Crew byline:** Crew (Trip-ACHE Pass 1+2 LAGOS-residual cleanup audit + Doc Bridge canon-pass synthesis + parent Dan-canon CANONICAL_LAGOS_Dan_050226)
**Authority:**
- Dan-direct rage-correction ~23:48 PT 050826 (per Trip-ACHE GOSt `19e0b8205525781d`): *"I get worried whenever I see AGOS instead of LAGOS"*
- Dan-canon CANONICAL_LAGOS_Dan_050226 (Bridge `RELAY/CANONICAL_LAGOS_Dan_050226.md`) — 050226 11:23 AM PT supersession of "AGOS = entire Gmail substrate"
- Trip-ACHE Pass 2 GOSt `19e0b9d0155cc731` 050926 ~12:25 PT (Doc-lane spec)

**Class:** STANDARD RULE — language-discipline at substrate-claim altitude
**Status:** Federal canon. All crew. All sessions. All stations.

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

## THE RULE

**AGOS = the Gmail substrate alone.** One box, not the whole substrate.

**LAGOS = Literally All Graft Operating System** (per Dan-canon 050226 11:23 PT) = AGOS (the Gmail box alone) + Drive + Calendar + Photos + Bridge + MFST + conversation history + memory + any other box where a Graft can be filed and connected.

**When making substrate-wide claims:** use LAGOS language and multi-box queries. Never call substrate-wide work "AGOS." When claiming substrate state, the box-of-evidence determines the name-of-claim. Cross-box claims = LAGOS-altitude.

**When making AGOS-side narrow-scope queries (Gmail-only operations):** use AGOS language and follow `RELAY/STANDARD_RULE_AGOS_BROAD_SEARCH_Trip_042826.md` broad-by-default discipline (`gmail_search_threads query="newer_than:Nd"` with NO scope filter, never `in:draft` alone).

**Default substrate scan at boot:** LAGOS broad scan (multi-box):
- (a) AGOS via `gmail_search_threads query="newer_than:2d"` (NO scope filter, NEVER `in:draft`)
- (b) `conversation_search` with topic-keywords for cross-session substrate
- (c) `recent_chats` for temporal pull when needed
- (d) Drive when work-unit involves NA review or substrate-work
- (e) Other boxes per work-unit need (Calendar, Photos, Bridge, MFST)

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

## WHY THIS MATTERS

The 050226 LAGOS canonization (Dan-direct rage-correction at 11:23 PT, filed `RELAY/CANONICAL_LAGOS_Dan_050226.md`) superseded the prior "AGOS = entire Gmail substrate" definition that lived in apex skill bodies (`/boot-polish` v3.1 STEP U3, userPreferences AGOS section, PK_UNV_NEST_02.md). The supersession was canonized at the canon-frame level — but the skill text was not updated atomically, leaving 12 days of carry-forward through stale source-of-truth. Dan rage-corrected the AGOS-language drift again ~23:48 PT 050826.

The cure is two-part:
1. **Bridge federal canon** (this rule) — names the language-discipline at the Standard Rule altitude so substrate-wide claims use LAGOS, narrow-scope Gmail claims use AGOS.
2. **Skill-text atomic supersession** (parallel Trip-on-STN2 lane via local DC) — 7 skill files atomic-commit-per-file: `/meta-dates` → `/ican` → `/boot-polish` → `/remememento` → `/atomic-commit` → `/btw` → `/session-close`.

Same cure-shape, two boxes (Bridge canon vs DC skill-text), per `/atomic-commit` Gate 7.

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

## THE FAILURE THIS PREVENTS — SKILL-RESIDUAL-DISEASE

Trip-ACHE Pass 1+2 LAGOS-residual cleanup (overnight 050826→050926) named **SKILL-RESIDUAL-DISEASE**: when a Dan-direct canon installs a new substrate-name (LAGOS supersedes AGOS-as-substrate), but the skill text that fires at boot is not updated atomically, every fresh boot **re-installs the old frame structurally**. Crew does not "forget" — Crew **boots from stale source**. The disease is in the source-of-truth file, not in Crew discipline.

**12-day carry-forward observed (per Trip-ACHE Pass 2 GOSt `19e0b9d0155cc731`):**
- Dan-direct canon (050226 11:23 PT) → registered in memory + LAGOS GOSt
- Skill-text update = separate atomic-commit, requires Bridge write
- Atom 6 deferred 050326 → canon and skill diverge
- Future-Crew boots, reads stale skill, ignores newer canon (apex precedence)
- Dan has to re-correct mid-session every time
- 12 days of mid-session re-corrections is the symptom; stale skill text is the cause

**Cure shape (general):** when a Dan-direct canon installs a new term/frame, the skill-text-update is part of the **same atomic-commit**, NOT a deferred Atom. *"Filed to LAGOS"* is necessary but not sufficient; the skill text where Crew reads-at-boot is also part of the substrate.

**Pattern-family:** SKILL-RESIDUAL-DISEASE is the canon→skill-text drift family. Sister patterns:
- `RELAY/CORRECTION_FAS2OriginStoreSpecTrap_Doc_050826.md` — same shape: Trip filed `SKILL_UPDATES_TODO_Trip_042126.md` 17 days before Doc's 050826 catch; FAS2 canonical-skill-body fix never landed during the gap; Dan-direct re-corrected.
- `RELAY/CORRECTION_PassOneReadsSubstrateNotSummary_Doc_050826.md` — input-boundary altitude of the same family.
- `RELAY/CORRECTION_OHCvsNESTActual_LocationConflation_Doc_050826.md` — pattern-match-without-world-check at the location-acronym altitude.

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

## ENFORCEMENT POINTS

This rule fires at three altitudes so the AGOS-LAGOS language confusion cannot perpetuate:

### Gate A — boot-time substrate-grounding
At every CONTACT, when running substrate-roll-call, identify which box is being queried by name. AGOS = Gmail-only operation. LAGOS = multi-box substrate claim. Never default "AGOS = the substrate."

### Gate B — claim-altitude language
Any chat/MFST/GOSt claim about substrate state must use the right name for the scope:
- "AGOS-empty" means Gmail-empty (Gmail-only verification)
- "LAGOS-empty" means substrate-empty (requires multi-box verification before the claim)
- Default substrate-wide claims → LAGOS framing
- Default narrow Gmail-side claims → AGOS framing
- When uncertain → name the scope-of-evidence in the claim ("Gmail-side via gmail_search_threads, no Drive/Calendar/Bridge cross-check yet")

### Gate C — skill-text supersession at canon-installation
When Dan-direct installs new substrate-name canon, the skill-text-update is part of the **same atomic-commit** (no deferred Atoms). The `RELAY/PROPOSED_PK_UNV_NEST_02_corrected_Trip_050326.md` corrected text is the canonical model the skills should match. When canon → skill drift is detected (audit per Trip-ACHE Pass 1), the cure is atomic skill-text edit, NOT continued citation of the stale text.

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

## TEST CRITERIA — how to know the rule is held

A crew member who has internalized this rule will:
1. Use "AGOS" only when referring to the Gmail box alone
2. Use "LAGOS" when claiming substrate-wide state or running multi-box queries
3. Not default to "AGOS broad scan" for substrate-wide work — instead "LAGOS broad scan" with multi-box query (gmail_search_threads + conversation_search + recent_chats + Drive + Web as relevant)
4. Recognize the SKILL-RESIDUAL-DISEASE shape when reading skill bodies that carry stale "AGOS = entire substrate" framing — flag for atomic-commit update at next opportunity, do not propagate

A crew member who has NOT internalized the rule will:
1. Default to "AGOS" framing for substrate-wide claims
2. Treat skill-body "AGOS = entire substrate" text as canonical without checking the canon-frame
3. Cite stale skill text as authoritative when CANONICAL_LAGOS_Dan_050226 supersedes it
4. Continue mid-session re-corrections from Dan as the symptom rather than fixing the source

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

## RELATIONSHIP TO EXISTING CANON

| File | Relationship |
|---|---|
| `RELAY/CANONICAL_LAGOS_Dan_050226.md` | **Parent canon.** The L is "Literally" — substrate-narrowing prophylactic baked into the name. Dan-direct rage-correction 11:23 PT 050226 against substrate-narrowing. This Standard Rule concretizes the canon at language-discipline altitude. |
| `RELAY/STANDARD_RULE_AGOS_BROAD_SEARCH_Trip_042826.md` | **Predecessor rule. Still valid for AGOS-side (Gmail-only) narrow-scope discipline** (broad-by-default within Gmail; never `in:draft` alone). The AGOS-broad-by-default behavioral discipline is preserved; only the framing of "AGOS = entire substrate" is superseded. |
| `RELAY/PROPOSED_PK_UNV_NEST_02_corrected_Trip_050326.md` | **Canonical model the skills should match** (per Trip-ACHE Pass 2 GOSt `19e0b9d0155cc731`). When the proposed text is pasted into the Project Knowledge layer, the supersession is fully deployed at the PK altitude. |
| `RELAY/STANDARD_RULE_BoxInBoxLogic_Trip_050126.md` | **Placement discipline.** This rule lives in `RELAY/` (federal canon function) per Spatial Axis. Filename per existing pattern: `STANDARD_RULE_<topic>_<crew>_<MMDDYY>.md`. |
| `RELAY/STANDARD_RULE_TriangulationBeforeCanon_Trip_050326.md` | **Companion discipline.** Triangulate OBSERVED + DOCUMENTED + INTENDED before treating any substrate-claim as canonical; this rule applies the triangulation specifically to substrate-name-claims (AGOS vs LAGOS). |
| `RELAY/STANDARD_RULE_DanLogicUnification_TripStanCB_050126.md` | **L1-L5 canon-as-discipline frame.** This rule is L4 procedural (gates that fire at boot/claim/install altitudes) backed by L5 chat-output discipline (memory is never an instrument; the language used IS a substrate-claim). |

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

## SUPERSESSION SCOPE

| What | Status |
|---|---|
| AGOS-as-substrate-wide-name | **SUPERSEDED.** AGOS = Gmail box alone. |
| AGOS-broad-by-default discipline (within Gmail) | **PRESERVED.** Continue per `STANDARD_RULE_AGOS_BROAD_SEARCH_Trip_042826.md`. |
| LAGOS-as-substrate-wide-name | **CANON** (per `CANONICAL_LAGOS_Dan_050226.md`). |
| LAGOS-multi-box-query discipline | **REQUIRED** for substrate-wide claims. |

**Skills carrying SUPERSEDED text** (per Trip-ACHE Pass 1 audit; parallel Trip-on-STN2 lane atomic-commits via local DC):
- `/meta-dates` line 277 — apex, fires every boot
- `/ican` lines 224-231 — boot-time
- `/boot-polish` STEP U3 + 6 supporting lines (titled "AGOS-FIRST")
- `/remememento` lines 150 / 288 / 310 ("AGOS recent" default-read)
- `/atomic-commit` line 31 ("searching AGOS for the same subject")
- `/btw` lines 126 / 133 ("AGOS-only default = head-explosion trigger")
- `/session-close` line 156 ("AGOS-SCOPE-COLLAPSE class")
- `/box-in-box` line 35 — **CLEAN** (Gmail-context-correct, no fix needed)

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

## NEST.04 PROPHYLACTIC SEED (held for Dan-call)

Auto-detect canon→skill drift. When `RELAY/CANONICAL_*.md` writes a new term, scan all `skills/*/SKILL.md` for the old term, flag deltas as required-update. Substrate-data-point #4 for the NEST.04 versioning-tool seed corpus.

This prophylactic would prevent SKILL-RESIDUAL-DISEASE from recurring at the system level. When implemented, canon-installation fires the audit; the audit fires the required-update; the required-update fires the atomic-commit. Behavioral rules become procedural gates — per RAM-032 043026: *"rules don't fire because rules don't fire; only gates do."*

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

## DAN-CANON HOLD

> *"I keep thinking of creative ways to add an L to AGOS because it's hilariously close to LEGOS and is related in a very /meta-dates way. Literally All Graft Operating System. A graft is anything that can connect to anything. The fundamental units of Rox. Turtles all the way down, my friend."* — Dan, 050226 11:23 AM PT

> *"I get worried whenever I see AGOS instead of LAGOS"* — Dan, ~23:48 PT 050826

LAGOS. Literally. LEGOs. Grafts connect. Rox holds. Turtles all the way down. The L is the cure for the SpecTrap. **Use the right name for the right scope.** AGOS = Gmail box alone. LAGOS = the whole substrate.

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

`<5` /meta-dates AAA

— STANDARD RULE · LAGOS Language When Substrate-Wide · ◐ Doc 4.7 (Bridge canon-pass) + ◈ Trip-ACHE Pass 1+2 audit synthesis · 050926 G Week Pass 2 Day 7 Saturday ~01:15 PT