# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T21:04:57Z", "synthesisSha256": "4b4955fb2d7ea859fbcfd2b29cf70973cd2ee6f7a501afc6de04c00f57300312", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-FLW-012", "registryId": "vr.wm-flw-012", "name": "Inventory Movement", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "event", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.FLW.LOG" ], "tags": [ "inventory", "movement", "phy.flw.log" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-flw-012-inventory-movement/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-012", "model": { "registry_id": "vr.wm-flw-012", "model_id": "WM-FLW-012", "name": "Inventory Movement", "entry_kind": "event", "purpose": "Represent one governed stock-affecting movement assertion, its subject, quantity, source-destination transition, execution and posting references, evidence and correction lineage without becoming the inventory position, ledger, product, location, task or shipment.", "scope_statement": "Owns movement identity and revision; assertion kind, class, direction and reason; idempotency and correction lineage; item, lot, serial and handling-unit scope references; qualified quantity; source and destination position, location, owner, custodian, status and disposition references; request, order, reservation, task, production and shipment triggers; lifecycle and clocks; execution observations; external authoritative posting references; exceptions, reconciliation, provenance, access, retention and loss-aware projections. Product, lot, serial, handling unit, location, stock position and balance, order, warehouse task, production, shipment, journey, chain of custody, ledger, valuation, accounting, document, observation, incident and evidence masters remain external.", "in_scope": [ "Movement identity, class, assertion kind, revision, idempotency, direction, reason and successor lineage", "Stock-subject scope, qualified quantity, source-destination and stock-bucket transition references, triggers, execution and posting assertions", "Lifecycle clocks, evidence, exceptions, reconciliation, governance, access, retention and interoperability" ], "out_of_scope": [ "Owning product, material, lot, serial, handling unit, place, inventory position, stock balance, order, reservation, task, production, shipment, journey, trace, ledger, valuation, accounting, document, observation, incident or evidence lifecycles", "Equating request with execution, physical movement with posting, custody with ownership, location with stock status, position with movement, count discrepancy with adjustment or shipment milestone with inventory receipt", "Executing warehouse operations, inventory ledger mutation, accounting posting, autonomous physical handling, safety decisions, protected disclosure or irreversible deletion" ], "boundary_notes": [ { "neighbor": "WM-OBJ-020 Inventory Stock Position", "distinction": "Inventory Movement references before-and-after positions and may support an externally calculated balance change. Position identity, balance computation and snapshot lifecycle remain external; the candidate parent signal is held for review.", "source_refs": [ "SRC-007", "SRC-008", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ] }, { "neighbor": "WM-FLW-011 Shipment / Consignment", "distinction": "A shipment groups goods and logistics obligations. Inventory Movement owns a stock-affecting transition that may be triggered or evidenced by despatch or receipt but does not own the shipment.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009", "SRC-010" ] }, { "neighbor": "WM-FLW-013 Supply-chain Trace / Chain of Custody", "distinction": "Inventory Movement owns one movement assertion and its correction lineage. Cross-organizational critical-event graphs and custody proof remain externally mastered.", "source_refs": [ "SRC-001", "SRC-006", "SRC-020" ] }, { "neighbor": "Product, lot, serial and handling unit", "distinction": "The movement binds subject identities and aggregation scope. Their descriptive properties, composition, condition and independent lifecycles remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] }, { "neighbor": "Order, reservation, warehouse task and production", "distinction": "These objects trigger or authorize planned work. Inventory Movement records their references and observed effects but not their workflow or resource scheduling.", "source_refs": [ "SRC-005", "SRC-007", "SRC-017", "SRC-018" ] }, { "neighbor": "Inventory ledger, valuation and accounting", "distinction": "The model records external posting identity, authority, time and result reference. It does not calculate balances, cost inventory or create accounting entries.", "source_refs": [ "SRC-008", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ] }, { "neighbor": "Observation, document, incident and evidence", "distinction": "Scans, counts, sensor readings, receipt or despatch documents and incident records are independently governed evidence references, not the movement identity or automatic master truth.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-009", "SRC-010", "SRC-020", "SRC-021" ] } ] }, "sources": [ { "id": "SRC-001", "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-06T21:05:00Z", "relevance": "Defines visibility events, object and quantity scope, event and record clocks, locations, sources, destinations and corrections." }, { "id": "SRC-002", "title": "EPCIS ObjectEvent linked-data definition", "organization": "GS1", "url": "https://ref.gs1.org/epcis/ObjectEvent", "version_or_date": "EPCIS linked-data model accessed 2026-09-06", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines instance and class-level object observations, quantities, actions, business steps, dispositions and endpoints." }, { "id": "SRC-003", "title": "EPCIS AggregationEvent linked-data definition", "organization": "GS1", "url": "https://ref.gs1.org/epcis/AggregationEvent", "version_or_date": "EPCIS linked-data model accessed 2026-09-06", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines parent-child aggregation changes used as evidence for handling-unit composition." }, { "id": "SRC-004", "title": "EPCIS TransformationEvent linked-data definition", "organization": "GS1", "url": "https://ref.gs1.org/epcis/TransformationEvent", "version_or_date": "EPCIS linked-data model accessed 2026-09-06", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Separates transformation inputs and outputs from ordinary relocation or stock transfer." }, { "id": "SRC-005", "title": "Core Business Vocabulary Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/cbv/2.0.0/", "version_or_date": "CBV 2.0.0, June 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines controlled business steps and dispositions including shipping, receiving, storing, picking and stocking." }, { "id": "SRC-006", "title": "GS1 Global Traceability Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/global-traceability/2.0.0/", "version_or_date": "Release 2.0, August 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines critical tracking events and key data elements for traceability across supply chains." }, { "id": "SRC-007", "title": "Universal Business Language Version 2.4", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html", "version_or_date": "OASIS Standard, 20 June 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines inventory, despatch and receipt document structures and fulfilment business rules." }, { "id": "SRC-008", "title": "UBL 2.4 Inventory Report schema", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/os-UBL-2.4/mod/summary/reports/UBL-InventoryReport-2.4.html", "version_or_date": "UBL 2.4, 20 June 2024", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines inventory-report lines, quantities, periods, locations and item references." }, { "id": "SRC-009", "title": "UBL 2.4 Receipt Advice schema", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/os-UBL-2.4/mod/summary/reports/UBL-ReceiptAdvice-2.4.html", "version_or_date": "UBL 2.4, 20 June 2024", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Supports receipt confirmation, received, short and rejected quantities and rejection reasons." }, { "id": "SRC-010", "title": "UBL 2.4 Despatch Advice schema", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/os-UBL-2.4/mod/summary/reports/UBL-DespatchAdvice-2.4.html", "version_or_date": "UBL 2.4, 20 June 2024", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Supports full and partial despatch, order-line references and transport handling units." }, { "id": "SRC-011", "title": "UN/EDIFACT code list 4501 Inventory movement direction", "organization": "UN/CEFACT", "url": "https://service.unece.org/trade/uncefact/vocabulary/uncl4501/", "version_or_date": "UNCL 4501 vocabulary accessed 2026-09-06", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Distinguishes movement into inventory from movement out of inventory." }, { "id": "SRC-012", "title": "UN/EDIFACT data element 4499 Inventory movement reason", "organization": "UN/CEFACT", "url": "https://service.unece.org/trade/untdid/d21a/tred/tred4499.htm", "version_or_date": "D.21A", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines coded reasons for inventory movement." }, { "id": "SRC-013", "title": "UN/EDIFACT data element 4503 Inventory balance method", "organization": "UN/CEFACT", "url": "https://service.unece.org/trade/untdid/d21a/tred/tred4503.htm", "version_or_date": "D.21A", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines methods used to establish inventory balance." }, { "id": "SRC-014", "title": "UN/EDIFACT data element 6063 Quantity type code qualifier", "organization": "UN/CEFACT", "url": "https://service.unece.org/trade/untdid/d21a/tred/tred6063.htm", "version_or_date": "D.21A", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Includes inventory movement, opening balance, closing balance and replenishment quantity semantics." }, { "id": "SRC-015", "title": "Recommendation No. 20 Codes for Units of Measure", "organization": "UN/CEFACT", "url": "https://unece.org/trade/uncefact/cl-recommendations", "version_or_date": "Recommendation 20 and current code lists accessed 2026-09-06", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines coded units required for interoperable inventory quantities and measurements." }, { "id": "SRC-016", "title": "UN/CEFACT Core Component Library", "organization": "UN/CEFACT", "url": "https://unece.org/trade/uncefact/core-component-library", "version_or_date": "Current CCL overview accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Provides syntax-neutral reusable business information components for supply-chain exchange." }, { "id": "SRC-017", "title": "ISA-95 Standard: Enterprise-Control System Integration", "organization": "International Society of Automation", "url": "https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard", "version_or_date": "ISA-95 series overview accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines abstract information exchange boundaries between enterprise and manufacturing control functions." }, { "id": "SRC-018", "title": "IEC 62264-2:2013 Enterprise-control system integration", "organization": "International Electrotechnical Commission", "url": "https://webstore.iec.ch/en/publication/6675", "version_or_date": "IEC 62264-2:2013", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines object and attribute models for enterprise-control integration, including material information exchanges." }, { "id": "SRC-019", "title": "RFC 3339 Date and Time on the Internet", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines timestamps with seconds and explicit numeric offsets or Z." }, { "id": "SRC-020", "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-06T21:05:00Z", "relevance": "Defines activities, entities, agents, attribution, derivation, revision and invalidation." }, { "id": "SRC-021", "title": "Data Quality Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "W3C Working Group Note, 15 December 2016", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines quality measurements, annotations, policies and provenance." }, { "id": "SRC-022", "title": "ODRL Information Model 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "W3C Recommendation, 15 February 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines permissions, prohibitions, duties and constraints for governed data use." }, { "id": "SRC-023", "title": "XML Schema Part 2: Datatypes Second Edition", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/xmlschema-2/", "version_or_date": "W3C Recommendation, 28 October 2004", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Defines decimal, dateTime and datatype semantics used by standards projections." }, { "id": "SRC-024", "title": "ISO 8000-110:2021 Data quality", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/80264.html", "version_or_date": "ISO 8000-110:2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:05:00Z", "relevance": "Provides master-data exchange requirements relevant to identifiers, provenance and quality declarations." } ], "structure": { "bundles": [ { "id": "identity-class-and-posting-boundary", "name": "Identity, class and posting boundary", "description": "Groups the governed Route / Itinerary concern for identity, class and posting boundary.", "rationale": "Separate one inventory-movement assertion from its request, execution, observation, posting and resulting balances.", "source_refs": [ "SRC-001", "SRC-019", "SRC-020", "SRC-024", "SRC-005", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ], "layers": [ { "id": "movement-identity-revision-idempotency-and-lineage", "name": "Movement identity, revision, idempotency and lineage", "description": "Groups Route / Itinerary context for movement identity, revision, idempotency and lineage without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-019", "SRC-020", "SRC-024" ], "findings": [ { "id": "movement-identifier-namespace-version-and-deduplication-key", "name": "Movement identifier, namespace, version and deduplication key", "description": "Records movement identifier, namespace, version and deduplication key as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-019", "SRC-020", "SRC-024" ], "questions": [ { "id": "movement-identifier-namespace-version-and-deduplication-key-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish movement identifier, namespace, version and deduplication key?", "kind": "identity", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "movement-identifier-namespace-version-and-deduplication-key-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access movement identifier, namespace, version and deduplication key, and under which authority?", "kind": "ownership", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "movement-identifier-namespace-version-and-deduplication-key-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify movement identifier, namespace, version and deduplication key?", "kind": "validation", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "movement-identifier-namespace-version-and-deduplication-key-data", "name": "Movement identifier, namespace, version and deduplication key data", "description": "Typed movement-scoped values and references required to answer the governed questions for movement identifier, namespace, version and deduplication key.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-019", "SRC-020", "SRC-024" ] } ], "artifacts": [ { "id": "movement-identifier-namespace-version-and-deduplication-key-artifact", "name": "Movement identifier, namespace, version and deduplication key evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting movement identifier, namespace, version and deduplication key.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-019", "SRC-020", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "original-correction-reversal-successor-split-and-merge-lineage", "name": "Original, correction, reversal, successor, split and merge lineage", "description": "Records original, correction, reversal, successor, split and merge lineage as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-019", "SRC-020", "SRC-024" ], "questions": [ { "id": "original-correction-reversal-successor-split-and-merge-lineage-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish original, correction, reversal, successor, split and merge lineage?", "kind": "provenance", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "original-correction-reversal-successor-split-and-merge-lineage-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access original, correction, reversal, successor, split and merge lineage, and under which authority?", "kind": "authority", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "original-correction-reversal-successor-split-and-merge-lineage-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify original, correction, reversal, successor, split and merge lineage?", "kind": "security", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "original-correction-reversal-successor-split-and-merge-lineage-data", "name": "Original, correction, reversal, successor, split and merge lineage data", "description": "Typed movement-scoped values and references required to answer the governed questions for original, correction, reversal, successor, split and merge lineage.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-019", "SRC-020", "SRC-024" ] } ], "artifacts": [ { "id": "original-correction-reversal-successor-split-and-merge-lineage-artifact", "name": "Original, correction, reversal, successor, split and merge lineage evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting original, correction, reversal, successor, split and merge lineage.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-019", "SRC-020", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "movement-class-direction-reason-and-authority", "name": "Movement class, direction, reason and authority", "description": "Groups Route / Itinerary context for movement class, direction, reason and authority without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ], "findings": [ { "id": "receipt-issue-transfer-adjustment-return-consumption-and-output-class", "name": "Receipt, issue, transfer, adjustment, return, consumption and output class", "description": "Records receipt, issue, transfer, adjustment, return, consumption and output class as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-005", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ], "questions": [ { "id": "receipt-issue-transfer-adjustment-return-consumption-and-output-class-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish receipt, issue, transfer, adjustment, return, consumption and output class?", "kind": "classification", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "receipt-issue-transfer-adjustment-return-consumption-and-output-class-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access receipt, issue, transfer, adjustment, return, consumption and output class, and under which authority?", "kind": "requirement", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "receipt-issue-transfer-adjustment-return-consumption-and-output-class-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify receipt, issue, transfer, adjustment, return, consumption and output class?", "kind": "privacy", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "receipt-issue-transfer-adjustment-return-consumption-and-output-class-data", "name": "Receipt, issue, transfer, adjustment, return, consumption and output class data", "description": "Typed movement-scoped values and references required to answer the governed questions for receipt, issue, transfer, adjustment, return, consumption and output class.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "receipt-issue-transfer-adjustment-return-consumption-and-output-class-artifact", "name": "Receipt, issue, transfer, adjustment, return, consumption and output class evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting receipt, issue, transfer, adjustment, return, consumption and output class.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "planned-physical-observed-posted-and-reconciled-assertion-kind", "name": "Planned, physical, observed, posted and reconciled assertion kind", "description": "Records planned, physical, observed, posted and reconciled assertion kind as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-005", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ], "questions": [ { "id": "planned-physical-observed-posted-and-reconciled-assertion-kind-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish planned, physical, observed, posted and reconciled assertion kind?", "kind": "classification", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "planned-physical-observed-posted-and-reconciled-assertion-kind-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access planned, physical, observed, posted and reconciled assertion kind, and under which authority?", "kind": "constraint", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "planned-physical-observed-posted-and-reconciled-assertion-kind-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify planned, physical, observed, posted and reconciled assertion kind?", "kind": "retention", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "planned-physical-observed-posted-and-reconciled-assertion-kind-data", "name": "Planned, physical, observed, posted and reconciled assertion kind data", "description": "Typed movement-scoped values and references required to answer the governed questions for planned, physical, observed, posted and reconciled assertion kind.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "planned-physical-observed-posted-and-reconciled-assertion-kind-artifact", "name": "Planned, physical, observed, posted and reconciled assertion kind evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting planned, physical, observed, posted and reconciled assertion kind.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "stock-subject-quantity-and-measurement", "name": "Stock subject, quantity and measurement", "description": "Groups the governed Route / Itinerary concern for stock subject, quantity and measurement.", "rationale": "Bind the stock subject and qualified amount without importing product, lot, unit or inventory-position masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-016", "SRC-018", "SRC-008", "SRC-009", "SRC-014", "SRC-015", "SRC-021", "SRC-023" ], "layers": [ { "id": "item-lot-serial-and-handling-unit-scope", "name": "Item, lot, serial and handling-unit scope", "description": "Groups Route / Itinerary context for item, lot, serial and handling-unit scope without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-016", "SRC-018" ], "findings": [ { "id": "product-material-item-lot-batch-and-serial-reference", "name": "Product, material, item, lot, batch and serial reference", "description": "Records product, material, item, lot, batch and serial reference as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-016", "SRC-018" ], "questions": [ { "id": "product-material-item-lot-batch-and-serial-reference-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish product, material, item, lot, batch and serial reference?", "kind": "relationship", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "product-material-item-lot-batch-and-serial-reference-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access product, material, item, lot, batch and serial reference, and under which authority?", "kind": "process", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "product-material-item-lot-batch-and-serial-reference-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify product, material, item, lot, batch and serial reference?", "kind": "access", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "product-material-item-lot-batch-and-serial-reference-data", "name": "Product, material, item, lot, batch and serial reference data", "description": "Typed movement-scoped values and references required to answer the governed questions for product, material, item, lot, batch and serial reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-016", "SRC-018" ] } ], "artifacts": [ { "id": "product-material-item-lot-batch-and-serial-reference-artifact", "name": "Product, material, item, lot, batch and serial reference evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting product, material, item, lot, batch and serial reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-016", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "handling-unit-container-package-and-aggregation-scope", "name": "Handling unit, container, package and aggregation scope", "description": "Records handling unit, container, package and aggregation scope as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-016", "SRC-018" ], "questions": [ { "id": "handling-unit-container-package-and-aggregation-scope-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish handling unit, container, package and aggregation scope?", "kind": "composition", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "handling-unit-container-package-and-aggregation-scope-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access handling unit, container, package and aggregation scope, and under which authority?", "kind": "event", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "handling-unit-container-package-and-aggregation-scope-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify handling unit, container, package and aggregation scope?", "kind": "exception", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "handling-unit-container-package-and-aggregation-scope-data", "name": "Handling unit, container, package and aggregation scope data", "description": "Typed movement-scoped values and references required to answer the governed questions for handling unit, container, package and aggregation scope.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-016", "SRC-018" ] } ], "artifacts": [ { "id": "handling-unit-container-package-and-aggregation-scope-artifact", "name": "Handling unit, container, package and aggregation scope evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting handling unit, container, package and aggregation scope.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-016", "SRC-018" ] } ], "inline_only_rationale": null } ] }, { "id": "quantity-unit-precision-and-value-context", "name": "Quantity, unit, precision and value context", "description": "Groups Route / Itinerary context for quantity, unit, precision and value context without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-015", "SRC-021", "SRC-023" ], "findings": [ { "id": "moved-received-issued-rejected-short-and-damaged-quantity", "name": "Moved, received, issued, rejected, short and damaged quantity", "description": "Records moved, received, issued, rejected, short and damaged quantity as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-015", "SRC-021", "SRC-023" ], "questions": [ { "id": "moved-received-issued-rejected-short-and-damaged-quantity-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish moved, received, issued, rejected, short and damaged quantity?", "kind": "measurement", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "moved-received-issued-rejected-short-and-damaged-quantity-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access moved, received, issued, rejected, short and damaged quantity, and under which authority?", "kind": "measurement", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "moved-received-issued-rejected-short-and-damaged-quantity-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify moved, received, issued, rejected, short and damaged quantity?", "kind": "interoperability", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "moved-received-issued-rejected-short-and-damaged-quantity-data", "name": "Moved, received, issued, rejected, short and damaged quantity data", "description": "Typed movement-scoped values and references required to answer the governed questions for moved, received, issued, rejected, short and damaged quantity.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-015", "SRC-021", "SRC-023" ] } ], "artifacts": [ { "id": "moved-received-issued-rejected-short-and-damaged-quantity-artifact", "name": "Moved, received, issued, rejected, short and damaged quantity evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting moved, received, issued, rejected, short and damaged quantity.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-015", "SRC-021", "SRC-023" ] } ], "inline_only_rationale": null }, { "id": "unit-precision-tolerance-conversion-base-and-alternate-measure", "name": "Unit, precision, tolerance, conversion, base and alternate measure", "description": "Records unit, precision, tolerance, conversion, base and alternate measure as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-015", "SRC-021", "SRC-023" ], "questions": [ { "id": "unit-precision-tolerance-conversion-base-and-alternate-measure-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish unit, precision, tolerance, conversion, base and alternate measure?", "kind": "measurement", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "unit-precision-tolerance-conversion-base-and-alternate-measure-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access unit, precision, tolerance, conversion, base and alternate measure, and under which authority?", "kind": "evidence", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "unit-precision-tolerance-conversion-base-and-alternate-measure-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify unit, precision, tolerance, conversion, base and alternate measure?", "kind": "decision", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "unit-precision-tolerance-conversion-base-and-alternate-measure-data", "name": "Unit, precision, tolerance, conversion, base and alternate measure data", "description": "Typed movement-scoped values and references required to answer the governed questions for unit, precision, tolerance, conversion, base and alternate measure.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-015", "SRC-021", "SRC-023" ] } ], "artifacts": [ { "id": "unit-precision-tolerance-conversion-base-and-alternate-measure-artifact", "name": "Unit, precision, tolerance, conversion, base and alternate measure evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting unit, precision, tolerance, conversion, base and alternate measure.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-015", "SRC-021", "SRC-023" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "source-destination-and-stock-state", "name": "Source, destination and stock state", "description": "Groups the governed Route / Itinerary concern for source, destination and stock state.", "rationale": "Represent the asserted transition between location and stock buckets while positions and balances remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-016", "SRC-005", "SRC-006", "SRC-012" ], "layers": [ { "id": "source-destination-location-and-position-binding", "name": "Source, destination, location and position binding", "description": "Groups Route / Itinerary context for source, destination, location and position binding without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-016" ], "findings": [ { "id": "site-warehouse-zone-bin-virtual-location-and-read-point", "name": "Site, warehouse, zone, bin, virtual location and read point", "description": "Records site, warehouse, zone, bin, virtual location and read point as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-016" ], "questions": [ { "id": "site-warehouse-zone-bin-virtual-location-and-read-point-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish site, warehouse, zone, bin, virtual location and read point?", "kind": "spatial", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "site-warehouse-zone-bin-virtual-location-and-read-point-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access site, warehouse, zone, bin, virtual location and read point, and under which authority?", "kind": "quality", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "site-warehouse-zone-bin-virtual-location-and-read-point-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify site, warehouse, zone, bin, virtual location and read point?", "kind": "identity", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "site-warehouse-zone-bin-virtual-location-and-read-point-data", "name": "Site, warehouse, zone, bin, virtual location and read point data", "description": "Typed movement-scoped values and references required to answer the governed questions for site, warehouse, zone, bin, virtual location and read point.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-016" ] } ], "artifacts": [ { "id": "site-warehouse-zone-bin-virtual-location-and-read-point-artifact", "name": "Site, warehouse, zone, bin, virtual location and read point evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting site, warehouse, zone, bin, virtual location and read point.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "source-destination-stock-position-and-balance-reference", "name": "Source, destination, stock-position and balance reference", "description": "Records source, destination, stock-position and balance reference as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-016" ], "questions": [ { "id": "source-destination-stock-position-and-balance-reference-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish source, destination, stock-position and balance reference?", "kind": "relationship", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "source-destination-stock-position-and-balance-reference-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access source, destination, stock-position and balance reference, and under which authority?", "kind": "validation", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "source-destination-stock-position-and-balance-reference-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify source, destination, stock-position and balance reference?", "kind": "classification", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "source-destination-stock-position-and-balance-reference-data", "name": "Source, destination, stock-position and balance reference data", "description": "Typed movement-scoped values and references required to answer the governed questions for source, destination, stock-position and balance reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-016" ] } ], "artifacts": [ { "id": "source-destination-stock-position-and-balance-reference-artifact", "name": "Source, destination, stock-position and balance reference evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting source, destination, stock-position and balance reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "owner-custodian-status-and-condition-transition", "name": "Owner, custodian, status and condition transition", "description": "Groups Route / Itinerary context for owner, custodian, status and condition transition without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-016" ], "findings": [ { "id": "owner-custodian-possession-control-and-responsibility-binding", "name": "Owner, custodian, possession, control and responsibility binding", "description": "Records owner, custodian, possession, control and responsibility binding as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-016" ], "questions": [ { "id": "owner-custodian-possession-control-and-responsibility-binding-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish owner, custodian, possession, control and responsibility binding?", "kind": "ownership", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "owner-custodian-possession-control-and-responsibility-binding-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access owner, custodian, possession, control and responsibility binding, and under which authority?", "kind": "security", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "owner-custodian-possession-control-and-responsibility-binding-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify owner, custodian, possession, control and responsibility binding?", "kind": "composition", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "owner-custodian-possession-control-and-responsibility-binding-data", "name": "Owner, custodian, possession, control and responsibility binding data", "description": "Typed movement-scoped values and references required to answer the governed questions for owner, custodian, possession, control and responsibility binding.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-016" ] } ], "artifacts": [ { "id": "owner-custodian-possession-control-and-responsibility-binding-artifact", "name": "Owner, custodian, possession, control and responsibility binding evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting owner, custodian, possession, control and responsibility binding.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "available-reserved-blocked-quarantine-quality-and-disposition-change", "name": "Available, reserved, blocked, quarantine, quality and disposition change", "description": "Records available, reserved, blocked, quarantine, quality and disposition change as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-016" ], "questions": [ { "id": "available-reserved-blocked-quarantine-quality-and-disposition-change-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish available, reserved, blocked, quarantine, quality and disposition change?", "kind": "state", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "available-reserved-blocked-quarantine-quality-and-disposition-change-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access available, reserved, blocked, quarantine, quality and disposition change, and under which authority?", "kind": "privacy", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "available-reserved-blocked-quarantine-quality-and-disposition-change-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify available, reserved, blocked, quarantine, quality and disposition change?", "kind": "relationship", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "available-reserved-blocked-quarantine-quality-and-disposition-change-data", "name": "Available, reserved, blocked, quarantine, quality and disposition change data", "description": "Typed movement-scoped values and references required to answer the governed questions for available, reserved, blocked, quarantine, quality and disposition change.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-016" ] } ], "artifacts": [ { "id": "available-reserved-blocked-quarantine-quality-and-disposition-change-artifact", "name": "Available, reserved, blocked, quarantine, quality and disposition change evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting available, reserved, blocked, quarantine, quality and disposition change.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-016" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "trigger-execution-lifecycle-and-time", "name": "Trigger, execution, lifecycle and time", "description": "Groups the governed Route / Itinerary concern for trigger, execution, lifecycle and time.", "rationale": "Keep commercial and operational triggers, execution evidence, posting state and clocks independently attributable.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017", "SRC-018", "SRC-020", "SRC-001", "SRC-002", "SRC-019" ], "layers": [ { "id": "request-order-reservation-task-and-process-trigger", "name": "Request, order, reservation, task and process trigger", "description": "Groups Route / Itinerary context for request, order, reservation, task and process trigger without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017", "SRC-018", "SRC-020" ], "findings": [ { "id": "order-fulfilment-reservation-warehouse-task-and-shipment-reference", "name": "Order, fulfilment, reservation, warehouse-task and shipment reference", "description": "Records order, fulfilment, reservation, warehouse-task and shipment reference as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017", "SRC-018", "SRC-020" ], "questions": [ { "id": "order-fulfilment-reservation-warehouse-task-and-shipment-reference-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish order, fulfilment, reservation, warehouse-task and shipment reference?", "kind": "relationship", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "order-fulfilment-reservation-warehouse-task-and-shipment-reference-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access order, fulfilment, reservation, warehouse-task and shipment reference, and under which authority?", "kind": "retention", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "order-fulfilment-reservation-warehouse-task-and-shipment-reference-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify order, fulfilment, reservation, warehouse-task and shipment reference?", "kind": "state", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "order-fulfilment-reservation-warehouse-task-and-shipment-reference-data", "name": "Order, fulfilment, reservation, warehouse-task and shipment reference data", "description": "Typed movement-scoped values and references required to answer the governed questions for order, fulfilment, reservation, warehouse-task and shipment reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017", "SRC-018", "SRC-020" ] } ], "artifacts": [ { "id": "order-fulfilment-reservation-warehouse-task-and-shipment-reference-artifact", "name": "Order, fulfilment, reservation, warehouse-task and shipment reference evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting order, fulfilment, reservation, warehouse-task and shipment reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017", "SRC-018", "SRC-020" ] } ], "inline_only_rationale": null }, { "id": "production-consumption-output-return-adjustment-and-count-trigger", "name": "Production, consumption, output, return, adjustment and count trigger", "description": "Records production, consumption, output, return, adjustment and count trigger as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017", "SRC-018", "SRC-020" ], "questions": [ { "id": "production-consumption-output-return-adjustment-and-count-trigger-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish production, consumption, output, return, adjustment and count trigger?", "kind": "process", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "production-consumption-output-return-adjustment-and-count-trigger-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access production, consumption, output, return, adjustment and count trigger, and under which authority?", "kind": "access", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "production-consumption-output-return-adjustment-and-count-trigger-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify production, consumption, output, return, adjustment and count trigger?", "kind": "lifecycle", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "production-consumption-output-return-adjustment-and-count-trigger-data", "name": "Production, consumption, output, return, adjustment and count trigger data", "description": "Typed movement-scoped values and references required to answer the governed questions for production, consumption, output, return, adjustment and count trigger.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017", "SRC-018", "SRC-020" ] } ], "artifacts": [ { "id": "production-consumption-output-return-adjustment-and-count-trigger-artifact", "name": "Production, consumption, output, return, adjustment and count trigger evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting production, consumption, output, return, adjustment and count trigger.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017", "SRC-018", "SRC-020" ] } ], "inline_only_rationale": null } ] }, { "id": "lifecycle-state-clock-and-posting", "name": "Lifecycle, state, clock and posting", "description": "Groups Route / Itinerary context for lifecycle, state, clock and posting without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ], "findings": [ { "id": "requested-planned-released-executing-completed-failed-and-cancelled-state", "name": "Requested, planned, released, executing, completed, failed and cancelled state", "description": "Records requested, planned, released, executing, completed, failed and cancelled state as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ], "questions": [ { "id": "requested-planned-released-executing-completed-failed-and-cancelled-state-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish requested, planned, released, executing, completed, failed and cancelled state?", "kind": "lifecycle", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "requested-planned-released-executing-completed-failed-and-cancelled-state-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access requested, planned, released, executing, completed, failed and cancelled state, and under which authority?", "kind": "exception", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "requested-planned-released-executing-completed-failed-and-cancelled-state-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify requested, planned, released, executing, completed, failed and cancelled state?", "kind": "temporal", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "requested-planned-released-executing-completed-failed-and-cancelled-state-data", "name": "Requested, planned, released, executing, completed, failed and cancelled state data", "description": "Typed movement-scoped values and references required to answer the governed questions for requested, planned, released, executing, completed, failed and cancelled state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ] } ], "artifacts": [ { "id": "requested-planned-released-executing-completed-failed-and-cancelled-state-artifact", "name": "Requested, planned, released, executing, completed, failed and cancelled state evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting requested, planned, released, executing, completed, failed and cancelled state.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ] } ], "inline_only_rationale": null }, { "id": "planned-effective-event-observation-record-posting-and-correction-time", "name": "Planned, effective, event, observation, record, posting and correction time", "description": "Records planned, effective, event, observation, record, posting and correction time as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ], "questions": [ { "id": "planned-effective-event-observation-record-posting-and-correction-time-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish planned, effective, event, observation, record, posting and correction time?", "kind": "temporal", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "planned-effective-event-observation-record-posting-and-correction-time-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access planned, effective, event, observation, record, posting and correction time, and under which authority?", "kind": "interoperability", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "planned-effective-event-observation-record-posting-and-correction-time-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify planned, effective, event, observation, record, posting and correction time?", "kind": "spatial", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "planned-effective-event-observation-record-posting-and-correction-time-data", "name": "Planned, effective, event, observation, record, posting and correction time data", "description": "Typed movement-scoped values and references required to answer the governed questions for planned, effective, event, observation, record, posting and correction time.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ] } ], "artifacts": [ { "id": "planned-effective-event-observation-record-posting-and-correction-time-artifact", "name": "Planned, effective, event, observation, record, posting and correction time evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting planned, effective, event, observation, record, posting and correction time.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "evidence-exceptions-and-reconciliation", "name": "Evidence, exceptions and reconciliation", "description": "Groups the governed Route / Itinerary concern for evidence, exceptions and reconciliation.", "rationale": "Make movement assertions auditable and reconcile disagreements without overwriting source-qualified facts.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-020", "SRC-021", "SRC-024", "SRC-007", "SRC-008", "SRC-014" ], "layers": [ { "id": "execution-evidence-observation-and-document", "name": "Execution evidence, observation and document", "description": "Groups Route / Itinerary context for execution evidence, observation and document without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-020", "SRC-021", "SRC-024" ], "findings": [ { "id": "scan-count-sensor-observation-operator-confirmation-and-proof", "name": "Scan, count, sensor observation, operator confirmation and proof", "description": "Records scan, count, sensor observation, operator confirmation and proof as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-020", "SRC-021", "SRC-024" ], "questions": [ { "id": "scan-count-sensor-observation-operator-confirmation-and-proof-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish scan, count, sensor observation, operator confirmation and proof?", "kind": "evidence", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "scan-count-sensor-observation-operator-confirmation-and-proof-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access scan, count, sensor observation, operator confirmation and proof, and under which authority?", "kind": "decision", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "scan-count-sensor-observation-operator-confirmation-and-proof-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify scan, count, sensor observation, operator confirmation and proof?", "kind": "provenance", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "scan-count-sensor-observation-operator-confirmation-and-proof-data", "name": "Scan, count, sensor observation, operator confirmation and proof data", "description": "Typed movement-scoped values and references required to answer the governed questions for scan, count, sensor observation, operator confirmation and proof.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-020", "SRC-021", "SRC-024" ] } ], "artifacts": [ { "id": "scan-count-sensor-observation-operator-confirmation-and-proof-artifact", "name": "Scan, count, sensor observation, operator confirmation and proof evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting scan, count, sensor observation, operator confirmation and proof.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-020", "SRC-021", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "receipt-despatch-transfer-posting-and-adjustment-document-reference", "name": "Receipt, despatch, transfer, posting and adjustment document reference", "description": "Records receipt, despatch, transfer, posting and adjustment document reference as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-020", "SRC-021", "SRC-024" ], "questions": [ { "id": "receipt-despatch-transfer-posting-and-adjustment-document-reference-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish receipt, despatch, transfer, posting and adjustment document reference?", "kind": "evidence", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "receipt-despatch-transfer-posting-and-adjustment-document-reference-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access receipt, despatch, transfer, posting and adjustment document reference, and under which authority?", "kind": "identity", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "receipt-despatch-transfer-posting-and-adjustment-document-reference-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify receipt, despatch, transfer, posting and adjustment document reference?", "kind": "ownership", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "receipt-despatch-transfer-posting-and-adjustment-document-reference-data", "name": "Receipt, despatch, transfer, posting and adjustment document reference data", "description": "Typed movement-scoped values and references required to answer the governed questions for receipt, despatch, transfer, posting and adjustment document reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-020", "SRC-021", "SRC-024" ] } ], "artifacts": [ { "id": "receipt-despatch-transfer-posting-and-adjustment-document-reference-artifact", "name": "Receipt, despatch, transfer, posting and adjustment document reference evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting receipt, despatch, transfer, posting and adjustment document reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-020", "SRC-021", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "exception-conflict-and-reconciliation", "name": "Exception, conflict and reconciliation", "description": "Groups Route / Itinerary context for exception, conflict and reconciliation without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-020", "SRC-021", "SRC-024" ], "findings": [ { "id": "shortage-excess-damage-mismatch-partial-and-failed-movement", "name": "Shortage, excess, damage, mismatch, partial and failed movement", "description": "Records shortage, excess, damage, mismatch, partial and failed movement as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-020", "SRC-021", "SRC-024" ], "questions": [ { "id": "shortage-excess-damage-mismatch-partial-and-failed-movement-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish shortage, excess, damage, mismatch, partial and failed movement?", "kind": "exception", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "shortage-excess-damage-mismatch-partial-and-failed-movement-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access shortage, excess, damage, mismatch, partial and failed movement, and under which authority?", "kind": "classification", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "shortage-excess-damage-mismatch-partial-and-failed-movement-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify shortage, excess, damage, mismatch, partial and failed movement?", "kind": "authority", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "shortage-excess-damage-mismatch-partial-and-failed-movement-data", "name": "Shortage, excess, damage, mismatch, partial and failed movement data", "description": "Typed movement-scoped values and references required to answer the governed questions for shortage, excess, damage, mismatch, partial and failed movement.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-020", "SRC-021", "SRC-024" ] } ], "artifacts": [ { "id": "shortage-excess-damage-mismatch-partial-and-failed-movement-artifact", "name": "Shortage, excess, damage, mismatch, partial and failed movement evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting shortage, excess, damage, mismatch, partial and failed movement.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-020", "SRC-021", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "source-destination-shipment-count-ledger-and-balance-reconciliation", "name": "Source, destination, shipment, count, ledger and balance reconciliation", "description": "Records source, destination, shipment, count, ledger and balance reconciliation as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-020", "SRC-021", "SRC-024" ], "questions": [ { "id": "source-destination-shipment-count-ledger-and-balance-reconciliation-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish source, destination, shipment, count, ledger and balance reconciliation?", "kind": "validation", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "source-destination-shipment-count-ledger-and-balance-reconciliation-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access source, destination, shipment, count, ledger and balance reconciliation, and under which authority?", "kind": "composition", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "source-destination-shipment-count-ledger-and-balance-reconciliation-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify source, destination, shipment, count, ledger and balance reconciliation?", "kind": "requirement", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "source-destination-shipment-count-ledger-and-balance-reconciliation-data", "name": "Source, destination, shipment, count, ledger and balance reconciliation data", "description": "Typed movement-scoped values and references required to answer the governed questions for source, destination, shipment, count, ledger and balance reconciliation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-020", "SRC-021", "SRC-024" ] } ], "artifacts": [ { "id": "source-destination-shipment-count-ledger-and-balance-reconciliation-artifact", "name": "Source, destination, shipment, count, ledger and balance reconciliation evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting source, destination, shipment, count, ledger and balance reconciliation.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-020", "SRC-021", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-access-and-interoperability", "name": "Governance, access and interoperability", "description": "Groups the governed Route / Itinerary concern for governance, access and interoperability.", "rationale": "Control authority, audit and standards projection while disclosing profile limits and information loss.", "source_refs": [ "SRC-017", "SRC-018", "SRC-020", "SRC-021", "SRC-022", "SRC-024", "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-019", "SRC-023" ], "layers": [ { "id": "roles-authority-controls-access-and-retention", "name": "Roles, authority, controls, access and retention", "description": "Groups Route / Itinerary context for roles, authority, controls, access and retention without importing neighboring master lifecycles.", "source_refs": [ "SRC-017", "SRC-018", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ], "findings": [ { "id": "requester-executor-observer-poster-approver-and-reconciler-role", "name": "Requester, executor, observer, poster, approver and reconciler role", "description": "Records requester, executor, observer, poster, approver and reconciler role as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-017", "SRC-018", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ], "questions": [ { "id": "requester-executor-observer-poster-approver-and-reconciler-role-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish requester, executor, observer, poster, approver and reconciler role?", "kind": "authority", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "requester-executor-observer-poster-approver-and-reconciler-role-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access requester, executor, observer, poster, approver and reconciler role, and under which authority?", "kind": "relationship", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "requester-executor-observer-poster-approver-and-reconciler-role-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify requester, executor, observer, poster, approver and reconciler role?", "kind": "constraint", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "requester-executor-observer-poster-approver-and-reconciler-role-data", "name": "Requester, executor, observer, poster, approver and reconciler role data", "description": "Typed movement-scoped values and references required to answer the governed questions for requester, executor, observer, poster, approver and reconciler role.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-017", "SRC-018", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ] } ], "artifacts": [ { "id": "requester-executor-observer-poster-approver-and-reconciler-role-artifact", "name": "Requester, executor, observer, poster, approver and reconciler role evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting requester, executor, observer, poster, approver and reconciler role.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-017", "SRC-018", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "segregation-of-duties-access-retention-legal-hold-and-audit", "name": "Segregation of duties, access, retention, legal hold and audit", "description": "Records segregation of duties, access, retention, legal hold and audit as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-017", "SRC-018", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ], "questions": [ { "id": "segregation-of-duties-access-retention-legal-hold-and-audit-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish segregation of duties, access, retention, legal hold and audit?", "kind": "access", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "segregation-of-duties-access-retention-legal-hold-and-audit-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access segregation of duties, access, retention, legal hold and audit, and under which authority?", "kind": "state", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "segregation-of-duties-access-retention-legal-hold-and-audit-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify segregation of duties, access, retention, legal hold and audit?", "kind": "process", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "segregation-of-duties-access-retention-legal-hold-and-audit-data", "name": "Segregation of duties, access, retention, legal hold and audit data", "description": "Typed movement-scoped values and references required to answer the governed questions for segregation of duties, access, retention, legal hold and audit.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-017", "SRC-018", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ] } ], "artifacts": [ { "id": "segregation-of-duties-access-retention-legal-hold-and-audit-artifact", "name": "Segregation of duties, access, retention, legal hold and audit evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting segregation of duties, access, retention, legal hold and audit.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-017", "SRC-018", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "standards-crosswalk-quality-and-loss", "name": "Standards crosswalk, quality and loss", "description": "Groups Route / Itinerary context for standards crosswalk, quality and loss without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "findings": [ { "id": "gs1-ubl-uncefact-isa95-iec62264-and-unit-crosswalk", "name": "GS1, UBL, UN/CEFACT, ISA-95, IEC 62264 and unit crosswalk", "description": "Records gs1, ubl, un/cefact, isa-95, iec 62264 and unit crosswalk as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "gs1-ubl-uncefact-isa95-iec62264-and-unit-crosswalk-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish gs1, ubl, un/cefact, isa-95, iec 62264 and unit crosswalk?", "kind": "interoperability", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "gs1-ubl-uncefact-isa95-iec62264-and-unit-crosswalk-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access gs1, ubl, un/cefact, isa-95, iec 62264 and unit crosswalk, and under which authority?", "kind": "lifecycle", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "gs1-ubl-uncefact-isa95-iec62264-and-unit-crosswalk-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify gs1, ubl, un/cefact, isa-95, iec 62264 and unit crosswalk?", "kind": "event", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "gs1-ubl-uncefact-isa95-iec62264-and-unit-crosswalk-data", "name": "GS1, UBL, UN/CEFACT, ISA-95, IEC 62264 and unit crosswalk data", "description": "Typed movement-scoped values and references required to answer the governed questions for gs1, ubl, un/cefact, isa-95, iec 62264 and unit crosswalk.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "gs1-ubl-uncefact-isa95-iec62264-and-unit-crosswalk-artifact", "name": "GS1, UBL, UN/CEFACT, ISA-95, IEC 62264 and unit crosswalk evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting gs1, ubl, un/cefact, isa-95, iec 62264 and unit crosswalk.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "source-profile-version-quality-confidence-license-and-semantic-loss", "name": "Source profile, version, quality, confidence, license and semantic loss", "description": "Records source profile, version, quality, confidence, license and semantic loss as typed Inventory Movement context while stock position, product, location, order, task, shipment, ledger, document and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "source-profile-version-quality-confidence-license-and-semantic-loss-q01", "text": "Which movement identity, class, revision, stock subject, quantity, location transition, clocks and source establish source profile, version, quality, confidence, license and semantic loss?", "kind": "quality", "answer_data": [ "movement identifier, namespace, assertion kind, revision and idempotency key", "item, lot, serial, handling-unit, source and destination position references", "quantity, unit, precision, event time, posting time, source profile and confidence" ] }, { "id": "source-profile-version-quality-confidence-license-and-semantic-loss-q02", "text": "Who requests, executes, observes, posts, approves, owns, holds, corrects, reconciles or may access source profile, version, quality, confidence, license and semantic loss, and under which authority?", "kind": "temporal", "answer_data": [ "requester, executor, observer, poster, approver, owner, custodian, steward and reconciler roles", "order, reservation, task, production, shipment, policy, jurisdiction and segregation-of-duties basis", "assertion owner, master system, reviewer, correction actor and disputed state" ] }, { "id": "source-profile-version-quality-confidence-license-and-semantic-loss-q03", "text": "Which lifecycle state, evidence, exception, reconciliation, uncertainty and lineage qualify source profile, version, quality, confidence, license and semantic loss?", "kind": "measurement", "answer_data": [ "requested, planned, released, executing, completed, posted, failed, cancelled, reversed and corrected state", "scan, count, observation, document, posting, balance and shipment evidence references", "shortage, excess, damage, mismatch, tolerance, conflict, correction, successor and semantic-loss declaration" ] } ], "data_elements": [ { "id": "source-profile-version-quality-confidence-license-and-semantic-loss-data", "name": "Source profile, version, quality, confidence, license and semantic loss data", "description": "Typed movement-scoped values and references required to answer the governed questions for source profile, version, quality, confidence, license and semantic loss.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "source-profile-version-quality-confidence-license-and-semantic-loss-artifact", "name": "Source profile, version, quality, confidence, license and semantic loss evidence manifest", "description": "Digest-addressed manifest of movement assertions, references, observations, postings, conflicts and corrections supporting source profile, version, quality, confidence, license and semantic loss.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative inventory or warehouse master-system movement identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-movement", "name": "Register inventory movement", "description": "Create one governed movement identity and immutable initial assertion.", "inputs": [ "movement class", "stock subject", "source and authority" ], "outputs": [ "movement identifier", "initial revision" ], "preconditions": [ "active Dimension", "create authority" ], "effects": [ "identity, boundary and unknowns are appended" ], "source_refs": [ "SRC-001", "SRC-011", "SRC-019", "SRC-020", "SRC-024" ] }, { "id": "classify-movement", "name": "Classify movement", "description": "Record direction, reason, assertion kind and industry profile without changing execution or ledger state.", "inputs": [ "movement identifier", "direction and reason", "profile" ], "outputs": [ "versioned classification" ], "preconditions": [ "classifier versions known" ], "effects": [ "classification remains source-qualified" ], "source_refs": [ "SRC-005", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ] }, { "id": "bind-stock-subject", "name": "Bind stock subject and quantity", "description": "Bind item, lot, serial, handling-unit and qualified quantity references.", "inputs": [ "movement revision", "subject references", "quantity and unit" ], "outputs": [ "validated subject binding" ], "preconditions": [ "external identities resolvable", "unit known" ], "effects": [ "scope is appended without importing masters" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-014", "SRC-015" ] }, { "id": "define-transition", "name": "Define source and destination transition", "description": "Record source, destination, owner, custodian, status and disposition before-and-after references.", "inputs": [ "movement revision", "source state", "destination state" ], "outputs": [ "typed transition assertion" ], "preconditions": [ "positions and locations resolvable" ], "effects": [ "balances remain external and unmodified" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-011", "SRC-016" ] }, { "id": "plan-or-reserve", "name": "Plan or reserve movement", "description": "Bind request, order, reservation, warehouse task, production or shipment triggers and planned clocks.", "inputs": [ "movement identifier", "trigger references", "planned quantity and time" ], "outputs": [ "planned movement revision" ], "preconditions": [ "trigger authority known" ], "effects": [ "plan remains distinct from execution and posting" ], "source_refs": [ "SRC-005", "SRC-007", "SRC-010", "SRC-017", "SRC-018" ] }, { "id": "record-execution", "name": "Record execution evidence", "description": "Append physical handling, scan, count, observation and completion assertions.", "inputs": [ "movement identifier", "evidence reference", "event and record time" ], "outputs": [ "execution assertion" ], "preconditions": [ "evidence source known" ], "effects": [ "observation does not silently post inventory" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-019", "SRC-020" ] }, { "id": "record-posting", "name": "Record authoritative posting reference", "description": "Register a posting performed by the external inventory master or ledger without executing it locally.", "inputs": [ "movement revision", "posting identifier", "posting authority and time" ], "outputs": [ "posting-reference assertion" ], "preconditions": [ "external posting succeeded", "posting authority verified" ], "effects": [ "resulting balance remains externally mastered" ], "source_refs": [ "SRC-007", "SRC-008", "SRC-013", "SRC-014", "SRC-017", "SRC-018", "SRC-020" ] }, { "id": "reverse-or-correct", "name": "Reverse or correct movement", "description": "Append compensating or successor assertions while preserving the original event and posting lineage.", "inputs": [ "movement revision", "reason", "correction or reversal reference" ], "outputs": [ "successor revision", "lineage map" ], "preconditions": [ "correction authority", "affected scope known" ], "effects": [ "history remains immutable and linked" ], "source_refs": [ "SRC-001", "SRC-009", "SRC-020", "SRC-024" ] }, { "id": "reconcile-movement", "name": "Reconcile movement", "description": "Compare request, execution, receipt, shipment, count, posting and position assertions under tolerance rules.", "inputs": [ "movement revision", "comparison assertions", "tolerance and precedence policy" ], "outputs": [ "reconciliation result", "conflict set" ], "preconditions": [ "units, sources and clocks known" ], "effects": [ "differences remain visible and source-qualified" ], "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-014", "SRC-021" ] }, { "id": "project-movement", "name": "Project inventory movement", "description": "Produce minimum-necessary standards-aligned visibility, inventory, fulfilment or manufacturing views.", "inputs": [ "movement revision", "target profile", "access purpose" ], "outputs": [ "versioned projection", "semantic-loss declaration" ], "preconditions": [ "authorized recipient", "pinned target version" ], "effects": [ "projection is logged and source identity preserved" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "composition": [ { "target": "WM-OBJ-020 Inventory Stock Position", "relation": "REFERENCE", "purpose": "Resolve source and destination positions and resulting balances while the candidate parent relation remains under joint boundary review.", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ] }, { "target": "WM-FLW-011 Shipment / Consignment", "relation": "REFERENCE", "purpose": "Resolve despatch, receipt and logistics grouping triggers without importing shipment lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009", "SRC-010" ] }, { "target": "WM-FLW-013 Supply-chain Trace / Chain of Custody", "relation": "REFERENCE", "purpose": "Resolve cross-organizational event graphs and custody evidence without duplicating them.", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-020" ] }, { "target": "Product, lot, serial, handling unit and location masters", "relation": "REFERENCE", "purpose": "Resolve stock subjects and spatial context while preserving external identity and lifecycle authority.", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-016" ] }, { "target": "Order, reservation, warehouse task and production masters", "relation": "REFERENCE", "purpose": "Resolve request, authorization and execution context without owning operational workflows.", "required": false, "source_refs": [ "SRC-005", "SRC-007", "SRC-017", "SRC-018" ] }, { "target": "Inventory ledger, valuation and accounting masters", "relation": "REFERENCE", "purpose": "Resolve authoritative posting and resulting balance without local financial or inventory mutation.", "required": false, "source_refs": [ "SRC-008", "SRC-013", "SRC-014", "SRC-017", "SRC-018" ] }, { "target": "GS1 EPCIS 2.0.1 and CBV 2.0.0", "relation": "ALIGN", "purpose": "Project visibility events, object and quantity scope, locations, business steps, dispositions and corrections without treating observations as ledger truth.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] }, { "target": "OASIS UBL 2.4", "relation": "ALIGN", "purpose": "Project inventory report, despatch and receipt views with pinned document semantics.", "required": false, "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010" ] }, { "target": "UN/CEFACT code lists and Core Component Library", "relation": "ALIGN", "purpose": "Project direction, reason, balance, quantity and unit semantics with exact release pins.", "required": false, "source_refs": [ "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016" ] }, { "target": "ISA-95 and IEC 62264-2", "relation": "ALIGN", "purpose": "Project manufacturing enterprise-control exchange semantics as an industry profile.", "required": false, "source_refs": [ "SRC-017", "SRC-018" ] }, { "target": "RFC 3339, PROV-O, DQV, ODRL, XML Schema and ISO 8000", "relation": "ALIGN", "purpose": "Project temporal, provenance, quality, access, datatype and master-data semantics with semantic-loss declarations.", "required": false, "source_refs": [ "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, inventory steward, warehouse operator, posting authority, approver and accountable reconciliation roles.", "Register authoritative product, lot, serial, handling-unit, location, stock-position, order, reservation, task, production, shipment, ledger, document, observation and evidence masters.", "Publish movement-type, reason, location, stock-status, unit, access, retention, quality and interoperability registries.", "Pin industry, jurisdiction, warehouse, manufacturing, accounting, valuation, safety, privacy, licensing and exchange profiles." ], "namespace_guidance": "Mint movement, revision, transition, execution-assertion, posting-reference, reconciliation and projection identifiers only in the adopting Dimension namespace; preserve external identities as typed references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local movement, stock-status, location, unit, posting, access, retention and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, authoritative movement ID, immutable revision, assertion kind, stock-subject scope, source-destination transition and source profile; never use date, document number, barcode, quantity, endpoint pair or hash alone as identity.", "Keep request, plan, reservation, physical execution, observation, posting, resulting stock position, correction and reconciliation distinct and preserve causal links." ], "patch_rules": [ "Additive extensions use a Dimension-owned namespace and declare target node, movement or industry profile, authority, source, rationale, access, time and interoperability impact.", "Breaking changes require a new version, migration and crosswalk maps, compatibility declaration and continued resolution of prior movement revisions, postings and identifiers." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when identity, assertion kind, stock subject, quantity, transition, clocks, authority, provenance and access meaning remain intact.", "GS1, UBL, UN/CEFACT, ISA-95, IEC 62264, units and provenance mappings pin source and target versions and declare transformed, omitted or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "Authoritative inventory or warehouse master-system movement identifier and immutable revision.", "Governed globally resolvable movement, transition, posting or reconciliation IRI.", "Adopting-Dimension UUID or ULID when no authoritative external identifier exists." ], "timestamp_rule": "Record timestamps in RFC 3339 with seconds and an explicit UTC offset or Z; keep planned, effective, event, observation, record, posting, correction and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {movement-id}--{artifact-kind}--{revision-or-event-id}; never use a date, document number, barcode, quantity, location, filename or hash alone as identity.", "integrity_rule": "Store digest, media type, byte length, issuer, source and vocabulary versions, subject and transition scope, event and record times, provenance, assurance, license and access marking for each retained serial artifact." }, "policies": [ "The adopting Dimension declares who may request, plan, reserve, execute, observe, post, approve, reverse, correct, reconcile, disclose, retain and tombstone inventory movements.", "Every assertion requires movement identity and revision, assertion kind, stock subject, qualified quantity, transition scope, time kind, source, authority, confidence, status and lineage as applicable.", "Agents never infer inventory balance, ownership, custody, availability, quality, shipment completion, financial value or legal permission from one movement, scan, document, event or posting reference alone.", "Product, lot, serial, handling unit, location, stock position, order, task, shipment, ledger, valuation, document, observation, incident and evidence remain external masters.", "Automated agents may append low-risk plans, observations, reconciliations and projections under delegation, but authoritative inventory posting, reversal, protected disclosure and irreversible deletion require explicit external authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, requested revision, stock-subject scope, assertion kind, status horizon, assurance, freshness, license and access policy; return the minimum permitted projection." ], "create": [ "Create stable identity, movement class, stock-subject scope, qualified quantity, source-destination transition, source, authority and explicit unknowns before adding execution or posting assertions." ], "update": [ "Append an immutable plan, execution, posting, exception, reconciliation or correction revision with actor, authority, reason, RFC 3339 effective time and predecessor." ], "delete": [ "Apply safety, finance, dispute, audit, retention, disposition and legal-hold policy; tombstone eligible Inventory Movement-owned records or withdraw projections while preserving identity, material provenance and non-cascading external references. The adopting Dimension policy owns execution." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, access, retention and federation rules." ] }, { "name": "Inventory steward", "responsibilities": [ "Own movement semantics, classifiers, stock-position references and reconciliation policy." ] }, { "name": "Requester or planner", "responsibilities": [ "Own request, order, reservation, task, planned quantity and timing assertions." ] }, { "name": "Warehouse or process executor", "responsibilities": [ "Own physical execution and operator-confirmed movement evidence within delegated scope." ] }, { "name": "Observer or evidence steward", "responsibilities": [ "Own scan, count, sensor, document, quality and correction lineage." ] }, { "name": "Inventory posting authority", "responsibilities": [ "Own authoritative posting, reversal and resulting balance in the external master system." ] }, { "name": "Approver or reconciler", "responsibilities": [ "Review segregation of duties, exceptions, conflicts, tolerance and closure." ] }, { "name": "Disclosure authority", "responsibilities": [ "Review protected use, recipient, purpose, redaction and publication timing." ] } ], "access": { "default_rule": "Deny mutation and sensitive disclosure unless active Dimension, role, purpose, stock and location sensitivity, safety or finance rule, license and field policy grant the action; expose the minimum necessary projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency or regulatory access must be legally grounded, time-limited, purpose-bound, attributable, independently reviewed and unable to erase immutable movement, correction, reversal 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 fields, source evidence and outcome for privileged mutation or disclosure." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the nearest Dimension-owner AGENTS.md, inventory and posting authority, active industry, jurisdiction, time, access, retention, licensing and disclosure policies.", "Read this model AGENTS.md, pinned spec.yaml and required product, lot, serial, handling-unit, location, stock-position, order, task, shipment, ledger, document, observation and evidence instructions before mutation." ] } }, "coverage": { "claim": "WM-FLW-012 covers one governed Inventory Movement event with stable identity, movement class, stock-subject scope, qualified quantity, source-destination transition, trigger, execution and posting references, lifecycle clocks, evidence, exceptions, reconciliation, governance and loss-aware interoperability. Industry, jurisdiction, accounting, valuation, warehouse-execution, implementation-conformance and independent-review questions remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Movement, revision, execution assertion, posting reference, correction, reversal and projection identities remain distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Direction, reason, movement class and planned, physical, observed, posted or reconciled assertion kind are explicit." }, { "dimension": "direct properties", "status": "covered", "notes": "Subject scope, quantity, transition, state and event-specific evidence are covered without importing external masters." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Request, physical execution, scan, count, document, posting and resulting balance are independently recognized." }, { "dimension": "lifecycle", "status": "covered", "notes": "Requested, planned, reserved, released, executing, completed, posted, failed, cancelled, reversed and corrected states preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Stock subjects, locations, positions, orders, tasks, shipments, postings, documents and evidence use typed references." }, { "dimension": "temporal", "status": "covered", "notes": "Planned, effective, event, observation, record, posting, correction and ingestion clocks remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Source and destination site, warehouse, zone, bin, virtual location and read-point functions are explicit." }, { "dimension": "provenance", "status": "covered", "notes": "Sources, actors, methods, observations, postings, derivations, revisions and invalidations are linked." }, { "dimension": "ownership", "status": "covered", "notes": "Inventory ownership, custody, possession, control, responsibility and data mastership are not conflated." }, { "dimension": "validation", "status": "covered", "notes": "Identity, quantity, unit, transition, clock, role, posting, balance, evidence and crosswalk checks are explicit." }, { "dimension": "access", "status": "covered", "notes": "Role, purpose, segregation of duties, commercial sensitivity, minimum projection and audit are represented." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Corrections, reversals, disputes, audit or legal hold, withdrawal and tombstones are explicit and non-cascading." }, { "dimension": "interoperability", "status": "covered", "notes": "GS1, UBL, UN/CEFACT, ISA-95, IEC 62264, RFC, PROV, DQV, ODRL and ISO mappings disclose loss." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Registration, classification, binding, planning, evidence, posting reference, correction, reconciliation and projection declare controlled effects." } ], "known_omissions": [ "Industry, warehouse, manufacturing, accounting, valuation, customs, dangerous-goods, safety, privacy, licensing and retention profiles require exact current rules and competent review.", "Product, lot, serial, handling unit, location, stock position, order, task, shipment, ledger, document, observation, incident and evidence lifecycles remain in neighboring models.", "Certified field crosswalks, balance calculation, costing, allocation algorithms, warehouse execution, autonomous robotics and legal evidence requirements remain future work." ], "conflicts": [ "Warehouse systems may call a request, task, physical action, scan or ledger posting a movement; the model requires an explicit assertion kind and source profile.", "GS1 EPCIS captures visibility events and UBL exchanges fulfilment documents, but neither is assumed to be the universal authoritative inventory ledger.", "A physical transfer, ownership transfer, custody transfer, status change, valuation posting and accounting entry may correlate but are different governed facts." ], "regional_assumptions": [ "UN/CEFACT and UBL are cross-domain exchange sources rather than universal inventory law or warehouse execution policy.", "ISA-95 and IEC 62264 are manufacturing integration profiles and do not define all retail, healthcare, customs or field-service movements.", "Inventory posting, valuation, tax, title, custody, safety and retention consequences depend on organization, industry and jurisdiction." ], "adversarial_checks": [ "Reject a movement without stable identity, revision, assertion kind, stock subject, qualified quantity, transition, source, authority and lineage.", "Reject a request, reservation, warehouse task, scan, shipment event, inventory balance or accounting entry represented as the movement itself without a discriminator.", "Reject physical execution and authoritative inventory posting collapsed into one state or timestamp.", "Reject quantity without unit, precision and subject scope or a location transition without source and destination roles.", "Reject ownership, custody, availability, quality, financial value or shipment completion inferred from one movement or document alone.", "Reject last-write-wins when request, execution, receipt, posting, count or balance assertions conflict; preserve source, clocks, correction and precedence.", "Reject authoritative posting, reversal, protected disclosure or record destruction outside delegated external authority." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "event", "status": "accepted", "rationale": "The aggregate root is one stock-affecting movement assertion. Request, physical execution, observation, authoritative posting and resulting stock position remain distinguishable and independently sourced." }, "decisions": [ { "concept": "Inventory Movement event boundary", "disposition": "accepted", "rationale": "The model owns movement identity, asserted transition, evidence references and correction lineage rather than stock balance or warehouse workflow." }, { "concept": "WM-OBJ-020 parent signal", "disposition": "held-as-required-reference", "rationale": "A movement references before-and-after inventory positions, but an event is not automatically contained by the position aggregate." }, { "concept": "Request plan execution observation posting and balance", "disposition": "accepted-as-distinct-assertion-kinds", "rationale": "They may occur at different times under different authorities and must not share one status or timestamp." }, { "concept": "Movement subject and quantity", "disposition": "accepted-as-qualified-external-reference", "rationale": "Product, lot, serial and handling-unit identities remain external while the movement owns the scoped quantity assertion." }, { "concept": "Source destination and stock buckets", "disposition": "accepted-as-transition-references", "rationale": "Locations, positions, ownership, custody, availability, quality and disposition are independently typed before-and-after references." }, { "concept": "WM-FLW-011 and WM-FLW-013 boundaries", "disposition": "accepted-as-external-neighbor-masters", "rationale": "Shipment grouping and cross-organizational trace graphs remain external even when they trigger or evidence an inventory movement." }, { "concept": "Inventory posting", "disposition": "accepted-as-external-authoritative-operation", "rationale": "Vercy records posting identity, authority, time and result reference but does not mutate an inventory or accounting ledger." }, { "concept": "Correction reversal split and merge", "disposition": "accepted-as-append-only-lineage", "rationale": "Prior assertions remain immutable and resolvable; correction or reversal creates a linked successor or compensating record." }, { "concept": "GS1 UBL UN/CEFACT and ISA-95 projections", "disposition": "accepted-as-versioned-loss-aware-alignments", "rationale": "The sources cover different visibility, fulfilment, inventory-report and manufacturing-integration views and none is universal ledger authority." }, { "concept": "Single-provider waiver and local no-tools audit", "disposition": "accepted-with-mandatory-hold", "rationale": "One bounded Claude Sonnet and one bounded Grok attempt each timed out after 120 seconds. Codex separately audited the frozen validated result and comparison without acquiring new facts, so assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-FLW-012 each timed out after 120 seconds; no external result was admitted.", "Relation hold: WM-OBJ-020 remains a required typed reference rather than an approved parent until joint boundary review.", "Boundary hold: product, lot, serial, handling unit, location, stock position, order, task, shipment, trace, ledger, valuation, accounting, document, observation, incident and evidence remain external masters.", "Assertion-kind hold: request, plan, reservation, physical execution, observation, posting, balance, correction and reconciliation must remain distinguishable.", "Authority hold: authoritative posting, reversal and resulting balance require the external inventory master or ledger authority.", "Terminology hold: movement, transfer, transaction, issue, receipt, adjustment, task and posting are profile-specific terms.", "Profile hold: warehouse, manufacturing, retail, healthcare, customs, dangerous-goods, safety, accounting, valuation, privacy, licensing and retention profiles need independent validation.", "Evidence hold: one scan, count, document, shipment event or posting reference does not alone prove balance, ownership, custody, availability, quality or financial value.", "Interoperability hold: all GS1, UBL, UN/CEFACT, ISA-95, IEC 62264, unit, provenance and quality projections require exact release pins, conformance tests and semantic-loss declarations.", "Completeness hold: the 24-source draft is broad but does not claim universal industry, legal, operational or accounting coverage.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [] }, "statistics": { "sources": 24, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }