tegwick
9370348d54
statehub register + repo-seed template scaffold (CLAUDE.md, .claude/rules/, registry/). INTENT.md and SCOPE.md rewritten from the generated stub to match net-kingdom's ratified tenant-engine-boundary-contract_v0.1.md (Purpose, Responsibility Boundary, Non-Goals). topic_slug corrected from the auto-assigned custodian default to netkingdom, matching key-cape and user-engine. TEN-WP-0001 (bootstrap) complete: files reviewed/refined, stack decided (Python 3.12 + FastAPI, matching qonto-assistant's convention), first real workplan seeded. TEN-WP-0002 drafted: service skeleton, domain model (tenant/grouping/ capability-role/plan-grant), storage layer, and the three boundary-contract API surfaces (cache-read for key-cape, live-lookup for flex-auth with an explicit fail-closed requirement, write API behind a WriteAuthorizer seam since real flex-auth integration is a declared non-goal for this pass). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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/REPO-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 repo-seed
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}
)