# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T20:44:03Z", "synthesisSha256": "ba39b42da3b7054ad18e460d67e8ff667e8e9f7b145f337b849e1ce6362d5f3a", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-FLW-011", "registryId": "vr.wm-flw-011", "name": "Shipment / Consignment", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.FLW.LOG" ], "tags": [ "shipment", "consignment", "phy.flw.log" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-flw-011-shipment-consignment/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-011", "model": { "registry_id": "vr.wm-flw-011", "model_id": "WM-FLW-011", "name": "Shipment / Consignment", "entry_kind": "aggregate", "purpose": "Represent one governed trade shipment or transport consignment, or an explicitly combined logistics view, with goods scope, parties, endpoints, many-to-many allocation, requirements, status assertions and correction lineage without becoming its goods, movement, handling units, documents, trace or fulfilment obligation.", "scope_statement": "Owns mandatory shipment-or-consignment semantic kind; object and revision identity; commercial, carrier, customs and party identifiers; trade and transport party-role bindings; shipment-consignment allocation; item, quantity, value and origin bindings; package, handling-unit and equipment membership references; logistics locations and movement-plan references; service, handling, dangerous-goods, temperature, security, customs and regulatory requirements; planned, estimated, predicted, observed and actual milestone assertions; shipment-scoped custody and responsibility bindings; exceptions and outcome references; qualified measures; document and evidence references; provenance, reconciliation, access, retention and loss-aware projections. Goods, products, orders, contracts, fulfilment, handling units, inventory movements, journeys, routes, services, schedules, parties, places, bookings, transport documents, customs declarations, dangerous-goods masters, sensors, generic events, chain of custody, incidents, insurance claims and evidence masters remain external.", "in_scope": [ "Shipment or consignment identity, revision, mandatory semantic kind, party and endpoint boundary, many-to-many allocation and successor lineage", "Goods-item scope, package and handling-unit membership references, requirements, movement bindings, milestone assertions, qualified measures and documents", "Status, exceptions, responsibility bindings, provenance, reconciliation, privacy, access, retention and interoperability" ], "out_of_scope": [ "Owning goods, products, orders, contracts, fulfilment, handling units, inventory movement, journey, route, service, schedule, party, place, booking, document, declaration, dangerous-goods master, sensor, trace, incident, claim, evidence or payment lifecycles", "Equating shipment with consignment, item with package, package with handling unit, custody with ownership, transport status with inventory state, plan with actual movement, milestone assertion with trace event or proof of delivery with fulfilment", "Performing transportation, inventory mutation, customs clearance, dangerous-goods certification, custody proof, claims determination, autonomous consequential rerouting, protected disclosure or irreversible deletion" ], "boundary_notes": [ { "neighbor": "WM-FLW-004 Goods Movement / Logistics", "distinction": "Goods Movement / Logistics is a broader flow context. Shipment / Consignment owns the bounded trade or transport grouping and its assertions; the registered parent signal remains candidate until both models are jointly reviewed.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] }, { "neighbor": "WM-OBJ-021 Handling Unit / Logistics Container", "distinction": "Shipment / Consignment records membership, loading, marks and seals. Handling-unit identity, physical properties, nesting, condition and lifecycle remain externally mastered; CONTAINS is accepted only as typed membership.", "source_refs": [ "SRC-005", "SRC-007", "SRC-010", "SRC-013", "SRC-014", "SRC-017", "SRC-020" ] }, { "neighbor": "WM-FLW-009 Journey / Trip and WM-FLW-010 Route / Itinerary", "distinction": "Shipment / Consignment binds planned or actual transport references and milestones. Journey execution, route geometry, movement observations and outcomes remain externally mastered.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013", "SRC-018" ] }, { "neighbor": "WM-FLW-012 Inventory Movement", "distinction": "A shipment milestone may cause or correlate with inventory movement, but stock ledger, location balance, reservation and inventory adjustment remain Inventory Movement concerns.", "source_refs": [ "SRC-003", "SRC-013", "SRC-014", "SRC-015" ] }, { "neighbor": "WM-FLW-013 Supply-chain Trace / Chain of Custody", "distinction": "The model binds source-qualified milestones and current custody or responsibility assertions. Cross-organizational event graph, chain-of-custody proof and trace-query lifecycle remain in the trace pattern.", "source_refs": [ "SRC-005", "SRC-006", "SRC-014", "SRC-015", "SRC-018", "SRC-022" ] }, { "neighbor": "WM-ECO-024 Fulfilment / Delivery", "distinction": "Fulfilment may reference shipments as physical delivery evidence. Commercial obligation, acceptance, proof evaluation, remedies and fulfilment outcome remain externally mastered.", "source_refs": [ "SRC-003", "SRC-006", "SRC-013" ] }, { "neighbor": "Transport document, Customs declaration and Insurance claim", "distinction": "Shipping instructions, waybills, bills of lading, declarations and claims are independently governed records referenced by the shipment or consignment; their issuance, legal effect and adjudication are external.", "source_refs": [ "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-019" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Buy-Ship-Pay Reference Data Model", "organization": "UN/CEFACT", "url": "https://unece.org/trade/standards/trade-and-uncefact/uncefact/supply-chain-management", "version_or_date": "BSP-RDM overview accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Provides the syntax-neutral cross-domain trade and multimodal transport reference-model framework." }, { "id": "SRC-002", "title": "UN/CEFACT Web Vocabulary", "organization": "UN/CEFACT", "url": "https://vocab.unece.org/docs/", "version_or_date": "Vocabulary documentation accessed 2026-09-06", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Publishes current Buy-Ship-Pay semantics, code lists and linked-data vocabulary from maintained source files." }, { "id": "SRC-003", "title": "Supply Chain Reference Data Model D22A", "organization": "UN/CEFACT", "url": "https://service.unece.org/trade/uncefact/publication/SupplyChainMGMT/SCRDM/HTML/011.htm", "version_or_date": "SCRDM D22A, June 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines the supply-chain master structure and reusable trade-delivery and consignment entities." }, { "id": "SRC-004", "title": "Supply Chain Reference Data Model BRS", "organization": "UN/CEFACT", "url": "https://unece.org/fileadmin/DAM/uncefact/BRS/BRS_SCRDM_v1.0.0.2.pdf", "version_or_date": "Version 1.0.0.2, 15 December 2016", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines consignment, consignment item, logistics package, delivery and related supply-chain terms." }, { "id": "SRC-005", "title": "Integrated Track and Trace for Multi-Modal Transportation BRS", "organization": "UN/CEFACT", "url": "https://unece.org/sites/default/files/2023-07/BRS-IntegratedTrackandTraceforMulti-ModalTransportationv0.1-Final.pdf", "version_or_date": "Version 0.1, September 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Models shipment lifecycle links to consignments, transport units, parties, events and status evidence." }, { "id": "SRC-006", "title": "Integrated Track and Trace: trade shipment and consignment distinction", "organization": "UN/CEFACT", "url": "https://unece.org/sites/default/files/2021-03/ECE_TRADE_C_CEFACT_2021_INF4E-Integrated-T-T.pdf", "version_or_date": "ECE/TRADE/C/CEFACT/2021/INF.4", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Distinguishes seller-to-buyer trade shipment from a transport-contract consignment and explains split and consolidation." }, { "id": "SRC-007", "title": "Shipping Instructions Business Requirements Specification", "organization": "UN/CEFACT", "url": "https://unece.org/fileadmin/DAM/cefact/brs/BRS_ShippingInstruction_v1.pdf", "version_or_date": "Version 1.0, October 2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines instructions linked to consignment, items, packaging, equipment, movements, services and parties." }, { "id": "SRC-008", "title": "Recommendation No. 16: UN/LOCODE", "organization": "UN/CEFACT", "url": "https://unlocode.unece.org/recommendation16/", "version_or_date": "Fourth edition, 2020", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines unambiguous location identifiers for international trade and transport." }, { "id": "SRC-009", "title": "Recommendation No. 20: Codes for Units of Measure", "organization": "UN/CEFACT", "url": "https://unece.org/code-list-recommendations", "version_or_date": "Recommendation 20 and current code lists accessed 2026-09-06", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines coded units for mass, length, volume, time and other trade quantities." }, { "id": "SRC-010", "title": "Recommendation No. 21: Codes for Types of Cargo, Packages and Packaging Materials", "organization": "UN/CEFACT", "url": "https://unece.org/fileadmin/DAM/cefact/recommendations/rec21/rec21rev1_ecetrd195e.pdf", "version_or_date": "Recommendation 21, Revision 1", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines cargo, package and packaging-material classifiers and their boundary from transport equipment." }, { "id": "SRC-011", "title": "WCO Data Model", "organization": "World Customs Organization", "url": "https://www.wcoomd.org/DataModel", "version_or_date": "WCO Data Model 4.1.0 context, accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Provides the cross-border regulatory data framework for customs and other border agencies." }, { "id": "SRC-012", "title": "Guidance on the use of Main Class Levels", "organization": "World Customs Organization", "url": "https://wiki-datamodel.wcoomd.org/en/technical-guide/guidance-on-using-Main-Class-Levels", "version_or_date": "Guidance accessed 2026-09-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Distinguishes GoodsShipment as what is shipped from Consignment as how goods are shipped under a transport contract." }, { "id": "SRC-013", "title": "Universal Business Language Version 2.4", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html", "version_or_date": "OASIS Standard, 20 June 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines shipment and consignment many-to-many semantics, freight documents, events, items and transport structures." }, { "id": "SRC-014", "title": "EPCIS Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/epcis/2.0.1/", "version_or_date": "EPCIS 2.0.1, 1 July 2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines visibility events and what, when, where, why and how observations with event and record times." }, { "id": "SRC-015", "title": "Core Business Vocabulary", "organization": "GS1", "url": "https://ref.gs1.org/standards/cbv/2.0.0/", "version_or_date": "CBV 2.0.0, June 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines controlled business steps and dispositions for shipping, receiving and logistics visibility." }, { "id": "SRC-016", "title": "ONE Record", "organization": "International Air Transport Association", "url": "https://www.iata.org/one-record", "version_or_date": "Standard overview accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines a shared air-cargo shipment record, common data model, secured API and federated data access." }, { "id": "SRC-017", "title": "ONE Record Ontology", "organization": "International Air Transport Association", "url": "https://onerecord.iata.org/ns/cargo/3.2.0", "version_or_date": "Ontology 3.2.0, modified 24 June 2025", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines air-cargo shipment, piece, waybill, booking, transport segment, ULD and related logistics objects." }, { "id": "SRC-018", "title": "Track and Trace", "organization": "Digital Container Shipping Association", "url": "https://dcsa.org/standards/track-and-trace/standard-documentation-track-and-trace", "version_or_date": "Current documentation accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines interoperable container-shipping tracking across pre-shipment, ocean and post-shipment phases." }, { "id": "SRC-019", "title": "Regulation (EU) 2020/1056 on electronic freight transport information", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX%3A32020R1056", "version_or_date": "15 July 2020", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines electronic freight-transport information exchanged with competent authorities in the EU." }, { "id": "SRC-020", "title": "ISO/IEC 15459-1:2014", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/54779.html", "version_or_date": "Edition 3, confirmed", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines unique identification of individual transport units used for physical logistical transfers." }, { "id": "SRC-021", "title": "RFC 3339: Date and Time on the Internet", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:40:00Z", "relevance": "Defines timestamps with seconds and explicit offsets." }, { "id": "SRC-022", "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-06T20:40:00Z", "relevance": "Defines attribution, derivation, revision, invalidation and delegation." }, { "id": "SRC-023", "title": "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-06T20:40:00Z", "relevance": "Defines quality measurements, annotations, policies and provenance." }, { "id": "SRC-024", "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-06T20:40:00Z", "relevance": "Defines permissions, prohibitions, duties and constraints for governed logistics data." } ], "structure": { "bundles": [ { "id": "identity-kind-and-contract-boundary", "name": "Identity, kind and contract boundary", "description": "Groups the governed Route / Itinerary concern for identity, kind and contract boundary.", "rationale": "Distinguish the trade view of what is shipped from the transport-contract view of how it moves.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-022", "SRC-004", "SRC-007" ], "layers": [ { "id": "identity-version-and-semantic-kind", "name": "Identity, version and semantic kind", "description": "Groups Route / Itinerary context for identity, version and semantic kind without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-022" ], "findings": [ { "id": "shipment-or-consignment-identity-namespace-version-and-kind", "name": "Shipment or consignment identity, namespace, version and mandatory kind", "description": "Records shipment or consignment identity, namespace, version and mandatory kind as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-022" ], "questions": [ { "id": "shipment-or-consignment-identity-namespace-version-and-kind-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish shipment or consignment identity, namespace, version and mandatory kind?", "kind": "identity", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "shipment-or-consignment-identity-namespace-version-and-kind-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access shipment or consignment identity, namespace, version and mandatory kind, and under which contract or authority?", "kind": "authority", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "shipment-or-consignment-identity-namespace-version-and-kind-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify shipment or consignment identity, namespace, version and mandatory kind?", "kind": "security", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "shipment-or-consignment-identity-namespace-version-and-kind-data", "name": "Shipment or consignment identity, namespace, version and mandatory kind data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for shipment or consignment identity, namespace, version and mandatory kind.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-022" ] } ], "artifacts": [ { "id": "shipment-or-consignment-identity-namespace-version-and-kind-artifact", "name": "Shipment or consignment identity, namespace, version and mandatory kind evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting shipment or consignment identity, namespace, version and mandatory kind.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-022" ] } ], "inline_only_rationale": null }, { "id": "commercial-carrier-customs-and-party-assigned-identifiers", "name": "Commercial, carrier, customs and party-assigned identifiers", "description": "Records commercial, carrier, customs and party-assigned identifiers as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-022" ], "questions": [ { "id": "commercial-carrier-customs-and-party-assigned-identifiers-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish commercial, carrier, customs and party-assigned identifiers?", "kind": "classification", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "commercial-carrier-customs-and-party-assigned-identifiers-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access commercial, carrier, customs and party-assigned identifiers, and under which contract or authority?", "kind": "requirement", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "commercial-carrier-customs-and-party-assigned-identifiers-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify commercial, carrier, customs and party-assigned identifiers?", "kind": "privacy", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "commercial-carrier-customs-and-party-assigned-identifiers-data", "name": "Commercial, carrier, customs and party-assigned identifiers data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for commercial, carrier, customs and party-assigned identifiers.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-022" ] } ], "artifacts": [ { "id": "commercial-carrier-customs-and-party-assigned-identifiers-artifact", "name": "Commercial, carrier, customs and party-assigned identifiers evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting commercial, carrier, customs and party-assigned identifiers.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-022" ] } ], "inline_only_rationale": null } ] }, { "id": "trade-transport-parties-and-allocation", "name": "Trade, transport, parties and allocation", "description": "Groups Route / Itinerary context for trade, transport, parties and allocation without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ], "findings": [ { "id": "seller-buyer-shipper-recipient-consignor-and-consignee-roles", "name": "Seller, buyer, shipper, recipient, consignor and consignee roles", "description": "Records seller, buyer, shipper, recipient, consignor and consignee roles as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ], "questions": [ { "id": "seller-buyer-shipper-recipient-consignor-and-consignee-roles-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish seller, buyer, shipper, recipient, consignor and consignee roles?", "kind": "relationship", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "seller-buyer-shipper-recipient-consignor-and-consignee-roles-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access seller, buyer, shipper, recipient, consignor and consignee roles, and under which contract or authority?", "kind": "constraint", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "seller-buyer-shipper-recipient-consignor-and-consignee-roles-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify seller, buyer, shipper, recipient, consignor and consignee roles?", "kind": "retention", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "seller-buyer-shipper-recipient-consignor-and-consignee-roles-data", "name": "Seller, buyer, shipper, recipient, consignor and consignee roles data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for seller, buyer, shipper, recipient, consignor and consignee roles.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "seller-buyer-shipper-recipient-consignor-and-consignee-roles-artifact", "name": "Seller, buyer, shipper, recipient, consignor and consignee roles evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting seller, buyer, shipper, recipient, consignor and consignee roles.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "shipment-consignment-many-to-many-allocation-and-contract-basis", "name": "Shipment-consignment many-to-many allocation and contract basis", "description": "Records shipment-consignment many-to-many allocation and contract basis as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ], "questions": [ { "id": "shipment-consignment-many-to-many-allocation-and-contract-basis-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish shipment-consignment many-to-many allocation and contract basis?", "kind": "composition", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "shipment-consignment-many-to-many-allocation-and-contract-basis-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access shipment-consignment many-to-many allocation and contract basis, and under which contract or authority?", "kind": "process", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "shipment-consignment-many-to-many-allocation-and-contract-basis-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify shipment-consignment many-to-many allocation and contract basis?", "kind": "access", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "shipment-consignment-many-to-many-allocation-and-contract-basis-data", "name": "Shipment-consignment many-to-many allocation and contract basis data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for shipment-consignment many-to-many allocation and contract basis.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "shipment-consignment-many-to-many-allocation-and-contract-basis-artifact", "name": "Shipment-consignment many-to-many allocation and contract basis evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting shipment-consignment many-to-many allocation and contract basis.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "items-packages-and-logistics-composition", "name": "Items, packages and logistics composition", "description": "Groups the governed Route / Itinerary concern for items, packages and logistics composition.", "rationale": "Describe goods groupings and transport membership without importing item or handling-unit lifecycles.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017", "SRC-005", "SRC-010", "SRC-014", "SRC-020" ], "layers": [ { "id": "goods-consignment-items-and-quantities", "name": "Goods, consignment items and quantities", "description": "Groups Route / Itinerary context for goods, consignment items and quantities without importing neighboring master lifecycles.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ], "findings": [ { "id": "trade-item-goods-item-consignment-item-piece-and-line-binding", "name": "Trade item, goods item, consignment item, piece and line binding", "description": "Records trade item, goods item, consignment item, piece and line binding as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ], "questions": [ { "id": "trade-item-goods-item-consignment-item-piece-and-line-binding-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish trade item, goods item, consignment item, piece and line binding?", "kind": "composition", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "trade-item-goods-item-consignment-item-piece-and-line-binding-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access trade item, goods item, consignment item, piece and line binding, and under which contract or authority?", "kind": "event", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "trade-item-goods-item-consignment-item-piece-and-line-binding-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify trade item, goods item, consignment item, piece and line binding?", "kind": "exception", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "trade-item-goods-item-consignment-item-piece-and-line-binding-data", "name": "Trade item, goods item, consignment item, piece and line binding data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for trade item, goods item, consignment item, piece and line binding.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "artifacts": [ { "id": "trade-item-goods-item-consignment-item-piece-and-line-binding-artifact", "name": "Trade item, goods item, consignment item, piece and line binding evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting trade item, goods item, consignment item, piece and line binding.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "inline_only_rationale": null }, { "id": "commodity-classification-description-quantity-value-and-origin", "name": "Commodity classification, description, quantity, value and origin", "description": "Records commodity classification, description, quantity, value and origin as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ], "questions": [ { "id": "commodity-classification-description-quantity-value-and-origin-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish commodity classification, description, quantity, value and origin?", "kind": "classification", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "commodity-classification-description-quantity-value-and-origin-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access commodity classification, description, quantity, value and origin, and under which contract or authority?", "kind": "measurement", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "commodity-classification-description-quantity-value-and-origin-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify commodity classification, description, quantity, value and origin?", "kind": "interoperability", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "commodity-classification-description-quantity-value-and-origin-data", "name": "Commodity classification, description, quantity, value and origin data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for commodity classification, description, quantity, value and origin.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "artifacts": [ { "id": "commodity-classification-description-quantity-value-and-origin-artifact", "name": "Commodity classification, description, quantity, value and origin evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting commodity classification, description, quantity, value and origin.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "id": "package-handling-unit-and-equipment-membership", "name": "Package, handling unit and equipment membership", "description": "Groups Route / Itinerary context for package, handling unit and equipment membership without importing neighboring master lifecycles.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-010", "SRC-013", "SRC-014", "SRC-017", "SRC-020" ], "findings": [ { "id": "package-piece-handling-unit-pallet-uld-container-and-equipment-reference", "name": "Package, piece, handling unit, pallet, ULD, container and equipment reference", "description": "Records package, piece, handling unit, pallet, uld, container and equipment reference as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-010", "SRC-013", "SRC-014", "SRC-017", "SRC-020" ], "questions": [ { "id": "package-piece-handling-unit-pallet-uld-container-and-equipment-reference-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish package, piece, handling unit, pallet, uld, container and equipment reference?", "kind": "relationship", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "package-piece-handling-unit-pallet-uld-container-and-equipment-reference-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access package, piece, handling unit, pallet, uld, container and equipment reference, and under which contract or authority?", "kind": "evidence", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "package-piece-handling-unit-pallet-uld-container-and-equipment-reference-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify package, piece, handling unit, pallet, uld, container and equipment reference?", "kind": "decision", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "package-piece-handling-unit-pallet-uld-container-and-equipment-reference-data", "name": "Package, piece, handling unit, pallet, ULD, container and equipment reference data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for package, piece, handling unit, pallet, uld, container and equipment reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-010", "SRC-013", "SRC-014", "SRC-017", "SRC-020" ] } ], "artifacts": [ { "id": "package-piece-handling-unit-pallet-uld-container-and-equipment-reference-artifact", "name": "Package, piece, handling unit, pallet, ULD, container and equipment reference evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting package, piece, handling unit, pallet, uld, container and equipment reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-010", "SRC-013", "SRC-014", "SRC-017", "SRC-020" ] } ], "inline_only_rationale": null }, { "id": "aggregation-loading-nesting-marks-seals-and-membership-interval", "name": "Aggregation, loading, nesting, marks, seals and membership interval", "description": "Records aggregation, loading, nesting, marks, seals and membership interval as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-010", "SRC-013", "SRC-014", "SRC-017", "SRC-020" ], "questions": [ { "id": "aggregation-loading-nesting-marks-seals-and-membership-interval-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish aggregation, loading, nesting, marks, seals and membership interval?", "kind": "composition", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "aggregation-loading-nesting-marks-seals-and-membership-interval-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access aggregation, loading, nesting, marks, seals and membership interval, and under which contract or authority?", "kind": "quality", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "aggregation-loading-nesting-marks-seals-and-membership-interval-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify aggregation, loading, nesting, marks, seals and membership interval?", "kind": "identity", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "aggregation-loading-nesting-marks-seals-and-membership-interval-data", "name": "Aggregation, loading, nesting, marks, seals and membership interval data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for aggregation, loading, nesting, marks, seals and membership interval.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-010", "SRC-013", "SRC-014", "SRC-017", "SRC-020" ] } ], "artifacts": [ { "id": "aggregation-loading-nesting-marks-seals-and-membership-interval-artifact", "name": "Aggregation, loading, nesting, marks, seals and membership interval evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting aggregation, loading, nesting, marks, seals and membership interval.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-010", "SRC-013", "SRC-014", "SRC-017", "SRC-020" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "locations-movement-and-service-bindings", "name": "Locations, movement and service bindings", "description": "Groups the governed Route / Itinerary concern for locations, movement and service bindings.", "rationale": "Bind logistics endpoints and planned or actual transport references while movement masters retain execution authority.", "source_refs": [ "SRC-002", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-018", "SRC-001", "SRC-005", "SRC-016", "SRC-017" ], "layers": [ { "id": "origin-destination-and-logistics-locations", "name": "Origin, destination and logistics locations", "description": "Groups Route / Itinerary context for origin, destination and logistics locations without importing neighboring master lifecycles.", "source_refs": [ "SRC-002", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-018" ], "findings": [ { "id": "ship-from-ship-to-receipt-acceptance-loading-unloading-and-delivery-location", "name": "Ship-from, ship-to, receipt, acceptance, loading, unloading and delivery location", "description": "Records ship-from, ship-to, receipt, acceptance, loading, unloading and delivery location as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-002", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-018" ], "questions": [ { "id": "ship-from-ship-to-receipt-acceptance-loading-unloading-and-delivery-location-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish ship-from, ship-to, receipt, acceptance, loading, unloading and delivery location?", "kind": "spatial", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "ship-from-ship-to-receipt-acceptance-loading-unloading-and-delivery-location-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access ship-from, ship-to, receipt, acceptance, loading, unloading and delivery location, and under which contract or authority?", "kind": "validation", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "ship-from-ship-to-receipt-acceptance-loading-unloading-and-delivery-location-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify ship-from, ship-to, receipt, acceptance, loading, unloading and delivery location?", "kind": "classification", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "ship-from-ship-to-receipt-acceptance-loading-unloading-and-delivery-location-data", "name": "Ship-from, ship-to, receipt, acceptance, loading, unloading and delivery location data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for ship-from, ship-to, receipt, acceptance, loading, unloading and delivery location.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-018" ] } ], "artifacts": [ { "id": "ship-from-ship-to-receipt-acceptance-loading-unloading-and-delivery-location-artifact", "name": "Ship-from, ship-to, receipt, acceptance, loading, unloading and delivery location evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting ship-from, ship-to, receipt, acceptance, loading, unloading and delivery location.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-002", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "port-terminal-border-transshipment-storage-and-location-function", "name": "Port, terminal, border, transshipment, storage and location function", "description": "Records port, terminal, border, transshipment, storage and location function as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-002", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-018" ], "questions": [ { "id": "port-terminal-border-transshipment-storage-and-location-function-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish port, terminal, border, transshipment, storage and location function?", "kind": "classification", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "port-terminal-border-transshipment-storage-and-location-function-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access port, terminal, border, transshipment, storage and location function, and under which contract or authority?", "kind": "security", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "port-terminal-border-transshipment-storage-and-location-function-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify port, terminal, border, transshipment, storage and location function?", "kind": "composition", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "port-terminal-border-transshipment-storage-and-location-function-data", "name": "Port, terminal, border, transshipment, storage and location function data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for port, terminal, border, transshipment, storage and location function.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-018" ] } ], "artifacts": [ { "id": "port-terminal-border-transshipment-storage-and-location-function-artifact", "name": "Port, terminal, border, transshipment, storage and location function evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting port, terminal, border, transshipment, storage and location function.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-002", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-018" ] } ], "inline_only_rationale": null } ] }, { "id": "transport-plan-service-and-parties", "name": "Transport plan, service and parties", "description": "Groups Route / Itinerary context for transport plan, service and parties without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-018" ], "findings": [ { "id": "mode-carrier-forwarder-service-booking-route-journey-and-leg-reference", "name": "Mode, carrier, forwarder, service, booking, route, journey and leg reference", "description": "Records mode, carrier, forwarder, service, booking, route, journey and leg reference as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "mode-carrier-forwarder-service-booking-route-journey-and-leg-reference-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish mode, carrier, forwarder, service, booking, route, journey and leg reference?", "kind": "relationship", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "mode-carrier-forwarder-service-booking-route-journey-and-leg-reference-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access mode, carrier, forwarder, service, booking, route, journey and leg reference, and under which contract or authority?", "kind": "privacy", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "mode-carrier-forwarder-service-booking-route-journey-and-leg-reference-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify mode, carrier, forwarder, service, booking, route, journey and leg reference?", "kind": "relationship", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "mode-carrier-forwarder-service-booking-route-journey-and-leg-reference-data", "name": "Mode, carrier, forwarder, service, booking, route, journey and leg reference data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for mode, carrier, forwarder, service, booking, route, journey and leg reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "mode-carrier-forwarder-service-booking-route-journey-and-leg-reference-artifact", "name": "Mode, carrier, forwarder, service, booking, route, journey and leg reference evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting mode, carrier, forwarder, service, booking, route, journey and leg reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "pickup-handover-transshipment-delivery-sequence-and-connection", "name": "Pickup, handover, transshipment, delivery sequence and connection", "description": "Records pickup, handover, transshipment, delivery sequence and connection as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "pickup-handover-transshipment-delivery-sequence-and-connection-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish pickup, handover, transshipment, delivery sequence and connection?", "kind": "process", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "pickup-handover-transshipment-delivery-sequence-and-connection-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access pickup, handover, transshipment, delivery sequence and connection, and under which contract or authority?", "kind": "retention", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "pickup-handover-transshipment-delivery-sequence-and-connection-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify pickup, handover, transshipment, delivery sequence and connection?", "kind": "state", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "pickup-handover-transshipment-delivery-sequence-and-connection-data", "name": "Pickup, handover, transshipment, delivery sequence and connection data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for pickup, handover, transshipment, delivery sequence and connection.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "pickup-handover-transshipment-delivery-sequence-and-connection-artifact", "name": "Pickup, handover, transshipment, delivery sequence and connection evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting pickup, handover, transshipment, delivery sequence and connection.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "requirements-milestones-and-condition", "name": "Requirements, milestones and condition", "description": "Groups the governed Route / Itinerary concern for requirements, milestones and condition.", "rationale": "Keep requested service, regulatory requirements and observed status independently attributable.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007", "SRC-010", "SRC-011", "SRC-013", "SRC-016", "SRC-019", "SRC-006", "SRC-014", "SRC-015", "SRC-018", "SRC-021", "SRC-022" ], "layers": [ { "id": "service-handling-and-compliance-requirements", "name": "Service, handling and compliance requirements", "description": "Groups Route / Itinerary context for service, handling and compliance requirements without importing neighboring master lifecycles.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007", "SRC-010", "SRC-011", "SRC-013", "SRC-016", "SRC-019" ], "findings": [ { "id": "delivery-term-service-level-handling-instruction-and-time-window", "name": "Delivery term, service level, handling instruction and time window", "description": "Records delivery term, service level, handling instruction and time window as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007", "SRC-010", "SRC-011", "SRC-013", "SRC-016", "SRC-019" ], "questions": [ { "id": "delivery-term-service-level-handling-instruction-and-time-window-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish delivery term, service level, handling instruction and time window?", "kind": "constraint", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "delivery-term-service-level-handling-instruction-and-time-window-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access delivery term, service level, handling instruction and time window, and under which contract or authority?", "kind": "access", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "delivery-term-service-level-handling-instruction-and-time-window-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify delivery term, service level, handling instruction and time window?", "kind": "lifecycle", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "delivery-term-service-level-handling-instruction-and-time-window-data", "name": "Delivery term, service level, handling instruction and time window data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for delivery term, service level, handling instruction and time window.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005", "SRC-007", "SRC-010", "SRC-011", "SRC-013", "SRC-016", "SRC-019" ] } ], "artifacts": [ { "id": "delivery-term-service-level-handling-instruction-and-time-window-artifact", "name": "Delivery term, service level, handling instruction and time window evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting delivery term, service level, handling instruction and time window.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007", "SRC-010", "SRC-011", "SRC-013", "SRC-016", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "dangerous-goods-temperature-security-customs-and-regulatory-requirement", "name": "Dangerous-goods, temperature, security, customs and regulatory requirement", "description": "Records dangerous-goods, temperature, security, customs and regulatory requirement as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007", "SRC-010", "SRC-011", "SRC-013", "SRC-016", "SRC-019" ], "questions": [ { "id": "dangerous-goods-temperature-security-customs-and-regulatory-requirement-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish dangerous-goods, temperature, security, customs and regulatory requirement?", "kind": "requirement", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "dangerous-goods-temperature-security-customs-and-regulatory-requirement-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access dangerous-goods, temperature, security, customs and regulatory requirement, and under which contract or authority?", "kind": "exception", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "dangerous-goods-temperature-security-customs-and-regulatory-requirement-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify dangerous-goods, temperature, security, customs and regulatory requirement?", "kind": "temporal", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "dangerous-goods-temperature-security-customs-and-regulatory-requirement-data", "name": "Dangerous-goods, temperature, security, customs and regulatory requirement data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for dangerous-goods, temperature, security, customs and regulatory requirement.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005", "SRC-007", "SRC-010", "SRC-011", "SRC-013", "SRC-016", "SRC-019" ] } ], "artifacts": [ { "id": "dangerous-goods-temperature-security-customs-and-regulatory-requirement-artifact", "name": "Dangerous-goods, temperature, security, customs and regulatory requirement evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting dangerous-goods, temperature, security, customs and regulatory requirement.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007", "SRC-010", "SRC-011", "SRC-013", "SRC-016", "SRC-019" ] } ], "inline_only_rationale": null } ] }, { "id": "milestone-time-status-and-condition", "name": "Milestone time, status and condition", "description": "Groups Route / Itinerary context for milestone time, status and condition without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-006", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-021", "SRC-022" ], "findings": [ { "id": "planned-estimated-predicted-observed-and-actual-milestone-time", "name": "Planned, estimated, predicted, observed and actual milestone time", "description": "Records planned, estimated, predicted, observed and actual milestone time as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-005", "SRC-006", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-021", "SRC-022" ], "questions": [ { "id": "planned-estimated-predicted-observed-and-actual-milestone-time-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish planned, estimated, predicted, observed and actual milestone time?", "kind": "temporal", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "planned-estimated-predicted-observed-and-actual-milestone-time-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access planned, estimated, predicted, observed and actual milestone time, and under which contract or authority?", "kind": "interoperability", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "planned-estimated-predicted-observed-and-actual-milestone-time-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify planned, estimated, predicted, observed and actual milestone time?", "kind": "spatial", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "planned-estimated-predicted-observed-and-actual-milestone-time-data", "name": "Planned, estimated, predicted, observed and actual milestone time data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for planned, estimated, predicted, observed and actual milestone time.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-021", "SRC-022" ] } ], "artifacts": [ { "id": "planned-estimated-predicted-observed-and-actual-milestone-time-artifact", "name": "Planned, estimated, predicted, observed and actual milestone time evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting planned, estimated, predicted, observed and actual milestone time.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-021", "SRC-022" ] } ], "inline_only_rationale": null }, { "id": "booked-accepted-picked-up-in-transit-arrived-delivered-returned-and-cancelled-status", "name": "Booked, accepted, picked-up, in-transit, arrived, delivered, returned and cancelled status", "description": "Records booked, accepted, picked-up, in-transit, arrived, delivered, returned and cancelled status as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-005", "SRC-006", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-021", "SRC-022" ], "questions": [ { "id": "booked-accepted-picked-up-in-transit-arrived-delivered-returned-and-cancelled-status-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish booked, accepted, picked-up, in-transit, arrived, delivered, returned and cancelled status?", "kind": "lifecycle", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "booked-accepted-picked-up-in-transit-arrived-delivered-returned-and-cancelled-status-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access booked, accepted, picked-up, in-transit, arrived, delivered, returned and cancelled status, and under which contract or authority?", "kind": "decision", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "booked-accepted-picked-up-in-transit-arrived-delivered-returned-and-cancelled-status-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify booked, accepted, picked-up, in-transit, arrived, delivered, returned and cancelled status?", "kind": "provenance", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "booked-accepted-picked-up-in-transit-arrived-delivered-returned-and-cancelled-status-data", "name": "Booked, accepted, picked-up, in-transit, arrived, delivered, returned and cancelled status data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for booked, accepted, picked-up, in-transit, arrived, delivered, returned and cancelled status.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-021", "SRC-022" ] } ], "artifacts": [ { "id": "booked-accepted-picked-up-in-transit-arrived-delivered-returned-and-cancelled-status-artifact", "name": "Booked, accepted, picked-up, in-transit, arrived, delivered, returned and cancelled status evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting booked, accepted, picked-up, in-transit, arrived, delivered, returned and cancelled status.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-021", "SRC-022" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "responsibility-exceptions-and-measures", "name": "Responsibility, exceptions and measures", "description": "Groups the governed Route / Itinerary concern for responsibility, exceptions and measures.", "rationale": "Represent shipment-scoped responsibility, exceptions and qualified measures without replacing trace, claim or inventory masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-022", "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-017", "SRC-023" ], "layers": [ { "id": "custody-responsibility-and-exceptions", "name": "Custody, responsibility and exceptions", "description": "Groups Route / Itinerary context for custody, responsibility and exceptions without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-022" ], "findings": [ { "id": "custody-possession-control-risk-responsibility-and-handover-binding", "name": "Custody, possession, control, risk, responsibility and handover binding", "description": "Records custody, possession, control, risk, responsibility and handover binding as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-005", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-022" ], "questions": [ { "id": "custody-possession-control-risk-responsibility-and-handover-binding-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish custody, possession, control, risk, responsibility and handover binding?", "kind": "ownership", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "custody-possession-control-risk-responsibility-and-handover-binding-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access custody, possession, control, risk, responsibility and handover binding, and under which contract or authority?", "kind": "identity", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "custody-possession-control-risk-responsibility-and-handover-binding-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify custody, possession, control, risk, responsibility and handover binding?", "kind": "ownership", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "custody-possession-control-risk-responsibility-and-handover-binding-data", "name": "Custody, possession, control, risk, responsibility and handover binding data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for custody, possession, control, risk, responsibility and handover binding.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-022" ] } ], "artifacts": [ { "id": "custody-possession-control-risk-responsibility-and-handover-binding-artifact", "name": "Custody, possession, control, risk, responsibility and handover binding evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting custody, possession, control, risk, responsibility and handover binding.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-022" ] } ], "inline_only_rationale": null }, { "id": "shortage-excess-damage-loss-delay-refusal-failed-delivery-and-claim-reference", "name": "Shortage, excess, damage, loss, delay, refusal, failed delivery and claim reference", "description": "Records shortage, excess, damage, loss, delay, refusal, failed delivery and claim reference as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-005", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-022" ], "questions": [ { "id": "shortage-excess-damage-loss-delay-refusal-failed-delivery-and-claim-reference-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish shortage, excess, damage, loss, delay, refusal, failed delivery and claim reference?", "kind": "exception", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "shortage-excess-damage-loss-delay-refusal-failed-delivery-and-claim-reference-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access shortage, excess, damage, loss, delay, refusal, failed delivery and claim reference, and under which contract or authority?", "kind": "classification", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "shortage-excess-damage-loss-delay-refusal-failed-delivery-and-claim-reference-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify shortage, excess, damage, loss, delay, refusal, failed delivery and claim reference?", "kind": "authority", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "shortage-excess-damage-loss-delay-refusal-failed-delivery-and-claim-reference-data", "name": "Shortage, excess, damage, loss, delay, refusal, failed delivery and claim reference data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for shortage, excess, damage, loss, delay, refusal, failed delivery and claim reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-022" ] } ], "artifacts": [ { "id": "shortage-excess-damage-loss-delay-refusal-failed-delivery-and-claim-reference-artifact", "name": "Shortage, excess, damage, loss, delay, refusal, failed delivery and claim reference evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting shortage, excess, damage, loss, delay, refusal, failed delivery and claim reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-022" ] } ], "inline_only_rationale": null } ] }, { "id": "quantity-dimensions-weight-volume-and-value", "name": "Quantity, dimensions, weight, volume and value", "description": "Groups Route / Itinerary context for quantity, dimensions, weight, volume and value without importing neighboring master lifecycles.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-017", "SRC-023" ], "findings": [ { "id": "package-piece-item-count-and-dimensional-measures", "name": "Package, piece and item count and dimensional measures", "description": "Records package, piece and item count and dimensional measures as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-017", "SRC-023" ], "questions": [ { "id": "package-piece-item-count-and-dimensional-measures-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish package, piece and item count and dimensional measures?", "kind": "measurement", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "package-piece-item-count-and-dimensional-measures-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access package, piece and item count and dimensional measures, and under which contract or authority?", "kind": "composition", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "package-piece-item-count-and-dimensional-measures-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify package, piece and item count and dimensional measures?", "kind": "requirement", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "package-piece-item-count-and-dimensional-measures-data", "name": "Package, piece and item count and dimensional measures data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for package, piece and item count and dimensional measures.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-017", "SRC-023" ] } ], "artifacts": [ { "id": "package-piece-item-count-and-dimensional-measures-artifact", "name": "Package, piece and item count and dimensional measures evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting package, piece and item count and dimensional measures.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-017", "SRC-023" ] } ], "inline_only_rationale": null }, { "id": "gross-net-chargeable-weight-volume-declared-value-and-tolerance", "name": "Gross, net and chargeable weight, volume, declared value and tolerance", "description": "Records gross, net and chargeable weight, volume, declared value and tolerance as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-017", "SRC-023" ], "questions": [ { "id": "gross-net-chargeable-weight-volume-declared-value-and-tolerance-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish gross, net and chargeable weight, volume, declared value and tolerance?", "kind": "measurement", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "gross-net-chargeable-weight-volume-declared-value-and-tolerance-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access gross, net and chargeable weight, volume, declared value and tolerance, and under which contract or authority?", "kind": "relationship", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "gross-net-chargeable-weight-volume-declared-value-and-tolerance-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify gross, net and chargeable weight, volume, declared value and tolerance?", "kind": "constraint", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "gross-net-chargeable-weight-volume-declared-value-and-tolerance-data", "name": "Gross, net and chargeable weight, volume, declared value and tolerance data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for gross, net and chargeable weight, volume, declared value and tolerance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-017", "SRC-023" ] } ], "artifacts": [ { "id": "gross-net-chargeable-weight-volume-declared-value-and-tolerance-artifact", "name": "Gross, net and chargeable weight, volume, declared value and tolerance evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting gross, net and chargeable weight, volume, declared value and tolerance.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-017", "SRC-023" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "documents-provenance-access-and-interoperability", "name": "Documents, provenance, access and interoperability", "description": "Groups the governed Route / Itinerary concern for documents, provenance, access and interoperability.", "rationale": "Make assertions traceable and safely projectable across trade, customs, modal and visibility standards.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-019", "SRC-022", "SRC-023", "SRC-001", "SRC-002", "SRC-014", "SRC-015", "SRC-018", "SRC-020", "SRC-021", "SRC-024" ], "layers": [ { "id": "documents-evidence-and-correction", "name": "Documents, evidence and correction", "description": "Groups Route / Itinerary context for documents, evidence and correction without importing neighboring master lifecycles.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-019", "SRC-022", "SRC-023" ], "findings": [ { "id": "shipping-instruction-packing-list-waybill-bill-of-lading-declaration-and-certificate-reference", "name": "Shipping instruction, packing list, waybill, bill of lading, declaration and certificate reference", "description": "Records shipping instruction, packing list, waybill, bill of lading, declaration and certificate reference as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-019", "SRC-022", "SRC-023" ], "questions": [ { "id": "shipping-instruction-packing-list-waybill-bill-of-lading-declaration-and-certificate-reference-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish shipping instruction, packing list, waybill, bill of lading, declaration and certificate reference?", "kind": "evidence", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "shipping-instruction-packing-list-waybill-bill-of-lading-declaration-and-certificate-reference-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access shipping instruction, packing list, waybill, bill of lading, declaration and certificate reference, and under which contract or authority?", "kind": "state", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "shipping-instruction-packing-list-waybill-bill-of-lading-declaration-and-certificate-reference-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify shipping instruction, packing list, waybill, bill of lading, declaration and certificate reference?", "kind": "process", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "shipping-instruction-packing-list-waybill-bill-of-lading-declaration-and-certificate-reference-data", "name": "Shipping instruction, packing list, waybill, bill of lading, declaration and certificate reference data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for shipping instruction, packing list, waybill, bill of lading, declaration and certificate reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-019", "SRC-022", "SRC-023" ] } ], "artifacts": [ { "id": "shipping-instruction-packing-list-waybill-bill-of-lading-declaration-and-certificate-reference-artifact", "name": "Shipping instruction, packing list, waybill, bill of lading, declaration and certificate reference evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting shipping instruction, packing list, waybill, bill of lading, declaration and certificate reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-019", "SRC-022", "SRC-023" ] } ], "inline_only_rationale": null }, { "id": "source-assertion-quality-conflict-correction-invalidation-and-successor", "name": "Source, assertion, quality, conflict, correction, invalidation and successor", "description": "Records source, assertion, quality, conflict, correction, invalidation and successor as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-019", "SRC-022", "SRC-023" ], "questions": [ { "id": "source-assertion-quality-conflict-correction-invalidation-and-successor-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish source, assertion, quality, conflict, correction, invalidation and successor?", "kind": "provenance", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "source-assertion-quality-conflict-correction-invalidation-and-successor-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access source, assertion, quality, conflict, correction, invalidation and successor, and under which contract or authority?", "kind": "lifecycle", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "source-assertion-quality-conflict-correction-invalidation-and-successor-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify source, assertion, quality, conflict, correction, invalidation and successor?", "kind": "event", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "source-assertion-quality-conflict-correction-invalidation-and-successor-data", "name": "Source, assertion, quality, conflict, correction, invalidation and successor data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for source, assertion, quality, conflict, correction, invalidation and successor.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-019", "SRC-022", "SRC-023" ] } ], "artifacts": [ { "id": "source-assertion-quality-conflict-correction-invalidation-and-successor-artifact", "name": "Source, assertion, quality, conflict, correction, invalidation and successor evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting source, assertion, quality, conflict, correction, invalidation and successor.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-017", "SRC-019", "SRC-022", "SRC-023" ] } ], "inline_only_rationale": null } ] }, { "id": "access-retention-and-crosswalks", "name": "Access, retention and crosswalks", "description": "Groups Route / Itinerary context for access, retention and crosswalks without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "findings": [ { "id": "commercial-confidentiality-purpose-consent-access-retention-and-legal-hold", "name": "Commercial confidentiality, purpose, consent, access, retention and legal hold", "description": "Records commercial confidentiality, purpose, consent, access, retention and legal hold as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "commercial-confidentiality-purpose-consent-access-retention-and-legal-hold-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish commercial confidentiality, purpose, consent, access, retention and legal hold?", "kind": "access", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "commercial-confidentiality-purpose-consent-access-retention-and-legal-hold-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access commercial confidentiality, purpose, consent, access, retention and legal hold, and under which contract or authority?", "kind": "temporal", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "commercial-confidentiality-purpose-consent-access-retention-and-legal-hold-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify commercial confidentiality, purpose, consent, access, retention and legal hold?", "kind": "measurement", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "commercial-confidentiality-purpose-consent-access-retention-and-legal-hold-data", "name": "Commercial confidentiality, purpose, consent, access, retention and legal hold data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for commercial confidentiality, purpose, consent, access, retention and legal hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "commercial-confidentiality-purpose-consent-access-retention-and-legal-hold-artifact", "name": "Commercial confidentiality, purpose, consent, access, retention and legal hold evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting commercial confidentiality, purpose, consent, access, retention and legal hold.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "uncefact-wco-ubl-gs1-iata-dcsa-efti-and-provenance-crosswalk", "name": "UN/CEFACT, WCO, UBL, GS1, IATA, DCSA, eFTI and provenance crosswalk", "description": "Records un/cefact, wco, ubl, gs1, iata, dcsa, efti and provenance crosswalk as typed Shipment / Consignment context while goods, orders, handling units, inventory, movement, documents, trace, claims and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "uncefact-wco-ubl-gs1-iata-dcsa-efti-and-provenance-crosswalk-q01", "text": "Which shipment or consignment identity, mandatory kind, revision, item scope, location, time and source establish un/cefact, wco, ubl, gs1, iata, dcsa, efti and provenance crosswalk?", "kind": "interoperability", "answer_data": [ "shipment or consignment identifier, namespace, mandatory kind, revision and lifecycle state", "trade, transport, customs and carrier identifiers plus item, package and movement references", "location function, event time, observation or record time, source profile and confidence" ] }, { "id": "uncefact-wco-ubl-gs1-iata-dcsa-efti-and-provenance-crosswalk-q02", "text": "Who sells, buys, ships, consigns, carries, receives, owns, controls, asserts, reviews or may access un/cefact, wco, ubl, gs1, iata, dcsa, efti and provenance crosswalk, and under which contract or authority?", "kind": "spatial", "answer_data": [ "seller, buyer, shipper, recipient, consignor, consignee, carrier, forwarder, declarant and steward roles", "trade, transport, delivery, customs, custody, delegation, purpose, jurisdiction and access basis", "assertion owner, source system, reviewer, correction actor and disputed state" ] }, { "id": "uncefact-wco-ubl-gs1-iata-dcsa-efti-and-provenance-crosswalk-q03", "text": "Which quantities, requirements, milestones, exceptions, evidence, uncertainty and lineage qualify un/cefact, wco, ubl, gs1, iata, dcsa, efti and provenance crosswalk?", "kind": "evidence", "answer_data": [ "item, package and handling-unit composition, quantities, measures, units and tolerances", "service, handling, dangerous-goods, temperature, security, customs and regulatory requirements", "status or event reference, document snapshot, digest, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "uncefact-wco-ubl-gs1-iata-dcsa-efti-and-provenance-crosswalk-data", "name": "UN/CEFACT, WCO, UBL, GS1, IATA, DCSA, eFTI and provenance crosswalk data", "description": "Typed shipment- or consignment-scoped values and references required to answer the governed questions for un/cefact, wco, ubl, gs1, iata, dcsa, efti and provenance crosswalk.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "uncefact-wco-ubl-gs1-iata-dcsa-efti-and-provenance-crosswalk-artifact", "name": "UN/CEFACT, WCO, UBL, GS1, IATA, DCSA, eFTI and provenance crosswalk evidence manifest", "description": "Digest-addressed manifest of definitions, memberships, instructions, status assertions, measurements, documents, corrections and external records supporting un/cefact, wco, ubl, gs1, iata, dcsa, efti and provenance crosswalk.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative shipment or consignment master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-logistics-object", "name": "Register shipment or consignment", "description": "Create one governed identity with a mandatory trade-shipment, transport-consignment or combined-logistics-view kind.", "inputs": [ "kind discriminator", "party and endpoint references", "owner and source" ], "outputs": [ "object identifier", "initial revision" ], "preconditions": [ "active Dimension", "create authority" ], "effects": [ "identity, boundary and explicit unknowns are appended" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-011", "SRC-012", "SRC-013", "SRC-022" ] }, { "id": "allocate-shipment-consignment", "name": "Allocate shipment and consignment", "description": "Record many-to-many allocation of trade-shipment item quantities to transport consignments.", "inputs": [ "shipment and consignment identifiers", "item and quantity allocation", "contract basis" ], "outputs": [ "versioned allocation map" ], "preconditions": [ "both objects resolvable", "quantities and units known" ], "effects": [ "allocation is appended without merging identities" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-012", "SRC-013" ] }, { "id": "compose-items", "name": "Compose goods and consignment items", "description": "Append item, commodity, quantity, value and origin bindings without owning product masters.", "inputs": [ "object identifier", "item references", "quantities and classifiers" ], "outputs": [ "validated item composition" ], "preconditions": [ "stable external item identities" ], "effects": [ "composition and residual quantities are recorded" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-012", "SRC-013" ] }, { "id": "bind-handling-units", "name": "Bind packages and handling units", "description": "Bind pieces, packages, handling units and transport equipment with membership intervals, marks and seals.", "inputs": [ "shipment or consignment revision", "unit references", "membership action and time" ], "outputs": [ "typed membership bindings" ], "preconditions": [ "handling-unit identities resolvable" ], "effects": [ "membership is versioned without importing unit lifecycle" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-010", "SRC-013", "SRC-014", "SRC-017", "SRC-020" ] }, { "id": "bind-movement-plan", "name": "Bind locations and movement plan", "description": "Bind logistics locations, service, booking, route, journey, leg and planned milestone references.", "inputs": [ "object revision", "location and movement references", "planned clocks" ], "outputs": [ "movement-plan binding" ], "preconditions": [ "external place and movement identities resolvable" ], "effects": [ "plan remains distinct from actual movement" ], "source_refs": [ "SRC-005", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-016", "SRC-018" ] }, { "id": "apply-requirements", "name": "Apply service and compliance requirements", "description": "Record service level, handling, dangerous-goods, temperature, security, customs and regulatory requirements.", "inputs": [ "object revision", "requirement set", "authority and jurisdiction" ], "outputs": [ "typed requirement profile" ], "preconditions": [ "classifier versions and units known" ], "effects": [ "requested, accepted, violated and waived requirements remain distinguishable" ], "source_refs": [ "SRC-002", "SRC-005", "SRC-007", "SRC-010", "SRC-011", "SRC-013", "SRC-016", "SRC-019" ] }, { "id": "record-milestone", "name": "Record milestone assertion", "description": "Append source-qualified planned, estimated, predicted, observed or actual milestone assertions.", "inputs": [ "object identifier", "milestone assertion", "source and clocks" ], "outputs": [ "immutable milestone assertion" ], "preconditions": [ "event kind and source known" ], "effects": [ "evidence is appended without overwriting plans or trace masters" ], "source_refs": [ "SRC-005", "SRC-013", "SRC-014", "SRC-015", "SRC-018", "SRC-021", "SRC-022" ] }, { "id": "record-exception", "name": "Record exception and outcome", "description": "Register shortage, excess, damage, loss, delay, refusal, failed delivery, return or claim reference.", "inputs": [ "object revision", "exception evidence", "responsible assertion" ], "outputs": [ "exception record", "successor or claim reference" ], "preconditions": [ "affected scope known" ], "effects": [ "exception and response lineage are appended" ], "source_refs": [ "SRC-005", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-018", "SRC-022" ] }, { "id": "reconcile-measures-documents", "name": "Reconcile measures and documents", "description": "Compare item counts, weights, volumes, values, instructions, transport documents and regulatory assertions.", "inputs": [ "object revision", "measurement and document assertions", "tolerance and precedence policy" ], "outputs": [ "reconciliation result", "conflict set" ], "preconditions": [ "units, sources and versions known" ], "effects": [ "differences and corrections remain visible" ], "source_refs": [ "SRC-007", "SRC-009", "SRC-011", "SRC-013", "SRC-017", "SRC-022", "SRC-023" ] }, { "id": "project-logistics-view", "name": "Project shipment or consignment", "description": "Produce minimum-necessary standards-aligned trade, transport, customs, visibility or modal views.", "inputs": [ "object revision", "target profile", "access purpose" ], "outputs": [ "versioned projection", "semantic-loss declaration" ], "preconditions": [ "authorized recipient", "pinned target version" ], "effects": [ "projection is logged and source identity is preserved" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-022", "SRC-023", "SRC-024" ] } ], "composition": [ { "target": "WM-FLW-004 Goods Movement / Logistics", "relation": "REFERENCE", "purpose": "Resolve broader logistics flow context while the candidate parent relation remains under joint boundary review.", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] }, { "target": "WM-OBJ-021 Handling Unit / Logistics Container", "relation": "COMPOSE", "purpose": "Represent typed membership and loading without importing handling-unit identity or lifecycle.", "required": false, "source_refs": [ "SRC-005", "SRC-007", "SRC-010", "SRC-013", "SRC-014", "SRC-017", "SRC-020" ] }, { "target": "WM-FLW-009 Journey / Trip", "relation": "REFERENCE", "purpose": "Resolve transport execution and observations while shipment and consignment keep commercial or transport grouping identity.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-012", "SRC-013", "SRC-018" ] }, { "target": "WM-FLW-012 Inventory Movement and WM-FLW-013 Supply-chain Trace / Chain of Custody", "relation": "REFERENCE", "purpose": "Resolve stock mutations and cross-organizational trace evidence without duplicating their lifecycles.", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-014", "SRC-015", "SRC-022" ] }, { "target": "UN/CEFACT BSP-RDM, SCRDM, MMT and UN/LOCODE", "relation": "ALIGN", "purpose": "Project syntax-neutral trade, transport and location views with exact release and classifier pins.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010" ] }, { "target": "WCO Data Model and EU eFTI", "relation": "ALIGN", "purpose": "Project cross-border regulatory information without treating one jurisdictional profile as universal law.", "required": false, "source_refs": [ "SRC-011", "SRC-012", "SRC-019" ] }, { "target": "OASIS UBL 2.4", "relation": "ALIGN", "purpose": "Project documents, shipment-consignment allocations, items, events and freight status with pinned semantics.", "required": false, "source_refs": [ "SRC-013" ] }, { "target": "GS1 EPCIS 2.0.1 and CBV 2.0.0", "relation": "ALIGN", "purpose": "Project visibility-event and business-vocabulary views without turning observations into master truth.", "required": false, "source_refs": [ "SRC-014", "SRC-015" ] }, { "target": "IATA ONE Record 3.2 and DCSA Track and Trace", "relation": "ALIGN", "purpose": "Project air-cargo and container-shipping views as modal profiles.", "required": false, "source_refs": [ "SRC-016", "SRC-017", "SRC-018" ] }, { "target": "RFC 3339, PROV-O, DQV and ODRL", "relation": "ALIGN", "purpose": "Project temporal, provenance, quality and access semantics with exact pins and semantic-loss declarations.", "required": false, "source_refs": [ "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, shipment and consignment stewards, trade and transport authorities and accountable decision roles.", "Register authoritative goods, order, contract, party, place, handling-unit, inventory, journey, route, service, booking, document, declaration, dangerous-goods, trace, sensor, incident, claim and evidence masters.", "Publish shipment, consignment, allocation, relation, status, identifier, access, retention, quality and interoperability registries.", "Pin trade, mode, region, customs, dangerous-goods, measurement, temperature, safety, privacy, licensing and exchange profiles." ], "namespace_guidance": "Mint shipment, consignment, revision, allocation, item-binding, milestone-assertion, exception and projection identifiers only in the adopting Dimension namespace; preserve external master identities as typed references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local shipment, consignment, allocation, identifier, status, access, retention and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, mandatory semantic kind, authoritative master ID, immutable revision, party and endpoint boundary, item scope and source profile; never use date, tracking number, document number, barcode, endpoint pair or hash alone as identity.", "Keep trade shipment, transport consignment, goods item, consignment item, package, handling unit, transport equipment, inventory movement, journey, trace event, delivery obligation and transport document distinct and preserve allocations, corrections and successors." ], "patch_rules": [ "Additive extensions use a Dimension-owned namespace and declare target node, trade, mode or jurisdiction profile, authority, source, rationale, access, time and interoperability impact.", "Breaking changes require a new version, migration and crosswalk maps, compatibility declaration and continued resolution of prior object revisions, allocations and identifiers." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when kind, identity, item allocation, parties, endpoints, clocks, status, authority, provenance and access meaning remain intact.", "UN/CEFACT, WCO, UBL, GS1, IATA, DCSA, eFTI, UN/LOCODE, units and provenance mappings pin source and target versions and declare transformed, omitted or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "Authoritative shipment or consignment master-system identifier and immutable revision.", "Governed globally resolvable shipment, consignment, allocation or milestone IRI.", "Adopting-Dimension UUID or ULID when no authoritative external identifier exists." ], "timestamp_rule": "Record event timestamps in RFC 3339 with seconds and an explicit UTC offset or Z; keep planned, estimated, predicted, observed, actual, record, correction and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {shipment-or-consignment-id}--{artifact-kind}--{revision-or-event-id}; never use a date, tracking code, document number, barcode, party, location, filename or hash alone as identity.", "integrity_rule": "Store digest, media type, byte length, issuer, source and vocabulary versions, object scope, event and record times, provenance, assurance, license and access marking for each retained serial artifact." }, "policies": [ "The adopting Dimension declares who may create, allocate, compose, bind, instruct, assert status, correct, disclose, retain and tombstone shipment or consignment records.", "Every assertion requires mandatory semantic kind, identity and revision, item or logistics scope, party and endpoint context, time kind, source, authority, confidence, status and lineage as applicable.", "Agents never infer ownership, custody, fulfilment, inventory state, legal permission, customs clearance, safe handling, delivery completion or claim validity from a status, tracking code, document or location alone.", "Goods, orders, fulfilment, handling units, inventory movements, journeys, routes, services, parties, locations, contracts, bookings, documents, declarations, dangerous-goods masters, sensors, trace, incidents, claims and evidence remain external masters.", "Automated agents may append low-risk memberships, status assertions, reconciliations and projections under delegation, but custody transfer, customs declaration, dangerous-goods decisions, protected disclosure and irreversible deletion require accountable authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, mandatory kind, requested revision, item scope, status horizon, assurance, freshness, license and access policy; return the minimum permitted projection." ], "create": [ "Create stable identity, mandatory kind, party and endpoint boundary, item scope, source, authority and explicit unknowns before adding allocations, units or milestone assertions." ], "update": [ "Append an immutable allocation, composition, instruction, status, measurement, exception or correction revision with actor, authority, reason, RFC 3339 effective time and predecessor." ], "delete": [ "Apply trade, customs, safety, dispute, audit, retention, disposition and legal-hold policy; tombstone eligible Shipment / Consignment-owned records or withdraw projections while preserving identity, material provenance and non-cascading external references. The adopting Dimension policy owns execution." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, access, retention and federation rules." ] }, { "name": "Shipment steward", "responsibilities": [ "Own trade-shipment boundary, goods grouping, allocations and commercial assertions." ] }, { "name": "Consignment steward", "responsibilities": [ "Own transport-consignment boundary, contract context, logistics composition and status assertions." ] }, { "name": "Trade party", "responsibilities": [ "Own seller, buyer, shipper, recipient and goods information within its authority." ] }, { "name": "Transport service party", "responsibilities": [ "Own consignor, consignee, carrier, forwarder, service and movement assertions it performs." ] }, { "name": "Regulatory authority or declarant", "responsibilities": [ "Own customs, dangerous-goods, security and regulatory assertions under applicable law." ] }, { "name": "Observation or data steward", "responsibilities": [ "Govern sources, clocks, measurements, status mappings, quality and correction lineage." ] }, { "name": "Reviewer or disclosure authority", "responsibilities": [ "Review evidence, conflicts, protected use, recipient, purpose, redaction and publication timing." ] } ], "access": { "default_rule": "Deny mutation and sensitive disclosure unless the active Dimension, role, purpose, object kind, trade confidentiality, location sensitivity, customs or safety rule, license and field policy grant the action; expose the minimum necessary projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency or regulatory access must be legally grounded, time-limited, purpose-bound, attributable, independently reviewed and unable to erase immutable shipment, consignment, correction or legal-hold evidence." ], "audit_requirements": [ "Log actor, role, purpose, object and revision identity, action, decision, policy and vocabulary versions, RFC 3339 timestamp with offset, affected fields, source evidence and outcome for privileged mutation or disclosure." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the nearest Dimension-owner AGENTS.md, trade and transport authority, active mode, jurisdiction, time, access, retention, licensing and disclosure policies.", "Read this model AGENTS.md, pinned spec.yaml and required goods, order, handling-unit, inventory, journey, route, service, party, location, contract, booking, document, declaration, dangerous-goods, trace, sensor, incident, claim and evidence model instructions before mutation." ] } }, "coverage": { "claim": "WM-FLW-011 covers a governed Shipment / Consignment aggregate family with a mandatory semantic kind, shipment-consignment many-to-many allocation, goods and package composition, handling-unit membership, locations and movement references, service and compliance requirements, milestone assertions, responsibility, exceptions, measures, documents, provenance, access and loss-aware projections. Trade, mode, jurisdiction, dangerous-goods, customs, implementation-conformance and independent-review questions remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Trade shipment, transport consignment, revision, allocation, item binding, milestone assertion and projection identities remain distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Mandatory kind separates seller-to-buyer goods grouping from consignor-to-consignee transport-contract grouping." }, { "dimension": "direct properties", "status": "covered", "notes": "Party and endpoint boundary, item scope, requirements, qualified measures and status assertions are covered without importing external masters." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Master assertion, plan, prediction, status report, EPCIS event, sensor observation, document and correction are distinguished." }, { "dimension": "lifecycle", "status": "covered", "notes": "Draft, planned, booked, accepted, picked-up, in-transit, arrived, delivered, returned, cancelled, corrected and tombstoned states preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Trade and transport parties, goods, packages, handling units, journeys, routes, services, documents, declarations, trace and claims use typed bindings." }, { "dimension": "temporal", "status": "covered", "notes": "Planned, estimated, predicted, observed, actual, record, correction and ingestion clocks remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Origin, destination, receipt, loading, transshipment, unloading, border, storage and delivery location functions are explicit." }, { "dimension": "provenance", "status": "covered", "notes": "Sources, actors, methods, documents, events, derivations, revisions and invalidations are linked." }, { "dimension": "ownership", "status": "covered", "notes": "Trade ownership, custody, possession, control, risk, responsibility and data mastership are not conflated." }, { "dimension": "validation", "status": "covered", "notes": "Identity, kind, many-to-many allocation, quantity balance, membership, endpoint, clock, requirement, measurement, document and crosswalk checks are explicit." }, { "dimension": "access", "status": "covered", "notes": "Role, purpose, commercial confidentiality, customs, safety, location sensitivity, minimum projection and audit are represented." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Corrections, disputes, customs or legal hold, withdrawal and tombstones are explicit and non-cascading." }, { "dimension": "interoperability", "status": "covered", "notes": "UN/CEFACT, WCO, UBL, GS1, IATA, DCSA, eFTI, UN/LOCODE, ISO, RFC, PROV, DQV and ODRL mappings disclose loss." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Registration, allocation, item composition, unit binding, movement binding, requirements, milestones, exceptions, reconciliation and projection declare controlled effects." } ], "known_omissions": [ "Trade, mode, region, customs, dangerous-goods, security, temperature, food, pharmaceutical, animal, waste, sanctions, export-control, safety, privacy, licensing and retention profiles require exact current rules and competent review.", "Goods, orders, contracts, fulfilment, handling units, inventory, journeys, routes, services, bookings, documents, declarations, dangerous-goods masters, trace, sensors, incidents, claims and evidence lifecycles remain in neighboring models.", "Certified field crosswalks, status inference, ETA, exception causality, custody proof, customs admissibility and legal evidence requirements remain future work." ], "conflicts": [ "UN/CEFACT and WCO use shipment as the trade or goods view and consignment as the transport-contract view, while UBL describes them as contractual or logical versus physical or logistical views; the model requires a mandatory semantic kind and source profile.", "Shipment and consignment have many-to-many allocation under split and consolidated transport, so neither can be treated as the universal container of the other.", "A tracking status, EPCIS event, sensor reading, transport document, customs declaration and proof of delivery are different assertion or evidence classes and cannot silently establish ownership, custody, fulfilment or legal clearance." ], "regional_assumptions": [ "WCO customs guidance and EU eFTI rules are regulatory profiles rather than universal commercial or transport law.", "IATA ONE Record and DCSA Track and Trace are modal profiles for air cargo and container shipping and do not define all shipment types.", "Dangerous-goods, customs, sanctions, transport documents, title, custody and delivery consequences depend on mode, contract and jurisdiction." ], "adversarial_checks": [ "Reject an object without stable identity, mandatory shipment-or-consignment kind, revision, party and endpoint boundary, item scope, source and lineage.", "Reject shipment and consignment collapsed into one identity or a one-to-many-only relationship that cannot represent split and consolidated transport.", "Reject a goods item, package, handling unit, container, inventory movement, journey, status event, document or delivery obligation represented as the shipment or consignment itself.", "Reject planned, estimated, predicted, observed and actual milestone times collapsed into one timestamp or interpreted without source and timezone rules.", "Reject custody, ownership, fulfilment, customs clearance, safe condition or delivery inferred from location, tracking status, waybill or proof label alone.", "Reject last-write-wins when item quantities, handling-unit membership, status assertions, measurements or documents conflict; preserve source, clocks, correction and precedence.", "Reject protected commercial or location disclosure, dangerous-goods decision, customs submission or record destruction outside delegated authority." ] }, "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-mandatory-kind", "rationale": "Cross-domain discovery justifies one aggregate family only when every instance declares trade-shipment, transport-consignment or combined-logistics-view. Goods, obligations, handling units, inventory, movement, trace, documents, declarations, claims and evidence remain external masters." }, "decisions": [ { "concept": "Shipment / Consignment aggregate boundary", "disposition": "accepted-with-mandatory-semantic-kind", "rationale": "Trade shipment and transport consignment are related views but have different party, contract and allocation semantics." }, { "concept": "Trade shipment and transport consignment", "disposition": "accepted-as-distinct-identities", "rationale": "UN/CEFACT and WCO separate what goods are shipped from how they move under a transport contract." }, { "concept": "Split and consolidated transport", "disposition": "accepted-as-many-to-many-allocation", "rationale": "One shipment may use several consignments and one consignment may consolidate all or part of several shipments." }, { "concept": "WM-FLW-004 parent signal", "disposition": "held-as-compositional-reference", "rationale": "Goods Movement / Logistics is broader, and the relation ledger does not yet approve inheritance." }, { "concept": "WM-OBJ-021 CONTAINS relation", "disposition": "accepted-as-typed-membership-only", "rationale": "Shipment or consignment can group handling units, while unit identity, physical state, nesting and lifecycle remain external." }, { "concept": "WM-FLW-009 reference", "disposition": "accepted-with-execution-boundary", "rationale": "Shipment / Consignment binds movement journeys and milestones but does not own movement execution or observations." }, { "concept": "Inventory movement and trace", "disposition": "accepted-as-external-neighbor-masters", "rationale": "Stock mutation and cross-organizational chain-of-custody event graphs remain in WM-FLW-012 and WM-FLW-013." }, { "concept": "Status and visibility events", "disposition": "accepted-as-source-qualified-assertions", "rationale": "Tracking status, EPCIS events, sensor observations and predicted milestones cannot silently overwrite master assertions." }, { "concept": "Transport documents and declarations", "disposition": "accepted-as-external-record-references", "rationale": "Instructions, waybills, bills of lading, customs declarations and certificates retain independent identity, issuance and legal effect." }, { "concept": "Standards projections", "disposition": "accepted-as-versioned-loss-aware-alignments", "rationale": "UN/CEFACT, WCO, UBL, GS1, IATA, DCSA and eFTI use different scopes, profiles and legal contexts." }, { "concept": "Single-provider waiver and local 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 acquiring new facts, so assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-FLW-011 each timed out after 120 seconds; no external result was admitted.", "Aggregate hold: every instance must declare trade-shipment, transport-consignment or combined-logistics-view.", "Relation hold: WM-FLW-004 remains a compositional reference rather than an approved parent until joint boundary review.", "Containment hold: WM-OBJ-021 is a typed membership target; handling-unit identity, physical state, nesting and lifecycle remain external.", "Boundary hold: goods, orders, fulfilment, inventory movement, journey execution, trace, documents, declarations, claims and evidence remain external masters.", "Terminology hold: shipment, consignment, goods shipment, trade shipment, cargo, item, piece, package, handling unit and transport equipment are profile-specific terms.", "Mode hold: air, road, rail, maritime, inland-waterway, postal, courier, multimodal and autonomous-freight profiles need independent validation.", "Jurisdiction hold: customs, dangerous-goods, sanctions, export control, security, temperature, title, custody, privacy, licensing and retention rules depend on context.", "Evidence hold: tracking status, document possession, a location event or proof label does not alone prove ownership, custody, fulfilment, safe condition or legal clearance.", "Interoperability hold: every UN/CEFACT, WCO, UBL, GS1, IATA, DCSA, eFTI, UN/LOCODE, ISO, RFC, PROV, DQV and ODRL projection needs exact pins, conformance evidence and semantic-loss declarations.", "Review hold: trade, transport, customs, dangerous-goods, safety, privacy, logistics, data governance, records and independent external review are outstanding.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Approve or reject the WM-FLW-004 parent relation after joint Goods Movement / Logistics boundary review.", "Create independently validated trade-shipment, transport-consignment, air-cargo, ocean-container, road, rail, parcel, cold-chain, dangerous-goods, humanitarian and waste profiles.", "Benchmark identifier matching, split and consolidation allocation, quantity reconciliation, status inference, ETA, exception causality, custody proof and customs admissibility.", "Pin exact releases and licensing conditions and obtain independent domain review before promotion beyond reviewable-draft assurance." ] }, "statistics": { "sources": 24, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }