The public jamesfgibbons/constitutional-cms repository is authoritative for portable framework content:
- contract and schema shapes
- validators and conformance tooling
- synthetic examples and fixtures
- public documentation
- signed release tags and public release notes
- sanitized, independently checkable public receipts when explicitly published
Private implementation repositories remain authoritative for:
- entity registries, route maps, and source coverage
- operational thresholds, scores, and compression logic
- prompts, voice systems, and enrichment recipes
- private incidents, evaluation baselines, and operating receipts
- website presentation, lead capture, checker runtime, and deployment configuration
The website may adapt portable framework text, but normative language must link to a pinned public release. A private implementation may conform to the framework without publishing its protected inputs. Neither the website nor a private implementation silently becomes the source of portable contract law.
Public examples use an explicit provenance statement. Missing provenance or a private-source reference is a release blocker, not a documentation nit.