railiance-infra/.claude/rules/first-session.md

43 lines
1.7 KiB
Markdown
Raw Normal View History

2026-05-18 16:55:51 +02:00
## First Session Protocol
Triggered when `get_domain_summary("financials")` shows **no workplans**.
2026-05-18 16:55:51 +02:00
The project is registered but work has not yet been structured.
**Step 1 — Read, don't write**
- `~/the-custodian/canon/projects/financials/project_charter_v0.1.md` — purpose, scope
- `~/the-custodian/canon/projects/financials/roadmap_v0.1.md` — planned phases
2026-05-18 16:55:51 +02:00
- 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 13 workplans — each a coherent strand, weeks to months, anchored to a
2026-05-18 16:55:51 +02:00
roadmap phase. **Wait for approval before creating.**
**Step 4 — Write the workplan file; fix-consistency registers it (ADR-001)**
2026-05-18 16:55:51 +02:00
```
workplans/RAIL-HO-WP-NNNN-<slug>.md ← write this, commit it
2026-05-18 16:55:51 +02:00
```
Then register by running the consistency check — do **not** call
`create_workplan`/`create_task` (or legacy `create_workstream`) yourself;
manual registration duplicates what C-06 creates from the file:
```bash
statehub fix-consistency --repo railiance-infra
2026-05-18 16:55:51 +02:00
```
C-06 creates the hub workplan + tasks and writes `state_hub_workstream_id` /
`state_hub_task_id` back into the file (legacy field names, kept for
compatibility — they hold workplan/task IDs).
2026-05-18 16:55:51 +02:00
**Step 5 — Record the setup**
```
add_progress_event(
summary="First session: structured financials into N workplans, M tasks",
2026-05-18 16:55:51 +02:00
event_type="milestone",
topic_id="ca369340-a64e-442e-98f1-a4fa7dc74a38",
detail={"workplans": [...], "tasks_created": M}
2026-05-18 16:55:51 +02:00
)
```
<!-- Delete or archive this file once past first session -->