The five gates
Draft
The publisher builds the skill and declares its tools and inputs in the manifest.
- Evidence: Manifest, declared tools, and publisher
Scanned & tested
Review the package and run sandbox, functional, adversarial, and regression tests.
- Evidence: Scan findings, sandbox trace, test results, and regression comparison
Signed
Bind the publisher key and attestations to the release’s content hash.
- Evidence: Content hash, signature, attestations, and approver
Published
Make the immutable version discoverable by trust tier and domain.
- Evidence: Version, trust tier, publish date, and changelog
Installed
Check that the release’s tier meets workspace policy.
- Evidence: Workspace, installer, pinned version, and agent bindings
Who owns each control?
The registry governs the skill. Runtime permissions and decision records belong to the rest of the Elixir Platform.
Scroll horizontally to see the full comparison.
| Control | Owner | Question it answers |
|---|---|---|
| Publishing, scans, evaluations, and signatures | ElixirHub | What does this version do, and who approved it? |
| Discovery and workspace trust policy | ElixirHub | May this workspace install the release? |
| Runtime permissions and tool access | ElixirClaw | What may the agent do right now? |
| Context Graph and decision records | ElixirData | What was decided, with which skill version, and why? |
Install where agents already work
ElixirClaw agents
Attach a reviewed release to an enterprise agent with its version pinned.
Explore ElixirClawCLI and API
Use the registry’s publishing and discovery interfaces in your workflow.
View API documentation