Skip to content

fix: restore Alia chat with a bounded production input budget - #1579

Merged
NateIsern merged 3 commits into
mainfrom
fix/alia-production-input-budget-20261004
Oct 4, 2026
Merged

NateIsern merged 3 commits into
mainfrom
fix/alia-production-input-budget-20261004

Conversation

@NateIsern

Copy link
Copy Markdown
Member

Alia rejected ordinary chat before provider dispatch because the internal pilot allowed only8,192 controlled UTF-8/framing units; its real synthetic Hello context is29,027, including21 built-in tool schemas. Give Alia text completion a126,976 ceiling while preserving decisions8,192, per-route context, output2,048, exact deployment allowlist and existing capacity/metering.

The same HTTP/Postgres fixture reproduces400 before the fix and passes with one dispatch afterward;73 tests in4 suites pass, including exact boundary, Unicode/schema payloads, route context and duplicate refusal. Larger admitted inputs can increase provider cost; this is a bounded product correction under the user's existing approval, with no invented funding or invoice guarantee. Detailed evidence in docs/audits/2026-10-04-alia-production-input-budget. Tracks #1571/#1519 and incident chatcmpl-03f86870-ed03-4760-bede-cde281975bfc.

@NateIsern
NateIsern enabled auto-merge October 4, 2026 16:55
@NateIsern

Copy link
Copy Markdown
Member Author

Independent source and evidence review: no blocker found in source 27ebf33872c4e3c6e72e97a728f157d42a8ffaf2 / evidence head 9304fca25bb19553a63b699a0b467218d7704bd6.

The 126,976 ceiling applies only to completions. Decisions keep 8,192; the output cap, allowed deployment tuples, per-route context qualification, quoting, and request capacity remain enforced. The added HTTP/SQL controls cover exact N acceptance, N+1 denial before metering, UTF-8 and tool-schema oversize, smaller route context, one dispatch and idempotent refusal. I independently checked all 13 source/record hashes against Git/current files and the 13 pinned measurement inputs. Preserved results report 73 passing tests across four suites, build success and scoped lint success; I did not rerun those suites.

The real Alia builder measurement uses synthetic Hello context and shows 29,027–30,328 controlled units, already above the former cap. Larger admitted input can increase provider cost: this is a bounded product input allowance, not a monetary ceiling or a provider-token guarantee. No original private prompt/provider replay is claimed. Full-repository lint warnings remain explicitly recorded. Runtime promotion and CI acceptance remain with the release operator.

Source and evidence.

@NateIsern
NateIsern added this pull request to the merge queue Oct 4, 2026
Merged via the queue into main with commit f716a52 Oct 4, 2026
22 checks passed
@NateIsern
NateIsern deleted the fix/alia-production-input-budget-20261004 branch October 4, 2026 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant