{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-act-015","code":"wm-act-015-occurrence-event","url":"https://ver.cy/models/wm-act-015-occurrence-event/","name":"Occurrence / Event","alternateNames":["X1"],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Activities and processes","entryKind":"event","plane":"","domain":["ACT.EVT"],"industry":["Cross-industry"],"navPath":"NAV.ACT.EVT","tags":["occurrence","event","act.evt"],"facets":{}},"whatItIs":"This model covers the record of an individuated occurrence: its identity and boundary, its type, its factual and record status, its temporal position and extent (including event time versus observation and ingestion time, temporal reference frames and stated uncertainty), its spatial or virtual setting, the participation of parties and objects and the entities used or generated, its part-whole and causal relations to other occurrences, the sources and evidence on which it is asserted, and the governance of the record (stewardship, disclosure, correction, retention, alignment and exchange). It is deliberately storage- and interface-neutral: JSON, YAML, Markdown, RDF, Git, MCP and MongoDB are projections of these semantics, not the semantics.","purpose":"Provide the format-neutral backbone for recording that a discrete thing happened in the world — what occurred, when, where, who or what took part, on what evidence, with what certainty, and how it relates to other occurrences — so that every specialised event model reuses one shape for time, place, participation, causality and record correction.","scope":{"in":["Individuation and identity of a single occurrence, including deduplication keys and identifier supersession","Occurrence typing against governed code lists and mapping to external event vocabularies","Factual and record status, including negative assertions (it did not happen) and in-error records","Temporal position and extent as instants, intervals, durations and open-ended spans, with an explicit temporal reference frame","Separation of event time, phenomenon time, observation/result time, record/ingestion time and correction declaration time","Stated temporal precision, approximation and uncertainty, including unspecified components","Place and setting statements that reference, but do not define, external place identities; geometry with a declared CRS","Participation of parties and objects, the capacity or role in which each took part, and delegation of responsibility for participation","Entities used, generated, transformed or invalidated by the occurrence, and the quantities involved","Part-whole, series and episode aggregation of occurrences","Asserted causal and influence links between occurrences, with asserter and confidence","Source records, reporting chains, evidence artifacts and their integrity and custody","Corroboration, certainty and conflicting accounts","Append-only correction, retraction and supersession of occurrence records","Stewardship, participant-level disclosure control, retention classes and disposition","Alignment to external standards and projection into exchange envelopes"],"out":["Intent, deliberation, motive and moral or legal responsibility of an actor — these specialise the occurrence in the Act model","Reciprocity and mutual-participation semantics — these specialise the occurrence in the Encounter model","Identity, attributes and lifecycle of participating persons, organisations and assets","Identity, naming, addressing and gazetteer resolution of places","Result values, units, scales and measurement uncertainty of observations","Planned, requested or scheduled future actions and their fulfilment workflow","Type-level recurring patterns and phenomena as distinct from their individual instances","State conditions that hold over an interval without being a discrete happening","Incident triage, escalation and response workflow","Transport bindings, wire formats, serialization and query-language syntax","System audit trails of operations performed on the record store","Business process and workflow definitions that occurrences might conform to"],"boundaries":[{"neighbor":"WM-ACT-002 Act","distinction":"PROV-O separates mere occurrence from agent responsibility (prov:wasAssociatedWith, prov:Association) and CIDOC CRM separates E5 Event from E7 Activity, defined as actions intentionally carried out by an actor; intent and responsibility therefore belong to the Act model while this model records only that parties participated and in what capacity."},{"neighbor":"WM-ACT-018 Encounter","distinction":"This model records participation as a set of one-sided involvements; reciprocal or mutual participation between two or more parties, and the obligations arising from it, are added by the Encounter specialisation."},{"neighbor":"Observation and measurement model","distinction":"SOSA treats an Observation as an act that occurs and therefore as an occurrence, but the observable property, procedure, sensor and result value belong to the measurement model; this model retains only the linkage and the phenomenonTime/resultTime distinction."},{"neighbor":"Address / Location Referencing model (legacy U7)","distinction":"GeoSPARQL separates geo:Feature (the identified real-world thing) from geo:Geometry (its spatial representation); this model carries the geometry and the granularity of a place statement but references Feature identity externally."},{"neighbor":"Request / Plan model","distinction":"The HL7 FHIR workflow patterns distinguish Event (an activity that has taken place or is ongoing) from Request (a desired future action); scheduled-but-not-yet-occurred items are not occurrences here, which is why schema.org eventStatus values such as EventScheduled are treated as schedule state, not factual status."},{"neighbor":"Observed Phenomenon model (legacy X2)","distinction":"A recurring pattern is a type-level construct; this model records individual instances and may reference the series they instantiate, but does not define the pattern itself."},{"neighbor":"Situation / Condition model (legacy X4)","distinction":"OWL-Time distinguishes a temporal entity from what holds during it; states that persist over an interval are situations, while this model records the discrete happenings that open, advance and close them."},{"neighbor":"Exchange envelope and transport (CloudEvents)","distinction":"CloudEvents defines an occurrence as the statement of fact and the event as the data record expressing it with context; the envelope attributes id, source, type and time are a projection of this model's identity, typing and event-time semantics, not additional semantics."},{"neighbor":"Audit trail model (legacy S4)","distinction":"Operations performed on the occurrence store are audited elsewhere; what stays here is the provenance of the assertion itself — who reported it, when it was recorded and by what declaration it was corrected."}]},"distinguishingFeatures":["The shared backbone for anything that happened: one shape for time, place, participants, causality and evidence.","Can record that something did not happen, and keeps records made in error as such.","Separates event time, observation time and recording time."],"structure":{"bundles":[{"id":"occurrence-core","name":"Occurrence Core","description":"The identity, boundary, type and factual status of the happening itself, before anything is said about time, place, participation or cause.","layers":[{"id":"identity-and-individuation","name":"Identity and Individuation","description":"How one occurrence is delimited from the continuum of activity and how that single occurrence is named and re-found across systems.","findings":[{"id":"occurrence-identifier","name":"Occurrence identifier and deduplication key","description":"The authoritative name of the occurrence record, the scheme it belongs to, the fallback minting rule when no master system exists, and the key on which two records are judged to denote the same happening.","questions":[{"text":"Which system of record holds the authoritative identifier for this occurrence, and under what identifier scheme was it issued?","id":"q-id-authority","kind":"identity"},{"text":"What combination of attributes decides that two incoming records denote the same occurrence rather than two distinct occurrences?","id":"q-id-sameness","kind":"constraint"},{"text":"When no master-system identifier exists, is a governed IRI or a locally minted UUID or ULID used, and which authority mints it?","id":"q-id-fallback","kind":"decision"},{"text":"Under what conditions may the identifier be superseded, and how does a consumer resolve an old identifier to the current record?","id":"q-id-supersession","kind":"lifecycle"}]},{"id":"occurrence-individuation","name":"Occurrence boundary and granularity","description":"The criterion by which the happening is delimited, whether it is recorded as instantaneous or extended, and what happens when one occurrence is later found to be several or several to be one.","questions":[{"text":"What criterion delimits this happening from the surrounding continuum of activity, and who applied it?","id":"q-ind-criterion","kind":"definition"},{"text":"Is the occurrence recorded as an instant with no interior or as an extended process with internal constituent parts?","id":"q-ind-extent","kind":"composition"},{"text":"How is the record repaired when one recorded occurrence turns out to be two, or two turn out to be one?","id":"q-ind-resplit","kind":"exception"}]},{"id":"occurrence-designation-and-aboutness","name":"Summary and aboutness","description":"An occurrence has a human-readable name or summary and may be about other entities. Schema.org Event requires name and allows description, disambiguatingDescription, about and workFeatured or workPerformed. CIDOC P3 has note and P129 is about. FHIR Event.note captures comments by performer or subject. The summary is not a substitute for structured type, time or participants.","questions":[{"text":"What short summary distinguishes this occurrence from similar happenings, and in which language?","id":"occurrence-designation-and-aboutness-q01","kind":"classification"},{"text":"Which entities, works or topics is the occurrence about or did it feature, without treating those as participants?","id":"occurrence-designation-and-aboutness-q02","kind":"relationship"},{"text":"What disambiguating description is required when name and type are insufficient to separate this particular from another of the same kind?","id":"occurrence-designation-and-aboutness-q03","kind":"quality"}]}]},{"id":"typing-and-factuality","name":"Typing and Factuality","description":"What kind of occurrence this is, and whether it is asserted to have happened, to be ongoing, not to have happened, or to have been recorded in error.","findings":[{"id":"occurrence-classification","name":"Occurrence type and governing vocabulary","description":"The code or codes classifying the occurrence, the scheme that governs them, who may extend that scheme, and how local types map to external event vocabularies.","questions":[{"text":"Which type code or codes classify this occurrence, and from which governed scheme and version do they come?","id":"q-cls-code","kind":"classification"},{"text":"May an occurrence carry more than one type, and how are conflicting or overlapping types reconciled?","id":"q-cls-multiplicity","kind":"constraint"},{"text":"Which body governs the type vocabulary, and what is the procedure for adding or retiring a code value?","id":"q-cls-authority","kind":"authority"},{"text":"To which external event vocabularies is each local type mapped, and is the mapping exact, broader or narrower?","id":"q-cls-mapping","kind":"interoperability"}]},{"id":"occurrence-factuality-status","name":"Factual assertion and record status","description":"Whether the happening is asserted to have occurred, is ongoing, is asserted not to have occurred, or the record is repudiated as entered in error, together with the reason and the allowed transitions.","questions":[{"text":"What is the current status of this occurrence record, and does that status describe the happening or the record?","id":"q-fact-status","kind":"state"},{"text":"Which status transitions are permitted, which are terminal, and who is authorised to make each transition?","id":"q-fact-transitions","kind":"lifecycle"},{"text":"When the record asserts that the happening did not occur, what evidence and reason support that negative assertion?","id":"q-fact-negative","kind":"evidence"},{"text":"How is schedule state such as cancelled, postponed or rescheduled kept distinct from the assertion that the happening occurred?","id":"q-fact-schedule","kind":"validation"}]}]}]},{"id":"temporality","name":"Temporality","description":"When the occurrence happened, in what frame that time is expressed, how precisely it is known, and how event time is separated from the times at which it was observed, recorded and corrected.","layers":[{"id":"temporal-position-and-extent","name":"Temporal Position, Extent and Uncertainty","description":"The stated time of the happening as instant, interval or duration, the reference frame it is expressed in, and the precision and qualification attached to it.","findings":[{"id":"event-time-extent","name":"Event time position and extent","description":"Whether the occurrence is placed at an instant or over an interval, how beginning, end and duration are stated, and how open-ended or still-running occurrences are expressed.","questions":[{"text":"Is the event time expressed as an instant, a bounded interval, or a duration anchored at one end?","id":"q-time-kind","kind":"temporal"},{"text":"How is an occurrence that has begun but not ended, or whose end is unknown, distinguished from one with a known end?","id":"q-time-open","kind":"state"},{"text":"Where the boundaries are inherently fuzzy, which outer and inner bounds are asserted for the beginning and the end?","id":"q-time-fuzzy-bounds","kind":"constraint"}]},{"id":"temporal-reference-frame","name":"Temporal reference frame, offset and time zone","description":"The calendar or temporal reference system in which the time is expressed, the required lexical form, and the retention of local offset and IANA time zone name alongside the UTC instant.","questions":[{"text":"Which temporal reference system is the event time expressed in, and is it declared explicitly rather than assumed to be Gregorian and UTC?","id":"q-trs-frame","kind":"temporal"},{"text":"What UTC offset was in effect at the place of the occurrence, and is the IANA time zone name recorded in addition to that offset?","id":"q-trs-offset","kind":"constraint"},{"text":"How are ordinal, relative, geologic or non-Gregorian times conveyed to consumers that expect a civil timestamp?","id":"q-trs-nonstandard","kind":"interoperability"}]},{"id":"temporal-uncertainty-precision","name":"Temporal precision, approximation and uncertainty","description":"The stated precision of the time value and any qualification marking it uncertain, approximate, partly unspecified or drawn from a set of alternatives.","questions":[{"text":"To what precision is the event time actually known, as distinct from the precision at which it happens to be serialised?","id":"q-unc-precision","kind":"measurement"},{"text":"Is the time asserted as uncertain, approximate, both, or partly unspecified, and to which components does the qualification apply?","id":"q-unc-qualifier","kind":"quality"},{"text":"How must a consumer treat an imprecise or qualified time value when ordering, filtering or joining occurrences?","id":"q-unc-comparison","kind":"validation"}]}]},{"id":"record-time-and-ordering","name":"Record Time, Observation Time and Ordering","description":"The distinct clocks that bear on an occurrence record — when it happened, when it was observed, when the result applies, when it was ingested, when a correction was declared — and how records are ordered when those clocks disagree.","findings":[{"id":"event-versus-record-time","name":"Event time versus observation and ingestion time","description":"Separation of the time the happening occurred from the time a result applies to its subject, the time the observing act completed, the time the record entered the store, and the time any correction was declared.","questions":[{"text":"Which distinct times are recorded for this occurrence, and which clock produced each of them?","id":"q-rt-separation","kind":"provenance"},{"text":"Where the record carries an observation, does the phenomenon time differ from the time the observing act completed, and by how much?","id":"q-rt-phenomenon","kind":"temporal"},{"text":"Which of the recorded times governs retention clocks, query windows and completeness watermarks?","id":"q-rt-basis","kind":"decision"},{"text":"How is a record ingested long after the fact distinguished from one captured in near real time?","id":"q-rt-backfill","kind":"quality"}]},{"id":"ordering-and-clock-integrity","name":"Ordering, interval relations and clock integrity","description":"How occurrences are ordered when timestamps tie or clocks disagree, which qualitative interval relations are asserted, and what evidence supports the trustworthiness of the recorded time.","questions":[{"text":"When two occurrences carry the same timestamp, what deterministic rule establishes their order?","id":"q-ord-tiebreak","kind":"constraint"},{"text":"Which qualitative interval relations between this occurrence and others are asserted rather than computed from timestamps?","id":"q-ord-relations","kind":"relationship"},{"text":"What is known about the clock that produced the timestamp, and what protects the record against back-dating?","id":"q-ord-clocktrust","kind":"security"}]}]}]},{"id":"spatiality-and-setting","name":"Spatiality and Setting","description":"Where the occurrence took place — as a reference to an identified place, as geometry in a declared reference system, or as a non-physical setting — and at what granularity and accuracy.","layers":[{"id":"place-specification","name":"Place Specification","description":"The reference to where the occurrence happened and its geometric expression, kept distinct from the identity of the place itself.","findings":[{"id":"place-reference-and-granularity","name":"Place reference, role and granularity","description":"Which identified place the occurrence is attached to, in what role that place plays, at what granularity, and how an unknown or deliberately withheld place is expressed.","questions":[{"text":"Which identified place does this occurrence reference, and in which external register does that identity live?","id":"q-place-ref","kind":"spatial"},{"text":"Does the record distinguish the precise point of capture from the wider business or organisational location, and how are both used?","id":"q-place-role","kind":"composition"},{"text":"At what granularity is the place asserted, and is that granularity a limit of knowledge or a deliberate generalisation?","id":"q-place-granularity","kind":"quality"},{"text":"How is a place that is unknown, inapplicable or withheld distinguished from one that was simply not captured?","id":"q-place-absent","kind":"exception"}]},{"id":"geometry-crs-and-spatial-uncertainty","name":"Geometry, coordinate reference system and positional accuracy","description":"The geometric representation of where the occurrence happened, the coordinate reference system it is expressed in, its positional accuracy, and any generalisation applied before disclosure.","questions":[{"text":"In which serialisation is the geometry expressed, and which coordinate reference system URI governs its coordinates?","id":"q-geo-serialisation","kind":"spatial"},{"text":"What positional accuracy is claimed for the geometry, and what produced that claim?","id":"q-geo-accuracy","kind":"measurement"},{"text":"Has the geometry been coarsened, offset or clipped before disclosure, and is the original retained under restriction?","id":"q-geo-generalisation","kind":"privacy"}]}]},{"id":"setting-and-non-physical-context","name":"Setting and Non-Physical Context","description":"Occurrences that take place wholly or partly outside physical space, and the declared context in which the producer situates them.","findings":[{"id":"virtual-and-hybrid-setting","name":"Virtual, hybrid and producer-context setting","description":"Whether the occurrence took place physically, virtually or in both modes, how a virtual location is identified, and how the producer's declared context relates to the physical place.","questions":[{"text":"Did the occurrence take place in physical space, in a virtual environment, or in both simultaneously?","id":"q-set-mode","kind":"classification"},{"text":"How is the virtual location identified so that two occurrences in the same environment can be recognised as co-located?","id":"q-set-virtualid","kind":"identity"},{"text":"What producer context does the record declare, and is it a substitute for the physical place or an addition to it?","id":"q-set-context","kind":"provenance"},{"text":"Which jurisdiction governs this occurrence, and is it derived from the physical place or asserted independently?","id":"q-set-jurisdiction","kind":"authority"}]}]}]},{"id":"participation-and-effects","name":"Participation and Effects","description":"Who and what took part in the occurrence, in what capacity, and which entities were used, produced, transformed or invalidated by it.","layers":[{"id":"participants-and-roles","name":"Participants and Roles","description":"The parties and objects involved and the capacity in which each was involved, including delegation of that capacity.","findings":[{"id":"participant-reference","name":"Participant and subject reference","description":"Which parties and objects took part, which one is the subject or feature of interest, how they are referenced into external party models, and how pseudonymous or unidentified participants are handled.","questions":[{"text":"Which parties and objects are recorded as taking part, and by which external identifiers are they referenced?","id":"q-part-who","kind":"relationship"},{"text":"Which participant is the subject or feature of interest of the occurrence, as distinct from the others involved?","id":"q-part-subject","kind":"composition"},{"text":"Does this occurrence type require at least one participant, and is an occurrence with no identified participant valid?","id":"q-part-minimum","kind":"constraint"},{"text":"How is a participant recorded when their identity is unknown, pseudonymous or deliberately not resolved?","id":"q-part-pseudonymous","kind":"privacy"}]},{"id":"role-capacity-and-delegation","name":"Role, capacity, presence and delegation","description":"The capacity in which each participant took part, whether they were present or absent, on whose behalf they acted, and the governed vocabulary from which roles are drawn.","questions":[{"text":"In what capacity did each participant take part, and from which governed role vocabulary is that capacity drawn?","id":"q-role-code","kind":"classification"},{"text":"On whose behalf did a participant act, and how far back does the recorded delegation chain reach?","id":"q-role-delegation","kind":"authority"},{"text":"Was the participant physically or virtually present, represented, or recorded as involved without being present?","id":"q-role-presence","kind":"state"},{"text":"Which recorded participation facts stop short of asserting intent or responsibility, and where does that assertion belong instead?","id":"q-role-boundary","kind":"definition"}]}]},{"id":"entities-and-changes","name":"Entities and Changes","description":"What the occurrence consumed, produced, transformed or invalidated, and in what quantity.","findings":[{"id":"affected-entities-and-transformation","name":"Entities used, generated and transformed","description":"The inputs consumed and outputs produced by the occurrence, the quantities involved, the state change effected, and the linkage that ties inputs to outputs across separately recorded steps.","questions":[{"text":"Which entities did the occurrence use as inputs and which did it generate, and are those sets asserted to be complete?","id":"q-ent-io","kind":"composition"},{"text":"In what quantities were entities consumed or produced, and in which units and measurement scale?","id":"q-ent-quantity","kind":"measurement"},{"text":"What state or disposition of an affected entity changed as a result of the occurrence?","id":"q-ent-statechange","kind":"state"},{"text":"When inputs and outputs are recorded by separate occurrences, what identifier links them into one transformation?","id":"q-ent-linkage","kind":"relationship"}]}]}]},{"id":"explanation-and-composition","name":"Explanation and Composition","description":"How occurrences aggregate into larger units and how they are asserted to influence or explain one another.","layers":[{"id":"aggregation-and-recurrence","name":"Aggregation, Series and Recurrence","description":"Grouping occurrences into wholes, episodes and series, and separating an individual instance from the recurring pattern it instantiates.","findings":[{"id":"part-whole-episode-and-series","name":"Part-whole aggregation, episodes and recurring series","description":"How an occurrence sits inside a larger occurrence or narrative episode, how a member of a recurring series is distinguished from the series itself, and how the whole's temporal span relates to its members.","questions":[{"text":"Of which larger occurrence or episode is this occurrence a part, and is the parent's membership asserted to be exhaustive?","id":"q-agg-parent","kind":"composition"},{"text":"May one occurrence belong to more than one episode or aggregate at the same time, and how are competing groupings reconciled?","id":"q-agg-multi","kind":"constraint"},{"text":"Is the temporal span of the aggregate asserted independently or derived from its members, and what happens when a member is added or retracted?","id":"q-agg-span","kind":"temporal"},{"text":"Is this occurrence an instance of a recurring series, and how is the series identity kept distinct from the instance identity?","id":"q-agg-series","kind":"identity"}]}]},{"id":"causality-and-purpose","name":"Causality and Purpose","description":"Asserted influence between occurrences, and the business or motivational context that explains why the occurrence took place.","findings":[{"id":"causal-and-influence-links","name":"Asserted causal and influence links","description":"Links stating that one occurrence caused, contributed to, informed or derived from another, always carrying the asserter, the basis and a confidence, and never inferred from temporal order alone.","questions":[{"text":"What kind of influence is asserted between these occurrences — full causation, contribution, enablement, or mere information flow?","id":"q-cause-kind","kind":"relationship"},{"text":"Who asserted this causal link, on what basis, and at what time?","id":"q-cause-asserter","kind":"provenance"},{"text":"What confidence is attached to the link, on what scale, and what would falsify it?","id":"q-cause-confidence","kind":"quality"},{"text":"What constraints prevent cycles and temporally impossible causation among asserted links?","id":"q-cause-consistency","kind":"validation"}]},{"id":"purpose-and-business-context","name":"Purpose, business step and reason","description":"Why the occurrence took place: the business process step it belongs to, the resulting disposition, the transactions it relates to, and the coded reasons recorded for it.","questions":[{"text":"Which business process step does this occurrence represent, and from which governed vocabulary is that step drawn?","id":"q-why-step","kind":"classification"},{"text":"What business or physical disposition results from the occurrence, and does it persist until another occurrence changes it?","id":"q-why-disposition","kind":"state"},{"text":"Which business transactions, orders or cases does the occurrence relate to, and in what role?","id":"q-why-transaction","kind":"relationship"},{"text":"What recorded reason or motivating circumstance is asserted for the occurrence, and is it a fact or an interpretation?","id":"q-why-motivation","kind":"evidence"}]}]}]},{"id":"evidence-and-assertion-quality","name":"Evidence and Assertion Quality","description":"On what basis the occurrence is asserted, what evidence supports it, how certain it is, and how a wrong record is corrected without destroying history.","layers":[{"id":"assertion-and-evidence","name":"Assertion Provenance and Evidence","description":"Who said the occurrence happened, through what chain of reporting, and what evidence is attached and protected.","findings":[{"id":"source-record-and-reporting-chain","name":"Source record and reporting chain","description":"The account from which the occurrence was recorded, whether it is first-hand or reported, the chain of intermediaries between the happening and the record, and the standing of each source.","questions":[{"text":"Who supplied the account from which this occurrence was recorded, and when did they supply it?","id":"q-src-who","kind":"provenance"},{"text":"Is the account first-hand, reported by a proxy, or derived from another record, and is that standing recorded explicitly?","id":"q-src-firsthand","kind":"authority"},{"text":"What intermediaries stand between the happening and this record, and is the chain complete?","id":"q-src-chain","kind":"relationship"},{"text":"What is known about the reliability or accreditation of each source, and where is that judgement recorded?","id":"q-src-standing","kind":"quality"}]},{"id":"evidence-artifacts-and-integrity","name":"Evidence artifacts, integrity and custody","description":"The media, sensor data and documents evidencing the occurrence, how each is bound to the record, how its integrity is demonstrated, and who has held it.","questions":[{"text":"What evidence artifacts are attached to this occurrence, and what does each purport to show?","id":"q-ev-what","kind":"evidence"},{"text":"What digest or signature demonstrates that an evidence artifact has not changed since capture, and who computed it?","id":"q-ev-integrity","kind":"security"},{"text":"Who has held or accessed the evidence since capture, and is the custody record gapless?","id":"q-ev-custody","kind":"access"},{"text":"How is an evidence artifact bound to this occurrence rather than to a similar one, and what happens if the binding is disputed?","id":"q-ev-binding","kind":"validation"}]}]},{"id":"certainty-and-correction","name":"Certainty, Conflict and Correction","description":"How confident the record is, how conflicting accounts are held, and how an erroneous record is corrected without mutation.","findings":[{"id":"corroboration-and-certainty","name":"Corroboration, certainty and conflicting accounts","description":"The certainty attached to the occurrence, how independent corroboration raises it, and how mutually inconsistent accounts of the same happening are retained side by side.","questions":[{"text":"What certainty is asserted that the occurrence happened as recorded, and on what defined scale?","id":"q-cert-level","kind":"quality"},{"text":"How many genuinely independent sources corroborate the occurrence, and what makes them independent?","id":"q-cert-corroboration","kind":"evidence"},{"text":"When two accounts of the same happening disagree, are both retained, and how is the disagreement represented?","id":"q-cert-conflict","kind":"exception"},{"text":"What certainty threshold must be met before the occurrence may be published, acted upon or propagated to downstream models?","id":"q-cert-threshold","kind":"decision"}]},{"id":"correction-retraction-and-versioning","name":"Correction, retraction and supersession","description":"How a record found to be wrong is repudiated and superseded by corrective records, why in-place mutation is refused, and how consumers detect that a record they hold has been superseded.","questions":[{"text":"By what mechanism is an erroneous record repudiated while the erroneous content itself is preserved?","id":"q-corr-mechanism","kind":"lifecycle"},{"text":"Does a corrective record reuse the identifier of the record it corrects, or take a new one, and how is the relation expressed?","id":"q-corr-identity","kind":"identity"},{"text":"Which changes count as material and require a correction record rather than an additive in-place update?","id":"q-corr-materiality","kind":"constraint"},{"text":"How does a consumer holding a copy detect that the record has been superseded or repudiated?","id":"q-corr-detection","kind":"interoperability"}]}]}]},{"id":"governance-and-exchange","name":"Governance and Exchange","description":"Who stewards the occurrence record, who may see which parts of it, how long it is kept and how it is disposed of, and how it is aligned and exchanged with other systems.","layers":[{"id":"stewardship-access-and-retention","name":"Stewardship, Access and Retention","description":"Accountability for the record, control over its disclosure, and the rules governing how long it survives and how it ends.","findings":[{"id":"ownership-and-stewardship","name":"Ownership, stewardship and amendment authority","description":"Which party is accountable for the occurrence record, which registrar maintains it, what rights participants retain over their own participation, and how stewardship transfers.","questions":[{"text":"Which party is accountable for this occurrence record, and is that the primary actor or an observing registrar?","id":"q-own-accountable","kind":"ownership"},{"text":"Who is authorised to declare this record in error or to file a corrective record, and who is not?","id":"q-own-amend","kind":"authority"},{"text":"What rights does a recorded participant retain over the portion of the record describing their own participation?","id":"q-own-participant","kind":"ownership"},{"text":"How is stewardship transferred when the accountable party dissolves, merges or hands over the register?","id":"q-own-transfer","kind":"process"}]},{"id":"access-disclosure-and-projection","name":"Access, disclosure and published projections","description":"The default visibility of an occurrence, participant-level control over disclosure, the exceptions that override withholding, and the named projections in which the occurrence may be published.","questions":[{"text":"What is the default visibility of this occurrence, and which party decides that default?","id":"q-acc-default","kind":"access"},{"text":"How does a participant grant or withhold disclosure of their own participation without affecting the rest of the record?","id":"q-acc-participant","kind":"privacy"},{"text":"Under what conditions may participant withholding be overridden, and who authorises the override?","id":"q-acc-override","kind":"exception"},{"text":"Which named projections of this occurrence may be published, and what does each deliberately omit?","id":"q-acc-projection","kind":"interoperability"}]},{"id":"retention-and-deletion","name":"Retention, erasure and disposition","description":"How long the occurrence record is kept and on which clock, how erasure obligations are reconciled with an append-only log, which exceptions permit continued retention, and what evidences that a disposition was executed.","questions":[{"text":"How long is this occurrence retained, from which recorded time does that period run, and on what basis was it set?","id":"q-ret-period","kind":"retention"},{"text":"When an erasure obligation applies, which elements are removed and which survive so that the occurrence's existence and identifier remain intact?","id":"q-ret-erasure","kind":"privacy"},{"text":"Which exceptions — legal hold, legal claims, public-interest archiving, research or statistics, legal obligation — justify continued retention here?","id":"q-ret-exception","kind":"exception"},{"text":"What evidences that a retention decision was actually executed against both the record and its evidence artifacts?","id":"q-ret-evidence","kind":"validation"}]}]},{"id":"interoperability-and-delivery","name":"Interoperability and Delivery","description":"How the occurrence is aligned to external vocabularies without overclaiming conformance, and how it is transmitted, deduplicated and assessed for completeness at the boundary.","findings":[{"id":"external-alignment-and-conflicts","name":"External alignment, conformance evidence and recorded conflicts","description":"Which external vocabularies the model is aligned to, at what version, with what evidence, and which conflicts between those vocabularies are recorded rather than silently resolved.","questions":[{"text":"To which external vocabularies and versions is this model aligned, and is each alignment exact, broader or narrower?","id":"q-align-targets","kind":"interoperability"},{"text":"What evidence supports any claim of conformance, as opposed to a claim of alignment?","id":"q-align-evidence","kind":"validation"},{"text":"Which conflicts between aligned standards are recorded, and how must an implementer choose between them?","id":"q-align-conflict","kind":"exception"},{"text":"Who maintains each mapping, and how often is it re-verified against the upstream standard?","id":"q-align-owner","kind":"authority"}]},{"id":"delivery-deduplication-and-completeness","name":"Delivery, deduplication and completeness","description":"How the occurrence is carried in an exchange envelope, how receivers detect duplicates and replays, how corrections propagate to prior recipients, and how a consumer knows whether it has seen everything.","questions":[{"text":"Which envelope carries the occurrence in transit, and which envelope attributes are projections of model elements rather than new facts?","id":"q-del-envelope","kind":"interoperability"},{"text":"On what rule may a receiver treat two deliveries as the same occurrence, and what must it never treat as a duplicate?","id":"q-del-duplicate","kind":"constraint"},{"text":"How is a correction propagated to recipients that already consumed the erroneous record?","id":"q-del-correction","kind":"process"},{"text":"How does a consumer determine that it has received all occurrences up to a given point, and how are gaps declared?","id":"q-del-completeness","kind":"quality"}]}]}]}]},"agentConduct":{"may":["Record an occurrence with evidence and stated uncertainty.","Link occurrences by part-whole or causal relations with evidence.","Correct a record by appending a correction."],"mustNot":["State a cause as fact without evidence.","Assign intent or blame; that belongs to the act model and to people.","Drop stated uncertainty when copying a record."],"requiresHuman":["Asserting responsibility for harmful events.","Merging records that may describe different occurrences."]},"ethics":{"considerations":["Event records about people (incidents, accidents) can stigmatize; keep facts separate from judgement.","Negative assertions and corrections protect people from false records."],"affectedParties":["People and organizations taking part in events","Investigators and the public relying on records"]},"owners":{"steward":"The recording authority for each kind of event (operator, registry, investigator) owns its records.","roles":[{"name":"Occurrence Registrar","responsibilities":["Capture occurrences from sources, assign identity under the identity priority and stamp record time.","Run deduplication and decide whether an incoming record is a duplicate or an independent additional account.","Maintain factual and record status and file correction notices when authorised."]},{"name":"Participating Party","responsibilities":["Grant or withhold disclosure of their own participation and withdraw a grant later.","Dispute a recorded account of an occurrence in which they took part and have the dispute recorded.","Request rectification of inaccurate participation details or erasure where an obligation applies."]},{"name":"Evidence Custodian","responsibilities":["Compute and verify artifact digests at ingestion, on custody transfer and on evidential reads.","Maintain a gapless chain of custody and record any discontinuity rather than closing the gap silently.","Quarantine artifacts whose integrity fails and execute artifact-level disposition under retention decisions."]},{"name":"Model Steward","responsibilities":["Maintain the bundles, layers, findings and questions, and record which nodes lack primary source support.","Version and publish the governed code lists and the constraint set, with migration notes for breaking changes.","Maintain the alignment and conflict register and re-verify pinned upstream standard versions on the declared interval."]},{"name":"Access and Retention Authority","responsibilities":["Set default visibility classes and retention classes and adjudicate policy conflicts under the declared strategy.","Decide disclosure overrides and legal holds, and record the ground, the authorising role and any notification obligation.","Authorise erasure and disposition decisions after evaluating the applicable exceptions."]},{"name":"Exchange Operator","responsibilities":["Project occurrences into exchange envelopes and maintain the attribute-to-element mapping.","Operate duplicate detection, correction propagation to prior recipients and completeness watermarks.","Declare delivery gaps and backfill policy rather than allowing silent incompleteness."]}],"masterSystems":["Incident or event registries","Sensor and logging systems"]},"relations":[{"target":"WM-ACT-002 Act","type":"extends","note":"The Act model specialises this occurrence by adding an intentional or causal actor bearing responsibility; PROV separates responsibility (wasAssociatedWith) from occurrence and CIDOC separates E7 Activity, defined as intentionally carried out, from E5 Event, so intent must not be modelled here."},{"target":"WM-ACT-018 Encounter","type":"extends","note":"The Encounter model specialises this occurrence by adding reciprocal participation and the mutual obligations arising from it, which this model deliberately does not express."},{"target":"WM-FLW-013 Supply-chain trace","type":"composes","note":"A supply-chain trace composes an ordered set of custody occurrences; the EPCIS event types and the what/when/where/why capture pattern supply the custody vocabulary that the trace assembles."},{"target":"Incident / Emergency model (legacy X3)","type":"extends","note":"Incident models specialise this occurrence with severity, escalation and response workflow, which are status and process semantics beyond the generic Event pattern."},{"target":"Observed Phenomenon model (legacy X2)","type":"references","note":"Type-level recurring patterns live in the phenomenon model; this model references the series or pattern that an individual occurrence instantiates without defining it."},{"target":"Situation / Condition model (legacy X4)","type":"references","note":"Occurrences open, advance and close states that hold over intervals; OWL-Time separates the temporal entity from what holds during it, so state persistence belongs to the situation model."},{"target":"Address / Location Referencing model (legacy U7)","type":"references","note":"Place identity, addressing and gazetteer resolution are external; GeoSPARQL's separation of geo:Feature from geo:Geometry makes the reference mandatory whenever a place is asserted."},{"target":"Person model (legacy H1)","type":"references","note":"Human participants are referenced, never defined here; the participation link carries only role, presence and delegation."},{"target":"Organization model (legacy O1)","type":"references","note":"Organisational participants and the parties on whose behalf individuals act are referenced into the organisation model, which owns their identity and structure."},{"target":"Measurement and Observation Result model","type":"references","note":"Where an occurrence is an observation, the observable property, procedure, result value, unit and measurement uncertainty belong to the measurement model; only the act and its phenomenon/result times are retained here."},{"target":"Consent / Access Grant model (legacy S2)","type":"composes","note":"Participant-level disclosure grants are mixed in so a participant can control visibility of their own participation without owning the whole record."},{"target":"Audit Trail model (legacy S4)","type":"references","note":"Operations performed on the occurrence store are audited in the audit model; only the provenance of the assertion itself stays here."},{"target":"W3C Time Ontology in OWL (OWL-Time)","type":"composes","note":"Supplies the temporal value types — TemporalEntity with Instant and Interval, hasBeginning/hasEnd, duration and the explicit temporal reference system — that this model composes rather than redefines."},{"target":"IETF RFC 3339 and RFC 9557","type":"aligned","note":"Fix the lexical form of every timestamp (seconds plus explicit offset or Z) and the recording of IANA time zone names alongside offsets; alignment is asserted, not conformance certification."},{"target":"OGC GeoSPARQL 1.1","type":"composes","note":"Supplies geometry serialisations and the requirement to declare a coordinate reference system by URI for any spatial expression of where the occurrence took place."},{"target":"Library of Congress Extended Date/Time Format (EDTF)","type":"composes","note":"Supplies the literal syntax for uncertain, approximate, partly unspecified and open-ended dates, which OWL-Time does not natively provide."},{"target":"W3C PROV-O","type":"aligned","note":"Aligns occurrence with prov:Activity and the attribution, association, delegation, usage, generation and communication relations used for participation, entity effects and influence links."},{"target":"CIDOC CRM 7.1.3","type":"aligned","note":"Aligns occurrence with E5 Event and its time-span, place, participation, part-whole and motivation properties, and supplies the fuzzy temporal ordering pattern."},{"target":"GS1 EPCIS 2.0","type":"aligned","note":"Aligns the what/when/where/why capture dimensions, the eventTime / eventTimeZoneOffset / recordTime split and the ErrorDeclaration correction pattern; alignment is scoped to supply-chain contexts and not asserted as conformance."},{"target":"HL7 FHIR R5 Event pattern","type":"aligned","note":"Aligns the record status vocabulary including not-done and entered-in-error, the recorded/reported distinction and the normative Event-versus-Request boundary."},{"target":"W3C SSN/SOSA","type":"aligned","note":"Aligns observation acts as occurrences and imports the phenomenonTime versus resultTime distinction into the temporality bundle."},{"target":"Schema.org Event","type":"aligned","note":"Aligns public-chronicle typing, superEvent/subEvent and virtual location; the eventStatus vocabulary is explicitly treated as schedule state and is not mapped onto factual status."},{"target":"CNCF CloudEvents 1.0.2","type":"aligned","note":"Aligns the exchange envelope as a projection: id, source, type and time map to model identity, typing and event time, and the source+id uniqueness rule grounds duplicate detection."},{"target":"W3C ODRL Information Model 2.2","type":"composes","note":"Supplies the machine-readable expression of permissions, prohibitions, duties, constraints and conflict-resolution strategy over the occurrence record and its parts."},{"target":"WM-ACT-002 Act","type":"neighbor","note":"PROV-O separates mere occurrence from agent responsibility (prov:wasAssociatedWith, prov:Association) and CIDOC CRM separates E5 Event from E7 Activity, defined as actions intentionally carried out by an actor; intent and responsibility therefore belong to the Act model while this model records only that parties participated and in what capacity."},{"target":"WM-ACT-018 Encounter","type":"neighbor","note":"This model records participation as a set of one-sided involvements; reciprocal or mutual participation between two or more parties, and the obligations arising from it, are added by the Encounter specialisation."},{"target":"Observation and measurement model","type":"neighbor","note":"SOSA treats an Observation as an act that occurs and therefore as an occurrence, but the observable property, procedure, sensor and result value belong to the measurement model; this model retains only the linkage and the phenomenonTime/resultTime distinction."},{"target":"Address / Location Referencing model (legacy U7)","type":"neighbor","note":"GeoSPARQL separates geo:Feature (the identified real-world thing) from geo:Geometry (its spatial representation); this model carries the geometry and the granularity of a place statement but references Feature identity externally."},{"target":"Request / Plan model","type":"neighbor","note":"The HL7 FHIR workflow patterns distinguish Event (an activity that has taken place or is ongoing) from Request (a desired future action); scheduled-but-not-yet-occurred items are not occurrences here, which is why schema.org eventStatus values such as EventScheduled are treated as schedule state, not factual status."},{"target":"Observed Phenomenon model (legacy X2)","type":"neighbor","note":"A recurring pattern is a type-level construct; this model records individual instances and may reference the series they instantiate, but does not define the pattern itself."},{"target":"Situation / Condition model (legacy X4)","type":"neighbor","note":"OWL-Time distinguishes a temporal entity from what holds during it; states that persist over an interval are situations, while this model records the discrete happenings that open, advance and close them."},{"target":"Exchange envelope and transport (CloudEvents)","type":"neighbor","note":"CloudEvents defines an occurrence as the statement of fact and the event as the data record expressing it with context; the envelope attributes id, source, type and time are a projection of this model's identity, typing and event-time semantics, not additional semantics."},{"target":"Audit trail model (legacy S4)","type":"neighbor","note":"Operations performed on the occurrence store are audited elsewhere; what stays here is the provenance of the assertion itself — who reported it, when it was recorded and by what declaration it was corrected."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier issued by the system of record for the occurrence or artifact — for example the capturing registry's event identifier, the producer's context-scoped identifier pair, or the filing system's document number.","Governed global identifier or IRI from a recognised scheme — a persistent HTTP IRI, a registry-governed event or document identifier, or another identifier whose issuing authority is named and resolvable.","UUID or ULID minted by the adopting Dimension, recorded together with its minting authority and its mint instant in RFC 3339 with seconds and an explicit offset.","Never identity: a date, a timestamp, a title, a natural-language summary or a sequence position alone. Content digests may serve as deduplication keys and integrity checks but never as primary identity, because identical content recurs across distinct occurrences."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["An occurrence record has a type, a time with precision, a setting, participants and sources."]},"capabilities":{"applicability":"required","items":["Record an occurrence: Accept an assertion that something happened and create an occurrence record with identity, type, event time, factual status and at least one asserting source.","Assign occurrence identity: Apply the identity priority to select or mint the authoritative identifier for an occurrence and register any alternates.","Normalise temporal position: Convert a submitted time statement to the canonical form while preserving the original offset, time zone name, reference system and any uncertainty qualification.","Resolve place statement: Bind a place statement to an externally identified place, attach geometry with a declared coordinate reference system, and apply any disclosure generalisation.","Assert participation: Record that a party or object took part in the occurrence, in a governed role, with presence and any delegation chain, without asserting intent.","Attach evidence: Bind an evidence artifact to the occurrence, compute and record its digest, and open or extend its chain of custody.","Deduplicate and reconcile: Detect that an incoming record denotes an already recorded occurrence and either discard it as a duplicate or reconcile it as an additional independent account.","Assert a causal or influence link: Record an asserted influence between two occurrences with its kind, asserter, basis and confidence, subject to temporal and acyclicity constraints.","Compose an aggregate or episode: Group related occurrences into a larger occurrence, episode or series instance and derive or assert the aggregate's temporal span.","Declare error and issue correction: Repudiate an erroneous occurrence record without mutating it and file the corrective records that supersede it.","Project and disclose: Produce a named projection of an occurrence for a stated audience, applying the access policy, participant grants and any spatial or personal generalisation.","Apply retention disposition: Evaluate the retention class, holds and legal exceptions for an occurrence and execute the resulting redaction, anonymisation, archival transfer or destruction.","Validate an occurrence record: Check a record against structural, temporal, referential and policy constraints before acceptance or publication.","Dispute occurrence: Record a formal contest of the account, holding competing source records without collapsing them into one certainty flag.","Interchange event: Map an occurrence to or from CIDOC E5, schema.org Event, EPCIS, CloudEvents, PROV Activity or FHIR Event without implying conformance not evidenced by the alignment map."]},"hazards":{"applicability":"required","items":["Duplicate events from multiple observers counted twice.","Clock and time zone errors changing order of events."]},"interfaces":{"applicability":"required","items":["W3C PROV-O Activity.","OWL-Time.","CIDOC CRM E5 Event."]},"context":{"applicability":"required","items":["Retention, erasure and privacy statements assume an EU or EEA-style data-protection regime derived from Regulation (EU) 2016/679; jurisdictions with sectoral, statutory-records or no comparable regime will need different retention classes and exception grounds.","The default temporal reference system is the Gregorian calendar with UTC; any other calendar, ordinal scale or geologic timescale must be declared explicitly through the temporal reference system element and will not be understood by consumers that assume the default.","Availability and currency of the IANA time zone database is assumed; jurisdictions that change offsets at short notice may produce records whose stored offset and named zone disagree for a period.","GS1 EPCIS conventions reflect commercial supply-chain practice and are not assumed to apply to civic, scientific, personal or cultural-heritage occurrences.","Access and disclosure defaults assume that participants have legally recognised rights over records describing them; where they do not, the participant-level controls degrade to steward discretion.","Identifier schemes are assumed to be resolvable over an open network; air-gapped or sovereign deployments will need a local resolution authority named in the AGENTS.md bootstrap record.","Civil-time instants default to Gregorian calendar with RFC 3339 offset; historical, archaeological and geologic occurrences must declare a TRS.","Leap seconds are representable (second=60) but not predictable; applications must not invent future leap-second timestamps.","Privacy and erasure expectations assume a jurisdiction in which participation can be personal data; public-chronicle rules still omit non-consenting parties.","Daylight-saving and political timezone changes make unqualified local time non-interoperable, as RFC 3339 requires.","EPCIS CBV business steps are GS1-centric; other industries must supply their own bizStep schemes."]}},"sources":[{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium (W3C)"},{"title":"Time Ontology in OWL (OWL-Time)","url":"https://www.w3.org/TR/owl-time/","note":"World Wide Web Consortium (W3C)"},{"title":"RFC 3339 — Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"Internet Engineering Task Force (IETF)"},{"title":"RFC 9557 — Date and Time on the Internet: Timestamps with Additional Information","url":"https://www.rfc-editor.org/rfc/rfc9557.html","note":"Internet Engineering Task Force (IETF)"},{"title":"EPCIS Ontology (EPCIS 2.0)","url":"https://ref.gs1.org/standards/epcis/epcis-ontology.ttl","note":"GS1"},{"title":"Definition of the CIDOC Conceptual Reference Model, version 7.1.3","url":"https://cidoc-crm.org/html/cidoc_crm_v7.1.3.html","note":"CIDOC CRM Special Interest Group / ICOM"},{"title":"FHIR Event Pattern (Release 5)","url":"https://www.hl7.org/fhir/event.html","note":"Health Level Seven International (HL7)"},{"title":"Semantic Sensor Network Ontology (SSN/SOSA)","url":"https://www.w3.org/TR/vocab-ssn/","note":"World Wide Web Consortium (W3C)"},{"title":"CloudEvents — Version 1.0.2 Specification","url":"https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md","note":"Cloud Native Computing Foundation (CNCF) Serverless Working Group"},{"title":"Extended Date/Time Format (EDTF) Specification","url":"https://lcnetdev.github.io/standards/datetime/edtf.html","note":"Library of Congress, Network Development and MARC Standards Office"},{"title":"OGC GeoSPARQL — A Geographic Query Language for RDF Data, version 1.1","url":"https://docs.ogc.org/is/22-047r1/22-047r1.html","note":"Open Geospatial Consortium (OGC)"},{"title":"Event — Schema.org Type","url":"https://schema.org/Event","note":"Schema.org community (W3C Schema.org Community Group)"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"World Wide Web Consortium (W3C)"},{"title":"Art. 5 GDPR — Principles relating to processing of personal data (unofficial reproduction of Regulation (EU) 2016/679)","url":"https://gdpr-info.eu/art-5-gdpr/","note":"Intersoft Consulting (gdpr-info.eu)"},{"title":"Art. 17 GDPR — Right to erasure ('right to be forgotten') (unofficial reproduction of Regulation (EU) 2016/679)","url":"https://gdpr-info.eu/art-17-gdpr/","note":"Intersoft Consulting (gdpr-info.eu)"},{"title":"Definition of the CIDOC Conceptual Reference Model, Version 7.0 and 7.1.3 (ISO 21127:2023 content)","url":"https://cidoc-crm.org/html/cidoc_crm_v7.0.html","note":"CIDOC CRM Special Interest Group / ICOM"},{"title":"ISO 21127:2023 Information and documentation — A reference ontology for the interchange of cultural heritage information","url":"https://www.iso.org/standard/85100.html","note":"ISO / CIDOC CRM SIG"},{"title":"schema.org EventStatusType","url":"https://schema.org/EventStatusType","note":"Schema.org"},{"title":"RFC 3339 Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"IETF Network Working Group"},{"title":"GS1 EPCIS Standard (ISO/IEC 19987) — visibility event data model","url":"https://ref.gs1.org/standards/epcis/","note":"GS1"},{"title":"ISO/IEC 21838-2:2021 Basic Formal Ontology (BFO) and BFO 2020 occurrent hierarchy","url":"https://github.com/BFO-ontology/BFO-2020","note":"ISO/IEC JTC 1 and BFO-ontology maintainers"}],"openQuestions":["Acquire the paywalled or unparsed normative texts and re-validate against them: ISO 8601-1 and 8601-2, ISO 19108 temporal schema, ISO 15489 records management, ISO 21127:2023, ISO/IEC 19987, ISO/IEC 21838-2, and the GS1 EPCIS 2.0 narrative PDF whose conformance clauses and cardinality rules were never verified.","Fetch RFC 5545 iCalendar (RECURRENCE-ID, EXDATE, exception dates) as a primary source before finalising series, recurrence-template and instance-identity semantics; neither provider consulted it and both currently bound recurrence to schema.org Schedule alone.","Decide whether an explicit fulfilment relation (FHIR Event.basedOn) from an occurrence to the Request/Plan model is required as a first-class link, or whether the existing business-transaction question adequately carries it.","Review Grok's BFO occurrent-hierarchy distinction (Process and process boundary, no Event class) for inclusion as a boundary note, since this plan can add findings and functions but not boundary notes.","Resolve whether CIDOC P12 occurred in the presence of, as distinct from P11 had participant, warrants its own question set under participant-reference or remains a refinement of the existing presence question.","Decide the placement of the CloudEvents 1.0.2 guidance that context attributes are inspectable in the clear and must not carry sensitive payload — most likely a question under access-disclosure-and-projection.","Survey the domain-specific event vocabularies neither provider examined — hazard and disaster taxonomies, judicial and legal proceeding events, astronomical and geological scales, financial transaction event standards, and insurance loss-event definitions — each of which may reveal a required dimension the backbone lacks.","Ground delivery semantics beyond CloudEvents: event-sourcing and CQRS practice, stream ordering guarantees, exactly-once versus at-least-once delivery, and completeness watermarks currently rest on a single tier-2 source.","The official EUR-Lex text of Regulation (EU) 2016/679 could not be retrieved at access time across four URL forms; an unofficial reproduction was used instead, and every retention, erasure and privacy statement should be re-validated against the official text.","ISO 8601-1 and ISO 8601-2, ISO 19108 (temporal schema) and ISO 15489 (records management) are paywalled and were not consulted; EDTF was used as the accessible profile of ISO 8601-2 and OWL-Time as the accessible temporal model.","NIST log-management and audit-control guidance could not be parsed at access time, leaving clock synchronisation, log integrity and back-dating defences without primary grounding.","The GS1 EPCIS 2.0 narrative specification is distributed as a PDF that could not be parsed; the machine-readable EPCIS ontology was used instead, so EPCIS conformance clauses and cardinality rules stated in prose were not verified.","Event-sourcing and CQRS practice, stream ordering guarantees and exactly-once delivery semantics are not grounded; delivery semantics rest only on CloudEvents.","Domain-specific event vocabularies not surveyed include disaster and hazard event taxonomies, judicial and legal proceeding events, astronomical and geological event scales, and financial transaction event standards; each may reveal required dimensions this model lacks.","Uncertainty modelling beyond temporal qualification — for example probabilistic participation, geometric uncertainty distributions or evidential belief functions — is not modelled.","Legal rules on evidence admissibility and on the evidential weight of digital records are out of scope and not surveyed.","Non-Western and indigenous temporal reference systems are accommodated structurally through the temporal reference system element but no concrete system was modelled or tested.","Multilingual labelling, transliteration and script handling for summaries, place names and party names are not addressed.","No normative global event typology; kind schemes are adopted per Dimension.","Relativistic spacetime beyond CIDOC E92/E93 Presence is not operationalized; marked as rare cultural-heritage alignment rather than a required layer.","RFC 5545 iCalendar RECURRENCE-ID and exception dates were not fetched as a primary source in this pass; recurring calendars are bounded to schema.org Schedule and a schedule sibling.","Legal 'event of default' and insurance loss-event statutes are jurisdiction-specific and not modelled as core kinds.","Natural-language event extraction quality metrics are out of scope.","Counterfactual and possible-world happenings have no primary-standard representation here.","Quantum measurement events and sub-second distributed-systems happened-before calculi beyond PROV wasInformedBy are gaps.","Detailed geospatial CRS and moving-object trajectories belong in location and mobility siblings."],"resources":{"spec":"/models/wm-act-015-occurrence-event/spec.yaml","agents":"/models/wm-act-015-occurrence-event/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-015"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-act-015-occurrence-event/spec.yaml","ver-cy/world-models/card-supplements/wm-act-015-occurrence-event.json"],"providers":["Claude","Grok"],"researchStatus":"reviewable-draft","generatedAt":"2026-08-24T23:11:46Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}