# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T14:23:09Z", "synthesisSha256": "5978b0ce3d9e5d6f6529b660f5cc401478ff7f78d80e7a06cd9a8dba53ec822c", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-017", "registryId": "vr.wm-act-017", "name": "Situation", "version": "0.3.0", "previousVersions": [ { "version": "0.2.0-legacy", "url": "https://github.com/ver-cy/world-models/blob/feat/mega-model-registry/models/events-phenomena/X4-situation-and-condition.md" } ], "entryKind": "entity", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.SIT" ], "tags": [ "situation", "act.sit" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-017-situation/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-017", "model": { "registry_id": "vr.wm-act-017", "model_id": "WM-ACT-017", "name": "Situation", "entry_kind": "entity", "purpose": "Represent a state of affairs holding for an identified subject over time, with scoped assertions, evidence and revision history.", "scope_statement": "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.", "in_scope": [ "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_of_scope": [ "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" ], "boundary_notes": [ { "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.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "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.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "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.", "source_refs": [ "SRC-002", "SRC-007" ] }, { "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.", "source_refs": [ "SRC-004" ] }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Time Ontology in OWL", "organization": "W3C", "url": "https://www.w3.org/TR/2017/REC-owl-time-20171019/", "version_or_date": "Recommendation 2017-10-19", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:21:37Z", "relevance": "Intervals, instants, temporal reference systems and interval relations; not a complete situation ontology." }, { "id": "SRC-002", "title": "Semantic Sensor Network Ontology", "organization": "W3C", "url": "https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/", "version_or_date": "Recommendation 2017-10-19", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:21:37Z", "relevance": "Observation, feature of interest, procedure, phenomenon time and result time; interpretation is separate from sensing." }, { "id": "SRC-003", "title": "PROV-O: The PROV Ontology", "organization": "W3C", "url": "https://www.w3.org/TR/2013/REC-prov-o-20130430/", "version_or_date": "Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:21:37Z", "relevance": "Attribution, derivation, revision and specialization support evidence lineage, without certifying truth or permission." }, { "id": "SRC-004", "title": "Common Alerting Protocol Version 1.2", "organization": "OASIS", "url": "https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html", "version_or_date": "OASIS Standard 2010-07-01", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:21:37Z", "relevance": "Alert identity, handling status, updates, cancellation, targeting and information timing. A limited alert-domain alignment, not the generic situation root." }, { "id": "SRC-005", "title": "Date and Time on the Internet: Timestamps", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:21:37Z", "relevance": "Timestamp syntax and offset semantics. Does not define intervals or domain validity. CAP timestamp conversion needs an explicit binding." }, { "id": "SRC-006", "title": "SKOS Simple Knowledge Organization System Reference", "organization": "W3C", "url": "https://www.w3.org/TR/2009/REC-skos-reference-20090818/", "version_or_date": "Recommendation 2009-08-18", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:21:37Z", "relevance": "Concept identifiers, schemes, labels and mappings; closed value sets and transition rules need a separate profile." }, { "id": "SRC-007", "title": "Data on the Web Best Practices: Data Quality Vocabulary", "organization": "W3C", "url": "https://www.w3.org/TR/2016/NOTE-vocab-dqv-20161215/", "version_or_date": "Working Group Note 2016-12-15, non-normative", "source_type": "ontology", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T14:21:37Z", "relevance": "Quality annotations, metrics and fitness for use; a descriptive Note, not a universal confidence scale or certification." } ], "structure": { "bundles": [ { "id": "sit-b-identity", "name": "Identity and meaning", "description": "Define the situation thread and the condition whose persistence is being described.", "rationale": "Proposed local grouping grounded in the cited concepts; it is not a structure prescribed by an external standard.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "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.", "source_refs": [ "SRC-001", "SRC-003" ], "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.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "sit-f-thread-q1", "kind": "identity", "text": "Which master identifier distinguishes this situation from another episode about the same subject?", "answer_data": [ "Master namespace", "Situation identifier", "Recurrence or split criterion" ] }, { "id": "sit-f-thread-q2", "kind": "definition", "text": "What condition dimension makes this one coherent situation thread?", "answer_data": [ "Condition definition", "Primary subject reference", "Granularity rationale" ] }, { "id": "sit-f-thread-q3", "kind": "lifecycle", "text": "When does a recurrence require a new situation rather than a revision?", "answer_data": [ "Continuity policy", "Prior situation link", "Merge or split decision and reviewer" ] } ], "data_elements": [ { "id": "sit-f-thread-d1", "name": "situation_id", "description": "Stable identity assigned independently of mutable times.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "sit-f-thread-d2", "name": "continuity_rule", "description": "Profile rule for recurrence, split, merge and alias handling.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "sit-f-thread-artifact", "name": "Situation identity record", "description": "Versioned local evidence view for situation identity. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-006", "SRC-004" ], "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.", "source_refs": [ "SRC-006", "SRC-004" ], "questions": [ { "id": "sit-f-meaning-q1", "kind": "classification", "text": "Which scheme and version define the asserted condition term?", "answer_data": [ "Scheme identifier", "Version", "Term identifier", "Definition" ] }, { "id": "sit-f-meaning-q2", "kind": "state", "text": "Which separate fields describe record review and confidence rather than the condition itself?", "answer_data": [ "Condition value", "Review state", "Assertion basis", "Quality qualifier" ] }, { "id": "sit-f-meaning-q3", "kind": "constraint", "text": "Which combinations of condition terms are incompatible in this profile?", "answer_data": [ "Exclusivity rule", "Applicable scope", "Unknown or unmapped term behavior" ] } ], "data_elements": [ { "id": "sit-f-meaning-d1", "name": "condition_scheme", "description": "Pinned scheme with explicit local value-set constraints.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-004" ] }, { "id": "sit-f-meaning-d2", "name": "condition_term", "description": "Condition code or explicit unknown; labels do not establish equivalence.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-004" ] } ], "artifacts": [ { "id": "sit-f-meaning-artifact", "name": "Condition binding", "description": "Versioned local evidence view for condition scheme. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-006", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "sit-b-attachment", "name": "Subject and reach", "description": "Bind statements to the correct subject, parts and effective scope.", "rationale": "Proposed local grouping grounded in the cited concepts; it is not a structure prescribed by an external standard.", "source_refs": [ "SRC-002", "SRC-004" ], "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.", "source_refs": [ "SRC-002", "SRC-003" ], "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.", "source_refs": [ "SRC-002", "SRC-003" ], "questions": [ { "id": "sit-f-subject-q1", "kind": "relationship", "text": "Which authoritative subject does this condition concern?", "answer_data": [ "Subject master ID", "Model or type", "Binding basis", "Resolution status" ] }, { "id": "sit-f-subject-q2", "kind": "composition", "text": "If several entities are involved, what defines the collective subject and its membership version?", "answer_data": [ "Collective subject reference", "Membership snapshot reference", "Participant roles", "Not applicable reason" ] }, { "id": "sit-f-subject-q3", "kind": "ownership", "text": "Who stewards the situation record and how is that role distinct from owning the subject?", "answer_data": [ "Record steward role", "Subject owner reference if applicable", "Delegation evidence" ] } ], "data_elements": [ { "id": "sit-f-subject-d1", "name": "subject_ref", "description": "Primary subject including target namespace and unresolved-reference flag.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "sit-f-subject-d2", "name": "membership_ref", "description": "Externally mastered collective subject membership when applicable.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "sit-f-subject-artifact", "name": "Subject binding record", "description": "Versioned local evidence view for primary subject. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-004", "SRC-002" ], "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.", "source_refs": [ "SRC-004", "SRC-002" ], "questions": [ { "id": "sit-f-reach-q1", "kind": "spatial", "text": "What part, area or organizational scope is affected by this assertion?", "answer_data": [ "Scope type", "Extent or master reference", "Exclusions", "Coordinate reference system if geometric" ] }, { "id": "sit-f-reach-q2", "kind": "temporal", "text": "When does a revised extent become applicable?", "answer_data": [ "Scope revision", "Effective interval", "Recorded time", "Superseded scope" ] }, { "id": "sit-f-reach-q3", "kind": "validation", "text": "How is partial overlap between two scope descriptions represented without assuming equal coverage?", "answer_data": [ "Intersection assessment reference", "Resolution and method", "Uncertain boundaries", "Coverage limitations" ] } ], "data_elements": [ { "id": "sit-f-reach-d1", "name": "scope_binding", "description": "Typed effective-dated reach and exclusions, with external geometry reference if used.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-002" ] }, { "id": "sit-f-reach-d2", "name": "scope_quality", "description": "Precision and unresolved extent issues, not a location inferred from a label.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-002" ] } ], "artifacts": [ { "id": "sit-f-reach-artifact", "name": "Reach revision", "description": "Versioned local evidence view for effective reach. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-004", "SRC-002" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "sit-b-time", "name": "Validity and knowledge time", "description": "Keep what holds when distinct from when information entered the record.", "rationale": "Proposed local grouping grounded in the cited concepts; it is not a structure prescribed by an external standard.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "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.", "source_refs": [ "SRC-001", "SRC-005" ], "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.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "sit-f-interval-q1", "kind": "temporal", "text": "What are the begin and end bounds and the evidence basis for each?", "answer_data": [ "Bounds", "Observed, estimated or planned basis", "Precision", "Open or unknown marker" ] }, { "id": "sit-f-interval-q2", "kind": "constraint", "text": "Which endpoint inclusion and temporal reference rules apply?", "answer_data": [ "Inclusive or exclusive boundaries", "Calendar or reference system", "Zero-duration handling", "Offset" ] }, { "id": "sit-f-interval-q3", "kind": "exception", "text": "How is uncertain or interrupted validity represented without fabricating exact instants?", "answer_data": [ "Bound ranges", "Disjoint interval references or separate episode IDs", "Uncertainty rationale" ] } ], "data_elements": [ { "id": "sit-f-interval-d1", "name": "validity", "description": "Candidate interval object with bound kind, value, precision and inclusion flags.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "sit-f-interval-d2", "name": "temporal_profile", "description": "Pinned reference system and normalization policy.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "sit-f-interval-artifact", "name": "Validity statement", "description": "Versioned local evidence view for validity interval. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "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.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "sit-f-knowledge-q1", "kind": "provenance", "text": "When was this assertion observed, produced and recorded?", "answer_data": [ "Observation or phenomenon time", "Result time", "Assertion time", "Ingestion time", "Clock uncertainty" ] }, { "id": "sit-f-knowledge-q2", "kind": "process", "text": "What changed in this revision and why was earlier effective time retained or corrected?", "answer_data": [ "Prior revision", "Changed fields", "Reason", "Actor", "Evidence", "Concurrency token" ] }, { "id": "sit-f-knowledge-q3", "kind": "temporal", "text": "Which record revision was available at the requested knowledge-time cutoff?", "answer_data": [ "Knowledge cutoff", "Revision chain", "Supersession time", "Unavailable-history marker" ] } ], "data_elements": [ { "id": "sit-f-knowledge-d1", "name": "recorded_at", "description": "Ingestion timestamp distinct from assertion and validity time.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "sit-f-knowledge-d2", "name": "revision_lineage", "description": "Prior revision and attribution; lawful redaction may constrain history access.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "sit-f-knowledge-artifact", "name": "Assertion revision ledger", "description": "Versioned local evidence view for recording and revision time. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "sit-b-evidence", "name": "Assertion and assurance", "description": "Separate observations, interpretations and official claims, including disagreement and stale evidence.", "rationale": "Proposed local grouping grounded in the cited concepts; it is not a structure prescribed by an external standard.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ], "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.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "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.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "questions": [ { "id": "sit-f-basis-q1", "kind": "evidence", "text": "Which evidence supports this particular condition assertion?", "answer_data": [ "Evidence references", "Relevant extracts or locators", "Supporting and contrary role", "Access constraints" ] }, { "id": "sit-f-basis-q2", "kind": "measurement", "text": "If a measurement informed the condition, which procedure and interpretation rule were used?", "answer_data": [ "Observation reference", "Units and uncertainty in source", "Rule version", "Threshold context", "Not applicable reason" ] }, { "id": "sit-f-basis-q3", "kind": "authority", "text": "What gives this issuer authority to attest a declared status for this subject and interval?", "answer_data": [ "Issuer role", "Mandate or delegation reference", "Jurisdiction and scope", "Verification state" ] } ], "data_elements": [ { "id": "sit-f-basis-d1", "name": "assertion_id", "description": "Distinct attributed claim identity within the situation thread.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "sit-f-basis-d2", "name": "basis_and_evidence", "description": "Basis code, issuer, evidence references and optional derivation rule; unknown allowed.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "sit-f-basis-artifact", "name": "Attributed assertion", "description": "Versioned local evidence view for assertion basis. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-007", "SRC-003" ], "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.", "source_refs": [ "SRC-007", "SRC-003" ], "questions": [ { "id": "sit-f-quality-q1", "kind": "quality", "text": "What fitness and freshness criteria apply to reliance on this assertion?", "answer_data": [ "Quality metric definition", "Evidence age limit", "Review due time", "Intended use", "Assessment result" ] }, { "id": "sit-f-quality-q2", "kind": "exception", "text": "Which contrary assertions remain unresolved within overlapping validity and reach?", "answer_data": [ "Competing assertion IDs", "Overlap basis", "Conflict classification", "Resolution or unresolved reason" ] }, { "id": "sit-f-quality-q3", "kind": "decision", "text": "What documented rule permits one assertion to be preferred for a particular view?", "answer_data": [ "Selection policy version", "Reviewer or delegated evaluator", "Excluded candidates and reasons", "No-selection outcome" ] } ], "data_elements": [ { "id": "sit-f-quality-d1", "name": "quality_assessment", "description": "Metric and freshness assessment references with evaluation time.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-003" ] }, { "id": "sit-f-quality-d2", "name": "disputes", "description": "Explicit competing claims and scoped disposition; no last-write-wins truth rule.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-003" ] } ], "artifacts": [ { "id": "sit-f-quality-artifact", "name": "Reliance assessment", "description": "Versioned local evidence view for disagreement and freshness. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-007", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "sit-b-continuity", "name": "Change and communication", "description": "Record changes to assertions without confusing messaging with changes in the world.", "rationale": "Proposed local grouping grounded in the cited concepts; it is not a structure prescribed by an external standard.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "questions": [ { "id": "sit-f-change-q1", "kind": "event", "text": "What evidence indicates that the condition began, changed or ceased?", "answer_data": [ "Change type", "Effective time or range", "Optional occurrence reference", "Unknown trigger reason" ] }, { "id": "sit-f-change-q2", "kind": "lifecycle", "text": "Does this operation end the condition, retract an assertion or retire the local record?", "answer_data": [ "Operation category", "Target assertion or thread", "Evidence", "Consequences for projections" ] }, { "id": "sit-f-change-q3", "kind": "validation", "text": "How are overlapping revisions, gaps and out-of-order updates reconciled?", "answer_data": [ "Expected revision", "Interval consistency result", "Duplicate detection", "Conflict or refusal report" ] } ], "data_elements": [ { "id": "sit-f-change-d1", "name": "change_links", "description": "Optional external occurrences and qualified causal claims; temporal succession alone is not causation.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "sit-f-change-d2", "name": "closure_basis", "description": "Separate cessation evidence, retraction reason and record retirement state.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "sit-f-change-artifact", "name": "Change qualification", "description": "Versioned local evidence view for change evidence. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "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.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "sit-f-exchange-q1", "kind": "interoperability", "text": "Which pinned mapping connects a received alert or exported view to this situation?", "answer_data": [ "Mapping version", "External message identity", "Field correspondence", "Loss report" ] }, { "id": "sit-f-exchange-q2", "kind": "state", "text": "What does a message update, cancellation or expiry change in the local evidence view?", "answer_data": [ "Referenced message IDs", "Information validity", "Condition impact evidence or none", "Review result" ] }, { "id": "sit-f-exchange-q3", "kind": "access", "text": "Which provenance and uncertainty remain visible in a minimal status view for this recipient?", "answer_data": [ "Recipient scope", "As-of and known-at cutoffs", "Assertion ID", "Freshness and dispute markers", "Redaction notice" ] } ], "data_elements": [ { "id": "sit-f-exchange-d1", "name": "message_links", "description": "External identifiers and binding details; multiple messages may concern one situation.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "sit-f-exchange-d2", "name": "projection_context", "description": "Recipient policy, cutoffs, selection rule and limitations.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "sit-f-exchange-artifact", "name": "Scoped status view", "description": "Versioned local evidence view for messages and projections. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "sit-b-governance", "name": "Governed maintenance", "description": "Apply local authority, access and retention policies to sensitive situation assertions.", "rationale": "Proposed local grouping grounded in the cited concepts; it is not a structure prescribed by an external standard.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "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.", "source_refs": [ "SRC-003", "SRC-004" ], "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.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "sit-f-permission-q1", "kind": "authority", "text": "Which policy authorizes this actor to record, correct or retract this assertion?", "answer_data": [ "Role", "Policy version", "Permitted operation", "Scope", "Delegation validity" ] }, { "id": "sit-f-permission-q2", "kind": "privacy", "text": "What sensitive information can this condition or its history reveal about an affected party?", "answer_data": [ "Sensitivity category", "Purpose", "Minimization rule", "Disclosure review" ] }, { "id": "sit-f-permission-q3", "kind": "security", "text": "How are unauthorized edits and exceptional access detected and reviewed?", "answer_data": [ "Authorization outcome reference", "Audit event reference", "Exception expiry", "Reviewer" ] } ], "data_elements": [ { "id": "sit-f-permission-d1", "name": "maintenance_policy", "description": "Adopter-owned permission and sensitivity binding; no rights inferred from a source citation.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "sit-f-permission-d2", "name": "exception_refs", "description": "Authorized and time-limited access exception evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "sit-f-permission-artifact", "name": "Maintenance authority binding", "description": "Versioned local evidence view for permission to maintain. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-003", "SRC-007" ], "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.", "source_refs": [ "SRC-003", "SRC-007" ], "questions": [ { "id": "sit-f-retirement-q1", "kind": "retention", "text": "Which retention rule and holds govern assertions, evidence copies and recipient projections?", "answer_data": [ "Retention policy reference", "Trigger and duration", "Hold scope", "Responsible role" ] }, { "id": "sit-f-retirement-q2", "kind": "process", "text": "What remains resolvable when a situation is superseded, merged or lawfully disposed?", "answer_data": [ "Successor or alias link", "Minimal tombstone", "Redacted history marker", "Disposition evidence" ] }, { "id": "sit-f-retirement-q3", "kind": "validation", "text": "Which checks must a consuming system pass before relying on a migrated situation?", "answer_data": [ "Identity map", "Semantic loss report", "Access preservation", "Cutoff and conflict fixtures", "Reviewer" ] } ], "data_elements": [ { "id": "sit-f-retirement-d1", "name": "retention_binding", "description": "Adopter policy reference with scoped holds and disposal authority.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "sit-f-retirement-d2", "name": "retirement_record", "description": "Reason, successor, lawful tombstone and disposal receipt references as applicable.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "sit-f-retirement-artifact", "name": "Retirement assessment", "description": "Versioned local evidence view for retention and retirement. Preserve source references, access scope, unknowns and revision identity; not an authoritative external act.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier, then governed IRI, then Dimension-assigned UUID or ULID; separate revision identifier, never a date-derived identity.", "source_refs": [ "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "sit-op-register", "name": "Register situation thread", "description": "Proposed local operation to create a scoped thread; does not create a real-world condition.", "inputs": [ "Master subject reference", "Condition scheme and continuity rule" ], "outputs": [ "New thread and initial revision or refusal" ], "preconditions": [ "Resolved or explicitly unresolved subject", "Authorized steward", "Duplicate check" ], "effects": [ "Create local identity without asserting truth" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "sit-op-attach", "name": "Attach attributed assertion", "description": "Proposed local operation to associate a claim and its evidence.", "inputs": [ "Thread ID", "Issuer and basis", "Validity and reach", "Evidence links" ], "outputs": [ "Attributed assertion or rejection report" ], "preconditions": [ "Evidence access allowed", "Scheme binding checked", "Mandate evidence for declared status" ], "effects": [ "Append assertion; retain contrary claims" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "sit-op-revise", "name": "Revise assertion record", "description": "Proposed local correction preserving prior knowledge and effective times.", "inputs": [ "Expected revision", "Field patch", "Correction basis" ], "outputs": [ "New revision or concurrency conflict" ], "preconditions": [ "Authorized editor", "Current revision matches", "Interval and scope checks pass" ], "effects": [ "Append correction and invalidate affected cached views; no external action" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "sit-op-assess", "name": "Record reliance assessment", "description": "Proposed local recording of a profile-qualified assessment supplied by a reviewer or referenced evaluator.", "inputs": [ "Assertion candidates", "Policy version", "Assessment evidence" ], "outputs": [ "Assessment with unresolved issues or refusal" ], "preconditions": [ "Reviewer authority", "Defined metrics", "Both validity and knowledge cutoffs supplied" ], "effects": [ "Record assessed usability; do not certify truth or execute domain evaluation" ], "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "sit-op-project", "name": "Build scoped view", "description": "Proposed read operation selecting only eligible assertions under a pinned policy.", "inputs": [ "Subject and condition", "As-of time", "Known-at time", "Recipient scope" ], "outputs": [ "Qualified status view or unknown, stale, disputed, or denied outcome" ], "preconditions": [ "Access policy checked", "Cutoffs explicit", "Selection policy pinned" ], "effects": [ "Produce local view with source and loss markers; no public alert delivery" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "sit-op-retire", "name": "Retire local thread", "description": "Proposed local retirement and disposition assessment; deletion execution follows the adopting policy.", "inputs": [ "Thread revision", "Reason", "Retention and hold assessment" ], "outputs": [ "Retirement record or blocked disposition" ], "preconditions": [ "Authorized custodian", "References and holds checked", "Successor mapping reviewed" ], "effects": [ "Remove from active views and retain lawful minimal lineage; do not lift an official status" ], "source_refs": [ "SRC-003", "SRC-007" ] } ], "composition": [ { "target": "WM-ACT-015", "relation": "REFERENCE", "purpose": "Candidate optional occurrence link for change evidence; event lifecycle stays external.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-ACT-016", "relation": "REFERENCE", "purpose": "Candidate phenomenon link, without importing its observation or physical dynamics.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-MAT-008", "relation": "REFERENCE", "purpose": "Candidate evidence-record link; measurement acquisition and source units stay with the observation master.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "WM-XCT-009", "relation": "REFERENCE", "purpose": "Candidate temporal profile reference; calendar rules are not owned here.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "WM-KNW-015", "relation": "REFERENCE", "purpose": "Optional related risk record. Registry parent pointer does not mandate containment; risk assessment stays external.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "WM-VRT-003", "relation": "REFERENCE", "purpose": "Optional scenario origin for hypothetical assertions; no inheritance from simulation or ownership of its runtime.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "https://www.w3.org/TR/2017/REC-owl-time-20171019/", "relation": "ALIGN", "purpose": "Conceptual temporal alignment only; operational endpoint rules need a tested binding.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html", "relation": "ALIGN", "purpose": "Optional alert profile; preserve message identity, separate information and condition validity, and explicitly transform timestamp conventions.", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Name a role-based situation record steward and authoritative master namespace.", "Pin subject bindings, condition vocabulary, continuity rules and temporal profile.", "Declare separate authority for attestation, record maintenance, access and disposition.", "Supply purpose, sensitivity, retention, freshness and conflict-selection policies before operational adoption." ], "namespace_guidance": "Use a governed situation namespace with stable identifiers and separate assertion/revision IDs. The subject owner is a possible steward, not automatically the declaring authority.", "registry_links": [ "vr.wm-act-017", "Legacy X4 mapping requires explicit migration review.", "No WM-ACT-017 edge was found in the relationship ledger; proposed references remain unratified." ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve master identity, attributed source values and explicit unknowns. Normalize a view only under a pinned vocabulary and temporal policy.", "Do not collapse disagreeing issuers or record review state into a single condition fact." ], "patch_rules": [ "Require expected revision, actor, reason, scope and evidence; append corrections with both effective and recorded time.", "Apply approved identity merges through aliases and explicit successor maps, never by reusing a date or label." ], "compatibility_rules": [ "Treat changes to continuity, bound inclusion, authority precedence or term meaning as semantic migrations requiring review.", "Preserve unmapped codes and source payload references; report projection loss and deny unsupported operational conversions." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "Dimension-assigned UUID or ULID" ], "timestamp_rule": "Represent exact instants with RFC 3339 seconds and an explicit offset or Z. Distinguish event/effective time from observation, result and ingestion time. Preserve source precision, unknown offsets and uncertain bounds; never invent seconds for an imprecise date.", "serial_naming_rule": "Use stable situation, assertion and revision identifiers with an independent sequence; dates may be display metadata only.", "integrity_rule": "Hash serialized evidence where permitted and bind its revision and issuer. A hash proves byte integrity only. Redaction and disposal leave lawful minimal markers, not a promise of eternal payload preservation." }, "policies": [ "Local design policy: no condition is presumed true merely because it is latest, signed or within an open interval.", "No public declaration, alert delivery, enforcement or physical intervention is authorized by a local function.", "Separate actual, planned and hypothetical contexts; never silently promote simulation output to an observed fact.", "Apply least privilege, purpose limitation and minimization to situation and history views; profile-specific legal review remains a hold.", "CAP 1.2 uses a timestamp profile differing from RFC 3339 offset interpretation. Preserve lexical input and mapping provenance; do not blindly reinterpret -00:00 or assume Z is accepted in CAP." ], "crud": { "read": [ "Check recipient scope and return cutoffs, selected assertion identity, uncertainty and freshness with every status view." ], "create": [ "Check role authority, master subject, condition scheme and duplicate continuity before creating a local thread." ], "update": [ "Require expected revision and auditable correction basis. Concurrent claims may coexist without overwriting truth." ], "delete": [ "Retire local records separately from cessation of the condition. Retention and holds determine whether payload deletion is lawful.", "The adopting Dimension retention service owns deletion execution, copies and downstream disposition. Retain only a lawful minimal tombstone and permitted lineage; record inaccessible or disposed evidence honestly." ] }, "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." ] } ], "access": { "default_rule": "Deny access unless a role and purpose policy grants the requested scope; possession of a subject identifier is not a grant.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency or exceptional access needs a recorded basis, limited scope, expiry and subsequent review under the adopter policy." ], "audit_requirements": [ "Record actor, purpose, policy version, target revision, decision and time for reads and writes as required by policy.", "Audit records remain externally mastered; record their references and protect sensitive histories." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Owner role", "Authority policy", "Evidence and freshness policy" ], "read_order": [ "AGENTS.md", "spec.yaml", "Adopting Dimension and access policies", "Pinned subject, evidence and vocabulary references", "Current revision and applicable holds" ] } }, "coverage": { "claim": "Source-grounded proposed Situation entity covering stable threads, scoped assertions, evidence, validity and knowledge time, change references and local governance. A separate frozen no-tools Codex self-audit accepted this as a noncanonical reviewable draft. Independent review, live source/version verification, adoption profiles and executable conformance remain open; no universal state ontology is claimed.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Thread, assertion and revision identities are separate; mutable begin time never establishes identity." }, { "dimension": "lifecycle", "status": "covered", "notes": "Condition cessation, assertion retraction and local retirement are distinct." }, { "dimension": "relationships", "status": "covered", "notes": "Optional evidence and event references preserve external ownership; candidate edges need ratification." }, { "dimension": "temporal", "status": "covered", "notes": "Effective and knowledge times, bound uncertainty, endpoint policy and recurrent episodes are explicit." }, { "dimension": "provenance", "status": "covered", "notes": "Evidence, issuer, derivation, contrary claims and revisions are linked." }, { "dimension": "ownership", "status": "covered", "notes": "Stewardship is role-based and separate from subject ownership and official authority." }, { "dimension": "validation", "status": "gap", "notes": "Research schema validated separately; nested instance schemas and acceptance fixtures remain unimplemented." }, { "dimension": "access", "status": "covered", "notes": "Recipient-specific current and historical views preserve redaction and freshness markers." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Adopter policy governs retention, holds, tombstones and external disposition execution." }, { "dimension": "interoperability", "status": "gap", "notes": "Temporal, provenance, vocabulary and alert mappings are conceptual; executable loss tests remain pending." }, { "dimension": "direct properties", "status": "covered", "notes": "Condition, temporal reach, assertion basis and scope are direct properties. Mass or dimensions belong to referenced subjects." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Observation is evidence for an interpretation; official status is not inferred from sensing alone." }, { "dimension": "capabilities and behavior", "status": "covered", "notes": "Six proposed local functions have preconditions and refusal outcomes; none operates the world." }, { "dimension": "context and evidence", "status": "covered", "notes": "Subject, scope, mandate, evidence and scenario context qualify every use." }, { "dimension": "regional assumptions", "status": "gap", "notes": "Adopter review required for jurisdiction, regulated status, privacy and retention profiles." }, { "dimension": "independent review", "status": "gap", "notes": "Claude and Grok skipped; local no-tools audit is self-review only." }, { "dimension": "source verification", "status": "gap", "notes": "Selected browser content reviewed; direct HTTP not attempted under reported sandbox restriction. Current versions and full claim verification remain open." } ], "known_omissions": [ "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." ], "conflicts": [], "regional_assumptions": [ "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." ], "adversarial_checks": [ "Latest message after an older valid assertion: retain both knowledge and effective ordering.", "Expired or cancelled alert: do not infer that the underlying condition ceased.", "Same subject has contradictory overlapping claims: return disputed unless a scoped selection rule is evidenced.", "Unknown end with stale evidence: do not display confirmed current status.", "Corrected begin time: preserve thread identity and record revision provenance.", "Scenario output or test alert: keep hypothetical or test context explicit.", "Erased sensitive payload: preserve only lawful markers and report the missing evidence." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The operational root is an identified situation thread that persists across attributed assertions and corrections. It neither asserts the infallibility of a world state nor becomes the observation, event, alert or simulation that provides context. The registry standalone-mm value describes the record plane and is not the subject-kind enum." }, "decisions": [ { "concept": "Situation root and assertion identity", "disposition": "accepted", "rationale": "A stable thread plus distinct assertion and revision IDs supports correction and recurrence review. Mutable begin time and source message identity cannot determine thread identity." }, { "concept": "Primary subject cardinality", "disposition": "qualified", "rationale": "One primary subject is explicitly a local design convention. Collective subjects require an external identity and membership context; the proposal does not claim universal single-entity situations." }, { "concept": "Subject ownership and declaring authority", "disposition": "separated", "rationale": "The legacy owner archetype is preserved as context, but stewardship, observation, official mandate and access control remain separately evidenced roles." }, { "concept": "Condition terminology", "disposition": "accepted with profile dependency", "rationale": "Scheme, term and version are distinct from record state and confidence. The admitted text does not claim that SKOS closes a value set or defines valid transitions." }, { "concept": "Validity and knowledge time", "disposition": "accepted", "rationale": "Effective bounds, observation, assertion and ingestion times remain distinct. Unknown or imprecise bounds are not fabricated exact timestamps; cutoffs govern historical views." }, { "concept": "Current truth from latest transition", "disposition": "rejected", "rationale": "The proposed projection checks validity, scope, freshness, permissions and a selection policy. Contradiction can yield disputed or unknown, and an open interval does not prove continuing truth." }, { "concept": "Event and cessation semantics", "disposition": "qualified", "rationale": "Occurrence references are optional and events are not universally instantaneous. Condition cessation, assertion retraction and record retirement are distinct operations." }, { "concept": "CAP alignment", "disposition": "limited", "rationale": "Alert status and information expiry are not situation status or cessation. The model exposes the timestamp-profile mismatch and requires a tested binding instead of claiming native conformance." }, { "concept": "Risk parent pointer and simulation boundary", "disposition": "unratified references only", "rationale": "The frozen relation ledger is empty for this model. The risk registry parent pointer does not impose containment or redefine Situation as an objective. Simulation execution remains outside the boundary." }, { "concept": "Local functions and physical effects", "disposition": "accepted as proposed", "rationale": "All six operations have scoped inputs, preconditions and refusal outcomes. They record or project information and do not issue official declarations, deliver public alerts or execute physical intervention." }, { "concept": "History, privacy and disposal", "disposition": "accepted with policy dependency", "rationale": "Revision continuity does not imply indefinite payload retention. Lawful minimization, scoped holds, minimal tombstones and externally executed disposition preserve that distinction." }, { "concept": "Evidence breadth and executable schemas", "disposition": "deferred assurance", "rationale": "The seven primary documents support selected concepts, not the whole generic ontology. Candidate object fields, complex recurrence and collective scope bindings still require implementation schemas and adversarial fixtures." }, { "concept": "Provider independence and source checks", "disposition": "held", "rationale": "Claude and Grok supplied no admitted result. This assessment is local self-review with no tools during semantic reasoning. Browser content access and zero direct HTTP attempts cannot be promoted to independently verified sources or measured HTTP success." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts. The separate local Codex no-tools self-audit is not an independent second-provider review.", "Live source and version verification remains incomplete. Selected browser text was reviewed for all seven sources, but direct HTTP checks were not attempted under the owner-reported sandbox restriction: zero measured HTTP 200 responses. Current errata, version currency, licensing and full claim support need coordinator or independent verification; check_sources.py is prepared.", "Adopting profiles must qualify continuity, collective subjects, status authority, legal applicability, privacy, retention, freshness and conflict selection. The cited standards do not confer official powers or prescribe these local policies.", "Nested instance schemas, pinned neighbor bindings, temporal and CAP mappings, complex recurrence handling and executable conformance fixtures remain incomplete. No runtime, ontology-equivalence or operational compliance certification is claimed.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }