A reviewed path for new checks and ZK circuit releases.
The studio is where future issuers and U-net admins coordinate new attestation types before they become visible in the dynamic verification check catalog.
A dynamic check catalog only works if holders and verifiers can trust that every active type has a known issuer path, a verifier artifact, and a clear release state.
What a release actually requires
Four gates, every attestation type passes through all of them.
Request shape
Request type, predicate metadata, label, consent text, category, and issuer eligibility notes.
Circuit manifest
Circuit release manifest with circuit ID, VK ID, proof format, public input order, oracle hash, and proof encoding.
Artifact validation
Verifier artifact hash checks and sample proof bundle validation before activation.
Release lifecycle
Lifecycle controls for draft, staged, active, deprecated, and revoked releases.
The studio flow
Predicate metadata, verifier artifacts, sample proofs, and release status stay visible as separate gates.
Describe the predicate
Define the label, consent text, category, issuer eligibility notes, and public-input expectations.
Attach verifier artifacts
Provide the circuit ID, VK ID, proof format, artifact hashes, and sample proof bundle.
Validate before activation
Check proof shape and verifier artifacts before a release becomes visible in the verification catalog.
Manage lifecycle states
Move through draft, staged, active, deprecated, and revoked states without losing release context.
The goal is confidence before visibility.
A dynamic check catalog only works if holders and verifiers can trust that each active type has a known issuer path, verifier artifact, and release state.