Files
sql-server-query-ai/kb/Output token ceiling.md
T
ahmed mohammedandClaude Opus 4.7 8b42a0931c docs: karpathy-pattern wiki built from the spec, plan, design contract and decisions ledger
kb/ is its own wiki root: 34 pages across 7 categories, index.md catalog, log.md, AGENTS.md schema layer, and raw/ holding copies of README, the spec, the 13-task plan, the design master and the SDD ledger.

Every page cross-references 3 to 6 others and all 107 wikilinks resolve except two [["list"]] artefacts inside JSON snippets in the copied plan.

Kept separate from the repository root on purpose: its generated graph lands in kb/.ua/ instead of overwriting the code graph.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-09-22 12:14:05 +03:00

13 lines
651 B
Markdown

# Decision: output token ceiling
Once every option had to carry runnable T-SQL, the candidate JSON outgrew the old 2 048-token budget. The user
waited 38 seconds and got "The analyst model returned malformed JSON" — a truncated response has no closing brace.
Both calls default to 4 096 now, and the failure message names the character count and tells the user which extra
parameter raises the ceiling, because `cfg.extra` is spread after `max_tokens`.
The general rule recorded here: when a prompt asks a model for more content, check the budget before blaming the
model's judgement.
Related: [[Analyst model]], [[Placeholder SQL is dropped]].