# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T14:08:23Z", "synthesisSha256": "9cdccc49878a49f51c5c4dae9df185d72b36cec777111999245caea5c231676e", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-010", "registryId": "vr.wm-act-010", "name": "Production Run", "version": "1.0.0", "previousVersions": [], "entryKind": "event", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.PRD" ], "tags": [ "production", "run", "act.prd" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-010-production-run/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-010", "model": { "registry_id": "vr.wm-act-010", "model_id": "WM-ACT-010", "name": "Production Run", "entry_kind": "event", "purpose": "Describe one bounded manufacturing execution that transforms materials into goods, with evidence-qualified inputs, outputs, resources and outcomes.", "scope_statement": "An execution occurrence with stable run identity and an explicit temporal and process boundary, represented before completion, while ongoing, or after termination. A planned reservation does not assert that execution happened. The root is the production occurrence, not the order, a recipe, a material lot, a telemetry message or the record describing it. Continuous production needs a declared window and carry-over rules. All hierarchy and functions below are proposed local research design, not executable industrial control.", "in_scope": [ "Run identity, actual execution boundary, selected definition revisions and accountable roles", "Actual resource participation, material transformation, scoped genealogy and unit-aware output accounting", "Observed progression, interruption, deviations, inspection and disposition references, record corrections and qualified reporting" ], "out_of_scope": [ "Master authoring of product specifications, recipes, bills of materials, routings, orders, schedules, equipment, organizations and material lots", "Machine commands, safety interlocks, plant optimization, inventory postings, quality release, recall execution and statutory reporting submission", "Hazardous or controlled production instructions; only policy, authority and specialist-review references are admitted", "Universal mass-balance, cost accounting, environmental accounting or manufacturing conformance engines" ], "boundary_notes": [ { "neighbor": "Legacy K8 Production and Manufacturing", "distinction": "The legacy definition/execution/performance umbrella is narrowed to Production Run. Definition masters, lot status, licensing and recall lifecycles become external references. The legacy claim of conformance and wildcard imports are not inherited.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "neighbor": "WM-ACT-002 Act; WM-ACT-003 Process / Workflow", "distinction": "Act is a candidate conceptual alignment only; a run may contain several operation occurrences. Process definitions and their execution engines stay external. No registry relationship edge for this model was found.", "source_refs": [ "SRC-006", "SRC-007" ] }, { "neighbor": "Production order and WM-ACT-008 Plan / Schedule", "distinction": "An order requests work and a schedule allocates time. Record zero or more documented associations under a profile rather than impose a universal one-to-one relationship. The ISA-95 response binding requires its order ID; this does not identify a universal run.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "OPC UA Machinery run and JobResponse", "distinction": "The machinery vocabulary defines run as completed execution or a completed subset. This model admits ongoing/aborted occurrences; map only qualified completed units to that run term and retain response, order and run IDs separately.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "neighbor": "WM-MAT-004 Material Batch / Lot; WM-FLW-008 Mass-balance / Material Flow", "distinction": "Runs reference material masters and scoped transformation assertions. One lot may span runs and one run may create several lots. Detailed material balance is delegated; genealogy is a graph, not necessarily a tree or a quantitative allocation.", "source_refs": [ "SRC-004", "SRC-008" ] }, { "neighbor": "WM-ACT-033 Review / Inspection / Audit", "distinction": "Run-specific links identify samples, results and qualified dispositions without owning inspection methods, laboratory records or release decisions. Completion does not certify quality.", "source_refs": [ "SRC-005", "SRC-007" ] }, { "neighbor": "WM-OBJ-006 Equipment / Machinery; WM-BLT-008 Site / Campus; WM-ORG-001 Organization", "distinction": "Time-bounded resource participation and location are run facts; asset lifecycle, site authority, worker qualifications and organization identity remain externally mastered.", "source_refs": [ "SRC-002", "SRC-006" ] } ] }, "sources": [ { "id": "SRC-001", "title": "OPC UA for ISA-95 - Part 4: Job Control, 6.3.4 Job Order", "organization": "OPC Foundation", "url": "https://reference.opcfoundation.org/specs/OPC-10031-4/6.3.4", "version_or_date": "2.00.0, section 6.3.4; browser header observed 2026-10-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:06:00Z", "relevance": "Requirements and proposed times belong to the order; work-master choices need not be singular." }, { "id": "SRC-002", "title": "OPC UA for ISA-95 - Part 4: Job Control, 6.3.5 Job Response", "organization": "OPC Foundation", "url": "https://reference.opcfoundation.org/specs/OPC-10031-4/6.3.5", "version_or_date": "2.00.0, section 6.3.5; browser header observed 2026-10-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:06:00Z", "relevance": "Execution reporting has its own identity, actual times, state and resource actuals; a response is not automatically a run." }, { "id": "SRC-003", "title": "OPC UA for Machinery - Part 3: Job Management", "organization": "OPC Foundation", "url": "https://reference.opcfoundation.org/specs/OPC-40001-3/full", "version_or_date": "1.0.1; sections 3.2.2, 7.1, 7.2 and 9.2", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:06:00Z", "relevance": "Completed-run meaning, output reporting and result categories provide a bounded alignment; this model also records ongoing execution." }, { "id": "SRC-004", "title": "EPCIS Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/epcis/2.0.1/", "version_or_date": "URL 2.0.1; retrieved PDF identifies Release 2.0, June 2022; patch identity needs verification", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:06:00Z", "relevance": "Section 7.4.5 TransformationEvent supplies input/output and possible-contribution semantics; event corrections and identifiers inform evidence links." }, { "id": "SRC-005", "title": "Core Business Vocabulary Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/cbv/2.0.0/", "version_or_date": "Release 2.0, June 2022; business steps and dispositions", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:06:00Z", "relevance": "Separate business steps from product dispositions; a vocabulary label does not confer release authority." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation, 30 April 2013; sections 3 and 5", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:06:00Z", "relevance": "Activity, entity, association, usage, generation and derivation distinguish execution from its descriptions and material participants." }, { "id": "SRC-007", "title": "Enabling the Digital Thread for Smart Manufacturing", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/ctl/smart-connected-systems-division/smart-connected-manufacturing-systems-group/enabling-digital", "version_or_date": "Historical project 2013-2018; page accessed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T14:06:00Z", "relevance": "Overview supports traceable exchange among engineering, manufacturing and quality; not a normative run schema." }, { "id": "SRC-008", "title": "The International System of Units, SI Brochure", "organization": "Bureau International des Poids et Mesures", "url": "https://www.bipm.org/documents/20126/41483022/SI-Brochure-9-EN.pdf/2d2b50bf-f2b4-9661-f402-5f9d66e4b507?download=true&t=1780410776583&version=7.0", "version_or_date": "9th edition, English version 4.01, updated 2026; sections 5.4.1-5.4.7", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:06:00Z", "relevance": "Quantity values, units and uncertainty inform observation and accounting records; process-specific tolerances are adopter inputs." } ], "structure": { "bundles": [ { "id": "bundle-boundary", "name": "Execution boundary", "description": "Identity and selected definition evidence.", "rationale": "Proposed run-specific grouping of evidenced assertions and external references; target master lifecycles remain outside this model.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-identity", "name": "Run identity and scope", "description": "Proposed boundary record separates the occurrence from order, response, lot and record identities. An ongoing or failed attempt is representable without inventing an output.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "findings": [ { "id": "finding-identity", "name": "Recognizable execution boundary", "description": "Proposed boundary record separates the occurrence from order, response, lot and record identities. An ongoing or failed attempt is representable without inventing an output.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "finding-identity-q01", "text": "Which master namespace and identifier distinguish this execution from its order and reports?", "kind": "identity", "answer_data": [ "run-master-id", "namespace", "order-links", "response-links" ] }, { "id": "finding-identity-q02", "text": "Which production mode and segmentation rule make this one run?", "kind": "classification", "answer_data": [ "mode", "campaign-or-window-boundary", "parent-or-child-run-links" ] }, { "id": "finding-identity-q03", "text": "What evidence establishes actual execution rather than only planned intent?", "kind": "evidence", "answer_data": [ "execution-evidence", "occurrence-status", "recognition-confidence" ] } ], "data_elements": [ { "id": "finding-identity-run-key", "name": "Run key", "description": "Authoritative execution identifier scoped to the assigning master.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "finding-identity-run-boundary", "name": "Run boundary", "description": "Mode, boundary rule, occurrence status, window or operation subset and recognized evidence; unknown boundaries block aggregation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "finding-identity-related-identities", "name": "Related identities", "description": "Typed links with master namespace, target revision and relation; order and report IDs are not aliases unless verified.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Run boundary record", "description": "Proposed evidence-bearing view for recognizable execution boundary. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-definition", "name": "Definition binding", "description": "Proposed selection history records what was applicable and what was actually used. A controlled mid-run change creates a new interval or segment; it does not rewrite earlier execution evidence.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-definition", "name": "Selected definition revisions", "description": "Proposed selection history records what was applicable and what was actually used. A controlled mid-run change creates a new interval or segment; it does not rewrite earlier execution evidence.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "finding-definition-q01", "text": "Which external product, work-master, bill and routing revisions were selected for each segment?", "kind": "relationship", "answer_data": [ "definition-links", "revisions", "selected-intervals" ] }, { "id": "finding-definition-q02", "text": "What evidence authorizes the selection or deviation from the intended definition?", "kind": "authority", "answer_data": [ "authorization-reference", "decision-role", "exception-scope" ] }, { "id": "finding-definition-q03", "text": "When did each selected revision apply and what was executed before a change?", "kind": "temporal", "answer_data": [ "effective-intervals", "operation-links", "prior-binding", "change-evidence" ] } ], "data_elements": [ { "id": "finding-definition-definition-links", "name": "Definition links", "description": "Typed external master references and immutable revisions; distinguish alternatives offered from selections used.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "finding-definition-selection-intervals", "name": "Selection intervals", "description": "Segment, valid-from/to, selection evidence and unknown or disputed intervals.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "finding-definition-definition-decision", "name": "Definition decision", "description": "External authorization, substitution or deviation decision references with scope.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-definition", "name": "Definition selection history", "description": "Proposed evidence-bearing view for selected definition revisions. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-participation", "name": "Participation and progression", "description": "Accountability, resource use and observed progression.", "rationale": "Proposed run-specific grouping of evidenced assertions and external references; target master lifecycles remain outside this model.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "layers": [ { "id": "layer-responsibility", "name": "Responsibility and resources", "description": "Proposed participation ledger distinguishes allocated requirements from actual use. It records responsible roles and resource intervals without acquiring the equipment or personnel master.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "findings": [ { "id": "finding-responsibility", "name": "Actual resource participation", "description": "Proposed participation ledger distinguishes allocated requirements from actual use. It records responsible roles and resource intervals without acquiring the equipment or personnel master.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "questions": [ { "id": "finding-responsibility-q01", "text": "Which adopting owner and accountable production role govern this run record?", "kind": "ownership", "answer_data": [ "owner-reference", "role-assignment", "delegation-scope" ] }, { "id": "finding-responsibility-q02", "text": "At which site and work centre did each execution segment occur?", "kind": "spatial", "answer_data": [ "site-reference", "work-centre-reference", "segment-interval" ] }, { "id": "finding-responsibility-q03", "text": "Which personnel roles, equipment and assets actually participated and what evidence supports their use?", "kind": "composition", "answer_data": [ "resource-references", "use-role", "interval", "usage-evidence" ] } ], "data_elements": [ { "id": "finding-responsibility-governance", "name": "Governance", "description": "Adopting owner reference, accountable role, record steward and delegated authority; role-based ownership only.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "finding-responsibility-locations", "name": "Locations", "description": "External site and work-centre identifiers with segment and effective interval.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "finding-responsibility-resource-actuals", "name": "Resource actuals", "description": "Resource master reference, role, actual interval, measured usage and evidence; minimize worker personal data.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-responsibility", "name": "Resource participation ledger", "description": "Proposed evidence-bearing view for actual resource participation. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-progress", "name": "Execution progression", "description": "Proposed event history retains the source state vocabulary, occurrence time, observation time and uncertainty. Missing end evidence remains unknown; an imported completion claim is not a quality release.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "findings": [ { "id": "finding-progress", "name": "State and timing evidence", "description": "Proposed event history retains the source state vocabulary, occurrence time, observation time and uncertainty. Missing end evidence remains unknown; an imported completion claim is not a quality release.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "finding-progress-q01", "text": "What is the latest evidenced execution state under the selected profile?", "kind": "state", "answer_data": [ "state-code", "vocabulary-version", "as-of-time", "evidence" ] }, { "id": "finding-progress-q02", "text": "Which actual start, pause, resume and end times are known, estimated or disputed?", "kind": "temporal", "answer_data": [ "event-times", "recorded-times", "clock-uncertainty", "dispute-links" ] }, { "id": "finding-progress-q03", "text": "How are retries, partial completion and an aborted attempt distinguished from a resumed run?", "kind": "lifecycle", "answer_data": [ "continuity-rule", "attempt-links", "termination-reason", "segment-history" ] } ], "data_elements": [ { "id": "finding-progress-state-assertions", "name": "State assertions", "description": "Source state code, vocabulary version, effective time, evidence, actor and confidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "finding-progress-timing-observations", "name": "Timing observations", "description": "Actual and observed timestamps, clock basis, uncertainty, event type and operation reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "finding-progress-continuity", "name": "Continuity", "description": "Profile rule and evidence for resume versus new run; cancellation before execution preserves an unexecuted record.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-progress", "name": "Execution event history", "description": "Proposed evidence-bearing view for state and timing evidence. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-transformation", "name": "Material transformation", "description": "Input consumption and output lineage.", "rationale": "Proposed run-specific grouping of evidenced assertions and external references; target master lifecycles remain outside this model.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008" ], "layers": [ { "id": "layer-inputs", "name": "Material inputs", "description": "Proposed input ledger records consumption, return, sampling and corrections distinctly. Planned bill quantities cannot substitute for observed actuals. Partial consumption does not erase the input lot.", "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ], "findings": [ { "id": "finding-inputs", "name": "Consumption assertions", "description": "Proposed input ledger records consumption, return, sampling and corrections distinctly. Planned bill quantities cannot substitute for observed actuals. Partial consumption does not erase the input lot.", "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ], "questions": [ { "id": "finding-inputs-q01", "text": "Which material identities and granularity identify the consumed inputs?", "kind": "identity", "answer_data": [ "lot-or-serial-or-class-reference", "assigning-master", "granularity" ] }, { "id": "finding-inputs-q02", "text": "What quantity was consumed or returned on which measurement basis?", "kind": "measurement", "answer_data": [ "amount", "unit", "material-basis", "method", "uncertainty", "interval" ] }, { "id": "finding-inputs-q03", "text": "Which source records and corrections substantiate each input assertion?", "kind": "provenance", "answer_data": [ "source-event-id", "origin-system", "receipt-time", "correction-chain" ] } ], "data_elements": [ { "id": "finding-inputs-input-identities", "name": "Input identities", "description": "Master material references with lot, serial or class granularity and explicit unidentified-input markers.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ] }, { "id": "finding-inputs-input-quantities", "name": "Input quantities", "description": "Quantity, unit, material basis, consume/return/sample classification, time, method and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ] }, { "id": "finding-inputs-input-evidence", "name": "Input evidence", "description": "Source event key, content digest, segment link and superseding correction; unknown is not zero.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-inputs", "name": "Input consumption ledger", "description": "Proposed evidence-bearing view for consumption assertions. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-outputs", "name": "Outputs and genealogy", "description": "Proposed output and genealogy assertions preserve incomplete evidence and distinguish possible contribution from measured allocation. Transformations, packaging aggregation and mere movement are different relations. Scrap, byproducts and work in progress are not silently lost.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-outputs", "name": "Transformation evidence graph", "description": "Proposed output and genealogy assertions preserve incomplete evidence and distinguish possible contribution from measured allocation. Transformations, packaging aggregation and mere movement are different relations. Scrap, byproducts and work in progress are not silently lost.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "finding-outputs-q01", "text": "Which output identities and output categories were actually observed for this run?", "kind": "composition", "answer_data": [ "output-references", "good-scrap-byproduct-wip-category", "occurrence-evidence" ] }, { "id": "finding-outputs-q02", "text": "What transformation evidence links inputs to outputs and how precise is the claim?", "kind": "relationship", "answer_data": [ "transformation-link", "contribution-kind", "allocation-evidence", "lineage-completeness" ] }, { "id": "finding-outputs-q03", "text": "How are split, merged, reworked or unidentified materials represented without double counting?", "kind": "exception", "answer_data": [ "segment-links", "rework-run-reference", "quantity-allocation", "unresolved-lineage" ] } ], "data_elements": [ { "id": "finding-outputs-output-assertions", "name": "Output assertions", "description": "Output master reference, quantity evidence and category; no mandatory output for ongoing or failed execution.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "finding-outputs-lineage-edges", "name": "Lineage edges", "description": "Input/output endpoints, transformation reference, possible-contribution or quantified-allocation kind, precision and evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "finding-outputs-lineage-limits", "name": "Lineage limits", "description": "Unknown endpoints, external inaccessible segments, rework linkage and completeness boundary.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-outputs", "name": "Transformation evidence graph", "description": "Proposed evidence-bearing view for transformation evidence graph. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-performance", "name": "Observations and accounting", "description": "Qualified measurements and explicit accounting bases.", "rationale": "Proposed run-specific grouping of evidenced assertions and external references; target master lifecycles remain outside this model.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-observations", "name": "Measurements and observations", "description": "Proposed observation index links run-specific measurements to their methods and conditions. The run has duration and output measures; dimensions and material properties belong to the measured subject, not to an abstract execution identifier.", "source_refs": [ "SRC-007", "SRC-008" ], "findings": [ { "id": "finding-observations", "name": "Qualified process observations", "description": "Proposed observation index links run-specific measurements to their methods and conditions. The run has duration and output measures; dimensions and material properties belong to the measured subject, not to an abstract execution identifier.", "source_refs": [ "SRC-007", "SRC-008" ], "questions": [ { "id": "finding-observations-q01", "text": "Which property of which subject was measured with what value, unit and uncertainty?", "kind": "measurement", "answer_data": [ "subject-reference", "property", "value", "unit", "uncertainty" ] }, { "id": "finding-observations-q02", "text": "Which method, instrument and conditions qualify the observation?", "kind": "quality", "answer_data": [ "method-revision", "instrument-reference", "calibration-evidence", "conditions" ] }, { "id": "finding-observations-q03", "text": "Which criteria revision and acceptance rule were applied without treating missing measurements as passing?", "kind": "validation", "answer_data": [ "criteria-reference", "evaluation-evidence", "applicability", "missing-data-state" ] } ], "data_elements": [ { "id": "finding-observations-observations", "name": "Observations", "description": "Subject, property, quantity value, unit, time, uncertainty and raw evidence reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "finding-observations-measurement-context", "name": "Measurement context", "description": "Method version, instrument identity, calibration reference, conditions and representativeness limits.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "finding-observations-evaluation-links", "name": "Evaluation links", "description": "External criteria and evaluation references; record unknown, unavailable and not-applicable separately.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-observations", "name": "Run observation index", "description": "Proposed evidence-bearing view for qualified process observations. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-accounting", "name": "Output accounting", "description": "Proposed accounting snapshot states the boundary, units, numerator and denominator for every yield. Piece yield and mass balance are not interchangeable; zero or unknown denominators prevent a numeric ratio. Missing flow or rework evidence remains an unresolved balance.", "source_refs": [ "SRC-003", "SRC-008" ], "findings": [ { "id": "finding-accounting", "name": "Qualified yield reconciliation", "description": "Proposed accounting snapshot states the boundary, units, numerator and denominator for every yield. Piece yield and mass balance are not interchangeable; zero or unknown denominators prevent a numeric ratio. Missing flow or rework evidence remains an unresolved balance.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "finding-accounting-q01", "text": "What quantities and accounting boundary define this reported yield?", "kind": "measurement", "answer_data": [ "metric-definition", "numerator", "denominator", "unit", "boundary", "interval" ] }, { "id": "finding-accounting-q02", "text": "Which conversions, tolerances and category rules make the totals comparable?", "kind": "constraint", "answer_data": [ "conversion-basis", "tolerance-profile", "category-overlap-rule", "rounding" ] }, { "id": "finding-accounting-q03", "text": "Which residuals, carry-over or repeated rework quantities prevent a reconciled result?", "kind": "exception", "answer_data": [ "residual", "wip-opening-closing", "duplicate-rework-check", "unresolved-causes" ] } ], "data_elements": [ { "id": "finding-accounting-metric-definition", "name": "Metric definition", "description": "Metric name/version, boundary, numerator, denominator, unit and rounding; no universal yield formula.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "finding-accounting-quantity-breakdown", "name": "Quantity breakdown", "description": "Qualified output categories and carry-over with disjointness or overlap declarations.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "finding-accounting-reconciliation", "name": "Reconciliation", "description": "Computed candidate result or indeterminate status, compatible-unit check, residual, tolerance and evidence snapshot.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-accounting", "name": "Output accounting snapshot", "description": "Proposed evidence-bearing view for qualified yield reconciliation. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Exceptions and quality", "description": "Deviation history and externally authorized dispositions.", "rationale": "Proposed run-specific grouping of evidenced assertions and external references; target master lifecycles remain outside this model.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-deviations", "name": "Deviations and interruptions", "description": "Proposed exception record links interruptions and deviations to affected segments and policy decisions. Local annotation cannot override a safety interlock, authorize a changed recipe or establish that physical remediation occurred.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ], "findings": [ { "id": "finding-deviations", "name": "Scoped exception history", "description": "Proposed exception record links interruptions and deviations to affected segments and policy decisions. Local annotation cannot override a safety interlock, authorize a changed recipe or establish that physical remediation occurred.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ], "questions": [ { "id": "finding-deviations-q01", "text": "Which interruption or deviation was observed and which segment or material was affected?", "kind": "event", "answer_data": [ "event-reference", "type", "affected-scope", "observation-time" ] }, { "id": "finding-deviations-q02", "text": "Which external decision governs continuation, segregation or a changed execution basis?", "kind": "decision", "answer_data": [ "decision-reference", "authority-scope", "conditions", "expiry" ] }, { "id": "finding-deviations-q03", "text": "Which unresolved safety or controlled-production restriction blocks an agent action?", "kind": "security", "answer_data": [ "policy-reference", "prohibited-action", "escalation-role", "unresolved-condition" ] } ], "data_elements": [ { "id": "finding-deviations-exception-scope", "name": "Exception scope", "description": "Type, affected run segment/material, observed interval, severity label and evidence; no hazardous procedural details.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] }, { "id": "finding-deviations-exception-decisions", "name": "Exception decisions", "description": "Authorized decision references, conditions, expiration and review status.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] }, { "id": "finding-deviations-follow-up-evidence", "name": "Follow up evidence", "description": "External corrective-action and verification references; planned and executed actions remain distinct.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-deviations", "name": "Run exception register", "description": "Proposed evidence-bearing view for scoped exception history. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-quality", "name": "Quality and disposition links", "description": "Proposed inspection index retains sample scope, criteria and disposition references separately. An observed pass or a successful production result does not by itself authorize release, sale or recall.", "source_refs": [ "SRC-005", "SRC-007" ], "findings": [ { "id": "finding-quality", "name": "Inspection and release evidence", "description": "Proposed inspection index retains sample scope, criteria and disposition references separately. An observed pass or a successful production result does not by itself authorize release, sale or recall.", "source_refs": [ "SRC-005", "SRC-007" ], "questions": [ { "id": "finding-quality-q01", "text": "Which inspection or sample evidence applies to which run outputs?", "kind": "evidence", "answer_data": [ "inspection-reference", "sample-scope", "criteria-revision", "evidence-time" ] }, { "id": "finding-quality-q02", "text": "Who is authorized to make the referenced disposition and what scope was decided?", "kind": "authority", "answer_data": [ "decision-master", "authorized-role", "affected-lots", "conditions" ] }, { "id": "finding-quality-q03", "text": "Which outputs remain pending, held or disputed despite production completion?", "kind": "state", "answer_data": [ "disposition-assertions", "as-of-time", "unresolved-results", "release-evidence" ] } ], "data_elements": [ { "id": "finding-quality-inspection-links", "name": "Inspection links", "description": "Inspection master, sample, target outputs and representativeness scope.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "finding-quality-disposition-links", "name": "Disposition links", "description": "External decision identifier and revision, authority evidence, affected materials and conditions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "finding-quality-quality-unknowns", "name": "Quality unknowns", "description": "Pending, disputed, missing or stale evidence and responsible review role.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-quality", "name": "Inspection and disposition index", "description": "Proposed evidence-bearing view for inspection and release evidence. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity-exchange", "name": "Continuity and exchange", "description": "Record provenance and controlled projections.", "rationale": "Proposed run-specific grouping of evidenced assertions and external references; target master lifecycles remain outside this model.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-continuity", "name": "Evidence and correction", "description": "Proposed correction lineage preserves attribution and distinguishes revision of a record from reversal of the physical transformation. Preserve history subject to lawful retention and access limits, with scoped tombstones after permitted payload disposal.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-continuity", "name": "Record continuity and provenance", "description": "Proposed correction lineage preserves attribution and distinguishes revision of a record from reversal of the physical transformation. Preserve history subject to lawful retention and access limits, with scoped tombstones after permitted payload disposal.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "questions": [ { "id": "finding-continuity-q01", "text": "Which source and actor made each run assertion and which record revision is being read?", "kind": "provenance", "answer_data": [ "source-reference", "actor-role", "asserted-at", "record-revision" ] }, { "id": "finding-continuity-q02", "text": "How are duplicate deliveries and conflicting corrections resolved without changing the original claim silently?", "kind": "validation", "answer_data": [ "source-event-key", "digest", "correction-link", "conflict-status" ] }, { "id": "finding-continuity-q03", "text": "Which retention, hold and disposal rules govern run evidence and residual references?", "kind": "retention", "answer_data": [ "policy-version", "retention-trigger", "hold-scope", "disposal-authority", "tombstone" ] } ], "data_elements": [ { "id": "finding-continuity-assertion-provenance", "name": "Assertion provenance", "description": "Origin master, source revision, actor role, assertion and ingestion times with integrity evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "finding-continuity-correction-lineage", "name": "Correction lineage", "description": "Prior and replacement assertion keys, reason, authority, digest and conflict resolution; duplicates are idempotent.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "finding-continuity-retention-binding", "name": "Retention binding", "description": "Adopting policy version, hold references, minimum retained identity and lawful payload-disposal authority.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-continuity", "name": "Evidence continuity record", "description": "Proposed evidence-bearing view for record continuity and provenance. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-exchange", "name": "Controlled exchange", "description": "Proposed export projection discloses only authorized run fields and reports mapping losses. Role assignment, read access and export authority are distinct. The local projection operation has no transmission side effect.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-exchange", "name": "Recipient-qualified run projection", "description": "Proposed export projection discloses only authorized run fields and reports mapping losses. Role assignment, read access and export authority are distinct. The local projection operation has no transmission side effect.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-007" ], "questions": [ { "id": "finding-exchange-q01", "text": "Which recipient purpose permits access to which run fields and artifacts?", "kind": "access", "answer_data": [ "recipient-role", "purpose", "field-scope", "authorization-reference" ] }, { "id": "finding-exchange-q02", "text": "How are worker details, confidential recipes and restricted material facts minimized?", "kind": "privacy", "answer_data": [ "redaction-rules", "disclosure-basis", "restricted-references" ] }, { "id": "finding-exchange-q03", "text": "Which pinned exchange profile preserves run, order, response and material identities and reports losses?", "kind": "interoperability", "answer_data": [ "profile-version", "identity-map", "state-map", "loss-report", "conformance-status" ] } ], "data_elements": [ { "id": "finding-exchange-disclosure-scope", "name": "Disclosure scope", "description": "Recipient role, purpose, permitted fields, expiry and authority reference.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "finding-exchange-projection-controls", "name": "Projection controls", "description": "Redaction and aggregation rules, protected artifact handling and existence-disclosure restrictions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "finding-exchange-mapping-profile", "name": "Mapping profile", "description": "Pinned mapping version, identifier semantics, vocabulary mappings, conversion evidence and rejected or lossy fields.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-exchange", "name": "Controlled run projection", "description": "Proposed evidence-bearing view for recipient-qualified run projection. References authoritative records and identifies its revision and disclosure scope.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; adopting Dimension UUID/ULID third. Keep run identity, evidence identity and revision distinct; date and filename are not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-register", "name": "Register execution boundary", "description": "Proposed, unimplemented local operation. Create a local run record without asserting that execution started.", "inputs": [ "master identity", "boundary proposal", "occurrence evidence or planned-only marker" ], "outputs": [ "local record key or identity-conflict refusal" ], "preconditions": [ "Adopting owner policy authorizes this local operation for the actor, purpose and scope.", "Expected record revision matches; required references, evidence and input units resolve or produce an explicit refusal.", "Applicable safety, confidentiality and retention restrictions are checked; no implied external actuation authority." ], "effects": [ "Duplicate keys are reconciled; unknown execution remains unconfirmed." ], "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "function-bind-definition", "name": "Bind selected definition evidence", "description": "Proposed, unimplemented local operation. Record the selected external revision for a segment without changing the definition master.", "inputs": [ "run revision", "definition references", "effective segment", "decision evidence" ], "outputs": [ "selection revision or unresolved-binding refusal" ], "preconditions": [ "Adopting owner policy authorizes this local operation for the actor, purpose and scope.", "Expected record revision matches; required references, evidence and input units resolve or produce an explicit refusal.", "Applicable safety, confidentiality and retention restrictions are checked; no implied external actuation authority." ], "effects": [ "Retain prior selection and authority evidence; do not issue a machine or recipe command." ], "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "function-record-actuals", "name": "Record actual execution assertions", "description": "Proposed, unimplemented local operation. Append local resource, state and material assertions with source attribution.", "inputs": [ "run revision", "source assertion key", "actuals and units", "occurrence and ingestion times" ], "outputs": [ "accepted assertion keys or ambiguity report" ], "preconditions": [ "Adopting owner policy authorizes this local operation for the actor, purpose and scope.", "Expected record revision matches; required references, evidence and input units resolve or produce an explicit refusal.", "Applicable safety, confidentiality and retention restrictions are checked; no implied external actuation authority." ], "effects": [ "Deduplicate exact replays, preserve conflicting claims and segregate invalid units; no inventory posting or physical act." ], "source_refs": [ "SRC-002", "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "function-trace", "name": "Build scoped genealogy view", "description": "Proposed, unimplemented local operation. Traverse recorded transformation links under recipient access limits.", "inputs": [ "run or material references", "direction and depth", "evidence snapshot", "recipient purpose" ], "outputs": [ "local trace view and completeness limits" ], "preconditions": [ "Adopting owner policy authorizes this local operation for the actor, purpose and scope.", "Expected record revision matches; required references, evidence and input units resolve or produce an explicit refusal.", "Applicable safety, confidentiality and retention restrictions are checked; no implied external actuation authority." ], "effects": [ "Mark possible contribution separately from measured allocation; rework and inaccessible links remain visible as limits without leaking protected identities." ], "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "function-reconcile", "name": "Assess candidate output accounting", "description": "Proposed, unimplemented local operation. Compute a local candidate summary only under a supplied metric and compatible-unit basis.", "inputs": [ "qualified quantity snapshot", "metric definition", "conversion evidence", "tolerance profile" ], "outputs": [ "candidate totals and residuals or indeterminate result" ], "preconditions": [ "Adopting owner policy authorizes this local operation for the actor, purpose and scope.", "Expected record revision matches; required references, evidence and input units resolve or produce an explicit refusal.", "Applicable safety, confidentiality and retention restrictions are checked; no implied external actuation authority." ], "effects": [ "Reject unknown or zero denominators, incompatible units and unresolved double counting; no certification or stock adjustment." ], "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "function-project", "name": "Prepare controlled run report", "description": "Proposed, unimplemented local operation. Prepare a local evidence-linked report using a pinned recipient and exchange profile.", "inputs": [ "run revision", "recipient authority", "mapping profile", "redaction policy" ], "outputs": [ "local report with losses and holds or refusal" ], "preconditions": [ "Adopting owner policy authorizes this local operation for the actor, purpose and scope.", "Expected record revision matches; required references, evidence and input units resolve or produce an explicit refusal.", "Applicable safety, confidentiality and retention restrictions are checked; no implied external actuation authority." ], "effects": [ "Log projection provenance; no external transmission, legal submission, quality release or canonicality claim." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ] } ], "composition": [ { "target": "WM-ACT-002", "relation": "ALIGN", "purpose": "Candidate act alignment only; multi-operation execution is not asserted to be atomic.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "WM-ACT-003", "relation": "REFERENCE", "purpose": "Candidate reference to process definition and routing context; engine and process lifecycle external.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "WM-ACT-009", "relation": "REFERENCE", "purpose": "Candidate reference to governed work instructions and method revisions.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "WM-ACT-008", "relation": "REFERENCE", "purpose": "Candidate schedule context; planned time does not establish actual execution.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-MAT-004", "relation": "REFERENCE", "purpose": "Candidate material lot master binding; consumption and output links do not own lot release or recall.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "WM-OBJ-006", "relation": "REFERENCE", "purpose": "Candidate equipment identity and qualification reference; no machine control.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-BLT-008", "relation": "REFERENCE", "purpose": "Candidate plant and work-centre location binding.", "required": false, "source_refs": [ "SRC-002", "SRC-006" ] }, { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Candidate producer identity and responsibility reference; no corporate master ownership.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "WM-ACT-033", "relation": "REFERENCE", "purpose": "Candidate inspection evidence reference; results and disposition authority stay external.", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "target": "WM-FLW-008", "relation": "REFERENCE", "purpose": "Candidate detailed material balance reference; local yield is a qualified projection only.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "OPC UA ISA-95 Job Control 2.00.0", "relation": "ALIGN", "purpose": "Map order and response fields through a tested profile; do not equate run and response IDs.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "OPC UA Machinery Job Management 1.0.1", "relation": "ALIGN", "purpose": "Qualify completed units for its narrower run definition; ongoing occurrence mapping needs an extension.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "GS1 EPCIS 2.0 and CBV 2.0", "relation": "ALIGN", "purpose": "Map eligible transformation evidence and controlled terms without asserting conformance or exact lineage allocation.", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] }, { "target": "W3C PROV-O", "relation": "ALIGN", "purpose": "Map the occurrence to Activity and records/materials to distinct Entities with qualified responsibility.", "required": false, "source_refs": [ "SRC-006" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Name an adopting owner by role and reference, with a record steward and accountable production authority.", "Declare run boundary, identity namespace, resource and material masters, selected profile versions and unknown-data rules.", "Provide access, retention, safety, quality-decision and external-side-effect policies; this model grants no plant-control authority." ], "namespace_guidance": "Use the adopting Dimension namespace for local IDs; preserve external master namespaces. Stable IDs omit dates and record revisions are separate.", "registry_links": [ "vr.wm-act-010", "WM-MAT-004 candidate material master", "WM-ACT-033 candidate inspection reference" ] }, "canon_and_patch": { "canonicalization_rules": [ "Keep occurrence identity separate from record revision, order, response, operation and lot identities.", "Preserve source units and vocabularies; qualified normalized values need conversion evidence and originals.", "Null, unknown, zero, not observed and not applicable have different meanings; do not default missing quantities or quality evidence to success." ], "patch_rules": [ "Use expected-revision checks and idempotent source keys; append attributable corrections with reasons and supersession links.", "Changes of definition binding or boundary require impact review and versioned intervals, not replacement of historical actuals." ], "compatibility_rules": [ "Changing boundary, quantity basis, mapping semantics or required authority is a breaking profile change.", "Pin external model bindings and exchange profiles before operational use; no conformance follows from structural validation." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier within the assigning namespace", "Governed global identifier or IRI with verified binding", "UUID or ULID allocated by the adopting Dimension" ], "timestamp_rule": "Use RFC 3339 with seconds and an explicit offset or Z. Distinguish event time, effective interval, observation time and ingestion time; preserve precision, clock basis and uncertainty. Unknown actual times are not replaced by planned times.", "serial_naming_rule": "Use stable run key, artifact kind and separate revision/sequence for labels. Timestamps aid ordering but are not identifiers.", "integrity_rule": "Retain source keys, provenance, content digests and correction links according to retention policy. A digest detects byte changes but does not prove production truth, source authority or product conformity." }, "policies": [ "All operation definitions are proposed local record functions; machine actuation, quality release, recall and external submission require separately authorized systems and qualified profiles.", "Protect worker privacy, recipe confidentiality and restricted material information; publish only authorized projections.", "Safety and controlled-production constraints remain policy-level references. Never generate hazardous production instructions or infer permission from an order reference.", "Do not treat successful execution, a passing observation, a complete graph or a numeric yield as universal compliance certification." ], "crud": { "read": [ "Read an authorized evidence snapshot with source revisions, uncertainty, holds and recipient scope; protect restricted existence metadata." ], "create": [ "Resolve master identity and explicit occurrence status first; record source authority and boundary. A planned-only record never claims a physical run occurred." ], "update": [ "Append correction or selection-history revisions under concurrency control; preserve attributable conflicts and invalidate derived summaries when their evidence changes." ], "delete": [ "Adopting Dimension retention and disposition policy owns deletion execution. Enforce applicable holds; dispose permitted payloads and replicas under scoped authority and retain only lawful minimal tombstones.", "Deleting a run record cannot reverse physical production, erase a target lot master or rescind a quality decision. Avoid perpetual retention of worker personal data." ] }, "roles": [ { "name": "Adopting owner", "responsibilities": [ "Set namespace, policy, delegation and disclosure scope." ] }, { "name": "Production record steward", "responsibilities": [ "Resolve run identity, evidence attribution, corrections and profile selection." ] }, { "name": "Execution reporter", "responsibilities": [ "Record authorized actuals and uncertainty without inferring release or changing masters." ] }, { "name": "Quality decision authority", "responsibilities": [ "Own external inspection/disposition decisions and their scoped evidence." ] }, { "name": "Safety authority", "responsibilities": [ "Own applicable safety restrictions and escalation rules outside local record functions." ] }, { "name": "Authorized reviewer", "responsibilities": [ "Inspect evidence, mapping losses and residual conflicts under recipient scope." ] } ], "access": { "default_rule": "Deny by default; grant role, purpose and field-scoped access under the adopting owner policy. Read access does not authorize export or physical action.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Time-limited emergency access needs independent policy authority and audit evidence; it does not bypass safety interlocks or grant quality release." ], "audit_requirements": [ "Record actor role, purpose, policy revision, time, affected evidence revision and local read/write/export outcome. Reference the authoritative audit system rather than duplicating its lifecycle." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Nearest adopting owner and Dimension policy", "AGENTS.md", "spec.yaml including holds and boundaries", "Pinned external masters, evidence and exchange profiles" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one bounded manufacturing execution, with explicit distinctions among occurrence, order, response, definition and material identity. Separate frozen local no-tools self-audit completed. Reviewable draft only; independent review, source/version checks, adopting profiles and executable conformance remain holds.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Master-scoped occurrence key and separate order, response, lot and record identities." }, { "dimension": "lifecycle", "status": "covered", "notes": "Observed execution, interruption, continuity, termination and planned-only status are qualified." }, { "dimension": "relationships", "status": "covered", "notes": "Candidate references retain external definition, material, resource and inspection masters." }, { "dimension": "temporal", "status": "covered", "notes": "Effective, event, observation and ingestion time remain separate with uncertainty." }, { "dimension": "provenance", "status": "covered", "notes": "Source keys, attribution, corrections and integrity limits are explicit." }, { "dimension": "ownership", "status": "covered", "notes": "Adopting owner and delegated production, stewardship and quality roles are distinct." }, { "dimension": "validation", "status": "gap", "notes": "Research structure validates; executable instance rules and mappings still require tests." }, { "dimension": "access", "status": "covered", "notes": "Recipient purpose, field scopes, restricted existence metadata and local export rules." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Policy-driven holds, lawful payload disposal and minimal tombstones." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual OPC UA, EPCIS/CBV and PROV mappings only, with narrower run semantics disclosed." }, { "dimension": "direct properties", "status": "covered", "notes": "Duration, state, scoped quantities and output metrics belong to the run; physical properties attach to measured subjects." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Occurrence evidence is separate from planned order and observations have method, uncertainty and conditions." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Six proposed local functions with preconditions, refusals and explicit limits; no industrial control." }, { "dimension": "context and evidence", "status": "covered", "notes": "Profile, authority, master references, source limits and omissions are retained." }, { "dimension": "sector coverage", "status": "gap", "notes": "Discrete, batch and windowed continuous cases need adoption fixtures and specialist policy review." } ], "known_omissions": [ "Independent external review absent; local Codex audit is not a second provider.", "Direct HTTP and byte-level source/version verification unattempted under owner-reported sandbox block; coordinator checker required.", "Executable nested instance schemas, mapping code, vocabulary/state conformance and adversarial fixtures not implemented.", "Continuous process segmentation, sector-specific quality, safety, metrology, privacy and retention profiles need specialist adoption review.", "No full ISA-95/IEC 62264 or ISO quality certification claimed; evidence is limited to the accessible cited sections." ], "conflicts": [], "regional_assumptions": [ "International information-model examples do not supply a universal legal regime. Adopters must establish applicable sector, safety, environmental, privacy and records rules.", "No brand or company is assigned as model owner; ownership is role-based in the adopting Dimension." ], "adversarial_checks": [ "Challenge order/run/response conflation and the narrower completed-run vocabulary.", "Challenge mandatory output, exact one-recipe claims, input-output tree assumptions and exact allocation from possible contribution.", "Challenge incompatible units, unknown denominators, co-products, window carry-over and double-counted rework.", "Challenge physical command authority inferred from record operations, production completion equated with quality release, and confidential lineage disclosure.", "Challenge record immutability interpreted as perpetual personal-data retention; separate correction, erasure and physical reversal." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "event", "status": "accepted", "rationale": "The root denotes an execution occurrence over a bounded interval, while its descriptive record can exist before or after that occurrence. Planned-only records do not assert execution. A production order, report, recipe or lot is a different subject. The registry standalone-mm value is a catalogue classification rather than the semantic kind." }, "decisions": [ { "concept": "Occurrence and descriptive record", "disposition": "accepted with qualification", "rationale": "The scope, identity evidence and create/register rules distinguish actual production from recorded intent. The record can survive the event without changing the event boundary." }, { "concept": "Completed-run standard terminology", "disposition": "qualified alignment", "rationale": "The machinery source uses a narrower completed-run meaning. The admitted result explicitly limits that mapping and records ongoing or aborted occurrences as a broader local concept; no standard conformance is claimed." }, { "concept": "Legacy umbrella and supplement", "disposition": "narrowed and reconciled", "rationale": "Definition authoring, lot lifecycle, licensing, recall and statistical submission remain external. The supplement supplies leads only; mandatory output, a universal single recipe and a universal yield formula are not admitted." }, { "concept": "Run, order and response identity", "disposition": "separated", "rationale": "Run keys, order associations and report keys remain distinct. Binding-specific mandatory identifiers are not promoted to universal one-to-one run cardinality." }, { "concept": "Definition selection and change", "disposition": "accepted", "rationale": "Offered work-master alternatives differ from selections used. Versioned segments and decision evidence preserve changes without rewriting earlier execution or acquiring definition-master authority." }, { "concept": "External resource and material masters", "disposition": "reference only", "rationale": "Candidate composition links have no mandatory runtime status. Local time-bounded participation and actuals do not own equipment, lot, site, organization, method, process or inspection lifecycles." }, { "concept": "Progression, retries and incomplete output", "disposition": "accepted", "rationale": "Source state vocabularies and timing uncertainty are retained. A profile determines whether a restart continues the occurrence or starts another; missing or failed output is representable." }, { "concept": "Transformation genealogy", "disposition": "qualified", "rationale": "Possible contribution is not quantitative allocation. Partial consumption, unknown endpoints and rework are retained; transformation, aggregation and movement are distinct." }, { "concept": "Measurements and output accounting", "disposition": "accepted as candidate design", "rationale": "Measured subject, units, method, conditions and uncertainty are explicit. Accounting has a boundary and metric definition, rejects invalid denominators and retains unresolved carry-over or double counting." }, { "concept": "Quality outcome and industrial authority", "disposition": "separated", "rationale": "Completion and a passing observation do not confer release authority. Deviation and disposition evidence stays external, and hazardous restrictions are policy-level references." }, { "concept": "Local function effects", "disposition": "accepted as proposed only", "rationale": "All six functions are unimplemented local record operations with authority, concurrency and evidence preconditions. They neither actuate equipment nor post stock, release products or send reports." }, { "concept": "Correction, retention and physical reversal", "disposition": "separated", "rationale": "Attributable record supersession does not reverse physical production. Lawful payload disposal and scoped holds coexist with minimal continuity evidence; perpetual personal-data retention is not required." }, { "concept": "Restricted trace and export", "disposition": "accepted with policy dependency", "rationale": "Recipient purpose, field scopes and existence-disclosure restrictions are explicit. Local report preparation is distinct from external transmission and from read authority." }, { "concept": "Evidence independence and source verification", "disposition": "limited and held", "rationale": "Eight source records from five organizations support selected distinctions. Several belong to the same standards families. Browser access does not establish direct HTTP success, current versions or applicability, and the EPCIS version-label mismatch is unresolved." }, { "concept": "Executable schemas and independent review", "disposition": "deferred", "rationale": "Candidate data groups and conceptual mappings do not implement conformance. This local self-audit cannot replace an independent provider; no waived-provider content or agreement is admitted." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts. The separate local Codex no-tools self-audit is not a second-provider review.", "Live source and version verification remains incomplete. Selected browser evidence was reviewed, but direct HTTP checks were not attempted under the owner-reported sandbox restriction: zero measured HTTP 200 responses, no local response hashes. The EPCIS 2.0.1 URL versus Release 2.0 PDF label and all current-version/licensing pins need coordinator verification using check_sources.py.", "Adopting manufacturing profiles require specialist review of continuous-process segmentation, recipe and order cardinalities, quality decisions, safety, controlled-production restrictions, metrology, environmental obligations, worker privacy and retention. No operational authority or universal legal/compliance certification is granted.", "Nested instance schemas, pinned neighbor bindings, OPC UA/EPCIS/CBV/PROV mappings, unit conversions and adversarial instance fixtures remain unimplemented. The broader ongoing-run concept is not automatically conformant with the narrower completed-run vocabulary; executable conformance is a separate gate.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Complete direct source retrieval, response hashing, version-label reconciliation, licensing and current-applicability review without treating HTTP success as substantive verification.", "Develop executable profiles and fixtures for planned-only records, abort without output, multi-definition segments, continuous carry-over, partial input consumption, rework, restricted lineage and disputed release evidence.", "Restore independent external review and qualified adoption testing before any canonical or publishable-draft promotion." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }