2003
WordPress
A human writes a page, clicks publish, and it is on the internet. The author is the quality gate. It works — until there are four hundred pages and no human left to check them.
FREE PUBLIC-WIRE AUDIT
Your agents can generate 10,000 pages. Can your system prove one?
Run an observe-only audit of a public URL. Constitutional CMS identifies visible contradictions, authority gaps, and unmeasured checks—and produces a receipt instead of another health score.
Inspect a sample receipt →·Run the CLI →
We run the same diagnostic on this site. Portable contracts are pinned tov0.5.0. Candidate tiers are not certification.
Two points in the lifecycle
After the wire. Before the next ship.
After publication
/check
- Inspects what an outsider actually received
- Public URL, ungated receipt
- certified: false on the public court
Before publication
CLI
- Evaluates evidence from your own system
- Same catalog, same receipt grammar
- CI opts into --fail-on FAIL
A score collapses “wrong,” “not applicable,” and “not observed” into one number. Constitutional CMS keeps them separate. Don’t repair eighty pages if one shared producer is wrong. Don’t trust the hosted checker — re-run the same verdict locally.
Decision lab · not this site
What surface has this page earned?
This lab is a teaching control. It is not the live receipt above. Toggle the evidence and watch the candidate tier change: claims, schema, and links are privileges earned by evidence, not decorations added at render time.
Product ladder
From audit to gate: four steps up the proof stack.
Start with a public URL. End with a claim gate. Each step earns its place by making one question falsifiable.
1
Public Truth Audit
One public URL, ungated. Paste a link, get a receipt. No account, no site changes, no composite score—just observable contradictions, authority gaps, and unmeasured checks.
2
Truth Receipt
Portable object; findings before email. A stranger can re-check every claim independently. The receipt is the artifact—not a dashboard login or an ephemeral health score.
3
Failure-Class Sweep
"This pattern appears structural. One page or one producer?" When the same contract violation repeats, the question shifts from single-URL inspection to systematic governance. Concierge only—contact us to discuss.
4
Claim Gate
Later paid motion. The question becomes: "May this claim be expressed on these surfaces right now?" The gate answers before publish, not after. Pre-announcement—not available yet.
The problem
Publishing used to have a human in the loop. Then the loop got four hundred pages wide.
Every era of publishing had a quality gate. The question is whether the gate survives when the author is an agent.
2026
Agent authors
An agent writes a page, clicks publish, and it is on the internet. Nobody checked the data, the links, or whether the page deserves the index. The site passes CI. The site is broken.
NOW
Constitutional CMS
An agent writes a page, and a contract decides whether it publishes. Data must trace to a source. Links must resolve. Thin pages stay shells until they earn a tier. Fail-closed, not fail-silent.
How it works
Read the contract, write inside the boundary, verify against the live surface.
Constitutional AI governs what models say. Constitutional CMS governs what agents publish. The contract replaces hand-wavy coordination. Each role knows what it can touch, what it must not invent, and what counts as done in production.
READ
Paused — click to resume
READWRITEVERIFYPUBLISHAUDIT
The five contract families
One canonical grammar for what the framework governs.
These are the same five families published in the pinned public repository—not a second five-item doctrine invented by the website.
01
Page type contracts
What a page needs at each quality tier.
02
Enrichment stage contracts
Which stage writes which state, and the gate that must pass first.
03
Link graph rules
What is allowed to link to what.
04
Snapshot boundary
The database schema is the inter-agent contract.
05
Sprint contracts
Scope, ownership, and what done means on the live site.
Read the canonical contract shapes →
Then see incident-learned invariants →
Design principles
Seven principles the contracts are written against.
Each principle is a decision rule: when a situation arises, this is the call the framework makes. Click to expand.
Agents read the contract before writing a line. Code generation begins from constraints instead of from improvisation — the boundary is the first input, not an afterthought.
Each fact has exactly one canonical source. When two representations disagree, one of them loses automatically. No surface re-derives what another surface already owns.
Empty, stale, and suppressed are typed states, rendered differently — never collapsed into one “unavailable.” A page that says “we don’t know” is honest; a page that invents a plausible value is not.
Machine proposals stay inert until a human or a declared policy ratifies them. You can always name who — or what rule — authorized each change that reached production.
Renderers translate, format, and localize. They never change a value. When a renderer receives a non-compliant payload, it refuses to emit rather than improvise.
Every production claim is verified from the served surface — not from the layer that produced it. A stranger, given the receipt, can independently re-check the claim today.
When the data boundary drifts, the system fails safely, not silently. A degraded page withholds schema and links until it earns them back. Governance decays without re-verification.
Interactive demo
A page meets a contract. The contract decides.
This is the publish gate: every field the contract requires must be on the page, and each one must trace to a source. One missing field blocks publish — fail-closed, not fail-silent.
Publish gate — synthetic entity pageidle
page_type: entity_page tier: FULL required: [validated_fact, source_snapshot, entity_name, json_ld] gate: fail_closed — one missing field blocks publish
·validated_fact present
·source_snapshot present
·entity named
·schema matches page
·tier eligible
PASS — synthetic candidate resolves to FULL. This demonstration is not certification.
Provenance mode: synthetic
Proof, not prose
Inspect a public page against the diagnostic catalog.
Paste a URL and get a bounded public-surface receipt plus a candidate tier. It is an inspection aid, not certification, and it never claims access to private implementation evidence.
Where it fits
Not a replacement for your stack. A governance layer on top of it.
Constitutional CMS sits where the publish decision happens. It does not replace the tools that build pages — it decides which pages deserve the wire.
Traditional CMS
human authors
- Draft and published are the only two states
- Editorial judgment is the quality gate
- One author, one page, one click
- Breaks when agents become the authors
Agent harness
build fast
- Agents are skilled at additive features
- Nobody tells them what they can’t do
- Conflicts pass CI and ship anyway
- Silent drift is the default outcome
Constitutional CMS
govern the publish
- Contracts define what agents may publish
- Continuous quality tiers, not binary states
- Every fact traces to one canonical source
- Fail-closed when the boundary drifts
Adjacent, not competing
Once a finding is governed, VIBEnet can govern how it reaches human attention.
Perception never changes the underlying verdict. Constitutional CMS is the first CTA.Right to publish vs right to notice →
Claim Gate Pilot
Sell prevention, not another audit.
The first URL audit is free. Email belongs at the Failure-Class Sweep — when the question becomes whether one shared producer is wrong. The bounded offer is a Claim Gate on that class.
✓ Receipt saved. You are on the list — we will follow up.
By submitting, you consent to a follow-up about Constitutional CMS. We retain submissions for 180 days.Read the privacy notice.