# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T14:16:31Z", "synthesisSha256": "4eb8bce29f7fe7fa559f47f8e3ec366f9434c4ce1dc6b93b688181320394f6f0", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-013", "registryId": "vr.wm-act-013", "name": "Maintenance", "version": "0.3.0", "previousVersions": [ { "version": "0.2.0-legacy", "url": "https://github.com/ver-cy/world-models/blob/feat/mega-model-registry/models/activity-work/K11-maintenance-and-repair.md" } ], "entryKind": "entity", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.MNT" ], "tags": [ "maintenance", "act.mnt" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-013-maintenance/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-013", "model": { "registry_id": "vr.wm-act-013", "model_id": "WM-ACT-013", "name": "Maintenance", "entry_kind": "entity", "purpose": "Describe the continuing maintenance record for one identified physical asset or explicitly delimited maintainable system.", "scope_statement": "One persistent asset-scoped maintenance record, with qualified condition assertions, applied programme references and linked work history. The root is not a single intervention, an asset master or a portfolio maintenance policy. All hierarchy, fields and functions below are proposed local design informed by the cited sources, not prescribed standard schemas. It records evidence and decisions without performing maintenance or certifying safety.", "in_scope": [ "Stable record identity and effective stewardship for one externally mastered asset or system boundary", "Condition, defects, applied strategy, due rules, planned and unplanned work, competence and control evidence", "Actual interventions, resources, inspection outcomes, release references, learning and controlled continuity" ], "out_of_scope": [ "Asset, ownership, personnel, inventory, finance, contract and procedure master data", "Construction, manufacture, general operation, portfolio optimization and software patch management", "Physical repair instructions, dangerous-item procedures, automated safety authorization and compliance certification" ], "boundary_notes": [ { "neighbor": "WM-OBJ-022 asset lifecycle context", "distinction": "The incoming candidate COMPOSE edge may expose a maintenance-history projection. It neither transfers the asset master nor makes one maintenance record compulsory for every asset.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "Generic act and work order", "distinction": "Acts have their own event identities and orders have their own authorization histories. The persistent maintenance root does not inherit the identity or lifecycle of one act; the legacy EXTEND claim is not ratified at the root.", "source_refs": [ "SRC-003", "SRC-006" ] }, { "neighbor": "Ownership, service contract and organization", "distinction": "References identify asset rights, delegated duties and service commitments. Record stewardship can differ from legal asset ownership; a grant alone cannot settle statutory access duties.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "neighbor": "Plan, schedule, procedure and inventory", "distinction": "Shared definitions and stock masters remain external. This record stores asset-specific applicability, deviations and resource-use evidence with pinned references.", "source_refs": [ "SRC-002", "SRC-003" ] } ] }, "sources": [ { "id": "SRC-001", "title": "ISO 55000:2024 - Asset management - Vocabulary, overview and principles", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/83053.html", "version_or_date": "Edition 2, July 2024; public catalogue only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:14:32Z", "relevance": "Public overview supports lifecycle context and distinction from the wider asset management system. Full paid text was not read." }, { "id": "SRC-002", "title": "ISO 14224:2016 - Collection and exchange of reliability and maintenance data for equipment", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/64076.html", "version_or_date": "Edition 3, September 2016; corrected October 2016; public abstract only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:14:32Z", "relevance": "Abstract identifies equipment, failure and maintenance data, resources, consequences and downtime. Petroleum-sector scope; excludes direct cost data. No clause-level or universal compliance claim." }, { "id": "SRC-003", "title": "Operations and Maintenance Best Practices Guide", "organization": "United States Department of Energy", "url": "https://www.energy.gov/sites/default/files/2020/04/f74/omguide_complete_w-eo-disclaimer.pdf", "version_or_date": "Release 3.0, August 2010; selected chapters 4 and 5", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:14:32Z", "relevance": "Sections 4.2-4.4 and 5.2-5.4 provide context for work tracking, history, resources and strategy. Historical guidance, not current legal authority or a universal performance promise." }, { "id": "SRC-004", "title": "Maintenance of work equipment", "organization": "Health and Safety Executive", "url": "https://www.hse.gov.uk/work-equipment-machinery/maintenance.htm", "version_or_date": "Undated live guidance accessed 2026-10-06; revision pin unresolved", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:14:32Z", "relevance": "Selected maintenance planning, competence and safe-work guidance. Great Britain work-equipment example only; hazardous details are deliberately not reproduced." }, { "id": "SRC-005", "title": "Inspection of work equipment", "organization": "Health and Safety Executive", "url": "https://www.hse.gov.uk/work-equipment-machinery/inspection.htm", "version_or_date": "Undated live guidance accessed 2026-10-06; revision pin unresolved", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:14:32Z", "relevance": "Risk-based inspection extent, intervals, competence and records. Does not require every simple pre-use check to have a formal record. Local legal applicability remains open." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:14:32Z", "relevance": "Sections 3.1-3.3 distinguish entities, activities, agents, attribution, derivation and revision. Conceptual provenance alignment; not a trust or safety certificate." }, { "id": "SRC-007", "title": "RFC 3339 - Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "July 2002; section 5.6; later updates and errata not exhaustively checked", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:14:32Z", "relevance": "Timestamp representation with seconds and offsets. This local profile keeps unknown precision separate and does not infer order solely from clocks." } ], "structure": { "bundles": [ { "id": "maintenance-context-bundle", "name": "Context and responsibility", "description": "Defines whose record this is and the exact maintained boundary.", "rationale": "Separates context and responsibility concerns so evidence and authority are not inferred across lifecycle stages.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ], "layers": [ { "id": "maintenance-identity-layer", "name": "Asset and record identity", "description": "Keep a stable maintenance record ID distinct from the asset reference. Replacement or boundary changes require explicit continuity decisions, not silent reuse.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "findings": [ { "id": "maintenance-identity-finding", "name": "Bounded maintenance identity", "description": "Keep a stable maintenance record ID distinct from the asset reference. Replacement or boundary changes require explicit continuity decisions, not silent reuse.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "questions": [ { "id": "maintenance-identity-q1", "text": "Which master identifiers and system boundary distinguish this maintenance record from the asset and its replaceable components?", "kind": "identity", "answer_data": [ "maintenance-identity-identity-map" ] }, { "id": "maintenance-identity-q2", "text": "How are replacement, split or merged asset boundaries linked without rewriting earlier work history?", "kind": "relationship", "answer_data": [ "maintenance-identity-continuity-map" ] }, { "id": "maintenance-identity-q3", "text": "Which asset class, operating context and maintenance profile qualify the meaning of this record?", "kind": "classification", "answer_data": [ "maintenance-identity-context-profile" ] } ], "data_elements": [ { "id": "maintenance-identity-identity-map", "name": "Identity Map", "description": "Candidate group: record ID, asset master reference, component scope and identifier issuer. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "maintenance-identity-continuity-map", "name": "Continuity Map", "description": "Candidate group: predecessor and successor references, scope mapping and effective period. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "maintenance-identity-context-profile", "name": "Context Profile", "description": "Candidate group: asset class, duty context, location reference and profile version. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "maintenance-identity-artifact", "name": "Bounded maintenance identity evidence", "description": "Versioned record or protected evidence index for bounded maintenance identity. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "maintenance-responsibility-layer", "name": "Stewardship and authority", "description": "Separate record custody, asset rights, technical responsibility and contracted work. Time-bounded delegation must identify scope and evidence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "findings": [ { "id": "maintenance-responsibility-finding", "name": "Effective responsibility assignment", "description": "Separate record custody, asset rights, technical responsibility and contracted work. Time-bounded delegation must identify scope and evidence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "maintenance-responsibility-q1", "text": "Who is accountable for this maintenance record during each custody period, and where are asset rights recorded?", "kind": "ownership", "answer_data": [ "maintenance-responsibility-custody-periods" ] }, { "id": "maintenance-responsibility-q2", "text": "Which delegation permits a maintainer to record work, approve changes or endorse a release for the specific asset scope?", "kind": "authority", "answer_data": [ "maintenance-responsibility-delegation-evidence" ] }, { "id": "maintenance-responsibility-q3", "text": "Which recipient may see technician, defect or commercial details, and what independent duties constrain an owner grant?", "kind": "access", "answer_data": [ "maintenance-responsibility-disclosure-policy" ] } ], "data_elements": [ { "id": "maintenance-responsibility-custody-periods", "name": "Custody Periods", "description": "Candidate group: steward role, asset rights reference and effective period. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "maintenance-responsibility-delegation-evidence", "name": "Delegation Evidence", "description": "Candidate group: role, permitted action, scope, expiry and authority reference. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "maintenance-responsibility-disclosure-policy", "name": "Disclosure Policy", "description": "Candidate group: recipient purpose, field restrictions, duty basis and review decision. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "maintenance-responsibility-artifact", "name": "Effective responsibility assignment evidence", "description": "Versioned record or protected evidence index for effective responsibility assignment. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "maintenance-condition-bundle", "name": "Condition and defects", "description": "Keeps observations separate from interpretation and repair conclusions.", "rationale": "Separates condition and defects concerns so evidence and authority are not inferred across lifecycle stages.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "maintenance-observations-layer", "name": "Condition observations", "description": "An observation is an attributed, time-specific assessment with method and limitations. A dashboard latest value must not suppress conflicting or stale evidence.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ], "findings": [ { "id": "maintenance-observations-finding", "name": "Qualified assessment evidence", "description": "An observation is an attributed, time-specific assessment with method and limitations. A dashboard latest value must not suppress conflicting or stale evidence.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ], "questions": [ { "id": "maintenance-observations-q1", "text": "What was observed on which component, using which scale, unit, method and instrument qualification?", "kind": "measurement", "answer_data": [ "maintenance-observations-assessment-values" ] }, { "id": "maintenance-observations-q2", "text": "When was the condition observed and recorded, and what uncertainty or operating context limits comparison?", "kind": "temporal", "answer_data": [ "maintenance-observations-assessment-context" ] }, { "id": "maintenance-observations-q3", "text": "How are missing, stale or contradictory observations represented without treating absence as acceptable condition?", "kind": "quality", "answer_data": [ "maintenance-observations-assessment-quality" ] } ], "data_elements": [ { "id": "maintenance-observations-assessment-values", "name": "Assessment Values", "description": "Candidate group: component reference, value, unit or scale, method version and instrument evidence. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "maintenance-observations-assessment-context", "name": "Assessment Context", "description": "Candidate group: observation time, recording time, precision, operating state and limitation. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "maintenance-observations-assessment-quality", "name": "Assessment Quality", "description": "Candidate group: quality status, disagreement links, stale rule and review attribution. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "maintenance-observations-artifact", "name": "Qualified assessment evidence evidence", "description": "Versioned record or protected evidence index for qualified assessment evidence. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "maintenance-defects-layer", "name": "Defect interpretation", "description": "A reported anomaly, confirmed defect, failure mode and causal hypothesis remain distinguishable. Closure needs its own evidence and can be reopened.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "findings": [ { "id": "maintenance-defects-finding", "name": "Defect and failure attribution", "description": "A reported anomaly, confirmed defect, failure mode and causal hypothesis remain distinguishable. Closure needs its own evidence and can be reopened.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "questions": [ { "id": "maintenance-defects-q1", "text": "Which defect or anomaly is open on the maintained scope, and how was its severity qualified?", "kind": "state", "answer_data": [ "maintenance-defects-defect-state" ] }, { "id": "maintenance-defects-q2", "text": "What evidence supports the assigned failure mode or suspected cause, including alternative explanations?", "kind": "provenance", "answer_data": [ "maintenance-defects-diagnostic-basis" ] }, { "id": "maintenance-defects-q3", "text": "What evidence and authorized review support closure or reopening of a defect after an intervention?", "kind": "lifecycle", "answer_data": [ "maintenance-defects-defect-disposition" ] } ], "data_elements": [ { "id": "maintenance-defects-defect-state", "name": "Defect State", "description": "Candidate group: defect ID, affected scope, observed symptom, status and severity basis. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "maintenance-defects-diagnostic-basis", "name": "Diagnostic Basis", "description": "Candidate group: classification vocabulary version, causal confidence, evidence and alternatives. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "maintenance-defects-defect-disposition", "name": "Defect Disposition", "description": "Candidate group: linked intervention, reviewer, residual issue, disposition and superseded state. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "maintenance-defects-artifact", "name": "Defect and failure attribution evidence", "description": "Versioned record or protected evidence index for defect and failure attribution. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "maintenance-programme-bundle", "name": "Applied programme", "description": "Records why work is due and preserves approved changes.", "rationale": "Separates applied programme concerns so evidence and authority are not inferred across lifecycle stages.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007" ], "layers": [ { "id": "maintenance-strategy-layer", "name": "Strategy applicability", "description": "The applied programme links a reviewed strategy to asset context. A chosen approach is not a guarantee of reliability and may vary by failure mode.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "maintenance-strategy-finding", "name": "Asset-specific strategy decision", "description": "The applied programme links a reviewed strategy to asset context. A chosen approach is not a guarantee of reliability and may vary by failure mode.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "maintenance-strategy-q1", "text": "Which strategy applies to each maintained function, and what risk or performance rationale supports it?", "kind": "decision", "answer_data": [ "maintenance-strategy-strategy-decision" ] }, { "id": "maintenance-strategy-q2", "text": "Which versioned instructions, obligations and procedure definitions constrain the selected maintenance strategy?", "kind": "requirement", "answer_data": [ "maintenance-strategy-programme-basis" ] }, { "id": "maintenance-strategy-q3", "text": "How are strategy changes or deliberate deferrals justified, bounded and reviewed without hiding unresolved risk?", "kind": "exception", "answer_data": [ "maintenance-strategy-programme-exception" ] } ], "data_elements": [ { "id": "maintenance-strategy-strategy-decision", "name": "Strategy Decision", "description": "Candidate group: strategy code, maintained function, objective, rationale and approval reference. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "maintenance-strategy-programme-basis", "name": "Programme Basis", "description": "Candidate group: instruction and obligation references, applicability period and procedure revision. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "maintenance-strategy-programme-exception", "name": "Programme Exception", "description": "Candidate group: exception reason, authority, risk reference, expiry and compensating-policy reference. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "maintenance-strategy-artifact", "name": "Asset-specific strategy decision evidence", "description": "Versioned record or protected evidence index for asset-specific strategy decision. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "maintenance-due-rules-layer", "name": "Intervals and triggers", "description": "Keep calendar, usage and condition triggers explicit. Unknown meter continuity or unavailable condition evidence yields an indeterminate result, not a safe extension.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ], "findings": [ { "id": "maintenance-due-rules-finding", "name": "Qualified due-work determination", "description": "Keep calendar, usage and condition triggers explicit. Unknown meter continuity or unavailable condition evidence yields an indeterminate result, not a safe extension.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ], "questions": [ { "id": "maintenance-due-rules-q1", "text": "Which calendar, elapsed-use or condition rule determines the next due work and its observation basis?", "kind": "temporal", "answer_data": [ "maintenance-due-rules-due-rule" ] }, { "id": "maintenance-due-rules-q2", "text": "How are meter resets, missing readings, time uncertainty and trigger conflicts handled before marking work due or overdue?", "kind": "validation", "answer_data": [ "maintenance-due-rules-due-quality" ] }, { "id": "maintenance-due-rules-q3", "text": "Who approved the planned work window or interval revision, and how are blocked or overdue tasks escalated?", "kind": "process", "answer_data": [ "maintenance-due-rules-schedule-decision" ] } ], "data_elements": [ { "id": "maintenance-due-rules-due-rule", "name": "Due Rule", "description": "Candidate group: rule version, baseline event, time zone, usage unit, threshold and evidence reference. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] }, { "id": "maintenance-due-rules-due-quality", "name": "Due Quality", "description": "Candidate group: reset history, completeness, evaluation instant, conflict rule and indeterminate reason. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] }, { "id": "maintenance-due-rules-schedule-decision", "name": "Schedule Decision", "description": "Candidate group: approved window, dependencies, revision authority, escalation and exception reference. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "maintenance-due-rules-artifact", "name": "Qualified due-work determination evidence", "description": "Versioned record or protected evidence index for qualified due-work determination. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "maintenance-work-control-bundle", "name": "Work control", "description": "Separates requested work, authority and readiness to undertake it.", "rationale": "Separates work control concerns so evidence and authority are not inferred across lifecycle stages.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "maintenance-orders-layer", "name": "Work request and order", "description": "Requests, approval and execution evidence are separate. An emergency or retrospective record is possible without inventing prior approval or a mandatory programme link.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "maintenance-orders-finding", "name": "Authorized scope and progress", "description": "Requests, approval and execution evidence are separate. An emergency or retrospective record is possible without inventing prior approval or a mandatory programme link.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "maintenance-orders-q1", "text": "Which request and work-order identifiers link the proposed task to its asset scope and initiating condition?", "kind": "identity", "answer_data": [ "maintenance-orders-work-links" ] }, { "id": "maintenance-orders-q2", "text": "Who authorized which work scope and revision, with what priority, constraints and permitted expenditure reference?", "kind": "authority", "answer_data": [ "maintenance-orders-order-authorization" ] }, { "id": "maintenance-orders-q3", "text": "How are cancellation, partial completion, blocked work and emergency retrospective registration distinguished from authorized completion?", "kind": "state", "answer_data": [ "maintenance-orders-order-progress" ] } ], "data_elements": [ { "id": "maintenance-orders-work-links", "name": "Work Links", "description": "Candidate group: request ID, order master ID, asset scope, defect or programme reference. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "maintenance-orders-order-authorization", "name": "Order Authorization", "description": "Candidate group: authorizer role, scope version, priority basis, constraints and budget decision reference. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "maintenance-orders-order-progress", "name": "Order Progress", "description": "Candidate group: state, state time, completed scope, remaining scope and exception evidence. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "maintenance-orders-artifact", "name": "Authorized scope and progress evidence", "description": "Versioned record or protected evidence index for authorized scope and progress. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "maintenance-readiness-layer", "name": "Competence and work controls", "description": "The record links competence, approved method and risk-control decisions. Presence of a checklist is not proof that controls are effective; dangerous procedures remain outside this model.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "findings": [ { "id": "maintenance-readiness-finding", "name": "Evidence of readiness review", "description": "The record links competence, approved method and risk-control decisions. Presence of a checklist is not proof that controls are effective; dangerous procedures remain outside this model.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "maintenance-readiness-q1", "text": "What task-specific competence and procedure revision were required, and what evidence was reviewed for each assigned role?", "kind": "requirement", "answer_data": [ "maintenance-readiness-competence-check" ] }, { "id": "maintenance-readiness-q2", "text": "Which authorized risk-control and permit records govern the work, and how is their current status evidenced?", "kind": "security", "answer_data": [ "maintenance-readiness-control-references" ] }, { "id": "maintenance-readiness-q3", "text": "What stops or postpones the task when competence, control evidence or site coordination is missing or disputed?", "kind": "exception", "answer_data": [ "maintenance-readiness-readiness-exception" ] } ], "data_elements": [ { "id": "maintenance-readiness-competence-check", "name": "Competence Check", "description": "Candidate group: role, task scope, competence reference, validity and approved procedure revision. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "maintenance-readiness-control-references", "name": "Control References", "description": "Candidate group: risk assessment, control or permit reference, issuer, status and verification time. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "maintenance-readiness-readiness-exception", "name": "Readiness Exception", "description": "Candidate group: blocking reason, affected task scope, escalation recipient and restart decision reference. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "maintenance-readiness-artifact", "name": "Evidence of readiness review evidence", "description": "Versioned record or protected evidence index for evidence of readiness review. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "maintenance-performance-bundle", "name": "Performed work and resources", "description": "Records what actually happened without rewriting the authorized plan.", "rationale": "Separates performed work and resources concerns so evidence and authority are not inferred across lifecycle stages.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007" ], "layers": [ { "id": "maintenance-interventions-layer", "name": "Actual intervention", "description": "An intervention can cover part of an order or reveal new work. Actual times, actors and deviations retain their own provenance; no work is inferred from a scheduled slot.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "maintenance-interventions-finding", "name": "Attributed work execution record", "description": "An intervention can cover part of an order or reveal new work. Actual times, actors and deviations retain their own provenance; no work is inferred from a scheduled slot.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007" ], "questions": [ { "id": "maintenance-interventions-q1", "text": "What maintenance action actually occurred, by whom, on which scope and against which order or emergency basis?", "kind": "event", "answer_data": [ "maintenance-interventions-actual-work" ] }, { "id": "maintenance-interventions-q2", "text": "Which actual activity and outage periods were observed, with what time precision and distinction from planned duration?", "kind": "temporal", "answer_data": [ "maintenance-interventions-actual-periods" ] }, { "id": "maintenance-interventions-q3", "text": "Which deviations, interrupted steps or newly discovered defects require separate authorization or follow-up?", "kind": "process", "answer_data": [ "maintenance-interventions-execution-deviations" ] } ], "data_elements": [ { "id": "maintenance-interventions-actual-work", "name": "Actual Work", "description": "Candidate group: intervention ID, action description, actor role, asset scope and order or exception reference. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "maintenance-interventions-actual-periods", "name": "Actual Periods", "description": "Candidate group: activity start and end, outage intervals, precision, recording time and partial-state reason. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "maintenance-interventions-execution-deviations", "name": "Execution Deviations", "description": "Candidate group: scope deviation, stopped work, new defect references and follow-up decision. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "maintenance-interventions-artifact", "name": "Attributed work execution record evidence", "description": "Versioned record or protected evidence index for attributed work execution record. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "maintenance-resources-layer", "name": "Parts and resource use", "description": "Represent installed, removed, consumed and unused materials separately. Resource use links to external inventory and finance records; lot traceability depends on the item profile.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "findings": [ { "id": "maintenance-resources-finding", "name": "Traceable resource disposition", "description": "Represent installed, removed, consumed and unused materials separately. Resource use links to external inventory and finance records; lot traceability depends on the item profile.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "maintenance-resources-q1", "text": "Which components or materials were installed, removed or consumed, in what quantities and units?", "kind": "composition", "answer_data": [ "maintenance-resources-material-movements" ] }, { "id": "maintenance-resources-q2", "text": "Which serial, lot, supplier or suitability evidence is available, required or missing for each used item?", "kind": "provenance", "answer_data": [ "maintenance-resources-material-evidence" ] }, { "id": "maintenance-resources-q3", "text": "How are labor, tools, unused parts, waste and cost references reconciled without making this record the inventory or finance master?", "kind": "relationship", "answer_data": [ "maintenance-resources-resource-reconciliation" ] } ], "data_elements": [ { "id": "maintenance-resources-material-movements", "name": "Material Movements", "description": "Candidate group: part reference, movement type, quantity, unit and affected position. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "maintenance-resources-material-evidence", "name": "Material Evidence", "description": "Candidate group: item traceability identifiers, suitability decision, source record and missing-evidence status. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "maintenance-resources-resource-reconciliation", "name": "Resource Reconciliation", "description": "Candidate group: resource-use entries, return or disposal references, labor duration and finance links. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "maintenance-resources-artifact", "name": "Traceable resource disposition evidence", "description": "Versioned record or protected evidence index for traceable resource disposition. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "maintenance-outcome-bundle", "name": "Verification and disposition", "description": "Separates evidence of results from authority to resume use.", "rationale": "Separates verification and disposition concerns so evidence and authority are not inferred across lifecycle stages.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "maintenance-verification-layer", "name": "Post-work evidence", "description": "Before and after evidence may be incomparable, unchanged or worse. A temporal association does not establish that the intervention caused the observed change.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ], "findings": [ { "id": "maintenance-verification-finding", "name": "Qualified outcome comparison", "description": "Before and after evidence may be incomparable, unchanged or worse. A temporal association does not establish that the intervention caused the observed change.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ], "questions": [ { "id": "maintenance-verification-q1", "text": "Which inspection or test evidence demonstrates the actual result against the stated acceptance criteria?", "kind": "validation", "answer_data": [ "maintenance-verification-acceptance-evidence" ] }, { "id": "maintenance-verification-q2", "text": "Are the before and after observations comparable in scope, scale and operating context, and what change can be supported?", "kind": "measurement", "answer_data": [ "maintenance-verification-condition-comparison" ] }, { "id": "maintenance-verification-q3", "text": "Which residual defects, failed criteria or unobserved outcomes remain visible after the work is recorded as performed?", "kind": "quality", "answer_data": [ "maintenance-verification-residual-outcome" ] } ], "data_elements": [ { "id": "maintenance-verification-acceptance-evidence", "name": "Acceptance Evidence", "description": "Candidate group: criterion revision, examination reference, observed result, reviewer and limitation. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "maintenance-verification-condition-comparison", "name": "Condition Comparison", "description": "Candidate group: paired observations, comparison method, supported difference and comparability status. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "maintenance-verification-residual-outcome", "name": "Residual Outcome", "description": "Candidate group: residual issue links, unmet criterion, unknown result and follow-up scope. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "maintenance-verification-artifact", "name": "Qualified outcome comparison evidence", "description": "Versioned record or protected evidence index for qualified outcome comparison. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "maintenance-release-layer", "name": "Use restrictions and release", "description": "Local completion does not authorize operation. Record an external authorized decision with scope, restrictions and expiry; allow withheld, conditional or revoked disposition.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "maintenance-release-finding", "name": "Qualified disposition decision", "description": "Local completion does not authorize operation. Record an external authorized decision with scope, restrictions and expiry; allow withheld, conditional or revoked disposition.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "maintenance-release-q1", "text": "Who made the applicable decision to allow, restrict or prohibit further use, and on what competence and authority basis?", "kind": "authority", "answer_data": [ "maintenance-release-release-authority" ] }, { "id": "maintenance-release-q2", "text": "What asset configuration, operating conditions, residual issues and validity period bound the recorded release or restriction?", "kind": "constraint", "answer_data": [ "maintenance-release-release-conditions" ] }, { "id": "maintenance-release-q3", "text": "How are a withheld, conditional or revoked release and any subsequent resumption of use recorded as distinct events?", "kind": "lifecycle", "answer_data": [ "maintenance-release-release-history" ] } ], "data_elements": [ { "id": "maintenance-release-release-authority", "name": "Release Authority", "description": "Candidate group: decision reference, issuer role, delegated scope and authority evidence. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "maintenance-release-release-conditions", "name": "Release Conditions", "description": "Candidate group: configuration reference, permitted scope, restrictions, expiry and residual issue references. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "maintenance-release-release-history", "name": "Release History", "description": "Candidate group: decision revision, effective time, revocation basis, use event reference and notification evidence. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "maintenance-release-artifact", "name": "Qualified disposition decision evidence", "description": "Versioned record or protected evidence index for qualified disposition decision. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "maintenance-continuity-bundle", "name": "Learning and record continuity", "description": "Supports qualified summaries and responsible preservation.", "rationale": "Separates learning and record continuity concerns so evidence and authority are not inferred across lifecycle stages.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "maintenance-learning-layer", "name": "History and improvement", "description": "Summary metrics require explicit populations, durations and exclusions. Proposed programme changes remain separate decisions; no reliability improvement is promised.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "findings": [ { "id": "maintenance-learning-finding", "name": "Evidence-qualified maintenance review", "description": "Summary metrics require explicit populations, durations and exclusions. Proposed programme changes remain separate decisions; no reliability improvement is promised.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "maintenance-learning-q1", "text": "What population, observation window, downtime definition and exclusions underlie a maintenance or failure metric?", "kind": "measurement", "answer_data": [ "maintenance-learning-metric-definition" ] }, { "id": "maintenance-learning-q2", "text": "Which missing work records, repeat defects or uncertain classifications limit the interpretation of reported performance?", "kind": "quality", "answer_data": [ "maintenance-learning-review-limitations" ] }, { "id": "maintenance-learning-q3", "text": "What approved follow-up changes the programme after review, and how is its rationale linked to the supporting evidence?", "kind": "decision", "answer_data": [ "maintenance-learning-improvement-decision" ] } ], "data_elements": [ { "id": "maintenance-learning-metric-definition", "name": "Metric Definition", "description": "Candidate group: metric name, numerator, denominator, asset population, window and exclusions. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "maintenance-learning-review-limitations", "name": "Review Limitations", "description": "Candidate group: completeness indicators, repeat-event links, uncertainty and reviewer assessment. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "maintenance-learning-improvement-decision", "name": "Improvement Decision", "description": "Candidate group: proposal, supporting history, decision authority, effective revision and later review point. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "maintenance-learning-artifact", "name": "Evidence-qualified maintenance review evidence", "description": "Versioned record or protected evidence index for evidence-qualified maintenance review. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "maintenance-record-continuity-layer", "name": "Transfer and retention", "description": "Corrections, custody transfer and lawful disposal must preserve meaning without imposing perpetual payload retention. Different record classes may have different periods and access duties.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "maintenance-record-continuity-finding", "name": "Controlled history continuity", "description": "Corrections, custody transfer and lawful disposal must preserve meaning without imposing perpetual payload retention. Different record classes may have different periods and access duties.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "maintenance-record-continuity-q1", "text": "How does a corrected or imported entry identify its source, original version and superseded assertion?", "kind": "provenance", "answer_data": [ "maintenance-record-continuity-revision-lineage" ] }, { "id": "maintenance-record-continuity-q2", "text": "Which record-class retention rule, unresolved claim or hold governs disposal, including copies and personal details?", "kind": "retention", "answer_data": [ "maintenance-record-continuity-retention-decision" ] }, { "id": "maintenance-record-continuity-q3", "text": "What authorized transfer package preserves asset and event references, code meanings, access limits and missing-history declarations?", "kind": "interoperability", "answer_data": [ "maintenance-record-continuity-handover-package" ] } ], "data_elements": [ { "id": "maintenance-record-continuity-revision-lineage", "name": "Revision Lineage", "description": "Candidate group: source master ID, import mapping, revision ID, supersession link and attribution. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "maintenance-record-continuity-retention-decision", "name": "Retention Decision", "description": "Candidate group: record class, rule reference, trigger, hold scope, disposition authority and copy inventory. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "maintenance-record-continuity-handover-package", "name": "Handover Package", "description": "Candidate group: recipient scope, identifier mapping, vocabulary versions, redactions and completeness statement. Unknown and not-applicable values need explicit status; nested schema is deferred.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "maintenance-record-continuity-artifact", "name": "Controlled history continuity evidence", "description": "Versioned record or protected evidence index for controlled history continuity. A pointer is not proof of truth or authorization.", "media_or_form": [ "Structured record", "Protected evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer and revision; otherwise a scoped registered UUID. Digest verifies bytes, not identity or truth. Time is metadata, never the sole identifier.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "maintenance-register-context", "name": "Register bounded maintenance context", "description": "Proposed, unimplemented local operation. Create the local record and qualified asset links.", "inputs": [ "Asset reference, scope definition, custody evidence", "Expected record revision and actor role" ], "outputs": [ "Registered record or unresolved-identity refusal" ], "preconditions": [ "Valid asset scope and explicit actor authorization for this operation", "Expected revision matches; source evidence and applicable profile can be resolved" ], "effects": [ "No merging of ambiguous assets or assumption of ownership.", "Successful writes append attributed revision evidence; stale or unauthorized requests leave state unchanged." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "maintenance-record-assessment", "name": "Record an attributed assessment", "description": "Proposed, unimplemented local operation. Append an observation or defect assertion with uncertainty.", "inputs": [ "Observation, method, actor, time and evidence", "Expected record revision and actor role" ], "outputs": [ "Versioned assessment or incomplete-evidence refusal" ], "preconditions": [ "Valid asset scope and explicit actor authorization for this operation", "Expected revision matches; source evidence and applicable profile can be resolved" ], "effects": [ "Preserves contrary observations and separates causal hypotheses.", "Successful writes append attributed revision evidence; stale or unauthorized requests leave state unchanged." ], "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "maintenance-evaluate-due", "name": "Evaluate stated due rules", "description": "Proposed, unimplemented local operation. Evaluate a supplied approved trigger as a proposed local calculation.", "inputs": [ "Rule revision, baseline, usage or condition evidence, evaluation instant", "Expected record revision and actor role" ], "outputs": [ "Due, not-due or indeterminate result with basis" ], "preconditions": [ "Valid asset scope and explicit actor authorization for this operation", "Expected revision matches; source evidence and applicable profile can be resolved" ], "effects": [ "Does not extend an interval, authorize deferral or suppress unknown input.", "Successful writes append attributed revision evidence; stale or unauthorized requests leave state unchanged." ], "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] }, { "id": "maintenance-link-work", "name": "Link order and readiness evidence", "description": "Proposed, unimplemented local operation. Record separately authorized scope and readiness references.", "inputs": [ "Order revision, delegation, competence and control evidence", "Expected record revision and actor role" ], "outputs": [ "Linked work-control snapshot or conflict refusal" ], "preconditions": [ "Valid asset scope and explicit actor authorization for this operation", "Expected revision matches; source evidence and applicable profile can be resolved" ], "effects": [ "Does not issue permits, dispatch work or operate equipment.", "Successful writes append attributed revision evidence; stale or unauthorized requests leave state unchanged." ], "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "maintenance-record-intervention", "name": "Record actual work and resources", "description": "Proposed, unimplemented local operation. Append performed-work assertions and resource references.", "inputs": [ "Attributed intervention, actual periods, parts and deviations", "Expected record revision and actor role" ], "outputs": [ "Versioned work record with outstanding exceptions" ], "preconditions": [ "Valid asset scope and explicit actor authorization for this operation", "Expected revision matches; source evidence and applicable profile can be resolved" ], "effects": [ "Does not infer completion from schedule or update stock and financial masters.", "Successful writes append attributed revision evidence; stale or unauthorized requests leave state unchanged." ], "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "maintenance-record-disposition", "name": "Record qualified outcome and release", "description": "Proposed, unimplemented local operation. Link observed outcomes and an externally authorized use decision.", "inputs": [ "Acceptance evidence, residual defects, decision issuer and scoped authority", "Expected record revision and actor role" ], "outputs": [ "Outcome record and qualified disposition or unresolved-authority refusal" ], "preconditions": [ "Valid asset scope and explicit actor authorization for this operation", "Expected revision matches; source evidence and applicable profile can be resolved" ], "effects": [ "Cannot itself certify safety, close unsupported defects or authorize return to service.", "Successful writes append attributed revision evidence; stale or unauthorized requests leave state unchanged." ], "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "maintenance-prepare-history", "name": "Prepare a scoped history projection", "description": "Proposed, unimplemented local operation. Produce an entitled-recipient view with completeness and lineage metadata.", "inputs": [ "Recipient purpose, current access decision, record selection and retention constraints", "Expected record revision and actor role" ], "outputs": [ "Redacted history and mapping manifest or access refusal" ], "preconditions": [ "Valid asset scope and explicit actor authorization for this operation", "Expected revision matches; source evidence and applicable profile can be resolved" ], "effects": [ "Does not transfer custody, disclose externally or dispose of evidence automatically.", "Successful writes append attributed revision evidence; stale or unauthorized requests leave state unchanged." ], "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "composition": [ { "target": "WM-OBJ-022", "relation": "REFERENCE", "purpose": "Candidate external asset lifecycle context. The incoming COMPOSE edge is a history projection, not mandatory containment or reciprocal ownership.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "Asset and ownership master", "relation": "REFERENCE", "purpose": "Resolve asset identity and rights without copying masters. Exact registry bindings require later review.", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "Plan, schedule and procedure definitions", "relation": "REFERENCE", "purpose": "Pin approved definitions; record only applied asset scope and actual deviations locally.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "Service, organization and personnel records", "relation": "REFERENCE", "purpose": "Resolve contract and competence evidence; do not infer release authority from employment or service assignment.", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "target": "Inventory and financial records", "relation": "REFERENCE", "purpose": "Link material movements and approved cost evidence; ISO 14224 abstract is not a direct-cost schema.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "Generic act model", "relation": "ALIGN", "purpose": "Maintenance interventions may specialize activity semantics; the persistent root does not inherit an atomic act lifecycle.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "ISO 55000:2024 and ISO 14224:2016", "relation": "ALIGN", "purpose": "Public overview and abstract alignment only, subject to domain and licensing review; no conformance assertion.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "PROV-O and RFC 3339", "relation": "ALIGN", "purpose": "Conceptual attribution and timestamp alignment; executable mappings and validators remain deferred.", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Name the accountable record steward and delegated maintainer roles with effective scope; use role names rather than company names.", "Declare the single asset or maintainable system boundary, asset master binding and custody periods.", "Pin the maintenance profile, data classifications, retention schedule and decision authorities before operational adoption.", "Publish a local AGENTS.md with specification, storage, interface and process references, stating unresolved runtime bindings." ], "namespace_guidance": "Use a stable owner-scoped maintenance namespace and opaque record IDs. Keep asset, work order, intervention, artifact and revision identifiers distinct; dates and personal names must not be identity keys.", "registry_links": [ "vr.wm-act-013", "WM-OBJ-022 candidate asset lifecycle link; exact bindings require review" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve original observations, units, code systems and attributed revisions; normalized projections retain reversible mappings.", "Use explicit unknown, disputed and not-applicable states. No last-write-wins resolution of contradictory safety evidence." ], "patch_rules": [ "Require expected revision, actor authority, reason and evidence before local mutation; reject stale concurrent writes.", "Correct by linked supersession, retaining required evidence subject to the applicable retention and privacy rules." ], "compatibility_rules": [ "Version changes to asset boundary, strategy codes, due semantics or release meaning require reviewed migration and explicit loss reports.", "Legacy K11 object names are migration leads. Do not import its conformance label, wildcard standards, mandatory programme/order links or one-to-one condition delta." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier qualified by issuer and revision", "Existing durable registry identifier or controlled external reference", "Owner-scoped UUID registered before use; never a time-only identifier" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit UTC offset for known instants. Preserve observation versus recording time and actual precision separately; never invent seconds for date-only historical evidence.", "serial_naming_rule": "Serial reports use stable artifact ID and monotonic revision under the issuing system; human dates are labels, not identity.", "integrity_rule": "Bind revisions to byte digests, source references, creator and access classification. Digests detect changes but do not establish competence, completeness, authorization or physical truth." }, "policies": [ "All operational safety rules, release authority, inspection intervals and retention periods require a qualified asset and jurisdiction profile; the cited guidance does not create universal obligations.", "Dangerous subjects remain at policy and reference level. Agents do not execute repairs, bypass controls, authorize hazardous work or certify safe use.", "Keep personnel, site and commercial information scoped to a legitimate purpose. Asset ownership alone does not establish every disclosure right.", "Record limitations and missing history explicitly. Local schema validity is not physical-condition validation or evidence of regulatory compliance." ], "crud": { "read": [ "Resolve recipient purpose and effective permission before returning findings or evidence; redact sensitive actor and site details." ], "create": [ "Create only within verified asset scope with unique identity, issuer, evidence and attributed authorization; allow documented incomplete history." ], "update": [ "Append revisions with optimistic concurrency; distinguish observation corrections from changed real-world condition or authority." ], "delete": [ "Apply record-class retention, lawful holds and authorized disposition to payloads and copies; retain minimal lawful tombstones and lineage where permitted.", "Retiring a local maintenance record does not retire the asset, revoke legal decisions or justify indefinite retention of personal data." ] }, "roles": [ { "name": "Record steward", "responsibilities": [ "Maintain asset scope, custody and lawful access rules; coordinate retention review." ] }, { "name": "Maintenance planner", "responsibilities": [ "Record approved strategy, due rules, work scope and reviewed exceptions." ] }, { "name": "Competent maintainer", "responsibilities": [ "Submit attributed actual-work and resource evidence within authorized scope." ] }, { "name": "Technical reviewer", "responsibilities": [ "Assess outcome evidence and residual defects; preserve disagreement." ] }, { "name": "Release authority", "responsibilities": [ "Provide separately authorized, scoped and time-qualified use decisions where the applicable profile permits." ] }, { "name": "Records custodian", "responsibilities": [ "Control corrections, transfer packages, retention holds and authorized disposal." ] } ], "access": { "default_rule": "Deny access and mutation unless the actor has an effective role, asset scope and permitted purpose; technical competence and release authority require separate evidence.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency access requires an applicable policy, bounded purpose, recorded authority and subsequent review; it is not a bypass of safety controls." ], "audit_requirements": [ "Log access, export, revision and disposition decisions with actor, purpose, scope, time and outcome; protect logs and apply their own retention rules." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Record steward", "Asset scope", "Review state and holds" ], "read_order": [ "Read AGENTS.md identity, review state and unresolved holds.", "Read spec.yaml boundary, applicable profile and source limitations.", "Check permissions, referenced evidence and expected revision before any local operation." ] } }, "coverage": { "claim": "Source-grounded proposed structure for one persistent maintenance record scoped to a physical asset or explicitly bounded maintainable system. Selected public sources and a separate local no-tools self-audit support a reviewable draft. Independent review, source/version checks, asset and jurisdiction profiles, executable schemas and mappings remain holds; no universal completeness or safety certification is claimed.", "confidence": "medium", "checklist": [ { "dimension": "Identity", "status": "covered", "notes": "Record, asset, order and intervention identities remain distinct." }, { "dimension": "Lifecycle", "status": "covered", "notes": "Partial work, defects, disposition and continuity have separate histories." }, { "dimension": "Relationships", "status": "covered", "notes": "Candidate references retain external master ownership." }, { "dimension": "Temporal", "status": "covered", "notes": "Effective periods, due rules, actual periods and uncertainty are explicit." }, { "dimension": "Provenance", "status": "covered", "notes": "Observation, attribution, hypothesis and revision are distinguishable." }, { "dimension": "Ownership", "status": "covered", "notes": "Custody, rights and delegated authority are separate." }, { "dimension": "Validation", "status": "gap", "notes": "Research schema can validate; nested instance and safety conformance cannot yet be asserted." }, { "dimension": "Access", "status": "covered", "notes": "Purpose, role and asset scope govern restricted views." }, { "dimension": "Interoperability", "status": "gap", "notes": "Conceptual alignments exist; executable mappings and exact neighbor pins are deferred." }, { "dimension": "Resources", "status": "covered", "notes": "Parts, labor, tools and external financial links avoid duplicate masters." }, { "dimension": "Safety and authority", "status": "covered", "notes": "Policy-level controls and evidence references do not authorize physical actions." }, { "dimension": "Retention", "status": "covered", "notes": "Record-class rules and holds govern disposal; no universal lifetime retention." } ], "known_omissions": [ "Independent external review is absent; a later local self-audit cannot replace it.", "Full paid ISO texts and EN 13306 terminology mapping were not reviewed; no standard-conformance certification.", "Current source versions, complete errata, legal applicability and all asset-sector regimes remain unverified.", "Executable nested instance schemas, event cardinalities, state machines, neighbor bindings and import mappings require fixtures.", "Physical intervention methods, predictive algorithms, safety thresholds and universal maintenance intervals are deliberately excluded." ], "conflicts": [], "regional_assumptions": [ "Great Britain work-equipment guidance and historical United States facilities guidance are examples, not global law.", "The ISO 14224 abstract has a specified industrial domain; applying its concepts elsewhere is a proposed design inference." ], "adversarial_checks": [ "Reject work-order completion as proof of physical safety or release authority.", "Reject identical labels or timestamps as proof that asset, component or intervention identities match.", "Allow unknown, unchanged or worsened condition and unconfirmed causal attribution.", "Allow reactive work with no programme reference and truthful retrospective recording without invented prior authority.", "Treat custody transfer as a reviewed mapping, not deletion of inconvenient history." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The root retains record identity across observations, programme revisions, orders, interventions and custody periods. It is not an atomic event or an asset master. The registry standalone-mm value classifies the registry plane; entity is the subject kind. The legacy standing-history concept is reconciled without inheriting its act-root extension." }, "decisions": [ { "concept": "Persistent root and system boundary", "disposition": "accepted", "rationale": "One externally identified asset or explicitly bounded maintainable system anchors the continuing record. Component references and linked orders do not silently broaden it into a portfolio programme." }, { "concept": "Legacy generic act inheritance", "disposition": "rejected at root", "rationale": "A performed intervention may align with an activity, but the record persists across many such events. Root inheritance from the legacy generic act would conflate their identities and lifecycles." }, { "concept": "Incoming candidate asset composition", "disposition": "qualified", "rationale": "The WM-OBJ-022 edge can expose maintenance history while preserving the asset master. Optional composition entries denote unpinned runtime bindings, not permission to omit asset identity from an operational instance." }, { "concept": "Ownership and technical authority", "disposition": "separated", "rationale": "Custody, asset rights, permission to write, competence and authority to release equipment remain distinct. No company is named as model owner, and an owner grant cannot settle every external duty." }, { "concept": "Condition and diagnostic evidence", "disposition": "accepted with uncertainty", "rationale": "Observation method, time, scale, uncertainty and disagreement are retained. Failure causes can remain hypotheses and missing evidence is not treated as acceptable condition." }, { "concept": "Programme and due-work evaluation", "disposition": "qualified", "rationale": "Approved rules and their baselines remain separate from local evaluation. Missing meter history and uncertain time can produce indeterminate results; the proposed function cannot extend intervals or approve deferral." }, { "concept": "Work order and emergency history", "disposition": "accepted", "rationale": "Request, authorized scope and actual progress are distinct. Reactive or emergency work can be recorded truthfully without fabricating a programme link or prior authorization." }, { "concept": "Competence and safety controls", "disposition": "policy-level only", "rationale": "The questions ask for task-specific authority and control evidence. A linked permit or checklist is not proof of effective controls, and no physical or dangerous-item procedure is supplied." }, { "concept": "Actual work and resource ownership", "disposition": "accepted", "rationale": "Performed actions, actual periods and deviations have their own attribution. Material movements preserve missing traceability and link external stock and finance masters; direct cost semantics are not attributed to ISO 14224." }, { "concept": "Condition delta and release", "disposition": "separated", "rationale": "The result rejects mandatory one-to-one deltas, guaranteed improvement and inferred causation. Outcome evidence, authorized disposition and actual resumption of use remain separate records." }, { "concept": "Metrics and programme improvement", "disposition": "qualified", "rationale": "Metrics require explicit population, observation window and exclusions. Missing history remains visible and programme changes require a separate approved decision; historical savings claims are not adopted." }, { "concept": "Artifact continuity and retention", "disposition": "accepted with profile dependency", "rationale": "Issuer-qualified master IDs and revisions precede UUID fallback. Digests and clocks do not establish truth or authority. Revision history is reconciled with record-class retention, scoped holds and lawful minimal tombstones." }, { "concept": "Source support and instance conformance", "disposition": "limited and deferred", "rationale": "Public ISO summaries and selected guidance support conceptual design, not exact normative fields. All candidate object groups remain optional research descriptions; operational cardinalities, nested schemas and import mappings need fixtures and qualified review." }, { "concept": "Independent review and source status", "disposition": "waived and held", "rationale": "Claude and Grok have zero attempts and no admitted results under the owner override. This is a separate local Codex self-audit. Browser readings do not constitute measured direct HTTP status, complete currency verification or independent review." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not independent second-provider review.", "Live source and version verification remains incomplete. Direct HTTP was not attempted under the owner-reported sandbox restriction: zero attempts and zero measured HTTP 200 responses, with all seven statuses unmeasured. Selected browser evidence is documented; paid ISO texts, full update chains, errata and EN 13306 mapping remain unverified.", "Asset-sector and jurisdiction profiles require qualified review of safety authority, competence, inspection obligations, intervals, terminology, privacy, licensing and retention before operational use. No physical safety, legal compliance or maintenance-performance certification is claimed.", "Executable nested instance schemas, required field cardinalities, state transitions, exact neighbor bindings, provenance mappings and adversarial fixtures remain incomplete. The seven local functions are proposed and unimplemented; the package is not an operational maintenance controller.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify live source responses and current versions outside the sandbox, obtain appropriately licensed standards text, and review the relevant sector and jurisdiction requirements.", "Develop instance schemas and mappings with fixtures for replaced assets, meter reset, conflicting observations, emergency work, partial completion, failed inspection, withheld release and lawful record disposal.", "Restore independent external review before promotion beyond a noncanonical reviewable draft." ] }, "statistics": { "sources": 7, "bundles": 7, "layers": 14, "findings": 14, "questions": 42, "artifacts": 14, "functions": 7 } }