# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T15:27:06Z", "synthesisSha256": "2754f2dc2b7a9de1a3cd2099e568f5455368895452ac03e682f01e81ad45752b", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ECO-024", "registryId": "vr.wm-eco-024", "name": "Fulfilment / Delivery", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ECO.FUL" ], "tags": [ "fulfilment", "delivery", "soc.eco.ful" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-eco-024-fulfilment-delivery/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-eco-024", "model": { "registry_id": "vr.wm-eco-024", "model_id": "WM-ECO-024", "name": "Fulfilment / Delivery", "entry_kind": "aggregate", "purpose": "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.", "scope_statement": "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" ], "boundary_notes": [ { "neighbor": "WM-ECO-019 Purchase Order", "distinction": "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "neighbor": "WM-FLW-011 Shipment", "distinction": "The candidate reference points to physical transport execution. Shipment, consignment, package, carrier, route and tracking remain external while fulfilment binds dispatch and delivery evidence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-010", "SRC-013" ] }, { "neighbor": "WM-ECO-008 Invoice", "distinction": "The candidate reference connects delivered or accepted quantities to billing evidence. Fulfilment never issues or settles invoices.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "neighbor": "Inventory, service execution, entitlement, return and refund", "distinction": "These systems own allocation, actual service or access, reverse logistics and financial remedy lifecycles; fulfilment records typed references and effect observations.", "source_refs": [ "SRC-004", "SRC-005", "SRC-009", "SRC-012", "SRC-013", "SRC-017" ] }, { "neighbor": "UBL, UN/EDIFACT, EPCIS, CISG, EU law, Schema.org, TM Forum, RFC, PROV, DQV, ODRL and OpenAPI", "distinction": "Each representation has a distinct scope; every mapping is version-pinned, profile-qualified and loss-declaring.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Universal Business Language Version 2.3", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/UBL-2.3.html", "version_or_date": "OASIS Standard 15 June 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines order fulfilment, Despatch Advice, Receipt Advice, Fulfilment Cancellation, items, handling units, quantities, shortages, rejection and document references." }, { "id": "SRC-002", "title": "UN/EDIFACT Despatch advice message", "organization": "United Nations Economic Commission for Europe", "url": "https://service.unece.org/trade/untdid/d99a/trmd/desadv_d.htm", "version_or_date": "UN/EDIFACT D.99A DESADV", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines goods despatched or ready for despatch, consignment contents, parties, destinations, transport details, terms and invoice matching." }, { "id": "SRC-003", "title": "UN/EDIFACT Receiving advice message", "organization": "United Nations Economic Commission for Europe", "url": "https://service.unece.org/trade/untdid/d96b/trmd/recadv_d.htm", "version_or_date": "UN/EDIFACT D.96B RECADV", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines physical receipt and discrepancies in products, quantities, terms, packages and documentary requirements." }, { "id": "SRC-004", "title": "UN/EDIFACT Instruction to despatch message", "organization": "United Nations Economic Commission for Europe", "url": "https://service.unece.org/trade/untdid/d20a/trmd/insdes_c.htm", "version_or_date": "UN/EDIFACT D.20A INSDES", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines instructions to release or hold previously ordered goods, delivery location, delivery date and third-party service-provider context without changing the order." }, { "id": "SRC-005", "title": "EPCIS Standard 2.0.1", "organization": "GS1", "url": "https://ref.gs1.org/standards/epcis/2.0.1/", "version_or_date": "Release 2.0.1, ratified 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines interoperable event capture and query for object, aggregation, transaction, transformation and association observations with event time, record time, location, business step and source-destination context." }, { "id": "SRC-006", "title": "Core Business Vocabulary 2.0", "organization": "GS1", "url": "https://ref.gs1.org/standards/cbv/2.0.0/", "version_or_date": "Release 2.0, ratified 2022", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines controlled business steps, dispositions, source and destination types and error reasons for EPCIS event semantics such as shipping and receiving." }, { "id": "SRC-007", "title": "International Sale of Goods CISG and related transactions", "organization": "United Nations Commission on International Trade Law", "url": "https://uncitral.un.org/en/texts/salegoods", "version_or_date": "CISG adopted 11 April 1980; status and text accessed 6 September 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines seller delivery, document handover, conformity, buyer examination and taking delivery plus remedies and risk rules within its scope." }, { "id": "SRC-008", "title": "Directive 2011/83/EU on consumer rights", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32011L0083", "version_or_date": "Official consolidated context current at access", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines consumer delivery, performance, passing of risk, additional payments, withdrawal and reimbursement rules in scope." }, { "id": "SRC-009", "title": "Directive EU 2019/771 on contracts for the sale of goods", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/dir/2019/771/oj", "version_or_date": "Directive 20 May 2019; national transposition remains profile-specific", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines delivery and conformity duties, remedies, repair, replacement, price reduction and termination for consumer goods in scope." }, { "id": "SRC-010", "title": "ParcelDelivery", "organization": "Schema.org Community Group", "url": "https://schema.org/ParcelDelivery", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines public parcel-delivery discovery with order, carrier, tracking, origin, destination, expected arrival, events and item-shipped references." }, { "id": "SRC-011", "title": "DeliveryEvent", "organization": "Schema.org Community Group", "url": "https://schema.org/DeliveryEvent", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines an item-delivery event including delivery method, availability interval and access code." }, { "id": "SRC-012", "title": "Service Ordering Management API TMF641", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis/service-ordering-management-api-TMF641/v4.1", "version_or_date": "TMF641 v4.1 directory entry, stable update 15 May 2026", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines service-order creation, update, retrieval and notifications, useful for service-fulfilment bindings while service execution remains external." }, { "id": "SRC-013", "title": "Open API Directory", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis", "version_or_date": "Directory accessed 6 September 2026", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Registers shipment, tracking, resource, service activation, inventory, ordering, billing and payment API boundaries." }, { "id": "SRC-014", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339 July 2002, updated by RFC 9557", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines interoperable timestamps with seconds and explicit UTC relationship." }, { "id": "SRC-015", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines entities, activities, agents, attribution, generation, derivation, revision and qualified provenance." }, { "id": "SRC-016", "title": "Data on the Web Best Practices: Data Quality Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "W3C Working Group Note 15 December 2016", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines quality dimensions, metrics, measurements, annotations, policies and certificates." }, { "id": "SRC-017", "title": "ODRL Information Model 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "W3C Recommendation 15 February 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines permissions, prohibitions, duties, constraints, assets and parties for digital-delivery and access-policy projections." }, { "id": "SRC-018", "title": "OpenAPI Specification 3.1.1", "organization": "OpenAPI Initiative", "url": "https://spec.openapis.org/oas/v3.1.1.html", "version_or_date": "Version 3.1.1, 24 October 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:24:00Z", "relevance": "Defines HTTP API operations, schemas, responses, security and reusable components for fulfilment service projections." } ], "structure": { "bundles": [ { "id": "identity-obligation-order-and-parties", "name": "Identity, obligation, order and parties", "description": "Groups fulfilment context for identity, obligation, order and parties.", "rationale": "Identify one fulfilment aggregate and its promised obligation without remastering the order or parties", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-015" ], "layers": [ { "id": "fulfilment-root-identity-version-profile-and-state", "name": "Fulfilment root identity, version, profile and state", "description": "Groups source-qualified fulfilment context for fulfilment root identity, version, profile and state.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-015" ], "findings": [ { "id": "fulfilment-id-version-head-profile-status-and-master-system", "name": "Fulfilment ID, version head, profile, status and master system", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-015" ], "questions": [ { "id": "fulfilment-id-version-head-profile-status-and-master-system-q01", "text": "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?", "kind": "identity", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "fulfilment-id-version-head-profile-status-and-master-system-q02", "text": "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?", "kind": "provenance", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "fulfilment-id-version-head-profile-status-and-master-system-q03", "text": "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?", "kind": "quality", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "fulfilment-id-version-head-profile-status-and-master-system-data", "name": "Fulfilment ID, version head, profile, status and master system data", "description": "Typed fulfilment data for fulfilment id, version head, profile, status and master system, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-015" ] } ], "artifacts": [ { "id": "fulfilment-id-version-head-profile-status-and-master-system-record", "name": "Fulfilment ID, version head, profile, status and master system record", "description": "Immutable or successor-versioned fulfilment evidence for fulfilment id, version head, profile, status and master system.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for fulfilment-id-version-head-profile-status-and-master-system; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "goods-service-digital-access-pickup-installation-partial-staged-recurring-and-thirdparty-profile", "name": "Goods, service, digital, access, pickup, installation, partial, staged, recurring and third-party profile", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-015" ], "questions": [ { "id": "goods-service-digital-access-pickup-installation-partial-staged-recurring-and-thirdparty-profile-q01", "text": "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?", "kind": "classification", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "goods-service-digital-access-pickup-installation-partial-staged-recurring-and-thirdparty-profile-q02", "text": "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?", "kind": "ownership", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "goods-service-digital-access-pickup-installation-partial-staged-recurring-and-thirdparty-profile-q03", "text": "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?", "kind": "validation", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "goods-service-digital-access-pickup-installation-partial-staged-recurring-and-thirdparty-profile-data", "name": "Goods, service, digital, access, pickup, installation, partial, staged, recurring and third-party profile data", "description": "Typed fulfilment data for goods, service, digital, access, pickup, installation, partial, staged, recurring and third-party profile, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-015" ] } ], "artifacts": [ { "id": "goods-service-digital-access-pickup-installation-partial-staged-recurring-and-thirdparty-profile-record", "name": "Goods, service, digital, access, pickup, installation, partial, staged, recurring and third-party profile record", "description": "Immutable or successor-versioned fulfilment evidence for goods, service, digital, access, pickup, installation, partial, staged, recurring and third-party profile.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for goods-service-digital-access-pickup-installation-partial-staged-recurring-and-thirdparty-profile; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "order-obligation-parties-roles-and-authority", "name": "Order obligation, parties, roles and authority", "description": "Groups source-qualified fulfilment context for order obligation, parties, roles and authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-015" ], "findings": [ { "id": "order-contract-line-obligation-commitment-term-and-discharge-binding", "name": "Order, contract, line, obligation, commitment, term and discharge binding", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-015" ], "questions": [ { "id": "order-contract-line-obligation-commitment-term-and-discharge-binding-q01", "text": "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?", "kind": "relationship", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "order-contract-line-obligation-commitment-term-and-discharge-binding-q02", "text": "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?", "kind": "authority", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "order-contract-line-obligation-commitment-term-and-discharge-binding-q03", "text": "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?", "kind": "security", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "order-contract-line-obligation-commitment-term-and-discharge-binding-data", "name": "Order, contract, line, obligation, commitment, term and discharge binding data", "description": "Typed fulfilment data for order, contract, line, obligation, commitment, term and discharge binding, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-015" ] } ], "artifacts": [ { "id": "order-contract-line-obligation-commitment-term-and-discharge-binding-record", "name": "Order, contract, line, obligation, commitment, term and discharge binding record", "description": "Immutable or successor-versioned fulfilment evidence for order, contract, line, obligation, commitment, term and discharge binding.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for order-contract-line-obligation-commitment-term-and-discharge-binding; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "buyer-seller-supplier-provider-deliveryparty-recipient-beneficiary-agent-carrier-and-authority-role", "name": "Buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier and authority role", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-015" ], "questions": [ { "id": "buyer-seller-supplier-provider-deliveryparty-recipient-beneficiary-agent-carrier-and-authority-role-q01", "text": "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?", "kind": "ownership", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "buyer-seller-supplier-provider-deliveryparty-recipient-beneficiary-agent-carrier-and-authority-role-q02", "text": "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?", "kind": "requirement", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "buyer-seller-supplier-provider-deliveryparty-recipient-beneficiary-agent-carrier-and-authority-role-q03", "text": "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?", "kind": "privacy", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "buyer-seller-supplier-provider-deliveryparty-recipient-beneficiary-agent-carrier-and-authority-role-data", "name": "Buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier and authority role data", "description": "Typed fulfilment data for buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier and authority role, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-015" ] } ], "artifacts": [ { "id": "buyer-seller-supplier-provider-deliveryparty-recipient-beneficiary-agent-carrier-and-authority-role-record", "name": "Buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier and authority role record", "description": "Immutable or successor-versioned fulfilment evidence for buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier and authority role.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for buyer-seller-supplier-provider-deliveryparty-recipient-beneficiary-agent-carrier-and-authority-role; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "promised-subject-composition-quantity-and-condition", "name": "Promised subject, composition, quantity and condition", "description": "Groups fulfilment context for promised subject, composition, quantity and condition.", "rationale": "Represent what is promised and how it is grouped while item, inventory and package masters stay external", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-017" ], "layers": [ { "id": "item-service-resource-digital-content-and-substitution", "name": "Item, service, resource, digital content and substitution", "description": "Groups source-qualified fulfilment context for item, service, resource, digital content and substitution.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007", "SRC-009", "SRC-017" ], "findings": [ { "id": "product-service-resource-content-entitlement-specification-lot-serial-and-version-reference", "name": "Product, service, resource, content, entitlement, specification, lot, serial and version reference", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007", "SRC-009", "SRC-017" ], "questions": [ { "id": "product-service-resource-content-entitlement-specification-lot-serial-and-version-reference-q01", "text": "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?", "kind": "relationship", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "product-service-resource-content-entitlement-specification-lot-serial-and-version-reference-q02", "text": "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?", "kind": "constraint", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "product-service-resource-content-entitlement-specification-lot-serial-and-version-reference-q03", "text": "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?", "kind": "retention", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "product-service-resource-content-entitlement-specification-lot-serial-and-version-reference-data", "name": "Product, service, resource, content, entitlement, specification, lot, serial and version reference data", "description": "Typed fulfilment data for product, service, resource, content, entitlement, specification, lot, serial and version reference, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007", "SRC-009", "SRC-017" ] } ], "artifacts": [ { "id": "product-service-resource-content-entitlement-specification-lot-serial-and-version-reference-record", "name": "Product, service, resource, content, entitlement, specification, lot, serial and version reference record", "description": "Immutable or successor-versioned fulfilment evidence for product, service, resource, content, entitlement, specification, lot, serial and version reference.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for product-service-resource-content-entitlement-specification-lot-serial-and-version-reference; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007", "SRC-009", "SRC-017" ] } ], "inline_only_rationale": null }, { "id": "substitution-equivalence-variant-tolerance-quality-condition-and-acceptability", "name": "Substitution, equivalence, variant, tolerance, quality, condition and acceptability", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007", "SRC-009", "SRC-017" ], "questions": [ { "id": "substitution-equivalence-variant-tolerance-quality-condition-and-acceptability-q01", "text": "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?", "kind": "constraint", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "substitution-equivalence-variant-tolerance-quality-condition-and-acceptability-q02", "text": "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?", "kind": "process", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "substitution-equivalence-variant-tolerance-quality-condition-and-acceptability-q03", "text": "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?", "kind": "access", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "substitution-equivalence-variant-tolerance-quality-condition-and-acceptability-data", "name": "Substitution, equivalence, variant, tolerance, quality, condition and acceptability data", "description": "Typed fulfilment data for substitution, equivalence, variant, tolerance, quality, condition and acceptability, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007", "SRC-009", "SRC-017" ] } ], "artifacts": [ { "id": "substitution-equivalence-variant-tolerance-quality-condition-and-acceptability-record", "name": "Substitution, equivalence, variant, tolerance, quality, condition and acceptability record", "description": "Immutable or successor-versioned fulfilment evidence for substitution, equivalence, variant, tolerance, quality, condition and acceptability.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for substitution-equivalence-variant-tolerance-quality-condition-and-acceptability; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007", "SRC-009", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "id": "fulfilment-units-lines-batches-packages-and-quantities", "name": "Fulfilment units, lines, batches, packages and quantities", "description": "Groups source-qualified fulfilment context for fulfilment units, lines, batches, packages and quantities.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "fulfilment-unit-line-split-batch-stage-handlingunit-package-consignment-and-dependency", "name": "Fulfilment unit, line, split, batch, stage, handling unit, package, consignment and dependency", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "fulfilment-unit-line-split-batch-stage-handlingunit-package-consignment-and-dependency-q01", "text": "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?", "kind": "composition", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "fulfilment-unit-line-split-batch-stage-handlingunit-package-consignment-and-dependency-q02", "text": "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?", "kind": "event", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "fulfilment-unit-line-split-batch-stage-handlingunit-package-consignment-and-dependency-q03", "text": "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?", "kind": "exception", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "fulfilment-unit-line-split-batch-stage-handlingunit-package-consignment-and-dependency-data", "name": "Fulfilment unit, line, split, batch, stage, handling unit, package, consignment and dependency data", "description": "Typed fulfilment data for fulfilment unit, line, split, batch, stage, handling unit, package, consignment and dependency, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "fulfilment-unit-line-split-batch-stage-handlingunit-package-consignment-and-dependency-record", "name": "Fulfilment unit, line, split, batch, stage, handling unit, package, consignment and dependency record", "description": "Immutable or successor-versioned fulfilment evidence for fulfilment unit, line, split, batch, stage, handling unit, package, consignment and dependency.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for fulfilment-unit-line-split-batch-stage-handlingunit-package-consignment-and-dependency; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "ordered-promised-allocated-prepared-dispatched-delivered-received-accepted-rejected-and-outstanding-quantity", "name": "Ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantity", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "ordered-promised-allocated-prepared-dispatched-delivered-received-accepted-rejected-and-outstanding-quantity-q01", "text": "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?", "kind": "measurement", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "ordered-promised-allocated-prepared-dispatched-delivered-received-accepted-rejected-and-outstanding-quantity-q02", "text": "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?", "kind": "measurement", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "ordered-promised-allocated-prepared-dispatched-delivered-received-accepted-rejected-and-outstanding-quantity-q03", "text": "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?", "kind": "interoperability", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "ordered-promised-allocated-prepared-dispatched-delivered-received-accepted-rejected-and-outstanding-quantity-data", "name": "Ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantity data", "description": "Typed fulfilment data for ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantity, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "ordered-promised-allocated-prepared-dispatched-delivered-received-accepted-rejected-and-outstanding-quantity-record", "name": "Ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantity record", "description": "Immutable or successor-versioned fulfilment evidence for ordered, promised, allocated, prepared, dispatched, delivered, received, accepted, rejected and outstanding quantity.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for ordered-promised-allocated-prepared-dispatched-delivered-received-accepted-rejected-and-outstanding-quantity; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "planning-allocation-readiness-preparation-and-dispatch", "name": "Planning, allocation, readiness, preparation and dispatch", "description": "Groups fulfilment context for planning, allocation, readiness, preparation and dispatch.", "rationale": "Record fulfilment preparation and dispatch evidence without owning warehouse, inventory, carrier or service execution", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-012", "SRC-013" ], "layers": [ { "id": "plan-allocation-backorder-readiness-pick-pack-and-activation", "name": "Plan, allocation, backorder, readiness, pick, pack and activation", "description": "Groups source-qualified fulfilment context for plan, allocation, backorder, readiness, pick, pack and activation.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ], "findings": [ { "id": "plan-schedule-capacity-allocation-reservation-backorder-priority-and-dependency", "name": "Plan, schedule, capacity, allocation, reservation, backorder, priority and dependency", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ], "questions": [ { "id": "plan-schedule-capacity-allocation-reservation-backorder-priority-and-dependency-q01", "text": "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?", "kind": "process", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "plan-schedule-capacity-allocation-reservation-backorder-priority-and-dependency-q02", "text": "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?", "kind": "evidence", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "plan-schedule-capacity-allocation-reservation-backorder-priority-and-dependency-q03", "text": "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?", "kind": "decision", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "plan-schedule-capacity-allocation-reservation-backorder-priority-and-dependency-data", "name": "Plan, schedule, capacity, allocation, reservation, backorder, priority and dependency data", "description": "Typed fulfilment data for plan, schedule, capacity, allocation, reservation, backorder, priority and dependency, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "plan-schedule-capacity-allocation-reservation-backorder-priority-and-dependency-record", "name": "Plan, schedule, capacity, allocation, reservation, backorder, priority and dependency record", "description": "Immutable or successor-versioned fulfilment evidence for plan, schedule, capacity, allocation, reservation, backorder, priority and dependency.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for plan-schedule-capacity-allocation-reservation-backorder-priority-and-dependency; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "ready-pick-pack-stage-configure-provision-activate-verify-and-release-for-dispatch", "name": "Ready, pick, pack, stage, configure, provision, activate, verify and release for dispatch", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ], "questions": [ { "id": "ready-pick-pack-stage-configure-provision-activate-verify-and-release-for-dispatch-q01", "text": "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?", "kind": "state", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "ready-pick-pack-stage-configure-provision-activate-verify-and-release-for-dispatch-q02", "text": "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?", "kind": "quality", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "ready-pick-pack-stage-configure-provision-activate-verify-and-release-for-dispatch-q03", "text": "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?", "kind": "identity", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "ready-pick-pack-stage-configure-provision-activate-verify-and-release-for-dispatch-data", "name": "Ready, pick, pack, stage, configure, provision, activate, verify and release for dispatch data", "description": "Typed fulfilment data for ready, pick, pack, stage, configure, provision, activate, verify and release for dispatch, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "ready-pick-pack-stage-configure-provision-activate-verify-and-release-for-dispatch-record", "name": "Ready, pick, pack, stage, configure, provision, activate, verify and release for dispatch record", "description": "Immutable or successor-versioned fulfilment evidence for ready, pick, pack, stage, configure, provision, activate, verify and release for dispatch.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for ready-pick-pack-stage-configure-provision-activate-verify-and-release-for-dispatch; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "dispatch-despatch-advice-custody-and-transport-binding", "name": "Dispatch, despatch advice, custody and transport binding", "description": "Groups source-qualified fulfilment context for dispatch, despatch advice, custody and transport binding.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-013" ], "findings": [ { "id": "dispatch-instruction-advice-event-item-package-quantity-origin-destination-and-notice", "name": "Dispatch instruction, advice, event, item, package, quantity, origin, destination and notice", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-013" ], "questions": [ { "id": "dispatch-instruction-advice-event-item-package-quantity-origin-destination-and-notice-q01", "text": "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?", "kind": "event", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "dispatch-instruction-advice-event-item-package-quantity-origin-destination-and-notice-q02", "text": "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?", "kind": "validation", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "dispatch-instruction-advice-event-item-package-quantity-origin-destination-and-notice-q03", "text": "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?", "kind": "classification", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "dispatch-instruction-advice-event-item-package-quantity-origin-destination-and-notice-data", "name": "Dispatch instruction, advice, event, item, package, quantity, origin, destination and notice data", "description": "Typed fulfilment data for dispatch instruction, advice, event, item, package, quantity, origin, destination and notice, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-013" ] } ], "artifacts": [ { "id": "dispatch-instruction-advice-event-item-package-quantity-origin-destination-and-notice-record", "name": "Dispatch instruction, advice, event, item, package, quantity, origin, destination and notice record", "description": "Immutable or successor-versioned fulfilment evidence for dispatch instruction, advice, event, item, package, quantity, origin, destination and notice.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for dispatch-instruction-advice-event-item-package-quantity-origin-destination-and-notice; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "shipment-consignment-carrier-transport-leg-tracking-custody-risk-and-handover-reference", "name": "Shipment, consignment, carrier, transport leg, tracking, custody, risk and handover reference", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-013" ], "questions": [ { "id": "shipment-consignment-carrier-transport-leg-tracking-custody-risk-and-handover-reference-q01", "text": "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?", "kind": "relationship", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "shipment-consignment-carrier-transport-leg-tracking-custody-risk-and-handover-reference-q02", "text": "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?", "kind": "security", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "shipment-consignment-carrier-transport-leg-tracking-custody-risk-and-handover-reference-q03", "text": "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?", "kind": "composition", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "shipment-consignment-carrier-transport-leg-tracking-custody-risk-and-handover-reference-data", "name": "Shipment, consignment, carrier, transport leg, tracking, custody, risk and handover reference data", "description": "Typed fulfilment data for shipment, consignment, carrier, transport leg, tracking, custody, risk and handover reference, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-013" ] } ], "artifacts": [ { "id": "shipment-consignment-carrier-transport-leg-tracking-custody-risk-and-handover-reference-record", "name": "Shipment, consignment, carrier, transport leg, tracking, custody, risk and handover reference record", "description": "Immutable or successor-versioned fulfilment evidence for shipment, consignment, carrier, transport leg, tracking, custody, risk and handover reference.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for shipment-consignment-carrier-transport-leg-tracking-custody-risk-and-handover-reference; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "delivery-handover-receipt-inspection-and-acceptance", "name": "Delivery, handover, receipt, inspection and acceptance", "description": "Groups fulfilment context for delivery, handover, receipt, inspection and acceptance.", "rationale": "Separate delivery claims from recipient receipt, inspection, acceptance and service outcome", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-015", "SRC-016" ], "layers": [ { "id": "attempt-arrival-location-channel-handover-and-proof", "name": "Attempt, arrival, location, channel, handover and proof", "description": "Groups source-qualified fulfilment context for attempt, arrival, location, channel, handover and proof.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011" ], "findings": [ { "id": "delivery-attempt-arrival-availability-pickup-activation-endpoint-recipient-and-location", "name": "Delivery attempt, arrival, availability, pickup, activation, endpoint, recipient and location", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011" ], "questions": [ { "id": "delivery-attempt-arrival-availability-pickup-activation-endpoint-recipient-and-location-q01", "text": "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?", "kind": "spatial", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "delivery-attempt-arrival-availability-pickup-activation-endpoint-recipient-and-location-q02", "text": "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?", "kind": "privacy", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "delivery-attempt-arrival-availability-pickup-activation-endpoint-recipient-and-location-q03", "text": "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?", "kind": "relationship", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "delivery-attempt-arrival-availability-pickup-activation-endpoint-recipient-and-location-data", "name": "Delivery attempt, arrival, availability, pickup, activation, endpoint, recipient and location data", "description": "Typed fulfilment data for delivery attempt, arrival, availability, pickup, activation, endpoint, recipient and location, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "delivery-attempt-arrival-availability-pickup-activation-endpoint-recipient-and-location-record", "name": "Delivery attempt, arrival, availability, pickup, activation, endpoint, recipient and location record", "description": "Immutable or successor-versioned fulfilment evidence for delivery attempt, arrival, availability, pickup, activation, endpoint, recipient and location.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for delivery-attempt-arrival-availability-pickup-activation-endpoint-recipient-and-location; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "handover-custody-transfer-signature-photo-code-device-witness-and-proof", "name": "Handover, custody transfer, signature, photo, code, device, witness and proof", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011" ], "questions": [ { "id": "handover-custody-transfer-signature-photo-code-device-witness-and-proof-q01", "text": "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?", "kind": "evidence", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "handover-custody-transfer-signature-photo-code-device-witness-and-proof-q02", "text": "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?", "kind": "retention", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "handover-custody-transfer-signature-photo-code-device-witness-and-proof-q03", "text": "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?", "kind": "state", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "handover-custody-transfer-signature-photo-code-device-witness-and-proof-data", "name": "Handover, custody transfer, signature, photo, code, device, witness and proof data", "description": "Typed fulfilment data for handover, custody transfer, signature, photo, code, device, witness and proof, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "handover-custody-transfer-signature-photo-code-device-witness-and-proof-record", "name": "Handover, custody transfer, signature, photo, code, device, witness and proof record", "description": "Immutable or successor-versioned fulfilment evidence for handover, custody transfer, signature, photo, code, device, witness and proof.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for handover-custody-transfer-signature-photo-code-device-witness-and-proof; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "receipt-examination-inspection-acceptance-and-rejection", "name": "Receipt, examination, inspection, acceptance and rejection", "description": "Groups source-qualified fulfilment context for receipt, examination, inspection, acceptance and rejection.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "findings": [ { "id": "receipt-advice-recipient-quantity-package-condition-time-place-and-source", "name": "Receipt advice, recipient, quantity, package, condition, time, place and source", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "questions": [ { "id": "receipt-advice-recipient-quantity-package-condition-time-place-and-source-q01", "text": "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?", "kind": "event", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "receipt-advice-recipient-quantity-package-condition-time-place-and-source-q02", "text": "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?", "kind": "access", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "receipt-advice-recipient-quantity-package-condition-time-place-and-source-q03", "text": "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?", "kind": "lifecycle", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "receipt-advice-recipient-quantity-package-condition-time-place-and-source-data", "name": "Receipt advice, recipient, quantity, package, condition, time, place and source data", "description": "Typed fulfilment data for receipt advice, recipient, quantity, package, condition, time, place and source, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "receipt-advice-recipient-quantity-package-condition-time-place-and-source-record", "name": "Receipt advice, recipient, quantity, package, condition, time, place and source record", "description": "Immutable or successor-versioned fulfilment evidence for receipt advice, recipient, quantity, package, condition, time, place and source.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for receipt-advice-recipient-quantity-package-condition-time-place-and-source; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "examination-inspection-test-conformity-acceptance-rejection-reservation-and-reason", "name": "Examination, inspection, test, conformity, acceptance, rejection, reservation and reason", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "questions": [ { "id": "examination-inspection-test-conformity-acceptance-rejection-reservation-and-reason-q01", "text": "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?", "kind": "validation", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "examination-inspection-test-conformity-acceptance-rejection-reservation-and-reason-q02", "text": "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?", "kind": "exception", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "examination-inspection-test-conformity-acceptance-rejection-reservation-and-reason-q03", "text": "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?", "kind": "temporal", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "examination-inspection-test-conformity-acceptance-rejection-reservation-and-reason-data", "name": "Examination, inspection, test, conformity, acceptance, rejection, reservation and reason data", "description": "Typed fulfilment data for examination, inspection, test, conformity, acceptance, rejection, reservation and reason, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "examination-inspection-test-conformity-acceptance-rejection-reservation-and-reason-record", "name": "Examination, inspection, test, conformity, acceptance, rejection, reservation and reason record", "description": "Immutable or successor-versioned fulfilment evidence for examination, inspection, test, conformity, acceptance, rejection, reservation and reason.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for examination-inspection-test-conformity-acceptance-rejection-reservation-and-reason; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "exceptions-remedies-reconciliation-and-completion", "name": "Exceptions, remedies, reconciliation and completion", "description": "Groups fulfilment context for exceptions, remedies, reconciliation and completion.", "rationale": "Preserve discrepancies, recovery and discharge decisions without absorbing return, refund, invoice or dispute masters", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "layers": [ { "id": "shortage-excess-damage-loss-delay-failure-and-recovery", "name": "Shortage, excess, damage, loss, delay, failure and recovery", "description": "Groups source-qualified fulfilment context for shortage, excess, damage, loss, delay, failure and recovery.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-016" ], "findings": [ { "id": "shortage-excess-damage-loss-delay-wrongitem-condition-temperature-and-discrepancy", "name": "Shortage, excess, damage, loss, delay, wrong item, condition, temperature and discrepancy", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-016" ], "questions": [ { "id": "shortage-excess-damage-loss-delay-wrongitem-condition-temperature-and-discrepancy-q01", "text": "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?", "kind": "quality", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "shortage-excess-damage-loss-delay-wrongitem-condition-temperature-and-discrepancy-q02", "text": "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?", "kind": "interoperability", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "shortage-excess-damage-loss-delay-wrongitem-condition-temperature-and-discrepancy-q03", "text": "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?", "kind": "spatial", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "shortage-excess-damage-loss-delay-wrongitem-condition-temperature-and-discrepancy-data", "name": "Shortage, excess, damage, loss, delay, wrong item, condition, temperature and discrepancy data", "description": "Typed fulfilment data for shortage, excess, damage, loss, delay, wrong item, condition, temperature and discrepancy, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-016" ] } ], "artifacts": [ { "id": "shortage-excess-damage-loss-delay-wrongitem-condition-temperature-and-discrepancy-record", "name": "Shortage, excess, damage, loss, delay, wrong item, condition, temperature and discrepancy record", "description": "Immutable or successor-versioned fulfilment evidence for shortage, excess, damage, loss, delay, wrong item, condition, temperature and discrepancy.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for shortage-excess-damage-loss-delay-wrongitem-condition-temperature-and-discrepancy; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "failed-attempt-hold-reroute-retry-redelivery-replacement-repair-cancellation-and-escalation", "name": "Failed attempt, hold, reroute, retry, redelivery, replacement, repair, cancellation and escalation", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-016" ], "questions": [ { "id": "failed-attempt-hold-reroute-retry-redelivery-replacement-repair-cancellation-and-escalation-q01", "text": "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?", "kind": "exception", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "failed-attempt-hold-reroute-retry-redelivery-replacement-repair-cancellation-and-escalation-q02", "text": "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?", "kind": "decision", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "failed-attempt-hold-reroute-retry-redelivery-replacement-repair-cancellation-and-escalation-q03", "text": "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?", "kind": "provenance", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "failed-attempt-hold-reroute-retry-redelivery-replacement-repair-cancellation-and-escalation-data", "name": "Failed attempt, hold, reroute, retry, redelivery, replacement, repair, cancellation and escalation data", "description": "Typed fulfilment data for failed attempt, hold, reroute, retry, redelivery, replacement, repair, cancellation and escalation, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-016" ] } ], "artifacts": [ { "id": "failed-attempt-hold-reroute-retry-redelivery-replacement-repair-cancellation-and-escalation-record", "name": "Failed attempt, hold, reroute, retry, redelivery, replacement, repair, cancellation and escalation record", "description": "Immutable or successor-versioned fulfilment evidence for failed attempt, hold, reroute, retry, redelivery, replacement, repair, cancellation and escalation.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for failed-attempt-hold-reroute-retry-redelivery-replacement-repair-cancellation-and-escalation; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "reconciliation-acceptance-remedy-completion-and-discharge", "name": "Reconciliation, acceptance, remedy, completion and discharge", "description": "Groups source-qualified fulfilment context for reconciliation, acceptance, remedy, completion and discharge.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "findings": [ { "id": "order-dispatch-receipt-invoice-quantity-condition-status-and-evidence-reconciliation", "name": "Order, dispatch, receipt, invoice, quantity, condition, status and evidence reconciliation", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "questions": [ { "id": "order-dispatch-receipt-invoice-quantity-condition-status-and-evidence-reconciliation-q01", "text": "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?", "kind": "validation", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "order-dispatch-receipt-invoice-quantity-condition-status-and-evidence-reconciliation-q02", "text": "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?", "kind": "identity", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "order-dispatch-receipt-invoice-quantity-condition-status-and-evidence-reconciliation-q03", "text": "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?", "kind": "ownership", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "order-dispatch-receipt-invoice-quantity-condition-status-and-evidence-reconciliation-data", "name": "Order, dispatch, receipt, invoice, quantity, condition, status and evidence reconciliation data", "description": "Typed fulfilment data for order, dispatch, receipt, invoice, quantity, condition, status and evidence reconciliation, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "order-dispatch-receipt-invoice-quantity-condition-status-and-evidence-reconciliation-record", "name": "Order, dispatch, receipt, invoice, quantity, condition, status and evidence reconciliation record", "description": "Immutable or successor-versioned fulfilment evidence for order, dispatch, receipt, invoice, quantity, condition, status and evidence reconciliation.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for order-dispatch-receipt-invoice-quantity-condition-status-and-evidence-reconciliation; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "accepted-partial-rejected-remedied-completed-disputed-obligation-discharge-return-and-compensation-reference", "name": "Accepted, partial, rejected, remedied, completed, disputed, obligation discharge, return and compensation reference", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "questions": [ { "id": "accepted-partial-rejected-remedied-completed-disputed-obligation-discharge-return-and-compensation-reference-q01", "text": "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?", "kind": "lifecycle", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "accepted-partial-rejected-remedied-completed-disputed-obligation-discharge-return-and-compensation-reference-q02", "text": "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?", "kind": "classification", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "accepted-partial-rejected-remedied-completed-disputed-obligation-discharge-return-and-compensation-reference-q03", "text": "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?", "kind": "authority", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "accepted-partial-rejected-remedied-completed-disputed-obligation-discharge-return-and-compensation-reference-data", "name": "Accepted, partial, rejected, remedied, completed, disputed, obligation discharge, return and compensation reference data", "description": "Typed fulfilment data for accepted, partial, rejected, remedied, completed, disputed, obligation discharge, return and compensation reference, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "accepted-partial-rejected-remedied-completed-disputed-obligation-discharge-return-and-compensation-reference-record", "name": "Accepted, partial, rejected, remedied, completed, disputed, obligation discharge, return and compensation reference record", "description": "Immutable or successor-versioned fulfilment evidence for accepted, partial, rejected, remedied, completed, disputed, obligation discharge, return and compensation reference.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for accepted-partial-rejected-remedied-completed-disputed-obligation-discharge-return-and-compensation-reference; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-provenance-time-access-and-interoperability", "name": "Governance, provenance, time, access and interoperability", "description": "Groups fulfilment context for governance, provenance, time, access and interoperability.", "rationale": "Qualify authority, clocks, evidence, privacy, retention and projections", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "layers": [ { "id": "source-provenance-access-privacy-retention-and-correction", "name": "Source, provenance, access, privacy, retention and correction", "description": "Groups source-qualified fulfilment context for source, provenance, access, privacy, retention and correction.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-017" ], "findings": [ { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit", "name": "Owner, steward, source system, actor, activity, derivation, revision, conflict and audit", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-017" ], "questions": [ { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit-q01", "text": "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?", "kind": "provenance", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit-q02", "text": "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?", "kind": "composition", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit-q03", "text": "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?", "kind": "requirement", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit-data", "name": "Owner, steward, source system, actor, activity, derivation, revision, conflict and audit data", "description": "Typed fulfilment data for owner, steward, source system, actor, activity, derivation, revision, conflict and audit, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-017" ] } ], "artifacts": [ { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit-record", "name": "Owner, steward, source system, actor, activity, derivation, revision, conflict and audit record", "description": "Immutable or successor-versioned fulfilment evidence for owner, steward, source system, actor, activity, derivation, revision, conflict and audit.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-017" ] } ], "inline_only_rationale": null }, { "id": "purpose-address-recipient-access-confidentiality-disclosure-retention-legalhold-correction-and-tombstone", "name": "Purpose, address, recipient, access, confidentiality, disclosure, retention, legal hold, correction and tombstone", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-017" ], "questions": [ { "id": "purpose-address-recipient-access-confidentiality-disclosure-retention-legalhold-correction-and-tombstone-q01", "text": "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?", "kind": "privacy", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "purpose-address-recipient-access-confidentiality-disclosure-retention-legalhold-correction-and-tombstone-q02", "text": "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?", "kind": "relationship", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "purpose-address-recipient-access-confidentiality-disclosure-retention-legalhold-correction-and-tombstone-q03", "text": "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?", "kind": "constraint", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "purpose-address-recipient-access-confidentiality-disclosure-retention-legalhold-correction-and-tombstone-data", "name": "Purpose, address, recipient, access, confidentiality, disclosure, retention, legal hold, correction and tombstone data", "description": "Typed fulfilment data for purpose, address, recipient, access, confidentiality, disclosure, retention, legal hold, correction and tombstone, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-017" ] } ], "artifacts": [ { "id": "purpose-address-recipient-access-confidentiality-disclosure-retention-legalhold-correction-and-tombstone-record", "name": "Purpose, address, recipient, access, confidentiality, disclosure, retention, legal hold, correction and tombstone record", "description": "Immutable or successor-versioned fulfilment evidence for purpose, address, recipient, access, confidentiality, disclosure, retention, legal hold, correction and tombstone.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for purpose-address-recipient-access-confidentiality-disclosure-retention-legalhold-correction-and-tombstone; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "id": "event-clocks-validation-and-loss-aware-projections", "name": "Event clocks, validation and loss-aware projections", "description": "Groups source-qualified fulfilment context for event clocks, validation and loss-aware projections.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "findings": [ { "id": "requested-promised-ready-dispatched-arrived-attempted-handedover-received-inspected-accepted-completed-observed-and-known-time", "name": "Requested, promised, ready, dispatched, arrived, attempted, handed over, received, inspected, accepted, completed, observed and known time", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "requested-promised-ready-dispatched-arrived-attempted-handedover-received-inspected-accepted-completed-observed-and-known-time-q01", "text": "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?", "kind": "temporal", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "requested-promised-ready-dispatched-arrived-attempted-handedover-received-inspected-accepted-completed-observed-and-known-time-q02", "text": "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?", "kind": "state", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "requested-promised-ready-dispatched-arrived-attempted-handedover-received-inspected-accepted-completed-observed-and-known-time-q03", "text": "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?", "kind": "process", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "requested-promised-ready-dispatched-arrived-attempted-handedover-received-inspected-accepted-completed-observed-and-known-time-data", "name": "Requested, promised, ready, dispatched, arrived, attempted, handed over, received, inspected, accepted, completed, observed and known time data", "description": "Typed fulfilment data for requested, promised, ready, dispatched, arrived, attempted, handed over, received, inspected, accepted, completed, observed and known time, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "requested-promised-ready-dispatched-arrived-attempted-handedover-received-inspected-accepted-completed-observed-and-known-time-record", "name": "Requested, promised, ready, dispatched, arrived, attempted, handed over, received, inspected, accepted, completed, observed and known time record", "description": "Immutable or successor-versioned fulfilment evidence for requested, promised, ready, dispatched, arrived, attempted, handed over, received, inspected, accepted, completed, observed and known time.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for requested-promised-ready-dispatched-arrived-attempted-handedover-received-inspected-accepted-completed-observed-and-known-time; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "identity-quantity-state-sequence-condition-term-policy-privacy-ubl-edifact-epcis-schemaorg-tmf-prov-and-api-validation", "name": "Identity, quantity, state, sequence, condition, term, policy, privacy, UBL, EDIFACT, EPCIS, Schema.org, TMF, PROV and API validation", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "identity-quantity-state-sequence-condition-term-policy-privacy-ubl-edifact-epcis-schemaorg-tmf-prov-and-api-validation-q01", "text": "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?", "kind": "interoperability", "answer_data": [ "fulfilment, version, order obligation, unit, item, party and external identifiers", "goods, service, digital, pickup, installation, partial, staged or third-party profile and schema version", "unknown, planned, ready, partial, completed, failed, disputed and not-applicable states" ] }, { "id": "identity-quantity-state-sequence-condition-term-policy-privacy-ubl-edifact-epcis-schemaorg-tmf-prov-and-api-validation-q02", "text": "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?", "kind": "lifecycle", "answer_data": [ "buyer, seller, supplier, provider, delivery party, recipient, beneficiary, agent, carrier, inspector and source system", "purpose, contract, order, delegation, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "identity-quantity-state-sequence-condition-term-policy-privacy-ubl-edifact-epcis-schemaorg-tmf-prov-and-api-validation-q03", "text": "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?", "kind": "event", "answer_data": [ "distinct obligation, readiness, dispatch, transport, handover, receipt, inspection, acceptance, completion and knowledge times", "order, inventory, dispatch, shipment, service, receipt, inspection, invoice, evidence, quality and uncertainty references", "timezone, quantity variance, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "identity-quantity-state-sequence-condition-term-policy-privacy-ubl-edifact-epcis-schemaorg-tmf-prov-and-api-validation-data", "name": "Identity, quantity, state, sequence, condition, term, policy, privacy, UBL, EDIFACT, EPCIS, Schema.org, TMF, PROV and API validation data", "description": "Typed fulfilment data for identity, quantity, state, sequence, condition, term, policy, privacy, ubl, edifact, epcis, schema.org, tmf, prov and api validation, qualified by version, obligation, authority, quantity, time, condition, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "identity-quantity-state-sequence-condition-term-policy-privacy-ubl-edifact-epcis-schemaorg-tmf-prov-and-api-validation-record", "name": "Identity, quantity, state, sequence, condition, term, policy, privacy, UBL, EDIFACT, EPCIS, Schema.org, TMF, PROV and API validation record", "description": "Immutable or successor-versioned fulfilment evidence for identity, quantity, state, sequence, condition, term, policy, privacy, ubl, edifact, epcis, schema.org, tmf, prov and api validation.", "media_or_form": [ "logical fulfilment specification assertion", "obligation, unit, dispatch, handover, receipt, inspection, exception, completion, validation or projection record" ], "serial": true, "identity_strategy": "Fulfilment ID plus independent version, obligation, unit, dispatch, receipt or event ID and artifact kind for identity-quantity-state-sequence-condition-term-policy-privacy-ubl-edifact-epcis-schemaorg-tmf-prov-and-api-validation; party, order number, date, location, filename or digest never identifies fulfilment alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-fulfilment-obligation", "name": "Register fulfilment obligation", "description": "Governed operation to register fulfilment obligation without autonomous order acceptance, inventory mutation, dispatch, service execution, acceptance, billing, payment, return, refund, disclosure or disposition.", "inputs": [ "order or contract reference", "promised subject and quantity", "party roles" ], "outputs": [ "versioned fulfilment case" ], "preconditions": [ "identity, obligation, scope, authority, item, quantity and terms pass" ], "effects": [ "no inventory, shipment, service, invoice or payment is executed" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "plan-and-allocate-fulfilment", "name": "Plan and allocate fulfilment", "description": "Governed operation to plan and allocate fulfilment without autonomous order acceptance, inventory mutation, dispatch, service execution, acceptance, billing, payment, return, refund, disclosure or disposition.", "inputs": [ "fulfilment units", "external availability and capacity evidence" ], "outputs": [ "source-qualified plan and allocation request" ], "preconditions": [ "dependencies, quantity, timing, capacity source, authority and idempotency pass" ], "effects": [ "external inventory remains authoritative" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-013" ] }, { "id": "record-readiness-and-preparation", "name": "Record readiness and preparation", "description": "Governed operation to record readiness and preparation without autonomous order acceptance, inventory mutation, dispatch, service execution, acceptance, billing, payment, return, refund, disclosure or disposition.", "inputs": [ "fulfilment case", "external pick, pack, provision or activation evidence" ], "outputs": [ "readiness and preparation assertions" ], "preconditions": [ "unit, item, quantity, condition, actor, source and time pass" ], "effects": [ "warehouse or service execution remains external" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012" ] }, { "id": "record-dispatch-or-activation", "name": "Record dispatch or activation", "description": "Governed operation to record dispatch or activation without autonomous order acceptance, inventory mutation, dispatch, service execution, acceptance, billing, payment, return, refund, disclosure or disposition.", "inputs": [ "fulfilment unit", "dispatch, shipment or activation evidence" ], "outputs": [ "immutable dispatch or activation assertion" ], "preconditions": [ "authority, item, quantity, origin, destination or endpoint, time and source pass" ], "effects": [ "dispatch does not prove delivery or acceptance" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-010", "SRC-012" ] }, { "id": "record-handover-and-receipt", "name": "Record handover and receipt", "description": "Governed operation to record handover and receipt without autonomous order acceptance, inventory mutation, dispatch, service execution, acceptance, billing, payment, return, refund, disclosure or disposition.", "inputs": [ "fulfilment unit", "delivery attempt, handover and receipt evidence" ], "outputs": [ "source-qualified handover and receipt assertions" ], "preconditions": [ "recipient, place or endpoint, quantity, condition, event time and proof pass" ], "effects": [ "receipt does not prove inspection, acceptance or payment" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-010", "SRC-011" ] }, { "id": "inspect-accept-or-reject", "name": "Inspect, accept or reject", "description": "Governed operation to inspect, accept or reject without autonomous order acceptance, inventory mutation, dispatch, service execution, acceptance, billing, payment, return, refund, disclosure or disposition.", "inputs": [ "received fulfilment unit", "inspection method and evidence", "authorized decision" ], "outputs": [ "inspection and acceptance or rejection assertion" ], "preconditions": [ "criteria, quantity, condition, method, authority, reason and time pass" ], "effects": [ "decision does not autonomously invoice, pay, return or refund" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-009", "SRC-016" ] }, { "id": "record-exception-and-recovery", "name": "Record exception and recovery", "description": "Governed operation to record exception and recovery without autonomous order acceptance, inventory mutation, dispatch, service execution, acceptance, billing, payment, return, refund, disclosure or disposition.", "inputs": [ "fulfilment case", "discrepancy or failure evidence", "recovery proposal" ], "outputs": [ "exception assertion and governed recovery request" ], "preconditions": [ "type, severity, affected unit, evidence, authority and dependencies pass" ], "effects": [ "retry, replacement, reroute or cancellation remains separately authorized" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009" ] }, { "id": "reconcile-and-assess-completion", "name": "Reconcile and assess completion", "description": "Governed operation to reconcile and assess completion without autonomous order acceptance, inventory mutation, dispatch, service execution, acceptance, billing, payment, return, refund, disclosure or disposition.", "inputs": [ "order obligations", "fulfilment, receipt, inspection and exception evidence" ], "outputs": [ "reconciliation and proposed completion or discharge decision" ], "preconditions": [ "identity, quantity, condition, states, times, open exceptions and authority pass" ], "effects": [ "completion does not prove conformity, payment or dispute closure" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-009", "SRC-016" ] }, { "id": "correct-supersede-or-cancel-evidence", "name": "Correct, supersede or cancel evidence", "description": "Governed operation to correct, supersede or cancel evidence without autonomous order acceptance, inventory mutation, dispatch, service execution, acceptance, billing, payment, return, refund, disclosure or disposition.", "inputs": [ "issued fulfilment record", "authorized correction or cancellation reason" ], "outputs": [ "immutable successor and retained prior lineage" ], "preconditions": [ "authority, scope, dependencies, affected documents and non-cascade checks pass" ], "effects": [ "external order, shipment, invoice, return and payment masters are not mutated" ], "source_refs": [ "SRC-001", "SRC-015" ] }, { "id": "query-project-retain-and-audit", "name": "Query, project, retain and audit", "description": "Governed operation to query, project, retain and audit without autonomous order acceptance, inventory mutation, dispatch, service execution, acceptance, billing, payment, return, refund, disclosure or disposition.", "inputs": [ "fulfilment case", "purpose-bound access", "target profile", "records policy" ], "outputs": [ "filtered view, loss-declaring projection, retention result or audit event" ], "preconditions": [ "purpose, authority, privacy, mapping, digest, lifecycle and legal-hold checks pass" ], "effects": [ "projection never replaces the canonical case and disposition stays external" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "composition": [ { "target": "WM-ECO-019", "relation": "REFERENCE", "purpose": "Resolve the candidate containing purchase-order obligation without granting cascade mutation authority.", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "target": "WM-FLW-011", "relation": "REFERENCE", "purpose": "Resolve candidate shipment and transport execution without duplicating its lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-010", "SRC-013" ] }, { "target": "WM-ECO-008", "relation": "REFERENCE", "purpose": "Resolve candidate invoice evidence without owning billing or settlement.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "target": "Party, Product, Service, Inventory, Warehouse, Shipment, Consignment, Package, Location, Digital Artifact, Entitlement, Work Order, Payment, Return, Refund, Support and Records models", "relation": "REFERENCE", "purpose": "Resolve external identities, states, operations and evidence without duplicating their masters.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-012", "SRC-013", "SRC-015" ] }, { "target": "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", "relation": "ALIGN", "purpose": "Project version-pinned logistics, traceability, legal, discovery, service, temporal, provenance, quality, policy and API views with declared loss.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension owner, namespace authority, accountable fulfilment owner and delegated commercial, logistics, service, inspection and legal authorities", "Authoritative Order, Contract, Party, Product, Inventory, Shipment, Service, Entitlement, Location, Invoice, Payment, Return and Records registries", "Approved goods, service, digital, pickup, installation, sector, jurisdiction, quality, privacy, retention and interoperability profiles", "Role, delegation, substitution, dispatch, handover, acceptance, exception, completion, disclosure and agent-operation policies" ], "namespace_guidance": "Mint fulfilment, version, obligation, unit, dispatch, receipt, inspection, exception, completion, validation and projection IDs; preserve external master identifiers.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative fulfilment identifier, owner namespace and version head, never by order number, shipment, invoice, party, date, location or digest alone.", "Keep order obligation, fulfilment, inventory movement, shipment, package, consignment, service execution, entitlement, invoice, payment, return and refund independently identifiable." ], "patch_rules": [ "Extensions declare profile, identity, obligation, parties, subject, composition, quantity, condition, lifecycle, time, privacy and interoperability effects.", "Issued versions are immutable; splits, substitutions, corrections, cancellations and reconciliations create linked successors with affected units and authority.", "Never silently change obligation, item, quantity, condition, recipient, destination, service endpoint, substitution, acceptance criteria, term, authority or privacy marking." ], "compatibility_rules": [ "Ignore additive fields only when identity, version, obligation, parties, units, quantities, states, times, authority, access and provenance survive.", "Every projection pins specification version and declares loss in composition, quantity, condition, state, timing, authority and evidence semantics." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier for fulfilment, version, obligation, unit, dispatch, receipt, inspection, exception or artifact, qualified by namespace and kind.", "Governed globally resolvable fulfilment or artifact IRI.", "Dimension UUID or ULID when neither preceding identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; distinguish requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times whenever they differ.", "serial_naming_rule": "Use {fulfilment-id}--{version-id}--{obligation-unit-dispatch-receipt-or-event-id}--{artifact-kind}--{revision-id}.", "integrity_rule": "Store digest, media type, record kind, fulfilment and version IDs, profile, obligation, actor, quantity and unit, condition, event and knowledge times, confidentiality and provenance." }, "policies": [ "The fulfilment model owns obligation-performance context but not order, party, product, inventory, shipment, service, entitlement, invoice, payment, return or records masters.", "Commitment, allocation, readiness, dispatch, custody, attempt, handover, receipt, inspection, acceptance, completion, billing and payment states and clocks remain distinct.", "Dispatched, delivered, received, accepted or completed status never alone proves conformity, intended-recipient receipt, payment, discharge or dispute closure.", "Agents cannot autonomously accept obligations, allocate inventory, dispatch, activate, sign receipt, accept conformity, discharge, invoice, pay, return, refund, disclose or dispose without delegated authority." ], "crud": { "read": [ "Resolve fulfilment head, obligation, parties, units, subjects, quantities, conditions, plan, dispatch, handover, receipt, inspection, exceptions, completion, access and projection loss." ], "create": [ "Bind identity, obligation, owner, provider, recipient, purpose, profile, promised subject, quantity, terms, source authority and initial state before assertions are accepted." ], "update": [ "Append successor allocation, preparation, dispatch, handover, receipt, inspection, exception, remedy, completion and correction assertions with reason, authority, event time and knowledge time." ], "delete": [ "Apply legal hold, commercial, logistics, consumer, safety, privacy and Dimension retention policy; tombstone only the catalogue view without cascading to external masters, and let authoritative systems execute physical disposition." ] }, "roles": [ { "name": "Fulfilment owner", "responsibilities": [ "Own purpose, scope, profile, lifecycle, compatibility and accountable use." ] }, { "name": "Order and commercial steward", "responsibilities": [ "Own obligation, terms, tolerance, substitution and contract or order bindings." ] }, { "name": "Inventory and preparation steward", "responsibilities": [ "Own allocation, backorder, readiness, pick, pack and inventory-source bindings." ] }, { "name": "Logistics or service steward", "responsibilities": [ "Own dispatch, shipment, activation, handover and service-execution bindings." ] }, { "name": "Recipient and inspection authority", "responsibilities": [ "Own receipt, examination, conformity, acceptance, rejection and discrepancy decisions." ] }, { "name": "Privacy, safety and legal authority", "responsibilities": [ "Own protected delivery data, risk, remedies, access, jurisdiction and retention limitations." ] }, { "name": "Interoperability and records steward", "responsibilities": [ "Own mappings, conformance evidence, declared loss, legal hold and disposition policy." ] } ], "access": { "default_rule": "Deny recipient, address, route, access-code, item, serial, condition, tracking, proof, invoice, dispute and security-sensitive data unless purpose-bound policy permits the minimum necessary view.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Declared operational, safety, emergency, support, legal, audit, regulatory or subject-rights access must cite authority, scope, purpose and time limit and be logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, fulfilment and version, operation, authority, policy, RFC 3339 time, affected units or terms, source revision and outcome without duplicating restricted recipient data." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension namespace, order, fulfilment, logistics, quality, privacy, retention and agent policies.", "Read this fulfilment and linked order, party, product, inventory, shipment, service, entitlement, invoice, payment, return and records models before mutation." ] } }, "coverage": { "claim": "WM-ECO-024 covers one governed fulfilment aggregate from external obligation and promised subject through composition, allocation, readiness, dispatch or activation, handover, receipt, inspection, exceptions, reconciliation, completion, governance and loss-aware projections. Candidate relations, sector and jurisdiction profiles, legal determinations and independent external review remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Identity is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "classification and direct properties", "status": "covered", "notes": "Classification and direct properties is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Recognition and observation is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Capabilities and possible actions is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "composition", "status": "covered", "notes": "Composition is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "lifecycle", "status": "covered", "notes": "Lifecycle is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "relationships", "status": "covered", "notes": "Relationships is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "temporal", "status": "covered", "notes": "Temporal is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "spatial", "status": "covered", "notes": "Spatial is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "provenance", "status": "covered", "notes": "Provenance is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "ownership", "status": "covered", "notes": "Ownership is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "validation", "status": "covered", "notes": "Validation is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "access", "status": "covered", "notes": "Access is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retention and deletion is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "interoperability", "status": "covered", "notes": "Interoperability is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "authority and ethics", "status": "covered", "notes": "Authority and ethics is explicit; sector, jurisdiction, safety, legal-effect, relation and external-review profiles remain held where applicable." } ], "known_omissions": [ "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." ], "conflicts": [ "Order obligation, fulfilment case, inventory allocation, shipment, consignment, package, service execution, entitlement, invoice, payment, return and refund are related but not interchangeable.", "Committed, allocated, ready, dispatched, in transit, attempted, handed over, received, inspected, accepted, completed and discharged states belong to separate axes.", "Promised, scheduled, actual event, observation, ingestion and knowledge times must not be collapsed.", "Delivery evidence may conflict with recipient receipt, inspection or acceptance evidence and must coexist without destructive overwrite." ], "regional_assumptions": [ "Delivery, risk transfer, examination, acceptance, remedies, returns, taxes, customs and record retention depend on governing law, sector, contract and party type.", "CISG and EU consumer and sale-of-goods rules are scoped profiles, not universal governing law; Incoterms content is not reproduced." ], "adversarial_checks": [ "Reject fulfilment that collapses into order, inventory, shipment, service, invoice, payment, return or refund masters.", "Reject dispatched as delivered, delivered as intended-recipient receipt, receipt as inspection or acceptance, or completion as conformity and discharge.", "Reject quantity or condition without unit, item or lot identity, source, method, event time, uncertainty and reconciliation state.", "Reject correction or cancellation that erases prior dispatch, receipt, inspection or exception evidence.", "Reject autonomous allocation, dispatch, activation, acceptance, discharge, billing, payment, return, refund, disclosure or disposition without authority.", "Reject a projection that hides composition, quantity, condition, state-axis, time, authority, provenance or information loss." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted-with-profile-boundary", "rationale": "The root is an obligation-performance and evidence aggregate. Order, party, product, inventory, shipment, consignment, package, service execution, entitlement, invoice, payment, return, refund and records remain external masters." }, "decisions": [ { "concept": "Fulfilment obligation and execution evidence", "disposition": "accepted-with-explicit-boundary", "rationale": "The fulfilment case binds an external obligation to versioned performance evidence without becoming the order, inventory, shipment, service, invoice or payment master." }, { "concept": "WM-ECO-019 containment signal", "disposition": "accepted-as-candidate-reference", "rationale": "The candidate ledger says Purchase Order contains fulfilment obligations. This is retained as a non-canonical parent reference and grants no cascade mutation authority." }, { "concept": "WM-FLW-011 and WM-ECO-008 references", "disposition": "accepted-as-candidate-references", "rationale": "Shipment and Invoice are plausible external evidence neighbors, but the candidate edges do not let fulfilment own their state, execution or disposition." }, { "concept": "Promised subjects, units, quantities and conditions", "disposition": "accepted", "rationale": "Products, services, resources, content, lots and serials remain external while fulfilment units, splits, quantities, substitution, tolerance and condition are source-qualified bindings." }, { "concept": "Allocation, preparation and dispatch", "disposition": "accepted-with-external-master-boundary", "rationale": "Planning and readiness assertions are local context; inventory movement, warehouse execution, service provisioning and carrier operations remain external." }, { "concept": "Handover, receipt, inspection and acceptance", "disposition": "accepted", "rationale": "Each step preserves independent actor, source, evidence, state and time; a delivery claim cannot prove intended-recipient receipt, inspection or acceptance." }, { "concept": "Exceptions, remedies and completion", "disposition": "accepted", "rationale": "Shortage, excess, damage, loss, delay, failure, retry, replacement, rejection, completion and discharge remain separately attributable; return and compensation execute elsewhere." }, { "concept": "Legal delivery profiles", "disposition": "accepted-with-jurisdiction-hold", "rationale": "CISG and EU consumer and sales rules are scoped profiles rather than universal definitions of delivery, risk transfer, conformity or remedies." }, { "concept": "Interoperability projections", "disposition": "accepted-with-loss-declaration", "rationale": "UBL, UN/EDIFACT, EPCIS, Schema.org, TM Forum, RFC, PROV, DQV, ODRL and OpenAPI cover different facets and never replace the canonical aggregate." }, { "concept": "Single-provider waiver and no-tools audit", "disposition": "accepted-with-mandatory-hold", "rationale": "One bounded Claude Sonnet and one bounded Grok attempt each timed out after 120 seconds. Codex separately audited the frozen validated result and comparison without new facts; assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-ECO-024 each timed out after 120 seconds; no external result was admitted.", "Relation hold: WM-ECO-019 CONTAINS WM-ECO-024 and WM-ECO-024 references to WM-FLW-011 and WM-ECO-008 remain candidate ledger edges, not canonical relations.", "Boundary hold: fulfilment, order, party, product, inventory, shipment, consignment, package, service execution, entitlement, invoice, payment, return, refund and records retain separate identities.", "State-axis hold: commitment, allocation, readiness, dispatch, custody, attempt, handover, receipt, inspection, acceptance, completion, billing and payment states and clocks must not collapse.", "Quantity and condition hold: every promised, allocated, dispatched, received, accepted, rejected and outstanding value requires item, unit, lot or serial, method, source, time and uncertainty.", "Temporal hold: requested, promised, planned, ready, dispatched, arrived, attempted, handed-over, received, inspected, accepted, completed, observed, ingested and known times remain distinct.", "Completion hold: delivered, received, accepted, completed, conforming, paid, discharged and dispute-free require separate evidence and authority.", "Authority hold: order acceptance, allocation, dispatch, activation, receipt signature, conformity acceptance, discharge, billing, payment, return, refund, disclosure and disposition require delegated authority.", "Jurisdiction hold: CISG and EU consumer and sale-of-goods rules are scoped profiles; national, sector, safety, customs and contract rules need validation.", "Interoperability hold: every UBL, UN/EDIFACT, EPCIS, Schema.org, TM Forum, RFC, PROV, DQV, ODRL and OpenAPI projection needs version pins, conformance evidence and loss declarations.", "Privacy hold: recipient, address, route, access-code, item, serial, condition, tracking, proof and dispute data require purpose-bound access, minimization and retention controls.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 18, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }