Refresh agent instruction files

.claude/rules/agents.md

@@ -0,0 +1,20 @@
+## Kaizen Agents
+
+Specialized agent personas available on demand via the state-hub MCP.
+
+**Discover:** `list_kaizen_agents()` — returns all agents with name, description, category
+**Load:** `get_kaizen_agent("tdd-workflow")` — returns full instructions; read and follow them
+
+Common agents:
+
+| Agent | Category | When to use |
+|-------|----------|-------------|
+| `tdd-workflow` | testing | Step-by-step TDD8 workflow for any feature |
+| `code-refactoring` | quality | Code quality analysis and safe refactoring |
+| `test-maintenance` | testing | Diagnose and fix failing tests |
+| `requirements-engineering` | process | Prevent interface/mock mismatches upfront |
+| `keepaTodofile` | process | Maintain TODO.md during work |
+| `project-management` | process | Track status, determine next steps |
+| `datamodel-optimization` | quality | Optimize dataclasses and data structures |
+
+All 17 agents: call `list_kaizen_agents()` for the full list.

.claude/rules/architecture.md

@@ -1,20 +1,8 @@
-# Architecture Notes
+## Architecture
 
-The intended architecture is layered:
+<!-- TODO: Describe the key design decisions and component structure.
+     Key modules, data flows, external integrations, state machines, etc. -->
 
-```text
+## Quick Reference
-markitect-tool     -> syntax layer
-kontextual-engine  -> system/runtime layer
-infospace-bench    -> application layer
-```
 
-The first implementation should establish repo shape before service shape:
+`~/state-hub/mcp_server/TOOLS.md` — MCP tool reference
-
-- `infospaces/` for concrete infospace projects
-- `schemas/` or dependency references for artifact schemas
-- `workflows/` for application-level workflow definitions
-- `reports/` for evaluation and inspection outputs
-- `docs/` for migration and design records
-
-Use direct dependencies on lower-layer projects only where they clarify the
-boundary. Avoid copying infrastructure wholesale from `markitect-main`.

.claude/rules/first-session.md

@@ -0,0 +1,38 @@
+## First Session Protocol
+
+Triggered when `get_domain_summary("markitect")` shows **no workstreams**.
+The project is registered but work has not yet been structured.
+
+**Step 1 — Read, don't write**
+- `~/the-custodian/canon/projects/markitect/project_charter_v0.1.md` — purpose, scope
+- `~/the-custodian/canon/projects/markitect/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 workstreams to Bernd**
+Propose 1–3 workstreams — each a coherent strand, weeks to months, anchored to a
+roadmap phase. **Wait for approval before creating.**
+
+**Step 4 — Create workplan file first, then DB record (ADR-001)**
+```
+workplans/infospace-bench-WP-NNNN-<slug>.md   ← write this first
+```
+Then register in the hub:
+```
+create_workstream(topic_id="5571d954-0d30-4950-980d-7bcaaad8e3e2", title="...", owner="...", description="...")
+create_task(workstream_id="<id>", title="...", priority="high|medium|low")
+```
+
+**Step 5 — Record the setup**
+```
+add_progress_event(
+    summary="First session: structured markitect into N workstreams, M tasks",
+    event_type="milestone",
+    topic_id="5571d954-0d30-4950-980d-7bcaaad8e3e2",
+    detail={"workstreams": [...], "tasks_created": M}
+)
+```
+
+<!-- Delete or archive this file once past first session -->

.claude/rules/repo-boundary.md

@@ -1,19 +1,8 @@
-# Repo Boundary
+## Repo boundary
 
-`infospace-bench` owns application-level infospace usage. It must not absorb
+This repo owns **infospace-bench** only. It does not own:
-lower-layer responsibilities.
 
-Belongs here:
+<!-- TODO: List what belongs in adjacent repos, e.g.:
-
+- SSH key management → railiance-infra/
-- Infospace definitions and examples
+- State hub code     → state-hub/
-- Application workflow definitions
+-->
-- Evaluation and inspection reports
-- Migration notes from `markitect-main`
-- Workplans for applied infospace capabilities
-
-Belongs elsewhere:
-
-- Markdown parsing and structural syntax primitives: `markitect-tool`
-- Runtime persistence and orchestration: `kontextual-engine`
-- LLM provider abstraction: `llm-connect` or equivalent
-- Final production domain artifacts: the relevant domain repo

.claude/rules/repo-identity.md

@@ -1,11 +1,5 @@
-# Repo Identity
+**Purpose:** Application-layer workspace and service for concrete structured knowledge spaces; scoped successor to markitect-main infospace work.
 
-- Project: `infospace-bench`
+**Domain:** markitect
-- Domain: `markitect`
+**Repo slug:** infospace-bench
-- State Hub repo slug: `infospace-bench`
+**Topic ID:** 5571d954-0d30-4950-980d-7bcaaad8e3e2
-- State Hub topic ID: `5571d954-0d30-4950-980d-7bcaaad8e3e2`
-- Purpose: application-layer workspace and service for concrete infospaces.
-
-This repo is a scoped successor to the application-level infospace work in
-`markitect-main`. It should preserve and extend the parts that help create,
-evaluate, inspect, and evolve real knowledge spaces.

.claude/rules/session-protocol.md

@@ -1,8 +1,84 @@
-# Session Protocol
+## Session Protocol
 
-1. Read `SCOPE.md`, `INTENT.md`, and the active workplan before making changes.
+State Hub: http://127.0.0.1:8000
-2. Check `git status --short` and preserve user changes.
+
-3. Use State Hub as the coordination record when available.
+**Step 1 — Orient**
-4. Keep repo artifacts traceable: workplans, docs, configs, metrics, and outputs
+
-   should explain what changed and why.
+Read the offline-safe brief first — it works without a live hub connection:
-5. Prefer narrow, inspectable changes over broad platform work.
+```bash
+cat .custodian-brief.md
+```
+Then call the MCP tool for richer cross-domain context when MCP tools are exposed:
+```
+get_domain_summary("markitect")
+```
+If MCP tools are unavailable in the current agent session, use the REST API:
+```bash
+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="infospace-bench", unread_only=True)
+```
+Mark read with `mark_message_read(message_id)`. Reply or act on coordination
+requests before proceeding.
+
+Without MCP tools:
+```bash
+curl -s "http://127.0.0.1:8000/messages/?to_agent=infospace-bench&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**
+```bash
+ls workplans/
+```
+For each file with `status: ready`, `active`, or `blocked`, note pending
+`todo`/`in_progress` tasks.
+
+**Step 4 — Present brief**
+
+1. **Active workstreams** for `markitect` — title, task counts, blocking decisions
+2. **Pending tasks** from `workplans/` + any `[repo:infospace-bench]` hub tasks
+3. **Goal guidance** — if `goal_guidance` in 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
+4. **Suggested next action** — highest-priority open item
+5. **SBOM status** — flag if `last_sbom_at` is 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="5571d954-0d30-4950-980d-7bcaaad8e3e2", workstream_id="<uuid>")
+```
+Without MCP tools:
+```bash
+curl -s -X POST http://127.0.0.1:8000/progress/ \
+  -H "Content-Type: application/json" \
+  -d '{"topic_id":"5571d954-0d30-4950-980d-7bcaaad8e3e2","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:
+```bash
+git -C <repo_path> pull --ff-only
+cd ~/state-hub && make fix-consistency REPO=infospace-bench
+```
+For repos where implementation runs on a remote machine (e.g. CoulombCore),
+use the combined target which pulls before fixing:
+```bash
+cd ~/state-hub && make fix-consistency-remote REPO=infospace-bench
+```
+**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.

.claude/rules/stack-and-commands.md

@@ -1,26 +1,19 @@
-# Stack And Commands
+## Stack
 
-The implementation stack is not established yet. Until it is, prefer
+<!-- TODO: Fill in language, frameworks, and key dependencies -->
-documentation and small scaffold changes over choosing frameworks prematurely.
+- **Language:**
+- **Key deps:**
 
-The Python package depends on path deps (`markitect-tool`, `artifactstore`)
+## Dev Commands
-that bring heavy runtime dependencies. Use the Makefile to provision a
-local venv before running tests:
 
 ```bash
-make install     # creates ./.venv with all path deps
+# TODO: Fill in the standard commands for this repo
-make test        # full pytest suite (must run via .venv/bin/python)
+
-```
+# Install dependencies
-
+
-Useful commands:
+# Run tests
-
+
-```bash
+# Lint / type check
-git status --short
+
-rg --files
+# Build / package (if applicable)
-```
-
-State Hub registration was completed with:
-
-```bash
-/home/worsch/the-custodian/state-hub/.venv/bin/custodian register-project --domain markitect --path /home/worsch/infospace-bench
 ```

.claude/rules/workplan-convention.md

@@ -1,9 +1,28 @@
-# Workplan Convention
+## Workplan Convention (ADR-001)
 
-- Workplans live in `workplans/`.
+File location: `workplans/infospace-bench-WP-NNNN-<slug>.md`
-- Prefix new workplans with `IB-WP-`.
+ID prefix: `INFOSPACE-WP`
-- Use YAML frontmatter with `id`, `type`, `title`, `domain`, `repo`, `status`,
+
-  `owner`, `topic_slug`, `created`, and `updated`.
+Work items originate as files in this repo **before** being registered in the hub.
-- Include task blocks with stable IDs, status, priority, and optional State Hub
+
-  task IDs.
+Canonical workplan/workstream frontmatter statuses are:
-- Keep workplans tied to this repo's PRD/FRS requirements and State Hub context.
+`proposed`, `ready`, `active`, `blocked`, `backlog`, `finished`, `archived`.
+Use `proposed` for a newly drafted plan, `ready` after review against current
+repo state, and `finished` when implementation is complete. `stalled` and
+`needs_review` are derived health labels, not stored statuses.
+
+Closed workplans may be moved to `workplans/archived/` with a completion-date
+prefix: `YYMMDD-infospace-bench-WP-NNNN-<slug>.md`. The frontmatter id remains
+unchanged; the prefix is only for quick visual reference.
+
+Small opportunistic tasks discovered during another session use **Ad Hoc Tasks**:
+`workplans/ADHOC-YYYY-MM-DD.md`, workstream slug `adhoc-YYYY-MM-DD`, and task ids
+`ADHOC-YYYY-MM-DD-T01`, `T02`, etc. Use adhocs only for low-risk work completed
+directly. Promote anything requiring analysis, design, approval, dependencies, or
+multiple planned phases into a normal workplan.
+
+Ecosystem todos from other agents arrive as `[repo:infospace-bench]` hub tasks —
+visible at session start. Pick one up by creating the workplan file, then registering
+the workstream.
+
+<!-- Ralph Loop rules and HEUREKA sequence: ~/.claude/CLAUDE.md — do not duplicate here -->

AGENTS.md

@@ -0,0 +1,162 @@
+# infospace-bench — Agent Instructions
+
+## Repo Identity
+
+**Purpose:** Application-layer workspace and service for concrete structured knowledge spaces; scoped successor to markitect-main infospace work.
+
+**Domain:** markitect
+**Repo slug:** infospace-bench
+**Topic ID:** `5571d954-0d30-4950-980d-7bcaaad8e3e2`
+**Workplan prefix:** `INFOSPACE-WP-`
+
+---
+
+## State Hub Integration
+
+The Custodian State Hub tracks work across all domains. Interact via HTTP REST —
+there is no MCP server for Codex agents.
+
+| Context | URL |
+|---------|-----|
+| Local workstation | `http://127.0.0.1:8000` |
+| Remote via tunnel | `http://127.0.0.1:18000` |
+
+### Orient at session start
+
+```bash
+# Offline brief — works without hub connection
+cat .custodian-brief.md
+
+# Active workstreams for this domain
+curl -s "http://127.0.0.1:8000/workstreams/?topic_id=5571d954-0d30-4950-980d-7bcaaad8e3e2&status=active" \
+  | python3 -m json.tool
+
+# Check inbox
+curl -s "http://127.0.0.1:8000/messages/?to_agent=infospace-bench&unread_only=true" \
+  | python3 -m json.tool
+```
+
+Mark a message read:
+```bash
+curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
+  -H "Content-Type: application/json" -d '{}'
+```
+
+### Log progress (required at session close)
+
+```bash
+curl -s -X POST http://127.0.0.1:8000/progress/ \
+  -H "Content-Type: application/json" \
+  -d '{
+    "summary": "what was done",
+    "event_type": "note",
+    "author": "codex",
+    "workstream_id": "<uuid>",
+    "task_id": "<uuid>"
+  }'
+```
+
+Omit `workstream_id` / `task_id` when not applicable.
+
+### Update task status
+
+```bash
+curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
+  -H "Content-Type: application/json" \
+  -d '{"status": "in_progress"}'
+# values: todo | in_progress | done | blocked
+```
+
+### Flag a task for human review
+
+```bash
+curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
+  -H "Content-Type: application/json" \
+  -d '{"needs_human": true, "intervention_note": "reason"}'
+```
+
+---
+
+## Session Protocol
+
+**Start:**
+1. `cat .custodian-brief.md` — domain goal and open workstreams (offline-safe)
+2. Check inbox: `GET /messages/?to_agent=infospace-bench&unread_only=true`; mark read
+3. Scan workplans: `ls workplans/` — note `status: ready`, `active`, or `blocked` files and open tasks
+4. Check blocked tasks: `GET /tasks/?needs_human=true`
+
+**During work:**
+- Update task statuses in workplan files as tasks progress
+- Record significant decisions via `POST /decisions/`
+
+**Close:**
+1. Update workplan file task statuses to reflect progress
+2. Log: `POST /progress/` with a summary of what changed
+3. Note for the custodian operator: after workplan file changes, run from
+   `~/state-hub`:
+   ```bash
+   make fix-consistency REPO=infospace-bench
+   ```
+   This syncs task status from files into the hub DB.
+
+---
+
+## Workplan Convention (ADR-001)
+
+Work items originate as files in this repo — not in the hub. The hub is a
+read/cache/index layer that rebuilds from files.
+
+**File location:** `workplans/INFOSPACE-WP-NNNN-<slug>.md`
+
+**Archived location:** finished workplans may move to
+`workplans/archived/YYMMDD-INFOSPACE-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
+the completion/archive date; the frontmatter `id` does not change.
+
+**Ad Hoc Tasks:** small opportunistic fixes discovered during a session use
+`workplans/ADHOC-YYYY-MM-DD.md` with task ids `ADHOC-YYYY-MM-DD-T01`, etc. Use
+this only for low-risk work completed directly; create a normal workplan for
+anything needing analysis, design, approval, dependencies, or multiple phases.
+
+**Frontmatter:**
+
+```yaml
+---
+id: INFOSPACE-WP-NNNN
+type: workplan
+title: "..."
+domain: markitect
+repo: infospace-bench
+status: proposed | ready | active | blocked | backlog | finished | archived
+owner: codex
+topic_slug: ...
+created: "YYYY-MM-DD"
+updated: "YYYY-MM-DD"
+state_hub_workstream_id: "<uuid>"   # written by fix-consistency — do not edit
+---
+```
+
+Use `proposed` for a new draft, `ready` after review against current repo
+state, and `finished` after implementation. `stalled` and `needs_review` are
+derived health labels, not frontmatter statuses.
+
+**Task block format** (one per `##` section):
+
+```
+## Task Title
+
+` ` `task
+id: INFOSPACE-WP-NNNN-T01
+status: todo | in_progress | done | blocked
+priority: high | medium | low
+state_hub_task_id: "<uuid>"         # written by fix-consistency — do not edit
+` ` `
+
+Task description text.
+```
+
+Status progression: `todo` → `in_progress` → `done` (or `blocked`)
+
+To create a new workplan:
+1. Write the file following the format above
+2. Notify the custodian operator to run `make fix-consistency REPO=infospace-bench`
+   (or send a message to the hub agent via `POST /messages/`)

CLAUDE.md

@@ -1,7 +1,11 @@
+# infospace-bench — Claude Code Instructions
+
 @SCOPE.md
 @.claude/rules/repo-identity.md
 @.claude/rules/session-protocol.md
+@.claude/rules/first-session.md
 @.claude/rules/workplan-convention.md
-@.claude/rules/repo-boundary.md
-@.claude/rules/architecture.md
 @.claude/rules/stack-and-commands.md
+@.claude/rules/architecture.md
+@.claude/rules/repo-boundary.md
+@.claude/rules/agents.md