§ 01 . the control panel
Every run is a set of decisions.
For each subtask, LeanTokens selects an approved execution setup: agent, model, reasoning effort, tools, skills, and context. It then verifies the result and records the decision.
fig 01 . control surface
one prompt in, N sub-tasks configured, one verified output
policy updates after each run ↑
§ 02 . what it optimizes
Optimize for cost, speed,
and quality.
01 ↓
COST
Only the tokens you need.
Route each sub-task to the smallest capable model. Size context to the step. Skip redundant passes. Cache and reuse where valid.
02 ↓
LATENCY
Parallel by default.
Independent steps run in parallel. Long chains collapse where they can. Verifier retries are bounded, not open-ended.
03 ✓
QUALITY GATE
A floor you set.
You set an accuracy floor. Cost and latency optimizations only ship if outputs still pass the verifier and your regression checks.
where leantokens sits
Keep your agent stack. Add a control layer.
fig 02 . positioning
the bet
“Agent stacks are getting more complicated, not less. Someone has to turn the dials so you don't have to.”
§ 03 . how a run looks
Plan, configure, verify, learn.
fig 03 . one run