tegwick
8bdefcd6ba
- Align agent files with on-disk workplan prefixes (infer from workplan ids) - Set workplan domain to registered domain_slug; add topic_slug where applicable - Repair frontmatter delimiter formatting; migrate legacy task status literals - Regenerate AGENTS.md, CLAUDE.md, and .claude/rules from State Hub templates
2.2 KiB
id, type, title, domain, status, owner, topic_slug, state_hub_workstream_id, created, updated
| id | type | title | domain | status | owner | topic_slug | state_hub_workstream_id | created | updated |
|---|---|---|---|---|---|---|---|---|---|
| CUST-WP-0001 | workplan | Custodian Agent Runtime — Bootstrap | infotech | done | custodian | custodian | a2d9919d-62ec-49e7-9533-ba650757e70a | 2026-02-25 | 2026-03-12 |
Custodian Agent Runtime — Bootstrap
Summary
Design and bootstrap the Custodian as an acting agent: a standalone LLM-powered service that uses the State Hub as its coordination layer. Distinct from the State Hub tooling itself.
Context
The State Hub provides the read model and MCP interface. The Agent Runtime is a separate concern: the loop, policy engine, and tool adapters that make the Custodian an autonomous (or semi-autonomous) participant rather than a passive data store.
Dependencies
Both dependencies resolved and removed from the dependency graph (2026-03-11):
markitect/llm-shared-library(llm-connect)railiance/phase-0-operational-baseline
This workstream is unblocked. T2 is ready to execute.
Tasks
T1 — Bootstrap blocked: awaiting markitect/llm-shared-library
id: CUST-WP-0001-T01
state_hub_task_id: ac42e548-10bf-4851-94e2-c8d35876f2f9
status: done
priority: high
All implementation tasks for the agent runtime were blocked until llm-connect was extracted as a standalone installable package from markitect. Resolved 2026-02-27: llm-connect integrated in state-hub as editable dependency; markitect llm-check smoke test green.
T2 — Define agent architecture and capability scope
id: CUST-WP-0001-T02
state_hub_task_id: 9a9297cd-bd3c-409c-8384-6f06cfc6faa2
status: done
priority: medium
Decide the Custodian agent's primary loop: what is the core OODA cycle?
What tools does it need beyond the State Hub MCP? Where does it live —
new repo or runtime/ in the-custodian? Produce an architecture sketch
covering: entry point, LLM integration (via llm-connect), tool manifest,
state-hub interaction pattern, and deployment target.