Prior art, honestly placed
A publishing-governance approach.
Runtime security, infrastructure policy, API shapes, editorial workflow, and agent capability each have established approaches. This framework focuses on what a page may assert, its declared publication requirements, and who may write it. This is a scope comparison, not evidence that other tools cannot govern content.
| Tool | What it governs | What Constitutional CMS adds |
|---|---|---|
| Microsoft Agent Governance Toolkit | Runtime security — permissions, tool access, kill switches | Content governance: publish tiers, link graphs, schema emission |
| OPA / Rego | Infrastructure access policies | Content quality and publish-tier gating |
| OpenAPI | API response shapes | Full page lifecycle from ingestion to indexation |
| WordPress / Drupal | Human editorial workflow | Multi-agent production at programmatic scale |
| Anthropic Skills | What agents know how to do | What agents are not allowed to do |
The gap it closes
Make the publishing decision inspectable.
Constitutional CMS governs the publish decision itself: the tier a page has earned, the links it may emit, the schema it may carry, and the evidence it must trace. It composes with the tools above instead of competing with them.