tegwick
897c62caef
The .claude/rules/ files still carried the seed placeholders. The practical failure: session-protocol.md told agents to check the inbox with to_agent="repo-seed", which returns [] regardless. Three unread messages from gate-house and risk-nexus sat unread for days behind that wrong query until fix-consistency's C-28 surfaced them. Replaced repo-seed with tenant-engine throughout, and REPO-WP- with this repo's actual TEN-WP- prefix. Also records that no MCP server is registered (dev-hub was deregistered 2026-09-04), so the REST paths are the default rather than the fallback, and fixes the root CLAUDE.md heading, still "Repo Seed". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HHwvAEQfmzLHtrFGhXtVjq Assistant: claude-code Assistant-Model: opus Assistant-Process: 823014@bnt-lap001 Assistant-Session: 2a0786b1-efea-4c38-959b-6e86a493f259
1.6 KiB
First Session Protocol
Triggered when get_domain_summary("infotech") shows no workplans.
The project is registered but work has not yet been structured.
Step 1 — Read, don't write
~/the-custodian/canon/projects/infotech/project_charter_v0.1.md— purpose, scope~/the-custodian/canon/projects/infotech/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/TEN-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 tenant-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 infotech into N workplans, M tasks",
event_type="milestone",
topic_id="cee7bedf-2b48-46ef-8601-006474f2ad7a",
detail={"workplans": [...], "tasks_created": M}
)