# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-09T19:36:08Z", "synthesisSha256": "3500cfc6b3fc2d92787c8b49c2d8532a4e858217ba48ae88f01151c31f08239a", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-OBJ-020", "registryId": "vr.wm-obj-020", "name": "Inventory Stock Position", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.OBJ.INV" ], "tags": [ "inventory", "stock", "position", "phy.obj.inv" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-obj-020-inventory-stock-position/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-obj-020", "model": { "registry_id": "vr.wm-obj-020", "model_id": "WM-OBJ-020", "name": "Inventory Stock Position", "entry_kind": "aggregate", "purpose": "Describe a source-qualified inventory quantity position by product, ownership, location, status and time.", "scope_statement": "The aggregate owns stock-position identity, declared dimension grain, measured and derived quantities, snapshot currency, reconciliation evidence and bounded operational references. It is informational, not a physical object or execution engine.", "in_scope": [ "Stock dimension tuple, custody, restrictions and quantity basis", "Reservation and planned-measure semantics with source-defined formulas", "Snapshot consistency, count reconciliation, lineage and governed exchange" ], "out_of_scope": [ "Physical product geometry or material remastered as properties of a balance", "Inventory booking engine, automatic warehouse actuation and oversell guarantees", "Legal title determination, financial valuation and accounting entries" ], "boundary_notes": [ { "neighbor": "WM-OBJ-001 Physical Item", "distinction": "REFERENCE only: a stock aggregate is not a serial item or its physical characteristics.", "source_refs": [ "SRC-001", "SRC-005" ] }, { "neighbor": "WM-OBJ-002 Product Type / Catalog Item", "distinction": "Product identity and unit conversion master stay referenced, not copied.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "WM-FLW-012 Inventory Movement", "distinction": "Movement changes positions but is not itself the current balance; no complete event ledger is assumed.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "neighbor": "Reservation, order, warehouse and valuation masters", "distinction": "Position retains qualified references and quantities; execution, facility identity and monetary valuation remain external.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007", "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Inventory on-hand list", "organization": "Microsoft", "url": "https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-on-hand-list", "version_or_date": "Public page inspected 2026-09-09; revision pin pending", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-09T19:25:00Z", "relevance": "Selected indexed text: dimensions, aggregation and hierarchy reservations; vendor-specific practice." }, { "id": "SRC-002", "title": "Reserve inventory quantities", "organization": "Microsoft", "url": "https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/reserve-inventory-quantities", "version_or_date": "Public page inspected 2026-09-09; revision pin pending", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-09T19:25:00Z", "relevance": "Selected indexed text: physical and expected-receipt reservations are distinct." }, { "id": "SRC-003", "title": "Stock report", "organization": "Odoo", "url": "https://www.odoo.com/documentation/18.0/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.html", "version_or_date": "Odoo 18.0", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-09T19:25:00Z", "relevance": "Indexed passage only; direct open timed out. Distinct stock, usable and planned measures." }, { "id": "SRC-004", "title": "Consignment", "organization": "Odoo", "url": "https://www.odoo.com/documentation/18.0/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.html", "version_or_date": "Odoo 18.0", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-09T19:25:00Z", "relevance": "Indexed article: owner versus custodian and stock reporting; not legal title advice." }, { "id": "SRC-005", "title": "Inventory adjustments", "organization": "Odoo", "url": "https://www.odoo.com/documentation/18.0/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.html", "version_or_date": "Odoo 18.0", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-09T19:25:00Z", "relevance": "Indexed article: count, application, intervening movements, negative balance and reversal." }, { "id": "SRC-006", "title": "EPCIS Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/epcis/2.0.1/", "version_or_date": "URL 2.0.1; retrieved PDF header Release 2.0 June 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-09T19:25:00Z", "relevance": "Selected sections 7.3.3.1 and 7.4.1: quantity and time constraints, not a stock balance engine." }, { "id": "SRC-007", "title": "Inventory Visibility public APIs", "organization": "Microsoft", "url": "https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-visibility-api", "version_or_date": "2026-03-10", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-09T19:25:00Z", "relevance": "Selected query contracts: source-qualified measures, dimensions and returnNegative; no idempotency claim verified." }, { "id": "SRC-008", "title": "Inventory Visibility reservations", "organization": "Microsoft", "url": "https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-visibility-reservations", "version_or_date": "Public page inspected 2026-09-09; revision pin pending", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-09T19:25:00Z", "relevance": "Selected indexed mapping/formula text: soft reservation and offsets require configured semantics." }, { "id": "SRC-009", "title": "PROV-DM", "organization": "W3C", "url": "https://www.w3.org/TR/prov-dm/", "version_or_date": "Recommendation 2013-04-30", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-09T19:25:00Z", "relevance": "Attribution and derivation alignment; no inventory authority or correctness inferred." }, { "id": "SRC-010", "title": "Date and Time on the Internet: Timestamps", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339 July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-09T19:25:00Z", "relevance": "Seconds and explicit offset; time is not identity, total ordering or snapshot consistency." } ], "structure": { "bundles": [ { "id": "stock-position-identity-and-custody", "name": "Position identity and custody", "description": "Stock-position concerns: position identity and custody.", "rationale": "Groups two subject-specific records while keeping stock quantities separate from goods and movement masters.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-009" ], "layers": [ { "id": "position-grain", "name": "Position key and aggregation grain", "description": "Time-qualified stock-position assertions for position key and aggregation grain, with declared source semantics and master authority.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "findings": [ { "id": "position-grain-record", "name": "Position key and aggregation grain record", "description": "Time-qualified stock-position assertions for position key and aggregation grain, with declared source semantics and master authority.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "questions": [ { "id": "position-grain-q01", "text": "Which issuer, product reference and complete dimension tuple identify this position without merging distinct lots or owners?", "kind": "identity", "answer_data": [ "position-grain-position-key" ] }, { "id": "position-grain-q02", "text": "Which dimensions were filtered before aggregation, which were grouped, and which were suppressed from this view?", "kind": "composition", "answer_data": [ "position-grain-aggregation-contract" ] }, { "id": "position-grain-q03", "text": "Does an absent row mean zero stock, an excluded dimension, no history or an incomplete response?", "kind": "quality", "answer_data": [ "position-grain-row-presence" ] } ], "data_elements": [ { "id": "position-grain-position-key", "name": "position-key", "description": "Proposed structured answer group: issuer URI; product reference; dimension key/value array; identity revision. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "position-grain-aggregation-contract", "name": "aggregation-contract", "description": "Proposed structured answer group: filter expression; grouping keys; omitted dimensions; source query digest. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "position-grain-row-presence", "name": "row-presence", "description": "Proposed structured answer group: state enum; completeness declaration; exclusion reason; evidence reference. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "position-grain-evidence", "name": "Position key and aggregation grain evidence", "description": "Scoped snapshot, mapping or master receipt evidence for position key and aggregation grain. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "custody-location", "name": "Owner, custodian and location scope", "description": "Time-qualified stock-position assertions for owner, custodian and location scope, with declared source semantics and master authority.", "source_refs": [ "SRC-004", "SRC-001", "SRC-009" ], "findings": [ { "id": "custody-location-record", "name": "Owner, custodian and location scope record", "description": "Time-qualified stock-position assertions for owner, custodian and location scope, with declared source semantics and master authority.", "source_refs": [ "SRC-004", "SRC-001", "SRC-009" ], "questions": [ { "id": "custody-location-q01", "text": "Who owns the stock and who holds custody, under which organization and consignment references?", "kind": "ownership", "answer_data": [ "custody-location-party-bindings" ] }, { "id": "custody-location-q02", "text": "Which warehouse, bin, transit or external location is represented and which parent totals already include it?", "kind": "spatial", "answer_data": [ "custody-location-location-scope" ] }, { "id": "custody-location-q03", "text": "Which authority may disclose or change this owner's quantity without changing ownership merely because goods moved?", "kind": "authority", "answer_data": [ "custody-location-stock-authority" ] } ], "data_elements": [ { "id": "custody-location-party-bindings", "name": "party-bindings", "description": "Proposed structured answer group: owner ref; custodian ref; organization ref; consignment agreement ref. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-001", "SRC-009" ] }, { "id": "custody-location-location-scope", "name": "location-scope", "description": "Proposed structured answer group: location ref; location kind; parent aggregation refs; inclusion rule. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-001", "SRC-009" ] }, { "id": "custody-location-stock-authority", "name": "stock-authority", "description": "Proposed structured answer group: role ref; delegated scope; permitted action; policy ref. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-001", "SRC-009" ] } ], "artifacts": [ { "id": "custody-location-evidence", "name": "Owner, custodian and location scope evidence", "description": "Scoped snapshot, mapping or master receipt evidence for owner, custodian and location scope. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-004", "SRC-001", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "stock-measured-quantities-and-restrictions", "name": "Measured quantities and restrictions", "description": "Stock-position concerns: measured quantities and restrictions.", "rationale": "Groups two subject-specific records while keeping stock quantities separate from goods and movement masters.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "quantity-basis", "name": "Quantity basis and measurement semantics", "description": "Time-qualified stock-position assertions for quantity basis and measurement semantics, with declared source semantics and master authority.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "quantity-basis-record", "name": "Quantity basis and measurement semantics record", "description": "Time-qualified stock-position assertions for quantity basis and measurement semantics, with declared source semantics and master authority.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "quantity-basis-q01", "text": "What quantity, unit, precision and product-specific conversion basis does each measure carry?", "kind": "measurement", "answer_data": [ "quantity-basis-quantity-basis" ] }, { "id": "quantity-basis-q02", "text": "Is the value counted, measured, estimated or system-derived, and what uncertainty or rounding accompanies it?", "kind": "evidence", "answer_data": [ "quantity-basis-measurement-method" ] }, { "id": "quantity-basis-q03", "text": "Are negative, zero, unavailable and unknown values permitted for this measure, and what evidence explains an exception?", "kind": "exception", "answer_data": [ "quantity-basis-quantity-state" ] } ], "data_elements": [ { "id": "quantity-basis-quantity-basis", "name": "quantity-basis", "description": "Proposed structured answer group: decimal lexical value; unit code; unit system; conversion ref; precision. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "quantity-basis-measurement-method", "name": "measurement-method", "description": "Proposed structured answer group: kind enum; method ref; uncertainty; rounding rule. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "quantity-basis-quantity-state", "name": "quantity-state", "description": "Proposed structured answer group: state enum; sign policy; exception ref; source value. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "quantity-basis-evidence", "name": "Quantity basis and measurement semantics evidence", "description": "Scoped snapshot, mapping or master receipt evidence for quantity basis and measurement semantics. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "stock-restrictions", "name": "Stock status, condition and traceability", "description": "Time-qualified stock-position assertions for stock status, condition and traceability, with declared source semantics and master authority.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "findings": [ { "id": "stock-restrictions-record", "name": "Stock status, condition and traceability record", "description": "Time-qualified stock-position assertions for stock status, condition and traceability, with declared source semantics and master authority.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "stock-restrictions-q01", "text": "Which source-defined status and lot or serial constraints qualify the reported quantity?", "kind": "classification", "answer_data": [ "stock-restrictions-stock-dimensions" ] }, { "id": "stock-restrictions-q02", "text": "Which quarantines, damage, expiry or other restrictions affect usability, and where is the authoritative evidence?", "kind": "constraint", "answer_data": [ "stock-restrictions-usability-restrictions" ] }, { "id": "stock-restrictions-q03", "text": "Can status buckets overlap, and how is a transition represented without counting the same stock twice?", "kind": "state", "answer_data": [ "stock-restrictions-bucket-overlap" ] } ], "data_elements": [ { "id": "stock-restrictions-stock-dimensions", "name": "stock-dimensions", "description": "Proposed structured answer group: status code; vocabulary URI; lot refs; serial refs. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "stock-restrictions-usability-restrictions", "name": "usability-restrictions", "description": "Proposed structured answer group: restriction kind; applicable quantity; effective interval; evidence refs. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "stock-restrictions-bucket-overlap", "name": "bucket-overlap", "description": "Proposed structured answer group: partition policy; overlap refs; transition ref; deduplication rule. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "stock-restrictions-evidence", "name": "Stock status, condition and traceability evidence", "description": "Scoped snapshot, mapping or master receipt evidence for stock status, condition and traceability. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "stock-availability-and-commitments", "name": "Availability and commitments", "description": "Stock-position concerns: availability and commitments.", "rationale": "Groups two subject-specific records while keeping stock quantities separate from goods and movement masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008" ], "layers": [ { "id": "reservation-availability", "name": "Reservations and usable quantity", "description": "Time-qualified stock-position assertions for reservations and usable quantity, with declared source semantics and master authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "findings": [ { "id": "reservation-availability-record", "name": "Reservations and usable quantity record", "description": "Time-qualified stock-position assertions for reservations and usable quantity, with declared source semantics and master authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "questions": [ { "id": "reservation-availability-q01", "text": "What physical and expected-receipt reservations apply, at which dimension hierarchy and for which demand references?", "kind": "relationship", "answer_data": [ "reservation-availability-reservation-bindings" ] }, { "id": "reservation-availability-q02", "text": "Which versioned formula and inputs produce availability, including soft reservation offsets without duplicate subtraction?", "kind": "measurement", "answer_data": [ "reservation-availability-availability-derivation" ] }, { "id": "reservation-availability-q03", "text": "Is the result informational or an authoritative booking response, and what expiry and access conditions limit reliance on it?", "kind": "authority", "answer_data": [ "reservation-availability-reliance-boundary" ] } ], "data_elements": [ { "id": "reservation-availability-reservation-bindings", "name": "reservation-bindings", "description": "Proposed structured answer group: reservation refs; source bucket; hierarchy grain; demand refs. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "reservation-availability-availability-derivation", "name": "availability-derivation", "description": "Proposed structured answer group: formula ref; input measures; offset mapping; version. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "reservation-availability-reliance-boundary", "name": "reliance-boundary", "description": "Proposed structured answer group: authority kind; calculated at; expires at; permitted use. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "reservation-availability-evidence", "name": "Reservations and usable quantity evidence", "description": "Scoped snapshot, mapping or master receipt evidence for reservations and usable quantity. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "projected-stock", "name": "Incoming, outgoing and projected position", "description": "Time-qualified stock-position assertions for incoming, outgoing and projected position, with declared source semantics and master authority.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "findings": [ { "id": "projected-stock-record", "name": "Incoming, outgoing and projected position record", "description": "Time-qualified stock-position assertions for incoming, outgoing and projected position, with declared source semantics and master authority.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "questions": [ { "id": "projected-stock-q01", "text": "Which confirmed or tentative receipts and issues contribute to the selected planning horizon?", "kind": "event", "answer_data": [ "projected-stock-planned-flows" ] }, { "id": "projected-stock-q02", "text": "Which forecast assumptions distinguish projected stock from current physical on-hand and available-to-promise?", "kind": "measurement", "answer_data": [ "projected-stock-forecast-basis" ] }, { "id": "projected-stock-q03", "text": "How are canceled, delayed or partially fulfilled commitments reflected without rewriting observed quantities?", "kind": "lifecycle", "answer_data": [ "projected-stock-commitment-change" ] } ], "data_elements": [ { "id": "projected-stock-planned-flows", "name": "planned-flows", "description": "Proposed structured answer group: order refs; direction; quantity; due instant; commitment status. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] }, { "id": "projected-stock-forecast-basis", "name": "forecast-basis", "description": "Proposed structured answer group: horizon; scenario ref; calculation version; certainty. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] }, { "id": "projected-stock-commitment-change", "name": "commitment-change", "description": "Proposed structured answer group: change ref; superseded forecast; realized portion; remaining portion. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "projected-stock-evidence", "name": "Incoming, outgoing and projected position evidence", "description": "Scoped snapshot, mapping or master receipt evidence for incoming, outgoing and projected position. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "stock-observation-time-and-reconciliation", "name": "Observation time and reconciliation", "description": "Stock-position concerns: observation time and reconciliation.", "rationale": "Groups two subject-specific records while keeping stock quantities separate from goods and movement masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010" ], "layers": [ { "id": "snapshot-currency", "name": "Snapshot currency and source ordering", "description": "Time-qualified stock-position assertions for snapshot currency and source ordering, with declared source semantics and master authority.", "source_refs": [ "SRC-006", "SRC-007", "SRC-010", "SRC-009" ], "findings": [ { "id": "snapshot-currency-record", "name": "Snapshot currency and source ordering record", "description": "Time-qualified stock-position assertions for snapshot currency and source ordering, with declared source semantics and master authority.", "source_refs": [ "SRC-006", "SRC-007", "SRC-010", "SRC-009" ], "questions": [ { "id": "snapshot-currency-q01", "text": "At what effective instant and recording instant was the position observed, with which explicit timezone and source watermark?", "kind": "temporal", "answer_data": [ "snapshot-currency-snapshot-clock" ] }, { "id": "snapshot-currency-q02", "text": "Are all pages and dimensions from one consistent snapshot, or is consistency unknown or explicitly eventual?", "kind": "quality", "answer_data": [ "snapshot-currency-snapshot-consistency" ] }, { "id": "snapshot-currency-q03", "text": "Which late, repeated or corrected source records change the interpretation, and what stale-data policy prevents treating old stock as current?", "kind": "provenance", "answer_data": [ "snapshot-currency-freshness-policy" ] } ], "data_elements": [ { "id": "snapshot-currency-snapshot-clock", "name": "snapshot-clock", "description": "Proposed structured answer group: effective timestamp; recorded timestamp; source sequence; snapshot ID. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-007", "SRC-010", "SRC-009" ] }, { "id": "snapshot-currency-snapshot-consistency", "name": "snapshot-consistency", "description": "Proposed structured answer group: scope; page tokens; consistency declaration; missing partitions. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-007", "SRC-010", "SRC-009" ] }, { "id": "snapshot-currency-freshness-policy", "name": "freshness-policy", "description": "Proposed structured answer group: maximum age; last sync; correction refs; duplicate handling; stale state. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-007", "SRC-010", "SRC-009" ] } ], "artifacts": [ { "id": "snapshot-currency-evidence", "name": "Snapshot currency and source ordering evidence", "description": "Scoped snapshot, mapping or master receipt evidence for snapshot currency and source ordering. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-006", "SRC-007", "SRC-010", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "count-adjustment", "name": "Count evidence and adjustment disposition", "description": "Time-qualified stock-position assertions for count evidence and adjustment disposition, with declared source semantics and master authority.", "source_refs": [ "SRC-005", "SRC-009", "SRC-010" ], "findings": [ { "id": "count-adjustment-record", "name": "Count evidence and adjustment disposition record", "description": "Time-qualified stock-position assertions for count evidence and adjustment disposition, with declared source semantics and master authority.", "source_refs": [ "SRC-005", "SRC-009", "SRC-010" ], "questions": [ { "id": "count-adjustment-q01", "text": "What was independently counted, when and by whom, against which expected position and method?", "kind": "evidence", "answer_data": [ "count-adjustment-count-evidence" ] }, { "id": "count-adjustment-q02", "text": "Which movements occurred between count and application, and how was the difference reconciled before approval?", "kind": "validation", "answer_data": [ "count-adjustment-discrepancy-analysis" ] }, { "id": "count-adjustment-q03", "text": "Was an adjustment proposed, approved, applied or reversed, and where is the immutable master receipt?", "kind": "decision", "answer_data": [ "count-adjustment-adjustment-disposition" ] } ], "data_elements": [ { "id": "count-adjustment-count-evidence", "name": "count-evidence", "description": "Proposed structured answer group: count ref; counted quantity; count time; actor; expected snapshot. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-009", "SRC-010" ] }, { "id": "count-adjustment-discrepancy-analysis", "name": "discrepancy-analysis", "description": "Proposed structured answer group: intervening movement refs; reconciled difference; reason; unresolved amount. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-009", "SRC-010" ] }, { "id": "count-adjustment-adjustment-disposition", "name": "adjustment-disposition", "description": "Proposed structured answer group: state; approval ref; master transaction ref; reversal ref. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "count-adjustment-evidence", "name": "Count evidence and adjustment disposition evidence", "description": "Scoped snapshot, mapping or master receipt evidence for count evidence and adjustment disposition. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-005", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "stock-change-lineage-and-operational-boundary", "name": "Change lineage and operational boundary", "description": "Stock-position concerns: change lineage and operational boundary.", "rationale": "Groups two subject-specific records while keeping stock quantities separate from goods and movement masters.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ], "layers": [ { "id": "balance-lineage", "name": "Movement lineage and balance reconciliation", "description": "Time-qualified stock-position assertions for movement lineage and balance reconciliation, with declared source semantics and master authority.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ], "findings": [ { "id": "balance-lineage-record", "name": "Movement lineage and balance reconciliation record", "description": "Time-qualified stock-position assertions for movement lineage and balance reconciliation, with declared source semantics and master authority.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ], "questions": [ { "id": "balance-lineage-q01", "text": "Which opening position and authoritative movement records explain the closing position for the chosen dimension grain?", "kind": "provenance", "answer_data": [ "balance-lineage-balance-lineage" ] }, { "id": "balance-lineage-q02", "text": "Which unexplained differences, omitted events or unit conversions prevent a valid reconciliation?", "kind": "exception", "answer_data": [ "balance-lineage-reconciliation-exceptions" ] }, { "id": "balance-lineage-q03", "text": "Are the evidence set and reconstruction rule complete enough to reproduce the view without claiming an event feed itself is a balance?", "kind": "validation", "answer_data": [ "balance-lineage-reconstruction-evidence" ] } ], "data_elements": [ { "id": "balance-lineage-balance-lineage", "name": "balance-lineage", "description": "Proposed structured answer group: opening snapshot; closing snapshot; movement refs; reconstruction rule. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ] }, { "id": "balance-lineage-reconciliation-exceptions", "name": "reconciliation-exceptions", "description": "Proposed structured answer group: difference; missing refs; conversion exceptions; disposition. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ] }, { "id": "balance-lineage-reconstruction-evidence", "name": "reconstruction-evidence", "description": "Proposed structured answer group: coverage interval; source completeness; rule version; verification result. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "balance-lineage-evidence", "name": "Movement lineage and balance reconciliation evidence", "description": "Scoped snapshot, mapping or master receipt evidence for movement lineage and balance reconciliation. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "action-boundary", "name": "Operational action and concurrency boundary", "description": "Time-qualified stock-position assertions for operational action and concurrency boundary, with declared source semantics and master authority.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ], "findings": [ { "id": "action-boundary-record", "name": "Operational action and concurrency boundary record", "description": "Time-qualified stock-position assertions for operational action and concurrency boundary, with declared source semantics and master authority.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "action-boundary-q01", "text": "Which authorized master endpoint accepts a reservation, transfer or adjustment instead of treating a local property edit as execution?", "kind": "authority", "answer_data": [ "action-boundary-action-routing" ] }, { "id": "action-boundary-q02", "text": "Which expected version, action identifier and receipt distinguish a safely confirmed action from an uncertain or duplicated request?", "kind": "requirement", "answer_data": [ "action-boundary-action-preconditions" ] }, { "id": "action-boundary-q03", "text": "What must the agent do when the master rejects a request, the response is lost or another worker changed the position?", "kind": "exception", "answer_data": [ "action-boundary-uncertain-outcome" ] } ], "data_elements": [ { "id": "action-boundary-action-routing", "name": "action-routing", "description": "Proposed structured answer group: action kind; master endpoint ref; policy ref; authority scope. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ] }, { "id": "action-boundary-action-preconditions", "name": "action-preconditions", "description": "Proposed structured answer group: expected version; request ID; idempotency capability declaration; receipt ref. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ] }, { "id": "action-boundary-uncertain-outcome", "name": "uncertain-outcome", "description": "Proposed structured answer group: state; rejection code; reconciliation action; retry policy ref. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "action-boundary-evidence", "name": "Operational action and concurrency boundary evidence", "description": "Scoped snapshot, mapping or master receipt evidence for operational action and concurrency boundary. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "stock-governed-stock-knowledge-and-exchange", "name": "Governed stock knowledge and exchange", "description": "Stock-position concerns: governed stock knowledge and exchange.", "rationale": "Groups two subject-specific records while keeping stock quantities separate from goods and movement masters.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009" ], "layers": [ { "id": "stock-governance", "name": "Mastership, access and retention", "description": "Time-qualified stock-position assertions for mastership, access and retention, with declared source semantics and master authority.", "source_refs": [ "SRC-004", "SRC-007", "SRC-009" ], "findings": [ { "id": "stock-governance-record", "name": "Mastership, access and retention record", "description": "Time-qualified stock-position assertions for mastership, access and retention, with declared source semantics and master authority.", "source_refs": [ "SRC-004", "SRC-007", "SRC-009" ], "questions": [ { "id": "stock-governance-q01", "text": "Which source owns each measure, and which cached or federated copies are subordinate to that authority?", "kind": "ownership", "answer_data": [ "stock-governance-measure-mastership" ] }, { "id": "stock-governance-q02", "text": "Which owner, counterparty or location details may each role read, aggregate or export?", "kind": "access", "answer_data": [ "stock-governance-disclosure-scope" ] }, { "id": "stock-governance-q03", "text": "Which records must remain reproducible after correction, deletion or access withdrawal, subject to the applicable retention policy?", "kind": "retention", "answer_data": [ "stock-governance-retention-contract" ] } ], "data_elements": [ { "id": "stock-governance-measure-mastership", "name": "measure-mastership", "description": "Proposed structured answer group: measure ID; master ref; cache location; synchronization policy. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007", "SRC-009" ] }, { "id": "stock-governance-disclosure-scope", "name": "disclosure-scope", "description": "Proposed structured answer group: role ref; field scope; aggregation threshold; export restriction. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007", "SRC-009" ] }, { "id": "stock-governance-retention-contract", "name": "retention-contract", "description": "Proposed structured answer group: policy ref; evidence retention; correction chain; redaction receipt. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007", "SRC-009" ] } ], "artifacts": [ { "id": "stock-governance-evidence", "name": "Mastership, access and retention evidence", "description": "Scoped snapshot, mapping or master receipt evidence for mastership, access and retention. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-004", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "stock-exchange", "name": "Exchange fidelity and semantic validation", "description": "Time-qualified stock-position assertions for exchange fidelity and semantic validation, with declared source semantics and master authority.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "stock-exchange-record", "name": "Exchange fidelity and semantic validation record", "description": "Time-qualified stock-position assertions for exchange fidelity and semantic validation, with declared source semantics and master authority.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "stock-exchange-q01", "text": "Which source bucket, dimension, unit and timestamp mappings are preserved, transformed or lost in this projection?", "kind": "interoperability", "answer_data": [ "stock-exchange-mapping-contract" ] }, { "id": "stock-exchange-q02", "text": "Can the target represent unknown or signed balances when an EPCIS quantity has different constraints, or must export be rejected or explicitly extended?", "kind": "constraint", "answer_data": [ "stock-exchange-representation-limit" ] }, { "id": "stock-exchange-q03", "text": "Which subject-specific fixtures test consignment, hierarchy reservations, negative balances, concurrent counts and incomplete snapshots before an adapter is trusted?", "kind": "validation", "answer_data": [ "stock-exchange-conformance-evidence" ] } ], "data_elements": [ { "id": "stock-exchange-mapping-contract", "name": "mapping-contract", "description": "Proposed structured answer group: source version; target version; field map; loss register. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "stock-exchange-representation-limit", "name": "representation-limit", "description": "Proposed structured answer group: unsupported value; target constraint; rejection or extension; evidence. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "stock-exchange-conformance-evidence", "name": "conformance-evidence", "description": "Proposed structured answer group: fixture refs; expected results; observed results; unresolved failures. Explicit unknowns are allowed; nested executable schema remains deferred.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "stock-exchange-evidence", "name": "Exchange fidelity and semantic validation evidence", "description": "Scoped snapshot, mapping or master receipt evidence for exchange fidelity and semantic validation. Do not copy protected transaction payloads without permission.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Master-system ID first, then issuer-qualified UUID; immutable revision and exact-byte digest separately. Timestamp alone is not an identifier.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "read-position", "name": "Read a qualified stock position", "description": "Retrieve stock for one declared dimension grain.", "inputs": [ "Authorized source query", "Desired dimensions" ], "outputs": [ "Snapshot or explicit incomplete/unknown outcome" ], "preconditions": [ "Read permission and source contract" ], "effects": [ "No cross-owner aggregation or missing row interpreted as zero" ], "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "qualify-availability", "name": "Explain availability", "description": "Trace source-defined availability formulas without executing reservations.", "inputs": [ "Stock measures", "Formula and offset mappings" ], "outputs": [ "Qualified availability and unresolved inputs" ], "preconditions": [ "Compatible grain, units and source time" ], "effects": [ "No universal subtraction or physical-stock inference from future reservations" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "project-stock", "name": "Describe projected stock", "description": "Keep planning-horizon estimates distinct from observed balances.", "inputs": [ "Current snapshot", "Referenced planned receipts and issues" ], "outputs": [ "Scenario-qualified projection" ], "preconditions": [ "Declared plan version and fulfillment status" ], "effects": [ "No delivery promise or transaction authority granted" ], "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "reconcile-count", "name": "Reconcile count evidence", "description": "Compare a count and intervening movement evidence before proposing an adjustment.", "inputs": [ "Count record", "Source snapshots and movement references" ], "outputs": [ "Explained difference or unresolved discrepancy" ], "preconditions": [ "Matched owner, grain, unit and time" ], "effects": [ "No booking from count alone; approval remains external" ], "source_refs": [ "SRC-005", "SRC-009" ] }, { "id": "route-stock-action", "name": "Route an authorized action", "description": "Describe a master-mediated reservation or adjustment with explicit uncertain outcomes.", "inputs": [ "Authorized request", "Expected state and master capability declaration" ], "outputs": [ "Master receipt or uncertain/rejected outcome" ], "preconditions": [ "Actual delegated authority and verified endpoint contract" ], "effects": [ "No local property edit masquerades as execution; no blind retry after lost response" ], "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "exchange-position", "name": "Exchange with semantic loss report", "description": "Map authorized stock knowledge while preserving incompatible target constraints.", "inputs": [ "Source snapshot", "Pinned target mapping" ], "outputs": [ "Projection and loss/rejection report" ], "preconditions": [ "Source disclosure allowed and target constraints checked" ], "effects": [ "Reject unqualified signed stock to positive-only event quantity mapping" ], "source_refs": [ "SRC-006", "SRC-007", "SRC-009" ] } ], "composition": [ { "target": "WM-OBJ-001", "relation": "REFERENCE", "purpose": "Link identifiable physical items only when item-level evidence exists; aggregate remains nonphysical.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "WM-OBJ-002", "relation": "REFERENCE", "purpose": "Resolve product identity and qualified unit basis.", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-FLW-012", "relation": "REFERENCE", "purpose": "Link authoritative stock movements without assuming complete ledger coverage.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "https://ref.gs1.org/standards/epcis/2.0.1/", "relation": "ALIGN", "purpose": "Candidate event-evidence alignment with explicit quantity and time mapping losses; not conformance.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "https://www.w3.org/TR/prov-dm/", "relation": "ALIGN", "purpose": "Describe attribution and derivation, not permissions or physical truth.", "required": false, "source_refs": [ "SRC-009" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner and delegated inventory steward.", "Register authoritative stock, product, movement and location namespaces.", "Bind actual read, export, action and retention policies before operation." ], "namespace_guidance": "Issuer-qualified position ID plus explicit dimension tuple and immutable snapshot ID; neither product code nor timestamp alone identifies the position.", "registry_links": [ "Model registry", "Stock source registry", "Product and location registries", "Movement and action receipt registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve grain, unit, bucket semantics, effective time and unknown values.", "Never add overlapping status buckets or hierarchy reservations without a declared aggregation rule." ], "patch_rules": [ "Authorized namespaced schema extension with pinned base digest; reject incompatible unit or grain changes.", "Corrections append successor snapshots and reasons; stale-base edits do not overwrite a master." ], "compatibility_rules": [ "A changed bucket meaning or dimension grain needs explicit migration and new schema revision.", "Lossy exchange cannot silently replace authoritative stock data." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed issuer-qualified URI or global identifier", "Dimension-issued UUID with issuer context" ], "timestamp_rule": "RFC 3339 timestamps with seconds and explicit offset or Z; distinguish effective, recorded and counted times. Timestamps are not collision-proof identity.", "serial_naming_rule": "Artifact-kind prefix plus stable escaped identifier and revision; timestamp may be appended for readability, not uniqueness.", "integrity_rule": "Preserve exact-byte digest, source receipt and mapping version; a digest proves byte identity, not stock truth." }, "policies": [ "Availability formulas and allowed negative values must be declared by measure and source.", "Count evidence does not authorize inventory adjustments or legal ownership changes.", "On missing access, incomplete snapshot or stale evidence preserve unknowns; do not infer zero.", "Do not retry uncertain operational actions until the authoritative receipt and idempotency capabilities have been checked." ], "crud": { "read": [ "Read owner policy, pinned specification, source grain, snapshot currency and access scope before using quantities." ], "create": [ "Create a qualified snapshot from authorized source evidence; retain unobserved and excluded dimensions explicitly." ], "update": [ "Append corrected snapshots with expected-base checks and provenance; route operational actions to the authorized master and verify its receipt." ], "delete": [ "Apply retention and legal-hold policies; tombstone local records with protected provenance, never cascade deletion into product, movement or organization masters." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Defines namespaces and federation policy." ] }, { "name": "Inventory steward", "responsibilities": [ "Owns stock measure semantics and source bindings." ] }, { "name": "Count observer", "responsibilities": [ "Records evidence without assuming adjustment approval." ] }, { "name": "Adjustment approver", "responsibilities": [ "Authorizes a scoped master change under policy." ] }, { "name": "Reviewer", "responsibilities": [ "Checks aggregation, reconciliation and mappings." ] }, { "name": "Custodian", "responsibilities": [ "Maintains authorized caches and evidence retention." ] } ], "access": { "default_rule": "Deny unless the owning Dimension explicitly authorizes the scope and purpose.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Only recorded scoped and time-limited delegation; no stock custody implies unrestricted disclosure." ], "audit_requirements": [ "Record actor, purpose, source snapshot, action decision and receipt without secrets." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Dimension owner and policy", "Pinned stock model and source-grain bindings", "Authorized snapshot and freshness rules", "Dependencies, validation, extensions, action boundaries and retirement" ] } }, "coverage": { "claim": "Proposed stock-position information contract with twelve subject-specific records and thirty-six authored questions. No independent external review, transactional inventory engine or normative conformance is claimed.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Issuer and complete stock dimension tuple." }, { "dimension": "classification", "status": "covered", "notes": "Source-qualified stock status and nonphysical aggregate class." }, { "dimension": "direct properties", "status": "covered", "notes": "Quantity, unit, precision and declared bucket semantics." }, { "dimension": "recognition", "status": "covered", "notes": "Source keys, dimension grain and observation evidence; not visual item recognition." }, { "dimension": "capabilities", "status": "covered", "notes": "Six bounded proposed information operations; execution authority external." }, { "dimension": "lifecycle", "status": "covered", "notes": "Snapshot correction, count application and action disposition." }, { "dimension": "temporal", "status": "covered", "notes": "Effective, recorded and counted time plus freshness and completeness." }, { "dimension": "relationships", "status": "covered", "notes": "Owner, custodian, product, location, movement and order references." }, { "dimension": "provenance", "status": "covered", "notes": "Snapshot, count and reconstruction evidence." }, { "dimension": "ownership", "status": "covered", "notes": "Goods owner, custodian and data authority distinguished." }, { "dimension": "validation", "status": "covered", "notes": "Reconciliation, incompatible quantities and incomplete-snapshot fixtures proposed." }, { "dimension": "access", "status": "covered", "notes": "Role and owner-scoped disclosure." }, { "dimension": "retention", "status": "covered", "notes": "Policy-controlled preservation, correction and tombstones." }, { "dimension": "interoperability", "status": "covered", "notes": "Source measure mapping with positive-only event quantity limitation." }, { "dimension": "Physical geometry and material", "status": "not-applicable", "notes": "A quantity position is informational; actual item characteristics remain referenced." }, { "dimension": "Executable conformance", "status": "gap", "notes": "Nested schemas, adapters, real fixtures and independent external review deferred." } ], "known_omissions": [ "Claude and Grok each timed out once. No independent external review; Codex-only result must remain reviewable-draft.", "Mutable Microsoft page revision pins remain open; Odoo stock report inspected via indexed text only after direct fetch timeout.", "GS1 URL says 2.0.1 while retrieved PDF header says Release 2.0 June 2022; exact normative adapter pin and conformance remain unresolved.", "Nested field groups are proposed information contracts, not executable instance schemas; no inventory engine, reservation adapter or concurrency test delivered.", "Sector-specific unit conversion, negative-stock, quarantine, consignment and retention profiles need specialist review.", "Actual master authority, expected-version and idempotency capabilities must be verified by adopters; source API inspection did not establish these guarantees." ], "conflicts": [], "regional_assumptions": [ "Owning Dimension supplies jurisdiction, warehouse, confidentiality and retention policies. No legal ownership or financial valuation determination is made." ], "adversarial_checks": [ "Reject owner and custodian conflation.", "Reject sums across overlapping buckets or reservation hierarchy grains.", "Reject absent row, stale value or omitted quantity interpreted as zero.", "Reject expected-receipt reservation as physical stock.", "Reject a count applied without intervening movement reconciliation.", "Reject signed or zero stock blindly exported as positive EPCIS QuantityElement.", "Reject local edit treated as execution and uncertain-action blind retries." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "A source-qualified stock position aggregates quantities at a declared grain and time. Physical item, product, location, movement, reservation and valuation masters remain distinct; frozen REFERENCE WM-OBJ-001 is preserved." }, "decisions": [ { "concept": "Nonphysical position and master boundaries", "disposition": "accepted", "rationale": "Quantity and stock grain are intrinsic; geometry and material belong to referenced physical subjects." }, { "concept": "Aggregation, ownership and reservation", "disposition": "accepted", "rationale": "Source-defined hierarchy, overlap and offsets prevent naive totals; custody is not ownership and expected receipts are not on-hand." }, { "concept": "Time, counts and operational actions", "disposition": "accepted with limitations", "rationale": "Snapshots expose consistency and freshness; counts need reconciliation before authorized application; action effects require actual master receipts." }, { "concept": "EPCIS representation", "disposition": "accepted with limitations", "rationale": "Evidence alignment does not imply balance reconstruction; signed and zero balances require explicit target constraint handling." }, { "concept": "Evidence and runtime completeness", "disposition": "deferred", "rationale": "Selected source passages motivate candidate contracts; revision pins, nested schemas, adapters and real concurrency fixtures are not established." }, { "concept": "Provider attribution", "disposition": "accepted with mandatory hold", "rationale": "One terminal timeout per external provider; frozen no-tools Codex self-review is not independent evidence." } ], "publicationHolds": [ "No independent external research or review: Claude and Grok each timed out once. Codex-only research and self-audit remain reviewable-draft, never canonical.", "Mutable Microsoft revision pins remain open. Odoo stock-report evidence is selected indexed text; its direct fetch timed out.", "GS1 URL 2.0.1 returned a PDF labelled Release 2.0 June 2022. Exact normative adapter version and conformance remain unresolved.", "No executable nested instance schema, transactional inventory engine, reservation adapter, concurrency fixture or verified round-trip translation is delivered.", "Warehouse and sector-specific conversion, quarantine, consignment, negative-stock and retention policies need specialist review.", "Adopters must verify real master permissions, snapshot consistency, expected-version and idempotency capabilities before operational use.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Independent external review and exact source revision pins.", "Executable typed fields and negative fixtures for overlapping status and reservation hierarchies.", "Concurrent counting, uncertain-action receipts and complete snapshot tests against actual inventory masters.", "Loss-aware EPCIS and inventory API adapters with signed and unknown quantity fixtures." ] }, "statistics": { "sources": 10, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }