World Models · public research draft

Physical Item Instance

Model the context an agent needs to identify, describe, track and govern one individual physical thing as a distinguishable instance, separately from the type it instantiates and from any value, inventory or asset projection over it.

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-OBJ-001
Version0.3.0-research.1
Previous version-
Typeentity
ValidationPassed
Synthesis digestsha256:ef790059c3ed52d8…
27Sources
6Bundles
13Layers
31Findings
115Questions
29Artifacts
Format-independent logical structure

Bundles → Layers → Findings → Questions + Artifacts

identity-and-designationIdentity and designation2 layers

Everything needed to tell this individual thing apart from every other thing, to bind marks and identifiers to it, and to decide when it is still the same thing.

instance-identificationInstance identification5 findings

The identifiers borne by the item, the physical marks and data carriers that carry them, and the resolution of an observed identifier back to one record.

master-identifier

Master identifier and issuing authority

Which identifier is authoritative for this item, who issued it, under which scheme and syntax, and what uniqueness guarantees apply. ISO/IEC 15459-4 specifies a unique, non-significant string for individual items issued under a registered issuing agency; GS1 expresses the same idea as a primary key plus serial qualifier.

Questions
  1. Which single identifier is the authoritative master identifier for this item, and which agency or system issued it?identity
    Expected answer
    • identifier value
    • identifier scheme code
    • issuing agency or master system reference
    • assignment timestamp
  2. What uniqueness and non-reuse guarantee does the issuing scheme give, and over what period?constraint
    Expected answer
    • uniqueness scope (global, issuer, adopting Dimension)
    • reuse policy statement
    • guarantee duration
  3. If no authoritative external identifier exists, which locally minted identifier is used and how is its provenance recorded?provenance
    Expected answer
    • local identifier value (UUID or ULID)
    • minting authority
    • reason no governed identifier was available
  4. In which syntaxes may this identifier legitimately be expressed for exchange?interoperability
    Expected answer
    • canonical form
    • alternate syntax list (EPC URI, GS1 Digital Link URI, IRI, plain string)
    • transformation rule reference
Artifacts
  • Identifier assignment recordThe record evidencing that a specific identifier was allocated to this specific physical thing by a named authority, corresponding to CIDOC CRM identifier assignment.
identity-marking

Identity marks and data carriers

The physical realisation of identity on the thing itself: marking method, placement, durability, legibility, and the machine-readable carrier. IEC 61406-1 requires a globally unique identification link, machine readable via 2D symbol or NFC and attached to the individual unit; ESPR-driven passports require a data carrier on the product.

Questions
  1. How is each identifier physically applied to the item and where on the item is it placed?composition
    Expected answer
    • marking method code (engraved, etched, printed label, moulded, RFID tag)
    • placement description
    • application timestamp
  2. Is the mark expected to survive the item's service life, and what happens when it becomes illegible or is removed?quality
    Expected answer
    • durability class
    • current legibility state
    • re-marking procedure reference
  3. What exactly does the machine-readable carrier encode, and does it resolve to a live information service?interoperability
    Expected answer
    • carrier type code
    • encoded payload string
    • resolver endpoint reference
    • link type set
  4. Who is permitted to apply, alter or remove an identity mark on this item?authority
    Expected answer
    • authorised role reference
    • legal or contractual basis
    • alteration event log reference
Artifacts
  • Identity nameplate, label or tagThe physical or photographed nameplate, label, engraving or tag carrying human-readable and machine-readable identity on the item.
identifier-resolution

Identifier resolution, aliases and collisions

How an observed identifier is resolved to exactly one item record, how multiple scheme identifiers for the same thing are related, and how duplicates, cloned identifiers and merge/split situations are handled.

Questions
  1. Given a scanned or quoted identifier, what procedure resolves it to at most one item record?validation
    Expected answer
    • resolution rule reference
    • matched record reference
    • match confidence
    • unresolved fallback action
  2. Which additional identifiers are asserted to designate this same item, and on whose authority?relationship
    Expected answer
    • alias identifier list
    • asserting party reference
    • assertion timestamp
    • equivalence strength
  3. What is done when two physical things present the same identifier, or one thing presents conflicting identifiers?exception
    Expected answer
    • collision case reference
    • triage decision
    • quarantine state
    • investigation reference
  4. How are duplicate records merged or an erroneously merged record split, and how is the prior identifier preserved?lifecycle
    Expected answer
    • merge or split event record
    • surviving record reference
    • retired identifier list
    • reversal procedure reference
Artifacts
  • Identity resolution decision logLog of resolution, merge, split and quarantine decisions with the evidence relied upon, so identity changes are reversible and auditable.
non-serial-identification

Legibility, cloning risk and distinguishing marks

Object ID requires inscriptions and markings, distinguishing features and photographs because unique numbers can be copied, lost or never assigned. A cloned serial or unreadable tag does not by itself prove a second item, nor does it destroy the original item's identity. Condition of the mark is evidence about identification quality, not a new identifier.

Questions
  1. Is each identifier mark currently legible, damaged, over-labelled, removed or only photographically documented, and when was that assessed?quality
    Expected answer
    • legibility (legible|damaged|illegible|removed|photo-only)
    • assessed_at
    • assessor_ref
    • method
  2. What Object ID-style distinguishing features, inscriptions or damage patterns uniquely describe this object even if serials are absent or cloned?identity
    Expected answer
    • inscriptions
    • distinguishing_features
    • feature_photographs[]
    • measurement_set_ref
  3. Is there evidence that a presented identifier is cloned, counterfeit, reused or bound to another item, and what is the confidence and evidence of that suspicion?security
    Expected answer
    • suspicion_status (none|suspect|confirmed-conflict)
    • conflicting_item_id
    • evidence_refs[]
    • confidence
Artifacts
  • Identification evidence packPhotographs, inscriptions, distinguishing-feature notes and legibility assessments used when numbers are missing, unreadable or disputed. Object ID requires photographs plus the nine description categories kept in a secure place.
digital-representation-binding

Digital link, passport and shell

IEC 61406-1 defines the IL string as a URL that is both the globally unique identification of a physical object and a pointer to related information. Schema.org requires that a GS1 Digital Link containing serial AI 21 appear only on IndividualProduct. ESPR establishes a digital product passport with a unique product identifier, unique operator identifier and unique facility identifier, accessed via a data carrier on the product. IDTA AAS gives the asset a recommended globalAssetId (IEC 61406 format) and optional specificAssetIds, while the Administration Shell has a separate mandatory id. These are representations and links, not a second physical item.

Questions
  1. What resolvable IRI or URL currently identifies this physical object (IEC 61406 IL, GS1 Digital Link with AI 21, DPP unique product identifier), and does it encode instance grain rather than type or lot?identity
    Expected answer
    • resolvable_iris[] with scheme, url, grain (instance|type|lot|unspecified), last_resolved_at, resolution_status.
  2. Which digital representations (DPP, AAS, other twin) describe this item, what are their own identifiers, and which of those identifiers are explicitly not the item master?interoperability
    Expected answer
    • representations[] with kind (dpp|aas|twin|other), representation_id, global_asset_id, specific_asset_ids, distinct_from_item_master (boolean).
  3. If a DPP or similar passport exists, what unique operator identifier and unique facility identifier are bound to this item instance, and at which production event?provenance
    Expected answer
    • operator_identifier
    • facility_identifier
    • bound_at_event_id
    • event_time
    • Treat operator and facility as referenced parties/places, not as item identity.
Artifacts
  • Digital representation bindingA link from the physical item to an IL, Digital Link, DPP or AAS record, recording that the representation id is not a second item master.
type-linkage-and-individuationType linkage and individuation3 findings

The link from this instance to the class it instantiates, and the rules that decide when the instance begins, persists or ceases to be the same individual.

instance-of-type

Instance-of-type reference

The resolved reference from this individual to its product type or configuration, and the confidence in that resolution. schema.org places IndividualProduct under Product with isVariantOf pointing at a ProductModel; EPCIS keeps class-level identification separate from instance-level identification.

Questions
  1. Which type or configuration record does this item instantiate, and in which sibling model is it mastered?classification
    Expected answer
    • type model identifier
    • type record reference
    • configuration reference
    • resolution confidence
  2. On what evidence was the type resolved: marking, documentation, expert determination or inference?evidence
    Expected answer
    • resolution method code
    • evidence artifact reference
    • determining party reference
  3. In what respects does this specimen deviate from its type specification, and are those deviations authorised?constraint
    Expected answer
    • deviation description
    • authorisation reference
    • measured value versus specified value
  4. How is an item that cannot be assigned to any known type represented without inventing one?exception
    Expected answer
    • unclassified flag
    • provisional descriptive text
    • review task reference
Artifacts
  • Type determination recordDated statement of which class the item instantiates, by whom and on what evidence, including provisional or contested determinations.
identity-continuity

Individuation and identity continuity

The rules deciding what counts as one item and whether identity survives repair, component replacement, reconfiguration, division or joining. No consulted standard settles this; CIDOC CRM anchors documentation units and composition, and PROV offers specializationOf/alternateOf to relate records without asserting sameness.

Questions
  1. What physical criterion individuates this thing as one item rather than a part, a set or a quantity?definition
    Expected answer
    • individuation criterion text
    • boundary description
    • granularity level code
  2. Which changes preserve identity and which terminate it and create a successor item?lifecycle
    Expected answer
    • continuity rule reference
    • triggering change type
    • successor item reference
  3. When an item is split, merged or rebuilt, how is lineage to predecessor and successor items recorded?provenance
    Expected answer
    • predecessor item references
    • successor item references
    • derivation event reference
  4. Who decides a contested continuity case and by what documented rule?authority
    Expected answer
    • deciding role
    • rule citation
    • decision record reference
Artifacts
  • Identity continuity policyThe written, versioned rule set stating which interventions preserve item identity in this Dimension, needed because no cited standard resolves it.
configuration-and-lot-linkage

Configuration and lot inputs

A product configuration may classify a configured instance (variant-instance boundary). A lot or batch identifier is not an instance identifier; Schema.org places lot-bearing Digital Links on SomeProducts unless there is only a specific product. IEC 61406-2 separately treats lots/batches. Lot membership and configuration are classification or provenance facts on the instance.

Questions
  1. What product configuration or variant, if any, classifies this configured instance, and is that a sibling configuration master rather than an extra serial?classification
    Expected answer
    • configuration_model_id (e.g. WM-OBJ-017)
    • configuration_id
    • configuration_iri
    • is_instance_specific_option_set (boolean)
  2. From which lot or batch was this instance produced or separated, and is that lot used only as provenance rather than as the item identifier?provenance
    Expected answer
    • lot_id
    • lot_scheme
    • lot_is_not_instance_id (boolean, must be true for this model)
    • production_event_ref
  3. Which instance-level master data attributes (EPCIS ILMD such as expiration) belong to this instance rather than to the type, and what is their validity window?classification
    Expected answer
    • ilmd_attributes[] with name, value, unit, valid_from, valid_to, source_event_id.
Artifacts
  • Instance master data snapshotILMD or equivalent instance attributes (for example expiration) recorded at commissioning or transformation, distinct from type catalogue data.
physical-characterisationPhysical characterisation of the specimen2 layers

What is true of this particular specimen as measured or observed, and how it is physically built up, as distinct from what its type specifies.

observed-propertiesObserved and as-built properties2 findings

Properties measured on this specimen, their measurement context, and the materials it is actually made of.

measured-attributes

Measured attributes and measurement context

Quantities measured on this individual (mass, dimensions, readings) together with unit, method, instrument, uncertainty and the separation of measurement time from record time.

Questions
  1. Which properties are measured on this specimen rather than inherited from its type?measurement
    Expected answer
    • property code
    • measured value
    • unit of measure code
  2. By what method and instrument was each value obtained, and with what stated uncertainty?quality
    Expected answer
    • method reference
    • instrument or sensor reference
    • uncertainty or tolerance
    • calibration reference
  3. When was the value measured and when was it recorded, and which one governs currency of the value?temporal
    Expected answer
    • measurement timestamp (RFC 3339)
    • record timestamp (RFC 3339)
    • validity window
  4. How are conflicting measurements of the same property at the same time reconciled?exception
    Expected answer
    • conflict case reference
    • precedence rule
    • superseded value reference
Artifacts
  • Measurement or test reportDated report of measurements taken on this specimen, including method, instrument identity and uncertainty, suitable as evidence.
material-content

Material content and substances of concern

What this specimen is actually made of, referenced to material classes rather than restated, including substance declarations that product-passport regimes attach to the individual product.

Questions
  1. Which material classes constitute this item, and in what proportions where known?composition
    Expected answer
    • material class references
    • proportion or mass fraction
    • determination basis
  2. Which declarable or hazardous substances are recorded for this individual, and under which regime?requirement
    Expected answer
    • substance identifier
    • concentration
    • regulatory regime reference
    • declaration timestamp
  3. Is the material content declared, tested or inferred from the type specification?evidence
    Expected answer
    • determination method code
    • evidence artifact reference
    • confidence
Artifacts
  • Material or substance declarationDeclaration listing material content and substances of concern for the product, as carried into product-passport payloads.
instance-structureInstance structure and containment boundary2 findings

The item's membership in assemblies and the point at which instance identity stops and quantity begins.

component-membership

Component membership in an assembly

Whether this item is currently or was formerly installed in a parent item, in what position or role, and over what period. The assembly graph itself is mastered by WM-OBJ-012; EPCIS AggregationEvent and CIDOC P46 supply the parent/child semantics.

Questions
  1. Which parent item does this item form part of at a given instant, and in what position or role?composition
    Expected answer
    • parent item reference
    • position or role code
    • effective period start and end
  2. Which events installed or removed this item from a parent, and who performed them?event
    Expected answer
    • install or remove event reference
    • event timestamp
    • performing party reference
  3. Do child components retain their own instance identity while installed, or are they absorbed into the parent?identity
    Expected answer
    • child identity retention flag
    • child item references
    • absorption rule reference
  4. Where is the full assembly structure mastered, and which parts of it may be cached here?interoperability
    Expected answer
    • mastering model identifier
    • permitted cached fields
    • cache refresh rule
Artifacts
  • As-built configuration extractExtract of the assembly state showing this item's parent, position and effective period at a stated instant, sourced from the as-built assembly model.
instance-boundary

Boundary against quantity, batch and bulk

The rule that refuses instance identity to matter with no individuating boundary. ISO 22095 chain-of-custody models such as mass balance and controlled blending explicitly do not preserve one-to-one identity, and EPCIS provides class-level quantity fields precisely for this case.

Questions
  1. On what test is a candidate refused an item-instance record and represented as a quantity or batch instead?decision
    Expected answer
    • refusal test statement
    • representation chosen (quantity, lot, batch)
    • referring model identifier
  2. How are non-instance contents held inside this item (fluids, consumables, loose parts) represented without minting instances?composition
    Expected answer
    • content class reference
    • quantity and unit
    • measurement timestamp
  3. Which chain-of-custody model applies to the material in or around this item, and does it preserve identity?constraint
    Expected answer
    • chain-of-custody model code
    • identity preservation flag
    • standard reference
state-condition-and-lifecycleState, condition and authenticity3 layers

Where the item stands in its life, what shape it is in, what has been done to it, and whether it is what it claims to be.

lifecycle-stateLifecycle state3 findings

The item's status in a governed state model and the terminal states that end its tracked existence.

lifecycle-status

Lifecycle status and permitted transitions

The current governed status of the item, the transition that produced it, and the constraints on legal transitions. EPCIS disposition expresses the business state of an object after an event, and persistentDisposition expresses states that survive later events.

Questions
  1. What is the item's current lifecycle status and which event set it?state
    Expected answer
    • status code
    • setting event reference
    • status effective timestamp
  2. Which status transitions are permitted from the current status, and which are forbidden?constraint
    Expected answer
    • allowed transition list
    • guard condition
    • authorising role
  3. Which states persist across subsequent events until explicitly cleared, and who may clear them?lifecycle
    Expected answer
    • persistent state code
    • set and unset event references
    • clearing authority
  4. How is an item represented whose status is genuinely unknown, and for how long may that persist?exception
    Expected answer
    • unknown-status flag
    • last known status
    • last observation timestamp
    • escalation rule
Artifacts
  • Lifecycle state model definitionVersioned definition of the status vocabulary, permitted transitions, guards and authorising roles used by this Dimension, mapped to external vocabularies where they exist.
end-of-life

End of life, loss and disposal

How the item leaves tracked existence: destruction, recycling, permanent loss, theft or export beyond the record's reach, and what evidence closes the record without deleting it.

Questions
  1. By what mode did the item leave tracked existence, and when?lifecycle
    Expected answer
    • disposal mode code
    • effective timestamp
    • responsible party reference
  2. What evidence proves the terminal event, and who issued it?evidence
    Expected answer
    • evidence artifact reference
    • issuer reference
    • verification status
  3. Can a terminal state be reversed, for example when a lost item is recovered, and how is the gap recorded?exception
    Expected answer
    • reversal permitted flag
    • recovery event reference
    • unobserved period start and end
  4. How long is the record retained after the item ceases to exist, and under what obligation?retention
    Expected answer
    • retention period
    • legal or contractual basis
    • disposition action at expiry
Artifacts
  • Disposal, destruction or recycling certificateThird-party or operator certificate evidencing destruction, recycling or other permanent retirement of the individual item.
loss-theft-and-recovery

Loss, theft, seizure, recovery and deaccession

Object ID exists because stolen and trafficked objects cannot be recovered without documentation, photographs and distinguishing features; INTERPOL and customs use that documentation. Unknown whereabouts is not the same as non-existence. Seizure, loan, exhibition and deaccession change custody or collection membership without necessarily destroying the object. These states lack a single global code list and must be recorded as explicit exceptional statuses with evidence.

Questions
  1. Is the item missing to its holder, reported stolen, seized by authority, in dispute, or merely not recently observed, and when was that status asserted?exception
    Expected answer
    • exceptional_status (missing|stolen|seized|disputed|not-recently-observed|none)
    • asserted_at
    • asserted_by
    • legal_reference
    • last_known_location_ref
    • last_known_custodian_ref
  2. If previously missing or stolen, when was it recovered or returned, by whom, and did identity, condition or custody need re-validation?event
    Expected answer
    • recovery_event_time
    • recovered_by
    • identity_revalidated (boolean)
    • condition_assessment_id
    • new_custody_record_id
  3. Has a museum, court or owner deaccessioned, forfeited or legally abandoned the item, and does that end title, custody, or only collection membership?ownership
    Expected answer
    • deaccession_or_forfeiture (boolean)
    • instrument_ref
    • effects_on (title|custody|collection-membership)
    • event_time
Artifacts
  • Loss, theft, seizure or recovery case fileExceptional-status assertion with legal or operational evidence, last-known facts, and recovery or deaccession outcome. Object ID documentation is the cultural-goods form of this artifact.
condition-and-interventionCondition and intervention history1 findings

Dated judgements about the item's physical condition and the record of interventions that changed it.

condition-assessment

Condition assessment and intervention history

Condition as an assessed, dated judgement bound to a scale, assessor and method, together with the repairs, restorations and modifications that altered the individual. CIDOC CRM binds condition states to time-spans; schema.org itemCondition is a commerce enumeration and is not equivalent.

Questions
  1. What condition grade is asserted, on which named scale, and by whom?quality
    Expected answer
    • condition grade code
    • scale identifier and version
    • assessor reference
    • assessment timestamp
  2. By what method was condition determined: visual inspection, measurement, functional test or declaration?measurement
    Expected answer
    • assessment method code
    • observed defect list
    • supporting artifact reference
  3. Which interventions have been performed on this item, by whom, and what did they change?process
    Expected answer
    • intervention type code
    • performing party reference
    • affected components
    • completion timestamp
  4. How stale may a condition assessment be before it must not be presented as current?temporal
    Expected answer
    • assessment validity period
    • staleness threshold
    • re-assessment trigger
Artifacts
  • Condition or inspection reportDated report recording condition grade, defects, method, assessor and supporting imagery for this individual item.
authenticityAuthenticity and verification1 findings

Whether the physical thing in hand is the thing the record designates.

authenticity-verification

Authenticity verification and cloned-identifier handling

Checks that bind the physical thing to the record: mark inspection, carrier verification, tamper evidence and cryptographically verifiable credentials, plus the handling of negative results and duplicate presentations.

Questions
  1. Which verification checks were performed on this item, by whom, and with what result?validation
    Expected answer
    • check type code
    • verifier reference
    • result code
    • verification timestamp
  2. Which verifiable credentials assert facts about this item, and what is their current status?evidence
    Expected answer
    • credential identifier
    • issuer identifier
    • validFrom and validUntil
    • credentialStatus
  3. What happens when verification fails or when the same identifier is presented on two physical things?exception
    Expected answer
    • failure handling action
    • quarantine or recall state
    • notified parties
    • investigation reference
  4. What tamper-evidence exists on marks and carriers, and how is tampering recorded?security
    Expected answer
    • tamper feature description
    • tamper observation record
    • observation timestamp
Artifacts
  • Authenticity credential or certificateIssued credential or certificate asserting that the individual item is genuine, with issuer, validity window and revocation status.
whereabouts-and-controlWhereabouts and control2 layers

Where the item has been observed, what it is inside, who holds it and who owns it.

location-observationLocation observation2 findings

Dated statements of where the item was, with observation quality, and the containers or carriers it was observed within.

location-fix

Location fix and observation quality

A dated statement of the item's whereabouts resolved against a place reference, distinguishing the point of observation from the business location asserted afterwards, and carrying precision and source.

Questions
  1. Where is the item now believed to be, on the strength of which observation?spatial
    Expected answer
    • place reference
    • observation reference
    • belief timestamp
    • confidence
  2. Is a given location statement the point where the observation happened or the location the item is considered to be at afterwards?definition
    Expected answer
    • read point reference
    • business location reference
    • statement type code
  3. How was the whereabouts established: scan, sensor, sighting, declaration or inference?provenance
    Expected answer
    • observation source code
    • observing party or device reference
    • precision or accuracy
  4. How are contradictory or physically impossible location statements resolved?exception
    Expected answer
    • conflict case reference
    • precedence rule
    • rejected observation reference
Artifacts
  • Location observation logOrdered log of dated location statements about the item with source, precision and statement type, from which current whereabouts is derived.
containment-context

Containment and carrier context

What the item was inside when observed: a handling unit, a vehicle, a room or another item, and how aggregation and disaggregation change that context without changing item identity.

Questions
  1. What container, handling unit or carrier was the item inside at a given instant?relationship
    Expected answer
    • container reference
    • container type code
    • effective period
  2. Which aggregation or disaggregation events changed the item's containment, and when?event
    Expected answer
    • aggregation event reference
    • action code
    • event timestamp
  3. How deep may containment nest, and how is the outermost location derived from the innermost item?composition
    Expected answer
    • containment chain references
    • derivation rule
    • derived place reference
  4. Which model masters the container itself, so that its contents are not restated here?interoperability
    Expected answer
    • mastering model identifier
    • permitted local fields
Artifacts
  • Aggregation or disaggregation event recordRecord of the item being added to or removed from a container, carrying parent identifier, child identifiers, action and event time.
custody-and-rightsCustody, possession and rights2 findings

Who physically holds the item and under what basis, kept strictly distinct from who owns it.

custody-transfer

Custody record and transfer

Periods during which a named party held the item, the basis of holding, and the transfer events between holders, aligned with ISO 22095 custody terminology and EPCIS source/destination and shipping/receiving semantics.

Questions
  1. Who holds the item now, since when, and on what basis (ownership, lease, loan, bailment, transport)?ownership
    Expected answer
    • holder party reference
    • custody start timestamp
    • basis code
    • agreement reference
  2. Which transfer moved custody from one party to another, and was it acknowledged by both sides?process
    Expected answer
    • transfer event reference
    • source party
    • destination party
    • acknowledgement status
  3. What prevents two open custody records existing at once, and how is an overlap corrected?constraint
    Expected answer
    • single open custody rule
    • overlap detection result
    • correction record reference
  4. How are custody gaps recorded when the holder is genuinely unknown for a period?exception
    Expected answer
    • gap start and end
    • last known holder
    • gap reason code
Artifacts
  • Custody transfer receiptSigned or acknowledged record of a handover, naming source and destination parties, item identifiers, condition at handover and time.
ownership-reference

Ownership and rights reference

The reference to legal title and encumbrances held in the ownership sibling model, and the rule that possession does not imply title. CIDOC CRM distinguishes current owner (P52) from keeper (P49); ISO 55000 frames value-bearing entities as assets of an organization.

Questions
  1. Who is recorded as owner of this item, and in which model is that assertion mastered?ownership
    Expected answer
    • owner party reference
    • mastering model identifier
    • assertion timestamp
  2. When holder and owner differ, which record governs each type of decision about the item?authority
    Expected answer
    • decision type
    • governing role
    • basis reference
  3. What claims, liens, restitution claims or export restrictions limit dealings with this item?constraint
    Expected answer
    • encumbrance type
    • claiming party reference
    • jurisdiction
    • effective period
Artifacts
  • Title or rights evidence referencePointer to the document evidencing title, lien or restriction held by the ownership model, retained here only as a resolvable reference.
events-provenance-and-evidenceEvents, provenance and evidence2 layers

The event backbone that produces every other statement about the item, its time semantics, its origin story and the evidence that supports claims.

event-recordEvent record and time semantics3 findings

How events about the item are captured, corrected and ordered in time.

event-capture

Event capture and correction

The event structure that records what happened to the item, why, where and how, and the rules for idempotent capture, correction and retraction of events that must not be silently overwritten.

Questions
  1. What minimum fields must an event carry to be a valid statement about this item?requirement
    Expected answer
    • event type code
    • item identifier list
    • event time
    • business step code
    • disposition code
    • location references
  2. What business step and resulting disposition does the event assert, and from which vocabulary?classification
    Expected answer
    • business step code
    • disposition code
    • vocabulary identifier and version
  3. How is an erroneous event corrected or retracted without destroying the original assertion?exception
    Expected answer
    • correction event reference
    • superseded event identifier
    • reason code
    • corrector reference
  4. How are duplicate captures of the same real-world occurrence detected and collapsed?validation
    Expected answer
    • event identifier
    • deduplication key
    • duplicate decision record
Artifacts
  • Item event streamAppend-only stream of events concerning the item, from which current state, whereabouts and custody are derived rather than independently asserted.
time-semantics

Time semantics and ordering

The separation of when something happened from when it was recorded, the required timestamp form, and how ordering is decided when clocks disagree. RFC 3339 requires a stated offset to UTC, with 'Z' for zero offset and '-00:00' where the local offset is unknown; EPCIS carries eventTime, eventTimeZoneOffset and repository recordTime separately.

Questions
  1. For each statement, when did the fact occur and when was it observed or ingested?temporal
    Expected answer
    • event time (RFC 3339 with offset)
    • record or ingestion time (RFC 3339 with offset)
    • local time zone offset
  2. How is the order of statements decided when event times are equal, missing or inconsistent with record times?constraint
    Expected answer
    • ordering rule
    • tie-break key
    • anomaly flag
  3. How is an imprecise or historical time expressed without fabricating precision?quality
    Expected answer
    • time interval start and end
    • precision qualifier
    • estimation basis
event-dimensions

Event dimensions

EPCIS 2.0 records What, When, Where, Why and How. Event types are ObjectEvent, AggregationEvent, TransactionEvent, TransformationEvent and AssociationEvent. When includes event time and record time. Why includes bizStep, disposition and persistentDisposition. How includes sensor elements in 2.0. Instance EPCs must not be mixed up with class-level EPCs. Event hash identifiers and business-transaction hash URIs appear in CBV 2.0.

Questions
  1. What events in this item's history are known, with type, action, event time, record time, event id or hash, and which identifier of the item was observed?event
    Expected answer
    • events[] with event_type, action, event_time, record_time, event_id, event_hash, observed_identifier, biz_step, disposition.
  2. Was each event about this specific instance, a class/lot of which this instance is a member, or mixed, and is class-level inference flagged as inferred?validation
    Expected answer
    • observation_grain (instance|class|lot|inferred-from-class)
    • inference_flag
    • confidence
  3. What How-dimension sensor measurements accompanied the event, with quantity, unit, sensor id, and measurement time?measurement
    Expected answer
    • sensor_elements[] with type, value, unit, sensor_id, measurement_time
    • empty if none
Artifacts
  • Item eventOne EPCIS-aligned event about this instance, including dimensions What, When, Where, Why and How.
provenance-and-evidenceProvenance and evidence2 findings

Where the item came from, through whose hands, and what evidence supports each claim.

origin-provenance

Origin and chain of custody provenance

The origin of the individual (maker, place, date of production or first observation) and the ordered chain of custody from origin to the present, including declared gaps. PROV-O supplies generation, derivation and attribution; ISO 22095 supplies the custody model vocabulary.

Questions
  1. Who produced this individual, where and when, and how is that known?provenance
    Expected answer
    • producing party reference
    • production place reference
    • production timestamp or interval
    • evidence reference
  2. What is the ordered chain of holders from origin to now, and where are the gaps?relationship
    Expected answer
    • ordered custody references
    • gap intervals
    • chain completeness assessment
  3. Which chain-of-custody model does the chain claim to satisfy, and is that claim independently checked?validation
    Expected answer
    • custody model code
    • verification body reference
    • verification status
  4. How are contested or fabricated provenance claims flagged without deleting them?exception
    Expected answer
    • dispute record reference
    • disputing party
    • claim status code
Artifacts
  • Provenance dossierCompiled, ordered set of provenance statements and supporting documents for the individual item, including declared gaps and disputes.
attestation-evidence

Attestations, evidence quality and conflicting claims

How each claim about the item is supported, who vouches for it, how strong that support is, and what happens when two credible sources disagree.

Questions
  1. Which claim does each item of evidence support, and who issued that evidence?evidence
    Expected answer
    • supported claim reference
    • evidence artifact reference
    • issuer identifier
    • issue timestamp
  2. How is evidence strength graded, and what is the minimum grade for a claim to be published externally?quality
    Expected answer
    • evidence grade
    • grading scheme reference
    • publication threshold
  3. How is a credential's revocation, suspension or expiry reflected in claims that relied on it?validation
    Expected answer
    • credential status value
    • status checked at timestamp
    • dependent claim references
  4. When two sources make incompatible claims about the item, which prevails and on what recorded rule?decision
    Expected answer
    • conflicting claim references
    • precedence rule reference
    • resolution decision
    • decider reference
Artifacts
  • Attestation and supporting document setThe set of issuer-signed credentials, certificates, reports and images attached to claims about the item, each with issuer, validity window and status endpoint.
record-governance-and-interoperabilityRecord governance and interoperability2 layers

Who governs the item record, who may see what, how long it is kept, and how it exchanges with external standards without overclaiming conformance.

record-stewardshipRecord stewardship, access and retention3 findings

Mastership and authority over the record, scoped disclosure, and privacy and retention duties.

mastership-authority

Mastership, authority and record lifecycle

Which system and which party master this record, who may assert or change each part of it, and how record versions relate to the physical thing they describe.

Questions
  1. Which system of record masters this item record, and which fields are copies from elsewhere?authority
    Expected answer
    • mastering system reference
    • mastered field list
    • referenced field list with source model
  2. Which roles may create, amend or retire each class of statement about the item?access
    Expected answer
    • role reference
    • permitted statement classes
    • authorisation basis
  3. How is a change to the record distinguished from a change to the physical thing?definition
    Expected answer
    • record version identifier
    • record change timestamp
    • physical change event reference
  4. What retires the record itself, as opposed to ending the item's life?lifecycle
    Expected answer
    • record status code
    • retirement reason
    • approving role
Artifacts
  • Record change audit trailImmutable trail of record changes with actor, timestamp, before/after values and authorisation basis, separate from the physical event stream.
access-disclosure

Access scoping and disclosure views

Which audiences may see which parts of the record, including a public identity view that deliberately withholds whereabouts and holder, and the exceptions that override the default.

Questions
  1. What is the default visibility of each bundle and layer for a party with no explicit grant?access
    Expected answer
    • scope reference
    • default decision (deny or allow)
    • policy reference
  2. Which fields may appear in a publicly resolvable view of the item, and which must never appear?privacy
    Expected answer
    • published field list
    • prohibited field list
    • publication basis
  3. Under what exceptions may withheld data be disclosed, to whom, and with what record?exception
    Expected answer
    • exception type (legal order, theft report, safety recall, regulator request)
    • requesting party
    • disclosure record reference
    • approval reference
  4. How are access grants issued, time-boxed and revoked, and what happens to data already disclosed?security
    Expected answer
    • grant identifier
    • validity window
    • revocation event
    • post-disclosure obligations
Artifacts
  • Disclosure view definitionVersioned definition of each published projection (public identity view, custody chain view, holder inventory view) listing included and excluded fields.
privacy-retention

Privacy exposure and retention

When item data becomes personal data, and how retention duties for traceability are reconciled with data-protection limits. GDPR applies to processing of personal data about identifiable natural persons; item records routinely carry holder identity, ownership history and movement traces.

Questions
  1. Which fields link the item to an identifiable natural person, directly or by combination?privacy
    Expected answer
    • linking field list
    • identifiability assessment
    • lawful basis reference
  2. How long is each class of item data retained, on what legal or contractual basis?retention
    Expected answer
    • data class
    • retention period
    • basis reference
    • disposition action
  3. How is an erasure request reconciled with traceability, safety or product-passport duties that require retention?exception
    Expected answer
    • request reference
    • competing obligation reference
    • outcome (erase, restrict, pseudonymise, refuse)
    • decision record
  4. What correlation risk arises from a persistent, publicly resolvable item identifier, and how is it mitigated?security
    Expected answer
    • risk assessment reference
    • mitigation measures
    • residual risk statement
Artifacts
  • Retention and privacy scheduleVersioned schedule mapping each data class of the item record to a retention period, lawful basis, disposition action and privacy classification.
interoperabilityExternal alignment and exchange2 findings

How this model maps to external standards and exchanges item data without asserting unproven conformance.

vocabulary-alignment

Identifier and vocabulary alignment

Mappings from this model's terms to external vocabularies (GS1 EPCIS/CBV, GS1 Digital Link, schema.org, IEC 63278-1, CIDOC CRM, PROV-O) recorded as alignments with known conflicts, never as conformance claims.

Questions
  1. For each external standard, which of its terms does a given element of this model map to, and is the mapping exact, broader or narrower?interoperability
    Expected answer
    • external term identifier
    • local element identifier
    • mapping strength
    • standard version
  2. Where do external standards contradict one another about the same fact, and how is the contradiction recorded rather than hidden?constraint
    Expected answer
    • conflicting term pair
    • conflict description
    • local resolution rule
  3. Which version of each external vocabulary is the mapping valid against, and how is drift detected?provenance
    Expected answer
    • standard version or date
    • mapping validated at timestamp
    • re-validation trigger
  4. What evidence would be required before claiming conformance to a given external standard?validation
    Expected answer
    • conformance criteria reference
    • test evidence reference
    • current claim status
Artifacts
  • External alignment mapVersioned table mapping model elements to external standard terms with strength, standard version, validation date and recorded conflicts.
exchange-projection

Exchange projections and external obligations

The outbound payloads built from this model (visibility events, product-passport content, credential presentations) and the obligations that attach when data is published to an external regime.

Questions
  1. Which outbound projection is required for a given consumer, and which fields does it draw from?interoperability
    Expected answer
    • projection identifier
    • consumer or regime reference
    • source field list
  2. Does an external payload bind to the item instance, to a batch or to the model, and is that level stated explicitly?identity
    Expected answer
    • binding level code
    • bound identifier
    • level assertion basis
  3. What accuracy, availability and update duties attach once data is published to an external regime, and who is responsible?requirement
    Expected answer
    • regime reference
    • responsible operator reference
    • availability duty
    • update trigger
  4. How is divergence detected between a published projection and the current internal record?quality
    Expected answer
    • published snapshot reference
    • comparison timestamp
    • divergence finding
    • remediation action
Artifacts
  • Published payload snapshotImmutable snapshot of what was published externally (visibility event batch, passport payload, credential presentation) with time, recipient and integrity digest.

Publication holds

  • Source verification hold: every accepted source URL, organisation, version pin and access date must be re-fetched and confirmed live before publication, including the two providers' divergent GS1 endpoints (ref.gs1.org/epcis/ versus ref.gs1.org/standards/epcis/ and /standards/cbv/) and the two IEC 61406-1 webstore URLs.
  • Multi-profile validation hold: the merged structure has not been exercised against distinct domain profiles - serialised industrial equipment, consumer trade items, cultural and museum objects, unmarked natural specimens, and logistics handling-unit contexts - so profile-specific mandatory elements may still be missing.
  • Paywalled clause text hold: ISO 55000:2024, ISO 55001:2024, ISO 22095:2020 and ISO/IEC 15459-4 were grounded from catalogue and overview metadata only in both runs; clause-level obligations on asset lifecycle, chain-of-custody models and unique item identifiers remain unverified.
  • ESPR/DPP grain hold: both providers failed to render the EUR-Lex text of Regulation (EU) 2024/1781, so whether the unique product identifier binds at model, batch or item level, and the registry and data-carrier duties, rest on secondary summaries and must not be published as article-level facts.
  • EPCIS and CBV normative text hold: the base grounded EPCIS/CBV fields from the GS1 linked-data reference corroborated by a tier-3 implementation site; CBV vocabulary claims carried by the accepted event-dimensions finding must be reconciled against the ratified EPCIS 2.0 and CBV 2.0 standards before publication.
  • Local-policy labelling hold: identifier precedence across GS1, ISO/IEC 15459, IEC 61406 and AAS namespaces, and the identity-continuity rule across component replacement and rebuild, are unresolved by every consulted source and must be published as explicitly local decisions rather than standards-backed facts.

Deferred research

  • Sector-specific instance identification regimes omitted by both providers - ISO 3779 VIN, medical device UDI, IMEI, aerospace and defence item unique identification, and firearms marking - which may impose mandatory identity elements on the instance-identification layer.
  • ISO/IEC 15459 series clause text and GS1 General Specifications 8.0.0 provisions on issuing agencies, non-reuse periods and identifier retirement, to decide whether identifier issuance and post-disposal embargo deserves its own finding beside master-identifier.
  • EPCIS TransformationEvent and PROV wasDerivedFrom grounding for the base identity-continuity finding, plus CBV completeness_verified versus completeness_inferred for containment-context, as evidence enrichment rather than new nodes.
  • ICOM Object ID descriptive categories (title, subject, date or period, maker) and museum condition-report taxonomies, to test whether cultural descriptive identity is a distinct facet of the observed-properties layer or remains covered by measured-attributes and origin-provenance.
  • Darwin Core and biological collecting-event practice for natural specimens taken into tracking, since natural-object admission currently rests only on a broad CIDOC E18 alignment.
  • Automatic data capture standards (RFID air interfaces, 2D symbol quality grading) and metrology vocabulary for measurement uncertainty, both unconsulted in either run.
  • Deaccession, forfeiture, salvage and waste-shipment regimes (including Basel Convention) that govern the accepted exceptional-states and end-of-life findings in jurisdictions beyond the EU assumptions already recorded.