KAIF Execution Plan
Delivery is organized around seven shippable modules. Each has its own repo, CRDs, charts and evidence, and each contributes to one or more of the Development · Deployment · Evaluation lifecycles. The reader view keeps the three-lifecycle narrative; this page is where the work gets planned.
The seven modules
Technology stack mapped to each plane of the detailed architecture. Head-to-head research and comparisons of options per use case. Ships Helm charts, CRDs, GitOps manifests, automations and scripts.
Owns the design harness — pattern catalogue, model matrix, tool inventory, memory options, orchestration templates, tradeoff scoring — and the online design evaluator that measures those decisions once they run.
Owns operators, packaging, rollout, scaling, routing and the runtime wiring of observability. Enforces (does not author) eval, guardrail and identity policy.
Owns datasets, judges, rubrics, the Eval Gateway API and the storage of every eval result.
Owns Kyverno/OPA admission policies, OPA request-time authorization, content safety sidecars and runtime detection.
Turns raw traces, evals and cost signals into exec/product dashboards. Owns the KPI catalogue.
Owns workload identity, user identity, per-tool scopes, tenant isolation and secret distribution.
Operating model
- Cadence: 2-week iterations. Each ends with a demo + short write-up.
- Repos: one per module, plus
kaif-blueprint(this site) andkaif-agents(reference workloads). - Target cluster: kind / k3d locally, then a small managed cluster (3 nodes + 1 GPU) for "real" runs.
- Definition of Done: manifest in Git → deployed via GitOps → observable in Grafana → covered by at least one eval → documented on the site → KPI in kaif-value.
Roadmap
| Phase | Iters | Focus |
|---|---|---|
| P0 | 0 | kaif-platform foundations: cluster, GitOps, observability, supply chain, registries. |
| P1 | 1–3 | kaif-identity + kaif-guard baselines; kaif-design offline harness v1; kaif-eval build surface. |
| P2 | 4–6 | kaif-deploy operators + rollout; kaif-eval deploy-time gates; kaif-guard runtime controls. |
| P3 | 7–9 | kaif-eval runtime + kaif-design online harness; kaif-value dashboards v1. |
| P4 | 10+ | Reference agentic SDLC crew exercising every module end-to-end. |
Cross-cutting workstreams
- KAIF Technology Selection Report — owned by kaif-platform.
- Threat model — co-owned by kaif-guard + kaif-identity, updated per phase.
- Cost model — owned by kaif-value from P0 onward.