# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T14:06:21Z", "synthesisSha256": "50622ec30bd05c8bd1c2f029e61169faead213447b1e1e6cea0bff91eb203106", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-009", "registryId": "vr.wm-act-009", "name": "Method / Procedure", "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/K6-practice-method-and-procedure.md" } ], "entryKind": "entity", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.MTH" ], "tags": [ "method", "procedure", "act.mth" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-009-method-procedure/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-009", "model": { "registry_id": "vr.wm-act-009", "model_id": "WM-ACT-009", "name": "Method / Procedure", "entry_kind": "entity", "purpose": "Describe a reusable codified way of working, its governed editions, applicability, evidence and scoped adoption.", "scope_statement": "One identifiable instruction work, classified as method, procedure or a linked combination, with edition-specific content and adoption declarations. A method can be explanatory rather than sequential. This is a proposed information model, not an execution engine or a universal assurance standard.", "in_scope": [ "Stable instruction-work identity, purpose and reasoning", "Edition-specific instructions, dependencies, applicability and prerequisite declarations", "Review evidence references, normative mappings and qualified claims", "Publication, change, withdrawal, scoped adoption and controlled representations" ], "out_of_scope": [ "Process scheduling, runtime control flow and actual task execution", "Practitioner credential issuance, competence assessment and authorization enforcement", "External standard, organization, document and audit master lifecycles", "Automatic safety approval, conformity certification or legal authorization", "Operational details for weapons, detention or controlled items; only policy-level restrictions and specialist references are allowed" ], "boundary_notes": [ { "neighbor": "WM-ACT-003", "distinction": "Process definitions own operational flow, scheduling, resource binding and execution context. The sole registry relation is an incoming candidate REFERENCE: a released process definition pins an adopted immutable instruction edition. This model owns instruction publication and scoped adoption; backlinks are derived.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "neighbor": "WM-ACT-006", "distinction": "Task instances own assignment, actual performance and completion. A prescribed step is not an executed work item.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "neighbor": "WM-REC-001", "distinction": "Document and record masters own generic carriers and record controls; here the subject is the codified instruction work and its edition semantics.", "source_refs": [ "SRC-004", "SRC-005" ] }, { "neighbor": "WM-REC-005", "distinction": "Standard artifacts own the referenced norm and version; this model holds clause references and qualified alignment claims, not the norm lifecycle.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "WM-ACT-001 and WM-PER-009", "distinction": "Capability and competence definitions remain separate masters; only method-specific prerequisite references and thresholds belong here.", "source_refs": [ "SRC-002" ] }, { "neighbor": "WM-ORG-001", "distinction": "Authors, adopters and reviewers are external party references; their organizational structures and identity lifecycles remain external.", "source_refs": [ "SRC-003", "SRC-007" ] }, { "neighbor": "WM-ACT-033", "distinction": "Reviews and inspections remain external activities; this model binds their evidence to the edition and local release decision.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "WM-XCT-038 and WM-XCT-004", "distinction": "Policy evaluation and access audit are referenced services; recording an external decision does not implement evaluation, enforcement or audit trails.", "source_refs": [ "SRC-007", "SRC-003" ] }, { "neighbor": "WM-XCT-035", "distinction": "Retention rules and disposition execution remain externally governed. This model records policy and disposition references for its own content.", "source_refs": [ "SRC-001", "SRC-004" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Guidance for Preparing Standard Operating Procedures (SOPs)", "organization": "United States Environmental Protection Agency", "url": "https://www.epa.gov/sites/default/files/2015-06/documents/g6-final.pdf", "version_or_date": "EPA/600/B-07/001, QA/G-6, April 2007; historical guidance, currency not established", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:03:34Z", "relevance": "Sections 1-4 inform scope, instructions, checks, approval and document control. Environmental quality-system guidance is an example, not a universal mandate." }, { "id": "SRC-002", "title": "Software & Systems Process Engineering Meta-Model Specification", "organization": "Object Management Group", "url": "https://www.omg.org/spec/SPEM/2.0/PDF", "version_or_date": "SPEM 2.0, April 2008, formal/2008-04-01", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:03:34Z", "relevance": "Sections 6.3.1, 12.6-12.10, 13.7 and 14 inform reusable method content, roles, steps, typed work products and process-specific use. Generalization outside software is a local design choice." }, { "id": "SRC-003", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/2013/REC-prov-o-20130430/", "version_or_date": "Recommendation, 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:03:34Z", "relevance": "Plan, Entity, Activity, Association, hadPlan, attribution and derivation support distinguishing instruction resources from evidence of their use." }, { "id": "SRC-004", "title": "DCMI Metadata Terms", "organization": "Dublin Core Metadata Initiative", "url": "https://www.dublincore.org/specifications/dublin-core/dcmi-terms/", "version_or_date": "2020-01-20 issue shown on retrieved page", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:03:34Z", "relevance": "identifier, hasVersion, isFormatOf, language, rights, references and conformsTo inform metadata alignment; vocabulary terms are not certificates." }, { "id": "SRC-005", "title": "Data on the Web Best Practices", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/2017/REC-dwbp-20170131/", "version_or_date": "Recommendation, 2017-01-31", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:03:34Z", "relevance": "Best Practices 7-11 inform version indicators, histories and persistent identification of series and versions; application to instruction publications is proposed." }, { "id": "SRC-006", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002, sections 4-5; later updates not assessed", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:03:34Z", "relevance": "Section 5.6 provides timestamp syntax with seconds and offsets. Edition validity intervals and date-only precision remain separate local semantics." }, { "id": "SRC-007", "title": "ODRL Information Model 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/2018/REC-odrl-model-20180215/", "version_or_date": "Recommendation, 2018-02-15", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:03:34Z", "relevance": "Policy, Asset, Party, Permission, Prohibition, Duty and profiles inform rights references for instruction access and distribution. This model does not implement a rights evaluator." } ], "structure": { "bundles": [ { "id": "bundle-identity", "name": "Identity and intent", "description": "Identify the instruction work and the reason for its existence.", "rationale": "Proposed grouping of related instruction-work concerns. Cited sources motivate the concerns; the grouping and controls are local design, not a claim of source-mandated structure.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ], "layers": [ { "id": "layer-designation", "name": "Work and edition identity", "description": "Keep the reusable work, its immutable edition and its rendering separately addressable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-designation", "name": "Work and edition identity", "description": "Keep the reusable work, its immutable edition and its rendering separately addressable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "designation-q01", "text": "Which authoritative identifier distinguishes this instruction work from its editions and renderings?", "kind": "identity", "answer_data": [ "work_master_id", "edition_master_id", "rendering_ref", "namespace" ] }, { "id": "designation-q02", "text": "Is this resource a reasoned method, a detailed procedure, or a separately identified combination?", "kind": "classification", "answer_data": [ "resource_kind", "classification_basis", "related_work_refs" ] }, { "id": "designation-q03", "text": "Who is accountable for the work and who may maintain its editions?", "kind": "ownership", "answer_data": [ "accountable_party_ref", "maintainer_ref", "mandate_evidence_ref" ] }, { "id": "designation-q04", "text": "Which evidence establishes the received edition and its declared author?", "kind": "provenance", "answer_data": [ "source_locator", "issuer_ref", "receipt_time", "digest", "authenticity_status" ] } ], "data_elements": [ { "id": "designation-data-work-key", "name": "Work key", "description": "Candidate work key for work and edition identity; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "designation-data-edition-key", "name": "Edition key", "description": "Candidate edition key for work and edition identity; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "designation-data-identity-evidence", "name": "Identity evidence", "description": "Candidate identity evidence for work and edition identity; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "designation-artifact", "name": "Designation record", "description": "Candidate evidence artifact for work and edition identity, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-intent", "name": "Purpose and reasoning", "description": "Describe the intended result and explanatory basis without treating a claim of usefulness as a measured result.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "finding-intent", "name": "Purpose and reasoning", "description": "Describe the intended result and explanatory basis without treating a claim of usefulness as a measured result.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "intent-q01", "text": "What class of problem does the work address?", "kind": "definition", "answer_data": [ "problem_statement", "intended_outcome", "audience_ref" ] }, { "id": "intent-q02", "text": "What reasoning or evidence supports the proposed approach?", "kind": "evidence", "answer_data": [ "rationale", "evidence_refs", "evidence_limits" ] }, { "id": "intent-q03", "text": "Which procedures realize this method and which methods does this procedure claim to realize?", "kind": "relationship", "answer_data": [ "typed_work_links", "pinned_editions", "unresolved_links" ] }, { "id": "intent-q04", "text": "Which claimed benefits remain untested or contested?", "kind": "quality", "answer_data": [ "benefit_claim", "assessment_ref", "confidence", "contrary_evidence_ref" ] } ], "data_elements": [ { "id": "intent-data-purpose", "name": "Purpose", "description": "Candidate purpose for purpose and reasoning; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "intent-data-rationale", "name": "Rationale", "description": "Candidate rationale for purpose and reasoning; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "intent-data-realizations", "name": "Realization links", "description": "Candidate realization links for purpose and reasoning; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "intent-artifact", "name": "Method rationale", "description": "Candidate evidence artifact for purpose and reasoning, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-codification", "name": "Codified instructions", "description": "Describe intended work at instruction level while leaving operational scheduling and execution to consumers.", "rationale": "Proposed grouping of related instruction-work concerns. Cited sources motivate the concerns; the grouping and controls are local design, not a claim of source-mandated structure.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005" ], "layers": [ { "id": "layer-steps", "name": "Instruction content and checks", "description": "Represent stable instruction sections, intended outcomes and check points. A method may be explanatory and have no step sequence.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "finding-steps", "name": "Instruction content and checks", "description": "Represent stable instruction sections, intended outcomes and check points. A method may be explanatory and have no step sequence.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "steps-q01", "text": "Which stable sections or steps constitute this edition?", "kind": "composition", "answer_data": [ "step_ids", "section_refs", "instruction_text", "explanatory_only_reason" ] }, { "id": "steps-q02", "text": "What ordering or conditional interpretation is prescribed between these instructions?", "kind": "process", "answer_data": [ "precedence_constraints", "condition_text", "optionality", "ambiguity_status" ] }, { "id": "steps-q03", "text": "What types of input and expected output are declared for each instruction?", "kind": "requirement", "answer_data": [ "step_id", "input_type_refs", "output_type_refs", "requiredness" ] }, { "id": "steps-q04", "text": "Which instructions are protected from omission or alteration under the adoption policy?", "kind": "constraint", "answer_data": [ "protected_step_refs", "hold_point_rules", "authority_ref", "rationale" ] } ], "data_elements": [ { "id": "steps-data-instructions", "name": "Instruction definitions", "description": "Candidate instruction definitions for instruction content and checks; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "steps-data-ordering", "name": "Instruction ordering", "description": "Candidate instruction ordering for instruction content and checks; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "steps-data-work-types", "name": "Input and output types", "description": "Candidate input and output types for instruction content and checks; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "steps-artifact", "name": "Controlled instruction text", "description": "Candidate evidence artifact for instruction content and checks, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-dependencies", "name": "Reusable content dependencies", "description": "Resolve referenced procedures, templates and definitions to explicit versions without absorbing their ownership.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-dependencies", "name": "Reusable content dependencies", "description": "Resolve referenced procedures, templates and definitions to explicit versions without absorbing their ownership.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ], "questions": [ { "id": "dependencies-q01", "text": "Which external instruction or template editions does this work require?", "kind": "relationship", "answer_data": [ "dependency_ref", "edition_pin", "dependency_kind", "requiredness" ] }, { "id": "dependencies-q02", "text": "Which dependency mapping preserves section references and which information is lost?", "kind": "interoperability", "answer_data": [ "binding_profile", "source_section", "target_section", "loss_note" ] }, { "id": "dependencies-q03", "text": "What is the declared response when a required dependency is unavailable or contradictory?", "kind": "exception", "answer_data": [ "dependency_issue", "blocked_scope", "escalation_ref", "authorized_disposition" ] }, { "id": "dependencies-q04", "text": "Does the dependency graph contain an unresolved cycle or an unpinned mandatory reference?", "kind": "validation", "answer_data": [ "graph_check_result", "cycle_path", "unresolved_refs", "checked_revision" ] } ], "data_elements": [ { "id": "dependencies-data-dependencies", "name": "Dependency references", "description": "Candidate dependency references for reusable content dependencies; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "dependencies-data-mappings", "name": "Mapping declarations", "description": "Candidate mapping declarations for reusable content dependencies; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "dependencies-data-resolution", "name": "Resolution evidence", "description": "Candidate resolution evidence for reusable content dependencies; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "dependencies-artifact", "name": "Dependency manifest", "description": "Candidate evidence artifact for reusable content dependencies, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-applicability", "name": "Applicability and prerequisites", "description": "State the conditions and practitioner requirements needed to interpret a procedure responsibly.", "rationale": "Proposed grouping of related instruction-work concerns. Cited sources motivate the concerns; the grouping and controls are local design, not a claim of source-mandated structure.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "layers": [ { "id": "layer-conditions", "name": "Scope and operating limits", "description": "Record declared applicability and exclusions. No procedure is approved for a particular use merely because its text is available.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "finding-conditions", "name": "Scope and operating limits", "description": "Record declared applicability and exclusions. No procedure is approved for a particular use merely because its text is available.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "conditions-q01", "text": "Which settings, domains or locations are included in the declared scope?", "kind": "spatial", "answer_data": [ "domain_refs", "setting_constraints", "location_scope", "scope_basis" ] }, { "id": "conditions-q02", "text": "Which entry conditions or exclusions limit use of this edition?", "kind": "constraint", "answer_data": [ "preconditions", "exclusions", "unknown_conditions", "verification_owner_ref" ] }, { "id": "conditions-q03", "text": "Which quantities constrain applicability and how are their units and tolerances defined?", "kind": "measurement", "answer_data": [ "parameter_id", "unit", "threshold", "tolerance", "method_ref", "not_applicable_reason" ] }, { "id": "conditions-q04", "text": "Which hazard classifications require a specialist policy before the instructions may be applied?", "kind": "security", "answer_data": [ "hazard_class", "specialist_policy_ref", "disclosure_class", "escalation_route" ] } ], "data_elements": [ { "id": "conditions-data-scope", "name": "Scope declaration", "description": "Candidate scope declaration for scope and operating limits; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "conditions-data-limits", "name": "Applicability limits", "description": "Candidate applicability limits for scope and operating limits; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "conditions-data-hazards", "name": "Hazard policy references", "description": "Candidate hazard policy references for scope and operating limits; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "conditions-artifact", "name": "Applicability statement", "description": "Candidate evidence artifact for scope and operating limits, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-competence", "name": "Role and competence requirements", "description": "Declare required capabilities and authorization references without certifying any practitioner.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "finding-competence", "name": "Role and competence requirements", "description": "Declare required capabilities and authorization references without certifying any practitioner.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "competence-q01", "text": "Which capabilities or competence levels does each instruction role require?", "kind": "requirement", "answer_data": [ "role_ref", "capability_ref", "level", "applicability_basis" ] }, { "id": "competence-q02", "text": "Which authorization is required in addition to competence?", "kind": "authority", "answer_data": [ "role_ref", "authorization_policy_ref", "permitted_scope", "expiry_rule" ] }, { "id": "competence-q03", "text": "What kind of external evidence can demonstrate each prerequisite?", "kind": "evidence", "answer_data": [ "requirement_ref", "evidence_type", "issuer_criteria", "freshness_rule" ] }, { "id": "competence-q04", "text": "How should an adopter record an unmet or unknown prerequisite?", "kind": "exception", "answer_data": [ "unmet_requirement", "use_restriction", "escalation_ref", "reassessment_trigger" ] } ], "data_elements": [ { "id": "competence-data-roles", "name": "Instruction role requirements", "description": "Candidate instruction role requirements for role and competence requirements; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "competence-data-prerequisites", "name": "Competence prerequisites", "description": "Candidate competence prerequisites for role and competence requirements; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "competence-data-authorization", "name": "Authorization references", "description": "Candidate authorization references for role and competence requirements; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "competence-artifact", "name": "Prerequisite matrix", "description": "Candidate evidence artifact for role and competence requirements, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Evidence and alignment", "description": "Distinguish acceptance criteria, test evidence and external conformity claims.", "rationale": "Proposed grouping of related instruction-work concerns. Cited sources motivate the concerns; the grouping and controls are local design, not a claim of source-mandated structure.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "layers": [ { "id": "layer-acceptance", "name": "Acceptance and review evidence", "description": "Associate edition-specific acceptance expectations and review evidence; actual runs and inspections remain external records.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "finding-acceptance", "name": "Acceptance and review evidence", "description": "Associate edition-specific acceptance expectations and review evidence; actual runs and inspections remain external records.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "acceptance-q01", "text": "What evidence would show that the documented instructions are interpretable and fit for the stated scope?", "kind": "validation", "answer_data": [ "acceptance_criteria", "trial_design_ref", "reviewer_qualification", "scope_limit" ] }, { "id": "acceptance-q02", "text": "Which review result supports or challenges this exact edition?", "kind": "quality", "answer_data": [ "review_record_ref", "edition_digest", "finding_refs", "unresolved_issues" ] }, { "id": "acceptance-q03", "text": "What metric and sampling assumptions apply to a claimed performance result?", "kind": "measurement", "answer_data": [ "metric_definition_ref", "unit", "conditions", "uncertainty", "evidence_ref" ] }, { "id": "acceptance-q04", "text": "Who disposes of unresolved review findings before local release?", "kind": "decision", "answer_data": [ "decision_authority_ref", "disposition_ref", "open_issue", "release_restriction" ] } ], "data_elements": [ { "id": "acceptance-data-criteria", "name": "Acceptance criteria", "description": "Candidate acceptance criteria for acceptance and review evidence; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "acceptance-data-review-evidence", "name": "Review evidence links", "description": "Candidate review evidence links for acceptance and review evidence; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "acceptance-data-dispositions", "name": "Issue dispositions", "description": "Candidate issue dispositions for acceptance and review evidence; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "acceptance-artifact", "name": "Edition review dossier", "description": "Candidate evidence artifact for acceptance and review evidence, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-norms", "name": "Normative references and claims", "description": "Keep references, implementation intentions and evidenced conformity distinct and edition-specific.", "source_refs": [ "SRC-001", "SRC-004", "SRC-003" ], "findings": [ { "id": "finding-norms", "name": "Normative references and claims", "description": "Keep references, implementation intentions and evidenced conformity distinct and edition-specific.", "source_refs": [ "SRC-001", "SRC-004", "SRC-003" ], "questions": [ { "id": "norms-q01", "text": "Which external standard editions and clauses are cited or claimed to be implemented?", "kind": "relationship", "answer_data": [ "standard_ref", "version", "clause", "relationship_kind" ] }, { "id": "norms-q02", "text": "What evidence supports each conformity assertion and who made it?", "kind": "evidence", "answer_data": [ "claim_id", "claimant_ref", "evidence_ref", "assessed_scope", "assurance_kind" ] }, { "id": "norms-q03", "text": "Which exclusions, conflicts or approved deviations qualify the asserted alignment?", "kind": "exception", "answer_data": [ "claim_id", "exclusion", "conflicting_clause", "disposition_ref" ] }, { "id": "norms-q04", "text": "When must a changed external norm trigger review of the claim?", "kind": "temporal", "answer_data": [ "dependency_change_ref", "review_trigger", "responsible_role", "review_status" ] } ], "data_elements": [ { "id": "norms-data-norm-links", "name": "Norm references", "description": "Candidate norm references for normative references and claims; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-003" ] }, { "id": "norms-data-claims", "name": "Conformity assertions", "description": "Candidate conformity assertions for normative references and claims; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-003" ] }, { "id": "norms-data-qualifications", "name": "Claim qualifications", "description": "Candidate claim qualifications for normative references and claims; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-003" ] } ], "artifacts": [ { "id": "norms-artifact", "name": "Clause alignment register", "description": "Candidate evidence artifact for normative references and claims, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-publication", "name": "Edition publication and change", "description": "Govern released content identity, availability and later corrections without changing historical references.", "rationale": "Proposed grouping of related instruction-work concerns. Cited sources motivate the concerns; the grouping and controls are local design, not a claim of source-mandated structure.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-release", "name": "Edition release and status", "description": "Separate publication, effectiveness and adoption. Status is qualified by issuer and scope, not a universal current flag.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-release", "name": "Edition release and status", "description": "Separate publication, effectiveness and adoption. Status is qualified by issuer and scope, not a universal current flag.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "release-q01", "text": "What is this edition status and which recorded authority supports it?", "kind": "lifecycle", "answer_data": [ "edition_status", "status_scope", "authorization_ref", "status_record_ref" ] }, { "id": "release-q02", "text": "What are the distinct release, effective and recorded times for the edition?", "kind": "temporal", "answer_data": [ "release_time", "effective_interval", "recorded_time", "date_precision", "timezone_basis" ] }, { "id": "release-q03", "text": "Which approved content digest and dependency manifest define the released edition?", "kind": "validation", "answer_data": [ "edition_id", "content_digest", "manifest_ref", "approval_ref", "completeness_check" ] }, { "id": "release-q04", "text": "Which controlled locator provides this exact edition to an authorized audience?", "kind": "access", "answer_data": [ "edition_locator", "access_policy_ref", "distribution_state", "audience_scope" ] } ], "data_elements": [ { "id": "release-data-release-state", "name": "Release state", "description": "Candidate release state for edition release and status; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "release-data-release-basis", "name": "Release basis", "description": "Candidate release basis for edition release and status; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "release-data-edition-times", "name": "Edition times", "description": "Candidate edition times for edition release and status; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "release-artifact", "name": "Release declaration", "description": "Candidate evidence artifact for edition release and status, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-change", "name": "Revision, replacement and withdrawal", "description": "Preserve revision lineage and scoped withdrawal reasons. Parallel editions, translations and variants need explicit relations.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-change", "name": "Revision, replacement and withdrawal", "description": "Preserve revision lineage and scoped withdrawal reasons. Parallel editions, translations and variants need explicit relations.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "change-q01", "text": "Which earlier editions are revised, replaced or branched by this edition?", "kind": "lifecycle", "answer_data": [ "predecessor_refs", "relation_kind", "changed_sections", "branch_scope" ] }, { "id": "change-q02", "text": "Does an erratum change normative meaning or only a rendering?", "kind": "quality", "answer_data": [ "erratum_ref", "impact_assessment", "semantic_change", "new_revision_ref" ] }, { "id": "change-q03", "text": "What withdrawal or correction notice was issued and which editions does it affect?", "kind": "event", "answer_data": [ "notice_ref", "affected_editions", "stated_reason", "effective_time", "delivery_evidence_ref" ] }, { "id": "change-q04", "text": "Which historical content may be retained or removed under the governing policy?", "kind": "retention", "answer_data": [ "retention_policy_ref", "hold_ref", "disposition_authority", "tombstone_requirements" ] } ], "data_elements": [ { "id": "change-data-lineage", "name": "Edition lineage", "description": "Candidate edition lineage for revision, replacement and withdrawal; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "change-data-change-records", "name": "Change records", "description": "Candidate change records for revision, replacement and withdrawal; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "change-data-withdrawals", "name": "Withdrawal notices", "description": "Candidate withdrawal notices for revision, replacement and withdrawal; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "change-artifact", "name": "Change and withdrawal record", "description": "Candidate evidence artifact for revision, replacement and withdrawal, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-adoption", "name": "Adoption and usable distribution", "description": "Record scoped uptake and representations while preserving edition, rights and external process boundaries.", "rationale": "Proposed grouping of related instruction-work concerns. Cited sources motivate the concerns; the grouping and controls are local design, not a claim of source-mandated structure.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-uptake", "name": "Scoped adoption and tailoring", "description": "An adopter declares uptake of a pinned edition. Adoption is neither proof of execution nor a conformity certificate.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "findings": [ { "id": "finding-uptake", "name": "Scoped adoption and tailoring", "description": "An adopter declares uptake of a pinned edition. Adoption is neither proof of execution nor a conformity certificate.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "uptake-q01", "text": "Which adopter is accountable for this adoption record and its scope?", "kind": "ownership", "answer_data": [ "adoption_id", "adopter_ref", "scope", "accountable_role_ref" ] }, { "id": "uptake-q02", "text": "Which exact edition and local variant apply during the adoption interval?", "kind": "temporal", "answer_data": [ "edition_ref", "variant_ref", "effective_from", "effective_until", "recorded_time" ] }, { "id": "uptake-q03", "text": "Which tailoring decisions are authorized and how do they differ from the source edition?", "kind": "authority", "answer_data": [ "tailoring_ref", "affected_sections", "authority_ref", "approval_evidence", "unresolved_changes" ] }, { "id": "uptake-q04", "text": "Which process definitions reference this adoption and where are their master records?", "kind": "relationship", "answer_data": [ "process_ref", "process_edition", "process_owned_link_ref", "observation_time" ] } ], "data_elements": [ { "id": "uptake-data-adoptions", "name": "Adoption declarations", "description": "Candidate adoption declarations for scoped adoption and tailoring; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "uptake-data-tailoring", "name": "Tailoring references", "description": "Candidate tailoring references for scoped adoption and tailoring; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "uptake-data-process-uses", "name": "Process backlinks", "description": "Candidate process backlinks for scoped adoption and tailoring; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "uptake-artifact", "name": "Adoption declaration", "description": "Candidate evidence artifact for scoped adoption and tailoring, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-distribution", "name": "Representations, rights and feedback", "description": "Provide controlled renderings and feedback paths without treating a summary or translation as an interchangeable authority.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ], "findings": [ { "id": "finding-distribution", "name": "Representations, rights and feedback", "description": "Provide controlled renderings and feedback paths without treating a summary or translation as an interchangeable authority.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ], "questions": [ { "id": "distribution-q01", "text": "How does each translation, handbook or checklist map to its authoritative edition?", "kind": "interoperability", "answer_data": [ "rendering_id", "edition_ref", "language", "transformation", "omitted_sections", "review_status" ] }, { "id": "distribution-q02", "text": "What rights permit reading, copying, adapting or redistributing this representation?", "kind": "access", "answer_data": [ "rights_policy_ref", "action", "audience", "conditions", "external_decision_ref" ] }, { "id": "distribution-q03", "text": "Which personal or restricted details must be excluded from a distributed view?", "kind": "privacy", "answer_data": [ "view_scope", "redaction_policy_ref", "sensitive_fields", "disclosure_decision_ref" ] }, { "id": "distribution-q04", "text": "Where is feedback about ambiguity or obsolete copies recorded and who reviews it?", "kind": "provenance", "answer_data": [ "feedback_ref", "observed_edition", "issue_kind", "review_owner_ref", "disposition_ref" ] } ], "data_elements": [ { "id": "distribution-data-representations", "name": "Representation links", "description": "Candidate representation links for representations, rights and feedback; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "distribution-data-rights", "name": "Rights bindings", "description": "Candidate rights bindings for representations, rights and feedback; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "distribution-data-feedback", "name": "Feedback references", "description": "Candidate feedback references for representations, rights and feedback; nested shape and vocabulary require an adopter profile. Unknown is distinct from absent or not applicable.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "distribution-artifact", "name": "Distribution manifest", "description": "Candidate evidence artifact for representations, rights and feedback, bound to its work, edition and responsible record owner. Its presence alone does not prove the asserted facts.", "media_or_form": [ "Controlled structured record", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed global IRI second; otherwise owner-assigned UUID or ULID. Record edition and revision separately; timestamps and hashes are metadata, not identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-register-work", "name": "Register an instruction work", "description": "Proposed local operation, not implemented. Create a local work record with classified purpose and resolved ownership.", "inputs": [ "proposed identity", "purpose", "party master refs", "actor and expected record revision" ], "outputs": [ "work record or collision report" ], "preconditions": [ "Identity resolver and creation policy approve the namespace", "Actor has scoped permission; optimistic concurrency matches; unknown authority causes refusal" ], "effects": [ "Creates a draft local record; does not publish or approve use", "Append provenance under the adopting retention policy; return a conflict without writes on a stale revision" ], "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "function-revise-edition", "name": "Propose an edition revision", "description": "Proposed local operation, not implemented. Record proposed content changes against an exact edition without mutating a released payload.", "inputs": [ "base edition and digest", "patch", "change rationale", "actor and expected record revision" ], "outputs": [ "draft revision and change report or refusal" ], "preconditions": [ "Base edition resolves and rights permit adaptation", "Actor has scoped permission; optimistic concurrency matches; unknown authority causes refusal" ], "effects": [ "Creates a new draft revision; leaves past editions and adoptions unchanged", "Append provenance under the adopting retention policy; return a conflict without writes on a stale revision" ], "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "function-check-readiness", "name": "Check declared release readiness", "description": "Proposed local operation, not implemented. Inspect required evidence links and unresolved references for a selected adopter profile; do not decide practical fitness.", "inputs": [ "draft edition", "profile", "approval and review refs", "actor and expected record revision" ], "outputs": [ "readiness report with gaps or indeterminate result" ], "preconditions": [ "Profile and dependency versions are pinned and readable", "Actor has scoped permission; optimistic concurrency matches; unknown authority causes refusal" ], "effects": [ "Records local structural checks; no release, certification or external evaluation", "Append provenance under the adopting retention policy; return a conflict without writes on a stale revision" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "function-record-release", "name": "Record an authorized release", "description": "Proposed local operation, not implemented. Bind an externally authorized release declaration to the exact reviewed edition.", "inputs": [ "edition digest", "release authorization ref", "effective scope and time", "actor and expected record revision" ], "outputs": [ "release record or refusal" ], "preconditions": [ "Required readiness checks pass and issuer authority is evidenced", "Actor has scoped permission; optimistic concurrency matches; unknown authority causes refusal" ], "effects": [ "Records the local release state; performs no distribution or process activation", "Append provenance under the adopting retention policy; return a conflict without writes on a stale revision" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "function-record-adoption", "name": "Record scoped adoption", "description": "Proposed local operation, not implemented. Bind an adopter declaration and optional approved variant to the adopted edition.", "inputs": [ "adopter ref", "edition pin", "adoption interval", "tailoring evidence", "actor and expected record revision" ], "outputs": [ "adoption record or unresolved-evidence report" ], "preconditions": [ "Adopter authority and content rights are evidenced; variant resolves", "Actor has scoped permission; optimistic concurrency matches; unknown authority causes refusal" ], "effects": [ "Records declared uptake; does not certify compliance, execute work or alter process masters", "Append provenance under the adopting retention policy; return a conflict without writes on a stale revision" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007" ] }, { "id": "function-record-withdrawal", "name": "Record withdrawal or supersession", "description": "Proposed local operation, not implemented. Associate an authorized notice with affected editions and known adoption references.", "inputs": [ "notice ref", "affected edition ids", "reason", "authority ref", "actor and expected record revision" ], "outputs": [ "status change record and affected-reference report or refusal" ], "preconditions": [ "Notice is attributable and affected editions resolve", "Actor has scoped permission; optimistic concurrency matches; unknown authority causes refusal" ], "effects": [ "Appends local status evidence; does not deliver notifications, revoke external access or delete historical content", "Append provenance under the adopting retention policy; return a conflict without writes on a stale revision" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "composition": [ { "target": "WM-ACT-003", "relation": "REFERENCE", "purpose": "Read-only derived backlink to the incoming candidate process-owned REFERENCE. Preserve the process-side edition pin; this is not a newly asserted outgoing registry edge.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "WM-ACT-006", "relation": "REFERENCE", "purpose": "Proposed optional binding, not an existing registry edge. Task instances own assignment, actual performance and completion. A prescribed step is not an executed work item.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "WM-REC-001", "relation": "REFERENCE", "purpose": "Proposed optional binding, not an existing registry edge. Document and record masters own generic carriers and record controls; here the subject is the codified instruction work and its edition semantics.", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] }, { "target": "WM-REC-005", "relation": "REFERENCE", "purpose": "Proposed optional binding, not an existing registry edge. Standard artifacts own the referenced norm and version; this model holds clause references and qualified alignment claims, not the norm lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Proposed optional binding, not an existing registry edge. Authors, adopters and reviewers are external party references; their organizational structures and identity lifecycles remain external.", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "target": "WM-ACT-033", "relation": "REFERENCE", "purpose": "Proposed optional binding, not an existing registry edge. Reviews and inspections remain external activities; this model binds their evidence to the edition and local release decision.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-XCT-035", "relation": "REFERENCE", "purpose": "Proposed optional binding, not an existing registry edge. Retention rules and disposition execution remain externally governed. This model records policy and disposition references for its own content.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-ACT-001", "relation": "REFERENCE", "purpose": "Proposed optional binding, not an existing registry edge. Optional proposed capability prerequisite master binding; no capability evaluation is owned here.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-PER-009", "relation": "REFERENCE", "purpose": "Proposed optional binding, not an existing registry edge. Optional proposed competence definition master binding; no person certification is owned here.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-XCT-038", "relation": "REFERENCE", "purpose": "Proposed optional binding, not an existing registry edge. Optional external policy decision reference; no evaluator or enforcement engine is implemented.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "WM-XCT-004", "relation": "REFERENCE", "purpose": "Proposed optional binding, not an existing registry edge. Optional access-audit evidence reference; audit trail semantics remain external.", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "target": "https://www.omg.org/spec/SPEM/2.0/", "relation": "ALIGN", "purpose": "Conceptual alignment with reusable method content, qualifications and process use; no metamodel conformance claimed.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "https://www.w3.org/TR/2013/REC-prov-o-20130430/", "relation": "ALIGN", "purpose": "Conceptual Plan and provenance alignment; no complete RDF binding is supplied.", "required": false, "source_refs": [ "SRC-003" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Use generic accountable author, maintainer, adopter and reviewer roles resolved through authoritative party identifiers.", "Declare namespace, master-system identity and split ownership of instruction editions and adoption records.", "Supply local release, access, retention and specialist safety policies with explicit authority and effective scope.", "Pin model and vocabulary versions; record unknown bindings rather than inventing a provider or owner." ], "namespace_guidance": "Separate work, edition, section, adoption and rendering namespaces. Do not use dates or display names as primary keys. Global identifiers are governed by the adopting Dimension.", "registry_links": [ "vr.wm-act-009", "WM-ACT-003", "WM-REC-005", "WM-PER-009", "WM-XCT-035" ] }, "canon_and_patch": { "canonicalization_rules": [ "Normalize identifier syntax and language metadata without changing instructional meaning.", "Keep authoritative content distinct from extracts and translations; exact edition pins resolve to immutable content manifests." ], "patch_rules": [ "Draft patches require an expected revision, actor, reason and changed section identifiers. Never overwrite released normative content; issue an attributable revision.", "A rendering correction may preserve the edition only after a recorded no-semantic-change assessment; retain the previous rendering identity." ], "compatibility_rules": [ "Changing mandatory steps, prerequisites, outputs or applicability requires a migration assessment and adopter review.", "Parallel editions and branches may coexist. No automatic upgrade of process-side pins or adoption records; translations are equivalent only with qualified evidence." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "Adopting Dimension UUID or ULID" ], "timestamp_rule": "Use RFC 3339 with seconds and an explicit offset or Z for instants. Distinguish release, effective, event and observation/ingestion times. Preserve a date-only source as a date with precision metadata; do not invent midnight or an offset.", "serial_naming_rule": "Use stable artifact identifiers with separate revision and edition metadata. Human names may contain sequence numbers but neither dates nor hashes replace authoritative identity.", "integrity_rule": "Bind each controlled artifact to the work, edition, revision and digest algorithm. Digests detect byte changes, not author identity, instruction safety or conformity; require separate authority evidence." }, "policies": [ "All content is a reviewable research draft under a single-provider waiver; local schema validity does not certify an instance or method.", "Rights to read, adapt and distribute are distinct. Resolve applicable policy decisions externally; do not infer grants from a public locator.", "Dangerous applications stay at policy level with specialist authority and restricted disclosure; never generate operational detail from missing steps.", "Limit personal data in authorship, approval and adoption evidence; retain only justified scoped evidence and apply external retention policy.", "Preserve unknown, absent, not applicable, contested and confirmed states distinctly. Conflicting or missing authority blocks local release and adoption recording as confirmed." ], "crud": { "read": [ "Resolve the requested work and exact edition, audience and rights; show status scope, omissions, source limits and current adoption pin." ], "create": [ "Allocate a work or adoption ID only under its accountable owner namespace; record evidence and separate edition-specific content." ], "update": [ "Use expected-revision checks and attributable patches. Released meaning changes need a new revision; no process or task master is changed." ], "delete": [ "Retire or withdraw local instruction records with authority and a resolvable minimal tombstone when lawful. Apply retention and hold rules before removing payloads; do not promise perpetual personal-data history.", "Referenced masters and deletion execution remain with their own owners and the adopting Dimension retention/disposition service; a local tombstone does not erase downstream copies." ] }, "roles": [ { "name": "Instruction author", "responsibilities": [ "Draft content, purpose and applicability with evidence." ] }, { "name": "Edition maintainer", "responsibilities": [ "Resolve versions, dependencies and change records without overriding author or adopter authority." ] }, { "name": "Release approver", "responsibilities": [ "Record an authorized release decision against exact content and unresolved issues." ] }, { "name": "Adoption steward", "responsibilities": [ "Maintain scoped adopter declarations and approved tailoring references." ] }, { "name": "Qualified reviewer", "responsibilities": [ "Review instruction quality and limits; preserve negative evidence." ] }, { "name": "Record custodian", "responsibilities": [ "Apply scoped access and retention decisions while preserving lawful provenance." ] } ], "access": { "default_rule": "Deny ungranted mutation and restricted content access; permission is resolved by the applicable external policy for the actor, action, purpose, edition and audience.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "A public metadata view does not confer rights to the full text or adaptations.", "Emergency access or tailoring requires a separately evidenced policy decision; the model grants no override." ], "audit_requirements": [ "Reference externally governed access audit evidence and local mutation provenance with actor, purpose, scope, time and decision reference.", "Keep sensitive approval evidence out of public projections; the audit reference itself may require access control." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read AGENTS.md and local owner policy.", "Read spec.yaml including provider waiver and publication holds.", "Resolve exact edition, adoption scope, neighbors and authority before interpreting content.", "Record unresolved questions; do not infer approval, execution or current applicability from publication." ] } }, "coverage": { "claim": "Source-grounded proposed structure for an identifiable reusable instruction work, its governed editions and scoped adoption. Selected environmental quality and software-method sources inform the design. A separate frozen local no-tools self-audit is complete; independent review, source currency, qualified adoption profiles and executable conformance remain holds. This is a noncanonical reviewable draft.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Work, edition and rendering identities are separate; generic entity masters remain delegated." }, { "dimension": "lifecycle", "status": "covered", "notes": "Draft, release, change, withdrawal and adoption are scoped and evidence-qualified." }, { "dimension": "relationships", "status": "covered", "notes": "The incoming process reference is retained with its ownership direction; other neighbor bindings are proposals." }, { "dimension": "temporal", "status": "covered", "notes": "Release, effectiveness, adoption and recorded times are distinct; no invented precision." }, { "dimension": "provenance", "status": "covered", "notes": "Attribution, edition digests, received evidence and contested claims stay distinct." }, { "dimension": "ownership", "status": "covered", "notes": "Author/maintainer and adopter have separate record responsibilities; only generic roles are assigned." }, { "dimension": "validation", "status": "covered", "notes": "Research structure is testable; practical fitness and conformity require separately scoped evidence." }, { "dimension": "access", "status": "covered", "notes": "Rights references and audience-specific renderings preserve external enforcement ownership." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Disposition policy and lawful tombstones qualify history; downstream erasure is not claimed." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual SPEM, PROV and metadata alignments exist; executable mappings and round-trip fixtures are deferred." }, { "dimension": "direct properties", "status": "covered", "notes": "Purpose, classification, language, applicability and edition status are intrinsic descriptive properties." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Received source, declared issuer, digest and authenticity status identify candidate content without certifying it." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Six proposed local record operations separate preconditions, effects and refusal from execution." }, { "dimension": "physical properties", "status": "not-applicable", "notes": "The instruction work is abstract; quantities describe applicability constraints or referenced resources, not its mass or dimensions." }, { "dimension": "hazards and failure modes", "status": "covered", "notes": "Stale pins, ambiguous steps, missing authority and restricted domains require visible unresolved states and policy escalation." } ], "known_omissions": [ "Independent external review is absent; Claude and Grok were skipped under the owner-authorized waiver.", "Direct source HTTP status, current authority, errata, licenses and complete claim verification remain open.", "Nested instance schemas, controlled status vocabularies, neighbor version pins and executable mappings need implementation and tests.", "Domain-specific safety, translation equivalence, competence evidence, release authority and retention rules require qualified adoption profiles." ], "conflicts": [], "regional_assumptions": [ "EPA guidance is a historical United States environmental quality-system example, not a globally binding rule. Its own five-year review statement prevents treating availability as current authority.", "SPEM addresses software and systems methods. Reuse in other domains is a proposed analogy requiring profile validation.", "Web vocabularies supply alignment terms, not proof of legal rights, safety or conformance." ], "adversarial_checks": [ "A method without ordered steps can still be represented; an unexplained empty procedure cannot be treated as usable.", "A latest locator never silently replaces a process or adoption edition pin.", "An adoption declaration cannot prove execution, competence, rights or conformity.", "A translation that changes a mandatory step is a qualified variant, not a silent rendering.", "A withdrawal does not erase historical provenance or automatically revoke all local adoptions." ] }, "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 is a persistent codified instruction work with separately identified editions and adoption declarations. It is not the act of performing work or a library aggregate. The registry standalone-mm classification is a catalogue-plane value. An explanatory method can lack ordered steps without absorbing operational process semantics." }, "decisions": [ { "concept": "Work, edition and rendering identity", "disposition": "accepted", "rationale": "Designation and release findings keep stable work identity, version identity and representation identity distinct. Candidate fields do not yet constitute a release-ready instance schema, but the declared boundary is coherent." }, { "concept": "Method versus procedure", "disposition": "qualified", "rationale": "The intent and instruction findings support both a reasoned approach and detailed instructions. Explanatory-only work can omit steps; an incomplete procedural draft must disclose the gap and cannot be inferred usable." }, { "concept": "Incoming process reference ownership", "disposition": "accepted with explicit direction", "rationale": "The registry relation is incoming and candidate. The model preserves process-side ownership of the edition pin and exposes only a derived backlink. All six local functions avoid process scheduling, execution and task completion." }, { "concept": "Instruction ordering and dependency graph", "disposition": "accepted as descriptive", "rationale": "Instruction ordering, conditions and typed inputs describe intended work; dependency checks inspect content references. They do not supply a runtime token model, execution state or resource scheduler." }, { "concept": "Applicability and prerequisite evidence", "disposition": "accepted with profile dependency", "rationale": "Settings, quantities and competence requirements are declarations. Actual competence assessment and permission decisions remain external. Unknown prerequisites cannot become implied approval to use the procedure." }, { "concept": "Hazard and protected-step treatment", "disposition": "limited to policy", "rationale": "The proposal records hazard classes, restricted disclosure, specialist references and authorized tailoring evidence. It contains no domain-specific dangerous operating instructions or automatic safety approval." }, { "concept": "Review and conformity assertions", "disposition": "evidence-qualified", "rationale": "Acceptance and norm findings ask for exact edition evidence, claimant, assessed scope, exceptions and unresolved issues. A vocabulary mapping, release declaration, digest or adoption record does not prove conformity or practical fitness." }, { "concept": "Currentness and temporal precision", "disposition": "qualified", "rationale": "Release, effectiveness, recorded time and adopter scope are separate. Date-only inputs retain their precision. A newer edition or latest locator never silently upgrades a pinned adoption or process definition." }, { "concept": "Revision, branches and translations", "disposition": "accepted", "rationale": "Released meaning changes require a new attributable revision, and rendering corrections need a no-semantic-change assessment. Parallel versions and typed predecessor links avoid inheriting the legacy one-to-one supersession assumption." }, { "concept": "Adoption and tailoring", "disposition": "separated from execution", "rationale": "Adopter responsibility and approved variant references are local context. Process-owned use remains external. Adoption can be recorded as a declaration without implying actual performance, credential validity, rights or third-party certification." }, { "concept": "Rights, disclosure and distribution", "disposition": "accepted with external enforcement", "rationale": "Distribution questions distinguish read, copy, adapt and redistribute actions. Rights evaluation, enforcement and access-audit semantics stay external; a public metadata locator does not grant full-text access." }, { "concept": "Retention and withdrawal", "disposition": "accepted with policy dependency", "rationale": "Withdrawal changes a scoped status rather than deleting downstream copies. Local history is qualified by retention, holds and lawful minimal tombstones, so immutable content identity does not require perpetual personal-data storage." }, { "concept": "Local operations and authority", "disposition": "proposed only", "rationale": "All six functions have inputs, evidence and scoped permission preconditions, effects and refusal behavior. Recording an externally authorized release or adoption is distinct from granting authority or taking external action." }, { "concept": "Legacy and supplement reconciliation", "disposition": "qualified and partly rejected", "rationale": "The frozen design admits source-supported concerns while rejecting inherited certification, wildcard imports, universal checklist comparisons and universal one-to-one lineage. Neither preparation input is counted as evidence." }, { "concept": "Source verification and generalization", "disposition": "held", "rationale": "Selected passages from seven primary sources support the concerns, but a browser opening is not full document review or an HTTP-status measurement. Historical EPA authority and software-to-general-method extrapolation remain explicit qualifications." }, { "concept": "Executable conformance and independent review", "disposition": "deferred", "rationale": "The valid research schema leaves nested fields, status vocabularies, pinned bindings and adversarial instance fixtures incomplete. This local Codex audit cannot replace independent review by a waived provider or certify an implementation." } ], "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 is incomplete. Direct HTTP was not attempted under the owner-reported sandbox restriction and no status was measured. Selected browser content is documented in source-review.md. The coordinator must run check_sources.py and review authority, versions, errata, licensing and claim support; the historical EPA document's current authority is not established.", "Domain, jurisdiction, safety, competence, translation equivalence, release and adoption authority, licensing, privacy and retention require qualified adopter profiles before operational use. Generalization from environmental and software-method sources is a proposal, not universal applicability or certification.", "Nested instance schemas, status vocabularies, pinned neighbor bindings, executable SPEM/PROV/metadata mappings, concurrency and lineage constraints, and adversarial instance fixtures remain incomplete. No runtime, round-trip fidelity or operational conformance is claimed.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Complete source retrieval observations and current authority, errata, license and claim review for all admitted sources, especially the historical environmental guidance.", "Develop qualified adoption profiles and fixtures for explanatory methods, parallel editions, stale process pins, unauthorized tailoring, translation changes, partial withdrawal, unknown authority and lawful disposal.", "Implement nested schemas and versioned neighbor mappings without transferring process execution, competence certification or rights evaluation into this model.", "Restore independent external review before any canonical or publishable-draft promotion." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }