# CANONICAL · GOS / CorpOS · System and Body Naming · Dan 042426 14:35 PT

## The substrate name (GOS) and the architecture name (CorpOS)

**Filed:** 042426 F Week Pass 2 Day 6 · ~17:45 PT · Bridge canon mirror by ODT-Trip (Opus 4.7)
**Source canon:** Dan-direct 042426 14:35 PT chat to ACHEdex-Trip · "GOS" + "CorpOS" named in same turn
**Surfacing crew:** ACHEdex-Trip (Graft `19dc197d8fe3ebca` filed 042426 ~15:00 PT)
**Filing crew:** ODT-Trip (Bridge mirror — BM-19 of session bookmark series)
**Sibling canon:** `RELAY/CANONICAL_GOSt_NamingCanon_Dan_042426.md` — the verb form (BM-20, co-filed)
**Filing register:** Dan-canon establishment, filed to Bridge so future-crew booting from Bridge sees the canon at canon-altitude

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

## DAN, VERBATIM (042426 14:35 PT chat)

Dan-direct in same turn established two terms:

- **"GOS"** — the system / substrate / acronym (where Grafts live, how crew share state across sessions)
- **"CorpOS"** — the body / whole / system-name (play on "corpus" — the body of work)

Captured in ACHEdex-Trip Graft G8 `19dc197d8fe3ebca` filed ~25 minutes after Dan's chat, with full canon framing.

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

## THE TWO TERMS

### GOS

The system / substrate / acronym layer.

- Where Grafts live (Gmail drafts as the substrate)
- The shared distributed memory across crew + sessions
- Pronounced "goss" (single-syllable noun); resolved retroactively via GOSt sibling canon
- "GraftOS" was the longform precursor; GOS is the canon shorthand going-forward
- All filing-prefix discipline (per `CANONICAL_GraftOSLabels_042326.md`) operates over GOS

### CorpOS

The body / whole / system-name layer.

- Pun on "corpus" (the body of work) and "Corp" (incorporated body)
- The architecture of which GOS is one substrate
- Larger noun than GOS — names the whole, not just the storage layer
- Includes GOS, the Bridge canon, the portal, the fleet, the crew, the discipline practice

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

## THE THREE-TERM FAMILY (completed in same session via sibling canon BM-20)

| Term | Shape | Voice | Origin |
|---|---|---|---|
| **GOS** | the system / substrate / acronym | noun | Dan 042426 14:35 PT (this canon) |
| **GOSt** | the act of extracting raw → durable | **verb** | Dan 042426 ~16:38 PT (sibling BM-20) |
| **CorpOS** | the body / whole / system-name | noun (larger) | Dan 042426 14:35 PT (this canon) |

The motion between them:

```
RAW LAYER         →   GOSt        →   GOS         →   CorpOS
(working memory       (the verb /     (the substrate   (the whole
chat · research)      the act)        / acronym)       body / system)
volatile              motion          durable          architecture
```

GOSt is the door from raw → durable. GOS is the substrate where GOSt lands material. CorpOS is the body GOS contributes to.

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

## REFINING-NOT-REBUILDING

GOS / CorpOS are not new mechanisms. The substrate-of-Gmail-drafts has been operational since 042326 (and earlier under the "GraftOS" longform). The names refine usage that was already canon. **Same substrate; expressed more cleanly.**

This is the same Refining-not-Rebuilding pattern Dan named to ACHEdex-Trip 042426 14:24 PT in same session ("we are refining what is here, not rebuilding from scratch"). Naming-what-already-lives at the linguistic altitude.

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

## CROSS-REFERENCES

**Sibling canon (co-filed):**
- `RELAY/CANONICAL_GOSt_NamingCanon_Dan_042426.md` — the verb form (BM-20)

**Today's GOSt chain (terminology lineage):**
- ACHEdex G5 (042426 14:25 PT) — GraftOS-as-verb pattern named (parent of GOSt verb)
- ACHEdex G7 (042426 ~14:50 PT) — GOS terminology applied
- ACHEdex G8 (042426 ~15:00 PT) — GOS/CorpOS naming canon Graft (this canon's source filing)
- ODT-Trip [CANONICAL] GOSt naming (042426 ~16:40 PT, threadId `19dc1dec681f1850`) — sibling verb canon

**Related foundational canons on Bridge:**
- `RELAY/CANONICAL_GraftOSLabels_042326.md` — filing-prefix discipline (operates over GOS)
- `RELAY/CANONICAL_MemoryManagement_Trip_041926.md` — six-layer memory taxonomy (GOS = L5)

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

## THE TEACHING

**Names follow usage. Usage is the canon. Naming makes usage transmissible to future-crew at boot.**

The crew was using "GraftOS" interchangeably for both the substrate AND the act of writing to it. Dan said GOS as the noun-substrate so the verb-form (GOSt) had somewhere clean to live. The naming is what enables the architecture to be **taught**, not what makes the architecture **exist**. The architecture has been operating; the names give it sharable shape.

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

`<4` — ODT-Trip · ODT · 042426 ~17:45 PT · BM-19 Bridge canon mirror filed · sibling BM-20 GOSt canon co-filing next · three-term family complete at canon-altitude · in flow at calm/easy/slow