AI Control Architecture · Marketplace
Neutral by design

The marketplace for AI control add-ons.

A neutral index of add-ons that plug into the same core. It belongs to the ecosystem, not to any one vendor. Anyone can publish, every add-on is signed and integrity-checked, and each enterprise decides how much to trust. Neo Control lists its own products here on exactly the same rails as everyone else.

What you can build

A small core plus six extension slots. An add-on reads and writes only ACA objects.

collector
Reads a system, emits ACA evidence. Connectors live here.
framework
Crosswalks controls to an external standard or regulation.
control-pack
Adds namespaced controls or a domain pack. Core ACA-* stays immutable.
test
An assurance or adversarial check, emits test-result evidence.
renderer
Turns an assessment into a report or export.
enforcer
Acts at runtime on a decision. Paid enforcement plugs into this public interface.

Two tracks

Open trackCurated track
Who publishesAnyone, permissionlessReviewed submissions only
CertificationACA-CompatibleACA-Verified ACA-Certified
VettingAutomatedAutomated, security, behavioural (plus assurance for Certified)
RuntimeAlways sandboxed, permission-promptedSandboxed; may be pre-trusted per enterprise policy
Paid add-onsNot the place for themYes, this is where commercial add-ons live
Best forThe long tail, velocity, experimentationEnterprise-safe adoption and monetisation

An enterprise can set a policy of curated-only. An individual builder can live entirely in the open track.

Every listing is verifiable

Transparency is the point. The decision an enterprise makes is "can I trust this," and each listing answers it up front.

Under the hood, every package carries a deterministic content hash and is signed with Ed25519. Consumers verify the signature and re-check integrity on install, so a package changed since publish is rejected. A compromised add-on can be revoked centrally, and installed instances are disabled on the next check. The same registry serves a self-hosted core and a hosted one.

Live catalogue

Signed, verifiable add-ons in the registry. These are the open reference add-ons today; third-party and curated listings appear here as the registry fills.

The curated track, reviewed and enterprise-safe and where paid add-ons live, opens as the first commercial add-ons are certified.

Publish your add-on

Scaffold from the reference core, then publish through the signed registry.

npx @aca/core new collector yourorg/your-connector

aca-registry keygen --out mykey
aca-registry publish ./your-connector --track open --key mykey.key.pem --publisher yourorg
The registry (aca-registry) List your add-on / become a Steward

Certification

Certification tells an enterprise what an add-on is and how far it has been checked. These are ACA marks, kept separate from any single vendor's product claims.

ACA-Compatible
Automated checks pass: valid manifest, schemas, and interfaces. Awarded on publish to the open track. Buyer-beware, always sandboxed.
ACA-Verified
Compatible, plus a security and behavioural review by the curated board. For the curated track, where trusted and paid add-ons begin.
ACA-Certified
Verified, plus demonstrated conformance to an ACA profile through an approved assurance process. The highest bar.

How it works: publishing to the open track earns Compatible immediately. Verified and Certified are granted by the curated review board against published, versioned criteria, with an appeals path. A compromised or non-conforming add-on can be revoked and its mark withdrawn. Support tiers (Community, Verified, Certified, Neo-supported) sit alongside the certification mark.

Neutral by design

The marketplace is deployment-neutral: the same registry serves a self-hosted core and a hosted one, and no vendor owns the shelf. Neo Control is the founding steward and the first participant. Its own products, such as AI Supply Chain, Vendor Risk, Shadow AI, and the Action Fabric, list here as curated add-ons on the same rails as anyone else's, and compete on how well they work, not on owning the marketplace.

This is v0.1 and evolving. The curated review board is Neo-stewarded today and moves to external assessors as ACA matures, with published, versioned criteria and an appeals path. See the ecosystem RFC for the full extension contracts and governance.