feat: Phase 1 FDA host-operator Role and railiance01 pilot (WP-0009 T02–T07)
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
ci / test (push) Failing after 9s

Lock DEC-FDA-001 working defaults; add roles/host-operator package with
OS/security and load protocols; scaffold eng-coulomb-railiance01-ho-001
with bound agent, vault, ramp checklists, and Kai quote/ledger.
This commit is contained in:
tegwick 2026-07-16 10:47:52 +02:00
parent ca7e4ead77
commit 2d347d062f
31 changed files with 1171 additions and 58 deletions

View file

@ -4,7 +4,7 @@ type: workplan
title: "Forward-deployed agency: engagements, Kai ledger, host-operator pilot"
domain: agents
repo: kaizen-agentic
status: ready
status: active
owner: kaizen-agentic
topic_slug: custodian
created: "2026-07-16"
@ -18,22 +18,22 @@ tasks:
status: done
title: Business model and architecture drafts (Kai + engagement lifecycle)
- id: T02
status: todo
status: done
title: Accept or revise open decisions; promote drafts to accepted reference
- id: T03
status: todo
status: done
title: Role package scaffold for host-operator (ROLE.yaml + protocols)
- id: T04
status: todo
status: done
title: Phase 1 file-based engagement layout and pilot ENGAGEMENT for railiance01
- id: T05
status: todo
status: done
title: Bound agent definition from sys-medic craft + engagement binding appendix
- id: T06
status: todo
status: done
title: Ramp-up and ramp-down checklists with exit criteria evidence paths
- id: T07
status: todo
status: done
title: JSONL Kai ledger convention and quote snapshot for pilot
- id: T08
status: todo
@ -52,7 +52,7 @@ state_hub_workstream_id: "70f7afb1-78f1-4e3b-8437-48840b5b58cc"
# KAIZEN-WP-0009 — Forward-Deployed Agency
**Status:** ready
**Status:** active
**Owner:** kaizen-agentic
**Repo:** kaizen-agentic
**Depends on:** WP-0002 (agency memory), WP-0006 (schedule prepare), WP-0008 (customer engagement)
@ -111,91 +111,76 @@ Delivered 2026-07-16:
```task
id: KAIZEN-WP-0009-T02
status: todo
status: done
priority: high
state_hub_task_id: "d624072d-1939-40f0-bfa2-498a24673b4c"
```
Resolve architecture open questions with sponsor:
1. Kai ledger home (file JSONL vs hub extension)
2. Engagement store placement (dedicated repo vs railiance-hosts subdirectory)
3. Multi-target agent binding shape
4. Default metrics opt-in for supplier optimizer
Update both draft docs to `accepted` / v0.2 when decided. Optionally promote
architecture sections into ADR-007.
**Delivered 2026-07-16 (working defaults):**
[DEC-FDA-001](../docs/decisions/DEC-FDA-001-working-defaults.md) — JSONL ledger,
`engagements/pilots/` placement, one engagement × N targets, metrics opt-in off.
Docs promoted to v0.2. Sponsor may override; ADR-007 deferred to T11.
## host-operator Role package
```task
id: KAIZEN-WP-0009-T03
status: todo
status: done
priority: high
state_hub_task_id: "407eae88-a3fe-4da9-80eb-ea92828fd488"
```
Add supplier Role scaffold per architecture §5.1:
- `roles/host-operator/ROLE.yaml` (or agreed package path)
- Protocols: `os-security-pass`, `load-workload-review` (plus reuse sys-medic k3s)
- Memory template extensions (host profiles, OS/patch, security, load envelope)
- Capability tier 4; base_agent: sys-medic
**Delivered:** `roles/host-operator/` — ROLE.yaml v0.1.0, agent-definition,
memory-template, ramp-up/down, protocols `os-security-pass` + `load-workload-review`,
base_agent sys-medic, tier 4.
## Phase 1 engagement layout + pilot record
```task
id: KAIZEN-WP-0009-T04
status: todo
status: done
priority: high
state_hub_task_id: "c90fd780-982f-48ea-a017-2eee44f2e8c7"
```
Create file-based engagement tree for pilot (location per T02 decision), including:
- `ENGAGEMENT.yaml` for `eng-coulomb-railiance01-ho-001`
- Request YAML, schedule.yml, access-plan.md (no secrets)
- Empty vault scaffold
Document the path in architecture §11 if it differs from the draft proposal.
**Delivered:** `engagements/pilots/eng-coulomb-railiance01-ho-001/` full tree
(ENGAGEMENT, request, schedule, access-plan, vault, checklists, commercial, reports).
## Bound agent definition
```task
id: KAIZEN-WP-0009-T05
status: todo
status: done
priority: high
state_hub_task_id: "e48f0ec3-4258-4650-8c92-eb25e4dca755"
```
Materialise engagement-bound agent definition from sys-medic + binding appendix
(targets, phase, human_approval_for, vault paths, charter). Until Role package
ships, sys-medic + appendix is acceptable; migrate to host-operator when T03 lands.
**Delivered:** `agent-host-operator.md` bound definition (targets, phase,
approval gates, vault path, charter, protocol table).
## Ramp checklists
```task
id: KAIZEN-WP-0009-T06
status: todo
status: done
priority: medium
state_hub_task_id: "3c166660-b4b8-49fc-9dcb-c47e7d676792"
```
Author ramp-up (RU-01…RU-08) and ramp-down (RD-01…RD-07) checklists with
evidence paths matching architecture §7. Link from ENGAGEMENT.yaml.
**Delivered:** Role checklists + pilot `checklists/ramp-up-status.md` and
`ramp-down-status.md` with evidence paths; linked from ENGAGEMENT.yaml.
## Kai ledger (Phase 1)
```task
id: KAIZEN-WP-0009-T07
status: todo
status: done
priority: medium
state_hub_task_id: "16e90a62-973b-4cc8-ac36-87bfad52e538"
```
- `commercial/ledger.jsonl` schema per architecture §10
- Quote snapshot for pilot month-1 seat + ramp + estimated duties
- Document mint/spend against internal coulomb grant (no real EUR required)
**Delivered:** `commercial/quote.yaml` (~72800 Kai month-1), `ledger.jsonl`
with quote-open note, commercial README.
## CLI engagement group