--- id: KAIZEN-WP-0009 type: workplan title: "Forward-deployed agency: engagements, Kai ledger, host-operator pilot" domain: agents repo: kaizen-agentic status: active owner: kaizen-agentic topic_slug: custodian created: "2026-07-16" updated: "2026-07-16" depends_on: - KAIZEN-WP-0002 - KAIZEN-WP-0006 - KAIZEN-WP-0008 tasks: - id: T01 status: done title: Business model and architecture drafts (Kai + engagement lifecycle) - id: T02 status: done title: Accept or revise open decisions; promote drafts to accepted reference - id: T03 status: done title: Role package scaffold for host-operator (ROLE.yaml + protocols) - id: T04 status: done title: Phase 1 file-based engagement layout and pilot ENGAGEMENT for railiance01 - id: T05 status: done title: Bound agent definition from sys-medic craft + engagement binding appendix - id: T06 status: done title: Ramp-up and ramp-down checklists with exit criteria evidence paths - id: T07 status: done title: JSONL Kai ledger convention and quote snapshot for pilot - id: T08 status: todo title: CLI engagement command group (request, staff, prepare, checklist, scrub) - id: T09 status: todo title: Wire prepare/session-close to vault paths, metrics, and ledger entries - id: T10 status: todo title: Run railiance01 host-operator Phase 1 pilot through ramp-up exit - id: T11 status: todo title: Absorb pilot friction; ADR for engagement convention; docs cross-links state_hub_workstream_id: "70f7afb1-78f1-4e3b-8437-48840b5b58cc" --- # KAIZEN-WP-0009 — Forward-Deployed Agency **Status:** active **Owner:** kaizen-agentic **Repo:** kaizen-agentic **Depends on:** WP-0002 (agency memory), WP-0006 (schedule prepare), WP-0008 (customer engagement) ## Goal Turn kaizen-agentic into an **agentic consulting / forward-deployed agency** capability: clients (coulomb ecosystem companies and coulomb ops itself) can **request a Role**, receive a **bound agent definition**, run engagements with **ramp-up / operate / ramp-down**, keep **operational knowledge client-confidential**, and settle trial costs in **Kai** (transitionable to EUR later). First concrete pilot: **host-operator** Role attending **railiance01** (OS currency, security posture, load and workload review). ## Background Specs already drafted: | Doc | Purpose | |-----|---------| | [wiki/ForwardDeployedAgencyBusinessModel.md](../wiki/ForwardDeployedAgencyBusinessModel.md) | Seats, duties, Kai, confidentiality, conversion | | [docs/forward-deployed-engagement-architecture.md](../docs/forward-deployed-engagement-architecture.md) | Lifecycle, schemas, vault, CLI, pilot runbook | Existing building blocks: agency memory (ADR-002), protocols (ADR-003), schedule prepare (ADR-005), customer engagement convention (ADR-006), `sys-medic` craft. ## Engagement model (supplier view) ``` Client request → quote (Kai) → fund → staff Role → ramp-up → operate → ramp-down │ ├─ bound agent definition (client engagement store) ├─ engagement vault (CLIENT OWNED) └─ ledger entries (billing metadata only) ``` ## Tasks ## Business model and architecture drafts ```task id: KAIZEN-WP-0009-T01 status: done priority: high state_hub_task_id: "a9440a09-00fb-4668-94a7-f02ae14031d2" ``` Delivered 2026-07-16: - `wiki/ForwardDeployedAgencyBusinessModel.md` - `docs/forward-deployed-engagement-architecture.md` - Cross-links from PricingModel, RevenueModel, agency-framework ## Accept open decisions ```task id: KAIZEN-WP-0009-T02 status: done priority: high state_hub_task_id: "d624072d-1939-40f0-bfa2-498a24673b4c" ``` **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: done priority: high state_hub_task_id: "407eae88-a3fe-4da9-80eb-ea92828fd488" ``` **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: done priority: high state_hub_task_id: "c90fd780-982f-48ea-a017-2eee44f2e8c7" ``` **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: done priority: high state_hub_task_id: "e48f0ec3-4258-4650-8c92-eb25e4dca755" ``` **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: done priority: medium state_hub_task_id: "3c166660-b4b8-49fc-9dcb-c47e7d676792" ``` **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: done priority: medium state_hub_task_id: "16e90a62-973b-4cc8-ac36-87bfad52e538" ``` **Delivered:** `commercial/quote.yaml` (~72 800 Kai month-1), `ledger.jsonl` with quote-open note, commercial README. ## CLI engagement group ```task id: KAIZEN-WP-0009-T08 status: todo priority: medium state_hub_task_id: "52f7d872-1087-4890-9439-8d6c704351fd" ``` Implement `kaizen-agentic engagement` subcommands (Phase 2 of architecture): `request`, `quote`, `staff`, `render-agent`, `init-vault`, `phase`, `checklist`, `prepare`, `scrub`, `export-handoff` — minimum viable subset for pilot may be `staff`, `checklist`, `prepare`, `phase`. Tests for schema validate and checklist status. ## Session wire-up ```task id: KAIZEN-WP-0009-T09 status: todo priority: medium state_hub_task_id: "82ac0b5a-0309-4912-93bf-f05bee2abbc2" ``` - `engagement prepare` bundles definition + vault + protocols + access plan - Session close path updates vault, `metrics record`, optional Kai duty charge - No secrets in prepare output or ledger ## railiance01 pilot through ramp-up ```task id: KAIZEN-WP-0009-T10 status: todo priority: high state_hub_task_id: "6b21da0d-7ba5-4c64-92cb-9237cf71a102" ``` Execute architecture §11 ramp-up runbook against railiance01 (observe-class access via warden/cert paths). Exit when RU checklist complete and phase `operating`. Privileged changes only with recorded human approval. Evidence: baseline file, first health report, checklist marks, ledger entries. ## Absorb and ADR ```task id: KAIZEN-WP-0009-T11 status: todo priority: low state_hub_task_id: "f212949d-de22-46de-9ae0-63fc21e2701f" ``` - Supplier notes → playbook / architecture v0.2 - ADR-007 (or equivalent) for engagement convention if T02 promotes it - CHANGELOG + wiki links; optional activity-core schedule for daily review ## Out of scope - EUR payment processor / invoicing systems - Autonomous root without human gates - Replacing ops-warden, OpenBao, activity-core, or State Hub - Public Kai cryptocurrency - Fleet-wide host-operator rollout beyond railiance01 pilot ## Success criteria 1. Specs accepted (T02) and committed as team reference 2. Pilot engagement files exist with bound definition and client vault 3. Ramp-up exit criteria met once on railiance01 with evidence 4. Kai ledger records seat/ramp/duty without confidential payloads 5. No client vault content merged into supplier `agents/` without scrub + license 6. CLI or documented manual procedure can re-run prepare/checklist ## Related - [ForwardDeployedAgencyBusinessModel.md](../wiki/ForwardDeployedAgencyBusinessModel.md) - [forward-deployed-engagement-architecture.md](../docs/forward-deployed-engagement-architecture.md) - [ADR-006](../docs/adr/ADR-006-customer-engagement-convention.md) - [agent-sys-medic.md](../agents/agent-sys-medic.md) - [KAIZEN-WP-0008](kaizen-agentic-WP-0008-coulomb-loop-supplier-engagement.md)