Skip to content
CAI
Produce a survey ↗Verify a survey

The registry

Signed CAI deliveries. Producers push. Consumers read.

The registry is where signed CAI-delivery packages live — dated, content-hashed, Ed25519-signed. It is the physical anchor of the evidence model: the evidence exists once, here; the decisions built on it belong to whoever needs them.

The registry, read out

A delivery, as the registry serves it.

The anatomy of a CAI delivery: the verdict, the fixed band scale, the lens roll-up, and the provenance rows a consumer verifies against.

CAI score card

What the registry holds

Three things — packages, the public record, and access.

Signed CAI-delivery packages

Every delivery is dated, content-hashed and Ed25519-signed at the moment it's produced. A package can be handed on, but not altered — the signature and hash travel with it.

How verification works →

The public record

Opted-in open surveys — real repositories whose owners chose to publish, with the entire survey open to read. The human gallery lives on Watchdog public reports; the canonical signed records live here.

The access directory

"Give access" for sellers, "request access" for buyers — the directory that powers the two entry flows: a seller shares a delivery, or a cooperative buyer brings access to the code.

The trust invariant.

Signed & reproducible by us, not editable by the sharer — that is what makes a shared artifact believable. A seller can hand a buyer their survey precisely because the seller can't touch its contents.

What the registry is — and isn't.

The registry API (api.codeassuranceindex.info) serves push, pull and access grants for Watchdog and Assay. Openness is the trust anchor — not a marketplace.

Holding a delivery? Check it.

Produce a survey → watchdog.canine.dev · Commission a decision → assay.canine.dev