Enforcement is the weakest of the edition’s verticals: bundling an advisory vertical with a blocking one yields an advisory edition, because the least-checked document in the bundle is the one that carries the risk.
What an edition guarantees
- Every verifier an edition lists is activated by at least one of its verticals. A verifier that no vertical activates never runs, so it cannot be listed.
- Every vertical, policy set, source pack, connector type, and review role in an edition exists in the catalog. The build fails when one does not.
- The edition’s version and changelog are part of the record, so the bundle a customer licensed can be named exactly.
GET /api/editions lists editions; GET /api/editions/{id} returns the resolved bundle, including per-vertical verifiers and enforcement, the number of forbidden and conditional claims in each policy set, the union of allowed templates and style profiles, and each source pack’s API sources.
Editions describe the catalog. Attaching an edition to a workspace, pricing, and per-edition licensing are not yet available.
Verticals
The vertical configurations editions are built from.
Corpus API and MCP
Workspace documents and connectors.