NikaCheckResult deliberately stays open:
report_version: 1): the
same audit nika check --json prints. The fields an application usually
reads, measured on engine 0.123.0:
Pass
access to judge the access plan under a pin, as nika check --access
does:
clean: true (the file holds) with
verdicts.access_ready: false, and verdicts.blockers names the refusal in
the engine’s words (Access pins).
Apart from clean, exitCode and verdicts, the SDK types these fields as
unknown: narrow them in your code. Findings
are report data; configuration, engine resolution, transport and protocol
failures throw typed errors. Keep application policy outside the SDK, and
preserve unknown fields when storing or forwarding the report.
Permits and admission shows a complete policy check.
Remote checks intentionally reject the local-only model and nativeStrict
overrides rather than silently ignoring them.
For a contained served name, the remote result is the resident’s typed
acknowledgement or workflow refusal, without local findings or an exit code.
An explicit local path instead captures a local engine report and snapshot;
successful capture requires the resident to acknowledge that exact snapshot.
See remote checks for the two forms.
Which published source this page describes
Which published source this page describes
Run and cancel
Admit only after application policy accepts the check report.
Errors
Separate dirty reports from thrown boundary failures.