# HANDOFF — Any model (no CoS required)
**Updated:** 2026-09-09 · **Public-safe** · Kennesaw, GA  
**Purpose:** Claude / Kimi / Gemini / Grok / etc. can continue SEE, R work without the live Chief of Staff chat.

---

## 1. Read first (in order)

1. [`00_START_HERE.md`](00_START_HERE.md)
2. [`GRAIN.md`](GRAIN.md)
3. [`LOCKS.md`](LOCKS.md)
4. [`PROCESS_LOG.md`](PROCESS_LOG.md) — newest entries first
5. `/workspace/see-r/agents/MASTER_PLAN.md`
6. `/workspace/see-r/agents/README.md` + the matching `agents/handoffs/<role>.md`
7. `/workspace/see-r/CONTENT_PIPELINE.md` · `PUBLIC_PRIVATE_WEB.md` · `WORKBOARD.md`

If you are Contingency / continuity: also `agents/handoffs/contingency.md`.

---

## 2. What not to invent

- Employer / XiFin / Rutter facts on public surfaces or in this tracker
- Alternate brand strings (use the naming table)
- Nature / spiritual poetry for splash copy
- Woods-as-identity for GROUNDED
- Amp brand names in Adventure **copy** (visual amp OK)
- Payor flex in bio
- “Rooms” language for hub sections
- Pushing to GitHub without Ryan / CoS go
- Printing or echoing `GH_TOKEN` / secrets

---

## 3. How to update PROCESS_LOG

When you complete a Response to Ryan:

```markdown
### YYYY-MM-DD — short title
- **Ryan thought / ask:** …
- **How we responded:** …
- **Agents:** …
- **Artifacts:** paths
- **Status:** live / local / held / superseded
```

- Append at the **top** of `PROCESS_LOG.md`.
- Cite real paths.
- If a lock changed, leave the old entry and mark it `superseded`; add the new Response.
- Mirror highlights into `redesign/site/ai-tracker/` MD copies + HTML cards when shipping public preview.
- Keep public-safe (no employer names).

---

## 4. When to ask Ryan

Batch questions. Ask when:

- A Macro lock would change (naming, thesis, membrane, site job)
- Public unveil of Monitor / private material
- Push to Pages after Ryan previously skipped
- Budget / collab / photo assets (`band.jpg`) needed
- Anything Safety-flagged (mail, Drive, personal)

Do **not** ask one drip question at a time. Do **not** invent answers to fill silence.

---

## 5. Safety veto

- Safety Officer can block public personal data, Gmail pulls, Drive, Chronicle unveil.
- Default: **deny** mail/Drive until cleared. Drive is **frozen**.
- Gmail dual-pull is **held** as of 2026-09-09.
- Novel catalog never on Pages.

If unclear → hold and ask Ryan in a batch, noting Safety concern.

---

## 6. Push rules

1. Build under `/workspace/see-r/redesign/site/`.
2. Ryan spot-check (or explicit CoS go).
3. Push only with go — typically via existing `gh-pages-push` / Pages workflow.
4. **`GH_TOKEN` in box-secrets — never print, never paste into MD, never log.**
5. After push, update PROCESS_LOG status `local` → `live` for that Response.

---

## 7. Pipeline reminder

```
Settled MD → Content Writer → Garden Design HTML → Ryan → push
```

Frontier tokens for decisions + Settled MD. HTML from Settled only. Anti-Attachment applies to agents too — tools serve judgment.

---

## 8. #1 right now (unless Ryan reorders)

**Idea Garden build-out** (local preview exists; push skipped for now).  
Parallel thin: keep Chronicle honest; AI Tracker / Contingency keep this pack current.