# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-05T22:00:07Z", "synthesisSha256": "f64ab815d473b0675e593a87a68f3dc1b125f2862c250a35525d739dd082f81d", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-007", "registryId": "vr.wm-act-007", "name": "Work Order", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.WO" ], "tags": [ "work", "order", "act.wo" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-007-work-order/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-007", "model": { "registry_id": "vr.wm-act-007", "model_id": "WM-ACT-007", "name": "Work Order", "entry_kind": "aggregate", "purpose": "Represent an authoritative, versioned instruction that authorizes and constrains one or more units of work while preserving boundaries to requests, procedures, schedules and performed-work evidence.", "scope_statement": "Owns order identity, authorization, scope, requirements, administrative lifecycle, change control, acceptance criteria and closure disposition; references execution and domain records governed elsewhere.", "in_scope": [ "Order identity, class, authority, scope, requirements, constraints and order-level planning commitments", "Administrative state transitions, revisions, cancellation, acceptance decision, closure and governance metadata", "Typed references to tasks, procedures, targets, resources, contracts, schedules and performed-work evidence" ], "out_of_scope": [ "Task execution semantics, detailed scheduling, inventory transactions, cost accounting, access enforcement and proof that physical work occurred", "Lifecycle ownership of referenced assets, people, organizations, locations, contracts, procedures or evidence records" ], "boundary_notes": [ { "neighbor": "Work request", "distinction": "A request proposes or demands work and can be rejected; a work order is an authorized instruction with controlled scope and lifecycle.", "source_refs": [ "SRC-004", "SRC-005" ] }, { "neighbor": "Task or procedure", "distinction": "The order may contain task references and pin procedure versions, but task execution semantics and reusable instructions remain in their own models.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "neighbor": "Work performance or work record", "distinction": "A work order authorizes work; performed-work records and evidence establish what actually happened and are only referenced here.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "Schedule", "distinction": "The order may carry windows and commitments, but resource-level sequencing and calendar optimization belong to a schedule model.", "source_refs": [ "SRC-001", "SRC-003" ] } ] }, "sources": [ { "id": "SRC-001", "title": "ANSI/ISA-95.00.05-2018 preview: Business-to-Manufacturing Transactions", "organization": "International Society of Automation", "url": "https://www.isa.org/getmedia/bbc0eb3e-d047-440d-88fc-642b14bd8d40/ISA-95-00-05-2018-preview.pdf", "version_or_date": "2018 preview", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:00:00Z", "relevance": "Defines transaction and information-model boundaries around work schedules, work performance and work records." }, { "id": "SRC-002", "title": "ISA-95 Standard overview", "organization": "International Society of Automation", "url": "https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard", "version_or_date": "current page accessed 2026-09-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:00:00Z", "relevance": "Establishes the enterprise-control integration scope in which work-order information is exchanged." }, { "id": "SRC-003", "title": "OPC UA for ISA-95, Part 4: Job Control", "organization": "OPC Foundation", "url": "https://reference.opcfoundation.org/specs/OPC-10031-4/4.1", "version_or_date": "OPC 10031-4, section 4.1", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:00:00Z", "relevance": "Defines job-order control concepts, parameters, resource requirements and state-oriented interfaces aligned with ISA-95." }, { "id": "SRC-004", "title": "PLCS WorkOrder template", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/contexts/OASIS/templates/WorkOrder/template.html", "version_or_date": "PLCSlib 1.0 CS01", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:00:00Z", "relevance": "Models a work order as authority to undertake work with classification, issue date and unique identity." }, { "id": "SRC-005", "title": "PLCS concept model definitions", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/concept_model/model_definitions.html", "version_or_date": "PLCSlib 1.0 CS01", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:00:00Z", "relevance": "Separates a work request from the authority and commitment represented by a work order." }, { "id": "SRC-006", "title": "PLCS Aviation Maintenance DEX information model", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/plcs/dexlib/R1/dexlib/data/dex/aviation_maintenance/sys/plcs_info_model.htm", "version_or_date": "DEXlib R1", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-06T00:00:00Z", "relevance": "Shows the maintenance-domain binding between authorization, reportable items, task references and resulting records." }, { "id": "SRC-007", "title": "PLCS Referencing Task template", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/plcs/dexlib/cs01/data/templates/referencing_task/sys/section.htm", "version_or_date": "DEXlib CS01", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-06T00:00:00Z", "relevance": "Provides the versioned external-task-reference boundary used instead of copying procedure semantics into an order." }, { "id": "SRC-008", "title": "UN/EDIFACT Job Order message (JOBOFF)", "organization": "United Nations Economic Commission for Europe", "url": "https://unece.org/fileadmin/DAM/trade/untdid/d97b/trmd/joboff_c.htm", "version_or_date": "UN/EDIFACT D.97B", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:00:00Z", "relevance": "Supplies a cross-organizational job-order message precedent for identity, parties, dates, references and line-level instructions." } ], "structure": { "bundles": [ { "id": "authority-and-origin", "name": "Authority and origin", "description": "Establishes what the order is, why it exists and who is empowered to issue it.", "rationale": "An executable work instruction must be distinguishable from a request and traceable to an authorized issuer.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008" ], "layers": [ { "id": "order-identity", "name": "Order identity", "description": "Stable identity and classification of the governed order.", "source_refs": [ "SRC-004", "SRC-008" ], "findings": [ { "id": "authoritative-identity", "name": "Authoritative identity", "description": "The master-system identifier, aliases and revision-qualified identity of the work order.", "source_refs": [ "SRC-004", "SRC-008" ], "questions": [ { "id": "authoritative-identity-q01", "text": "What is the governed value of authoritative identity for this work order?", "kind": "identity", "answer_data": [ "Authoritative identity", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "authoritative-identity-q02", "text": "Who or what authoritative source establishes authoritative identity for this work order?", "kind": "spatial", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "authoritative-identity-q03", "text": "How is authoritative identity validated, changed and historically preserved?", "kind": "measurement", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "authoritative-identity-data", "name": "Authoritative identity record", "description": "Structured answer data for authoritative identity, including authority, effective time and provenance where applicable.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "authoritative-identity-artifact", "name": "Authoritative identity evidence", "description": "Versioned evidence or authoritative reference supporting the recorded authoritative identity.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "classification-and-kind", "name": "Classification and kind", "description": "The governed order class, profile and criteria that distinguish this order from neighboring instruction types.", "source_refs": [ "SRC-004", "SRC-005" ], "questions": [ { "id": "classification-and-kind-q01", "text": "What is the governed value of classification and kind for this work order?", "kind": "classification", "answer_data": [ "Classification and kind", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "classification-and-kind-q02", "text": "Who or what authoritative source establishes classification and kind for this work order?", "kind": "authority", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "classification-and-kind-q03", "text": "How is classification and kind validated, changed and historically preserved?", "kind": "retention", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "classification-and-kind-data", "name": "Classification and kind record", "description": "Structured answer data for classification and kind, including authority, effective time and provenance where applicable.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "classification-and-kind-artifact", "name": "Classification and kind evidence", "description": "Versioned evidence or authoritative reference supporting the recorded classification and kind.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "request-and-rationale", "name": "Request and rationale", "description": "The initiating demand and reason for converting it into authorized work.", "source_refs": [ "SRC-005", "SRC-008" ], "findings": [ { "id": "originating-request", "name": "Originating request", "description": "Reference to the demand, request or triggering condition from which the order was derived.", "source_refs": [ "SRC-005", "SRC-008" ], "questions": [ { "id": "originating-request-q01", "text": "What is the governed value of originating request for this work order?", "kind": "relationship", "answer_data": [ "Originating request", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "originating-request-q02", "text": "Who or what authoritative source establishes originating request for this work order?", "kind": "process", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "originating-request-q03", "text": "How is originating request validated, changed and historically preserved?", "kind": "definition", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "originating-request-data", "name": "Originating request record", "description": "Structured answer data for originating request, including authority, effective time and provenance where applicable.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "originating-request-artifact", "name": "Originating request evidence", "description": "Versioned evidence or authoritative reference supporting the recorded originating request.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "business-or-operational-rationale", "name": "Business or operational rationale", "description": "The stated need, risk, obligation or desired benefit that justifies ordering the work.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "business-or-operational-rationale-q01", "text": "What is the governed value of business or operational rationale for this work order?", "kind": "decision", "answer_data": [ "Business or operational rationale", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "business-or-operational-rationale-q02", "text": "Who or what authoritative source establishes business or operational rationale for this work order?", "kind": "evidence", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "business-or-operational-rationale-q03", "text": "How is business or operational rationale validated, changed and historically preserved?", "kind": "state", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "business-or-operational-rationale-data", "name": "Business or operational rationale record", "description": "Structured answer data for business or operational rationale, including authority, effective time and provenance where applicable.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "business-or-operational-rationale-artifact", "name": "Business or operational rationale evidence", "description": "Versioned evidence or authoritative reference supporting the recorded business or operational rationale.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "authorization", "name": "Authorization", "description": "The issuer's authority, effective scope and limitations.", "source_refs": [ "SRC-004", "SRC-006" ], "findings": [ { "id": "issuing-authority", "name": "Issuing authority", "description": "The person, organization or delegated role that issued the authoritative revision and the basis of that authority.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "issuing-authority-q01", "text": "What is the governed value of issuing authority for this work order?", "kind": "authority", "answer_data": [ "Issuing authority", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "issuing-authority-q02", "text": "Who or what authoritative source establishes issuing authority for this work order?", "kind": "security", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "issuing-authority-q03", "text": "How is issuing authority validated, changed and historically preserved?", "kind": "ownership", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "issuing-authority-data", "name": "Issuing authority record", "description": "Structured answer data for issuing authority, including authority, effective time and provenance where applicable.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "issuing-authority-artifact", "name": "Issuing authority evidence", "description": "Versioned evidence or authoritative reference supporting the recorded issuing authority.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "authorization-scope", "name": "Authorization scope", "description": "The work, targets, resources, period and limits covered by the issued authority.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "authorization-scope-q01", "text": "What is the governed value of authorization scope for this work order?", "kind": "constraint", "answer_data": [ "Authorization scope", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "authorization-scope-q02", "text": "Who or what authoritative source establishes authorization scope for this work order?", "kind": "exception", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "authorization-scope-q03", "text": "How is authorization scope validated, changed and historically preserved?", "kind": "event", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "authorization-scope-data", "name": "Authorization scope record", "description": "Structured answer data for authorization scope, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "authorization-scope-artifact", "name": "Authorization scope evidence", "description": "Versioned evidence or authoritative reference supporting the recorded authorization scope.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "ordered-work-definition", "name": "Ordered work definition", "description": "Defines the authorized scope, intended outcome, task composition and target context.", "rationale": "The order owns the instruction envelope while task, procedure, asset and location semantics stay in referenced models.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ], "layers": [ { "id": "scope-and-outcome", "name": "Scope and outcome", "description": "Authorized inclusions, exclusions and expected result.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "authorized-scope", "name": "Authorized scope", "description": "The explicit work boundary, including included and excluded activities and affected subjects.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "authorized-scope-q01", "text": "What is the governed value of authorized scope for this work order?", "kind": "composition", "answer_data": [ "Authorized scope", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "authorized-scope-q02", "text": "Who or what authoritative source establishes authorized scope for this work order?", "kind": "definition", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "authorized-scope-q03", "text": "How is authorized scope validated, changed and historically preserved?", "kind": "security", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "authorized-scope-data", "name": "Authorized scope record", "description": "Structured answer data for authorized scope, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "authorized-scope-artifact", "name": "Authorized scope evidence", "description": "Versioned evidence or authoritative reference supporting the recorded authorized scope.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "required-outcome", "name": "Required outcome", "description": "The deliverable, condition or service level that the authorized work is expected to produce.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "required-outcome-q01", "text": "What is the governed value of required outcome for this work order?", "kind": "requirement", "answer_data": [ "Required outcome", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "required-outcome-q02", "text": "Who or what authoritative source establishes required outcome for this work order?", "kind": "composition", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "required-outcome-q03", "text": "How is required outcome validated, changed and historically preserved?", "kind": "decision", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "required-outcome-data", "name": "Required outcome record", "description": "Structured answer data for required outcome, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "required-outcome-artifact", "name": "Required outcome evidence", "description": "Versioned evidence or authoritative reference supporting the recorded required outcome.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "task-composition", "name": "Task composition", "description": "Contained task references and immutable work-master bindings.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "contained-task-references", "name": "Contained task references", "description": "Ordered references to tasks with order-local parameters and dependency bindings, without importing task execution state.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "contained-task-references-q01", "text": "What is the governed value of contained task references for this work order?", "kind": "composition", "answer_data": [ "Contained task references", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "contained-task-references-q02", "text": "Who or what authoritative source establishes contained task references for this work order?", "kind": "lifecycle", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "contained-task-references-q03", "text": "How is contained task references validated, changed and historically preserved?", "kind": "relationship", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "contained-task-references-data", "name": "Contained task references record", "description": "Structured answer data for contained task references, including authority, effective time and provenance where applicable.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "contained-task-references-artifact", "name": "Contained task references evidence", "description": "Versioned evidence or authoritative reference supporting the recorded contained task references.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "procedure-or-work-master-reference", "name": "Procedure or work-master reference", "description": "A pinned reference to the approved procedure, recipe or work-master version governing execution.", "source_refs": [ "SRC-003", "SRC-007" ], "questions": [ { "id": "procedure-or-work-master-reference-q01", "text": "What is the governed value of procedure or work-master reference for this work order?", "kind": "interoperability", "answer_data": [ "Procedure or work-master reference", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "procedure-or-work-master-reference-q02", "text": "Who or what authoritative source establishes procedure or work-master reference for this work order?", "kind": "provenance", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "procedure-or-work-master-reference-q03", "text": "How is procedure or work-master reference validated, changed and historically preserved?", "kind": "ownership", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "procedure-or-work-master-reference-data", "name": "Procedure or work-master reference record", "description": "Structured answer data for procedure or work-master reference, including authority, effective time and provenance where applicable.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "procedure-or-work-master-reference-artifact", "name": "Procedure or work-master reference evidence", "description": "Versioned evidence or authoritative reference supporting the recorded procedure or work-master reference.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "target-context", "name": "Target context", "description": "The affected subject and the operational place in which the instruction applies.", "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ], "findings": [ { "id": "subject-or-target-reference", "name": "Subject or target reference", "description": "Reference to the asset, product, case, service or other object whose state or condition is to be changed.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "subject-or-target-reference-q01", "text": "What is the governed value of subject or target reference for this work order?", "kind": "relationship", "answer_data": [ "Subject or target reference", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "subject-or-target-reference-q02", "text": "Who or what authoritative source establishes subject or target reference for this work order?", "kind": "requirement", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "subject-or-target-reference-q03", "text": "How is subject or target reference validated, changed and historically preserved?", "kind": "process", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "subject-or-target-reference-data", "name": "Subject or target reference record", "description": "Structured answer data for subject or target reference, including authority, effective time and provenance where applicable.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "subject-or-target-reference-artifact", "name": "Subject or target reference evidence", "description": "Versioned evidence or authoritative reference supporting the recorded subject or target reference.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "location-and-operational-context", "name": "Location and operational context", "description": "Applicable site, functional location, hierarchy boundary and operating conditions relevant to execution.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "location-and-operational-context-q01", "text": "What is the governed value of location and operational context for this work order?", "kind": "spatial", "answer_data": [ "Location and operational context", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "location-and-operational-context-q02", "text": "Who or what authoritative source establishes location and operational context for this work order?", "kind": "event", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "location-and-operational-context-q03", "text": "How is location and operational context validated, changed and historically preserved?", "kind": "validation", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "location-and-operational-context-data", "name": "Location and operational context record", "description": "Structured answer data for location and operational context, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "location-and-operational-context-artifact", "name": "Location and operational context evidence", "description": "Versioned evidence or authoritative reference supporting the recorded location and operational context.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "planning-and-constraints", "name": "Planning and constraints", "description": "Captures order-level priority, timing, dependencies and mandatory controls.", "rationale": "These commitments constrain planning and release but do not replace a detailed schedule or an external permit-enforcement system.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "layers": [ { "id": "priority-and-time", "name": "Priority and time", "description": "Priority, criticality and authorized planning window.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "priority-and-criticality", "name": "Priority and criticality", "description": "The ranked urgency, consequence class and authority responsible for prioritization or escalation.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "priority-and-criticality-q01", "text": "What is the governed value of priority and criticality for this work order?", "kind": "classification", "answer_data": [ "Priority and criticality", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "priority-and-criticality-q02", "text": "Who or what authoritative source establishes priority and criticality for this work order?", "kind": "quality", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "priority-and-criticality-q03", "text": "How is priority and criticality validated, changed and historically preserved?", "kind": "interoperability", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "priority-and-criticality-data", "name": "Priority and criticality record", "description": "Structured answer data for priority and criticality, including authority, effective time and provenance where applicable.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "priority-and-criticality-artifact", "name": "Priority and criticality evidence", "description": "Versioned evidence or authoritative reference supporting the recorded priority and criticality.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "planned-window-and-deadline", "name": "Planned window and deadline", "description": "Earliest and latest start, due time, commitment window and the timezone basis for those values.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "planned-window-and-deadline-q01", "text": "What is the governed value of planned window and deadline for this work order?", "kind": "temporal", "answer_data": [ "Planned window and deadline", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "planned-window-and-deadline-q02", "text": "Who or what authoritative source establishes planned window and deadline for this work order?", "kind": "retention", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "planned-window-and-deadline-q03", "text": "How is planned window and deadline validated, changed and historically preserved?", "kind": "composition", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "planned-window-and-deadline-data", "name": "Planned window and deadline record", "description": "Structured answer data for planned window and deadline, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "planned-window-and-deadline-artifact", "name": "Planned window and deadline evidence", "description": "Versioned evidence or authoritative reference supporting the recorded planned window and deadline.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "dependencies-and-holds", "name": "Dependencies and holds", "description": "Predecessors, release conditions, permits and quality or safety gates.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "predecessors-and-blockers", "name": "Predecessors and blockers", "description": "Referenced orders, tasks, events or conditions that must be satisfied before release or continuation.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "predecessors-and-blockers-q01", "text": "What is the governed value of predecessors and blockers for this work order?", "kind": "relationship", "answer_data": [ "Predecessors and blockers", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "predecessors-and-blockers-q02", "text": "Who or what authoritative source establishes predecessors and blockers for this work order?", "kind": "interoperability", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "predecessors-and-blockers-q03", "text": "How is predecessors and blockers validated, changed and historically preserved?", "kind": "spatial", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "predecessors-and-blockers-data", "name": "Predecessors and blockers record", "description": "Structured answer data for predecessors and blockers, including authority, effective time and provenance where applicable.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "predecessors-and-blockers-artifact", "name": "Predecessors and blockers evidence", "description": "Versioned evidence or authoritative reference supporting the recorded predecessors and blockers.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "permit-safety-quality-constraints", "name": "Permit, safety and quality constraints", "description": "Applicable permits, isolations, safety controls, inspection points and quality gates bound to the order.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "permit-safety-quality-constraints-q01", "text": "What is the governed value of permit, safety and quality constraints for this work order?", "kind": "security", "answer_data": [ "Permit, safety and quality constraints", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "permit-safety-quality-constraints-q02", "text": "Who or what authoritative source establishes permit, safety and quality constraints for this work order?", "kind": "identity", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "permit-safety-quality-constraints-q03", "text": "How is permit, safety and quality constraints validated, changed and historically preserved?", "kind": "constraint", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "permit-safety-quality-constraints-data", "name": "Permit, safety and quality constraints record", "description": "Structured answer data for permit, safety and quality constraints, including authority, effective time and provenance where applicable.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "permit-safety-quality-constraints-artifact", "name": "Permit, safety and quality constraints evidence", "description": "Versioned evidence or authoritative reference supporting the recorded permit, safety and quality constraints.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "resource-requirements", "name": "Resource requirements", "description": "Defines responsibility and the capabilities, equipment, materials and commercial bounds required by the order.", "rationale": "The order records requirements and bindings while referenced people, inventory, equipment, contracts and cost ledgers remain authoritative for their own data.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-008" ], "layers": [ { "id": "responsibility", "name": "Responsibility", "description": "Accountability, assignment and acknowledgement.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "responsible-party", "name": "Responsible party", "description": "The accountable organizational unit, role or party for delivery and order administration.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "responsible-party-q01", "text": "What is the governed value of responsible party for this work order?", "kind": "ownership", "answer_data": [ "Responsible party", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "responsible-party-q02", "text": "Who or what authoritative source establishes responsible party for this work order?", "kind": "relationship", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "responsible-party-q03", "text": "How is responsible party validated, changed and historically preserved?", "kind": "quality", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "responsible-party-data", "name": "Responsible party record", "description": "Structured answer data for responsible party, including authority, effective time and provenance where applicable.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "responsible-party-artifact", "name": "Responsible party evidence", "description": "Versioned evidence or authoritative reference supporting the recorded responsible party.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "assignment-and-acknowledgement", "name": "Assignment and acknowledgement", "description": "Assignee references and their time-stamped acceptance, refusal or reassignment response.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "assignment-and-acknowledgement-q01", "text": "What is the governed value of assignment and acknowledgement for this work order?", "kind": "event", "answer_data": [ "Assignment and acknowledgement", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "assignment-and-acknowledgement-q02", "text": "Who or what authoritative source establishes assignment and acknowledgement for this work order?", "kind": "temporal", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "assignment-and-acknowledgement-q03", "text": "How is assignment and acknowledgement validated, changed and historically preserved?", "kind": "exception", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "assignment-and-acknowledgement-data", "name": "Assignment and acknowledgement record", "description": "Structured answer data for assignment and acknowledgement, including authority, effective time and provenance where applicable.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "assignment-and-acknowledgement-artifact", "name": "Assignment and acknowledgement evidence", "description": "Versioned evidence or authoritative reference supporting the recorded assignment and acknowledgement.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "required-resources", "name": "Required resources", "description": "Capabilities and consumable or reusable resources needed for execution.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "personnel-capability-requirements", "name": "Personnel capability requirements", "description": "Required roles, competencies, certifications, quantities and availability constraints without duplicating worker records.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "personnel-capability-requirements-q01", "text": "What is the governed value of personnel capability requirements for this work order?", "kind": "requirement", "answer_data": [ "Personnel capability requirements", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "personnel-capability-requirements-q02", "text": "Who or what authoritative source establishes personnel capability requirements for this work order?", "kind": "ownership", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "personnel-capability-requirements-q03", "text": "How is personnel capability requirements validated, changed and historically preserved?", "kind": "classification", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "personnel-capability-requirements-data", "name": "Personnel capability requirements record", "description": "Structured answer data for personnel capability requirements, including authority, effective time and provenance where applicable.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "personnel-capability-requirements-artifact", "name": "Personnel capability requirements evidence", "description": "Versioned evidence or authoritative reference supporting the recorded personnel capability requirements.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "equipment-material-asset-requirements", "name": "Equipment, material and asset requirements", "description": "Required equipment classes, tools, materials, quantities, units and reservation references.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "equipment-material-asset-requirements-q01", "text": "What is the governed value of equipment, material and asset requirements for this work order?", "kind": "measurement", "answer_data": [ "Equipment, material and asset requirements", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "equipment-material-asset-requirements-q02", "text": "Who or what authoritative source establishes equipment, material and asset requirements for this work order?", "kind": "constraint", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "equipment-material-asset-requirements-q03", "text": "How is equipment, material and asset requirements validated, changed and historically preserved?", "kind": "temporal", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "equipment-material-asset-requirements-data", "name": "Equipment, material and asset requirements record", "description": "Structured answer data for equipment, material and asset requirements, including authority, effective time and provenance where applicable.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "equipment-material-asset-requirements-artifact", "name": "Equipment, material and asset requirements evidence", "description": "Versioned evidence or authoritative reference supporting the recorded equipment, material and asset requirements.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "commercial-bounds", "name": "Commercial bounds", "description": "Estimated effort, authorized cost bounds and governing agreements.", "source_refs": [ "SRC-001", "SRC-008" ], "findings": [ { "id": "estimated-effort-and-cost-bound", "name": "Estimated effort and cost bound", "description": "Order-level estimates, ceilings, currencies, approval thresholds and uncertainty, not a replacement for cost transactions.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "estimated-effort-and-cost-bound-q01", "text": "What is the governed value of estimated effort and cost bound for this work order?", "kind": "measurement", "answer_data": [ "Estimated effort and cost bound", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "estimated-effort-and-cost-bound-q02", "text": "Who or what authoritative source establishes estimated effort and cost bound for this work order?", "kind": "evidence", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "estimated-effort-and-cost-bound-q03", "text": "How is estimated effort and cost bound validated, changed and historically preserved?", "kind": "requirement", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "estimated-effort-and-cost-bound-data", "name": "Estimated effort and cost bound record", "description": "Structured answer data for estimated effort and cost bound, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "estimated-effort-and-cost-bound-artifact", "name": "Estimated effort and cost bound evidence", "description": "Versioned evidence or authoritative reference supporting the recorded estimated effort and cost bound.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "service-contract-reference", "name": "Service contract reference", "description": "Pinned reference to the agreement, entitlement, warranty or service level governing the ordered work.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "service-contract-reference-q01", "text": "What is the governed value of service contract reference for this work order?", "kind": "relationship", "answer_data": [ "Service contract reference", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "service-contract-reference-q02", "text": "Who or what authoritative source establishes service contract reference for this work order?", "kind": "validation", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "service-contract-reference-q03", "text": "How is service contract reference validated, changed and historically preserved?", "kind": "evidence", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "service-contract-reference-data", "name": "Service contract reference record", "description": "Structured answer data for service contract reference, including authority, effective time and provenance where applicable.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "service-contract-reference-artifact", "name": "Service contract reference evidence", "description": "Versioned evidence or authoritative reference supporting the recorded service contract reference.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-and-change-control", "name": "Lifecycle and change control", "description": "Governs administrative state, release, revisions, suspension, cancellation and exceptions.", "rationale": "Issued meaning and authority must be historically reconstructable, and order state must not be confused with evidence that work occurred.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ], "layers": [ { "id": "order-state", "name": "Order state", "description": "Administrative lifecycle state and dispatch interface.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "lifecycle-state", "name": "Lifecycle state", "description": "The current administrative state, allowed transition, responsible actor and effective transition event.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "lifecycle-state-q01", "text": "What is the governed value of lifecycle state for this work order?", "kind": "state", "answer_data": [ "Lifecycle state", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "lifecycle-state-q02", "text": "Who or what authoritative source establishes lifecycle state for this work order?", "kind": "access", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "lifecycle-state-q03", "text": "How is lifecycle state validated, changed and historically preserved?", "kind": "exception", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "lifecycle-state-data", "name": "Lifecycle state record", "description": "Structured answer data for lifecycle state, including authority, effective time and provenance where applicable.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "lifecycle-state-artifact", "name": "Lifecycle state evidence", "description": "Versioned evidence or authoritative reference supporting the recorded lifecycle state.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "release-and-dispatch", "name": "Release and dispatch", "description": "The controlled release to an execution context, dispatch destination and acknowledgement reference.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "release-and-dispatch-q01", "text": "What is the governed value of release and dispatch for this work order?", "kind": "process", "answer_data": [ "Release and dispatch", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "release-and-dispatch-q02", "text": "Who or what authoritative source establishes release and dispatch for this work order?", "kind": "decision", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "release-and-dispatch-q03", "text": "How is release and dispatch validated, changed and historically preserved?", "kind": "identity", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "release-and-dispatch-data", "name": "Release and dispatch record", "description": "Structured answer data for release and dispatch, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "release-and-dispatch-artifact", "name": "Release and dispatch evidence", "description": "Versioned evidence or authoritative reference supporting the recorded release and dispatch.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "change-control", "name": "Change control", "description": "Immutable revisions and controlled termination or temporary inhibition.", "source_refs": [ "SRC-003", "SRC-004" ], "findings": [ { "id": "revision-and-supersession", "name": "Revision and supersession", "description": "Revision identity, changed scope, reason, approver and explicit predecessor or successor relation.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "revision-and-supersession-q01", "text": "What is the governed value of revision and supersession for this work order?", "kind": "lifecycle", "answer_data": [ "Revision and supersession", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "revision-and-supersession-q02", "text": "Who or what authoritative source establishes revision and supersession for this work order?", "kind": "classification", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "revision-and-supersession-q03", "text": "How is revision and supersession validated, changed and historically preserved?", "kind": "temporal", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "revision-and-supersession-data", "name": "Revision and supersession record", "description": "Structured answer data for revision and supersession, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "revision-and-supersession-artifact", "name": "Revision and supersession evidence", "description": "Versioned evidence or authoritative reference supporting the recorded revision and supersession.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "suspension-cancellation-and-expiry", "name": "Suspension, cancellation and expiry", "description": "Authority, reason, time and residual obligations when authorization is paused, withdrawn or expires.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "suspension-cancellation-and-expiry-q01", "text": "What is the governed value of suspension, cancellation and expiry for this work order?", "kind": "lifecycle", "answer_data": [ "Suspension, cancellation and expiry", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "suspension-cancellation-and-expiry-q02", "text": "Who or what authoritative source establishes suspension, cancellation and expiry for this work order?", "kind": "state", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "suspension-cancellation-and-expiry-q03", "text": "How is suspension, cancellation and expiry validated, changed and historically preserved?", "kind": "authority", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "suspension-cancellation-and-expiry-data", "name": "Suspension, cancellation and expiry record", "description": "Structured answer data for suspension, cancellation and expiry, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "suspension-cancellation-and-expiry-artifact", "name": "Suspension, cancellation and expiry evidence", "description": "Versioned evidence or authoritative reference supporting the recorded suspension, cancellation and expiry.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "exception-management", "name": "Exception management", "description": "Deviation, escalation and conflicting-order handling.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "deviation-and-escalation", "name": "Deviation and escalation", "description": "Requested or approved deviations, unresolved blockers, escalation paths and disposition deadlines.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "deviation-and-escalation-q01", "text": "What is the governed value of deviation and escalation for this work order?", "kind": "exception", "answer_data": [ "Deviation and escalation", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "deviation-and-escalation-q02", "text": "Who or what authoritative source establishes deviation and escalation for this work order?", "kind": "spatial", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "deviation-and-escalation-q03", "text": "How is deviation and escalation validated, changed and historically preserved?", "kind": "measurement", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "deviation-and-escalation-data", "name": "Deviation and escalation record", "description": "Structured answer data for deviation and escalation, including authority, effective time and provenance where applicable.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "deviation-and-escalation-artifact", "name": "Deviation and escalation evidence", "description": "Versioned evidence or authoritative reference supporting the recorded deviation and escalation.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "conflict-and-duplicate-resolution", "name": "Conflict and duplicate resolution", "description": "Relations to duplicate or contradictory orders and the authoritative resolution decision.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "conflict-and-duplicate-resolution-q01", "text": "What is the governed value of conflict and duplicate resolution for this work order?", "kind": "decision", "answer_data": [ "Conflict and duplicate resolution", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "conflict-and-duplicate-resolution-q02", "text": "Who or what authoritative source establishes conflict and duplicate resolution for this work order?", "kind": "authority", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "conflict-and-duplicate-resolution-q03", "text": "How is conflict and duplicate resolution validated, changed and historically preserved?", "kind": "retention", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "conflict-and-duplicate-resolution-data", "name": "Conflict and duplicate resolution record", "description": "Structured answer data for conflict and duplicate resolution, including authority, effective time and provenance where applicable.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "conflict-and-duplicate-resolution-artifact", "name": "Conflict and duplicate resolution evidence", "description": "Versioned evidence or authoritative reference supporting the recorded conflict and duplicate resolution.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "acceptance-closure-and-governance", "name": "Acceptance, closure and governance", "description": "Connects completion evidence to acceptance and closure while preserving provenance, ownership, access and retention controls.", "rationale": "Completion is an external claim until evaluated against declared criteria; the order retains its decision and references instead of absorbing performed-work evidence.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-008" ], "layers": [ { "id": "completion-interface", "name": "Completion interface", "description": "References to performed work and the criteria for acceptance.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "completion-claim-reference", "name": "Completion claim reference", "description": "Reference to a work-performance, work-record or completion claim and the issuer and time of that claim.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "completion-claim-reference-q01", "text": "What is the governed value of completion claim reference for this work order?", "kind": "evidence", "answer_data": [ "Completion claim reference", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "completion-claim-reference-q02", "text": "Who or what authoritative source establishes completion claim reference for this work order?", "kind": "process", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "completion-claim-reference-q03", "text": "How is completion claim reference validated, changed and historically preserved?", "kind": "definition", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "completion-claim-reference-data", "name": "Completion claim reference record", "description": "Structured answer data for completion claim reference, including authority, effective time and provenance where applicable.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "completion-claim-reference-artifact", "name": "Completion claim reference evidence", "description": "Versioned evidence or authoritative reference supporting the recorded completion claim reference.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "acceptance-criteria", "name": "Acceptance criteria", "description": "Measurable conditions, tolerances, evidence requirements and verifier authority used to evaluate completion.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "acceptance-criteria-q01", "text": "What is the governed value of acceptance criteria for this work order?", "kind": "validation", "answer_data": [ "Acceptance criteria", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "acceptance-criteria-q02", "text": "Who or what authoritative source establishes acceptance criteria for this work order?", "kind": "evidence", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "acceptance-criteria-q03", "text": "How is acceptance criteria validated, changed and historically preserved?", "kind": "state", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "acceptance-criteria-data", "name": "Acceptance criteria record", "description": "Structured answer data for acceptance criteria, including authority, effective time and provenance where applicable.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "acceptance-criteria-artifact", "name": "Acceptance criteria evidence", "description": "Versioned evidence or authoritative reference supporting the recorded acceptance criteria.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "closure-and-disposition", "name": "Closure and disposition", "description": "Acceptance decision, rejection, rework and final retention disposition.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "acceptance-or-rejection", "name": "Acceptance or rejection", "description": "The authorized evaluation decision, defects, exceptions and referenced corrective or rework order.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "acceptance-or-rejection-q01", "text": "What is the governed value of acceptance or rejection for this work order?", "kind": "decision", "answer_data": [ "Acceptance or rejection", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "acceptance-or-rejection-q02", "text": "Who or what authoritative source establishes acceptance or rejection for this work order?", "kind": "security", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "acceptance-or-rejection-q03", "text": "How is acceptance or rejection validated, changed and historically preserved?", "kind": "ownership", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "acceptance-or-rejection-data", "name": "Acceptance or rejection record", "description": "Structured answer data for acceptance or rejection, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "acceptance-or-rejection-artifact", "name": "Acceptance or rejection evidence", "description": "Versioned evidence or authoritative reference supporting the recorded acceptance or rejection.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "closure-and-retention", "name": "Closure and retention", "description": "Closure reason, unresolved obligations, retention class, legal hold and tombstone or erasure authority.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "closure-and-retention-q01", "text": "What is the governed value of closure and retention for this work order?", "kind": "retention", "answer_data": [ "Closure and retention", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "closure-and-retention-q02", "text": "Who or what authoritative source establishes closure and retention for this work order?", "kind": "exception", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "closure-and-retention-q03", "text": "How is closure and retention validated, changed and historically preserved?", "kind": "event", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "closure-and-retention-data", "name": "Closure and retention record", "description": "Structured answer data for closure and retention, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "closure-and-retention-artifact", "name": "Closure and retention evidence", "description": "Versioned evidence or authoritative reference supporting the recorded closure and retention.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "evidence-and-access", "name": "Evidence and access", "description": "Provenance, quality, ownership, disclosure and scoped access.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "findings": [ { "id": "provenance-and-quality", "name": "Provenance and quality", "description": "Source lineage, capture method, freshness, confidence and validation results for order facts and attached evidence.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "provenance-and-quality-q01", "text": "What is the governed value of provenance and quality for this work order?", "kind": "provenance", "answer_data": [ "Provenance and quality", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "provenance-and-quality-q02", "text": "Who or what authoritative source establishes provenance and quality for this work order?", "kind": "definition", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "provenance-and-quality-q03", "text": "How is provenance and quality validated, changed and historically preserved?", "kind": "security", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "provenance-and-quality-data", "name": "Provenance and quality record", "description": "Structured answer data for provenance and quality, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "provenance-and-quality-artifact", "name": "Provenance and quality evidence", "description": "Versioned evidence or authoritative reference supporting the recorded provenance and quality.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "ownership-disclosure-and-access", "name": "Ownership, disclosure and access", "description": "Record owner, stewardship, delegated writers, disclosure policy, access scopes and approved exceptions.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "ownership-disclosure-and-access-q01", "text": "What is the governed value of ownership, disclosure and access for this work order?", "kind": "access", "answer_data": [ "Ownership, disclosure and access", "applicable qualifier or explicit unknown", "source and effective version" ] }, { "id": "ownership-disclosure-and-access-q02", "text": "Who or what authoritative source establishes ownership, disclosure and access for this work order?", "kind": "composition", "answer_data": [ "authority or source reference", "effective timestamp", "provenance and confidence" ] }, { "id": "ownership-disclosure-and-access-q03", "text": "How is ownership, disclosure and access validated, changed and historically preserved?", "kind": "decision", "answer_data": [ "validation rule", "authorized change event", "prior-value or supersession reference" ] } ], "data_elements": [ { "id": "ownership-disclosure-and-access-data", "name": "Ownership, disclosure and access record", "description": "Structured answer data for ownership, disclosure and access, including authority, effective time and provenance where applicable.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "ownership-disclosure-and-access-artifact", "name": "Ownership, disclosure and access evidence", "description": "Versioned evidence or authoritative reference supporting the recorded ownership, disclosure and access.", "media_or_form": [ "structured record", "signed or controlled document", "resolvable external reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "create-draft-order", "name": "Create draft order", "description": "Establish a proposed order identity, origin and scope without granting authority.", "inputs": [ "request reference", "proposed scope", "draft owner" ], "outputs": [ "draft work order" ], "preconditions": [ "request or authorized drafting purpose exists" ], "effects": [ "a traceable but non-authorized order draft exists" ], "source_refs": [ "SRC-004", "SRC-005" ] }, { "id": "validate-order-boundary", "name": "Validate order boundary", "description": "Check required order facts, external references and separation from request, procedure and execution records.", "inputs": [ "work order revision", "validation profile" ], "outputs": [ "validation report" ], "preconditions": [ "order revision is resolvable" ], "effects": [ "boundary, reference and semantic failures are recorded" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "authorize-order", "name": "Authorize order", "description": "Issue an immutable revision under a verified authority and effective scope.", "inputs": [ "validated draft", "issuer authority", "effective time" ], "outputs": [ "authorized order revision" ], "preconditions": [ "validation passed", "issuer authority is current" ], "effects": [ "authorization event and immutable issued meaning are recorded" ], "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "release-order", "name": "Release order", "description": "Expose an authorized revision to its declared dispatch or execution context.", "inputs": [ "authorized order", "dispatch destination" ], "outputs": [ "release event", "dispatch reference" ], "preconditions": [ "order is authorized", "release constraints are satisfied" ], "effects": [ "order becomes available to the declared execution context" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "revise-order", "name": "Revise order", "description": "Create a traceable successor without overwriting an issued revision.", "inputs": [ "current revision", "change request", "approver" ], "outputs": [ "successor revision", "change record" ], "preconditions": [ "change authority is valid" ], "effects": [ "old and new meaning remain reconstructable" ], "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "suspend-or-resume-order", "name": "Suspend or resume order", "description": "Temporarily inhibit or restore administrative availability under named authority and reason.", "inputs": [ "order", "transition request", "authority" ], "outputs": [ "state-transition event" ], "preconditions": [ "transition is allowed", "authority is valid" ], "effects": [ "administrative availability changes without erasing history" ], "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "cancel-order", "name": "Cancel order", "description": "Withdraw remaining authorization while preserving evidence and residual obligations.", "inputs": [ "order", "cancellation reason", "authority" ], "outputs": [ "cancellation event", "residual-obligation record" ], "preconditions": [ "cancellation policy permits the transition" ], "effects": [ "future authorization ends and historical references remain resolvable" ], "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "record-completion-claim", "name": "Record completion claim", "description": "Bind external performed-work evidence without silently asserting acceptance.", "inputs": [ "work order", "performed-work reference", "claiming party" ], "outputs": [ "completion-claim binding" ], "preconditions": [ "external evidence is resolvable" ], "effects": [ "completion claim becomes reviewable separately from order state" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "accept-or-reject-result", "name": "Accept or reject result", "description": "Evaluate referenced evidence against the issued acceptance criteria and record the authorized decision.", "inputs": [ "order", "completion claim", "acceptance evidence" ], "outputs": [ "acceptance decision" ], "preconditions": [ "criteria and verifier authority are explicit" ], "effects": [ "accepted, rejected or conditional disposition is recorded" ], "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "close-order", "name": "Close order", "description": "Finalize disposition, unresolved exceptions and retention metadata after an authorized decision.", "inputs": [ "order", "acceptance decision", "retention class" ], "outputs": [ "closure event", "retention disposition" ], "preconditions": [ "closure prerequisites are satisfied" ], "effects": [ "order is closed but its identity, history and references remain governed" ], "source_refs": [ "SRC-001", "SRC-008" ] } ], "composition": [ { "target": "WM-ACT-006 Task", "relation": "COMPOSE", "purpose": "Groups typed task references and order-local parameters without claiming ownership of task execution semantics.", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "target": "Procedure or work-master model", "relation": "REFERENCE", "purpose": "Pins the executable instruction version while keeping reusable procedure content outside the order.", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "target": "Schedule or calendar model", "relation": "REFERENCE", "purpose": "Delegates detailed sequencing and capacity allocation while retaining order-level timing commitments.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "Asset, location, person, organization, material and inventory models", "relation": "REFERENCE", "purpose": "Uses authoritative domain identities without copying their properties or lifecycles.", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] }, { "target": "Contract, entitlement and cost models", "relation": "REFERENCE", "purpose": "Binds governing agreements and commercial limits without turning the order into a ledger.", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "target": "Performed-work and evidence models", "relation": "REFERENCE", "purpose": "Separates authorization from claims and proof of actual execution.", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "target": "ISA-95, OPC UA ISA-95, PLCS and UN/EDIFACT concepts", "relation": "ALIGN", "purpose": "Maintains documented semantic mappings without claiming conformance to any one implementation profile.", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, accountable stewards and authority delegation chain.", "Declare the Dimension namespace, identity master systems and authoritative work-order repository.", "Publish registries for models, objects, events and relation types plus applicable retention and access policies.", "Pin this model version and any jurisdictional or industry profile used for validation." ], "namespace_guidance": "Mint identifiers only inside the adopting Dimension's governed namespace; preserve upstream master-system identifiers and aliases without silently re-keying them.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local model, object and event registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, stable node IDs and explicit value units; never infer execution from administrative order state.", "Issued revisions are immutable and superseded by linked successors rather than overwritten." ], "patch_rules": [ "Additive extensions use a Dimension-owned namespace and declare their target bundle, layer, finding or artifact plus source and rationale.", "Breaking changes require a new model version, migration mapping, compatibility declaration and preserved access to prior versions." ], "compatibility_rules": [ "Consumers ignore unknown additive fields only when required semantics and access controls remain intact.", "Mappings to external job or work-order schemas must declare lossy fields, code-list versions and timezone handling." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system work-order identifier and immutable issued-revision identifier.", "Governed globally resolvable IRI or federation identifier.", "Adopting-Dimension UUID or ULID when no authoritative external identifier exists." ], "timestamp_rule": "Record event timestamps in RFC 3339 with seconds and an explicit UTC offset or Z; keep event, effective, observation and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {order-id}--{artifact-kind}--{revision-or-event-id}; never use a date alone as identity.", "integrity_rule": "Store a cryptographic digest, media type, byte length, issuer, provenance and immutable version reference for every retained serial artifact." }, "policies": [ "The adopting Dimension defines who may draft, authorize, release, revise, cancel, accept and close each order class.", "Facts, hypotheses and unknown values remain explicitly distinct and carry source, observation time and confidence where applicable.", "Safety, privacy, commercial confidentiality, export control and legal-hold policies are evaluated before disclosure or mutation.", "External references are resolved by pinned identity and version, with stale, missing or lossy bindings reported rather than guessed." ], "crud": { "read": [ "Resolve the model version, owner policy and referenced master systems; apply field- and artifact-level access rules and record material reads where policy requires." ], "create": [ "Create a draft only under an authorized purpose, allocate identity by priority, validate required boundary facts and keep it non-executable until an authorization event." ], "update": [ "Create an immutable successor revision for issued meaning, record actor, authority, reason and effective time, and validate references and transitions before and after the change." ], "delete": [ "Apply retention, legal-hold and deletion policy; tombstone issued orders or use approved cryptographic erasure while preserving minimum identity and non-cascading reference integrity." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, retention, access and delegation policy for work-order records." ] }, { "name": "Order issuer", "responsibilities": [ "Authorize scope and effective revision within documented authority." ] }, { "name": "Order steward", "responsibilities": [ "Maintain classification, references, lifecycle integrity and conflict resolution." ] }, { "name": "Assignee or executing party", "responsibilities": [ "Acknowledge assignment and publish execution claims to the proper performed-work model." ] }, { "name": "Verifier or acceptor", "responsibilities": [ "Evaluate evidence against acceptance criteria and record an authorized disposition." ] }, { "name": "Auditor", "responsibilities": [ "Review provenance, authorization, access, changes, retention and unresolved exceptions without editing operational truth." ] } ], "access": { "default_rule": "Deny mutation and restricted disclosure unless the active Dimension, role and order-class policy grants the action; expose only the minimum authorized projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency access must be time-limited, purpose-bound, attributable, independently reviewed and must not bypass legal hold or immutable history." ], "audit_requirements": [ "Log actor, role, purpose, order and revision identity, action, decision, policy version, timestamp with offset, affected scope and result for every privileged mutation or disclosure." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the nearest Dimension-owner AGENTS.md and policies.", "Read this model AGENTS.md, then the pinned spec.yaml and all referenced model contracts before mutation." ] } }, "coverage": { "claim": "A source-grounded reviewable draft of the authoritative Work Order envelope across maintenance, manufacturing and inter-organizational exchange, without a claim of universal profile completeness or independent external review.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Authoritative identity, aliases, revision identity and namespace priority are explicit." }, { "dimension": "lifecycle", "status": "covered", "notes": "Administrative states, transitions, revision, suspension, cancellation and closure are modeled." }, { "dimension": "relationships", "status": "covered", "notes": "Typed composition and references keep neighboring model ownership explicit." }, { "dimension": "temporal", "status": "covered", "notes": "Planning, effective and event time semantics use explicit timezone rules." }, { "dimension": "provenance", "status": "covered", "notes": "Source lineage, confidence, capture and artifact integrity are represented." }, { "dimension": "ownership", "status": "covered", "notes": "Dimension, record stewardship, issuer and responsible-party roles are separated." }, { "dimension": "validation", "status": "covered", "notes": "Boundary, transition, reference, acceptance and before-and-after checks are defined." }, { "dimension": "access", "status": "covered", "notes": "Default deny, granular scopes, emergency exception and audit requirements are defined." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retention, legal hold, tombstone and approved erasure rules preserve reference integrity." }, { "dimension": "interoperability", "status": "covered", "notes": "ISA-95, OPC UA, PLCS and UN/EDIFACT alignments and lossy mapping requirements are stated." }, { "dimension": "authority", "status": "covered", "notes": "Issuer authority, authorization scope, delegation and lifecycle action authority are explicit." }, { "dimension": "requirements and constraints", "status": "covered", "notes": "Outcome, resources, timing, permits, safety, quality and commercial bounds are represented." }, { "dimension": "evidence and acceptance", "status": "covered", "notes": "Completion claims remain external and are evaluated through explicit criteria and decisions." } ], "known_omissions": [ "Industry and jurisdiction profiles must supply exact state code lists, mandatory signatures, permit semantics, retention periods and cancellation effects.", "Exact sibling catalogue IDs for schedules, procedures, performed work, contracts, resources and access/audit bindings remain to be pinned as those models mature.", "The candidate relation to WM-ACT-006 is represented as COMPOSE rather than lifecycle ownership and needs later cross-model harmonization." ], "conflicts": [ "Standards use both work-order and job-order terminology and vary in state names; this model preserves a neutral administrative lifecycle plus explicit external mappings." ], "regional_assumptions": [ "No universal legal retention period, signature method, worker-qualification rule, safety permit regime or tax treatment is assumed." ], "adversarial_checks": [ "Reject any inference that a released, dispatched or closed order proves that the ordered work occurred.", "Reject copied asset, person, organization, inventory, contract or evidence lifecycles when a governed reference is sufficient.", "Reject cancellation, deletion, access expansion or acceptance decisions that lack explicit authority and preserved provenance.", "Reject timestamps without seconds and explicit offset, date-only artifact identity and destructive overwrites of issued revisions.", "Reject universal state vocabularies or retention periods presented without an industry or jurisdiction profile." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "The record-plane label standalone-mm does not determine the subject kind. Work Order is defensibly an aggregate because one authoritative root governs authorization, scope, requirements, state, revisions, acceptance criteria and closure while composing or referencing subordinate records." }, "decisions": [ { "concept": "Request versus order boundary", "disposition": "accepted", "rationale": "The model consistently treats a request as an input that can be rejected and the order as an authorized instruction, matching the cited PLCS distinction and preventing demand records from becoming executable by implication." }, { "concept": "Authorization versus performed-work evidence", "disposition": "accepted", "rationale": "Administrative release, dispatch and closure never prove that work occurred; completion and performance records remain external evidence references, which is essential for auditability and safe agent behavior." }, { "concept": "Aggregate root and task composition", "disposition": "accepted with later harmonization", "rationale": "The order can compose typed task references and order-local parameters without owning task execution semantics. The candidate WM-ACT-006 relation remains visible for later cross-model cardinality and lifecycle review." }, { "concept": "Physical-object facets", "disposition": "rejected as native order properties", "rationale": "A Work Order is an abstract governed record, so mass, material, geometry and other physical properties must belong to referenced targets and resources rather than being fabricated on the order itself." }, { "concept": "State vocabulary", "disposition": "deferred to profiles", "rationale": "The draft captures lifecycle semantics and transition authority but intentionally avoids one universal code list because ISA-95, OPC UA, PLCS and operational implementations use different state names and granularities." }, { "concept": "Revision and deletion semantics", "disposition": "accepted", "rationale": "Immutable issued revisions, linked successors, retention review, legal holds and tombstones preserve historical meaning and prevent destructive updates from invalidating external evidence or references." }, { "concept": "Artifact identity and time", "disposition": "accepted", "rationale": "Master-system identity is prioritized, date-only naming is forbidden, and RFC 3339 timestamps require seconds and explicit offsets while separating event, effective, observation and ingestion times." }, { "concept": "External standard alignment", "disposition": "accepted without conformance claim", "rationale": "The structure uses concepts supported by ISA, OPC Foundation, OASIS PLCS and UNECE, but exact implementation mappings and code-list versions remain explicit profile work rather than unsupported conformance claims." }, { "concept": "Access and emergency exceptions", "disposition": "accepted", "rationale": "Default-deny mutation and disclosure, granular scopes, purpose-bound emergency access and attributable audit records give agents actionable controls without embedding a separate enforcement engine." }, { "concept": "Question and finding coverage", "disposition": "accepted as reviewable draft", "rationale": "All findings expose at least value, authority/provenance and validation/change questions across broad semantic kinds. Their systematic wording is useful for machine completion but still warrants later domain-profile editorial review." } ], "publicationHolds": [ "Live source accessibility, exact standard editions and any normative clause-level mappings have not been independently verified for a canonical release.", "Claude and Grok did not return usable results within bounded attempts, so independent second-provider review is explicitly waived for this published reviewable draft.", "Industry and jurisdiction profiles must validate state vocabularies, signatures, permit rules, retention periods and cancellation effects before operational enforcement.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Validate exact state mappings and mandatory properties against current maintenance, manufacturing, field-service and public-sector implementation profiles.", "Pin mature sibling model IDs and cardinality contracts for procedures, schedules, resources, contracts, evidence, performed work, access control and audit trails.", "Review the generated question wording with practitioners and replace generic evidence forms with profile-specific artifacts where authoritative standards require them." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 17, "findings": 34, "questions": 102, "artifacts": 34, "functions": 10 } }