New
Capability-class routing. Applications request a capability — function calling, context length, evaluated quality floor, residency — and the route resolves it to a model. Model names in application code become unnecessary, which is what makes provider deprecation a change ticket rather than an incident.
Tool register. Every tool an agent can call, with its contract, permission scope, owner and policy gate, in one exportable view. Built for risk functions to read, which meant writing it for people who do not read code.
Quarantine as a first-class stage. Records failing the quality bar are held, flagged and routed for remediation rather than guessed at or dropped, with inflow, outflow, age distribution and reason breakdown reported.
Improved
- Hybrid retrieval available on all corpora, not only those explicitly configured for it.
- Entity resolution confidence exposed to retrieval scoping decisions.
- Trace store retention extended to match business record retention.
- Evaluation suites are versioned as independent artefacts with their own ownership.
Fixed
- Fixed routing fallbacks that could cross a residency boundary when the primary endpoint was unavailable. This was the change that led to the explicit residency failure policy in 2026.7.
- Fixed quarantined records being included in retrieval scope.
- Fixed lineage records not capturing the corpus version at time of use.
Deprecated
| Item | Replacement | Removal |
|---|---|---|
| Direct model-name requests | Capability-class routes | 2027.1 |
| Implicit retrieval scope | Explicit entity scoping | 2026.8 |
- Release
- Routing
- Agents
- Data