.nika file, so sharing one is just
sharing text. nika-registry
adds a trust layer: every entry is re-proven by CI — pinned to a full
commit + sha256, re-run through the conformance oracle, and certified by
the engine’s static analysis. You see what a workflow can do — exec,
tools, cost ceiling, secrets — before a single token is spent.
Trust lives in the artifact, not a gatekeeper: the certificate re-derives
locally with
nika check. You never have to believe the registry — you
re-run the proof yourself, offline.Install an artifact
The supported path is a short, auditable script in the registry repository. It needs Python 3.11 or newer (it reads TOML with the standard library) and PyYAML for its local audit step:get.py refuses on any mismatch (hash · advisory · file already there) and
never executes anything — the workflow lands on disk and you decide to
run it. Not curl | sh. Then check and run the file by its path like any
other workflow.
The guarantees
Machine surfaces (for agents)
index.json— every artifact with its pin, digest, cert summary and advisory state in one fetchllms.txt— the consume/verify path in agent-readable form