Client Delivery › C4 spec: Intelligence config
C4 spec: Intelligence config
C4 / L4 Intelligence: which models serve which work, at what cost, within which data boundaries.
REQ-M-00, portable by default: no client value may name a model vendor anywhere except inside the routing policy. Policy is coded and shipped through CI; transport is cloud configuration; the data-sensitivity boundary is always enforced, not optional.
REQ-M-00, portable by default: no client value may name a model vendor anywhere except inside the routing policy. Policy is coded and shipped through CI; transport is cloud configuration; the data-sensitivity boundary is always enforced, not optional.
The ground rules and artifact-placement conventions on the C1 specification apply to every band: values enter once in the binding, everything downstream is generated, nothing is hand-edited. Columns: discovery section, binding key, the exact artifact the value materializes into, when it takes effect, and the check that verifies it.
The configuration map
| ID | Client input | Disc. | Binding key | Materializes as | Takes effect | Verified by |
|---|---|---|---|---|---|---|
| M-01 | Model tier preference per use case | H | intelligence.tiers{} | Per-tenant policy overlay in the versioned routing table routing/tenants/<t>.yaml | Next call | Routing-policy schema check; regression evals gate every policy change |
| M-02 | Cost ceilings | H | intelligence.cost_ceilings{} | Same routing overlay; the router enforces per call, run budgets (C7) enforce per run | Next call | Ceiling test: a fixture exceeding the ceiling is downgraded or refused, never silently billed |
| M-03 | Latency targets: instant versus overnight classes | H | intelligence.latency{} | Latency class per use case in the routing overlay | Next call | Latency regression alerting per class |
| M-04 | Approved vendor list | E, H | intelligence.vendors[] | Vendor allow-list in the routing overlay; transport (inference profiles or deployments) configured per the cloud overlay | On config deploy | Router refuses a route outside the allow-list; a vendor swap demo touches exactly one file |
| M-05 | Data sensitivity boundary: which data classes reach which tiers and deployments | E, H | intelligence.data_boundary{} | Boundary matrix in the routing overlay, checked at the router hop | On config deploy | Fixture test: restricted-class content never reaches a disallowed tier or deployment |
Acceptance
- The tenant routing overlay deploys only through CI with regression evals green.
- The ceiling, allow-list, and sensitivity fixture tests all pass.
- A grep of everything above L4 finds no vendor name: the portability audit is clean.