tegwick
c7002cfcea
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
1.7 KiB
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 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; Repo Manager projects it (ADR-001)
workplans/COMMERCE-WP-NNNN-<slug>.md ← write this, commit it
Then run the deterministic, forge-derived sync — do not call
create_workplan/create_task yourself:
uv run --project ~/repo-manager rmgr sync --path . --push
Repo Manager writes deterministic state_hub_workstream_id and
state_hub_task_id values, pushes the file, verifies primary/railliance01,
and asks central to derive that exact Forgejo commit. If connectivity is down,
the queued receipt is pending evidence; rerun the same command later.
Step 5 — Record the setup
add_progress_event(
summary="First session: structured financials into N workplans, M tasks",
event_type="milestone",
topic_id="fe2aaa78-9c20-4feb-b3d2-4fe0529572a3",
detail={"workplans": [...], "tasks_created": M}
)