tegwick
ccbbc88503
Add the 9-file .claude/rules set (repo-identity, session-protocol, first-session, workplan-convention, stack-and-commands, architecture, repo-boundary, credential-routing, agents), adapted to binect-chrome: slug, agent name, BCHROME-WP- workplan prefix, shared communication topic. stack/architecture/repo-boundary filled with this repo's real content. Rewrite CLAUDE.md to the @-import structure mirroring binect-js (prior prose migrated into the rule files), retaining an inline Kaizen reference. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
3.1 KiB
Session Protocol
Dev Hub (State Hub API): http://127.0.0.1:8000
MCP server name in ~/.claude.json: dev-hub
Step 1 — Orient
Read the offline-safe brief first — it works without a live hub connection:
cat .custodian-brief.md
Then call the MCP tool for richer cross-domain context when MCP tools are exposed:
get_domain_summary("communication")
If MCP tools are unavailable in the current agent session, use the REST API:
curl -s "http://127.0.0.1:8000/state/summary" | python3 -m json.tool
If the hub is offline: cd ~/state-hub && make api
Step 2 — Check inbox With MCP tools:
get_messages(to_agent="binect-chrome", unread_only=True)
Mark read with mark_message_read(message_id). Reply or act on coordination
requests before proceeding.
Without MCP tools:
curl -s "http://127.0.0.1:8000/messages/?to_agent=binect-chrome&unread_only=true" \
| python3 -m json.tool
curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
-H "Content-Type: application/json" -d '{}'
Step 3 — Scan workplans
ls workplans/
For each file with status: ready, active, or blocked, note pending
wait/todo/progress tasks.
Step 4 — Present brief
- Active workstreams for
communication— title, task counts, blocking decisions - Pending tasks from
workplans/+ any[repo:binect-chrome]hub tasks - Goal guidance — if
goal_guidancein summary:needs_workplan: surface as top action — "Repo goal '{title}' has no workplan yet"alignment_warnings: flag if active work is not aligned with current goal
- Suggested next action — highest-priority open item
- SBOM status — flag if
last_sbom_atis unset for this repo
If no workstreams: follow First Session Protocol (first-session.md).
During work: record_decision() · add_progress_event() · resolve_decision()
State Hub is a read model. Bootstrap tools (
create_workstream,create_task) are First Session Protocol only. Work structure belongs in repo files (ADR-001).
Session close: With MCP tools:
add_progress_event(summary="...", topic_id="36c7421b-c537-4723-bf75-42a3ebc6a1dc", workstream_id="<uuid>")
Without MCP tools:
curl -s -X POST http://127.0.0.1:8000/progress/ \
-H "Content-Type: application/json" \
-d '{"topic_id":"36c7421b-c537-4723-bf75-42a3ebc6a1dc","workstream_id":"<uuid>","event_type":"note","summary":"what changed","author":"codex"}'
If workplan files were modified, ensure the local copy is up to date first:
git -C <repo_path> pull --ff-only
cd ~/state-hub && make fix-consistency REPO=binect-chrome
For repos where implementation runs on a remote machine (e.g. CoulombCore), use the combined target which pulls before fixing:
cd ~/state-hub && make fix-consistency-remote REPO=binect-chrome
C-15 (DB task ahead of file) is normal in multi-machine workflows — writeback will sync the file to match DB. C-16 (repo behind remote) blocks all writes until you pull — intentional to prevent clobbering remote progress.