← Back to catalogue
Published

Supply-chain Trace / Chain of Custody

vr.wm-flw-013 · wm-flw-013-supply-chain-trace-chain-of-custody

Provide a reusable governed pattern for linking traceable objects, events, custody assertions, transformations, locations, parties and evidence into a federated time-aware trace graph with qualified queries, gaps and corrections.

World Models Physical world and living systems PHY.FLW.LOG
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Trace identity, scope and semantic kind Groups the governed Route / Itinerary concern for trace identity, scope and semantic kind.

Trace identity, revision and result kind

Groups Route / Itinerary context for trace identity, revision and result kind without importing neighboring master lifecycles.

Trace graph scope, identifier, namespace and revision

Records trace graph scope, identifier, namespace and revision as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish trace graph scope, identifier, namespace and revision? identity
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on trace graph scope, identifier, namespace and revision, and under which authority? provenance
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify trace graph scope, identifier, namespace and revision? quality

Persistent graph, query request, result, snapshot and claim kind

Records persistent graph, query request, result, snapshot and claim kind as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish persistent graph, query request, result, snapshot and claim kind? classification
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on persistent graph, query request, result, snapshot and claim kind, and under which authority? ownership
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify persistent graph, query request, result, snapshot and claim kind? validation

Coverage objective, profile and system boundary

Groups Route / Itinerary context for coverage objective, profile and system boundary without importing neighboring master lifecycles.

Traceability objective, subject range, depth and direction

Records traceability objective, subject range, depth and direction as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish traceability objective, subject range, depth and direction? requirement
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on traceability objective, subject range, depth and direction, and under which authority? authority
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify traceability objective, subject range, depth and direction? security

Physical segregation, controlled blending, mass balance and book-and-claim profile

Records physical segregation, controlled blending, mass balance and book-and-claim profile as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish physical segregation, controlled blending, mass balance and book-and-claim profile? classification
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on physical segregation, controlled blending, mass balance and book-and-claim profile, and under which authority? requirement
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify physical segregation, controlled blending, mass balance and book-and-claim profile? privacy
Traceable-object, event and composition graph Groups the governed Route / Itinerary concern for traceable-object, event and composition graph.

Object identity, class and membership

Groups Route / Itinerary context for object identity, class and membership without importing neighboring master lifecycles.

Product, material, lot, serial, item, handling-unit, shipment and asset reference

Records product, material, lot, serial, item, handling-unit, shipment and asset reference as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish product, material, lot, serial, item, handling-unit, shipment and asset reference? relationship
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on product, material, lot, serial, item, handling-unit, shipment and asset reference, and under which authority? constraint
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify product, material, lot, serial, item, handling-unit, shipment and asset reference? retention

Aggregation, disaggregation, containment and membership interval

Records aggregation, disaggregation, containment and membership interval as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish aggregation, disaggregation, containment and membership interval? composition
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on aggregation, disaggregation, containment and membership interval, and under which authority? process
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify aggregation, disaggregation, containment and membership interval? access

Critical event, transformation and causality

Groups Route / Itinerary context for critical event, transformation and causality without importing neighboring master lifecycles.

Commission, observe, pack, ship, receive, store, use, return and dispose event

Records commission, observe, pack, ship, receive, store, use, return and dispose event as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish commission, observe, pack, ship, receive, store, use, return and dispose event? event
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on commission, observe, pack, ship, receive, store, use, return and dispose event, and under which authority? event
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify commission, observe, pack, ship, receive, store, use, return and dispose event? exception

Transformation input, output, process step, causality and yield

Records transformation input, output, process step, causality and yield as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish transformation input, output, process step, causality and yield? process
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on transformation input, output, process step, causality and yield, and under which authority? measurement
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify transformation input, output, process step, causality and yield? interoperability
Location, party and custody chain Groups the governed Route / Itinerary concern for location, party and custody chain.

Read point, business location, source and destination

Groups Route / Itinerary context for read point, business location, source and destination without importing neighboring master lifecycles.

Event read point, business location, jurisdiction and facility

Records event read point, business location, jurisdiction and facility as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish event read point, business location, jurisdiction and facility? spatial
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on event read point, business location, jurisdiction and facility, and under which authority? evidence
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify event read point, business location, jurisdiction and facility? decision

Source, destination, business step, disposition and movement reference

Records source, destination, business step, disposition and movement reference as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish source, destination, business step, disposition and movement reference? relationship
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on source, destination, business step, disposition and movement reference, and under which authority? quality
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify source, destination, business step, disposition and movement reference? identity

Party role, custody and handover

Groups Route / Itinerary context for party role, custody and handover without importing neighboring master lifecycles.

Owner, custodian, possessor, controller, responsible party and steward

Records owner, custodian, possessor, controller, responsible party and steward as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish owner, custodian, possessor, controller, responsible party and steward? ownership
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on owner, custodian, possessor, controller, responsible party and steward, and under which authority? validation
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify owner, custodian, possessor, controller, responsible party and steward? classification

Custody interval, transfer, handover, acceptance, refusal and exception

Records custody interval, transfer, handover, acceptance, refusal and exception as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish custody interval, transfer, handover, acceptance, refusal and exception? lifecycle
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on custody interval, transfer, handover, acceptance, refusal and exception, and under which authority? security
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify custody interval, transfer, handover, acceptance, refusal and exception? composition
Time, evidence, integrity and correction Groups the governed Route / Itinerary concern for time, evidence, integrity and correction.

Clocks, source, provenance and attribution

Groups Route / Itinerary context for clocks, source, provenance and attribution without importing neighboring master lifecycles.

Event, effective, observation, record, ingestion and publication time

Records event, effective, observation, record, ingestion and publication time as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish event, effective, observation, record, ingestion and publication time? temporal
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on event, effective, observation, record, ingestion and publication time, and under which authority? privacy
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify event, effective, observation, record, ingestion and publication time? relationship

Asserting agent, source system, method, authority and delegation

Records asserting agent, source system, method, authority and delegation as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish asserting agent, source system, method, authority and delegation? provenance
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on asserting agent, source system, method, authority and delegation, and under which authority? retention
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify asserting agent, source system, method, authority and delegation? state

Evidence, proof, quality, conflict and correction

Groups Route / Itinerary context for evidence, proof, quality, conflict and correction without importing neighboring master lifecycles.

Evidence artifact, digest, signature, credential and verification result

Records evidence artifact, digest, signature, credential and verification result as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish evidence artifact, digest, signature, credential and verification result? evidence
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on evidence artifact, digest, signature, credential and verification result, and under which authority? access
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify evidence artifact, digest, signature, credential and verification result? lifecycle

Completeness, confidence, gap, duplicate, conflict, error declaration and successor

Records completeness, confidence, gap, duplicate, conflict, error declaration and successor as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish completeness, confidence, gap, duplicate, conflict, error declaration and successor? quality
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on completeness, confidence, gap, duplicate, conflict, error declaration and successor, and under which authority? exception
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify completeness, confidence, gap, duplicate, conflict, error declaration and successor? temporal
Trace query, exposure, recall and federation Groups the governed Route / Itinerary concern for trace query, exposure, recall and federation.

Backward, forward, history and path query

Groups Route / Itinerary context for backward, forward, history and path query without importing neighboring master lifecycles.

One-up one-down, backward, forward and end-to-end trace

Records one-up one-down, backward, forward and end-to-end trace as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish one-up one-down, backward, forward and end-to-end trace? process
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on one-up one-down, backward, forward and end-to-end trace, and under which authority? interoperability
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify one-up one-down, backward, forward and end-to-end trace? spatial

Object, event, party, location, time and relationship filter

Records object, event, party, location, time and relationship filter as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish object, event, party, location, time and relationship filter? constraint
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on object, event, party, location, time and relationship filter, and under which authority? decision
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify object, event, party, location, time and relationship filter? provenance

Exposure, recall, impact and qualified result

Groups Route / Itinerary context for exposure, recall, impact and qualified result without importing neighboring master lifecycles.

Affected lot, item, party, location, shipment and downstream set

Records affected lot, item, party, location, shipment and downstream set as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish affected lot, item, party, location, shipment and downstream set? decision
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on affected lot, item, party, location, shipment and downstream set, and under which authority? identity
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify affected lot, item, party, location, shipment and downstream set? ownership

Recall, investigation, alert, status, action reference and residual uncertainty

Records recall, investigation, alert, status, action reference and residual uncertainty as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish recall, investigation, alert, status, action reference and residual uncertainty? exception
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on recall, investigation, alert, status, action reference and residual uncertainty, and under which authority? classification
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify recall, investigation, alert, status, action reference and residual uncertainty? authority
Governance, access, retention and interoperability Groups the governed Route / Itinerary concern for governance, access, retention and interoperability.

Federation, discovery, access, privacy and retention

Groups Route / Itinerary context for federation, discovery, access, privacy and retention without importing neighboring master lifecycles.

Registry, endpoint, query routing, availability and freshness

Records registry, endpoint, query routing, availability and freshness as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish registry, endpoint, query routing, availability and freshness? interoperability
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on registry, endpoint, query routing, availability and freshness, and under which authority? composition
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify registry, endpoint, query routing, availability and freshness? requirement

Purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold

Records purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold? access
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold, and under which authority? relationship
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold? constraint

Standards crosswalk, conformance and loss

Groups Route / Itinerary context for standards crosswalk, conformance and loss without importing neighboring master lifecycles.

GS1, UN/CEFACT, ISO, FDA, EU, DCSA, IATA and provenance crosswalk

Records gs1, un/cefact, iso, fda, eu, dcsa, iata and provenance crosswalk as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish gs1, un/cefact, iso, fda, eu, dcsa, iata and provenance crosswalk? interoperability
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on gs1, un/cefact, iso, fda, eu, dcsa, iata and provenance crosswalk, and under which authority? state
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify gs1, un/cefact, iso, fda, eu, dcsa, iata and provenance crosswalk? process

Profile, version, license, conformance, transformation and semantic loss

Records profile, version, license, conformance, transformation and semantic loss as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.

  1. Which trace identity, result kind, object and event scope, graph edge, clocks and source establish profile, version, license, conformance, transformation and semantic loss? validation
  2. Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on profile, version, license, conformance, transformation and semantic loss, and under which authority? lifecycle
  3. Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify profile, version, license, conformance, transformation and semantic loss? event

Classifiers Filled

Family
World Models
Category
Physical world and living systems
Entry kind
pattern
Navigation path
NAV.PHY.FLW.LOG
Domain
PHY.FLW.LOG
Industry
Cross-industry
Tags
supplychaintracecustodyphy.flw.log

What it is Filled

Owns trace scope, semantic kind and graph revision; trace objective, range, direction and chain-of-custody profile; typed bindings to objects, events, parties, places, movements and evidence; aggregation, transformation and custody edges; qualified clocks, sources, proof and quality; gaps, duplicates, conflicts, error declarations and successors; backward, forward, path and exposure query results; federation, access, retention and loss-aware projections. Products, lots, serials, handling units, shipments, inventory movements, journeys, locations, parties, generic events, observations, custody handovers, documents, credentials, incidents, recall actions, claims and evidence masters remain external.

In scope

  • Trace scope, graph and result identity, objective, range, direction, semantic kind, revision and successor lineage
  • Typed object-event graph, aggregation, transformation, location, party, custody, clock, source, evidence, proof, quality, gap and conflict assertions
  • Backward and forward query, exposure analysis, federation, privacy, access, retention, audit and interoperability

Out of scope

  • Owning product, lot, serial, handling unit, shipment, movement, journey, place, party, event, observation, handover, document, credential, incident, recall action, claim or evidence lifecycles
  • Equating traceability with tracking, custody with ownership, aggregation with transformation, event assertion with verified fact, physical flow with mass balance or book-and-claim, or exposure result with recall decision
  • Executing physical custody, product certification, identity issuance, evidence storage, recall, enforcement, protected disclosure or irreversible deletion

Why it exists Filled

Provide a reusable governed pattern for linking traceable objects, events, custody assertions, transformations, locations, parties and evidence into a federated time-aware trace graph with qualified queries, gaps and corrections.

Distinguishing features Filled

  • Assembles a graph of events, objects and custody edges, not the events themselves.
  • Traceability is not tracking; tracking follows current location only.
  • Custody is not ownership.
  • Mass balance, segregation and identity preservation are distinct models.

What robots and AI may and may not do Filled

Must not

  • Certify products or sustainability claims.
  • Order or scope a recall.
  • Infer custody from location alone.
  • Disclose supplier data beyond purpose.

Only with a human decision

  • Deciding the scope of a recall or enforcement action.
  • Certifying a product claim or accepting custody.

May

  • Append source-qualified events and edges.
  • Trace backward and forward.
  • Report gaps and contradictions in the trace.
  • Compute exposure sets for review.

Moral aspects Filled

  • Traceability protects consumers in food and medicine safety.
  • Supply chain transparency can reveal forced labour or deforestation.
  • Supplier data may expose small producers to commercial risk.

Who is affected

  • Consumers
  • Producers and suppliers
  • Workers in the supply chain
  • Regulators

Owners Filled

Steward

Declare the Dimension owner, trace steward, source authorities, custodians, verifiers, query operators and accountable decision roles.

Roles

Dimension owner
Own namespace, mastership, delegation, access, retention and federation rules.
Traceability steward
Own trace scope, graph semantics, chain-of-custody profiles, quality and correction policy.
Source-system authority
Own object, event, clock, location and business assertions within its system boundary.
Custodian or operator
Assert custody, possession, handling and handover evidence within delegated scope.
Evidence issuer or verifier
Own artifacts, digests, proof methods, verification results and limitations.
Query or investigation operator
Run authorized backward, forward, path and exposure analyses with declared rules.
Recall or regulatory authority
Own recall, enforcement, certification or regulatory decisions outside the trace pattern.
Disclosure reviewer
Review recipient, purpose, minimum disclosure, redaction and publication timing.

Links to other meta-models Filled

references

  • WM-FLW-004 Goods Movement / Logistics - Resolve broader logistics flow while the candidate parent relation remains under joint boundary review.
  • WM-FLW-011 Shipment / Consignment and WM-FLW-012 Inventory Movement - Resolve logistics groupings and stock-affecting transitions while trace owns only cross-source graph linkage.
  • Product, lot, serial, handling-unit, place and party masters - Resolve traceable objects and participants while preserving external identity and lifecycle authority.
  • Custody handover, document, credential, claim, recall and evidence masters - Resolve supporting records and accountable decisions without converting them into trace-owned payloads.

composes

  • WM-ACT-015 Occurrence / Event - Compose typed event references into the trace graph without importing generic event identity or lifecycle.

aligned

  • GS1 EPCIS 2.0.1, CBV 2.0.0 and Global Traceability 2.0 - Project critical events, objects, aggregation, transformation, locations, business context, queries and error declarations.
  • UN/CEFACT Integrated Track and Trace - Project cross-industry multimodal visibility and delegated event-registry views.
  • ISO 22095, ISO 22095-2, ISO 22005 and ISO 28000 - Project generic custody models, mass-balance attribution, food traceability and security management as pinned profiles.
  • FDA Food Traceability Rule and EU Digital Product Passport - Project jurisdiction-specific trace records, lots, critical events, product identifiers, access and retention duties.
  • DCSA Track and Trace and IATA ONE Record - Project container-shipping and air-cargo event and federation views as modal profiles.
  • RFC 3339, RFC 8785, PROV-O, DQV, ODRL and Data Integrity - Project temporal, canonicalization, provenance, quality, access and proof semantics with exact pins and loss declarations.

neighbor

  • WM-FLW-004 Goods Movement / Logistics - Goods Movement owns physical logistics flow. Trace / Chain of Custody links source-qualified histories across movements and organizations; the candidate parent signal remains under review.
  • WM-ACT-015 Occurrence / Event - The trace pattern composes typed event references and graph edges. Generic event identity, occurrence semantics and lifecycle remain external; the candidate COMPOSE relation is accepted only in that limited sense.
  • WM-FLW-011 Shipment / Consignment - Shipment / Consignment owns commercial or transport grouping and status assertions. The trace graph references it as an object and event context without importing that lifecycle.
  • WM-FLW-012 Inventory Movement - Inventory Movement owns one stock-affecting transition and external posting reference. The trace graph links movements across organizations but does not calculate stock positions or post ledgers.
  • Custody handover and ownership - The pattern links custody intervals, transfers, acceptance and refusal assertions. The handover event and legal ownership remain independently mastered and must not be inferred from location alone.
  • Evidence, credential and certification - Artifacts, digests, signatures, credentials and verification results are references that support assertions. Their issuance, storage, cryptographic validity, certification scope and legal effect remain external.
  • Recall, investigation and enforcement - The pattern may derive a qualified affected set with gaps and uncertainty. Accountable domain authorities own recall, alert, enforcement, remedy and public-disclosure decisions.

parent

  • WM-FLW-004

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Authoritative traceability master-system identifier and immutable revision.
  • Governed globally resolvable trace, edge, query-result or exposure-set IRI.
  • Adopting-Dimension UUID or ULID when no authoritative external identifier exists.

Direct properties not applicable Not applicable

Not applicable

A custody chain is a record of transfers; the traced goods carry the physical properties.

Recognition required Filled

  • A trace has objects, events, parties, places and custody edges with times.
  • Often confused with tracking, a shipment and a certificate.

Capabilities and actions required Filled

  • Register trace scope: Create one governed trace-graph or result identity with an explicit semantic kind and objective.
  • Bind traceable objects: Bind product, material, lot, serial, item, handling-unit, shipment and asset identities without importing their lifecycles.
  • Append critical event: Link an externally mastered event with business, spatial, temporal, party and evidence context.
  • Link composition or transformation: Append aggregation, disaggregation or input-output transformation edges with validity and yield context.
  • Record custody assertion: Append custody, possession, control, responsibility or handover assertions without inferring ownership.
  • Attach evidence and proof: Bind evidence artifacts, digests, signatures, credentials, verification results and quality statements.
  • Correct or contest trace assertion: Append error declaration, retraction, competing assertion or successor without deleting the original.
  • Trace backward or forward: Return a qualified graph slice across object, event, party, location and time filters.
  • Compute qualified exposure set: Derive candidate affected objects, parties, locations and shipments without making a recall or enforcement decision.
  • Project authorized trace view: Produce minimum-necessary standards-aligned trace, custody, regulatory or modal views.

Hazards and failure modes required Filled

  • Recall scope too narrow or too wide.
  • Fraudulent provenance claims.
  • Gaps hiding illegal sourcing.
  • Disclosure of commercial data.

Standards and interfaces required Filled

  • GS1 EPCIS 2.0 and CBV.
  • GS1 Global Traceability Standard.
  • ISO 22095 chain of custody.
  • W3C PROV-O.

Context of use required Filled

  • FDA food traceability and EU Digital Product Passport are jurisdictional and product-scope profiles rather than universal supply-chain rules.
  • DCSA and IATA are maritime-container and air-cargo modal profiles and do not define all transport or custody contexts.
  • Recall, certification, title, custody, privacy, security, retention and evidential consequences depend on sector, contract and jurisdiction.

Sources Filled

  1. EPCIS Standard - GS1
  2. Core Business Vocabulary Standard - GS1
  3. GS1 Global Traceability Standard - GS1
  4. EPCIS ObjectEvent linked-data definition - GS1
  5. EPCIS AggregationEvent linked-data definition - GS1
  6. EPCIS TransformationEvent linked-data definition - GS1
  7. Integrated Track and Trace for Multi-Modal Transportation BRS - UN/CEFACT
  8. White Paper on Integrated Track and Trace for Multimodal Transportation - UN/CEFACT
  9. Visibility and Collaborative Planning in Multimodal Supply Chain Operations BRS - UN/CEFACT
  10. ISO 22095:2020 Chain of custody - International Organization for Standardization
  11. ISO 22095-2:2026 Chain of custody mass balance - International Organization for Standardization
  12. ISO 22005:2007 Feed and food traceability - International Organization for Standardization
  13. ISO 28000:2022 Security and resilience - International Organization for Standardization
  14. FSMA Food Traceability Final Rule - United States Food and Drug Administration
  15. Regulation EU 2024/1781 Ecodesign for Sustainable Products - European Union
  16. Track and Trace Standard Documentation - Digital Container Shipping Association
  17. ONE Record - International Air Transport Association
  18. ONE Record Ontology - International Air Transport Association
  19. RFC 3339 Date and Time on the Internet - Internet Engineering Task Force
  20. RFC 8785 JSON Canonicalization Scheme - Internet Engineering Task Force
  21. PROV-O: The PROV Ontology - World Wide Web Consortium
  22. Data Quality Vocabulary - World Wide Web Consortium
  23. ODRL Information Model 2.2 - World Wide Web Consortium
  24. Verifiable Credential Data Integrity 1.0 - World Wide Web Consortium

Open questions

  • Sector, jurisdiction, chain-of-custody claim, certification, customs, dangerous-goods, safety, privacy, security, licensing and retention profiles require exact current rules and competent review.
  • Objects, events, movements, parties, places, handovers, observations, documents, credentials, claims, recall actions and evidence lifecycles remain in neighboring models.
  • Certified field crosswalks, identity resolution, graph completeness metrics, secure federation, signature suites, exposure algorithms, recall decision rules and legal evidence requirements remain future work.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-flw-013-supply-chain-trace-chain-of-custody/spec.yaml, ver-cy/world-models/card-supplements/wm-flw-013-supply-chain-trace-chain-of-custody.json