# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T21:35:57Z", "synthesisSha256": "297f57835b48f0323b197e693417706ec207214100e36fdcc2589efc37afbff8", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-MAT-004", "registryId": "vr.wm-mat-004", "name": "Material Batch / Lot", "version": "0.1.0-reviewable", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.MAT.SAM" ], "tags": [ "material", "batch", "lot", "phy.mat.sam" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-mat-004-material-batch-lot/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-mat-004", "model": { "registry_id": "vr.wm-mat-004", "model_id": "WM-MAT-004", "name": "Material Batch / Lot", "entry_kind": "entity", "purpose": "Describe one identified quantity of material for qualified quality assessment and traceability across its history.", "scope_statement": "A persistent lot entity defined by an accountable assigning authority and a declared material and production or receipt boundary. Its record links evidence, quantities, portions and decisions. Expected uniformity is a claim within specified limits, not proof of conformance. Continuous production may use a declared quantity or interval boundary. Batch and lot equivalence is profile-dependent.", "in_scope": [ "Qualified lot identity, material reference, boundary rule and aliases", "Lot-specific quantity assertions, packaging membership, production and genealogy references", "Sampling and test evidence links, disposition assertions, storage history, expiry/retest and trace coverage", "Local revision, access, retention and interoperability requirements" ], "out_of_scope": [ "Substance, formulation and engineered-material master definitions; recipe design and production control", "Sample, laboratory test, measurement, shipment, container and custody-event master lifecycles", "Executing physical operations, issuing release or recall decisions, certifying safety or operating an inventory ledger", "Hazardous or controlled material operating instructions; only policy and authorized profile references are allowed" ], "boundary_notes": [ { "neighbor": "WM-MAT-001 Chemical Substance; WM-MAT-002 Engineered Material; WM-MAT-003 Mixture / Formulation", "distinction": "Reference the applicable material definition and version. A lot may instantiate a substance, engineered material or mixture; none of these is the lot identity.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "neighbor": "WM-MAT-005 Lab Sample / Specimen", "distinction": "A sample has its own identity and sampling lineage. Lot-level inference must cite representativeness assessment; sample lifecycle remains external.", "source_refs": [ "SRC-004" ] }, { "neighbor": "WM-MAT-007 Laboratory Test / Analysis; WM-MAT-008 Observation / Measurement Record", "distinction": "Reference test and observation masters and their revisions. This model records relevance and decision support, not laboratory execution or raw-result replacement.", "source_refs": [ "SRC-003", "SRC-004" ] }, { "neighbor": "WM-FLW-013 Supply-chain Trace / Chain of Custody", "distinction": "Keep lot-specific links and known trace coverage. Custody events, shipments and title transfers have separate masters; a location observation proves none of them by itself.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "neighbor": "Production event, logistics unit and quality decision", "distinction": "A persistent lot is neither the transformation that created it nor a container or decision. One lot may span containers and locations; one container may contain several lots.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ] }, "sources": [ { "id": "SRC-001", "title": "EPCIS Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/epcis/2.0.1/", "version_or_date": "Retrieved PDF labels itself Release 2.0, June 2022; URL revision discrepancy unresolved", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T21:34:34Z", "relevance": "Sections 7.3 and 7.4 distinguish quantity, event time, location, aggregation, transformation and correction. Conceptual support only; URL version must be reconciled before conformance claims." }, { "id": "SRC-002", "title": "EPCIS and CBV Implementation Guideline", "organization": "GS1", "url": "https://ref.gs1.org/guidelines/epcis-cbv/2.0.0/", "version_or_date": "Release 2.0, March 2023", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T21:34:34Z", "relevance": "Sections 3.2 and 5.5 illustrate product-plus-lot identity, logistics units and input/output events. Examples are not proof of complete genealogy or mandatory use of GS1 identifiers." }, { "id": "SRC-003", "title": "Q7 Good Manufacturing Practice Guidance for Active Pharmaceutical Ingredients", "organization": "Food and Drug Administration", "url": "https://www.fda.gov/media/71518/download", "version_or_date": "September 2016, Revision 1", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T21:34:34Z", "relevance": "Selected API-sector guidance: glossary, sections 5.4, 6, 7, 11 and 15. Supports qualified lot definition, record review, sample/test references, disposition and distinct expiry/retest concepts. Nonbinding recommendations, not universal material law." }, { "id": "SRC-004", "title": "Semantic Sensor Network Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-ssn/", "version_or_date": "2017 Recommendation text, December 2017 editorial status note", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T21:34:34Z", "relevance": "Sections 4.3, 4.5 and 4.7 distinguish sample, sampling, observation, feature, result and times. A sample relationship does not prove representativeness." }, { "id": "SRC-005", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T21:34:34Z", "relevance": "Entity, activity, attribution, qualified derivation and revision support evidence links. Provenance is neither truth certification nor an inventory balance algorithm." }, { "id": "SRC-006", "title": "NIST Guide to the SI, Chapter 7: Rules and Style Conventions for Expressing Values of Quantities", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/pml/special-publication-811/nist-guide-si-chapter-7-rules-and-style-conventions-expressing-values", "version_or_date": "Web page updated 2025-08-18; SP 811 Chapter 7", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T21:34:34Z", "relevance": "Sections 7.1-7.5 support explicit quantity values, units and separately described measurement conditions. Does not provide material-specific conversion factors or acceptance tolerances." }, { "id": "SRC-007", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002, section 5.6", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T21:34:34Z", "relevance": "Timestamp syntax with seconds and offset. Date-only labels, uncertain intervals and effective dates need separate fields; syntax does not establish chronology or shelf life." } ], "structure": { "bundles": [ { "id": "bundle-definition", "name": "Identity and declared extent", "description": "Define the persistent lot and applicable material profile.", "rationale": "Authored grouping of cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "layers": [ { "id": "layer-identity", "name": "Qualified lot identity", "description": "Keep assigning namespace, product/material context and original lot code. Never merge bare code matches across issuers or treat a scanned label as authenticated identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "findings": [ { "id": "finding-identity", "name": "Identifier authority and reconciliation", "description": "Keep assigning namespace, product/material context and original lot code. Never merge bare code matches across issuers or treat a scanned label as authenticated identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "q-identity-1", "text": "Which authority and material context make this lot reference unique?", "kind": "identity", "answer_data": [ "issuer namespace; master lot ID; original code; material reference; assignment evidence", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-identity-2", "text": "Which labels or external aliases have been reconciled to the master reference?", "kind": "provenance", "answer_data": [ "alias namespace; observed label; source artifact; match basis; reviewer; confidence", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-identity-3", "text": "How are colliding or unreadable lot codes kept unresolved without merging material?", "kind": "exception", "answer_data": [ "candidate references; ambiguity reason; quarantine-of-record flag; resolution owner; revision", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-identity-identity", "name": "identity", "description": "Candidate group: issuer namespace; master lot ID; original code; material reference; assignment evidence. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "data-identity-aliases", "name": "aliases", "description": "Candidate group: alias namespace; observed label; source artifact; match basis; reviewer; confidence. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "data-identity-conflicts", "name": "conflicts", "description": "Candidate group: candidate references; ambiguity reason; quarantine-of-record flag; resolution owner; revision. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Qualified lot identity evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-boundary", "name": "Lot definition and applicability", "description": "The grouping rule and uniformity claim need evidence. Production batch, receipt lot and supplier lot may differ. Record their mappings rather than silently equating them.", "source_refs": [ "SRC-002", "SRC-003" ], "findings": [ { "id": "finding-boundary", "name": "Declared material and boundary rule", "description": "The grouping rule and uniformity claim need evidence. Production batch, receipt lot and supplier lot may differ. Record their mappings rather than silently equating them.", "source_refs": [ "SRC-002", "SRC-003" ], "questions": [ { "id": "q-boundary-1", "text": "What quantity or production interval is included by the lot definition?", "kind": "definition", "answer_data": [ "boundary rule; discrete or continuous mode; start/end or quantity; inclusion/exclusion basis", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-boundary-2", "text": "Which material definition, grade and specification version apply to this lot?", "kind": "classification", "answer_data": [ "material type reference; grade; specification revision; sector; jurisdiction; effective scope", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-boundary-3", "text": "What evidence and limits support the claimed uniformity of the lot?", "kind": "quality", "answer_data": [ "claimed properties; limits; evidence links; assessment status; known heterogeneity", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-boundary-extent", "name": "extent", "description": "Candidate group: boundary rule; discrete or continuous mode; start/end or quantity; inclusion/exclusion basis. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "data-boundary-profile", "name": "profile", "description": "Candidate group: material type reference; grade; specification revision; sector; jurisdiction; effective scope. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "data-boundary-uniformity", "name": "uniformity", "description": "Candidate group: claimed properties; limits; evidence links; assessment status; known heterogeneity. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "artifact-boundary", "name": "Lot definition and applicability evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-physical", "name": "Quantity and physical allocation", "description": "Separate material amounts and portions from packaging identity.", "rationale": "Authored grouping of cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "layers": [ { "id": "layer-quantity", "name": "Quantity and reconciliation", "description": "Keep produced, received, sampled, consumed, shipped, lost and remaining quantities as qualified assertions. A balance requires compatible bases and complete events; do not invent exact conservation across unlike units or process losses.", "source_refs": [ "SRC-001", "SRC-006" ], "findings": [ { "id": "finding-quantity", "name": "Quantified lot balances with explicit basis", "description": "Keep produced, received, sampled, consumed, shipped, lost and remaining quantities as qualified assertions. A balance requires compatible bases and complete events; do not invent exact conservation across unlike units or process losses.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "q-quantity-1", "text": "What quantity is asserted for the lot on each measurement basis?", "kind": "measurement", "answer_data": [ "value; unit; quantity kind; gross/net/dry basis; conditions; uncertainty; observed time; source", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-quantity-2", "text": "Which evidence reconciles recorded inputs, outputs, samples and losses?", "kind": "validation", "answer_data": [ "event set; conversion basis; tolerance authority; accounted losses; residual; completeness", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-quantity-3", "text": "What remains available in the stated scope and as of which time?", "kind": "state", "answer_data": [ "location scope; as-of time; physical amount; reserved amount; held amount; overlapping-category rule; ledger reference", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-quantity-quantities", "name": "quantities", "description": "Candidate group: value; unit; quantity kind; gross/net/dry basis; conditions; uncertainty; observed time; source. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-quantity-balance", "name": "balance", "description": "Candidate group: event set; conversion basis; tolerance authority; accounted losses; residual; completeness. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-quantity-availability", "name": "availability", "description": "Candidate group: location scope; as-of time; physical amount; reserved amount; held amount; overlapping-category rule; ledger reference. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-quantity", "name": "Quantity and reconciliation evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-packaging", "name": "Portions and containers", "description": "Containment and repacking do not automatically create a new lot. Track portions and effective membership without assigning container identity to material or forcing a fresh lot for every split.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "finding-packaging", "name": "Material membership distinct from packaging identity", "description": "Containment and repacking do not automatically create a new lot. Track portions and effective membership without assigning container identity to material or forcing a fresh lot for every split.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "q-packaging-1", "text": "Which portions of the lot are associated with which containers or serial items?", "kind": "composition", "answer_data": [ "portion reference; container/item reference; quantity; effective interval; membership evidence", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-packaging-2", "text": "Which repacking or portioning event changed containment without changing lot identity?", "kind": "event", "answer_data": [ "event reference; prior/new containers; portion mapping; identity assessment; evidence", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-packaging-3", "text": "When does the adopted profile require a new lot identity for a division or combination?", "kind": "constraint", "answer_data": [ "profile version; triggering condition; responsible authority; successor links; unresolved decision", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-packaging-membership", "name": "membership", "description": "Candidate group: portion reference; container/item reference; quantity; effective interval; membership evidence. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-packaging-repacking", "name": "repacking", "description": "Candidate group: event reference; prior/new containers; portion mapping; identity assessment; evidence. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-packaging-identityrule", "name": "identityrule", "description": "Candidate group: profile version; triggering condition; responsible authority; successor links; unresolved decision. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "artifact-packaging", "name": "Portions and containers evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-origin", "name": "Origin and genealogy", "description": "Link actual origin and qualified input/output lineage.", "rationale": "Authored grouping of cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-production", "name": "Origin and production context", "description": "Reference the actual production or receipt occurrence and responsible actor. Plans, recipes and equipment masters stay outside. Unknown origin must remain unknown rather than inferred from the lot code.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ], "findings": [ { "id": "finding-production", "name": "Lot creation linked to actual occurrences", "description": "Reference the actual production or receipt occurrence and responsible actor. Plans, recipes and equipment masters stay outside. Unknown origin must remain unknown rather than inferred from the lot code.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ], "questions": [ { "id": "q-production-1", "text": "Which production or receipt occurrence established this lot?", "kind": "process", "answer_data": [ "event master reference; site; responsible role; process revision reference; creation basis", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-production-2", "text": "Which times distinguish production, receipt and recording of the origin assertion?", "kind": "temporal", "answer_data": [ "event start/end; receipt time; recorded time; offset; precision; uncertainty", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-production-3", "text": "Which deviations or missing records limit reliance on the stated origin?", "kind": "evidence", "answer_data": [ "deviation reference; affected extent; evidence gap; review status; accountable reviewer", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-production-origin", "name": "origin", "description": "Candidate group: event master reference; site; responsible role; process revision reference; creation basis. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ] }, { "id": "data-production-times", "name": "times", "description": "Candidate group: event start/end; receipt time; recorded time; offset; precision; uncertainty. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ] }, { "id": "data-production-deviations", "name": "deviations", "description": "Candidate group: deviation reference; affected extent; evidence gap; review status; accountable reviewer. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-production", "name": "Origin and production context evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-genealogy", "name": "Transformation genealogy", "description": "Retain directed input/output relations with event and quantity basis. A possible-contribution relation is not an exact allocation. Distinguish real rework occurrences from correction of their records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "findings": [ { "id": "finding-genealogy", "name": "Evidenced ancestry and successor links", "description": "Retain directed input/output relations with event and quantity basis. A possible-contribution relation is not an exact allocation. Distinguish real rework occurrences from correction of their records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "questions": [ { "id": "q-genealogy-1", "text": "Which input lots may have contributed to this lot through which transformations?", "kind": "relationship", "answer_data": [ "input reference; event ID; transformation grouping; quantity if known; allocation certainty", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-genealogy-2", "text": "Which successor lots resulted from blending, rework or other material transformation?", "kind": "lifecycle", "answer_data": [ "successor reference; transformation type; authority evidence; quantity basis; identity continuity decision", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-genealogy-3", "text": "Which missing edges, duplicate events or cycles make the genealogy unreliable?", "kind": "validation", "answer_data": [ "revision-aware graph; duplicate key; cycle finding; missing node; investigation status; coverage boundary", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-genealogy-inputs", "name": "inputs", "description": "Candidate group: input reference; event ID; transformation grouping; quantity if known; allocation certainty. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "data-genealogy-outputs", "name": "outputs", "description": "Candidate group: successor reference; transformation type; authority evidence; quantity basis; identity continuity decision. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "data-genealogy-graphcheck", "name": "graphcheck", "description": "Candidate group: revision-aware graph; duplicate key; cycle finding; missing node; investigation status; coverage boundary. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-genealogy", "name": "Transformation genealogy evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-evidence", "name": "Sampling and quality evidence", "description": "Keep sample representation and test interpretation explicit.", "rationale": "Authored grouping of cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "layers": [ { "id": "layer-sampling", "name": "Sampling evidence linkage", "description": "A sample and its test result remain external records. Preserve the lot or portion sampled, sampling procedure reference and stated limits on extrapolation.", "source_refs": [ "SRC-003", "SRC-004" ], "findings": [ { "id": "finding-sampling", "name": "Representativeness and sample identity", "description": "A sample and its test result remain external records. Preserve the lot or portion sampled, sampling procedure reference and stated limits on extrapolation.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "q-sampling-1", "text": "Which independently identified samples were taken from which lot portions?", "kind": "relationship", "answer_data": [ "sample master reference; portion; sampling occurrence; amount removed; time; custody link", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-sampling-2", "text": "Which sampling plan and assessment justify using those samples for this lot?", "kind": "requirement", "answer_data": [ "procedure revision; selection basis; intended feature; representativeness assessment; exclusions", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-sampling-3", "text": "Which sample damage, mix-up or custody gap restricts interpretation?", "kind": "exception", "answer_data": [ "sample reference; restriction; event evidence; reviewer; affected conclusions", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-sampling-samples", "name": "samples", "description": "Candidate group: sample master reference; portion; sampling occurrence; amount removed; time; custody link. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-sampling-plan", "name": "plan", "description": "Candidate group: procedure revision; selection basis; intended feature; representativeness assessment; exclusions. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-sampling-limitations", "name": "limitations", "description": "Candidate group: sample reference; restriction; event evidence; reviewer; affected conclusions. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-sampling", "name": "Sampling evidence linkage evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-quality", "name": "Tests and acceptance evidence", "description": "Link results and certificates with method, limits, version and assessment status. A certificate is evidence, not automatic release. Conflicting, missing or invalidated results remain visible.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-quality", "name": "Results assessed against a pinned specification", "description": "Link results and certificates with method, limits, version and assessment status. A certificate is evidence, not automatic release. Conflicting, missing or invalidated results remain visible.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "q-quality-1", "text": "Which test results and methods support each claimed lot property?", "kind": "measurement", "answer_data": [ "test/observation reference; property; method revision; value/unit; uncertainty or qualifier; sample link", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-quality-2", "text": "Against which limits and specification revision were the results assessed?", "kind": "quality", "answer_data": [ "requirement reference; limits and basis; evaluator; decision rule; pass/fail/unknown; scope", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-quality-3", "text": "Which certificates or contrary results qualify the quality assessment?", "kind": "evidence", "answer_data": [ "certificate issuer/reference/revision; authenticity assessment; contrary result; invalidation basis; unresolved gap", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-quality-results", "name": "results", "description": "Candidate group: test/observation reference; property; method revision; value/unit; uncertainty or qualifier; sample link. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "data-quality-assessment", "name": "assessment", "description": "Candidate group: requirement reference; limits and basis; evaluator; decision rule; pass/fail/unknown; scope. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "data-quality-documents", "name": "documents", "description": "Candidate group: certificate issuer/reference/revision; authenticity assessment; contrary result; invalidation basis; unresolved gap. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-quality", "name": "Tests and acceptance evidence evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-suitability", "name": "Disposition and suitability context", "description": "Record authorized decisions alongside condition and dating evidence.", "rationale": "Authored grouping of cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-disposition", "name": "Disposition and authorized decisions", "description": "Keep quality disposition, inventory availability and recall/hold assertions separate. Decisions apply to an explicit portion, use, site or market and interval. No test pass or elapsed date can authorize release.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "findings": [ { "id": "finding-disposition", "name": "Scoped release and restrictions", "description": "Keep quality disposition, inventory availability and recall/hold assertions separate. Decisions apply to an explicit portion, use, site or market and interval. No test pass or elapsed date can authorize release.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "questions": [ { "id": "q-disposition-1", "text": "Which authorized decision supports the recorded disposition?", "kind": "authority", "answer_data": [ "decision master reference; issuer role; authority evidence; scope; effective time; supersession", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-disposition-2", "text": "Which overlapping holds or restrictions still apply to the lot or a portion?", "kind": "state", "answer_data": [ "hold reference; affected portion/use/market; effective interval; reason class; conflict state", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-disposition-3", "text": "Which rejection, return or recall references change the lot assessment?", "kind": "lifecycle", "answer_data": [ "decision/event reference; affected extent; prior/new assertion; reviewer; unresolved consequences", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-disposition-decision", "name": "decision", "description": "Candidate group: decision master reference; issuer role; authority evidence; scope; effective time; supersession. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "data-disposition-restrictions", "name": "restrictions", "description": "Candidate group: hold reference; affected portion/use/market; effective interval; reason class; conflict state. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "data-disposition-changes", "name": "changes", "description": "Candidate group: decision/event reference; affected extent; prior/new assertion; reviewer; unresolved consequences. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-disposition", "name": "Disposition and authorized decisions evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-conditions", "name": "Storage and dating", "description": "Link storage requirements and observations to the affected portions and intervals. Distinguish expiration, retest due date and label precision. A retest does not by itself extend expiry or erase exposure history.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-conditions", "name": "Qualified condition and time-sensitive suitability", "description": "Link storage requirements and observations to the affected portions and intervals. Distinguish expiration, retest due date and label precision. A retest does not by itself extend expiry or erase exposure history.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-conditions-1", "text": "Where was each portion held under which required and observed conditions?", "kind": "spatial", "answer_data": [ "location reference; portion; interval; condition requirements; observations; monitoring gaps", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-conditions-2", "text": "Which expiry or retest date is asserted and on what supporting basis?", "kind": "temporal", "answer_data": [ "date type; value; precision; governing timezone if relevant; stability evidence; approval reference", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-conditions-3", "text": "How do excursions or proposed date changes affect the recorded suitability assessment?", "kind": "exception", "answer_data": [ "exposure reference; affected portion; assessment authority; old/new dating assertion; justification; unresolved restrictions", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-conditions-storage", "name": "storage", "description": "Candidate group: location reference; portion; interval; condition requirements; observations; monitoring gaps. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-conditions-dating", "name": "dating", "description": "Candidate group: date type; value; precision; governing timezone if relevant; stability evidence; approval reference. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-conditions-excursions", "name": "excursions", "description": "Candidate group: exposure reference; affected portion; assessment authority; old/new dating assertion; justification; unresolved restrictions. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-conditions", "name": "Storage and dating evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity", "name": "Distribution and record continuity", "description": "Expose trace boundaries and govern record exchange and retention.", "rationale": "Authored grouping of cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-distribution", "name": "Distribution and trace coverage", "description": "Reference shipments, custody and recipient evidence with scope and time. Location, possession and ownership are different claims. A trace report cannot claim unknown recipients are absent or issue a recall.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "findings": [ { "id": "finding-distribution", "name": "Bounded forward and backward trace", "description": "Reference shipments, custody and recipient evidence with scope and time. Location, possession and ownership are different claims. A trace report cannot claim unknown recipients are absent or issue a recall.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "questions": [ { "id": "q-distribution-1", "text": "Which shipments and recipients are evidenced for which lot quantities?", "kind": "relationship", "answer_data": [ "shipment master; portion; quantity basis; recipient role; event time; source evidence", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-distribution-2", "text": "Which actors held title, custody or record stewardship over each stated interval?", "kind": "ownership", "answer_data": [ "actor reference; role type; scope; interval; authority/transfer evidence; disputed status", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-distribution-3", "text": "Where does the trace stop and which return or onward-transfer links remain missing?", "kind": "validation", "answer_data": [ "authorized graph scope; frontier nodes; missing links; returns; as-of time; completeness qualification", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-distribution-destinations", "name": "destinations", "description": "Candidate group: shipment master; portion; quantity basis; recipient role; event time; source evidence. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "data-distribution-responsibility", "name": "responsibility", "description": "Candidate group: actor reference; role type; scope; interval; authority/transfer evidence; disputed status. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "data-distribution-coverage", "name": "coverage", "description": "Candidate group: authorized graph scope; frontier nodes; missing links; returns; as-of time; completeness qualification. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-distribution", "name": "Distribution and trace coverage evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-continuity", "name": "Record continuity and exchange", "description": "Corrections preserve prior assertions and reasons under retention policy; physical material disposal and record deletion are different. Mappings must carry unresolved qualifiers or report losses.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ], "findings": [ { "id": "finding-continuity", "name": "Governed revisions and bounded projections", "description": "Corrections preserve prior assertions and reasons under retention policy; physical material disposal and record deletion are different. Mappings must carry unresolved qualifiers or report losses.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ], "questions": [ { "id": "q-continuity-1", "text": "Which retention schedule and holds govern lot records and linked evidence copies?", "kind": "retention", "answer_data": [ "record category; policy version; retention trigger; hold; custodian; disposal authorization; tombstone scope", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-continuity-2", "text": "Which recipient can see each lot assertion and supporting artifact?", "kind": "access", "answer_data": [ "recipient role; purpose; scope; redaction rule; exception basis; access audit reference", "Source reference, assertion status and explicit unknown or not-applicable reason" ] }, { "id": "q-continuity-3", "text": "Which mapping and acceptance checks preserve lot identity, quantities and uncertainty during export?", "kind": "interoperability", "answer_data": [ "target schema/version; identity mapping; unit/time mapping; omitted qualifiers; loss report; validation outcome", "Source reference, assertion status and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-continuity-retention", "name": "retention", "description": "Candidate group: record category; policy version; retention trigger; hold; custodian; disposal authorization; tombstone scope. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ] }, { "id": "data-continuity-access", "name": "access", "description": "Candidate group: recipient role; purpose; scope; redaction rule; exception basis; access audit reference. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ] }, { "id": "data-continuity-exchange", "name": "exchange", "description": "Candidate group: target schema/version; identity mapping; unit/time mapping; omitted qualifiers; loss report; validation outcome. Profile-specific nested schemas and cardinalities remain to be developed.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-continuity", "name": "Record continuity and exchange evidence register", "description": "Versioned lot-local index of assertions and external master references, not replacement of those masters.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI or local UUID. Entries use opaque sequence keys, not dates or material names as sole identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-lot", "name": "Resolve qualified lot identity", "description": "Proposed operation, not implemented. Match issuer, material context and code with evidence; return ambiguity rather than merging aliases by resemblance.", "inputs": [ "qualified reference", "authorized view" ], "outputs": [ "resolved reference or ambiguity report" ], "preconditions": [ "Authenticated role and purpose authorized for every included record", "Evidence and profile identified; unresolved authority cannot become an approval", "Mutations require expected revision and idempotency key; duplicates or concurrent changes cause refusal" ], "effects": [ "Read-only identity assessment" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "record-lot-assertion", "name": "Record a lot assertion", "description": "Proposed operation, not implemented. Append quantity, condition or origin evidence without changing a physical lot or external master.", "inputs": [ "lot reference", "source assertion", "quantity/time basis", "expected revision" ], "outputs": [ "new local revision or refusal" ], "preconditions": [ "Authenticated role and purpose authorized for every included record", "Evidence and profile identified; unresolved authority cannot become an approval", "Mutations require expected revision and idempotency key; duplicates or concurrent changes cause refusal" ], "effects": [ "Append provenance and unresolved qualifiers; no stock movement" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "link-genealogy", "name": "Link evidenced genealogy", "description": "Proposed operation, not implemented. Append an input/output event reference and allocation certainty; flag duplicates and apparent cycles for review.", "inputs": [ "lot and event references", "input/output links", "expected revision" ], "outputs": [ "link revision and anomaly report or refusal" ], "preconditions": [ "Authenticated role and purpose authorized for every included record", "Evidence and profile identified; unresolved authority cannot become an approval", "Mutations require expected revision and idempotency key; duplicates or concurrent changes cause refusal" ], "effects": [ "Append lineage evidence; no physical split, blend or rework" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "link-quality-decision", "name": "Link quality evidence and decision", "description": "Proposed operation, not implemented. Record an existing authorized decision and supporting tests with exact scope and unresolved restrictions.", "inputs": [ "decision authority evidence", "test references", "affected portion/use", "expected revision" ], "outputs": [ "disposition assertion revision or refusal" ], "preconditions": [ "Authenticated role and purpose authorized for every included record", "Evidence and profile identified; unresolved authority cannot become an approval", "Mutations require expected revision and idempotency key; duplicates or concurrent changes cause refusal" ], "effects": [ "Record the decision without issuing release, extending expiry or overriding holds" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "trace-lot", "name": "Prepare bounded trace report", "description": "Proposed operation, not implemented. Traverse authorized lot/event references with visited-node checks, revision context and explicit missing frontiers.", "inputs": [ "start lot", "direction", "as-of time", "authorized graph scope" ], "outputs": [ "trace report with completeness limits" ], "preconditions": [ "Authenticated role and purpose authorized for every included record", "Evidence and profile identified; unresolved authority cannot become an approval", "Mutations require expected revision and idempotency key; duplicates or concurrent changes cause refusal" ], "effects": [ "Create a local assessment artifact; no recall execution or recipient notification" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "export-lot-view", "name": "Prepare authorized lot projection", "description": "Proposed operation, not implemented. Project a pinned revision with mapping and loss report; refuse omission of mandatory identity, authority or uncertainty fields.", "inputs": [ "recipient scope", "lot revision", "target profile/version" ], "outputs": [ "local projection or refusal report" ], "preconditions": [ "Authenticated role and purpose authorized for every included record", "Evidence and profile identified; unresolved authority cannot become an approval", "Mutations require expected revision and idempotency key; duplicates or concurrent changes cause refusal" ], "effects": [ "Create local output and access log; no external transmission" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "composition": [ { "target": "WM-MAT-001 Chemical Substance", "relation": "REFERENCE", "purpose": "Candidate optional material-definition binding when applicable; no substance master duplication. Profile binding and version require validation before integration.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "WM-MAT-002 Engineered Material", "relation": "REFERENCE", "purpose": "Candidate optional engineered-material definition and specification reference. Profile binding and version require validation before integration.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "WM-MAT-003 Mixture / Formulation", "relation": "REFERENCE", "purpose": "Candidate optional formulation version reference; no recipe execution. Profile binding and version require validation before integration.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "WM-MAT-005 Lab Sample / Specimen", "relation": "REFERENCE", "purpose": "Sample identity and sampling lineage remain separately mastered. Profile binding and version require validation before integration.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "WM-MAT-007 Laboratory Test / Analysis", "relation": "REFERENCE", "purpose": "Test master and method references, without operating a laboratory. Profile binding and version require validation before integration.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "WM-MAT-008 Observation / Measurement Record", "relation": "REFERENCE", "purpose": "Measurement results and environmental observations remain external masters. Profile binding and version require validation before integration.", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "target": "WM-FLW-013 Supply-chain Trace / Chain of Custody", "relation": "REFERENCE", "purpose": "Custody and shipment evidence links; no transfer execution or ownership inference. Profile binding and version require validation before integration.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "target": "Production event and quality decision masters", "relation": "REFERENCE", "purpose": "Reference actual occurrence and authorized disposition, without adopting their execution functions. Profile binding and version require validation before integration.", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "target": "EPCIS", "relation": "ALIGN", "purpose": "Conceptual event and quantity alignment; implement and test a version-pinned mapping before claiming conformance.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "SOSA/SSN and PROV-O", "relation": "ALIGN", "purpose": "Conceptual sample, observation and provenance alignment; links do not certify truth or representativeness.", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Accountable lot custodian and assigning authority with declared master namespaces", "Material/sector profile, quality authority, specification versions and identity boundary rule", "Recipient access policy, records retention schedule, unit mappings and external-master responsibilities" ], "namespace_guidance": "Keep master-qualified opaque lot IDs. Preserve literal source codes including leading zeros. Issuer plus material context disambiguates aliases; dates alone never identify a lot.", "registry_links": [ "vr.wm-mat-004", "Optional neighbor references require pinned bindings; no registry relation for this model was present in the inspected ledger" ] }, "canon_and_patch": { "canonicalization_rules": [ "Keep lot, material, sample, container, event and decision identities separate. Uniformity, safety and completeness are qualified assertions.", "Preserve original unit, quantity basis and time precision alongside normalized values. Unknown is distinct from zero, absent and not applicable." ], "patch_rules": [ "Append actor, reason, source, expected revision and idempotency key; retain correction/supersession links.", "An approved correction may follow release; never silently overwrite history or restore a void result as valid. Physical changes require separate event evidence." ], "compatibility_rules": [ "Pin profiles and mapping versions. Refuse lossy projections that remove required scope, provenance, uncertainty or access restrictions." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with namespace and revision", "Governed global identifier or IRI with issuer and version", "Dimension-assigned UUID or ULID with reconciliation status" ], "timestamp_rule": "Recording instants use RFC 3339 with seconds and explicit offset or Z. Keep event, observation, decision-effective and ingestion times separate. Preserve date-only label values and uncertain intervals without inventing midnight precision.", "serial_naming_rule": "Use opaque lot key, artifact kind and immutable sequence/revision; no sensitive actor names in filenames.", "integrity_rule": "Record digest and algorithm, original source, retrieval and transformation metadata. A digest proves neither authenticity, test validity nor release authority." }, "policies": [ "Reviewable draft under the single-provider waiver; independent external review and live source/version checks remain holds.", "API-sector Q7 examples are nonbinding and cannot impose universal material rules. Applicable sector and jurisdiction profiles need qualified review.", "Do not issue release, recall or expiry extension, move material or operate hazardous processes. Controlled-material details remain policy references only.", "Minimum necessary disclosure applies to supplier, recipient, process and personal data; no automatic public lot history." ], "crud": { "read": [ "Return authorized scoped views with revisions, as-of times and completeness limits." ], "create": [ "Require lot identity namespace, material reference, boundary rule, custodian and evidence status; unresolved values must be explicit." ], "update": [ "Append evidenced corrections or links under expected-revision control; no implicit update of linked masters." ], "delete": [ "Apply custodian-approved retention schedules and legal/quality holds to local payloads and copies. Authorized disposal may keep a minimal tombstone where lawful.", "The adopting Dimension records service executes deletion; this model only records disposition evidence. Deleting a record does not dispose of material, revoke a decision or delete referenced masters." ] }, "roles": [ { "name": "Lot custodian", "responsibilities": [ "Maintain lot identity, boundary, evidence links and reconciliation." ] }, { "name": "Quality authority", "responsibilities": [ "Review applicability and authorize scoped disposition in the external decision system." ] }, { "name": "Production or receiving recorder", "responsibilities": [ "Supply evidenced origin and quantity assertions within delegation." ] }, { "name": "Laboratory evidence reviewer", "responsibilities": [ "Assess sample and test relevance without altering laboratory masters." ] }, { "name": "Records and access officer", "responsibilities": [ "Govern retention, recipient access, exports and disposal." ] } ], "access": { "default_rule": "Deny disclosure or mutation unless purpose, role and record scope are authorized. Storage administration grants no quality decision authority.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory or urgent safety disclosure requires explicit policy basis, accountable authorization and minimized scope; record the exception." ], "audit_requirements": [ "Record actor, purpose, revision, scope and result for access, export, correction and disposal; protect and retain the log under the applicable policy." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and Dimension authority/access policies", "spec.yaml, review state and publication holds", "Pinned material profile and authorized evidence references" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one persistent material lot, with qualified quantity, genealogy and quality evidence. A separate frozen local no-tools self-audit found no critical conflict. Independent review, direct source/version verification, sector applicability and executable conformance remain holds; this is a reviewable draft.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Namespace and material-qualified identifiers with collision handling." }, { "dimension": "lifecycle", "status": "covered", "notes": "Creation, portioning, transformation, disposition and record retirement remain distinct." }, { "dimension": "relationships", "status": "covered", "notes": "Separately mastered material, sample, test, event and custody references." }, { "dimension": "temporal", "status": "covered", "notes": "Occurrence, observation, recording, effective time and date-only labels remain distinct." }, { "dimension": "provenance", "status": "covered", "notes": "Source, actor, revision and uncertain derivation links." }, { "dimension": "ownership", "status": "covered", "notes": "Title, custody, record stewardship and quality authority are separate roles." }, { "dimension": "validation", "status": "gap", "notes": "Research-schema checks do not establish executable material or sector conformance." }, { "dimension": "access", "status": "covered", "notes": "Purpose and recipient scope with exceptions and redaction." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Record schedules, holds and controlled tombstones; material disposal stays external." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual alignments only; profile pins and round-trip checks remain." }, { "dimension": "properties and observation", "status": "covered", "notes": "Quantities, quality assertions and condition observations preserve basis and uncertainty." }, { "dimension": "capabilities and hazards", "status": "covered", "notes": "Local evidence operations only; false uniformity, identity collisions and missed trace links are explicit risks." } ], "known_omissions": [ "Independent external provider review is absent; the local self-audit cannot replace it.", "Direct HTTP checks were not attempted under the owner-declared sandbox block. Current reachability, response hashes and source revision reconciliation remain unverified.", "EPCIS URL includes 2.0.1 but the retrieved PDF identifies Release 2.0, June 2022. Resolve this before any executable mapping claim.", "Nested instance schemas, exact unit conversions, inventory balance rules and executable acceptance fixtures remain to be implemented.", "Sector-specific continuous-flow allocation, recycled-material accounting, food and other regulatory profiles require additional research.", "No complete identifier encoding, laboratory accreditation, safety certification or legal compliance assessment is provided." ], "conflicts": [], "regional_assumptions": [ "Q7 is an API-sector guidance example, not a rule for all materials or jurisdictions.", "No mandatory global identifier system or universal release, expiry, sampling or retention rule is imposed." ], "adversarial_checks": [ "Reject bare lot-code identity across producers or materials.", "Reject package split as automatic new material lot or transformation.", "Reject sample/test pass as proof of lot uniformity or release.", "Reject timestamp order or incomplete genealogy as exact material allocation.", "Reject retest as automatic expiry extension and prior release as immunity from later holds." ] }, "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": "entity", "status": "accepted", "rationale": "One lot retains identity across record revisions, packaging, movements and assessments. Production events, material definitions, samples, tests, containers and decisions have separate identities. The registry standalone-mm value is a record-plane classification, and its empty legacy and relation fields supply no contrary inheritance contract." }, "decisions": [ { "concept": "Lot identity and aliases", "disposition": "accepted", "rationale": "The draft requires issuer and material context and preserves collision uncertainty. A printed label or shared lot code cannot establish identity or authorize an automatic merge." }, { "concept": "Uniformity and continuous production", "disposition": "qualified", "rationale": "Declared limits and production or receipt boundaries support an entity without assuming perfect homogeneity. Continuous intervals are representable and supplier, receipt and production lots are not automatically equivalent." }, { "concept": "Quantity reconciliation", "disposition": "accepted as an evidence requirement", "rationale": "Quantities retain units, basis, conditions, uncertainty and time. Balance and availability require completeness and overlap rules; the draft does not implement an inventory ledger or assume exact conservation across unlike bases." }, { "concept": "Packaging and new lot identity", "disposition": "separated", "rationale": "Portion/container membership is distinct from transformation. The draft asks for a profile decision when new lot identity is required and does not repeat the supplement's universal new-identifier rule for every split." }, { "concept": "Genealogy certainty and cycles", "disposition": "qualified", "rationale": "Possible contribution is preserved separately from exact allocation. Duplicate or cyclic relations trigger investigation in a revision-aware graph; they are not silently deleted or treated as proof of physical impossibility." }, { "concept": "Sampling and test interpretation", "disposition": "accepted", "rationale": "Samples, tests and observations remain external masters. Representativeness, methods, limits, contrary results and certificate authenticity are assessed explicitly. A sample link or passing result does not prove whole-lot conformity." }, { "concept": "Disposition and overlapping holds", "disposition": "separated", "rationale": "Quality disposition, availability and hold/recall claims remain separate and scoped by portion, use, market and interval. Existing authority evidence is required; prior release does not erase a later or concurrent restriction." }, { "concept": "Expiry, retest and exposure", "disposition": "qualified", "rationale": "The draft preserves date type, precision, stability basis and affected portions. A retest cannot automatically extend expiry, and record changes cannot erase storage excursions or unresolved assessment." }, { "concept": "Distribution and ownership", "disposition": "qualified", "rationale": "Trace functions expose missing frontiers, scope and as-of time. Location observations do not establish custody or title, and a locally prepared report neither proves complete recipient coverage nor performs a recall." }, { "concept": "Record correction and disposal", "disposition": "accepted", "rationale": "Evidenced corrections can follow release while retaining supersession and reasons. Retention and holds constrain disposal; local payload deletion does not destroy material or change an external master or quality decision." }, { "concept": "Source and profile assurance", "disposition": "held", "rationale": "Selected browser evidence supports the proposed distinctions but not universal material law. Direct HTTP was not attempted. The EPCIS URL/PDF revision mismatch is explicitly unresolved, and unreviewed supplement claims and unexamined standards are not admitted as evidence." }, { "concept": "Executable functions and mappings", "disposition": "deferred", "rationale": "All six functions are proposals for local evidence operations with refusal rules. Candidate object groups, optional neighbor bindings and alignments need nested schemas and acceptance fixtures before operational use; no implemented runtime is claimed." }, { "concept": "Independent review", "disposition": "waived and held", "rationale": "Claude and Grok were skipped as instructed. This separate Codex semantic self-audit adds no facts or external-provider nodes and cannot be represented as independent review or provider agreement." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped; the separate local Codex no-tools self-audit is not a second-provider review.", "Direct HTTP verification was not attempted because the owner identifies a sandbox block: zero measured HTTP 200 responses and no response hashes. Selected browser evidence is recorded separately. The EPCIS 2.0.1 URL returned a PDF labelled Release 2.0, June 2022; version reconciliation, current-source status and licensing review remain pending. The coordinator must run check_sources.py outside the sandbox.", "Sector and jurisdiction applicability, identity boundary rules, quality authority, sampling, date changes and retention need qualified profile review. API-sector Q7 guidance is not universal material law or a safety certification.", "Nested instance schemas, pinned neighbor bindings, unit and quantity accounting rules, EPCIS/SOSA/PROV mappings and adversarial acceptance fixtures are incomplete. Proposed functions do not implement a runtime, laboratory workflow, inventory ledger or release/recall engine.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Resolve source version pins and direct reachability, especially the EPCIS URL/PDF mismatch, and obtain independent external review before canonical promotion.", "Implement and test nested fields and mappings using collision, mixed-container, continuous-production, invalid-sample, concurrent-hold, partial-trace and correction-after-release fixtures.", "Review material-sector and jurisdiction profiles, continuous-flow allocation, recycled-material accounting and controlled-material policy boundaries with qualified custodians." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }