# GRAIN — Altitude stack for SEE, R
**Updated:** 2026-09-09 · **Public-safe** · Kennesaw, GA  
**Owner:** Contingency / CoS

Grain = how finely we slice work and memory. Agents and models must name the grain they are operating at. Mixing grains causes silent rewrites, invented poetry, and “who said what” loss.

---

## The five grains

### Macro
**What:** Naming, thesis, public/private membrane, portfolio job of the site.  
**Where it lives:** `LOCKS.md`, `PROJECT_NAMING_FRAME.md`, `PUBLIC_PRIVATE_WEB.md`, `HUB_STRUCTURE.md`, `agents/MASTER_PLAN.md`.  
**Rules:** Change only with Ryan affirmation or explicit CoS lock note. Do not invent alternate brand strings.

### Process
**What:** How CoS + agents respond to Ryan.  
**Includes:**
- Batched questions (ADD-friendly — never drip one-at-a-time traps)
- Settled MD → Content Writer copy → Garden Design HTML → Ryan spot-check → CoS push
- Safety gates (Gmail / Monitor / personal / Drive)
- **Supersede, not silent rewrite** when locks change
**Where it lives:** `CONTENT_PIPELINE.md`, `HANDOFF_ANY_MODEL.md`, agent handoffs, Safety `PULL_GATE.md`.

### Beat
**What:** Dated public thinking: **what / why / moved / mystery**.  
**Where it lives:** Seer Chronicle (`/workspace/see-r/seer-chronicle/`, public `/chronicle/`).  
**Rules:** Ryan-dated stamps → synthesize. No auto-ingest Gmail. Woods beat superseded by attention-practice correction.

### Response *(this tracker’s grain)*
**What:** How an agent (or swarm) answered a specific Ryan thought / ask.  
**Shape:** stimulus (Ryan) → action (agents) → artifact path → status.  
**Where it lives:** **`PROCESS_LOG.md`** in this folder (and the public HTML rendering).  
**Distinct from Beat:** Chronicle is the thinking trail. Response is the *operational answer* to Ryan — what we did, who did it, where the files are, whether it shipped.

### Seed
**What:** Idea Garden maturity — Seed → Sapling → Fruit.  
**Where it lives:** Idea Garden (`/workspace/see-r/idea-garden/`, public `/garden/`).  
**Rules:** Nursery ≠ Chronicle. Fruit earns a URL; paid/private stay back. Safety veto on unsafe graduates.

---

## How they relate

```
Macro     →  what must stay true (locks / membrane / thesis)
Process   →  how the org moves (pipeline / Safety / supersede)
Beat      →  Chronicle: how thinking moved (public trail)
Response  →  AI Tracker: how we answered Ryan (ops trail)
Seed      →  Garden: idea maturity (nursery)
```

**AI Tracker records Response grain only.**  
Do not dump Chronicle beats or Garden seeds into `PROCESS_LOG` unless the Response *was* “we wrote that beat / planted that seed” — then cite the artifact path and keep the Chronicle/Garden file as source of truth for Beat/Seed content.

---

## Status vocabulary (Response)

| Status | Meaning |
|---|---|
| `live` | On public Pages (or affirmed live) |
| `local` | Built under `redesign/site/` (or workspace) — not pushed / not live yet |
| `held` | Intentionally paused (Safety, Ryan skip, budget) |
| `superseded` | Replaced by a later Response; leave the old entry readable |