From a vocabulary to a governed decision
Naming a state does not establish who may declare it. A useful implementation also identifies the governing authority, the evidence it accepts, and what each consuming surface may do with the result.
This is an explanatory design argument. It does not claim that earlier standards lack governance, that every industry has an unwritten state machine, or that Constitutional CMS invented these ideas.
Keep the questions separate
An entity may exist even when a claim about it is unavailable. A relationship may be absent without retiring either endpoint. A document may be withheld under its family contract without erasing the entity. Delivery of a document does not prove that a reader found it useful or that an external outcome improved.
Those distinctions need domain-specific authority. A public protocol can define the interface and falsification examples; the implementation supplies its own source mappings, policies and evidence.
A bounded example
Synthetic illustration: a catalog entry exists, but its current availability observation has expired. The availability claim is withheld. Other independently authorized claims may remain visible if the document’s governing contract permits it. Neither the stale claim nor a failed fetch is an authorized retirement decision.
This example demonstrates a distinction, not a measured production result.
Use the released protocol
The protocol map is the source for the framework’s existing schemes. This essay introduces no new canonical vocabulary, maturity sequence, score or certification mechanism.
Check a public page, then collect your own evidence and evaluate it locally. A private adapter may translate domain authority into normalized records without exposing private queries, thresholds or operating evidence.
Signal Contract remains a separate boundary for presentation of governed state. A renderer does not author new claims, and a displayed receipt does not grant authority.