Files
the-custodian/workplans/CUST-WP-0001-custodian-agent-runtime.md
tegwick fec05dcb5d docs(workplans): write files for 4 pre-ADR-001 orphan workstreams
Resolves all orphan-workstream FAIL findings from validate_repo_adr.
The custodian domain now passes 47/47 checks (0 warn, 0 fail).

Files written:
  CUST-WP-0001  custodian-agent-runtime (2 tasks: 1 done, 1 todo)
  CUST-WP-0002  contribution-tracking-sbom (15 tasks, v0.5 scope
                reductions annotated inline)
  CUST-WP-0003  whi-kpi-card (9 tasks)
  CUST-WP-0004  ep-td-tracking (10 tasks: 4 done, 6 todo)

All files cross-reference state_hub_workstream_id and
state_hub_task_id for future sync reconciliation.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-28 12:14:47 +01:00

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 custodian active custodian custodian a2d9919d-62ec-49e7-9533-ba650757e70a 2026-02-25 2026-02-28

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

  • Depends on: markitect/llm-shared-library (llm-connect) — must reach stable installable state before implementation can begin. Dependency resolved: llm-connect extracted and integrated (2026-02-27).
  • Depends on: railiance/phase-0-operational-baseline — agent runtime deployment requires a stable, backed-up server environment.
  • state_hub_dep_ids:
    • a46f5838-e489-434f-b7ee-996c2fdd81ad (llm-shared-library)
    • 7f0d9856-9561-4404-96f0-91e8eb79feca (phase-0-operational-baseline)

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: todo
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.