coulomb/kaizen-agentic
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kaizen-agentic/workplans/kaizen-agentic-WP-0009-forward-deployed-agency.md
tegwick e0d7b0c3ad
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 54s
Details
docs: forward-deployed agency model, architecture, and WP-0009 
Add Kai trial-currency business model and engagement architecture
(request → bound agent → ramp-up/down, client vault). Register workplan
KAIZEN-WP-0009 for host-operator@railiance01 pilot and CLI/ledger phases.
2026-07-16 10:28:58 +02:00

7.9 KiB
Raw Blame History

id type title domain repo status owner topic_slug created updated depends_on tasks
KAIZEN-WP-0009 workplan Forward-deployed agency: engagements, Kai ledger, host-operator pilot agents kaizen-agentic ready kaizen-agentic custodian 2026-07-16 2026-07-16
KAIZEN-WP-0002
KAIZEN-WP-0006
KAIZEN-WP-0008
id status title
T01 done Business model and architecture drafts (Kai + engagement lifecycle)
id status title
T02 todo Accept or revise open decisions; promote drafts to accepted reference
id status title
T03 todo Role package scaffold for host-operator (ROLE.yaml + protocols)
id status title
T04 todo Phase 1 file-based engagement layout and pilot ENGAGEMENT for railiance01
id status title
T05 todo Bound agent definition from sys-medic craft + engagement binding appendix
id status title
T06 todo Ramp-up and ramp-down checklists with exit criteria evidence paths
id status title
T07 todo JSONL Kai ledger convention and quote snapshot for pilot
id status title
T08 todo CLI engagement command group (request, staff, prepare, checklist, scrub)
id status title
T09 todo Wire prepare/session-close to vault paths, metrics, and ledger entries
id status title
T10 todo Run railiance01 host-operator Phase 1 pilot through ramp-up exit
id status title
T11 todo Absorb pilot friction; ADR for engagement convention; docs cross-links

KAIZEN-WP-0009 — Forward-Deployed Agency

Status: ready 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

Delivered 2026-07-16:

  • wiki/ForwardDeployedAgencyBusinessModel.md
  • docs/forward-deployed-engagement-architecture.md
  • Cross-links from PricingModel, RevenueModel, agency-framework

Accept open decisions

id: KAIZEN-WP-0009-T02
status: todo
priority: high

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.

host-operator Role package

id: KAIZEN-WP-0009-T03
status: todo
priority: high

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

Phase 1 engagement layout + pilot record

id: KAIZEN-WP-0009-T04
status: todo
priority: high

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.

Bound agent definition

id: KAIZEN-WP-0009-T05
status: todo
priority: high

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.

Ramp checklists

id: KAIZEN-WP-0009-T06
status: todo
priority: medium

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.

Kai ledger (Phase 1)

id: KAIZEN-WP-0009-T07
status: todo
priority: medium
  • 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)

CLI engagement group

id: KAIZEN-WP-0009-T08
status: todo
priority: medium

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

id: KAIZEN-WP-0009-T09
status: todo
priority: medium
  • 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

id: KAIZEN-WP-0009-T10
status: todo
priority: high

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

id: KAIZEN-WP-0009-T11
status: todo
priority: low
  • 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