the error register
NIKA-INFER-004
the provider spent tokens yet the visible answer is empty — a thinking model ate the budget on its reasoning trace (fail-closed · #651 · raise max_tokens or use a no-think variant). A typed refusal, one of 103 the registry names: stable code, spec category, the transient flag the retry machinery reads. The engine stamps this page's address on the finding itself. Route on the code, never on prose. Machines read the catalog.
- validation_errorcategorywell-formed input, spec-rule violation
- stablea retry cannot helpfix the file, not the timing
- 4of 4 in NIKA-INFERprev / next walk the registry
- 103registered codesthe normative floor · versioned
hear it from the binary
nika explain NIKA-INFER-004 answers offline with the failure, the fix shape and this page's address: the same text the check finding carries. A code is a contract: never renamed, never repurposed, safe to route on in on_codes and retry policy.
cross-references
the pages that name it
the family it sits in
the NIKA-INFER codes
4 codes- NIKA-INFER-001
- NIKA-INFER-002
- NIKA-INFER-003
- NIKA-INFER-004
Break a file on purpose in the playground and watch the code arrive typed. The boundary teaches the security family. Read the spec →