# Planning Chat → CC

**Read first:** [`working-with-sam.md`](./working-with-sam.md) — operating manual. Apply hard rules throughout the session. No padded estimates, no over-caution, no inventing times.

**Last sync:** 2026-05-14 (manual install + interrupt-resume protocol)
**Status:** Auto-discovery enabled. Pipeline Option B (quick-paste) live. GitHub MCP path queued as Option F.

## Current handoff procedure

1. Planning chat writes the CC prompt (text).
2. Sam (or whatever the planning-chat output mechanism is) puts it in one of:
   - `/handoff/quick-paste.html` (Option B — paste form on the substrate; recommended)
   - Paste directly into CC's prompt box (Option E — default fallback)
   - `/handoff-blocks/ai-coordination/planning-to-cc.md` (this file — commit, then CC reads at session start)
3. CC's session-start auto-discovery (`/handoff-blocks/automation-rules.md`, step 1) finds it and executes.

Until GitHub MCP setup happens (Option F, issue #037), Sam still does **one** paste per session — but it's into a quick-paste form or this file, not the CC input window. Marginal but real friction reduction.

## Tasks queued for CC

*(populated by planning chat when relaying a prompt)*

### Task: (none currently queued via this file — most prompts go through `/handoff/quick-paste.html` or direct paste)

## Strategic context CC should re-anchor on (snapshot)

Captured 2026-05-14 night to reset stale context that was here from May 12:

- **Recalibration outcomes (2026-05-13):** Substrate isn't sprawling, it's UNDER-CONNECTED. IA refactor = Sam's #1 priority for next 1–2 weeks. Phase 1 foundations shipped in commit 945cbbb (palette tokens, shared/components scaffolding, substrate map dashboard, thoughts inbox). See `/handoff-blocks/recalibration-decisions-2026-05-13.md` for full context.
- **Issue tracker is canonical:** `/personal/status-tracker/issues.json`. Both AIs read at session start. Scanner procedure in `/handoff-blocks/issue-scanner-procedure.md`.
- **Time discipline:** planning chat does NOT have access to time-of-day. Sam states current time at start of messages where time matters. No more invented timestamps.
- **Weekly recalibration cadence:** Sunday nights. First scheduled Sun May 17 (likely Pittsburgh / driving home).
- **Validation track for `/our/`:** Rain Collective coworker interest is a real product signal. Don't build more features until interpreted (issue #040).
- **Friends meeting June 4:** reframed from brainstorm → founding moment. Folder scaffolded at `/personal/friends-meeting-2026-06-04/`. Content fills over 3 weeks.
- **Pittsburgh medallion production:** tight. Need 4 Pirates + 6 Phillies in ~36 hrs (issue #043).

## Recently committed by CC

- 2026-05-14 night: autonomy mandate session — automation-rules.md, dashboard.html, quick-paste page, issue auto-resolution sweep.
- 2026-05-14 early: recalibration outcomes + IA Phase 1 foundations + handoff endpoints (commit 945cbbb).
- 2026-05-13/14 late: G5 result + Sameshot rebrand + G6 scaffold + clickable teams + audits (commit c3fe018).

## How to write to this file

Planning chat or Sam can commit content under `## Tasks queued for CC`. CC reads at session start and addresses the queue. After processing, CC moves the queued task into `## Recently committed by CC` with the commit hash.

## Convention reminder

Keep this file under ~100 lines. Archive older `Recently committed` entries into `/handoff-blocks/ai-coordination/planning-to-cc-archive.md` if it grows.
