What this proves

The case study is here to answer a narrow question: does the contract model hold up in production?

The answer is yes. It governed a live system with:

• 851 pages returning HTTP 200
• 54ms median time to first byte
• four AI agents working in parallel
• nineteen merged pull requests in a coordinated push

What the framework was responsible for

The framework governed:

• whether pages qualified for a publish tier
• whether thin pages degraded safely
• whether internal links could be emitted
• which agents were allowed to write state
• what counted as done in production

It reduced a common failure mode in agent-built systems: individually sensible changes creating a collectively incoherent site.

What remains private

This site does not publish:

• the detailed route and entity mappings
• the exact threshold tables behind the publishing system
• the compression logic and scoring layers used internally
• the enrichment voice controls and prompt recipes
• the private evaluation baselines that govern the operating model

Those are not omissions caused by an incomplete launch. They are the proprietary part of the business.

Built inside Targeted Impressions Labs

Constitutional CMS is a public spoke inside the wider Labs portfolio. The portfolio context matters because it explains why the framework exists at all: it was created to govern real products, not to serve as abstract policy theory.

For the broader parent context, visit Targeted Impressions Labs.