Open
The public release includes:
- the governance model
- the contract categories
- the example YAML structure
- the validator
- synthetic examples and public receipt shapes
That is enough to understand the pattern, test it, and adapt it to a different domain.
This site’s crawler choices are explicit in
/constitutional-site-manifest.json and commented in
/robots.txt: search allow, user-directed retrieval allow, training mixed.
Proprietary
The release intentionally excludes:
- detailed entity registries and mappings
- corridor logic and domain grouping systems
- score compression and threshold heuristics
- internal prompt packs and narrative controls
- private eval harnesses and anomaly rules
Those details are where a specific implementation becomes a durable operating advantage.
Why this line exists
The point of the open release is to publish the constitutional layer that makes agent-built publishing more trustworthy. The point is not to publish every private input, rule table, or research artifact that powers one company’s production system.
That line keeps the project honest:
- open where the field benefits from shared language
- closed where the implementation becomes a moat
What to expect if you adopt it
If you use Constitutional CMS in your own stack, your domain-specific contracts should become your own advantage. The public repo gives you a starting point. Your detailed mappings should stay yours.