2026-05-18 16:55:53 +02:00
# State Hub — Agent Instructions
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
## Repo Identity
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
**Purpose:** Standalone State Hub service repository extracted from the-custodian/state-hub. Owns the FastAPI API, MCP server, dashboard, migrations, consistency tooling, and operational docs.
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
**Domain:** custodian
**Repo slug:** state-hub
**Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a`
**Workplan prefix:** `STATE-WP-`
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
---
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
## State Hub Integration
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
The Custodian State Hub tracks work across all domains. Interact via HTTP REST —
there is no MCP server for Codex agents.
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
| Context | URL |
|---------|-----|
| Local workstation | `http://127.0.0.1:8000` |
| Remote via tunnel | `http://127.0.0.1:18000` |
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
### Orient at session start
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
```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=cee7bedf-2b48-46ef-8601-006474f2ad7a& status=active" \
| python3 -m json.tool
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
# Check inbox
curl -s "http://127.0.0.1:8000/messages/?to_agent=state-hub& unread_only=true" \
| python3 -m json.tool
```
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
Mark a message read:
```bash
curl -s -X PATCH "http://127.0.0.1:8000/messages/< id > /read" \
-H "Content-Type: application/json" -d '{}'
```
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
### Log progress (required at session close)
2026-05-17 18:54:57 +02:00
```bash
2026-05-18 16:55:53 +02:00
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 > "
}'
2026-05-17 18:54:57 +02:00
```
2026-05-18 16:55:53 +02:00
Omit `workstream_id` / `task_id` when not applicable.
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
### Update task status
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
```bash
curl -s -X PATCH "http://127.0.0.1:8000/tasks/< task_id > " \
-H "Content-Type: application/json" \
2026-05-26 01:32:50 +02:00
-d '{"status": "progress"}'
# values: wait | todo | progress | done | cancel
2026-05-18 16:55:53 +02:00
```
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
### 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"}'
2026-05-17 18:54:57 +02:00
```
2026-05-18 16:55:53 +02:00
---
## Session Protocol
**Start:**
1. `cat .custodian-brief.md` — domain goal and open workstreams (offline-safe)
2. Check inbox: `GET /messages/?to_agent=state-hub&unread_only=true` ; mark read
3. Scan workplans: `ls workplans/` — note `status: ready` , `active` , or `blocked` files and open tasks
2026-05-26 01:32:50 +02:00
4. Check human-needed tasks: `GET /tasks/?needs_human=true`
2026-05-18 16:55:53 +02:00
**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=state-hub
```
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/STATE-WP-NNNN-<slug>.md`
**Archived location:** finished workplans may move to
`workplans/archived/YYMMDD-STATE-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: STATE-WP-NNNN
type: workplan
title: "..."
domain: custodian
repo: state-hub
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: STATE-WP-NNNN-T01
2026-05-26 01:32:50 +02:00
status: wait | todo | progress | done | cancel
2026-05-18 16:55:53 +02:00
priority: high | medium | low
state_hub_task_id: "< uuid > " # written by fix-consistency — do not edit
` ` `
Task description text.
```
2026-05-17 18:54:57 +02:00
2026-05-26 01:32:50 +02:00
Status progression: `todo` → `progress` → `done` ; use `wait` for waiting/blocked work and `cancel` for stopped work.
2026-05-17 18:54:57 +02:00
2026-05-18 16:55:53 +02:00
To create a new workplan:
1. Write the file following the format above
2. Notify the custodian operator to run `make fix-consistency REPO=state-hub`
(or send a message to the hub agent via `POST /messages/` )