coulomb/kaizen-agentic
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
ci / test (push) Failing after 9s
Details

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

29
docs/forward-deployed-engagement-architecture.md
View file

@ -1,10 +1,12 @@
# Forward-Deployed Engagement Architecture
**Status:** draft specification v0.1
**Status:** v0.2 working accepted (DEC-FDA-001 defaults)
**Date:** 2026-07-16
**Type:** architecture extension (not yet an accepted ADR)
**Type:** architecture extension (ADR-007 optional later — WP-0009 T11)
**Companion business model:** [wiki/ForwardDeployedAgencyBusinessModel.md](../wiki/ForwardDeployedAgencyBusinessModel.md)
**Decisions:** [docs/decisions/DEC-FDA-001-working-defaults.md](decisions/DEC-FDA-001-working-defaults.md)
**Extends:** ADR-002 (memory), ADR-003 (protocols), ADR-005 (schedule), ADR-006 (customer engagement)
**Pilot tree:** `engagements/pilots/eng-coulomb-railiance01-ho-001/`
---
@ -681,18 +683,27 @@ kaizen-agentic once pilot checklist passes twice.
## 15. Open technical questions
1. Single monorepo path `engagements/` vs dedicated client engagement repo per company?
(**Recommend:** dedicated client repo or subdirectory in existing ops repo — e.g. railiance-hosts or a new `coulomb-ops-engagements`.)
2. Should bound definitions be signed (supply-chain) for production host ops?
3. Multi-target engagements: one agent definition vs. one per host?
(**Recommend:** one engagement, N targets, N baseline files.)
4. How aggressively to share metrics aggregates with supplier optimizer by default?
(**Recommend:** off until opt-in flag on engagement.)
Resolved for Phase 1 by [DEC-FDA-001](decisions/DEC-FDA-001-working-defaults.md):
| Question | Working default |
|----------|-----------------|
| Engagement store | Pilot under `engagements/pilots/` in kaizen-agentic; production vaults client-owned later |
| Multi-target | One engagement, N targets, N baseline files |
| Metrics to supplier optimizer | Opt-in, default off |
| Kai ledger | File JSONL under engagement `commercial/` |
Still open (non-blocking):
1. Should bound definitions be signed (supply-chain) for production host ops?
2. When to copy pilot vault to a client-owned repo for pure custody?
---
## Related documents
- [DEC-FDA-001](decisions/DEC-FDA-001-working-defaults.md)
- [roles/host-operator](../roles/host-operator/)
- [pilot engagement](../engagements/pilots/eng-coulomb-railiance01-ho-001/)
- [wiki/ForwardDeployedAgencyBusinessModel.md](../wiki/ForwardDeployedAgencyBusinessModel.md)
- [agency-framework.md](agency-framework.md)
- [adr/ADR-006-customer-engagement-convention.md](adr/ADR-006-customer-engagement-convention.md)