feat(tuning): a definition may name its own model-call ceilings, and Deep raises them #517

Merged

coilyco-ops merged 1 commit from coilyco-ops/cost-knobs-are-per-definition into main

2026-08-13 14:59:12 +00:00

AGit

coilyco-ops commented

2026-08-13 14:57:16 +00:00

Member

closes #467 - the two profiles do not share a substrate so they cannot share one ceiling. Echo names no budget and is byte-identical; Deep goes up within the 2x to 4x asked for.

coilyco-ops added 1 commit

2026-08-13 14:57:16 +00:00

feat(tuning): a definition may name its own model-call ceilings, and Deep raises them

ci / image-build (pull_request) Successful in 25s

Details

ci / test (pull_request) Successful in 41s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

b63d794ba1

The ask was to raise the limits put in place for cost control, and to make them
configurable because the easy way would break local ornith. That prediction was
right and it is the reason this is a mechanism rather than an edit.

The model-call ceilings were process-wide constants, and the two profiles do
not share a substrate. Echo's route resolves to a 35B model on the daily
driver. Deep's resolves upstream and never touches it. A ceiling that is cheap
on Deep is minutes of tower time per Echo turn, so one number cannot serve
both.

A definition may now name a model_budget. Every field it leaves out takes the
value in tuning.go, so a definition names only what it changes and a definition
naming none behaves exactly as the constants did. The constants stay the
defaults rather than becoming dead.

Echo names none and is unchanged. Deep raises within the 2x to 4x asked for:
tool rounds 6 to 12, the completion floor 1800 to 3600, the ceiling 3600 to
14400, and the tool-result cap 8k to 16k. The ladder gets a second rung so it
can actually climb to the ceiling it names, which is pinned by a test rather
than asserted, because a ceiling a ladder cannot reach is decoration.

Validated at load. Every field is a ceiling so none may be negative, and a
ceiling below the floor is refused because it is a ladder that cannot climb.

Two package helpers now take their limit rather than reading a constant. Their
existing callers pass the same constant, so those tests assert what they did.

Not decided here: the specific ceiling on sirens-echo#367 is about the default,
which this leaves where it is. That decision is now a value change rather than
a code change. The cost tension from deploy#431, where per-turn spend is
reported to understate real spend, is raised on the issue rather than resolved
quietly.

closes #467

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-13 14:57:16 +00:00

coilyco-ops referenced this pull request

2026-08-13 14:57:42 +00:00

Raise (by 2x ~ 4x) limits that were put in place for cost control #467

coilyco-ops merged commit 8c1016596f into main

2026-08-13 14:59:12 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-13 14:59:13 +00:00

Merge pull request 'feat(tuning): a definition may name its own model-call ceilings, and Deep raises them' (#517) from coilyco-ops/cost-knobs-are-per-definition into main

coilyco-ops referenced this pull request

2026-08-13 15:43:41 +00:00