{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-act-017","code":"wm-act-017-situation","url":"https://ver.cy/models/wm-act-017-situation/","name":"Situation","alternateNames":["X4"],"kind":"world-model","status":"published","version":"0.3.0","language":"en","classifiers":{"family":"World Models","category":"Activities and processes","entryKind":"entity","plane":"","domain":["ACT.SIT"],"industry":["Cross-industry"],"navPath":"NAV.ACT.SIT","tags":["situation","act.sit"],"facets":{}},"whatItIs":"One persistently identified situation thread about one primary subject and one declared condition dimension. Time-scoped assertions are attributed views of that situation, not guaranteed facts. Joint contexts use an explicit externally mastered collective subject. A situation can be planned, observed, inferred or disputed; its record lifecycle is separate from what holds in the world.","purpose":"Represent a state of affairs holding for an identified subject over time, with scoped assertions, evidence and revision history.","scope":{"in":["Situation identity and subject binding","Condition vocabulary, attributed assertions and bounded reach","Effective intervals, uncertain bounds, evidence freshness and retrospective revisions","Optional change-event and alert references, qualified views and local record governance"],"out":["Subject master data and ownership transfer","Occurrence, observation, phenomenon, risk and simulation lifecycles","Sensor operation, runtime evaluation, public alert delivery and physical intervention","Legal status creation, enforcement, operational emergency instructions and domain-specific medical determinations","Universal state ontology, executable mappings and certified instance validation"],"boundaries":[{"neighbor":"WM-ACT-015 Occurrence / Event","distinction":"A change may explain an interval boundary; occurrence identity and lifecycle remain external. Events are not assumed universally instantaneous and unknown triggers remain explicit."},{"neighbor":"WM-MAT-008 Observation / Measurement Record and WM-ACT-016 Observed Phenomenon","distinction":"Evidence records and phenomena are referenced. The situation is a scoped interpretation of what holds, not the observation activity, measured result or phenomenon master."},{"neighbor":"WM-VRT-003 Simulation and WM-KNW-015 Risk / Opportunity","distinction":"Scenario-scoped assertions may be represented but simulation execution and likelihood-impact assessment remain external. The registry risk parent pointer is a candidate taxonomic link, not mandatory containment or an objective model."},{"neighbor":"Alert and declaration records","distinction":"An alert announces information; its handling status, expiry or cancellation is not a generic world-state transition. Local recording does not issue a declaration."},{"neighbor":"Legacy X4 and unreviewed supplement","distinction":"Retain subject, state and interval concerns as design leads. Reject owner-equals-authority, identity derived from mutable begin time, latest-transition truth and compulsory known occurrence triggers. No legacy conformance claim is inherited."}]},"distinguishingFeatures":["Unlike WM-ACT-015 Occurrence / Event: A change may explain an interval boundary; occurrence identity and lifecycle remain external. Events are not assumed universally instantaneous and unknown triggers remain explicit.","Unlike WM-MAT-008 Observation / Measurement Record and WM-ACT-016 Observed Phenomenon: Evidence records and phenomena are referenced. The situation is a scoped interpretation of what holds, not the observation activity, measured result or phenomenon master.","Unlike WM-VRT-003 Simulation and WM-KNW-015 Risk / Opportunity: Scenario-scoped assertions may be represented but simulation execution and likelihood-impact assessment remain external. The registry risk parent pointer is a candidate taxonomic link, not mandatory containment or an objective model.","Unlike Alert and declaration records: An alert announces information; its handling status, expiry or cancellation is not a generic world-state transition. Local recording does not issue a declaration.","Unlike Legacy X4 and unreviewed supplement: Retain subject, state and interval concerns as design leads. Reject owner-equals-authority, identity derived from mutable begin time, latest-transition truth and compulsory known occurrence triggers. No legacy conformance claim is inherited."],"structure":{"bundles":[{"id":"sit-b-identity","name":"Identity and meaning","description":"Define the situation thread and the condition whose persistence is being described.","layers":[{"id":"sit-l-thread","name":"Situation identity context","description":"Proposed entity boundary: continuity belongs to an identified thread; revisions and assertion issuers have their own identifiers. A corrected start time does not create a new identity.","findings":[{"id":"sit-f-thread","name":"Situation identity","description":"Proposed entity boundary: continuity belongs to an identified thread; revisions and assertion issuers have their own identifiers. A corrected start time does not create a new identity.","questions":[{"text":"Which master identifier distinguishes this situation from another episode about the same subject?","id":"sit-f-thread-q1","kind":"identity"},{"text":"What condition dimension makes this one coherent situation thread?","id":"sit-f-thread-q2","kind":"definition"},{"text":"When does a recurrence require a new situation rather than a revision?","id":"sit-f-thread-q3","kind":"lifecycle"}]}]},{"id":"sit-l-meaning","name":"Condition scheme context","description":"Bind condition terms to a versioned vocabulary. Do not confuse a condition value with record approval state, evidence status, alert handling status or a physical measurement.","findings":[{"id":"sit-f-meaning","name":"Condition scheme","description":"Bind condition terms to a versioned vocabulary. Do not confuse a condition value with record approval state, evidence status, alert handling status or a physical measurement.","questions":[{"text":"Which scheme and version define the asserted condition term?","id":"sit-f-meaning-q1","kind":"classification"},{"text":"Which separate fields describe record review and confidence rather than the condition itself?","id":"sit-f-meaning-q2","kind":"state"},{"text":"Which combinations of condition terms are incompatible in this profile?","id":"sit-f-meaning-q3","kind":"constraint"}]}]}]},{"id":"sit-b-attachment","name":"Subject and reach","description":"Bind statements to the correct subject, parts and effective scope.","layers":[{"id":"sit-l-subject","name":"Primary subject context","description":"Use one primary subject reference per thread as a local design convention. A collective subject must be explicitly identified; membership and participant roles remain externally mastered.","findings":[{"id":"sit-f-subject","name":"Primary subject","description":"Use one primary subject reference per thread as a local design convention. A collective subject must be explicitly identified; membership and participant roles remain externally mastered.","questions":[{"text":"Which authoritative subject does this condition concern?","id":"sit-f-subject-q1","kind":"relationship"},{"text":"If several entities are involved, what defines the collective subject and its membership version?","id":"sit-f-subject-q2","kind":"composition"},{"text":"Who stewards the situation record and how is that role distinct from owning the subject?","id":"sit-f-subject-q3","kind":"ownership"}]}]},{"id":"sit-l-reach","name":"Effective reach context","description":"Scope can be spatial, organizational or a subset of a subject. Preserve scope revisions and exclusions; an alert audience is not the area in which a condition holds.","findings":[{"id":"sit-f-reach","name":"Effective reach","description":"Scope can be spatial, organizational or a subset of a subject. Preserve scope revisions and exclusions; an alert audience is not the area in which a condition holds.","questions":[{"text":"What part, area or organizational scope is affected by this assertion?","id":"sit-f-reach-q1","kind":"spatial"},{"text":"When does a revised extent become applicable?","id":"sit-f-reach-q2","kind":"temporal"},{"text":"How is partial overlap between two scope descriptions represented without assuming equal coverage?","id":"sit-f-reach-q3","kind":"validation"}]}]}]},{"id":"sit-b-time","name":"Validity and knowledge time","description":"Keep what holds when distinct from when information entered the record.","layers":[{"id":"sit-l-interval","name":"Validity interval context","description":"Interval bounds carry precision and basis. Unknown start, open end and forecast end are different states. No missing bound proves indefinite persistence.","findings":[{"id":"sit-f-interval","name":"Validity interval","description":"Interval bounds carry precision and basis. Unknown start, open end and forecast end are different states. No missing bound proves indefinite persistence.","questions":[{"text":"What are the begin and end bounds and the evidence basis for each?","id":"sit-f-interval-q1","kind":"temporal"},{"text":"Which endpoint inclusion and temporal reference rules apply?","id":"sit-f-interval-q2","kind":"constraint"},{"text":"How is uncertain or interrupted validity represented without fabricating exact instants?","id":"sit-f-interval-q3","kind":"exception"}]}]},{"id":"sit-l-knowledge","name":"Recording and revision time context","description":"Retain when an assertion was made, observed, received and superseded. Backdated validity is a correction with provenance, not a rewrite of what a consumer previously knew.","findings":[{"id":"sit-f-knowledge","name":"Recording and revision time","description":"Retain when an assertion was made, observed, received and superseded. Backdated validity is a correction with provenance, not a rewrite of what a consumer previously knew.","questions":[{"text":"When was this assertion observed, produced and recorded?","id":"sit-f-knowledge-q1","kind":"provenance"},{"text":"What changed in this revision and why was earlier effective time retained or corrected?","id":"sit-f-knowledge-q2","kind":"process"},{"text":"Which record revision was available at the requested knowledge-time cutoff?","id":"sit-f-knowledge-q3","kind":"temporal"}]}]}]},{"id":"sit-b-evidence","name":"Assertion and assurance","description":"Separate observations, interpretations and official claims, including disagreement and stale evidence.","layers":[{"id":"sit-l-basis","name":"Assertion basis context","description":"Each claim states whether it is observed, inferred, declared, planned or hypothetical. Those proposed basis codes need an adopter profile and do not establish truth or legal effect.","findings":[{"id":"sit-f-basis","name":"Assertion basis","description":"Each claim states whether it is observed, inferred, declared, planned or hypothetical. Those proposed basis codes need an adopter profile and do not establish truth or legal effect.","questions":[{"text":"Which evidence supports this particular condition assertion?","id":"sit-f-basis-q1","kind":"evidence"},{"text":"If a measurement informed the condition, which procedure and interpretation rule were used?","id":"sit-f-basis-q2","kind":"measurement"},{"text":"What gives this issuer authority to attest a declared status for this subject and interval?","id":"sit-f-basis-q3","kind":"authority"}]}]},{"id":"sit-l-quality","name":"Disagreement and freshness context","description":"Do not silently select the newest claim. Profile-specific freshness and authority checks can leave a current view unknown, stale or disputed; confidence scores require a defined meaning.","findings":[{"id":"sit-f-quality","name":"Disagreement and freshness","description":"Do not silently select the newest claim. Profile-specific freshness and authority checks can leave a current view unknown, stale or disputed; confidence scores require a defined meaning.","questions":[{"text":"What fitness and freshness criteria apply to reliance on this assertion?","id":"sit-f-quality-q1","kind":"quality"},{"text":"Which contrary assertions remain unresolved within overlapping validity and reach?","id":"sit-f-quality-q2","kind":"exception"},{"text":"What documented rule permits one assertion to be preferred for a particular view?","id":"sit-f-quality-q3","kind":"decision"}]}]}]},{"id":"sit-b-continuity","name":"Change and communication","description":"Record changes to assertions without confusing messaging with changes in the world.","layers":[{"id":"sit-l-change","name":"Change evidence context","description":"Reference opening, change and cessation evidence when known. Closure of a record, expiration of a forecast or silence from a source cannot alone prove cessation of the condition.","findings":[{"id":"sit-f-change","name":"Change evidence","description":"Reference opening, change and cessation evidence when known. Closure of a record, expiration of a forecast or silence from a source cannot alone prove cessation of the condition.","questions":[{"text":"What evidence indicates that the condition began, changed or ceased?","id":"sit-f-change-q1","kind":"event"},{"text":"Does this operation end the condition, retract an assertion or retire the local record?","id":"sit-f-change-q2","kind":"lifecycle"},{"text":"How are overlapping revisions, gaps and out-of-order updates reconciled?","id":"sit-f-change-q3","kind":"validation"}]}]},{"id":"sit-l-exchange","name":"Messages and projections context","description":"A recipient view preserves its cutoff, selected assertion and limitations. CAP is an optional message binding whose status and timing fields do not replace situation semantics.","findings":[{"id":"sit-f-exchange","name":"Messages and projections","description":"A recipient view preserves its cutoff, selected assertion and limitations. CAP is an optional message binding whose status and timing fields do not replace situation semantics.","questions":[{"text":"Which pinned mapping connects a received alert or exported view to this situation?","id":"sit-f-exchange-q1","kind":"interoperability"},{"text":"What does a message update, cancellation or expiry change in the local evidence view?","id":"sit-f-exchange-q2","kind":"state"},{"text":"Which provenance and uncertainty remain visible in a minimal status view for this recipient?","id":"sit-f-exchange-q3","kind":"access"}]}]}]},{"id":"sit-b-governance","name":"Governed maintenance","description":"Apply local authority, access and retention policies to sensitive situation assertions.","layers":[{"id":"sit-l-permission","name":"Permission to maintain context","description":"Attribution is not authorization. Local stewardship, evidence review and status-declaration authority are separate roles. Sensitive conditions require a documented purpose and access scope.","findings":[{"id":"sit-f-permission","name":"Permission to maintain","description":"Attribution is not authorization. Local stewardship, evidence review and status-declaration authority are separate roles. Sensitive conditions require a documented purpose and access scope.","questions":[{"text":"Which policy authorizes this actor to record, correct or retract this assertion?","id":"sit-f-permission-q1","kind":"authority"},{"text":"What sensitive information can this condition or its history reveal about an affected party?","id":"sit-f-permission-q2","kind":"privacy"},{"text":"How are unauthorized edits and exceptional access detected and reviewed?","id":"sit-f-permission-q3","kind":"security"}]}]},{"id":"sit-l-retirement","name":"Retention and retirement context","description":"Preserve necessary revision evidence under a qualified retention policy. Retirement removes a record from active views; lawful disposal of payloads is distinct from declaring a condition ended.","findings":[{"id":"sit-f-retirement","name":"Retention and retirement","description":"Preserve necessary revision evidence under a qualified retention policy. Retirement removes a record from active views; lawful disposal of payloads is distinct from declaring a condition ended.","questions":[{"text":"Which retention rule and holds govern assertions, evidence copies and recipient projections?","id":"sit-f-retirement-q1","kind":"retention"},{"text":"What remains resolvable when a situation is superseded, merged or lawfully disposed?","id":"sit-f-retirement-q2","kind":"process"},{"text":"Which checks must a consuming system pass before relying on a migrated situation?","id":"sit-f-retirement-q3","kind":"validation"}]}]}]}]},"agentConduct":{"may":["Register situation thread: Proposed local operation to create a scoped thread; does not create a real-world condition.","Attach attributed assertion: Proposed local operation to associate a claim and its evidence.","Revise assertion record: Proposed local correction preserving prior knowledge and effective times.","Record reliance assessment: Proposed local recording of a profile-qualified assessment supplied by a reviewer or referenced evaluator.","Build scoped view: Proposed read operation selecting only eligible assertions under a pinned policy.","Retire local thread: Proposed local retirement and disposition assessment; deletion execution follows the adopting policy."],"mustNot":["Separate actual, planned and hypothetical contexts; never silently promote simulation output to an observed fact.","Deny access unless a role and purpose policy grants the requested scope; possession of a subject identifier is not a grant."],"requiresHuman":[]},"ethics":{"considerations":["Adopter review required for jurisdiction, regulated status, privacy and retention profiles.","Domain-specific authority, closure, freshness, temporal precision, legal applicability and privacy requirements need expert profile review."],"affectedParties":[]},"owners":{"steward":"Name a role-based situation record steward and authoritative master namespace.","roles":[{"name":"Situation steward","responsibilities":["Maintains the local thread, subject binding and continuity rules."]},{"name":"Attesting authority","responsibilities":["Provides evidence of a scoped mandate for official assertions."]},{"name":"Evidence reviewer","responsibilities":["Assesses support, contradiction and freshness without assuming ownership implies authority."]},{"name":"Access custodian","responsibilities":["Applies recipient permissions and time-limited exceptions."]},{"name":"Records custodian","responsibilities":["Applies retention, holds and authorized disposition."]}],"masterSystems":[]},"relations":[{"target":"WM-ACT-015","type":"references","note":"Candidate optional occurrence link for change evidence; event lifecycle stays external."},{"target":"WM-ACT-016","type":"references","note":"Candidate phenomenon link, without importing its observation or physical dynamics."},{"target":"WM-MAT-008","type":"references","note":"Candidate evidence-record link; measurement acquisition and source units stay with the observation master."},{"target":"WM-XCT-009","type":"references","note":"Candidate temporal profile reference; calendar rules are not owned here."},{"target":"WM-KNW-015","type":"references","note":"Optional related risk record. Registry parent pointer does not mandate containment; risk assessment stays external."},{"target":"WM-VRT-003","type":"references","note":"Optional scenario origin for hypothetical assertions; no inheritance from simulation or ownership of its runtime."},{"target":"https://www.w3.org/TR/2017/REC-owl-time-20171019/","type":"aligned","note":"Conceptual temporal alignment only; operational endpoint rules need a tested binding."},{"target":"https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html","type":"aligned","note":"Optional alert profile; preserve message identity, separate information and condition validity, and explicitly transform timestamp conventions."},{"target":"WM-ACT-015 Occurrence / Event","type":"neighbor","note":"A change may explain an interval boundary; occurrence identity and lifecycle remain external. Events are not assumed universally instantaneous and unknown triggers remain explicit."},{"target":"WM-MAT-008 Observation / Measurement Record and WM-ACT-016 Observed Phenomenon","type":"neighbor","note":"Evidence records and phenomena are referenced. The situation is a scoped interpretation of what holds, not the observation activity, measured result or phenomenon master."},{"target":"WM-VRT-003 Simulation and WM-KNW-015 Risk / Opportunity","type":"neighbor","note":"Scenario-scoped assertions may be represented but simulation execution and likelihood-impact assessment remain external. The registry risk parent pointer is a candidate taxonomic link, not mandatory containment or an objective model."},{"target":"Alert and declaration records","type":"neighbor","note":"An alert announces information; its handling status, expiry or cancellation is not a generic world-state transition. Local recording does not issue a declaration."},{"target":"Legacy X4 and unreviewed supplement","type":"neighbor","note":"Retain subject, state and interval concerns as design leads. Reject owner-equals-authority, identity derived from mutable begin time, latest-transition truth and compulsory known occurrence triggers. No legacy conformance claim is inherited."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier","Governed global identifier or IRI","Dimension-assigned UUID or ULID"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":[]},"capabilities":{"applicability":"required","items":["Register situation thread: Proposed local operation to create a scoped thread; does not create a real-world condition.","Attach attributed assertion: Proposed local operation to associate a claim and its evidence.","Revise assertion record: Proposed local correction preserving prior knowledge and effective times.","Record reliance assessment: Proposed local recording of a profile-qualified assessment supplied by a reviewer or referenced evaluator.","Build scoped view: Proposed read operation selecting only eligible assertions under a pinned policy.","Retire local thread: Proposed local retirement and disposition assessment; deletion execution follows the adopting policy."]},"hazards":{"applicability":"optional","items":[]},"interfaces":{"applicability":"required","items":["PROV-O: The PROV Ontology"]},"context":{"applicability":"required","items":["No jurisdiction-specific legal powers are inferred. CAP is used only as an alert-domain example.","Owner, issuer and steward may differ; the registry owner archetype is not an authorization rule."]}},"sources":[{"title":"Time Ontology in OWL","url":"https://www.w3.org/TR/2017/REC-owl-time-20171019/","note":"W3C"},{"title":"Semantic Sensor Network Ontology","url":"https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/","note":"W3C"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/2013/REC-prov-o-20130430/","note":"W3C"},{"title":"Common Alerting Protocol Version 1.2","url":"https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html","note":"OASIS"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"IETF"},{"title":"SKOS Simple Knowledge Organization System Reference","url":"https://www.w3.org/TR/2009/REC-skos-reference-20090818/","note":"W3C"},{"title":"Data on the Web Best Practices: Data Quality Vocabulary","url":"https://www.w3.org/TR/2016/NOTE-vocab-dqv-20161215/","note":"W3C"}],"openQuestions":["Restore independent external review and verify admitted source versions, errata, claims and application suitability before any canonical promotion.","Build adoption profiles and adversarial fixtures for contradictory issuers, uncertain bounds, moving collective scope, stale open intervals, cancelled alerts, retrospective corrections and lawful erasure.","Implement and test nested schemas and loss-aware mappings, including the CAP/RFC 3339 timestamp distinction and optional registry relationships.","Executable nested schemas, test fixtures and round-trip mappings are not provided.","Domain-specific authority, closure, freshness, temporal precision, legal applicability and privacy requirements need expert profile review.","Non-Gregorian temporal bindings, moving collective membership and complex recurrent episodes require further profiles.","Cross-language concept equivalence, causal inference and calibrated confidence are not established.","Seven sources cover selected concepts, not all possible kinds of situations."],"resources":{"spec":"/models/wm-act-017-situation/spec.yaml","agents":"/models/wm-act-017-situation/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-017"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-act-017-situation/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-06T14:23:09Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"derived","structure":"filled","agentConduct":"derived","ethics":"derived","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"missing","interaction.capabilities":"filled","interaction.hazards":"missing","interaction.interfaces":"derived","interaction.context":"filled","sources":"filled"},"notes":{"distinguishingFeatures":"Derived from boundary notes against neighbouring models.","agentConduct":"Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.","ethics":"Sentences mentioning harm, privacy, consent or similar, collected from the specification.","interaction.properties":"Institutional or informational subject: no invented physical properties."},"score":0.75}}