World Models · public research draft

Occurrence / Event

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.

AI YAMLAGENTS.mdResearch evidence
Research draft. The Claude + Grok synthesis is public for review and use with caution. It passed structural validation but is not yet a canonical Vercy release because the source and coverage holds below remain open.
Catalogue IDWM-ACT-015
Version0.3.0-research.1
Previous version-
Typeevent
ValidationPassed
Synthesis digestsha256:d57e39ceef269d87…
21Sources
7Bundles
14Layers
28Findings
105Questions
12Artifacts
Format-independent logical structure

Bundles → Layers → Findings → Questions + Artifacts

occurrence-coreOccurrence Core2 layers

The identity, boundary, type and factual status of the happening itself, before anything is said about time, place, participation or cause.

identity-and-individuationIdentity and Individuation3 findings

How one occurrence is delimited from the continuum of activity and how that single occurrence is named and re-found across systems.

occurrence-identifier

Occurrence identifier and deduplication key

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
  1. Which system of record holds the authoritative identifier for this occurrence, and under what identifier scheme was it issued?identity
    Expected answer
    • Name and IRI of the master system
    • Identifier value as issued
    • Identifier scheme IRI and version
  2. What combination of attributes decides that two incoming records denote the same occurrence rather than two distinct occurrences?constraint
    Expected answer
    • Ordered list of deduplication key elements
    • Producer context identifier equivalent to a CloudEvents source
    • Normalisation applied before comparison
  3. When no master-system identifier exists, is a governed IRI or a locally minted UUID or ULID used, and which authority mints it?decision
    Expected answer
    • Identifier kind chosen
    • Minting authority reference
    • Mint instant in RFC 3339 with offset
  4. Under what conditions may the identifier be superseded, and how does a consumer resolve an old identifier to the current record?lifecycle
    Expected answer
    • Superseded identifier values
    • Supersession relation and reason
    • Resolution endpoint or alias register reference
occurrence-individuation

Occurrence boundary and granularity

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
  1. What criterion delimits this happening from the surrounding continuum of activity, and who applied it?definition
    Expected answer
    • Individuation criterion statement
    • Granularity level code
    • Applying party reference
  2. Is the occurrence recorded as an instant with no interior or as an extended process with internal constituent parts?composition
    Expected answer
    • Temporal entity kind (instant or interval)
    • References to constituent occurrences
    • Whether constituents are exhaustive of the whole
  3. How is the record repaired when one recorded occurrence turns out to be two, or two turn out to be one?exception
    Expected answer
    • Split or merge relation type
    • References to resulting and retired occurrences
    • Declaration time and reason for the restructuring
occurrence-designation-and-aboutness

Summary and aboutness

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
  1. What short summary distinguishes this occurrence from similar happenings, and in which language?classification
    Expected answer
    • summary (string)
    • language (bcp47)
  2. Which entities, works or topics is the occurrence about or did it feature, without treating those as participants?relationship
    Expected answer
    • about_refs (ref-list)
    • featured_work_refs (ref-list)
  3. What disambiguating description is required when name and type are insufficient to separate this particular from another of the same kind?quality
    Expected answer
    • disambiguating_description (string)
    • confused_with_refs (ref-list)
Artifacts
  • Occurrence narrativeLanguage-tagged name, summary and optional notes used to disambiguate the happening.
typing-and-factualityTyping and Factuality2 findings

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.

occurrence-classification

Occurrence type and governing vocabulary

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
  1. Which type code or codes classify this occurrence, and from which governed scheme and version do they come?classification
    Expected answer
    • Type code values
    • Scheme IRI and version tag
    • Human-readable label per code
  2. May an occurrence carry more than one type, and how are conflicting or overlapping types reconciled?constraint
    Expected answer
    • Cardinality rule for type codes
    • Precedence or primary-type rule
    • Documented overlaps between codes
  3. Which body governs the type vocabulary, and what is the procedure for adding or retiring a code value?authority
    Expected answer
    • Governing body reference
    • Change procedure reference
    • Retirement and replacement policy
  4. To which external event vocabularies is each local type mapped, and is the mapping exact, broader or narrower?interoperability
    Expected answer
    • Target term IRIs
    • Mapping relation kind
    • Evidence supporting the mapping
Artifacts
  • Occurrence type code listThe published, versioned code list of occurrence types with scheme IRI, labels, definitions, effective date and mappings to external vocabularies.
occurrence-factuality-status

Factual assertion and record status

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
  1. What is the current status of this occurrence record, and does that status describe the happening or the record?state
    Expected answer
    • Status code value
    • Whether the code applies to the happening or the record
    • Instant at which the status took effect
  2. Which status transitions are permitted, which are terminal, and who is authorised to make each transition?lifecycle
    Expected answer
    • Permitted transition pairs
    • Terminal status values
    • Authorised role per transition
  3. When the record asserts that the happening did not occur, what evidence and reason support that negative assertion?evidence
    Expected answer
    • Negation flag
    • Status reason code
    • Supporting source references
  4. How is schedule state such as cancelled, postponed or rescheduled kept distinct from the assertion that the happening occurred?validation
    Expected answer
    • Schedule status code
    • Factual status code
    • Constraint linking the two
temporalityTemporality2 layers

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.

temporal-position-and-extentTemporal Position, Extent and Uncertainty3 findings

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.

event-time-extent

Event time position and extent

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
  1. Is the event time expressed as an instant, a bounded interval, or a duration anchored at one end?temporal
    Expected answer
    • Temporal entity kind
    • Beginning instant
    • End instant or duration
  2. How is an occurrence that has begun but not ended, or whose end is unknown, distinguished from one with a known end?state
    Expected answer
    • Open-endedness marker
    • Reason the end is absent
    • Latest instant at which the occurrence was known to be running
  3. Where the boundaries are inherently fuzzy, which outer and inner bounds are asserted for the beginning and the end?constraint
    Expected answer
    • Earliest and latest possible beginning
    • Earliest and latest possible end
    • Basis for each bound
temporal-reference-frame

Temporal reference frame, offset and time zone

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
  1. Which temporal reference system is the event time expressed in, and is it declared explicitly rather than assumed to be Gregorian and UTC?temporal
    Expected answer
    • Temporal reference system IRI
    • Calendar or scale name
    • Whether the frame is declared or defaulted
  2. 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?constraint
    Expected answer
    • Numeric UTC offset as recorded
    • IANA time zone name
    • Whether '-00:00' was used to mean the local offset is unknown
  3. How are ordinal, relative, geologic or non-Gregorian times conveyed to consumers that expect a civil timestamp?interoperability
    Expected answer
    • Alternate position encoding
    • Conversion rule or refusal to convert
    • Consumer guidance recorded with the value
temporal-uncertainty-precision

Temporal precision, approximation and uncertainty

The stated precision of the time value and any qualification marking it uncertain, approximate, partly unspecified or drawn from a set of alternatives.

Questions
  1. To what precision is the event time actually known, as distinct from the precision at which it happens to be serialised?measurement
    Expected answer
    • Known precision unit
    • Serialised precision
    • Reason for any difference
  2. Is the time asserted as uncertain, approximate, both, or partly unspecified, and to which components does the qualification apply?quality
    Expected answer
    • Qualification marker used
    • Components qualified
    • Qualified literal as written
  3. How must a consumer treat an imprecise or qualified time value when ordering, filtering or joining occurrences?validation
    Expected answer
    • Comparison rule for qualified values
    • Behaviour when precision differs between operands
    • Whether qualified values may be silently coerced
record-time-and-orderingRecord Time, Observation Time and Ordering2 findings

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.

event-versus-record-time

Event time versus observation and ingestion time

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
  1. Which distinct times are recorded for this occurrence, and which clock produced each of them?provenance
    Expected answer
    • Event time value
    • Observation or result time value
    • Record or ingestion time value
    • Clock or system responsible for each
  2. Where the record carries an observation, does the phenomenon time differ from the time the observing act completed, and by how much?temporal
    Expected answer
    • Phenomenon time
    • Result time
    • Stated or computed lag
  3. Which of the recorded times governs retention clocks, query windows and completeness watermarks?decision
    Expected answer
    • Governing time element per purpose
    • Rationale for the choice
    • Behaviour when the governing time is absent
  4. How is a record ingested long after the fact distinguished from one captured in near real time?quality
    Expected answer
    • Latency between event time and record time
    • Backfill or historical-load marker
    • Reporting party for the late record
ordering-and-clock-integrity

Ordering, interval relations and clock integrity

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
  1. When two occurrences carry the same timestamp, what deterministic rule establishes their order?constraint
    Expected answer
    • Tie-break element and its ordering
    • Sequence or monotonic counter value
    • Scope within which the sequence is unique
  2. Which qualitative interval relations between this occurrence and others are asserted rather than computed from timestamps?relationship
    Expected answer
    • Interval relation code
    • Related occurrence reference
    • Asserting party and basis
  3. What is known about the clock that produced the timestamp, and what protects the record against back-dating?security
    Expected answer
    • Clock source and synchronisation status
    • Offset or drift applied at capture
    • Attestation or signature covering the timestamp
Artifacts
  • Time source attestationRecord of the clock source, its synchronisation status and any offset applied at the moment the occurrence timestamp was captured, used when the trustworthiness of the time itself is in question.
spatiality-and-settingSpatiality and Setting2 layers

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.

place-specificationPlace Specification2 findings

The reference to where the occurrence happened and its geometric expression, kept distinct from the identity of the place itself.

place-reference-and-granularity

Place reference, role and granularity

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
  1. Which identified place does this occurrence reference, and in which external register does that identity live?spatial
    Expected answer
    • Place feature IRI or master-system identifier
    • Register or gazetteer reference
    • Place label as recorded
  2. Does the record distinguish the precise point of capture from the wider business or organisational location, and how are both used?composition
    Expected answer
    • Capture point reference
    • Enclosing location reference
    • Rule relating the two
  3. At what granularity is the place asserted, and is that granularity a limit of knowledge or a deliberate generalisation?quality
    Expected answer
    • Granularity level code
    • Whether generalisation was deliberate
    • Party that decided the granularity
  4. How is a place that is unknown, inapplicable or withheld distinguished from one that was simply not captured?exception
    Expected answer
    • Absence reason code
    • Whether withholding is policy-driven
    • Reference to the governing policy
geometry-crs-and-spatial-uncertainty

Geometry, coordinate reference system and positional accuracy

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
  1. In which serialisation is the geometry expressed, and which coordinate reference system URI governs its coordinates?spatial
    Expected answer
    • Geometry serialisation and literal
    • Coordinate reference system URI
    • Whether a default CRS was assumed
  2. What positional accuracy is claimed for the geometry, and what produced that claim?measurement
    Expected answer
    • Accuracy value and unit
    • Measuring device or method
    • Confidence level of the accuracy claim
  3. Has the geometry been coarsened, offset or clipped before disclosure, and is the original retained under restriction?privacy
    Expected answer
    • Generalisation method and parameter
    • Whether the original geometry is retained
    • Policy authorising the generalisation
Artifacts
  • Geospatial trace or geometry fileSerialised geometry, track or map extract expressing where the occurrence took place, exchanged as a file when the geometry is too large or too structured to carry inline.
setting-and-non-physical-contextSetting and Non-Physical Context1 findings

Occurrences that take place wholly or partly outside physical space, and the declared context in which the producer situates them.

virtual-and-hybrid-setting

Virtual, hybrid and producer-context setting

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
  1. Did the occurrence take place in physical space, in a virtual environment, or in both simultaneously?classification
    Expected answer
    • Occurrence mode code
    • Physical place reference where applicable
    • Virtual location identifier where applicable
  2. How is the virtual location identified so that two occurrences in the same environment can be recognised as co-located?identity
    Expected answer
    • Virtual location URI or system identifier
    • Environment or tenant identifier
    • Stability guarantees for that identifier
  3. What producer context does the record declare, and is it a substitute for the physical place or an addition to it?provenance
    Expected answer
    • Producer context URI
    • Relationship of context to physical place
    • Whether the context is the only locational statement
  4. Which jurisdiction governs this occurrence, and is it derived from the physical place or asserted independently?authority
    Expected answer
    • Jurisdiction code
    • Derivation basis
    • Party that asserted the jurisdiction
participation-and-effectsParticipation and Effects2 layers

Who and what took part in the occurrence, in what capacity, and which entities were used, produced, transformed or invalidated by it.

participants-and-rolesParticipants and Roles2 findings

The parties and objects involved and the capacity in which each was involved, including delegation of that capacity.

participant-reference

Participant and subject reference

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
  1. Which parties and objects are recorded as taking part, and by which external identifiers are they referenced?relationship
    Expected answer
    • Participant references and kinds
    • External identifier scheme per participant
    • Register in which each identity is maintained
  2. Which participant is the subject or feature of interest of the occurrence, as distinct from the others involved?composition
    Expected answer
    • Subject reference
    • Basis for singling it out
    • Whether more than one subject is permitted
  3. Does this occurrence type require at least one participant, and is an occurrence with no identified participant valid?constraint
    Expected answer
    • Minimum participation cardinality per type
    • Validity rule for participant-free occurrences
    • Reason code when no participant is identified
  4. How is a participant recorded when their identity is unknown, pseudonymous or deliberately not resolved?privacy
    Expected answer
    • Pseudonym or local handle
    • Whether resolution is possible and by whom
    • Policy governing non-resolution
role-capacity-and-delegation

Role, capacity, presence and delegation

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
  1. In what capacity did each participant take part, and from which governed role vocabulary is that capacity drawn?classification
    Expected answer
    • Role code per participant
    • Role vocabulary IRI and version
    • Whether a participant may hold several roles
  2. On whose behalf did a participant act, and how far back does the recorded delegation chain reach?authority
    Expected answer
    • Delegating party reference
    • Depth and completeness of the chain
    • Instrument or plan authorising the delegation
  3. Was the participant physically or virtually present, represented, or recorded as involved without being present?state
    Expected answer
    • Presence mode code
    • Representing party where applicable
    • Basis for asserting presence
  4. Which recorded participation facts stop short of asserting intent or responsibility, and where does that assertion belong instead?definition
    Expected answer
    • Participation facts recorded here
    • Facts deferred to the Act model
    • Reference to the specialising record if one exists
entities-and-changesEntities and Changes1 findings

What the occurrence consumed, produced, transformed or invalidated, and in what quantity.

affected-entities-and-transformation

Entities used, generated and transformed

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
  1. Which entities did the occurrence use as inputs and which did it generate, and are those sets asserted to be complete?composition
    Expected answer
    • Used entity references
    • Generated entity references
    • Completeness assertion for each set
  2. In what quantities were entities consumed or produced, and in which units and measurement scale?measurement
    Expected answer
    • Quantity values with units
    • Uncertainty or tolerance where stated
    • Measuring method reference
  3. What state or disposition of an affected entity changed as a result of the occurrence?state
    Expected answer
    • Entity reference
    • Prior and resulting disposition codes
    • Whether the change is reversible
  4. When inputs and outputs are recorded by separate occurrences, what identifier links them into one transformation?relationship
    Expected answer
    • Transformation linkage identifier
    • Occurrences sharing that identifier
    • Authority that issued the linkage identifier
explanation-and-compositionExplanation and Composition2 layers

How occurrences aggregate into larger units and how they are asserted to influence or explain one another.

aggregation-and-recurrenceAggregation, Series and Recurrence1 findings

Grouping occurrences into wholes, episodes and series, and separating an individual instance from the recurring pattern it instantiates.

part-whole-episode-and-series

Part-whole aggregation, episodes and recurring series

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
  1. Of which larger occurrence or episode is this occurrence a part, and is the parent's membership asserted to be exhaustive?composition
    Expected answer
    • Parent occurrence reference
    • Sibling member references
    • Whether membership is exhaustive
  2. May one occurrence belong to more than one episode or aggregate at the same time, and how are competing groupings reconciled?constraint
    Expected answer
    • Multiple-membership rule
    • Grouping criterion per aggregate
    • Precedence rule between aggregates
  3. Is the temporal span of the aggregate asserted independently or derived from its members, and what happens when a member is added or retracted?temporal
    Expected answer
    • Aggregate span values
    • Derivation rule or independent assertion
    • Recomputation behaviour on membership change
  4. Is this occurrence an instance of a recurring series, and how is the series identity kept distinct from the instance identity?identity
    Expected answer
    • Series reference and identifier
    • Instance index or occurrence date within the series
    • Recurrence rule governing the series
causality-and-purposeCausality and Purpose2 findings

Asserted influence between occurrences, and the business or motivational context that explains why the occurrence took place.

purpose-and-business-context

Purpose, business step and reason

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
  1. Which business process step does this occurrence represent, and from which governed vocabulary is that step drawn?classification
    Expected answer
    • Business step code
    • Vocabulary IRI and version
    • Process definition reference
  2. What business or physical disposition results from the occurrence, and does it persist until another occurrence changes it?state
    Expected answer
    • Disposition code
    • Persistence assumption
    • Occurrence that later changes it
  3. Which business transactions, orders or cases does the occurrence relate to, and in what role?relationship
    Expected answer
    • Transaction identifiers and types
    • Role of the occurrence in each
    • Issuing party for each transaction identifier
  4. What recorded reason or motivating circumstance is asserted for the occurrence, and is it a fact or an interpretation?evidence
    Expected answer
    • Reason code or motivating occurrence reference
    • Whether recorded as fact or interpretation
    • Party that supplied the reason
evidence-and-assertion-qualityEvidence and Assertion Quality2 layers

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.

assertion-and-evidenceAssertion Provenance and Evidence2 findings

Who said the occurrence happened, through what chain of reporting, and what evidence is attached and protected.

source-record-and-reporting-chain

Source record and reporting chain

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
  1. Who supplied the account from which this occurrence was recorded, and when did they supply it?provenance
    Expected answer
    • Reporting party reference
    • Report submission time in RFC 3339 with offset
    • Channel through which the report arrived
  2. Is the account first-hand, reported by a proxy, or derived from another record, and is that standing recorded explicitly?authority
    Expected answer
    • First-hand or reported marker
    • Proxy party where applicable
    • Upstream record reference where derived
  3. What intermediaries stand between the happening and this record, and is the chain complete?relationship
    Expected answer
    • Ordered intermediary references
    • Completeness assertion for the chain
    • Transformations applied at each hop
  4. What is known about the reliability or accreditation of each source, and where is that judgement recorded?quality
    Expected answer
    • Reliability or accreditation value
    • Scale or certification scheme used
    • Party that made the judgement
Artifacts
  • Source account documentThe account on which the occurrence record rests: witness statement, submitted report, regulatory filing, message record or machine log extract.
evidence-artifacts-and-integrity

Evidence artifacts, integrity and custody

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
  1. What evidence artifacts are attached to this occurrence, and what does each purport to show?evidence
    Expected answer
    • Artifact references and media types
    • Claim each artifact supports
    • Capture device or system per artifact
  2. What digest or signature demonstrates that an evidence artifact has not changed since capture, and who computed it?security
    Expected answer
    • Digest algorithm and value
    • Computation time in RFC 3339 with offset
    • Computing party reference
  3. Who has held or accessed the evidence since capture, and is the custody record gapless?access
    Expected answer
    • Ordered custody entries with parties and times
    • Gap or discontinuity markers
    • Register in which custody is maintained
  4. How is an evidence artifact bound to this occurrence rather than to a similar one, and what happens if the binding is disputed?validation
    Expected answer
    • Binding identifier or assertion
    • Party that asserted the binding
    • Dispute handling procedure
Artifacts
  • Evidence media fileCaptured media or data file evidencing that the occurrence happened as recorded.
  • Chain of custody logSequential register of who held, moved, copied or accessed an evidence artifact from capture onward.
certainty-and-correctionCertainty, Conflict and Correction2 findings

How confident the record is, how conflicting accounts are held, and how an erroneous record is corrected without mutation.

corroboration-and-certainty

Corroboration, certainty and conflicting accounts

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
  1. What certainty is asserted that the occurrence happened as recorded, and on what defined scale?quality
    Expected answer
    • Certainty value
    • Scale definition and its endpoints
    • Party that assigned the certainty
  2. How many genuinely independent sources corroborate the occurrence, and what makes them independent?evidence
    Expected answer
    • Corroborating source references
    • Independence criterion applied
    • Certainty before and after corroboration
  3. When two accounts of the same happening disagree, are both retained, and how is the disagreement represented?exception
    Expected answer
    • Conflicting record references
    • Conflicting elements identified
    • Whether a preferred account is designated and by whom
  4. What certainty threshold must be met before the occurrence may be published, acted upon or propagated to downstream models?decision
    Expected answer
    • Threshold value per purpose
    • Authorising role
    • Behaviour for records below threshold
correction-retraction-and-versioning

Correction, retraction and supersession

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
  1. By what mechanism is an erroneous record repudiated while the erroneous content itself is preserved?lifecycle
    Expected answer
    • Error declaration record reference
    • Declaration time in RFC 3339 with offset
    • Declaring party reference
  2. Does a corrective record reuse the identifier of the record it corrects, or take a new one, and how is the relation expressed?identity
    Expected answer
    • Identifier reuse rule
    • Corrective record references
    • Relation type between erroneous and corrective records
  3. Which changes count as material and require a correction record rather than an additive in-place update?constraint
    Expected answer
    • List of material elements
    • List of additive elements
    • Adjudicating role when a change is contested
  4. How does a consumer holding a copy detect that the record has been superseded or repudiated?interoperability
    Expected answer
    • Supersession marker on the record
    • Notification or feed mechanism
    • Latest-version resolution rule
Artifacts
  • Correction notice recordThe filed declaration that a recorded occurrence is in error, naming the erroneous record, the reason, the declaring party and the corrective records that replace it.
governance-and-exchangeGovernance and Exchange2 layers

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.

stewardship-access-and-retentionStewardship, Access and Retention3 findings

Accountability for the record, control over its disclosure, and the rules governing how long it survives and how it ends.

ownership-and-stewardship

Ownership, stewardship and amendment authority

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
  1. Which party is accountable for this occurrence record, and is that the primary actor or an observing registrar?ownership
    Expected answer
    • Accountable party reference
    • Basis of accountability
    • Registrar reference where distinct
  2. Who is authorised to declare this record in error or to file a corrective record, and who is not?authority
    Expected answer
    • Authorised roles for repudiation
    • Authorised roles for correction
    • Escalation path when authority is contested
  3. What rights does a recorded participant retain over the portion of the record describing their own participation?ownership
    Expected answer
    • Participant rights enumerated
    • Mechanism by which they are exercised
    • Limits imposed by other parties' rights
  4. How is stewardship transferred when the accountable party dissolves, merges or hands over the register?process
    Expected answer
    • Transfer instrument reference
    • Effective time of transfer
    • Continuity guarantees for identifiers
access-disclosure-and-projection

Access, disclosure and published projections

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
  1. What is the default visibility of this occurrence, and which party decides that default?access
    Expected answer
    • Visibility class
    • Deciding role
    • Policy reference establishing the default
  2. How does a participant grant or withhold disclosure of their own participation without affecting the rest of the record?privacy
    Expected answer
    • Consent or grant reference
    • Scope of the grant in model terms
    • Withdrawal mechanism and its effect
  3. Under what conditions may participant withholding be overridden, and who authorises the override?exception
    Expected answer
    • Override ground
    • Authorising role
    • Notification obligation to affected parties
  4. Which named projections of this occurrence may be published, and what does each deliberately omit?interoperability
    Expected answer
    • Projection names
    • Elements omitted per projection
    • Audience and licence per projection
Artifacts
  • Access policy documentMachine-readable policy stating which parties may perform which actions on which parts of the occurrence record, with constraints, duties and a declared conflict-resolution strategy.
retention-and-deletion

Retention, erasure and disposition

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
  1. How long is this occurrence retained, from which recorded time does that period run, and on what basis was it set?retention
    Expected answer
    • Retention period
    • Governing time element
    • Legal, contractual or policy basis
  2. When an erasure obligation applies, which elements are removed and which survive so that the occurrence's existence and identifier remain intact?privacy
    Expected answer
    • Elements subject to removal
    • Elements retained and why
    • Resulting record state after redaction
  3. Which exceptions — legal hold, legal claims, public-interest archiving, research or statistics, legal obligation — justify continued retention here?exception
    Expected answer
    • Exception ground invoked
    • Authorising role and decision time
    • Safeguards applied under the exception
  4. What evidences that a retention decision was actually executed against both the record and its evidence artifacts?validation
    Expected answer
    • Disposition action performed
    • Execution time in RFC 3339 with offset
    • Certificate or register entry reference
Artifacts
  • Disposition certificateEvidence that a retention decision was carried out — redaction, anonymisation, archival transfer or destruction — covering both the occurrence record and its dependent evidence artifacts.
interoperability-and-deliveryInteroperability and Delivery2 findings

How the occurrence is aligned to external vocabularies without overclaiming conformance, and how it is transmitted, deduplicated and assessed for completeness at the boundary.

external-alignment-and-conflicts

External alignment, conformance evidence and recorded conflicts

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
  1. To which external vocabularies and versions is this model aligned, and is each alignment exact, broader or narrower?interoperability
    Expected answer
    • Target vocabulary IRIs and versions
    • Alignment relation per mapped element
    • Date the alignment was last verified
  2. What evidence supports any claim of conformance, as opposed to a claim of alignment?validation
    Expected answer
    • Conformance test or certification reference
    • Scope of the conformance claim
    • Elements explicitly excluded from the claim
  3. Which conflicts between aligned standards are recorded, and how must an implementer choose between them?exception
    Expected answer
    • Conflict statement per pair of standards
    • Chosen behaviour and its rationale
    • Consumer guidance for the unresolved cases
  4. Who maintains each mapping, and how often is it re-verified against the upstream standard?authority
    Expected answer
    • Maintaining party reference
    • Re-verification interval
    • Notification path for upstream changes
Artifacts
  • Alignment and conflict registerVersioned table mapping local occurrence elements to external vocabulary terms, recording the alignment relation, supporting evidence, verification date and known conflicts.
delivery-deduplication-and-completeness

Delivery, deduplication and completeness

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
  1. Which envelope carries the occurrence in transit, and which envelope attributes are projections of model elements rather than new facts?interoperability
    Expected answer
    • Envelope specification and version
    • Attribute-to-element mapping
    • Attributes carrying no model semantics
  2. On what rule may a receiver treat two deliveries as the same occurrence, and what must it never treat as a duplicate?constraint
    Expected answer
    • Duplicate detection key
    • Redelivery marker where present
    • Cases explicitly excluded from deduplication
  3. How is a correction propagated to recipients that already consumed the erroneous record?process
    Expected answer
    • Propagation mechanism
    • Ordering guarantee relative to the original
    • Acknowledgement expectation
  4. How does a consumer determine that it has received all occurrences up to a given point, and how are gaps declared?quality
    Expected answer
    • Completeness watermark and its governing time element
    • Gap declaration mechanism
    • Backfill policy for late arrivals

Publication holds

  • Source verification: every accepted URL must be re-fetched live and every version pin confirmed before publication — CIDOC CRM 7.1.3, schema.org v30.0, EPCIS 2.0 ontology, FHIR R5 5.0.0, CloudEvents 1.0.2, GeoSPARQL 1.1, RFC 3339, RFC 9557, EDTF, ODRL 2.2 and SSN/SOSA.
  • OWL-Time version divergence must be pinned: the base cites the 19 October 2017 Recommendation plus the 15 November 2022 Candidate Recommendation Draft while Grok cites only the 2022 draft; one status must be chosen and stated before any temporal claim is published.
  • Legal grounding hold: SRC-014 and SRC-015 are unofficial gdpr-info.eu reproductions at authority tier 4. Every retention, erasure and privacy statement must be re-validated against the official EUR-Lex text of Regulation (EU) 2016/679 before publication.
  • Domain-profile validation hold: the backbone must be exercised against at least three unlike profiles — cultural heritage, supply-chain visibility, and clinical or civic recording — before any claim that time, place, participation and causality generalise across them.
  • The time-source-attestation artifact and all clock-integrity, log-integrity and back-dating claims have no primary grounding (NIST retrieval failed in the base pass and Grok fetched nothing in this area). Publish only as declared model policy, or hold the node.
  • No fetched source defines a normative reliability or certainty scale, so the corroboration scale must be published as a per-Dimension declaration with stated endpoints, never as a governed value set.
  • The reconciliation of GDPR erasure with append-only correction — redacting personal elements while preserving the occurrence's existence and identifier — is a construction, not a cited resolution, and must be labelled as such wherever it appears.

Deferred research

  • 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.