Absorb railiance01 pilot supplier notes into the forward-deployed engagement playbook, accept ADR-007 elevating DEC-FDA-001, promote architecture and business model to v1.0, and mark KAIZEN-WP-0009 finished.
8.4 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | depends_on | tasks | state_hub_workstream_id | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| KAIZEN-WP-0009 | workplan | Forward-deployed agency: engagements, Kai ledger, host-operator pilot | agents | kaizen-agentic | finished | kaizen-agentic | custodian | 2026-07-16 | 2026-07-16 |
|
|
70f7afb1-78f1-4e3b-8437-48840b5b58cc |
KAIZEN-WP-0009 — Forward-Deployed Agency
Status: finished 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 | Seats, duties, Kai, confidentiality, conversion |
| 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
id: KAIZEN-WP-0009-T01
status: done
priority: high
state_hub_task_id: "a9440a09-00fb-4668-94a7-f02ae14031d2"
Delivered 2026-07-16:
wiki/ForwardDeployedAgencyBusinessModel.mddocs/forward-deployed-engagement-architecture.md- Cross-links from PricingModel, RevenueModel, agency-framework
Accept open decisions
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 — 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
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
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
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
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)
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
id: KAIZEN-WP-0009-T08
status: done
priority: medium
state_hub_task_id: "52f7d872-1087-4890-9439-8d6c704351fd"
Delivered: kaizen-agentic engagement CLI group + engagement.py module:
list, show, validate, checklist (+ --mark), phase, prepare,
staff, quote, scrub, export-handoff.
Tests: tests/test_engagement_cli.py. Docs: CLI cheat sheet section.
Session wire-up
id: KAIZEN-WP-0009-T09
status: done
priority: medium
state_hub_task_id: "82ac0b5a-0309-4912-93bf-f05bee2abbc2"
Delivered: engagement close-session wires vault session log, engagement-scoped
metrics (.kaizen/metrics/ under the pilot tree), Kai ledger.jsonl duty charge,
and reports/ stub. Rejects sensitive summaries. prepare session-close section
points at close-session. Tests cover formula, scrub, and CLI.
railiance01 pilot through ramp-up
id: KAIZEN-WP-0009-T10
status: done
priority: high
state_hub_task_id: "6b21da0d-7ba5-4c64-92cb-9237cf71a102"
Delivered 2026-07-16: Live observe on railiance01 via ssh railiance01
(tegwick). RU-01–08 complete; phase operating. Health: Critical memory
pressure (3.8G, no swap), load ≫ 2 cores, k3s API ServiceUnavailable at sample.
Evidence: baselines, health-review, privileged dry-run (RU-08), schedule enabled,
deep_assessment close-session (4900 Kai). No privileged changes applied.
Absorb and ADR
id: KAIZEN-WP-0009-T11
status: done
priority: low
state_hub_task_id: "f212949d-de22-46de-9ae0-63fc21e2701f"
Delivered 2026-07-16: ADR-007 accepted; forward-deployed engagement playbook v1 with railiance01 supplier-notes table; architecture v1.0; business model v1.0; DEC-FDA-001 elevated; CHANGELOG + cross-links. activity-core host schedule left optional (Phase 3) — documented in playbook.
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
- Specs accepted (T02) and committed as team reference
- Pilot engagement files exist with bound definition and client vault
- Ramp-up exit criteria met once on railiance01 with evidence
- Kai ledger records seat/ramp/duty without confidential payloads
- No client vault content merged into supplier
agents/without scrub + license - CLI or documented manual procedure can re-run prepare/checklist
Closure
All tasks T01–T11 done. Workplan finished 2026-07-16.