Published

Fulfilment / Delivery

vr.wm-eco-024 · wm-eco-024-fulfilment-delivery

Represent how an external order or obligation is fulfilled by goods, services, digital content or access so agents can distinguish promise, allocation, preparation, dispatch, handover, receipt, inspection, acceptance, exception and completion without confusing fulfilment with shipment, inventory, invoice, payment, return or refund.

World Models Society, people and institutions SOC.ECO.FUL

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Identity, obligation, order and parties Groups fulfilment context for identity, obligation, order and parties.

Fulfilment root identity, version, profile and state

Groups source-qualified fulfilment context for fulfilment root identity, version, profile and state.

Fulfilment ID, version head, profile, status and master system

Records fulfilment id, version head, profile, status and master system as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish fulfilment id, version head, profile, status and master system? identity
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on fulfilment id, version head, profile, status and master system, for which purpose and under what authority? provenance
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify fulfilment id, version head, profile, status and master system? quality

Goods, service, digital, access, pickup, installation, partial, staged, recurring and third-party profile

Records goods, service, digital, access, pickup, installation, partial, staged, recurring and third-party profile as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish goods, service, digital, access, pickup, installation, partial, staged, recurring and third-party profile? classification
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on goods, service, digital, access, pickup, installation, partial, staged, recurring and third-party profile, for which purpose and under what authority? ownership
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify goods, service, digital, access, pickup, installation, partial, staged, recurring and third-party profile? validation

Order obligation, parties, roles and authority

Groups source-qualified fulfilment context for order obligation, parties, roles and authority.

Order, contract, line, obligation, commitment, term and discharge binding

Records order, contract, line, obligation, commitment, term and discharge binding as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish order, contract, line, obligation, commitment, term and discharge binding? relationship
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on order, contract, line, obligation, commitment, term and discharge binding, for which purpose and under what authority? authority
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify order, contract, line, obligation, commitment, term and discharge binding? security

Buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier and authority role

Records buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier and authority role as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier and authority role? ownership
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier and authority role, for which purpose and under what authority? requirement
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier and authority role? privacy

Promised subject, composition, quantity and condition Groups fulfilment context for promised subject, composition, quantity and condition.

Item, service, resource, digital content and substitution

Groups source-qualified fulfilment context for item, service, resource, digital content and substitution.

Product, service, resource, content, entitlement, specification, lot, serial and version reference

Records product, service, resource, content, entitlement, specification, lot, serial and version reference as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish product, service, resource, content, entitlement, specification, lot, serial and version reference? relationship
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on product, service, resource, content, entitlement, specification, lot, serial and version reference, for which purpose and under what authority? constraint
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify product, service, resource, content, entitlement, specification, lot, serial and version reference? retention

Substitution, equivalence, variant, tolerance, quality, condition and acceptability

Records substitution, equivalence, variant, tolerance, quality, condition and acceptability as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish substitution, equivalence, variant, tolerance, quality, condition and acceptability? constraint
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on substitution, equivalence, variant, tolerance, quality, condition and acceptability, for which purpose and under what authority? process
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify substitution, equivalence, variant, tolerance, quality, condition and acceptability? access

Fulfilment units, lines, batches, packages and quantities

Groups source-qualified fulfilment context for fulfilment units, lines, batches, packages and quantities.

Fulfilment unit, line, split, batch, stage, handling unit, package, consignment and dependency

Records fulfilment unit, line, split, batch, stage, handling unit, package, consignment and dependency as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish fulfilment unit, line, split, batch, stage, handling unit, package, consignment and dependency? composition
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on fulfilment unit, line, split, batch, stage, handling unit, package, consignment and dependency, for which purpose and under what authority? event
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify fulfilment unit, line, split, batch, stage, handling unit, package, consignment and dependency? exception

Ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantity

Records ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantity as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantity? measurement
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantity, for which purpose and under what authority? measurement
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantity? interoperability

Planning, allocation, readiness, preparation and dispatch Groups fulfilment context for planning, allocation, readiness, preparation and dispatch.

Plan, allocation, backorder, readiness, pick, pack and activation

Groups source-qualified fulfilment context for plan, allocation, backorder, readiness, pick, pack and activation.

Plan, schedule, capacity, allocation, reservation, backorder, priority and dependency

Records plan, schedule, capacity, allocation, reservation, backorder, priority and dependency as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish plan, schedule, capacity, allocation, reservation, backorder, priority and dependency? process
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on plan, schedule, capacity, allocation, reservation, backorder, priority and dependency, for which purpose and under what authority? evidence
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify plan, schedule, capacity, allocation, reservation, backorder, priority and dependency? decision

Ready, pick, pack, stage, configure, provision, activate, verify and release for dispatch

Records ready, pick, pack, stage, configure, provision, activate, verify and release for dispatch as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish ready, pick, pack, stage, configure, provision, activate, verify and release for dispatch? state
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on ready, pick, pack, stage, configure, provision, activate, verify and release for dispatch, for which purpose and under what authority? quality
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify ready, pick, pack, stage, configure, provision, activate, verify and release for dispatch? identity

Dispatch, despatch advice, custody and transport binding

Groups source-qualified fulfilment context for dispatch, despatch advice, custody and transport binding.

Dispatch instruction, advice, event, item, package, quantity, origin, destination and notice

Records dispatch instruction, advice, event, item, package, quantity, origin, destination and notice as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish dispatch instruction, advice, event, item, package, quantity, origin, destination and notice? event
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on dispatch instruction, advice, event, item, package, quantity, origin, destination and notice, for which purpose and under what authority? validation
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify dispatch instruction, advice, event, item, package, quantity, origin, destination and notice? classification

Shipment, consignment, carrier, transport leg, tracking, custody, risk and handover reference

Records shipment, consignment, carrier, transport leg, tracking, custody, risk and handover reference as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish shipment, consignment, carrier, transport leg, tracking, custody, risk and handover reference? relationship
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on shipment, consignment, carrier, transport leg, tracking, custody, risk and handover reference, for which purpose and under what authority? security
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify shipment, consignment, carrier, transport leg, tracking, custody, risk and handover reference? composition

Delivery, handover, receipt, inspection and acceptance Groups fulfilment context for delivery, handover, receipt, inspection and acceptance.

Attempt, arrival, location, channel, handover and proof

Groups source-qualified fulfilment context for attempt, arrival, location, channel, handover and proof.

Delivery attempt, arrival, availability, pickup, activation, endpoint, recipient and location

Records delivery attempt, arrival, availability, pickup, activation, endpoint, recipient and location as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish delivery attempt, arrival, availability, pickup, activation, endpoint, recipient and location? spatial
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on delivery attempt, arrival, availability, pickup, activation, endpoint, recipient and location, for which purpose and under what authority? privacy
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify delivery attempt, arrival, availability, pickup, activation, endpoint, recipient and location? relationship

Handover, custody transfer, signature, photo, code, device, witness and proof

Records handover, custody transfer, signature, photo, code, device, witness and proof as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish handover, custody transfer, signature, photo, code, device, witness and proof? evidence
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on handover, custody transfer, signature, photo, code, device, witness and proof, for which purpose and under what authority? retention
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify handover, custody transfer, signature, photo, code, device, witness and proof? state

Receipt, examination, inspection, acceptance and rejection

Groups source-qualified fulfilment context for receipt, examination, inspection, acceptance and rejection.

Receipt advice, recipient, quantity, package, condition, time, place and source

Records receipt advice, recipient, quantity, package, condition, time, place and source as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish receipt advice, recipient, quantity, package, condition, time, place and source? event
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on receipt advice, recipient, quantity, package, condition, time, place and source, for which purpose and under what authority? access
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify receipt advice, recipient, quantity, package, condition, time, place and source? lifecycle

Examination, inspection, test, conformity, acceptance, rejection, reservation and reason

Records examination, inspection, test, conformity, acceptance, rejection, reservation and reason as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish examination, inspection, test, conformity, acceptance, rejection, reservation and reason? validation
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on examination, inspection, test, conformity, acceptance, rejection, reservation and reason, for which purpose and under what authority? exception
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify examination, inspection, test, conformity, acceptance, rejection, reservation and reason? temporal

Exceptions, remedies, reconciliation and completion Groups fulfilment context for exceptions, remedies, reconciliation and completion.

Shortage, excess, damage, loss, delay, failure and recovery

Groups source-qualified fulfilment context for shortage, excess, damage, loss, delay, failure and recovery.

Shortage, excess, damage, loss, delay, wrong item, condition, temperature and discrepancy

Records shortage, excess, damage, loss, delay, wrong item, condition, temperature and discrepancy as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish shortage, excess, damage, loss, delay, wrong item, condition, temperature and discrepancy? quality
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on shortage, excess, damage, loss, delay, wrong item, condition, temperature and discrepancy, for which purpose and under what authority? interoperability
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify shortage, excess, damage, loss, delay, wrong item, condition, temperature and discrepancy? spatial

Failed attempt, hold, reroute, retry, redelivery, replacement, repair, cancellation and escalation

Records failed attempt, hold, reroute, retry, redelivery, replacement, repair, cancellation and escalation as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish failed attempt, hold, reroute, retry, redelivery, replacement, repair, cancellation and escalation? exception
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on failed attempt, hold, reroute, retry, redelivery, replacement, repair, cancellation and escalation, for which purpose and under what authority? decision
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify failed attempt, hold, reroute, retry, redelivery, replacement, repair, cancellation and escalation? provenance

Reconciliation, acceptance, remedy, completion and discharge

Groups source-qualified fulfilment context for reconciliation, acceptance, remedy, completion and discharge.

Order, dispatch, receipt, invoice, quantity, condition, status and evidence reconciliation

Records order, dispatch, receipt, invoice, quantity, condition, status and evidence reconciliation as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish order, dispatch, receipt, invoice, quantity, condition, status and evidence reconciliation? validation
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on order, dispatch, receipt, invoice, quantity, condition, status and evidence reconciliation, for which purpose and under what authority? identity
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify order, dispatch, receipt, invoice, quantity, condition, status and evidence reconciliation? ownership

Accepted, partial, rejected, remedied, completed, disputed, obligation discharge, return and compensation reference

Records accepted, partial, rejected, remedied, completed, disputed, obligation discharge, return and compensation reference as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish accepted, partial, rejected, remedied, completed, disputed, obligation discharge, return and compensation reference? lifecycle
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on accepted, partial, rejected, remedied, completed, disputed, obligation discharge, return and compensation reference, for which purpose and under what authority? classification
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify accepted, partial, rejected, remedied, completed, disputed, obligation discharge, return and compensation reference? authority

Governance, provenance, time, access and interoperability Groups fulfilment context for governance, provenance, time, access and interoperability.

Source, provenance, access, privacy, retention and correction

Groups source-qualified fulfilment context for source, provenance, access, privacy, retention and correction.

Owner, steward, source system, actor, activity, derivation, revision, conflict and audit

Records owner, steward, source system, actor, activity, derivation, revision, conflict and audit as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish owner, steward, source system, actor, activity, derivation, revision, conflict and audit? provenance
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on owner, steward, source system, actor, activity, derivation, revision, conflict and audit, for which purpose and under what authority? composition
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify owner, steward, source system, actor, activity, derivation, revision, conflict and audit? requirement

Purpose, address, recipient, access, confidentiality, disclosure, retention, legal hold, correction and tombstone

Records purpose, address, recipient, access, confidentiality, disclosure, retention, legal hold, correction and tombstone as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish purpose, address, recipient, access, confidentiality, disclosure, retention, legal hold, correction and tombstone? privacy
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on purpose, address, recipient, access, confidentiality, disclosure, retention, legal hold, correction and tombstone, for which purpose and under what authority? relationship
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify purpose, address, recipient, access, confidentiality, disclosure, retention, legal hold, correction and tombstone? constraint

Event clocks, validation and loss-aware projections

Groups source-qualified fulfilment context for event clocks, validation and loss-aware projections.

Requested, promised, ready, dispatched, arrived, attempted, handed over, received, inspected, accepted, completed, observed and known time

Records requested, promised, ready, dispatched, arrived, attempted, handed over, received, inspected, accepted, completed, observed and known time as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish requested, promised, ready, dispatched, arrived, attempted, handed over, received, inspected, accepted, completed, observed and known time? temporal
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on requested, promised, ready, dispatched, arrived, attempted, handed over, received, inspected, accepted, completed, observed and known time, for which purpose and under what authority? state
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify requested, promised, ready, dispatched, arrived, attempted, handed over, received, inspected, accepted, completed, observed and known time? process

Identity, quantity, state, sequence, condition, term, policy, privacy, UBL, EDIFACT, EPCIS, Schema.org, TMF, PROV and API validation

Records identity, quantity, state, sequence, condition, term, policy, privacy, ubl, edifact, epcis, schema.org, tmf, prov and api validation as source-qualified fulfilment context while order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain independently identifiable.

What stable fulfilment, version, obligation, unit, item, party and external-master identities plus explicit profile and unknown state establish identity, quantity, state, sequence, condition, term, policy, privacy, ubl, edifact, epcis, schema.org, tmf, prov and api validation? interoperability
Who promises, supplies, prepares, dispatches, carries, hands over, receives, inspects, accepts, corrects or may rely on identity, quantity, state, sequence, condition, term, policy, privacy, ubl, edifact, epcis, schema.org, tmf, prov and api validation, for which purpose and under what authority? lifecycle
Which requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times, sources and evidence qualify identity, quantity, state, sequence, condition, term, policy, privacy, ubl, edifact, epcis, schema.org, tmf, prov and api validation? event

Classifiers Filled

Family: World Models
Category: Society, people and institutions
Entry kind: aggregate
Navigation path: NAV.SOC.ECO.FUL
Domain: SOC.ECO.FUL
Industry: Cross-industry
Tags: fulfilmentdeliverysoc.eco.ful

What it is Filled

Owns fulfilment identity, versions, profiles and state; order, contract, line and obligation bindings; party roles and authority; promised product, service, resource, digital content, entitlement, specification, lot and serial references; fulfilment units, splits, batches, stages, packages and dependencies; ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantities; substitution, tolerance, quality and condition assertions; plan, allocation, backorder, readiness, preparation, dispatch or activation evidence; shipment, consignment, carrier, transport and custody references; delivery attempts, handover proof, receipt, examination, inspection, conformity, acceptance and rejection evidence; shortages, excess, damage, loss, delay, failure, recovery, remedies, reconciliation, completion and discharge assertions; distinct clocks, provenance, privacy, retention, validation and loss-aware projections. External order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records masters remain authoritative.

In scope

Fulfilment identity, versions, obligation and party bindings, promised subjects, units, composition, quantities, conditions, allocation, readiness and dispatch or activation evidence
Handover, receipt, inspection, acceptance, exceptions, remedies, reconciliation, completion, clocks, provenance, access, retention and projections

Out of scope

Owning Purchase Order, Contract, Party, Product, Service, Inventory, Warehouse, Shipment, Consignment, Package, Route, Location, Digital Artifact, Entitlement, Appointment, Work Order, Invoice, Payment, Return, Refund, Support or Records masters
Treating dispatched, delivered, received, accepted or completed status as universal proof of intended-recipient receipt, conformity, payment, discharge, risk transfer or dispute closure
Autonomous order acceptance, inventory allocation, dispatch, service activation, receipt signature, acceptance, discharge, invoicing, payment, return, refund, disclosure or physical disposition

Why it exists Filled

Distinguishing features Filled

How an order or obligation is fulfilled, not the order itself.
Covers goods, services, digital content and access.
Differs from a shipment, which is a transport movement.
Keeps dispatch, handover, receipt, inspection and acceptance separate.

What robots and AI may and may not do Filled

Must not

Accept obligations or allocate inventory without delegation.
Sign receipt or accept conformity.
Discharge an obligation.
Invoice on delivery status alone.
Mark delivered without evidence.

Only with a human decision

Accepting or rejecting deliveries.
Resolving disputes over delivery.
Discharging obligations.

May

Plan and track fulfilment units and stages.
Record dispatch and handover events from sources.
Flag exceptions and delays.
Reconcile fulfilment with orders and invoices.

Moral aspects Filled

Failed delivery of essential goods or services harms people who depend on them.
Delivery addresses and recipient data are personal.
Courier and warehouse workers face time pressure from tracking metrics.

Who is affected

Recipients and buyers
Suppliers
Delivery and warehouse workers

Owners Filled

Steward

Dimension owner, namespace authority, accountable fulfilment owner and delegated commercial, logistics, service, inspection and legal authorities

Roles

Fulfilment owner: Own purpose, scope, profile, lifecycle, compatibility and accountable use.
Order and commercial steward: Own obligation, terms, tolerance, substitution and contract or order bindings.
Inventory and preparation steward: Own allocation, backorder, readiness, pick, pack and inventory-source bindings.
Logistics or service steward: Own dispatch, shipment, activation, handover and service-execution bindings.
Recipient and inspection authority: Own receipt, examination, conformity, acceptance, rejection and discrepancy decisions.
Privacy, safety and legal authority: Own protected delivery data, risk, remedies, access, jurisdiction and retention limitations.
Interoperability and records steward: Own mappings, conformance evidence, declared loss, legal hold and disposition policy.

Links to other meta-models Filled

references

WM-ECO-019 - Resolve the candidate containing purchase-order obligation without granting cascade mutation authority.
WM-FLW-011 - Resolve candidate shipment and transport execution without duplicating its lifecycle.
WM-ECO-008 - Resolve candidate invoice evidence without owning billing or settlement.
Party, Product, Service, Inventory, Warehouse, Shipment, Consignment, Package, Location, Digital Artifact, Entitlement, Work Order, Payment, Return, Refund, Support and Records models - Resolve external identities, states, operations and evidence without duplicating their masters.

aligned

UBL 2.3; UN/EDIFACT DESADV, RECADV and INSDES; EPCIS and CBV 2.0; CISG; EU consumer and sales profiles; Schema.org; TM Forum; RFC 3339; PROV-O; DQV; ODRL; OpenAPI 3.1.1 - Project version-pinned logistics, traceability, legal, discovery, service, temporal, provenance, quality, policy and API views with declared loss.

neighbor

WM-ECO-019 Purchase Order - The candidate ledger says the order contains fulfilment obligations. The order owns the exchanged commitment; this model owns obligation-performance and evidence context and does not mutate the order.
WM-FLW-011 Shipment - The candidate reference points to physical transport execution. Shipment, consignment, package, carrier, route and tracking remain external while fulfilment binds dispatch and delivery evidence.
WM-ECO-008 Invoice - The candidate reference connects delivered or accepted quantities to billing evidence. Fulfilment never issues or settles invoices.
Inventory, service execution, entitlement, return and refund - These systems own allocation, actual service or access, reverse logistics and financial remedy lifecycles; fulfilment records typed references and effect observations.
UBL, UN/EDIFACT, EPCIS, CISG, EU law, Schema.org, TM Forum, RFC, PROV, DQV, ODRL and OpenAPI - Each representation has a distinct scope; every mapping is version-pinned, profile-qualified and loss-declaring.

parent

WM-ECO-019

What else AI and robots need to interact with it Filled

Sources Filled

Universal Business Language Version 2.3 - OASIS Open
UN/EDIFACT Despatch advice message - United Nations Economic Commission for Europe
UN/EDIFACT Receiving advice message - United Nations Economic Commission for Europe
UN/EDIFACT Instruction to despatch message - United Nations Economic Commission for Europe
EPCIS Standard 2.0.1 - GS1
Core Business Vocabulary 2.0 - GS1
International Sale of Goods CISG and related transactions - United Nations Commission on International Trade Law
Directive 2011/83/EU on consumer rights - European Union
Directive EU 2019/771 on contracts for the sale of goods - European Union
ParcelDelivery - Schema.org Community Group
DeliveryEvent - Schema.org Community Group
Service Ordering Management API TMF641 - TM Forum
Open API Directory - TM Forum
Date and Time on the Internet: Timestamps - Internet Engineering Task Force
PROV-O: The PROV Ontology - World Wide Web Consortium
Data on the Web Best Practices: Data Quality Vocabulary - World Wide Web Consortium
ODRL Information Model 2.2 - World Wide Web Consortium
OpenAPI Specification 3.1.1 - OpenAPI Initiative

Open questions

Canonically adjudicate the WM-ECO-019 containment and WM-FLW-011 and WM-ECO-008 reference edges and register remaining neighbor relations.
Create goods, services, digital delivery, utilities, healthcare, food, hazardous-material, installation and regulated-sector profiles.
Conformance-test dispatch, receipt, inspection, quantity, condition, exception, completion and projection mappings against concrete implementations.
Validate organization-specific allocation, substitution, delivery, acceptance, safety, privacy, retention and emergency-access policies.
Obtain authorized legal, consumer, logistics, safety, customs and financial review before jurisdiction-specific claims.
Obtain independent external research review before promotion beyond reviewable-draft assurance.
Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.
The candidate WM-ECO-019 containment and WM-FLW-011 and WM-ECO-008 reference relations are not canonically approved.
Goods, services, digital delivery, utilities, healthcare, food, hazardous materials, installation and regulated sectors need separate profiles.
Incoterms, national contract, consumer, product-safety, tax, customs, privacy, signature and records rules require licensed or jurisdiction-specific review.
UBL, UN/EDIFACT, EPCIS, Schema.org and TM Forum projections do not universally prove physical delivery, legal acceptance or obligation discharge.

Machine files

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

Provenance

world-models research · reviewable-draft

Built from: models/wm-eco-024-fulfilment-delivery/spec.yaml, ver-cy/world-models/card-supplements/wm-eco-024-fulfilment-delivery.json