CAIN-42 · E54 · open ecosystem

The core is open. The catalog is real. Adoption is measured, not announced.

Ten project-maintained reference packages: enforcement, protocol, adapters, SDK, verifier, evidence network, control plane, adversarial lab and a local network. Every entry points at code in the release archive. There are no fictional third-party listings.

reference packages

78/78

public conformance cases

SELF_TESTED

badge — not a certification

external publishers (honest count)

UNKNOWN

downloads / active installs

Catalog — what is actually shipped

Package	Category	Trust label	What it does
MCPGate enforcement boundary	enforcement	LEVEL_2	single-use capability, default deny, replay
Hosted capability gate	enforcement	LEVEL_2	pinned issuer, request-bound capability
Universal governance protocol	protocol	LEVEL_2	cain.governance.v1 strict schemas
Framework adapters	adapters	LEVEL_2	six native tool-call shapes
Python SDK	sdk	LEVEL_1	client for guarded actions
Offline evidence verifier	verification	LEVEL_2	Merkle + signatures + witnesses, no CAIN imports
Independent evidence network	verification	LEVEL_2	log, checkpoints, disputes
Multi-tenant control plane	control-plane	LEVEL_2	registry, policy, delegation, revocation
Consequence adversarial lab	testing	LEVEL_2	oracle, attacks, mutations
Local four-node network	deployment	LEVEL_1	local PBFT, one host

Trust labels are evidence, not marketing. LEVEL_2 means functional conformance tests pass locally. LEVEL_4 would require an independent review; no package claims it. Third-party listings are zero until a real third party submits one.

Conformance, not certification

python3 -m cain.ecosystem.cli conformance
python3 -m cain.ecosystem.cli search mcp
python3 -m cain.ecosystem.cli metrics

# current output
badge: SELF_TESTED
adapters: 6 frameworks, 78/78 cases, 0 failed
evidence: VALID (sample bundle)

Adoption metrics — no invented numbers

download_requests: UNKNOWN (no readable access log on this host)
active_installations: UNKNOWN (no opt-in telemetry)
external_publishers: 0
external_contributors: UNKNOWN

Download counts are request counts, not users. This page will show a number only when a measurement source exists; until then it says UNKNOWN.

Submit an adapter or package

python3 -m cain.ecosystem.cli submit my-package.json

Required: name, publisher, category, license, description, version, protocol versions, capabilities, security declarations, maintenance status. A submission is schema-validated, then reviewed. It is not listed automatically and never inherits trust.

Honest gaps

No third-party publisher or adapter has been submitted; the ecosystem is at zero external adoption.
No package registry publishing (PyPI/npm) in this release; distribution is the source archive + git bundle.
No HTTP marketplace service; the catalog is a local library and a generated JSON.
No independent review, no certification, no standards-body status.
No reviews or ratings are shown because there are none.

← open core · E53 control plane · E52 evidence · claims · catalog JSON