Skip to content

CADS Manifest Marketplace

A ct-agent can activate a publisher-signed manifest that deterministically installs, runs, and verifies a service behind its own tunnel — instead of an operator hand-wiring a locally-trusted script.

A manifest is a remote-code-execution primitive by design: it tells a ct-agent what to build and run. So the honest question is never what is planned — it is what actually works, and how do we know. This site answers that, and marks every claim:

measured run end to end on a macOS host with no Docker daemon, on 2026-08-27, against the marketplace at d09eecd. The output was seen and is quoted verbatim.

audited run by the maintainer against a real budget-capped local model. The transcripts and the guard's error strings were checked against source independently.

not built deliberately absent — reserved in the schema, refused at runtime, and documented as such.


Start here

  • Tutorials

    Learn by doing. Publish your first manifest end to end and watch the guardrail catch a hostile one.

  • How-to

    Task recipes: run the registry locally, sign a manifest, read a verdict.

  • Reference

    The registry API, the manifest schema, the guardrail rules, the installer kinds.

  • Explanation

    Why a signature is never enough, how the harness is caged, and why this site marks measured versus claimed.

  • Demos

    What's actually running on top of ct-agent, and whether it has docs of its own.


What works today

Capability Status
Manifest signing & verification (ed25519) measured
Registry: publish → fetch → bundle, byte-identical measured
Guardrail scan at publish time (F.1 / F.2 / F.3) measured
Publisher authorization (401 / 400) measured
Activation ledger measured
Admin dashboard (read-only) measured
Binary installer runs without Docker measured
Workspace test suite, no daemon measured — 100 / 100
Harness: bounded local-LLM bundle edit audited
Harness containment (3 adversarial cases) audited
Hosted public registry (registry.bunsenbrenner.org) measured — 7-demo portfolio published, byte-identical refetch, 2026-08-29
Guided demo_prompt config, signed measured — signed & round-tripped byte-identical
Compose bundle activation (needs Docker) not run here
Kubernetes installer by design — schema only
Real payments by design — ledger only
Public human-facing catalogue UI not built — the hosted registry is a JSON API

The Reference gives each of these its own dry, complete entry.