Canonical taxonomy routing
One scheme per question.
Constitutional CMS uses several ordering schemes because they govern different objects. This page is the consuming-layer rule: identify the question first, then use only the scheme authoritative for that question.
Cardinal law
A taxonomy may not silently answer a question owned by another taxonomy.
Counts are labels, not identities. “Five contracts” and a five-item invariant release are unrelated sets. A page tier is not conformance. A release gate is not priority. A repair layer is not a control class.
A new taxonomy is inadmissible until it names the object it governs, the one canonical question it answers, and its relationship to every existing scheme.
Renderer-facing awareness is a separate public protocol —VIBEnet Signal Contract. It is not a fifth web-conformance profile and it is not a G0–G5 substitute.
Five contract families
What part of publishing is governed?
Governs: Page types, enrichment stages, link graph, snapshot boundary, sprint acceptance
Use it to: Choose the contract family that owns a rule or change.
Do not use it as: Not a maturity model, severity scale, or work queue.
Incident-learned invariants
What must remain true across implementations?
Governs: Falsifiable conditions extracted from generalized failure scenarios
Use it to: Name the condition a probe attempts to falsify.
Do not use it as: Not another set of contract families; counts may change by release.
G0–G5 maturity sequence
How mature and certifiable is an implementation?
Governs: The sole implementation and certification maturity sequence
Use it to: Describe adoption progress and the evidence family required at each stage.
Do not use it as: Not a page publication tier, capability profile, or composite score.
Four conformance profiles
Which web capability is being evaluated?
Governs: Web Foundation, Search, Answer and AI Retrieval, and Agentic Web
Use it to: Group related checks and expose evidence coverage by capability.
Do not use it as: Not a maturity sequence, work order, or guarantee of traffic or citation.
Eight release gates
What evidence must a release candidate pass?
Governs: The load-bearing publication and verification sequence
Use it to: Decide whether a candidate may be promoted.
Do not use it as: Not a backlog ranking system.
Four-layer repair stack
Which layer should be repaired first on a publishing surface?
Governs: Data truth → content truth → depth → experience
Use it to: Order dependent repairs within one implementation.
Do not use it as: Not the portfolio-wide controller for unlike work.
Seven control priority classes
Which admissible intervention deserves attention next?
Governs: Constitutional blockers through theory work
Use it to: Classify unlike candidate actions after constitutional filtering.
Do not use it as: Not a numeric score and not a substitute for the repair stack.
Routing sequence
Classify the object before ordering the work.
- 01Contract family
Which publishing boundary owns the change?
- 02Invariant
What falsifiable condition must remain true?
- 03Probe state
PASS, FAIL, or UNMEASURED—never inferred from missing inputs.
- 04Ordering
Use the repair stack inside a surface; use a priority class across unlike interventions.
- 05Gate and receipt
Promotion depends on evidence from the release gates, not the selected priority label.
The observer is governed
A probe must disclose whether it can change the system it measures.
Every probe declares mutation_class as pure_read,read_with_side_effect, or active_perturbation. Missing required evidence isUNMEASURED, never PASS.