Skip to main content
The SDK carries types and transport. The engine remains the policy enforcer.

Local seam

PROCESS BOUNDARY · ONE ARGV VALUE
The local transport spawns the resolved absolute engine path with an argv array and never wraps a workflow path in a shell string. A bare nika would make the operating system search PATH, so bin and NIKA_BIN must be absolute.

Admit authority before execution

A check() report describes the bytes it read at that moment; run() re-admits the file’s current content. If the path is mutable between the two calls, the report does not authorize what actually executes — gate the path’s integrity, or snapshot first. Check these facts explicitly:
  • permitted filesystem paths, network hosts, programs and tools;
  • model and environment requirements;
  • secret names, never values;
  • the static cost floor and unbounded flag;
  • explicit run.cancel() and runtime ceiling.

Remote seam

Bearer tokens belong in governed environment or workload identity plumbing, not source. The SDK exposes no logger or webhook verifier; keep application logging and delivery secrets outside the Nika transport. The token also downloads artifacts: any holder who knows a settled job’s id can read the files that job’s sealed journal records, the project files a builtin saved, the images an agent’s harness sent and the files an agent: task saved from them. The server serves only bytes that still match the journal, and the SDK checks them again on arrival, but the content is still whatever the workflow produced. Treat a downloaded file as untrusted input, and keep the server’s Content-Security-Policy: sandbox, nosniff and attachment headers if your application serves it again. Server runbook lists what the routes expose.

Threat boundaries

Continue

Security concepts

Read the default-deny engine model.

Cost honesty

Refuse unknown spend deliberately.

Webhooks

Verify delivery before dispatch.

CI gate

Put admission before secrets.