tegwick
c431915d56
Record the published fail-closed PEP stance in SCOPE, fill the agent stack and architecture stubs from the shipped layout, and retire the first-session protocol now that USER-WP-0001–0024 exist. Assistant: grok Assistant-Session: 01a04cea-f0d6-7ab3-9ffd-881eb6bea6cb
1.7 KiB
First Session Protocol
Retired 2026-08-29. Work is structured (USER-WP-0001–0024). Kept as
history; do not run. Active session flow is session-protocol.md.
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/USER-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 user-engine
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="a6c6e745-bf54-4465-9340-1534a2be493e",
detail={"workplans": [...], "tasks_created": M}
)