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

docs: forward-deployed agency model, architecture, and WP-0009
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 54s
Details

Browse source 
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.
This commit is contained in:
tegwick 2026-07-16 10:28:58 +02:00
parent baba72676d
commit e0d7b0c3ad
6 changed files with 1368 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

12
wiki/PricingModel.md
View file

@ -60,6 +60,16 @@ On top of token-based billing, KaizenAgentic can introduce **subscription layers
* **Predictable:** Clients can forecast spend by capability tier, independent of vendor-specific LLM pricing changes.
* **Flexible:** Basemodel transparent to avoid basemodel lockin supporting various providers (ChatGPT, Claude, Cursor, etc.).
---
xxx
### 6. Engagement packaging (forward-deployed agency)
Capability multipliers (*M*) remain the tier engine for Role products. For
**staffed engagements** (seats, duty sessions, ramp-up/down, trial currency **Kai**,
and conversion to EUR), see:
* [ForwardDeployedAgencyBusinessModel.md](ForwardDeployedAgencyBusinessModel.md)
* Technical companion: [docs/forward-deployed-engagement-architecture.md](../docs/forward-deployed-engagement-architecture.md)
Token formula `C × M` still applies when vendor tokens are pass-through; engagement
pricing adds seat + duty + access-class so value is not only token volume.