stolz-route
Chooses one smallest sufficient route and falls back safely when capabilities are missing.
decideI.A rational operator for context
Open source / provider-neutral core / evidence-gated claims
STOLZ A.I. is a set of five focused skills that selects the smallest sufficient route, loads context only when needed, reuses verified results, and keeps unchanged state outside the model — without lowering the bar for correctness.
§ 1No numerical savings claim without paired evidence.
The literary source is part of the product idea
In Goncharov's novel, Stolz is active, educated, practical, and systematic — a counterweight to inertia. STOLZ A.I. translates that character into agent engineering: plan before loading, act without fuss, and spend resources only where they move the task forward.
«Движений лишних у него не было» — “He made no unnecessary movements.”
Ivan Goncharov, Oblomov, part II
III.Five skills, one discipline
Install only what the route needs
Each skill has a narrow trigger and a safe fallback. STOLZ A.I. is not a catch-all prompt and does not replace the model, the runtime, or project-specific verification.
Chooses one smallest sufficient route and falls back safely when capabilities are missing.
decideValidates the route manifest, then loads only immutable, route-required context.
loadReuses a result only when its identity and verification still match the task.
reuseKeeps unchanged polls outside model narration and reports material transitions.
observeAccepts an efficiency comparison only after outcome and verification gates pass.
proveIV.Smallest sufficient route
The red editor's line does not cross out reasoning or verification. It crosses out work that adds no new information: broad reads, duplicate commands, stale results, and narration of unchanged state.
V.The claim has a gate
A published saving requires paired baseline and optimized runs on the same versioned fixture, equivalent required outcomes, and passing verification for both routes.
Read the benchmark reportBaseline and optimized routes receive the same versioned task.
Both routes must satisfy the same required result.
A lower count with failed checks is rejected.
Record the measured delta and its evidence boundary.
VI.Compatibility without borrowed authority
Fixture and CLI certification are available.
Adapter and isolated profiles are included.
Adapter and isolated profiles are included.
Declarative selection is not provider-call or savings certification.
VII.Start with the route
Clone a tagged or reviewed revision, run the test suite, and start with `stolz-route` unless the task already has one clear concern.
$ git clone https://github.com/Sergey360/stolz-ai.git
$ cd stolz-ai
$ npm install
$ npm test
✓ verified before install
VIII.Reader's notes
No. It targets waste around reasoning: unnecessary context, repeated operations, stale reuse, noisy monitoring, and ungated comparisons.
There is no provider-wide percentage claim. Savings depend on the task, runtime, fixture, and route. STOLZ A.I. publishes a number only with paired evidence and equivalent verified outcomes.
The core contracts are provider-neutral. Current C0/C1 support includes Codex local, Claude Code, and Qwen Code; stronger provider claims remain withheld where evidence is missing.
The character defines the product ethic: educated action, planning, resource discipline, and movement toward a concrete result — not saving at any cost.