## First Session Protocol

Triggered when `get_domain_summary("communication")` shows **no workplans**.
The project is registered but work has not yet been structured.

**Step 1 — Read, don't write**
- `~/the-custodian/canon/projects/communication/project_charter_v0.1.md` — purpose, scope
- `~/the-custodian/canon/projects/communication/roadmap_v0.1.md` — planned phases
- Scan repo root: README, directory structure, existing code or docs

**Step 2 — Survey in-progress work**
Look for TODOs, open branches, half-finished files. Note done vs. started but incomplete.

**Step 3 — Propose workplans to Bernd**
Propose 1–3 workplans — each a coherent strand, weeks to months, anchored to a
roadmap phase. **Wait for approval before creating.**

**Step 4 — Write the workplan file; fix-consistency registers it (ADR-001)**
```
workplans/BINECT-CHROME-WP-NNNN-<slug>.md   ← write this, commit it
```
Then register by running the consistency check — do **not** call
`create_workplan`/`create_task` yourself; manual registration duplicates what
C-06 creates from the file:
```bash
statehub fix-consistency --repo binect-chrome
```
C-06 creates the hub workplan + tasks and writes `state_hub_workstream_id`
(legacy frontmatter name — holds the workplan UUID) and `state_hub_task_id`
back into the file.

**Step 5 — Record the setup**
```
add_progress_event(
    summary="First session: structured communication into N workplans, M tasks",
    event_type="milestone",
    topic_id="36c7421b-c537-4723-bf75-42a3ebc6a1dc",
    detail={"workplans": [...], "tasks_created": M}
)
```

<!-- Delete or archive this file once past first session -->
