tegwick
97d0739537
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.
3 KiB
DEC-FDA-001 — Forward-deployed agency working defaults
Status: accepted — elevated into ADR-007 Date: 2026-07-16 Workplan: KAIZEN-WP-0009-T02 / T11 Deciders: kaizen-agentic (implementation default for Phase 1 pilot)
Context
Architecture open questions blocked Phase 1 scaffolding. We lock working defaults so host-operator @ railiance01 can proceed without waiting on a separate product decision cycle. Overrides are welcome; change this DEC and bump architecture/business model versions.
Decisions
D1 — Kai ledger home
Decision: Phase 1 uses a file-based JSONL ledger at
engagements/.../commercial/ledger.jsonl (schema in architecture §10).
No State Hub extension and no finance-system integration in Phase 1.
Rationale: Offline, reviewable, zero new infrastructure; enough to prove unit economics before EUR.
D2 — Engagement store placement
Decision:
| Artifact | Location |
|---|---|
| Role packages (supplier IP) | kaizen-agentic/roles/<role-id>/ |
| Pilot engagement tree | kaizen-agentic/engagements/pilots/<engagement-id>/ |
| Future production client vaults | Client-owned repo (e.g. railiance-hosts or dedicated ops-engagements); pilot may be copied out later |
Rationale: Keep Phase 1 self-contained in the supplier repo for iteration. Client-owned vault remains the confidentiality rule; pilot path is scaffolding, not a claim of ownership of operational knowledge.
D3 — Multi-target binding
Decision: One Engagement, N Targets. One bound agent definition;
baselines and findings are per-target under vault/baselines/<target-id>.md.
Pilot has N=1 (railiance01).
D4 — Metrics sharing with supplier optimizer
Decision: Opt-in, default off. Pilot does not publish vault content or
raw metrics to supplier optimizer. Local .kaizen/metrics or engagement
reports/ only. Shared aggregates require contribute_metrics: approved on
the engagement record (not set for pilot).
D5 — Craft base for host-operator
Decision: base_agent: sys-medic. Bound definition may start as sys-medic
prompt + engagement binding appendix; Role package owns charter, protocols, and
memory template.
D6 — Privilege policy
Decision: privileged_ops, package upgrade, firewall change, and reboot
require recorded human approval in the vault session log before execution.
Observe-class work does not.
Consequences
- Phase 1 pilot proceeds under
engagements/pilots/eng-coulomb-railiance01-ho-001/ - Architecture and business model docs promote to v0.2 (working accepted)
- ADR-007 may later elevate these defaults to fleet convention (T11)
Elevation
T11 promoted these defaults into ADR-007. Amend ADR-007 for future changes.