# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T00:03:03Z", "synthesisSha256": "1a9cd58a739705a878e752db7c67fcf13ea2150f815ec61939bf6640897ab24c", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-FLW-004", "registryId": "vr.wm-flw-004", "name": "Goods Movement / Logistics", "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": [ "goods", "movement", "logistics", "phy.flw.log" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-flw-004-goods-movement-logistics/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-004", "model": { "registry_id": "vr.wm-flw-004", "model_id": "WM-FLW-004", "name": "Goods Movement / Logistics", "entry_kind": "aggregate", "purpose": "Represent the governed plan and observed history of moving identified physical goods through routes, legs, custody transitions, milestones and exceptions independently of storage, interface or transport provider.", "scope_statement": "Owns movement, shipment and consignment identity and boundary, cargo and handling-unit bindings, routes, multimodal legs, schedules, observations, derived status, custody assertions, condition bindings, exceptions, ETA, replanning, regulatory-status references, projections and standards mappings while neighboring masters own physical objects and legal or commercial lifecycles.", "in_scope": [ "Movement, shipment and consignment identities, party roles, service constraints, cargo lines, package and handling-unit composition and equipment bindings", "Origins, destinations, routes, ordered multimodal legs, planned and actual milestones, custody assertions, condition evidence, exceptions, ETA, replanning and delivery outcomes", "Regulatory status references, identifier reconciliation, provenance, access, retention, stakeholder projections and interoperability crosswalks" ], "out_of_scope": [ "Sale, order, title, ownership, inventory accounting, financial valuation, contract, procurement, invoice, payment, insurance claim or customs-declaration master lifecycles", "Goods, lot, product, package, handling unit, transport equipment, vehicle, vessel, aircraft, facility, location, party, organization, sensor, evidence or document master lifecycles", "Universal mode-specific operations, routing algorithms, tariff rules, dangerous-goods law, sanctions, customs clearance logic, carrier liability or proof-of-delivery law" ], "boundary_notes": [ { "neighbor": "Goods, Product, Lot, Package and Handling Unit", "distinction": "The movement binds identified cargo and versions containment or aggregation for transport, while physical and commercial object properties remain externally mastered.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "neighbor": "Vehicle, Vessel, Aircraft and Transport Equipment", "distinction": "A leg references the means and equipment performing or containing movement; their registration, capacity, maintenance, location and lifecycle stay external.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "neighbor": "Party, Organization, Facility and Location", "distinction": "Parties and places are assigned interval-specific logistics roles and functions but retain authoritative identity and lifecycle in their masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] }, { "neighbor": "Order, Contract, Invoice, Payment, Ownership and Inventory", "distinction": "Commercial, legal, financial and stock records may motivate or evidence movement but are not movement events and remain typed references.", "source_refs": [ "SRC-001", "SRC-006", "SRC-009" ] }, { "neighbor": "Customs, Permit, Sanction and Regulatory Decision", "distinction": "The model binds authoritative declarations, holds, releases and permissions plus their operational effect without reproducing border-agency decision lifecycles.", "source_refs": [ "SRC-007", "SRC-008" ] }, { "neighbor": "Sensor, Observation, Evidence, Incident and Claim", "distinction": "Condition streams, proof, generic incidents and legal or insurance claims retain their master records; movement stores scoped observations, summaries and resolvable links.", "source_refs": [ "SRC-003", "SRC-006", "SRC-009" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Streamlined presentation of UN/CEFACT standards", "organization": "United Nations Economic Commission for Europe", "url": "https://unece.org/trade/uncefact/mainstandards", "version_or_date": "Current catalogue accessed 2026-09-06; MMT RDM releases listed by version", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T04:00:00Z", "relevance": "Publishes the syntax-neutral Multi Modal Transport and Supply Chain reference data models, code lists and mode-specific exchange structures." }, { "id": "SRC-002", "title": "Recommendation No. 16: United Nations Code for Trade and Transport Locations", "organization": "United Nations Economic Commission for Europe", "url": "https://unlocode.unece.org/recommendation16/", "version_or_date": "Fourth edition, 2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T04:00:00Z", "relevance": "Defines governed five-character trade and transport location identifiers, functions, subdivisions, coordinates, status and maintenance semantics." }, { "id": "SRC-003", "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-06T04:00:00Z", "relevance": "Defines capture and query semantics for visibility events, including event time, record time, objects, locations, business context, sensor elements and error declarations." }, { "id": "SRC-004", "title": "Core Business Vocabulary Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/cbv/2.0.0/", "version_or_date": "CBV 2.0, ratified June 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T04:00:00Z", "relevance": "Defines interoperable business steps, dispositions, source and destination types, location and error vocabulary used with EPCIS events." }, { "id": "SRC-005", "title": "Track and Trace standard documentation", "organization": "Digital Container Shipping Association", "url": "https://dcsa.org/standards/track-and-trace/standard-documentation-track-and-trace", "version_or_date": "Track and Trace 2.2 with Industry Blueprint 3.0 references", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T04:00:00Z", "relevance": "Defines container-shipping phases, equipment, shipment, transport and operational event semantics plus APIs and subscription callbacks." }, { "id": "SRC-006", "title": "ONE Record Ontology", "organization": "International Air Transport Association", "url": "https://onerecord.iata.org/ns/cargo/3.2.0", "version_or_date": "Revision 3.2.0, modified 24 June 2025", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T04:00:00Z", "relevance": "Defines a linked-data air-cargo model for logistics objects, actions, events, pieces, shipments, transport movements, locations, parties and data sharing." }, { "id": "SRC-007", "title": "WCO Data Model", "organization": "World Customs Organization", "url": "https://www.wcoomd.org/DataModel", "version_or_date": "Current official portal accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T04:00:00Z", "relevance": "Provides a harmonized cross-border regulatory data model for customs and other border-agency declarations, responses and status interfaces." }, { "id": "SRC-008", "title": "Convention on Facilitation of International Maritime Traffic", "organization": "International Maritime Organization", "url": "https://www.imo.org/en/about/conventions/pages/convention-on-facilitation-of-international-maritime-traffic-%28fal%29.aspx", "version_or_date": "FAL Convention overview including amendments effective 1 January 2024", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T04:00:00Z", "relevance": "Defines maritime arrival, stay and departure information exchange, cargo declarations, clearance interfaces and mandatory single-window profile." }, { "id": "SRC-009", "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-06T04:00:00Z", "relevance": "Defines portable entity, activity, agent, attribution, derivation, delegation, revision and invalidation provenance." }, { "id": "SRC-010", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T04:00:00Z", "relevance": "Defines interoperable timestamps with seconds and an explicit UTC offset for planned, estimated, observed, corrected and ingestion times." } ], "structure": { "bundles": [ { "id": "identity-scope-and-arrangement", "name": "Identity, scope and arrangement", "description": "Establishes the governed movement record, distinct transport objects, parties, roles and service boundary.", "rationale": "Shipment, consignment, transport movement and commercial order are not synonyms, so stable identity and arrangement boundaries precede routing or status.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ], "layers": [ { "id": "movement-and-consignment-identity", "name": "Movement and consignment identity", "description": "Stable identities, classes, revisions and aggregation boundaries.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ], "findings": [ { "id": "movement-master-identity-class-profile-and-status", "name": "Movement master identity, class, profile and status", "description": "Identifies the governed goods-movement aggregate, mode profile, current derived state, immutable revision and authoritative namespace.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ], "questions": [ { "id": "movement-master-identity-class-profile-and-status-q01", "text": "What governed logistics assertion is recorded for movement master identity, class, profile and status, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "identity", "answer_data": [ "Movement master identity, class, profile and status", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "movement-master-identity-class-profile-and-status-q02", "text": "Which source, actor, authority, observation or method establishes movement master identity, class, profile and status, with what evidence, confidence, freshness and limitations?", "kind": "spatial", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "movement-master-identity-class-profile-and-status-q03", "text": "Which validation, access, transition or correction rule governs movement master identity, class, profile and status, and how are predecessors, successors and external master bindings preserved?", "kind": "quality", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "movement-master-identity-class-profile-and-status-data", "name": "Movement master identity, class, profile and status assertion", "description": "Structured goods-movement answer data for movement master identity, class, profile and status, including object scope, place, time, state, source and provenance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "movement-master-identity-class-profile-and-status-artifact", "name": "Movement master identity, class, profile and status record", "description": "Versioned logistics record supporting movement master identity, class, profile and status with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "shipment-consignment-booking-order-and-transport-movement-boundary", "name": "Shipment, consignment, booking, order and transport movement boundary", "description": "Keeps logistics grouping, transport-service request, commercial order and physical movement identifiers distinct with typed aggregation and equivalence claims.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "shipment-consignment-booking-order-and-transport-movement-boundary-q01", "text": "What governed logistics assertion is recorded for shipment, consignment, booking, order and transport movement boundary, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "definition", "answer_data": [ "Shipment, consignment, booking, order and transport movement boundary", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "shipment-consignment-booking-order-and-transport-movement-boundary-q02", "text": "Which source, actor, authority, observation or method establishes shipment, consignment, booking, order and transport movement boundary, with what evidence, confidence, freshness and limitations?", "kind": "provenance", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "shipment-consignment-booking-order-and-transport-movement-boundary-q03", "text": "Which validation, access, transition or correction rule governs shipment, consignment, booking, order and transport movement boundary, and how are predecessors, successors and external master bindings preserved?", "kind": "validation", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "shipment-consignment-booking-order-and-transport-movement-boundary-data", "name": "Shipment, consignment, booking, order and transport movement boundary assertion", "description": "Structured goods-movement answer data for shipment, consignment, booking, order and transport movement boundary, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "shipment-consignment-booking-order-and-transport-movement-boundary-artifact", "name": "Shipment, consignment, booking, order and transport movement boundary record", "description": "Versioned logistics record supporting shipment, consignment, booking, order and transport movement boundary with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "parties-roles-and-service-terms", "name": "Parties, roles and service terms", "description": "Interval-specific responsibility and the referenced carriage arrangement.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "findings": [ { "id": "shipper-consignee-carrier-forwarder-terminal-and-agent-roles", "name": "Shipper, consignee, carrier, forwarder, terminal and agent roles", "description": "Binds authoritative party or organization references to role, leg, interval, delegation, contact projection and responsibility without importing party lifecycles.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "shipper-consignee-carrier-forwarder-terminal-and-agent-roles-q01", "text": "What governed logistics assertion is recorded for shipper, consignee, carrier, forwarder, terminal and agent roles, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "relationship", "answer_data": [ "Shipper, consignee, carrier, forwarder, terminal and agent roles", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "shipper-consignee-carrier-forwarder-terminal-and-agent-roles-q02", "text": "Which source, actor, authority, observation or method establishes shipper, consignee, carrier, forwarder, terminal and agent roles, with what evidence, confidence, freshness and limitations?", "kind": "ownership", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "shipper-consignee-carrier-forwarder-terminal-and-agent-roles-q03", "text": "Which validation, access, transition or correction rule governs shipper, consignee, carrier, forwarder, terminal and agent roles, and how are predecessors, successors and external master bindings preserved?", "kind": "security", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "shipper-consignee-carrier-forwarder-terminal-and-agent-roles-data", "name": "Shipper, consignee, carrier, forwarder, terminal and agent roles assertion", "description": "Structured goods-movement answer data for shipper, consignee, carrier, forwarder, terminal and agent roles, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "shipper-consignee-carrier-forwarder-terminal-and-agent-roles-artifact", "name": "Shipper, consignee, carrier, forwarder, terminal and agent roles record", "description": "Versioned logistics record supporting shipper, consignee, carrier, forwarder, terminal and agent roles with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "transport-service-booking-carriage-terms-and-handling-constraints", "name": "Transport service, booking, carriage terms and handling constraints", "description": "References the service or carriage agreement, service level, incoterm where applicable, cut-offs, handling instructions, liability boundary and acceptance criteria.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "transport-service-booking-carriage-terms-and-handling-constraints-q01", "text": "What governed logistics assertion is recorded for transport service, booking, carriage terms and handling constraints, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "constraint", "answer_data": [ "Transport service, booking, carriage terms and handling constraints", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "transport-service-booking-carriage-terms-and-handling-constraints-q02", "text": "Which source, actor, authority, observation or method establishes transport service, booking, carriage terms and handling constraints, with what evidence, confidence, freshness and limitations?", "kind": "authority", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "transport-service-booking-carriage-terms-and-handling-constraints-q03", "text": "Which validation, access, transition or correction rule governs transport service, booking, carriage terms and handling constraints, and how are predecessors, successors and external master bindings preserved?", "kind": "privacy", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "transport-service-booking-carriage-terms-and-handling-constraints-data", "name": "Transport service, booking, carriage terms and handling constraints assertion", "description": "Structured goods-movement answer data for transport service, booking, carriage terms and handling constraints, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "transport-service-booking-carriage-terms-and-handling-constraints-artifact", "name": "Transport service, booking, carriage terms and handling constraints record", "description": "Versioned logistics record supporting transport service, booking, carriage terms and handling constraints with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "cargo-composition-and-equipment", "name": "Cargo composition and equipment", "description": "Represents referenced goods, quantities, packaging hierarchy, handling units, transport equipment and seals.", "rationale": "Movement planning and proof depend on exact whole-part structure, but goods and equipment retain their physical properties and lifecycles in their own masters.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "cargo-lines-and-goods-bindings", "name": "Cargo lines and goods bindings", "description": "What is declared to move and how quantity is interpreted.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "cargo-line-goods-lot-batch-and-order-reference", "name": "Cargo line, goods, lot, batch and order reference", "description": "Binds each cargo line to authoritative product, item, lot, batch, serial and order-line identities with description, classification and declared relationship.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ], "questions": [ { "id": "cargo-line-goods-lot-batch-and-order-reference-q01", "text": "What governed logistics assertion is recorded for cargo line, goods, lot, batch and order reference, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "relationship", "answer_data": [ "Cargo line, goods, lot, batch and order reference", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "cargo-line-goods-lot-batch-and-order-reference-q02", "text": "Which source, actor, authority, observation or method establishes cargo line, goods, lot, batch and order reference, with what evidence, confidence, freshness and limitations?", "kind": "requirement", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "cargo-line-goods-lot-batch-and-order-reference-q03", "text": "Which validation, access, transition or correction rule governs cargo line, goods, lot, batch and order reference, and how are predecessors, successors and external master bindings preserved?", "kind": "retention", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "cargo-line-goods-lot-batch-and-order-reference-data", "name": "Cargo line, goods, lot, batch and order reference assertion", "description": "Structured goods-movement answer data for cargo line, goods, lot, batch and order reference, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "cargo-line-goods-lot-batch-and-order-reference-artifact", "name": "Cargo line, goods, lot, batch and order reference record", "description": "Versioned logistics record supporting cargo line, goods, lot, batch and order reference with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "quantity-weight-volume-dimensions-value-and-measurement-basis", "name": "Quantity, weight, volume, dimensions, value and measurement basis", "description": "Records declared and measured quantities, units, gross and net mass, volume, dimensions, declared value reference, tolerances, source and measurement time.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "questions": [ { "id": "quantity-weight-volume-dimensions-value-and-measurement-basis-q01", "text": "What governed logistics assertion is recorded for quantity, weight, volume, dimensions, value and measurement basis, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "measurement", "answer_data": [ "Quantity, weight, volume, dimensions, value and measurement basis", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "quantity-weight-volume-dimensions-value-and-measurement-basis-q02", "text": "Which source, actor, authority, observation or method establishes quantity, weight, volume, dimensions, value and measurement basis, with what evidence, confidence, freshness and limitations?", "kind": "constraint", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "quantity-weight-volume-dimensions-value-and-measurement-basis-q03", "text": "Which validation, access, transition or correction rule governs quantity, weight, volume, dimensions, value and measurement basis, and how are predecessors, successors and external master bindings preserved?", "kind": "access", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "quantity-weight-volume-dimensions-value-and-measurement-basis-data", "name": "Quantity, weight, volume, dimensions, value and measurement basis assertion", "description": "Structured goods-movement answer data for quantity, weight, volume, dimensions, value and measurement basis, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "quantity-weight-volume-dimensions-value-and-measurement-basis-artifact", "name": "Quantity, weight, volume, dimensions, value and measurement basis record", "description": "Versioned logistics record supporting quantity, weight, volume, dimensions, value and measurement basis with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "packages-handling-units-and-equipment", "name": "Packages, handling units and equipment", "description": "Nested containment, logistics aggregation and load integrity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "package-handling-unit-containment-aggregation-and-split", "name": "Package and handling-unit containment, aggregation and split", "description": "Versions parent-child packing, aggregation, disaggregation, consolidation, split and partial-delivery mappings without conflating a package with its contents.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "package-handling-unit-containment-aggregation-and-split-q01", "text": "What governed logistics assertion is recorded for package and handling-unit containment, aggregation and split, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "composition", "answer_data": [ "Package and handling-unit containment, aggregation and split", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "package-handling-unit-containment-aggregation-and-split-q02", "text": "Which source, actor, authority, observation or method establishes package and handling-unit containment, aggregation and split, with what evidence, confidence, freshness and limitations?", "kind": "process", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "package-handling-unit-containment-aggregation-and-split-q03", "text": "Which validation, access, transition or correction rule governs package and handling-unit containment, aggregation and split, and how are predecessors, successors and external master bindings preserved?", "kind": "exception", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "package-handling-unit-containment-aggregation-and-split-data", "name": "Package and handling-unit containment, aggregation and split assertion", "description": "Structured goods-movement answer data for package and handling-unit containment, aggregation and split, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "package-handling-unit-containment-aggregation-and-split-artifact", "name": "Package and handling-unit containment, aggregation and split record", "description": "Versioned logistics record supporting package and handling-unit containment, aggregation and split with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "transport-equipment-load-plan-seal-and-capacity-reference", "name": "Transport equipment, load plan, seal and capacity reference", "description": "Binds container, trailer, wagon, unit-load device or other equipment, load position, capacity use, seal identities and authoritative equipment master.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "transport-equipment-load-plan-seal-and-capacity-reference-q01", "text": "What governed logistics assertion is recorded for transport equipment, load plan, seal and capacity reference, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "relationship", "answer_data": [ "Transport equipment, load plan, seal and capacity reference", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "transport-equipment-load-plan-seal-and-capacity-reference-q02", "text": "Which source, actor, authority, observation or method establishes transport equipment, load plan, seal and capacity reference, with what evidence, confidence, freshness and limitations?", "kind": "event", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "transport-equipment-load-plan-seal-and-capacity-reference-q03", "text": "Which validation, access, transition or correction rule governs transport equipment, load plan, seal and capacity reference, and how are predecessors, successors and external master bindings preserved?", "kind": "interoperability", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "transport-equipment-load-plan-seal-and-capacity-reference-data", "name": "Transport equipment, load plan, seal and capacity reference assertion", "description": "Structured goods-movement answer data for transport equipment, load plan, seal and capacity reference, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "transport-equipment-load-plan-seal-and-capacity-reference-artifact", "name": "Transport equipment, load plan, seal and capacity reference record", "description": "Versioned logistics record supporting transport equipment, load plan, seal and capacity reference with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "route-schedule-and-multimodal-legs", "name": "Route, schedule and multimodal legs", "description": "Defines origin-to-destination plan, locations, corridors, ordered legs, modes, means and dependencies.", "rationale": "A route plan and its execution need versioned locations, leg order and time semantics so replanning does not erase what was originally intended.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-010" ], "layers": [ { "id": "locations-corridors-and-route-alternatives", "name": "Locations, corridors and route alternatives", "description": "Operational places, geographic path and candidate routing.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ], "findings": [ { "id": "origin-destination-waypoint-facility-location-and-function", "name": "Origin, destination, waypoint, facility location and function", "description": "Binds named places, facilities, read points, business locations and location functions using authoritative identifiers, coordinates, version and uncertainty.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006" ], "questions": [ { "id": "origin-destination-waypoint-facility-location-and-function-q01", "text": "What governed logistics assertion is recorded for origin, destination, waypoint, facility location and function, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "spatial", "answer_data": [ "Origin, destination, waypoint, facility location and function", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "origin-destination-waypoint-facility-location-and-function-q02", "text": "Which source, actor, authority, observation or method establishes origin, destination, waypoint, facility location and function, with what evidence, confidence, freshness and limitations?", "kind": "measurement", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "origin-destination-waypoint-facility-location-and-function-q03", "text": "Which validation, access, transition or correction rule governs origin, destination, waypoint, facility location and function, and how are predecessors, successors and external master bindings preserved?", "kind": "decision", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "origin-destination-waypoint-facility-location-and-function-data", "name": "Origin, destination, waypoint, facility location and function assertion", "description": "Structured goods-movement answer data for origin, destination, waypoint, facility location and function, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "origin-destination-waypoint-facility-location-and-function-artifact", "name": "Origin, destination, waypoint, facility location and function record", "description": "Versioned logistics record supporting origin, destination, waypoint, facility location and function with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "route-corridor-alternative-restriction-and-selection-rationale", "name": "Route corridor, alternative, restriction and selection rationale", "description": "Versions the planned corridor, alternatives, border crossings, compatibility restrictions, hazards, selected path and decision rationale.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "route-corridor-alternative-restriction-and-selection-rationale-q01", "text": "What governed logistics assertion is recorded for route corridor, alternative, restriction and selection rationale, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "decision", "answer_data": [ "Route corridor, alternative, restriction and selection rationale", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "route-corridor-alternative-restriction-and-selection-rationale-q02", "text": "Which source, actor, authority, observation or method establishes route corridor, alternative, restriction and selection rationale, with what evidence, confidence, freshness and limitations?", "kind": "evidence", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "route-corridor-alternative-restriction-and-selection-rationale-q03", "text": "Which validation, access, transition or correction rule governs route corridor, alternative, restriction and selection rationale, and how are predecessors, successors and external master bindings preserved?", "kind": "identity", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "route-corridor-alternative-restriction-and-selection-rationale-data", "name": "Route corridor, alternative, restriction and selection rationale assertion", "description": "Structured goods-movement answer data for route corridor, alternative, restriction and selection rationale, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "route-corridor-alternative-restriction-and-selection-rationale-artifact", "name": "Route corridor, alternative, restriction and selection rationale record", "description": "Versioned logistics record supporting route corridor, alternative, restriction and selection rationale with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "legs-modes-means-and-schedule", "name": "Legs, modes, means and schedule", "description": "Ordered execution units and planned time dependencies.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010" ], "findings": [ { "id": "leg-sequence-mode-carrier-transport-means-and-transfer-point", "name": "Leg sequence, mode, carrier, transport means and transfer point", "description": "Defines ordered leg identity, mode, carrier or subcontractor, referenced means, origin, destination, transfer point and predecessor dependencies.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "leg-sequence-mode-carrier-transport-means-and-transfer-point-q01", "text": "What governed logistics assertion is recorded for leg sequence, mode, carrier, transport means and transfer point, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "composition", "answer_data": [ "Leg sequence, mode, carrier, transport means and transfer point", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "leg-sequence-mode-carrier-transport-means-and-transfer-point-q02", "text": "Which source, actor, authority, observation or method establishes leg sequence, mode, carrier, transport means and transfer point, with what evidence, confidence, freshness and limitations?", "kind": "quality", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "leg-sequence-mode-carrier-transport-means-and-transfer-point-q03", "text": "Which validation, access, transition or correction rule governs leg sequence, mode, carrier, transport means and transfer point, and how are predecessors, successors and external master bindings preserved?", "kind": "definition", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "leg-sequence-mode-carrier-transport-means-and-transfer-point-data", "name": "Leg sequence, mode, carrier, transport means and transfer point assertion", "description": "Structured goods-movement answer data for leg sequence, mode, carrier, transport means and transfer point, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "leg-sequence-mode-carrier-transport-means-and-transfer-point-artifact", "name": "Leg sequence, mode, carrier, transport means and transfer point record", "description": "Versioned logistics record supporting leg sequence, mode, carrier, transport means and transfer point with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "requested-planned-cutoff-estimated-and-revised-schedule", "name": "Requested, planned, cut-off, estimated and revised schedule", "description": "Separates requested, booked, planned, cut-off, estimated and revised departure, arrival, availability and delivery times with timezone and provenance.", "source_refs": [ "SRC-005", "SRC-006", "SRC-010" ], "questions": [ { "id": "requested-planned-cutoff-estimated-and-revised-schedule-q01", "text": "What governed logistics assertion is recorded for requested, planned, cut-off, estimated and revised schedule, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "temporal", "answer_data": [ "Requested, planned, cut-off, estimated and revised schedule", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "requested-planned-cutoff-estimated-and-revised-schedule-q02", "text": "Which source, actor, authority, observation or method establishes requested, planned, cut-off, estimated and revised schedule, with what evidence, confidence, freshness and limitations?", "kind": "validation", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "requested-planned-cutoff-estimated-and-revised-schedule-q03", "text": "Which validation, access, transition or correction rule governs requested, planned, cut-off, estimated and revised schedule, and how are predecessors, successors and external master bindings preserved?", "kind": "classification", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "requested-planned-cutoff-estimated-and-revised-schedule-data", "name": "Requested, planned, cut-off, estimated and revised schedule assertion", "description": "Structured goods-movement answer data for requested, planned, cut-off, estimated and revised schedule, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-010" ] } ], "artifacts": [ { "id": "requested-planned-cutoff-estimated-and-revised-schedule-artifact", "name": "Requested, planned, cut-off, estimated and revised schedule record", "description": "Versioned logistics record supporting requested, planned, cut-off, estimated and revised schedule with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-005", "SRC-006", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "operational-events-and-visibility", "name": "Operational events and visibility", "description": "Records dispatch, handling, movement, transfer, delivery and visibility observations with correct temporal semantics.", "rationale": "Operational status must derive from append-only observations and corrections; a plan, prediction or scan is not automatically an actual physical or legal event.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010" ], "layers": [ { "id": "readiness-pickup-loading-and-departure", "name": "Readiness, pickup, loading and departure", "description": "Origin-side milestones and physical handling observations.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "availability-readiness-pickup-and-receipt-observation", "name": "Availability, readiness, pickup and receipt observation", "description": "Records announced readiness, carrier pickup, physical receipt, accepted quantities, actor, place, time, evidence and discrepancies.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "availability-readiness-pickup-and-receipt-observation-q01", "text": "What governed logistics assertion is recorded for availability, readiness, pickup and receipt observation, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "event", "answer_data": [ "Availability, readiness, pickup and receipt observation", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "availability-readiness-pickup-and-receipt-observation-q02", "text": "Which source, actor, authority, observation or method establishes availability, readiness, pickup and receipt observation, with what evidence, confidence, freshness and limitations?", "kind": "security", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "availability-readiness-pickup-and-receipt-observation-q03", "text": "Which validation, access, transition or correction rule governs availability, readiness, pickup and receipt observation, and how are predecessors, successors and external master bindings preserved?", "kind": "composition", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "availability-readiness-pickup-and-receipt-observation-data", "name": "Availability, readiness, pickup and receipt observation assertion", "description": "Structured goods-movement answer data for availability, readiness, pickup and receipt observation, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "availability-readiness-pickup-and-receipt-observation-artifact", "name": "Availability, readiness, pickup and receipt observation record", "description": "Versioned logistics record supporting availability, readiness, pickup and receipt observation with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "loading-stuffing-gate-departure-and-leg-start-observation", "name": "Loading, stuffing, gate, departure and leg-start observation", "description": "Records packing into equipment, loading, gate movement, dispatch or departure and leg start with affected objects, location and source evidence.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "loading-stuffing-gate-departure-and-leg-start-observation-q01", "text": "What governed logistics assertion is recorded for loading, stuffing, gate, departure and leg-start observation, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "event", "answer_data": [ "Loading, stuffing, gate, departure and leg-start observation", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "loading-stuffing-gate-departure-and-leg-start-observation-q02", "text": "Which source, actor, authority, observation or method establishes loading, stuffing, gate, departure and leg-start observation, with what evidence, confidence, freshness and limitations?", "kind": "privacy", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "loading-stuffing-gate-departure-and-leg-start-observation-q03", "text": "Which validation, access, transition or correction rule governs loading, stuffing, gate, departure and leg-start observation, and how are predecessors, successors and external master bindings preserved?", "kind": "relationship", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "loading-stuffing-gate-departure-and-leg-start-observation-data", "name": "Loading, stuffing, gate, departure and leg-start observation assertion", "description": "Structured goods-movement answer data for loading, stuffing, gate, departure and leg-start observation, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "loading-stuffing-gate-departure-and-leg-start-observation-artifact", "name": "Loading, stuffing, gate, departure and leg-start observation record", "description": "Versioned logistics record supporting loading, stuffing, gate, departure and leg-start observation with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "arrival-transfer-delivery-and-return", "name": "Arrival, transfer, delivery and return", "description": "Destination and interchange milestones with quantity outcomes.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "arrival-unloading-transshipment-and-leg-completion-observation", "name": "Arrival, unloading, transshipment and leg-completion observation", "description": "Records actual arrival, discharge, unloading, transfer, missed connection and leg completion separately with source and affected handling units.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "arrival-unloading-transshipment-and-leg-completion-observation-q01", "text": "What governed logistics assertion is recorded for arrival, unloading, transshipment and leg-completion observation, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "event", "answer_data": [ "Arrival, unloading, transshipment and leg-completion observation", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "arrival-unloading-transshipment-and-leg-completion-observation-q02", "text": "Which source, actor, authority, observation or method establishes arrival, unloading, transshipment and leg-completion observation, with what evidence, confidence, freshness and limitations?", "kind": "retention", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "arrival-unloading-transshipment-and-leg-completion-observation-q03", "text": "Which validation, access, transition or correction rule governs arrival, unloading, transshipment and leg-completion observation, and how are predecessors, successors and external master bindings preserved?", "kind": "state", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "arrival-unloading-transshipment-and-leg-completion-observation-data", "name": "Arrival, unloading, transshipment and leg-completion observation assertion", "description": "Structured goods-movement answer data for arrival, unloading, transshipment and leg-completion observation, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "arrival-unloading-transshipment-and-leg-completion-observation-artifact", "name": "Arrival, unloading, transshipment and leg-completion observation record", "description": "Versioned logistics record supporting arrival, unloading, transshipment and leg-completion observation with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "delivery-partial-failure-return-and-proof-reference", "name": "Delivery, partial delivery, failure, return and proof reference", "description": "Records offered, accepted, rejected, partial, failed or returned delivery with delivered quantities, recipient role, reservation, proof and dispute references.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "delivery-partial-failure-return-and-proof-reference-q01", "text": "What governed logistics assertion is recorded for delivery, partial delivery, failure, return and proof reference, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "lifecycle", "answer_data": [ "Delivery, partial delivery, failure, return and proof reference", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "delivery-partial-failure-return-and-proof-reference-q02", "text": "Which source, actor, authority, observation or method establishes delivery, partial delivery, failure, return and proof reference, with what evidence, confidence, freshness and limitations?", "kind": "access", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "delivery-partial-failure-return-and-proof-reference-q03", "text": "Which validation, access, transition or correction rule governs delivery, partial delivery, failure, return and proof reference, and how are predecessors, successors and external master bindings preserved?", "kind": "lifecycle", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "delivery-partial-failure-return-and-proof-reference-data", "name": "Delivery, partial delivery, failure, return and proof reference assertion", "description": "Structured goods-movement answer data for delivery, partial delivery, failure, return and proof reference, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "delivery-partial-failure-return-and-proof-reference-artifact", "name": "Delivery, partial delivery, failure, return and proof reference record", "description": "Versioned logistics record supporting delivery, partial delivery, failure, return and proof reference with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "event-semantics-time-and-correction", "name": "Event semantics, time and correction", "description": "Observation meaning, confidence, capture, ordering and repair.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-009", "SRC-010" ], "findings": [ { "id": "event-type-business-step-disposition-read-point-and-source", "name": "Event type, business step, disposition, read point and source", "description": "Classifies an observation, business step, disposition, action, read point, business location, source, destination and affected object set using pinned vocabularies.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "event-type-business-step-disposition-read-point-and-source-q01", "text": "What governed logistics assertion is recorded for event type, business step, disposition, read point and source, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "classification", "answer_data": [ "Event type, business step, disposition, read point and source", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "event-type-business-step-disposition-read-point-and-source-q02", "text": "Which source, actor, authority, observation or method establishes event type, business step, disposition, read point and source, with what evidence, confidence, freshness and limitations?", "kind": "exception", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "event-type-business-step-disposition-read-point-and-source-q03", "text": "Which validation, access, transition or correction rule governs event type, business step, disposition, read point and source, and how are predecessors, successors and external master bindings preserved?", "kind": "temporal", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "event-type-business-step-disposition-read-point-and-source-data", "name": "Event type, business step, disposition, read point and source assertion", "description": "Structured goods-movement answer data for event type, business step, disposition, read point and source, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "event-type-business-step-disposition-read-point-and-source-artifact", "name": "Event type, business step, disposition, read point and source record", "description": "Versioned logistics record supporting event type, business step, disposition, read point and source with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "event-estimate-capture-ingestion-order-correction-and-precedence", "name": "Event, estimate, capture, ingestion, order, correction and precedence", "description": "Separates actual event, estimated event, sensor time, record time and ingestion time and applies deterministic ordering, error declaration, correction and supersession.", "source_refs": [ "SRC-003", "SRC-005", "SRC-009", "SRC-010" ], "questions": [ { "id": "event-estimate-capture-ingestion-order-correction-and-precedence-q01", "text": "What governed logistics assertion is recorded for event, estimate, capture, ingestion, order, correction and precedence, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "provenance", "answer_data": [ "Event, estimate, capture, ingestion, order, correction and precedence", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "event-estimate-capture-ingestion-order-correction-and-precedence-q02", "text": "Which source, actor, authority, observation or method establishes event, estimate, capture, ingestion, order, correction and precedence, with what evidence, confidence, freshness and limitations?", "kind": "interoperability", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "event-estimate-capture-ingestion-order-correction-and-precedence-q03", "text": "Which validation, access, transition or correction rule governs event, estimate, capture, ingestion, order, correction and precedence, and how are predecessors, successors and external master bindings preserved?", "kind": "spatial", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "event-estimate-capture-ingestion-order-correction-and-precedence-data", "name": "Event, estimate, capture, ingestion, order, correction and precedence assertion", "description": "Structured goods-movement answer data for event, estimate, capture, ingestion, order, correction and precedence, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "event-estimate-capture-ingestion-order-correction-and-precedence-artifact", "name": "Event, estimate, capture, ingestion, order, correction and precedence record", "description": "Versioned logistics record supporting event, estimate, capture, ingestion, order, correction and precedence with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-005", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "custody-condition-and-integrity", "name": "Custody, condition and integrity", "description": "Represents handovers, responsibility intervals, seal state, condition observations and proof without claiming ownership.", "rationale": "Custody, possession, carrier responsibility, title, ownership and delivery acceptance differ; evidence and authority must accompany every transition claim.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-009" ], "layers": [ { "id": "custody-possession-and-responsibility", "name": "Custody, possession and responsibility", "description": "Expected and actual handovers with interval semantics.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-009" ], "findings": [ { "id": "custody-possession-control-carrier-responsibility-and-interval", "name": "Custody, possession, control, carrier responsibility and interval", "description": "Separates physical possession, operational control, contractual carrier responsibility, stewardship and ownership references for each object and interval.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ], "questions": [ { "id": "custody-possession-control-carrier-responsibility-and-interval-q01", "text": "What governed logistics assertion is recorded for custody, possession, control, carrier responsibility and interval, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "relationship", "answer_data": [ "Custody, possession, control, carrier responsibility and interval", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "custody-possession-control-carrier-responsibility-and-interval-q02", "text": "Which source, actor, authority, observation or method establishes custody, possession, control, carrier responsibility and interval, with what evidence, confidence, freshness and limitations?", "kind": "decision", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "custody-possession-control-carrier-responsibility-and-interval-q03", "text": "Which validation, access, transition or correction rule governs custody, possession, control, carrier responsibility and interval, and how are predecessors, successors and external master bindings preserved?", "kind": "provenance", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "custody-possession-control-carrier-responsibility-and-interval-data", "name": "Custody, possession, control, carrier responsibility and interval assertion", "description": "Structured goods-movement answer data for custody, possession, control, carrier responsibility and interval, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "custody-possession-control-carrier-responsibility-and-interval-artifact", "name": "Custody, possession, control, carrier responsibility and interval record", "description": "Versioned logistics record supporting custody, possession, control, carrier responsibility and interval with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "handover-offer-acceptance-rejection-dispute-and-evidence", "name": "Handover offer, acceptance, rejection, dispute and evidence", "description": "Records expected or actual offer, transfer, acceptance, rejection, reservation, discrepancy, signatory authority, proof and correction lineage.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ], "questions": [ { "id": "handover-offer-acceptance-rejection-dispute-and-evidence-q01", "text": "What governed logistics assertion is recorded for handover offer, acceptance, rejection, dispute and evidence, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "authority", "answer_data": [ "Handover offer, acceptance, rejection, dispute and evidence", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "handover-offer-acceptance-rejection-dispute-and-evidence-q02", "text": "Which source, actor, authority, observation or method establishes handover offer, acceptance, rejection, dispute and evidence, with what evidence, confidence, freshness and limitations?", "kind": "identity", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "handover-offer-acceptance-rejection-dispute-and-evidence-q03", "text": "Which validation, access, transition or correction rule governs handover offer, acceptance, rejection, dispute and evidence, and how are predecessors, successors and external master bindings preserved?", "kind": "ownership", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "handover-offer-acceptance-rejection-dispute-and-evidence-data", "name": "Handover offer, acceptance, rejection, dispute and evidence assertion", "description": "Structured goods-movement answer data for handover offer, acceptance, rejection, dispute and evidence, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "handover-offer-acceptance-rejection-dispute-and-evidence-artifact", "name": "Handover offer, acceptance, rejection, dispute and evidence record", "description": "Versioned logistics record supporting handover offer, acceptance, rejection, dispute and evidence with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "condition-security-and-sensor-bindings", "name": "Condition, security and sensor bindings", "description": "Integrity state and externally mastered telemetry evidence.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-009" ], "findings": [ { "id": "seal-opening-tamper-damage-shortage-and-condition-observation", "name": "Seal, opening, tamper, damage, shortage and condition observation", "description": "Records seal application or break, opening, tamper indication, damage, contamination, shortage, overage and inspection evidence with affected scope and confidence.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "seal-opening-tamper-damage-shortage-and-condition-observation-q01", "text": "What governed logistics assertion is recorded for seal, opening, tamper, damage, shortage and condition observation, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "evidence", "answer_data": [ "Seal, opening, tamper, damage, shortage and condition observation", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "seal-opening-tamper-damage-shortage-and-condition-observation-q02", "text": "Which source, actor, authority, observation or method establishes seal, opening, tamper, damage, shortage and condition observation, with what evidence, confidence, freshness and limitations?", "kind": "definition", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "seal-opening-tamper-damage-shortage-and-condition-observation-q03", "text": "Which validation, access, transition or correction rule governs seal, opening, tamper, damage, shortage and condition observation, and how are predecessors, successors and external master bindings preserved?", "kind": "authority", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "seal-opening-tamper-damage-shortage-and-condition-observation-data", "name": "Seal, opening, tamper, damage, shortage and condition observation assertion", "description": "Structured goods-movement answer data for seal, opening, tamper, damage, shortage and condition observation, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "seal-opening-tamper-damage-shortage-and-condition-observation-artifact", "name": "Seal, opening, tamper, damage, shortage and condition observation record", "description": "Versioned logistics record supporting seal, opening, tamper, damage, shortage and condition observation with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "temperature-shock-humidity-location-and-telemetry-reference", "name": "Temperature, shock, humidity, location and telemetry reference", "description": "Binds summarized condition excursions and sensor-stream evidence by device, calibration, interval, method, threshold, confidence and authoritative telemetry source.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ], "questions": [ { "id": "temperature-shock-humidity-location-and-telemetry-reference-q01", "text": "What governed logistics assertion is recorded for temperature, shock, humidity, location and telemetry reference, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "measurement", "answer_data": [ "Temperature, shock, humidity, location and telemetry reference", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "temperature-shock-humidity-location-and-telemetry-reference-q02", "text": "Which source, actor, authority, observation or method establishes temperature, shock, humidity, location and telemetry reference, with what evidence, confidence, freshness and limitations?", "kind": "classification", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "temperature-shock-humidity-location-and-telemetry-reference-q03", "text": "Which validation, access, transition or correction rule governs temperature, shock, humidity, location and telemetry reference, and how are predecessors, successors and external master bindings preserved?", "kind": "requirement", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "temperature-shock-humidity-location-and-telemetry-reference-data", "name": "Temperature, shock, humidity, location and telemetry reference assertion", "description": "Structured goods-movement answer data for temperature, shock, humidity, location and telemetry reference, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "temperature-shock-humidity-location-and-telemetry-reference-artifact", "name": "Temperature, shock, humidity, location and telemetry reference record", "description": "Versioned logistics record supporting temperature, shock, humidity, location and telemetry reference with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "exceptions-forecast-and-resolution", "name": "Exceptions, forecast and resolution", "description": "Governs deviations, ETA predictions, replanning, mitigation, resolution and external claims.", "rationale": "Delay and exception handling needs explicit affected scope, evidence, uncertainty and plan versions so a prediction or operational workaround does not rewrite history.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010" ], "layers": [ { "id": "exception-detection-and-assessment", "name": "Exception detection and assessment", "description": "Deviation identity, impact, evidence and causality restraint.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "delay-diversion-loss-damage-shortage-misroute-and-hold", "name": "Delay, diversion, loss, damage, shortage, misroute and hold", "description": "Classifies the observed or predicted exception, affected cargo, units, legs and milestones, severity, detected time, source and operational state.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "delay-diversion-loss-damage-shortage-misroute-and-hold-q01", "text": "What governed logistics assertion is recorded for delay, diversion, loss, damage, shortage, misroute and hold, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "classification", "answer_data": [ "Delay, diversion, loss, damage, shortage, misroute and hold", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "delay-diversion-loss-damage-shortage-misroute-and-hold-q02", "text": "Which source, actor, authority, observation or method establishes delay, diversion, loss, damage, shortage, misroute and hold, with what evidence, confidence, freshness and limitations?", "kind": "composition", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "delay-diversion-loss-damage-shortage-misroute-and-hold-q03", "text": "Which validation, access, transition or correction rule governs delay, diversion, loss, damage, shortage, misroute and hold, and how are predecessors, successors and external master bindings preserved?", "kind": "constraint", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "delay-diversion-loss-damage-shortage-misroute-and-hold-data", "name": "Delay, diversion, loss, damage, shortage, misroute and hold assertion", "description": "Structured goods-movement answer data for delay, diversion, loss, damage, shortage, misroute and hold, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "delay-diversion-loss-damage-shortage-misroute-and-hold-artifact", "name": "Delay, diversion, loss, damage, shortage, misroute and hold record", "description": "Versioned logistics record supporting delay, diversion, loss, damage, shortage, misroute and hold with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "cause-contributor-impact-confidence-and-escalation", "name": "Cause, contributor, impact, confidence and escalation", "description": "Separates observed facts, candidate causes and confirmed cause, estimates schedule, quantity, cost or condition impact, and assigns accountable escalation.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009" ], "questions": [ { "id": "cause-contributor-impact-confidence-and-escalation-q01", "text": "What governed logistics assertion is recorded for cause, contributor, impact, confidence and escalation, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "quality", "answer_data": [ "Cause, contributor, impact, confidence and escalation", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "cause-contributor-impact-confidence-and-escalation-q02", "text": "Which source, actor, authority, observation or method establishes cause, contributor, impact, confidence and escalation, with what evidence, confidence, freshness and limitations?", "kind": "relationship", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "cause-contributor-impact-confidence-and-escalation-q03", "text": "Which validation, access, transition or correction rule governs cause, contributor, impact, confidence and escalation, and how are predecessors, successors and external master bindings preserved?", "kind": "process", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "cause-contributor-impact-confidence-and-escalation-data", "name": "Cause, contributor, impact, confidence and escalation assertion", "description": "Structured goods-movement answer data for cause, contributor, impact, confidence and escalation, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "cause-contributor-impact-confidence-and-escalation-artifact", "name": "Cause, contributor, impact, confidence and escalation record", "description": "Versioned logistics record supporting cause, contributor, impact, confidence and escalation with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "eta-replanning-resolution-and-claims", "name": "ETA, replanning, resolution and claims", "description": "Controlled predictions, successor plans and remedy evidence.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010" ], "findings": [ { "id": "eta-method-input-confidence-freshness-and-replanned-route", "name": "ETA method, input, confidence, freshness and replanned route", "description": "Versions estimated arrival or delivery, method and model, input cut-off, confidence, freshness, override, alternative route and successor plan rationale.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010" ], "questions": [ { "id": "eta-method-input-confidence-freshness-and-replanned-route-q01", "text": "What governed logistics assertion is recorded for eta method, input, confidence, freshness and replanned route, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "measurement", "answer_data": [ "ETA method, input, confidence, freshness and replanned route", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "eta-method-input-confidence-freshness-and-replanned-route-q02", "text": "Which source, actor, authority, observation or method establishes eta method, input, confidence, freshness and replanned route, with what evidence, confidence, freshness and limitations?", "kind": "state", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "eta-method-input-confidence-freshness-and-replanned-route-q03", "text": "Which validation, access, transition or correction rule governs eta method, input, confidence, freshness and replanned route, and how are predecessors, successors and external master bindings preserved?", "kind": "event", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "eta-method-input-confidence-freshness-and-replanned-route-data", "name": "ETA method, input, confidence, freshness and replanned route assertion", "description": "Structured goods-movement answer data for eta method, input, confidence, freshness and replanned route, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "eta-method-input-confidence-freshness-and-replanned-route-artifact", "name": "ETA method, input, confidence, freshness and replanned route record", "description": "Versioned logistics record supporting eta method, input, confidence, freshness and replanned route with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "mitigation-resolution-recovery-closure-and-claim-reference", "name": "Mitigation, resolution, recovery, closure and claim reference", "description": "Records proposed and authorized response, action owner, preconditions, effect, reversibility, completion evidence, residual impact and external insurance or legal claim reference.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009" ], "questions": [ { "id": "mitigation-resolution-recovery-closure-and-claim-reference-q01", "text": "What governed logistics assertion is recorded for mitigation, resolution, recovery, closure and claim reference, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "process", "answer_data": [ "Mitigation, resolution, recovery, closure and claim reference", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "mitigation-resolution-recovery-closure-and-claim-reference-q02", "text": "Which source, actor, authority, observation or method establishes mitigation, resolution, recovery, closure and claim reference, with what evidence, confidence, freshness and limitations?", "kind": "lifecycle", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "mitigation-resolution-recovery-closure-and-claim-reference-q03", "text": "Which validation, access, transition or correction rule governs mitigation, resolution, recovery, closure and claim reference, and how are predecessors, successors and external master bindings preserved?", "kind": "measurement", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "mitigation-resolution-recovery-closure-and-claim-reference-data", "name": "Mitigation, resolution, recovery, closure and claim reference assertion", "description": "Structured goods-movement answer data for mitigation, resolution, recovery, closure and claim reference, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "mitigation-resolution-recovery-closure-and-claim-reference-artifact", "name": "Mitigation, resolution, recovery, closure and claim reference record", "description": "Versioned logistics record supporting mitigation, resolution, recovery, closure and claim reference with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "regulatory-governance-and-interoperability", "name": "Regulatory, governance and interoperability", "description": "Connects border controls, access, retention, stakeholder projections, identifiers and external standards without importing their lifecycles.", "rationale": "Cross-organizational logistics combines commercial and sensitive location data, so agents need explicit authority, minimal projections, provenance, pinned mappings and information-loss declarations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010" ], "layers": [ { "id": "border-dangerous-goods-and-regulatory-status", "name": "Border, dangerous-goods and regulatory status", "description": "Typed regulatory interfaces and operational consequences.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008" ], "findings": [ { "id": "customs-declaration-inspection-hold-release-and-clearance-reference", "name": "Customs declaration, inspection, hold, release and clearance reference", "description": "Binds authoritative declaration, inspection, risk decision, hold, release or clearance status, issuer, jurisdiction, validity and permitted logistics action.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ], "questions": [ { "id": "customs-declaration-inspection-hold-release-and-clearance-reference-q01", "text": "What governed logistics assertion is recorded for customs declaration, inspection, hold, release and clearance reference, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "authority", "answer_data": [ "Customs declaration, inspection, hold, release and clearance reference", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "customs-declaration-inspection-hold-release-and-clearance-reference-q02", "text": "Which source, actor, authority, observation or method establishes customs declaration, inspection, hold, release and clearance reference, with what evidence, confidence, freshness and limitations?", "kind": "temporal", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "customs-declaration-inspection-hold-release-and-clearance-reference-q03", "text": "Which validation, access, transition or correction rule governs customs declaration, inspection, hold, release and clearance reference, and how are predecessors, successors and external master bindings preserved?", "kind": "evidence", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "customs-declaration-inspection-hold-release-and-clearance-reference-data", "name": "Customs declaration, inspection, hold, release and clearance reference assertion", "description": "Structured goods-movement answer data for customs declaration, inspection, hold, release and clearance reference, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "customs-declaration-inspection-hold-release-and-clearance-reference-artifact", "name": "Customs declaration, inspection, hold, release and clearance reference record", "description": "Versioned logistics record supporting customs declaration, inspection, hold, release and clearance reference with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "dangerous-goods-permit-certificate-sanction-and-mode-rule-reference", "name": "Dangerous goods, permit, certificate, sanction and mode-rule reference", "description": "Binds classifications, permits, certificates, sanctions screening and mode-specific restrictions by authority and version without claiming universal compliance.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "dangerous-goods-permit-certificate-sanction-and-mode-rule-reference-q01", "text": "What governed logistics assertion is recorded for dangerous goods, permit, certificate, sanction and mode-rule reference, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "constraint", "answer_data": [ "Dangerous goods, permit, certificate, sanction and mode-rule reference", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "dangerous-goods-permit-certificate-sanction-and-mode-rule-reference-q02", "text": "Which source, actor, authority, observation or method establishes dangerous goods, permit, certificate, sanction and mode-rule reference, with what evidence, confidence, freshness and limitations?", "kind": "spatial", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "dangerous-goods-permit-certificate-sanction-and-mode-rule-reference-q03", "text": "Which validation, access, transition or correction rule governs dangerous goods, permit, certificate, sanction and mode-rule reference, and how are predecessors, successors and external master bindings preserved?", "kind": "quality", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "dangerous-goods-permit-certificate-sanction-and-mode-rule-reference-data", "name": "Dangerous goods, permit, certificate, sanction and mode-rule reference assertion", "description": "Structured goods-movement answer data for dangerous goods, permit, certificate, sanction and mode-rule reference, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "dangerous-goods-permit-certificate-sanction-and-mode-rule-reference-artifact", "name": "Dangerous goods, permit, certificate, sanction and mode-rule reference record", "description": "Versioned logistics record supporting dangerous goods, permit, certificate, sanction and mode-rule reference with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "access-provenance-retention-and-projections", "name": "Access, provenance, retention and projections", "description": "Federated rights, evidence preservation and stakeholder-specific views.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010" ], "findings": [ { "id": "role-purpose-field-access-location-privacy-and-audit", "name": "Role, purpose, field access, location privacy and audit", "description": "Applies owner and purpose-based minimum access to cargo, party, value, route, live location, condition and regulatory data with delegation, expiry and audit.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ], "questions": [ { "id": "role-purpose-field-access-location-privacy-and-audit-q01", "text": "What governed logistics assertion is recorded for role, purpose, field access, location privacy and audit, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "access", "answer_data": [ "Role, purpose, field access, location privacy and audit", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "role-purpose-field-access-location-privacy-and-audit-q02", "text": "Which source, actor, authority, observation or method establishes role, purpose, field access, location privacy and audit, with what evidence, confidence, freshness and limitations?", "kind": "provenance", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "role-purpose-field-access-location-privacy-and-audit-q03", "text": "Which validation, access, transition or correction rule governs role, purpose, field access, location privacy and audit, and how are predecessors, successors and external master bindings preserved?", "kind": "validation", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "role-purpose-field-access-location-privacy-and-audit-data", "name": "Role, purpose, field access, location privacy and audit assertion", "description": "Structured goods-movement answer data for role, purpose, field access, location privacy and audit, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "role-purpose-field-access-location-privacy-and-audit-artifact", "name": "Role, purpose, field access, location privacy and audit record", "description": "Versioned logistics record supporting role, purpose, field access, location privacy and audit with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "evidence-provenance-retention-hold-and-stakeholder-projection", "name": "Evidence provenance, retention, hold and stakeholder projection", "description": "Preserves sources, activities, agents, revisions, digests, retention, legal hold and tombstones and generates shipper, carrier, consignee, regulator or public views.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010" ], "questions": [ { "id": "evidence-provenance-retention-hold-and-stakeholder-projection-q01", "text": "What governed logistics assertion is recorded for evidence provenance, retention, hold and stakeholder projection, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "retention", "answer_data": [ "Evidence provenance, retention, hold and stakeholder projection", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "evidence-provenance-retention-hold-and-stakeholder-projection-q02", "text": "Which source, actor, authority, observation or method establishes evidence provenance, retention, hold and stakeholder projection, with what evidence, confidence, freshness and limitations?", "kind": "ownership", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "evidence-provenance-retention-hold-and-stakeholder-projection-q03", "text": "Which validation, access, transition or correction rule governs evidence provenance, retention, hold and stakeholder projection, and how are predecessors, successors and external master bindings preserved?", "kind": "security", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "evidence-provenance-retention-hold-and-stakeholder-projection-data", "name": "Evidence provenance, retention, hold and stakeholder projection assertion", "description": "Structured goods-movement answer data for evidence provenance, retention, hold and stakeholder projection, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "evidence-provenance-retention-hold-and-stakeholder-projection-artifact", "name": "Evidence provenance, retention, hold and stakeholder projection record", "description": "Versioned logistics record supporting evidence provenance, retention, hold and stakeholder projection with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "identifiers-vocabularies-and-mappings", "name": "Identifiers, vocabularies and mappings", "description": "Authority-aware federation and loss-declared exchange.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "findings": [ { "id": "party-goods-unit-equipment-location-event-and-document-identifier", "name": "Party, goods, unit, equipment, location, event and document identifier", "description": "Resolves authoritative identifiers, issuer, scope, validity, aliases and collisions for all referenced logistics objects and observations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "party-goods-unit-equipment-location-event-and-document-identifier-q01", "text": "What governed logistics assertion is recorded for party, goods, unit, equipment, location, event and document identifier, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "identity", "answer_data": [ "Party, goods, unit, equipment, location, event and document identifier", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "party-goods-unit-equipment-location-event-and-document-identifier-q02", "text": "Which source, actor, authority, observation or method establishes party, goods, unit, equipment, location, event and document identifier, with what evidence, confidence, freshness and limitations?", "kind": "authority", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "party-goods-unit-equipment-location-event-and-document-identifier-q03", "text": "Which validation, access, transition or correction rule governs party, goods, unit, equipment, location, event and document identifier, and how are predecessors, successors and external master bindings preserved?", "kind": "privacy", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "party-goods-unit-equipment-location-event-and-document-identifier-data", "name": "Party, goods, unit, equipment, location, event and document identifier assertion", "description": "Structured goods-movement answer data for party, goods, unit, equipment, location, event and document identifier, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "party-goods-unit-equipment-location-event-and-document-identifier-artifact", "name": "Party, goods, unit, equipment, location, event and document identifier record", "description": "Versioned logistics record supporting party, goods, unit, equipment, location, event and document identifier with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "uncefact-epcis-cbv-dcsa-one-record-wco-imo-crosswalk-and-loss", "name": "UN/CEFACT, EPCIS, CBV, DCSA, ONE Record, WCO and IMO crosswalk and loss", "description": "Pins source and target versions, maps objects, events, codes and time semantics, validates projections and declares omissions or non-round-trippable meaning.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "uncefact-epcis-cbv-dcsa-one-record-wco-imo-crosswalk-and-loss-q01", "text": "What governed logistics assertion is recorded for un/cefact, epcis, cbv, dcsa, one record, wco and imo crosswalk and loss, for which movement, consignment, cargo scope, leg, location, time and revision?", "kind": "interoperability", "answer_data": [ "UN/CEFACT, EPCIS, CBV, DCSA, ONE Record, WCO and IMO crosswalk and loss", "movement, cargo and leg scope", "location, time, state and revision" ] }, { "id": "uncefact-epcis-cbv-dcsa-one-record-wco-imo-crosswalk-and-loss-q02", "text": "Which source, actor, authority, observation or method establishes un/cefact, epcis, cbv, dcsa, one record, wco and imo crosswalk and loss, with what evidence, confidence, freshness and limitations?", "kind": "requirement", "answer_data": [ "source, actor and authority", "observation or method and evidence", "confidence, freshness and limitations" ] }, { "id": "uncefact-epcis-cbv-dcsa-one-record-wco-imo-crosswalk-and-loss-q03", "text": "Which validation, access, transition or correction rule governs un/cefact, epcis, cbv, dcsa, one record, wco and imo crosswalk and loss, and how are predecessors, successors and external master bindings preserved?", "kind": "retention", "answer_data": [ "validation and access rule", "authorized transition and effective time", "predecessor, successor and external reference" ] } ], "data_elements": [ { "id": "uncefact-epcis-cbv-dcsa-one-record-wco-imo-crosswalk-and-loss-data", "name": "UN/CEFACT, EPCIS, CBV, DCSA, ONE Record, WCO and IMO crosswalk and loss assertion", "description": "Structured goods-movement answer data for un/cefact, epcis, cbv, dcsa, one record, wco and imo crosswalk and loss, including object scope, place, time, state, source and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "uncefact-epcis-cbv-dcsa-one-record-wco-imo-crosswalk-and-loss-artifact", "name": "UN/CEFACT, EPCIS, CBV, DCSA, ONE Record, WCO and IMO crosswalk and loss record", "description": "Versioned logistics record supporting un/cefact, epcis, cbv, dcsa, one record, wco and imo crosswalk and loss with evidence, provenance and access marking.", "media_or_form": [ "structured movement assertion", "event or decision statement", "resolvable evidence or master-system index" ], "serial": true, "identity_strategy": "Authoritative logistics master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-goods-movement", "name": "Register goods movement", "description": "Create governed movement, shipment and consignment identities with scope, parties, profile and initial revision.", "inputs": [ "movement purpose", "cargo scope", "party roles" ], "outputs": [ "goods-movement master revision" ], "preconditions": [ "Dimension and authoritative namespaces resolve" ], "effects": [ "a governed logistics aggregate exists without implying dispatch or delivery" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "bind-cargo-and-handling-units", "name": "Bind cargo and handling units", "description": "Attach referenced goods, quantities, packages, handling units, equipment and containment versions.", "inputs": [ "movement", "goods references", "packing hierarchy" ], "outputs": [ "cargo-composition revision" ], "preconditions": [ "identifiers, units and parent-child constraints validate" ], "effects": [ "movement scope becomes explicit without importing goods masters" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "create-or-revise-route-plan", "name": "Create or revise route plan", "description": "Define origin, destination, route alternatives, ordered legs, modes, parties, means, locations and schedules.", "inputs": [ "movement", "routing requirements", "capacity and constraints" ], "outputs": [ "route-plan revision" ], "preconditions": [ "locations, modes and dependencies resolve" ], "effects": [ "a versioned plan exists while prior intent remains immutable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "record-logistics-observation", "name": "Record logistics observation", "description": "Append pickup, loading, departure, arrival, transfer, unloading, delivery or return evidence.", "inputs": [ "movement object", "event assertion", "source evidence" ], "outputs": [ "logistics event revision" ], "preconditions": [ "actor, time, place, affected objects and source validate" ], "effects": [ "derived state may change under deterministic precedence" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "correct-or-invalidate-observation", "name": "Correct or invalidate observation", "description": "Create an error declaration, correction or invalidating successor without rewriting the source event.", "inputs": [ "prior observation", "correction", "authority and reason" ], "outputs": [ "successor event revision" ], "preconditions": [ "correction authority and evidence resolve" ], "effects": [ "prior data remains resolvable and marked" ], "source_refs": [ "SRC-003", "SRC-009", "SRC-010" ] }, { "id": "record-custody-handover", "name": "Record custody handover", "description": "Append offered, accepted, rejected or disputed transfer of possession or responsibility with proof.", "inputs": [ "object scope", "from and to roles", "handover evidence" ], "outputs": [ "custody-transition revision" ], "preconditions": [ "roles, authority, place, time and evidence validate" ], "effects": [ "custody interval changes without implying title or ownership" ], "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] }, { "id": "record-condition-or-integrity-observation", "name": "Record condition or integrity observation", "description": "Attach seal, damage, shortage, temperature or other condition evidence and external telemetry references.", "inputs": [ "movement object", "condition observation", "evidence source" ], "outputs": [ "condition assertion" ], "preconditions": [ "device or observer, method, interval and affected scope resolve" ], "effects": [ "condition history becomes available without importing sensor lifecycle" ], "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "predict-eta-and-replan", "name": "Predict ETA and replan", "description": "Version predicted milestones and create a successor route plan with model provenance and uncertainty.", "inputs": [ "active plan", "observations", "prediction method" ], "outputs": [ "ETA revision", "optional successor plan" ], "preconditions": [ "input cut-off, method, confidence and permissions resolve" ], "effects": [ "prediction changes without overwriting actual events or prior plan" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010" ] }, { "id": "open-assess-and-resolve-exception", "name": "Open, assess and resolve exception", "description": "Register deviation, affected scope, evidence, candidate causes, impact, response, recovery and closure.", "inputs": [ "movement", "exception evidence", "assessment" ], "outputs": [ "exception revision", "resolution record" ], "preconditions": [ "classification, severity, owner and escalation policy resolve" ], "effects": [ "accountable mitigation proceeds while causal uncertainty stays visible" ], "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] }, { "id": "bind-regulatory-status", "name": "Bind regulatory status", "description": "Attach customs, inspection, hold, release, dangerous-goods, permit or certificate references and permitted effects.", "inputs": [ "movement or leg", "authority record", "jurisdiction" ], "outputs": [ "regulatory-status binding" ], "preconditions": [ "issuer, validity, scope and action semantics validate" ], "effects": [ "logistics actions reflect an external decision without copying its lifecycle" ], "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] }, { "id": "reconcile-external-identifiers-and-events", "name": "Reconcile external identifiers and events", "description": "Map carrier, platform and standards identities and observations with confidence and conflict history.", "inputs": [ "external identifiers", "candidate records", "matching rules" ], "outputs": [ "equivalence or non-equivalence assertion" ], "preconditions": [ "authority, scope, time and collision checks pass" ], "effects": [ "federated records link without silent merge or last-write-wins" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-009" ] }, { "id": "issue-tracking-projection-or-export", "name": "Issue tracking projection or export", "description": "Generate stakeholder-specific tracking or standards projections with validation, redaction and loss declaration.", "inputs": [ "movement revision", "recipient purpose", "target profile" ], "outputs": [ "tracking projection", "validation report" ], "preconditions": [ "version, permissions, freshness and mapping resolve" ], "effects": [ "minimum authorized data is shared with provenance and declared loss" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "composition": [ { "target": "Goods, Product, Lot, Package and Handling Unit models", "relation": "REFERENCE", "purpose": "Identifies what moves and its transport aggregation without importing object mastership.", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "target": "Vehicle, Equipment, Facility, Location, Party and Organization models", "relation": "REFERENCE", "purpose": "Resolves means, containers, places and role players by authoritative external identity.", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] }, { "target": "Contract, Order, Inventory, Customs, Permit, Invoice, Payment, Sensor, Evidence and Claim models", "relation": "REFERENCE", "purpose": "Connects commercial, regulatory, financial, telemetry and evidentiary records without importing their lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ] }, { "target": "UN/CEFACT Multi Modal Transport Reference Data Model", "relation": "ALIGN", "purpose": "Supports syntax-neutral multimodal transport semantics with a pinned release and declared local extensions.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "GS1 EPCIS 2.0.1 and CBV 2.0", "relation": "ALIGN", "purpose": "Supports visibility-event and vocabulary projections without equating an observation with legal proof.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "DCSA Track and Trace 2.2 and IATA ONE Record 3.2.0", "relation": "ALIGN", "purpose": "Supports container-shipping and air-cargo profiles while preserving the mode-neutral core.", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] }, { "target": "WCO Data Model and IMO FAL", "relation": "ALIGN", "purpose": "Supports cross-border and maritime regulatory projections without asserting jurisdictional compliance from structure alone.", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, movement steward, shipper, carrier and handling authorities, party and goods masters, regulatory interfaces, evidence custodian and disclosure authority.", "Declare shipment, consignment, goods, package, handling-unit, equipment, vehicle, facility, route, contract, customs, sensor, document and party master systems.", "Publish model, object, event, relation, identifier, location, access, retention, assurance and interoperability registries.", "Pin mode, jurisdiction, dangerous-goods, customs, identifier, event-vocabulary, privacy, retention and exchange profiles." ], "namespace_guidance": "Mint movement, shipment, consignment, route, leg, observation, exception and revision identifiers only in the adopting Dimension's governed namespace; preserve goods, handling-unit, equipment, vehicle, party, facility, contract, customs, sensor and document identifiers as typed external references with authority, version and time.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local movement, shipment, location, identifier, event, access and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, authoritative logistics master ID, immutable revision, object class, scope and issuer; never use tracking number, status, place, timestamp, filename or hash alone as identity.", "Keep movement, shipment, consignment, booking, cargo item, package, handling unit, equipment, route, leg, observation, custody assertion and regulatory record distinct and preserve corrections and supersession." ], "patch_rules": [ "Additive extensions use a Dimension-owned namespace and declare target node, mode or cargo profile, authority, source, rationale, access, event and interoperability impact.", "Breaking changes require a new version, migration and crosswalk maps, compatibility declaration and continued resolution of prior plans, events and external identifiers." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when movement identity, object class, scope, place, time kind, state, authority, provenance and access meaning remain intact.", "UN/CEFACT, EPCIS, CBV, DCSA, ONE Record, WCO and IMO mappings pin source and target versions and declare transformed, omitted or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "Authoritative logistics master-system identifier and immutable revision identifier.", "Governed globally resolvable movement, consignment, leg or event 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 requested, planned, estimated, predicted, actual, sensor, capture, record, correction and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {movement-id}--{artifact-kind}--{revision-or-event-id}; never use a tracking number, status, place, date, filename or hash alone as movement identity.", "integrity_rule": "Store digest, media type, byte length, issuer, source and vocabulary versions, object scope, event and record times, provenance, assurance and access marking for every retained serial artifact." }, "policies": [ "The adopting Dimension declares who may plan, book, bind cargo, observe, hand over, correct, replan, classify exceptions, bind regulatory status, disclose, retain and tombstone logistics records.", "Every movement assertion requires subject class and identity, cargo or equipment scope, leg or route context, place, time kind, source, authority, confidence, status and revision lineage as applicable.", "Agents never infer physical occurrence, custody, title, ownership, delivery acceptance, customs clearance, compliance or claim liability from a plan, estimate, scan or status code alone.", "Goods, handling units, equipment, vehicles, parties, facilities, contracts, customs records, permits, invoices, payments, sensor streams, evidence and documents remain in their owning systems and are referenced.", "Automated agents may append low-risk observations, predictions, reconciliations and projections under delegation, but custody acceptance, route changes with material risk, regulatory action, consequential disclosure and irreversible deletion default to confirmation or accountable authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, movement profile, object scope, time horizon, requested revision, assurance, freshness and access policy; return the minimum permitted projection." ], "create": [ "Create stable movement identity, class, scope, parties, cargo references, origin, destination, period, source, authority and explicit unknowns before planning or observation." ], "update": [ "Append an immutable plan, event or assertion revision with actor, authority, reason, RFC 3339 effective time and predecessor; validate identifiers, containment, route, time, evidence and access before and after mutation." ], "delete": [ "Apply carriage, customs, insurance, dispute, audit, retention and legal-hold policy; tombstone eligible records or withdraw projections while preserving identity, material observations and non-cascading external references." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, access, retention and federation rules." ] }, { "name": "Movement or shipment steward", "responsibilities": [ "Own movement scope, plan, cargo bindings, service requirements and reconciliation." ] }, { "name": "Carrier or handling operator", "responsibilities": [ "Own the legs, handling actions, custody segments, observations and exceptions it performs." ] }, { "name": "Cargo, equipment or facility steward", "responsibilities": [ "Maintain authoritative referenced object identity, properties, condition and availability." ] }, { "name": "Regulatory authority", "responsibilities": [ "Own declarations, inspections, holds, releases, permits and jurisdictional decisions." ] }, { "name": "Data and interoperability steward", "responsibilities": [ "Govern identifiers, vocabularies, event semantics, mappings, quality and loss declarations." ] }, { "name": "Reviewer, auditor or claims authority", "responsibilities": [ "Review evidence, custody, exceptions, corrections and disputes without rewriting originals." ] }, { "name": "Disclosure authority", "responsibilities": [ "Approve recipient, purpose, live-location exposure, confidentiality, redaction and publication timing." ] } ], "access": { "default_rule": "Deny mutation and sensitive disclosure unless the active Dimension, role, purpose, movement profile, object scope, location sensitivity and field policy grant the action; expose the minimum necessary projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency access must be time-limited, purpose-bound, attributable, independently reviewed and unable to erase immutable movement, custody, regulatory, correction or legal-hold evidence." ], "audit_requirements": [ "Log actor, role, purpose, movement and revision identity, action, decision, policy and vocabulary versions, RFC 3339 timestamp with offset, affected objects and legs, source evidence and outcome for privileged mutation, custody, regulatory use 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, movement authority, active mode, jurisdiction, dangerous-goods, identifier, access, retention and disclosure policies.", "Read this model AGENTS.md, pinned spec.yaml and required goods, handling-unit, equipment, vehicle, party, facility, contract, customs, sensor, evidence and document model instructions before mutation." ] } }, "coverage": { "claim": "A source-grounded reviewable draft of Goods Movement / Logistics across UN/CEFACT, UN/LOCODE, GS1 EPCIS and CBV, DCSA, IATA ONE Record, WCO, IMO, W3C provenance and IETF time standards, without a claim of universal mode, jurisdiction, dangerous-goods, customs or legal-proof completeness.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Movement, shipment, consignment, booking, cargo line, package, handling unit, equipment, route, leg, event, exception and revision identities are distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Object class, mode, role, event type, business step, disposition, exception, condition and regulatory profile are versioned." }, { "dimension": "direct properties", "status": "covered", "notes": "The informational movement object's scope, status, route, schedule, cargo bindings and constraints are covered; physical properties of goods, equipment and vehicles remain in their masters." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Agents distinguish plan, estimate, actual observation, correction, custody assertion and external authority decision by type, source, actor, time and evidence." }, { "dimension": "lifecycle", "status": "covered", "notes": "Registration, planning, booking reference, pickup, movement, transfer, delivery, return, exception, correction, replanning, closure and tombstone preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Cargo, packages, units, equipment, legs, locations, parties, custody intervals, contracts, customs records, sensors and evidence use typed bindings." }, { "dimension": "temporal", "status": "covered", "notes": "Requested, planned, cut-off, estimated, predicted, actual, sensor, capture, record, correction and ingestion times remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Origins, destinations, waypoints, facilities, read points, business locations, coordinates, functions, corridors and uncertainty are explicit." }, { "dimension": "provenance", "status": "covered", "notes": "Sources, actors, activities, methods, observations, corrections, estimates, evidence snapshots and successor revisions are linked." }, { "dimension": "ownership", "status": "covered", "notes": "Dimension owner, movement steward, carrier, handler, object steward, regulator, reviewer and disclosure authority have separate responsibilities." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, containment, quantity, unit, route order, time, event precedence, custody, condition, regulatory and crosswalk checks are explicit." }, { "dimension": "access", "status": "covered", "notes": "Role, purpose, delegation, field-level controls, live-location sensitivity, redaction, emergency access and audit are represented." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Immutable observations, corrections, custody and regulatory evidence, retention, legal hold, withdrawal and tombstones are explicit." }, { "dimension": "interoperability", "status": "covered", "notes": "UN/CEFACT, UN/LOCODE, EPCIS, CBV, DCSA, ONE Record, WCO and IMO profiles pin versions and disclose loss." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Registration, cargo binding, route planning, observation, correction, handover, condition capture, ETA, exception, regulatory binding, reconciliation and projection functions declare controlled effects." } ], "known_omissions": [ "Mode, jurisdiction, dangerous-goods, customs, carriage, liability, insurance, sanctions, privacy and retention profiles require exact current rules and competent review.", "Goods, product, lot, package, handling-unit, equipment, vehicle, facility, party, contract, customs, invoice, payment, sensor, evidence and claim lifecycles remain in neighboring masters.", "Certified field-level crosswalks, carrier-specific code mappings, routing algorithms, ETA validation suites and legal proof requirements remain future work." ], "conflicts": [ "Shipment, consignment and transport movement overlap across standards; this aggregate preserves typed local concepts and requires explicit crosswalks rather than choosing one vocabulary as universal.", "EPCIS and carrier tracking events are observations with business context, not automatic proof of custody, title, ownership, delivery acceptance or regulatory compliance.", "Generic logistics must support multiple modes while mode-specific operational, safety and regulatory semantics remain governed profiles and references." ], "regional_assumptions": [ "WCO and IMO sources define cross-border and maritime profiles, not universal requirements for domestic or non-maritime movement.", "DCSA Track and Trace 2.2 specializes container shipping and IATA ONE Record 3.2.0 specializes air cargo; neither is treated as the generic ontology alone.", "UN/LOCODE release content changes under an official maintenance process, so adopting Dimensions must retain directory version and status." ], "adversarial_checks": [ "Reject merging shipment, consignment, booking, cargo item, package, handling unit and transport equipment solely because one provider uses a shared identifier.", "Reject actual movement, custody, delivery acceptance, clearance or compliance inferred only from a plan, ETA, scan, status label or API response.", "Reject last-write-wins when carrier events conflict; preserve source, event time, record time, correction lineage, confidence and deterministic precedence.", "Reject an ETA or route change that overwrites actual events or the prior plan or omits model, input cut-off, confidence, authority and successor rationale.", "Reject copying goods, vehicle, facility, customs, contract, payment, sensor or claim lifecycles into the movement record when authoritative typed references suffice." ] }, "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 typed logistics objects and profiles", "rationale": "Movement, shipment, consignment, cargo composition, route, leg, observation, custody assertion and exception form one operational context aggregate, while physical, commercial, regulatory, sensor and evidentiary masters remain external references." }, "decisions": [ { "concept": "Shipment, consignment and movement", "disposition": "accepted as distinct linked identities", "rationale": "Standards overlap in terminology, so the model records class, authority and mapping instead of treating carrier identifiers as universal synonyms." }, { "concept": "Cargo, package, handling unit and equipment", "disposition": "accepted as distinct whole-part references", "rationale": "Transport aggregation may change without changing the goods, and equipment contains handling units without becoming their product identity." }, { "concept": "Physical mastership", "disposition": "accepted as external references", "rationale": "Goods, lots, packages, equipment, vehicles, facilities and sensors retain their direct physical properties and lifecycle outside the movement aggregate." }, { "concept": "Plan, estimate and observation", "disposition": "accepted as separate assertion kinds", "rationale": "Requested, planned, estimated, predicted, actual, corrected, record and ingestion times cannot overwrite or substitute for one another." }, { "concept": "Operational state", "disposition": "accepted as derived state", "rationale": "Status derives from append-only observations, authority, time and deterministic precedence rather than last-write-wins." }, { "concept": "Custody and ownership", "disposition": "accepted as separate relations", "rationale": "Possession, operational control, carrier responsibility, custody, stewardship, title and ownership may differ by object and interval." }, { "concept": "Tracking evidence", "disposition": "accepted with proof limitations", "rationale": "A scan or EPCIS-style event is an observation with business context and is not automatic proof of physical occurrence, custody, delivery acceptance or compliance." }, { "concept": "ETA and replanning", "disposition": "accepted as versioned predictions and successor plans", "rationale": "Predictions retain model, inputs, cut-off, confidence and override provenance, and replanning preserves original intent and actual history." }, { "concept": "Customs and regulatory boundary", "disposition": "accepted as authoritative external bindings", "rationale": "The movement records operational consequences of holds, releases, permits and certificates while border authorities own their decisions and lifecycle." }, { "concept": "Mode-specific standards", "disposition": "accepted as optional profiles", "rationale": "DCSA and IATA specialize ocean-container and air-cargo exchange while the base remains mode-neutral and uses pinned mappings." }, { "concept": "Access and live location", "disposition": "accepted as minimum stakeholder projections", "rationale": "Cargo, party, value, route, condition and current-location detail can be commercially, personally or operationally sensitive and requires purpose-bound field access." }, { "concept": "Question and function coverage", "disposition": "accepted as reviewable draft", "rationale": "The structure covers identity, composition, planning, observation, custody, condition, exceptions, actions, regulatory interfaces, validation, provenance, access, retention and interoperability, but specialist profiles still require review." } ], "publicationHolds": [ "Claude and Grok timed out during their bounded attempts, so independent external review is absent and explicitly waived for this published reviewable draft.", "The approved relationship ledger contains no outgoing relation rows for WM-FLW-004, so proposed composition links remain draft until registry governance approves sibling identifiers and cardinalities.", "Mode, jurisdiction, customs, dangerous-goods, sanctions, carriage, liability, insurance, delivery-proof, privacy and retention profiles require competent specialist review before operational enforcement.", "Certified UN/CEFACT, EPCIS, CBV, DCSA, ONE Record, WCO and IMO field crosswalks, conformance fixtures, identifier mappings and event-precedence suites remain unverified.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Validate the base against road, rail, maritime, inland-waterway, air, parcel, courier, cold-chain, dangerous-goods and humanitarian-logistics profiles.", "Create jurisdiction and mode-specific custody, clearance, carrier-liability, proof, dispute, retention and disclosure recipes.", "Develop deterministic validation fixtures for containment, split and consolidation, route order, multimodal transfer, event correction, derived status, ETA and exception resolution.", "Approve sibling model identifiers and relation cardinalities for shipment, handling units, goods, vehicles, facilities, locations, parties, contracts, customs, sensors, evidence and claims." ] }, "statistics": { "sources": 10, "bundles": 7, "layers": 16, "findings": 32, "questions": 96, "artifacts": 32, "functions": 12 } }