AGPL-3.0-or-later · forever.

the error register

NIKA-SEC-016

the effect-safe retry law — a declared retry: (max_attempts > 1) on a nika:fetch whose method replays side effects (POST · PUT · DELETE · PATCH) with no idempotency-key header: the failure may be ambiguous (the server may have committed before the socket dropped or the error was emitted), so the engine types the keyless call's failures non-transient and the declared retry is refused statically (an on_codes: retry would blind-replay regardless of transient) · pair an idempotency-key header (the receiver dedups the replay) or drop the retry: — GET/HEAD retry free (issue #1371). A typed refusal, one of 104 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.

  • security_errorcategorya security policy refused the effect
  • stablea retry cannot helpfix the file, not the timing
  • 15of 15 in NIKA-SECprev / next walk the registry
  • 104registered codesthe normative floor · versioned

hear it from the binary

nika explain NIKA-SEC-016 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.

Break a file on purpose in the playground and watch the code arrive typed. The boundary teaches the security family. Read the spec →