1.1Coming
Budgets enforced
Tokens, steps and cost checked before each model call.
Product / Platform / Routing and recipes
Routing and recipesComing
The cheapest path that can still be verified.
Before any model call: a rule, then a recipe, then a cache, then a small model, then a big one, inside token, step and cost budgets. Proven runs replay as recipes, still through the gate.
Fig.1
- 01S
door
signed entry
- 02N
understand
model reads
- 03N
plan
model proposes
- 04S
gate
rules decide
- 05S
hands
API first
- 06S
check
read back
- 07S
record
signed ledger
- 08N
learn
recipes, memory
How it works.
- 01 /
Classify
Deterministic features pick the path, from a decision table.
- 02 /
Take the cheapest path
A rule-answerable request spends no model tokens.
- 03 /
Learn
Verified runs become recipes; two failures demote them.
What you get. Each point labelled with its real status.
1.2Coming
Fallback provider
A second model provider takes over when the first fails.
1.3Coming
Adaptive retrieval
None, context, agentic, business graph or code graph, per request.
1.4Coming
Cost per resolved task
Only verified outcomes count.