railiance-platform/.claude/rules/first-session.md
codex 105a34784b
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
docs: add scoped registrar recovery guidance
2026-08-21 21:38:35 +02:00

1.9 KiB
Raw Blame History

First Session Protocol

Triggered when get_domain_summary("financials") shows no workplans. 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
  • 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 roadmap phase. Wait for approval before creating.

Step 4 — Write the workplan file; fix-consistency registers it (ADR-001)

workplans/RPF-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:

statehub fix-consistency --repo railiance-platform

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.

If C-06/C-11 is skipped on a non-registrar host, commit and push the workplan, then run uv run --project ~/repo-manager rmgr registrar-reconcile --path . --confirm-primary --push once. Never export registrar authority directly or create hub rows by hand.

Step 5 — Record the setup

add_progress_event(
    summary="First session: structured financials into N workplans, M tasks",
    event_type="milestone",
    topic_id="ca369340-a64e-442e-98f1-a4fa7dc74a38",
    detail={"workplans": [...], "tasks_created": M}
)