state
What holds and how it is valued
situationCore`: the named state of affairs and its kind · `status`: terms drawn from governed status schemes
This meta-model describes states of affairs that hold over time: a road is closed, a building is condemned, a supply is suspended, a district is under alert. It is the complement of the occurrence model: X1 records the instants at which the world changes, while this model records what holds between those instants, bound to a subject, valued with a status and bounded by a validity interval.
What holds and how it is valued
situationCore`: the named state of affairs and its kind · `status`: terms drawn from governed status schemes
When the state holds and how states succeed one another
interval`: the validity span, possibly open-ended · `succession`: transitions from one status to the next
What the state is about and how far it reaches
subjectBinding`: the link to the catalogue entity the state holds for · `scope`: the spatial or organizational reach of the state
Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.
Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.
Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.
CRUD procedures and interface bindings are not declared in this legacy version.
The owner archetype is the subject's owner: whoever holds the S1 ownership of the bound entity stewards situations about it. Attestations, monitoring and history access are all granted by that owner through S2, and every transition is auditable via S4.