# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T14:15:14Z", "synthesisSha256": "15088130f16b970811b224253c9e60c6c5bf668c495e414c798425ccd66bb598", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-012", "registryId": "vr.wm-act-012", "name": "Extraction Operation", "version": "0.3.0", "previousVersions": [ { "version": "0.2.0", "url": "https://ver.cy/models/world-k10-resource-extraction-operations/" } ], "entryKind": "entity", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.EXT" ], "tags": [ "extraction", "operation", "act.ext" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-012-extraction-operation/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-012", "model": { "registry_id": "vr.wm-act-012", "model_id": "WM-ACT-012", "name": "Extraction Operation", "entry_kind": "entity", "purpose": "Describe and inspect one bounded natural-resource extraction campaign through authority evidence, observed work, outputs, conditions and residual duties.", "scope_statement": "A persistent campaign record for mining, drilling, logging or fishing, including planned, incomplete, disputed and unauthorized episodes. The model represents evidence and local status; it neither controls physical extraction nor certifies legality or sustainability.", "in_scope": [ "Campaign identity, classification, boundary, footprint and actor references", "Applicable authority, plan, limit and condition bindings", "Execution intervals, output observations and downstream linkage", "Safety and environmental evidence links, reporting, cessation and residual-duty acceptance references" ], "out_of_scope": [ "Master rights, licences, resource or reserve estimation, site and equipment lifecycle", "Issuing permissions, operating machinery, emergency response, enforcement or legal determinations", "Aquaculture and cultivation cycles, downstream processing, sales or royalty accounting", "Executing restoration, releasing financial assurance or publishing private records" ], "boundary_notes": [ { "neighbor": "WM-ACT-002", "distinction": "Candidate reconciliation of legacy K2 EXTEND: a campaign can contain several acts and is not necessarily one atomic act. Pin act references; do not inherit an unverified schema.", "source_refs": [ "SRC-008" ] }, { "neighbor": "WM-ACT-010", "distinction": "Downstream production runs master processing and transformation; only output handoff references live here.", "source_refs": [ "SRC-005" ] }, { "neighbor": "WM-EAR-004", "distinction": "Mineral deposits and assessments are resource-owned; legacy P5 is not a site model. Only applicable mining or drilling resource references live here.", "source_refs": [ "SRC-004", "SRC-005" ] }, { "neighbor": "WM-BLT-008", "distinction": "Candidate managed site reference where applicable; mobile fishing operations may instead reference geographic areas. Site lifecycle is external.", "source_refs": [ "SRC-002", "SRC-005" ] }, { "neighbor": "WM-POL-014", "distinction": "Candidate legal rights and entitlement reference; physical extraction authority is separate from permission to read data.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "neighbor": "WM-XCT-001", "distinction": "Candidate stewardship binding for the record, distinct from title to land or natural resources; no generic ownership machinery duplicated.", "source_refs": [ "SRC-008" ] }, { "neighbor": "WM-XCT-002", "distinction": "Candidate data-access policy binding only. A legacy S2 data permission is not an extraction licence.", "source_refs": [ "SRC-008" ] }, { "neighbor": "https://www.w3.org/TR/prov-o/", "distinction": "Conceptual activity, entity, agent and derivation mapping only; executable mappings and conformance fixtures are deferred.", "source_refs": [ "SRC-008" ] }, { "neighbor": "Legacy K10 and unreviewed supplement", "distinction": "Reconcile as non-authoritative inputs. Reject universal commons tenure, mandatory quota or restoration, permit-plus-site identity, prevention of recording unauthorized activity and wildcard conformance. Campaign is a persistent entity, not necessarily one atomic act.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Code of Conduct for Responsible Fisheries", "organization": "Food and Agriculture Organization of the United Nations", "url": "https://www.fao.org/4/v9878e/v9878e00.htm", "version_or_date": "1995; selected Articles 7 and 8", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:12:58Z", "relevance": "Fishing authorization, effort, catch categories, monitoring and reporting; voluntary guidance, not a universal licence law." }, { "id": "SRC-002", "title": "Forest management planning", "organization": "Food and Agriculture Organization of the United Nations", "url": "https://www.fao.org/sustainable-forest-management-toolbox/modules/forest-management-planning/2/en?tabInx=1", "version_or_date": "Living SFM Toolbox module; credits report revision in 2017; reviewed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:12:58Z", "relevance": "Harvest planning, tenure, areas, yield limits and monitoring; selected module sections, no mandatory worldwide rotation or limit." }, { "id": "SRC-003", "title": "Mining and Minerals - Bonding", "organization": "Bureau of Land Management", "url": "https://www.blm.gov/programs/energy-and-minerals/mining-and-minerals/bonding", "version_or_date": "Undated public guidance; reviewed 2026-10-06; legal currency not established", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:12:58Z", "relevance": "US public-land surface-management example separating operation, reclamation duty and financial assurance." }, { "id": "SRC-004", "title": "Nevada - Mining and Minerals", "organization": "Bureau of Land Management", "url": "https://www.blm.gov/programs/energy-and-minerals/mining-and-minerals/about/nevada", "version_or_date": "Undated Nevada guidance; reviewed 2026-10-06; legal currency not established", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:12:58Z", "relevance": "Operator responsibility, notice or plan, reclamation and change-of-operator evidence as regional examples." }, { "id": "SRC-005", "title": "Production Information", "organization": "Bureau of Safety and Environmental Enforcement", "url": "https://www.data.bsee.gov/Main/Production.aspx", "version_or_date": "Living data catalogue; reviewed 2026-10-06; underlying datasets not downloaded", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:12:58Z", "relevance": "Separate well, lease, operator, measurement point, production and sales/inventory records; catalogue structure only." }, { "id": "SRC-006", "title": "Safety and Environmental Management Systems - SEMS", "organization": "Bureau of Safety and Environmental Enforcement", "url": "https://www.bsee.gov/sems", "version_or_date": "Living overview with regulatory history through 2019 and later data links; reviewed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:12:58Z", "relevance": "Offshore safety governance, management of change, stop-work authority and corrective-action evidence; not operational instructions or current-law certification." }, { "id": "SRC-007", "title": "On-line resource kit: mining", "organization": "International Labour Organization", "url": "https://www.ilo.org/resource/line-resource-kit-mining", "version_or_date": "3 April 2019 resource kit; linked convention text not fully retrieved", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:12:58Z", "relevance": "Mining safety and risk-assessment profile leads for large and small operations; kit summaries only, not full convention conformance." }, { "id": "SRC-008", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:12:58Z", "relevance": "Conceptual distinction between activity, entity and agent; attribution and derivation support evidence linkage, not truth certification." } ], "structure": { "bundles": [ { "id": "bundle-identity", "name": "Identity and boundary", "description": "Operation-specific context for identity and boundary.", "rationale": "Proposed grouping of related evidence questions; external masters retain their own authority and lifecycle.", "source_refs": [ "SRC-002", "SRC-005", "SRC-008" ], "layers": [ { "id": "layer-campaign", "name": "Campaign identity", "description": "One bounded extraction campaign or operating episode has its own identity. A mine, well, vessel, permit or reporting period cannot alone distinguish repeated operations.", "source_refs": [ "SRC-005", "SRC-008" ], "findings": [ { "id": "finding-campaign", "name": "Campaign identity", "description": "One bounded extraction campaign or operating episode has its own identity. A mine, well, vessel, permit or reporting period cannot alone distinguish repeated operations.", "source_refs": [ "SRC-005", "SRC-008" ], "questions": [ { "id": "question-campaign-1", "text": "Which master identifier distinguishes this campaign from other episodes at the same asset?", "kind": "identity", "answer_data": [ "data-campaign-1", "operation_id", "master_namespace", "aliases", "duplicate_resolution" ] }, { "id": "question-campaign-2", "text": "Which extraction profile and resource class describe the episode?", "kind": "classification", "answer_data": [ "data-campaign-2", "profile_ref", "profile_revision", "mining_drilling_logging_fishing", "resource_code" ] }, { "id": "question-campaign-3", "text": "What rule fixes the campaign boundary and separates extraction from exploration or processing?", "kind": "definition", "answer_data": [ "data-campaign-3", "boundary_rule", "inclusion_basis", "excluded_activity_refs" ] }, { "id": "question-campaign-4", "text": "Who maintains this record and who actually operated during each responsibility interval?", "kind": "ownership", "answer_data": [ "data-campaign-4", "record_steward_ref", "operator_refs", "effective_intervals", "evidence_refs" ] } ], "data_elements": [ { "id": "data-campaign-1", "name": "Campaign identity - identity", "description": "Candidate answer group: operation_id; master_namespace; aliases; duplicate_resolution. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "data-campaign-2", "name": "Campaign identity - classification", "description": "Candidate answer group: profile_ref; profile_revision; mining_drilling_logging_fishing; resource_code. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "data-campaign-3", "name": "Campaign identity - definition", "description": "Candidate answer group: boundary_rule; inclusion_basis; excluded_activity_refs. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "data-campaign-4", "name": "Campaign identity - ownership", "description": "Candidate answer group: record_steward_ref; operator_refs; effective_intervals; evidence_refs. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-campaign", "name": "Campaign identity statement", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-footprint", "name": "Resource and footprint", "description": "Link the resource and place masters; retain the operation-specific footprint or track and its evidence. Planned areas, actual disturbance and resource estimates are distinct.", "source_refs": [ "SRC-002", "SRC-005" ], "findings": [ { "id": "finding-footprint", "name": "Resource and footprint", "description": "Link the resource and place masters; retain the operation-specific footprint or track and its evidence. Planned areas, actual disturbance and resource estimates are distinct.", "source_refs": [ "SRC-002", "SRC-005" ], "questions": [ { "id": "question-footprint-1", "text": "Which site, well, harvest compartment or fishing area did the episode use?", "kind": "spatial", "answer_data": [ "data-footprint-1", "place_refs", "geometry_ref", "coordinate_system", "positional_uncertainty" ] }, { "id": "question-footprint-2", "text": "Which independently maintained stock or deposit assessment is relevant without being treated as extracted output?", "kind": "relationship", "answer_data": [ "data-footprint-2", "resource_master_ref", "assessment_revision", "validity_interval" ] }, { "id": "question-footprint-3", "text": "How does the observed footprint differ from the approved or planned area?", "kind": "measurement", "answer_data": [ "data-footprint-3", "planned_geometry_ref", "observed_geometry_ref", "observation_time", "comparison_basis" ] }, { "id": "question-footprint-4", "text": "How are uncertain positions and crossings between management areas represented?", "kind": "exception", "answer_data": [ "data-footprint-4", "uncertain_segments", "jurisdiction_refs", "unresolved_allocation", "evidence_refs" ] } ], "data_elements": [ { "id": "data-footprint-1", "name": "Resource and footprint - spatial", "description": "Candidate answer group: place_refs; geometry_ref; coordinate_system; positional_uncertainty. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "data-footprint-2", "name": "Resource and footprint - relationship", "description": "Candidate answer group: resource_master_ref; assessment_revision; validity_interval. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "data-footprint-3", "name": "Resource and footprint - measurement", "description": "Candidate answer group: planned_geometry_ref; observed_geometry_ref; observation_time; comparison_basis. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "data-footprint-4", "name": "Resource and footprint - exception", "description": "Candidate answer group: uncertain_segments; jurisdiction_refs; unresolved_allocation; evidence_refs. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-footprint", "name": "Footprint evidence index", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-authority", "name": "Authority and operating limits", "description": "Operation-specific context for authority and operating limits.", "rationale": "Proposed grouping of related evidence questions; external masters retain their own authority and lifecycle.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "layers": [ { "id": "layer-basis", "name": "Applicable authority evidence", "description": "Record the claimed legal or customary basis, competent authority and applicable conditions by reference. Evidence may describe unauthorized or disputed extraction without authorizing it.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "finding-basis", "name": "Applicable authority evidence", "description": "Record the claimed legal or customary basis, competent authority and applicable conditions by reference. Evidence may describe unauthorized or disputed extraction without authorizing it.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "question-basis-1", "text": "Which instruments or customary tenure evidence are claimed to permit this extraction?", "kind": "authority", "answer_data": [ "data-basis-1", "authority_refs", "holder_ref", "jurisdiction", "basis_type", "status_as_of" ] }, { "id": "question-basis-2", "text": "Which authority revision and validity interval applied when extraction occurred?", "kind": "temporal", "answer_data": [ "data-basis-2", "instrument_revision", "effective_start", "effective_end", "observation_time" ] }, { "id": "question-basis-3", "text": "Which community, tenure or access claims remain unresolved for the affected area?", "kind": "constraint", "answer_data": [ "data-basis-3", "rights_claim_refs", "consultation_evidence_refs", "dispute_state", "reviewer_ref" ] }, { "id": "question-basis-4", "text": "What evidence records an absent, suspended or contested authority basis?", "kind": "exception", "answer_data": [ "data-basis-4", "authority_evidence_state", "allegation_status", "source_ref", "escalation_ref" ] } ], "data_elements": [ { "id": "data-basis-1", "name": "Applicable authority evidence - authority", "description": "Candidate answer group: authority_refs; holder_ref; jurisdiction; basis_type; status_as_of. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "data-basis-2", "name": "Applicable authority evidence - temporal", "description": "Candidate answer group: instrument_revision; effective_start; effective_end; observation_time. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "data-basis-3", "name": "Applicable authority evidence - constraint", "description": "Candidate answer group: rights_claim_refs; consultation_evidence_refs; dispute_state; reviewer_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "data-basis-4", "name": "Applicable authority evidence - exception", "description": "Candidate answer group: authority_evidence_state; allegation_status; source_ref; escalation_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-basis", "name": "Authority applicability snapshot", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-limits", "name": "Limit and accounting basis", "description": "A cap is optional and profile-specific: quantity, area, effort or other conditions may apply. Store local operands and external rule references; shared allocation and legal compliance decisions remain external.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "finding-limits", "name": "Limit and accounting basis", "description": "A cap is optional and profile-specific: quantity, area, effort or other conditions may apply. Store local operands and external rule references; shared allocation and legal compliance decisions remain external.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "question-limits-1", "text": "Which limits apply to this campaign and which are explicitly not applicable?", "kind": "requirement", "answer_data": [ "data-limits-1", "rule_refs", "applicability_state", "reason", "scope_key" ] }, { "id": "question-limits-2", "text": "What resource, unit, period and allocation basis make output comparable to each limit?", "kind": "measurement", "answer_data": [ "data-limits-2", "resource_code", "quantity_basis", "unit", "period", "allocation_ref", "conversion_ref" ] }, { "id": "question-limits-3", "text": "Which other campaigns share the same allowance and authoritative accounting ledger?", "kind": "composition", "answer_data": [ "data-limits-3", "shared_limit_ref", "ledger_ref", "participating_operation_refs", "snapshot_time" ] }, { "id": "question-limits-4", "text": "What prevents provisional, duplicate or late output records from being treated as final utilization?", "kind": "validation", "answer_data": [ "data-limits-4", "accepted_revision_set", "completeness_state", "exclusions", "qualified_balance_ref" ] } ], "data_elements": [ { "id": "data-limits-1", "name": "Limit and accounting basis - requirement", "description": "Candidate answer group: rule_refs; applicability_state; reason; scope_key. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-limits-2", "name": "Limit and accounting basis - measurement", "description": "Candidate answer group: resource_code; quantity_basis; unit; period; allocation_ref; conversion_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-limits-3", "name": "Limit and accounting basis - composition", "description": "Candidate answer group: shared_limit_ref; ledger_ref; participating_operation_refs; snapshot_time. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-limits-4", "name": "Limit and accounting basis - validation", "description": "Candidate answer group: accepted_revision_set; completeness_state; exclusions; qualified_balance_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "artifact-limits", "name": "Limit binding record", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-execution", "name": "Plan and observed execution", "description": "Operation-specific context for plan and observed execution.", "rationale": "Proposed grouping of related evidence questions; external masters retain their own authority and lifecycle.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-plan", "name": "Plan and capability references", "description": "Pin the approved plan and selected method category at policy level. Equipment capability, worker competency and readiness reviews are external evidence, not permission inferred from possession of equipment.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-plan", "name": "Plan and capability references", "description": "Pin the approved plan and selected method category at policy level. Equipment capability, worker competency and readiness reviews are external evidence, not permission inferred from possession of equipment.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ], "questions": [ { "id": "question-plan-1", "text": "Which approved plan revision and method category were intended for this episode?", "kind": "process", "answer_data": [ "data-plan-1", "plan_ref", "revision", "method_category", "intended_outputs" ] }, { "id": "question-plan-2", "text": "Which assets, teams and competency records are associated with the plan?", "kind": "relationship", "answer_data": [ "data-plan-2", "asset_refs", "team_refs", "competency_evidence_refs", "readiness_review_ref" ] }, { "id": "question-plan-3", "text": "Which prerequisites and stop conditions are required by the applicable safety and environmental profile?", "kind": "constraint", "answer_data": [ "data-plan-3", "profile_refs", "prerequisite_evidence", "stop_condition_refs", "unresolved_items" ] }, { "id": "question-plan-4", "text": "Who approved a material change of plan and what evidence records its scope?", "kind": "decision", "answer_data": [ "data-plan-4", "change_ref", "approver_role", "approval_evidence_ref", "effective_time" ] } ], "data_elements": [ { "id": "data-plan-1", "name": "Plan and capability references - process", "description": "Candidate answer group: plan_ref; revision; method_category; intended_outputs. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "data-plan-2", "name": "Plan and capability references - relationship", "description": "Candidate answer group: asset_refs; team_refs; competency_evidence_refs; readiness_review_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "data-plan-3", "name": "Plan and capability references - constraint", "description": "Candidate answer group: profile_refs; prerequisite_evidence; stop_condition_refs; unresolved_items. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "data-plan-4", "name": "Plan and capability references - decision", "description": "Candidate answer group: change_ref; approver_role; approval_evidence_ref; effective_time. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-plan", "name": "Plan binding snapshot", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-timeline", "name": "Execution intervals and exceptions", "description": "Record proposed, underway, interrupted, ceased and cancelled states as local profile terms with supporting evidence. Cancellation before work, interruption and completed extraction have different meanings.", "source_refs": [ "SRC-002", "SRC-006", "SRC-008" ], "findings": [ { "id": "finding-timeline", "name": "Execution intervals and exceptions", "description": "Record proposed, underway, interrupted, ceased and cancelled states as local profile terms with supporting evidence. Cancellation before work, interruption and completed extraction have different meanings.", "source_refs": [ "SRC-002", "SRC-006", "SRC-008" ], "questions": [ { "id": "question-timeline-1", "text": "Which evidenced state describes the campaign and which transitions are still disputed?", "kind": "lifecycle", "answer_data": [ "data-timeline-1", "state_code", "state_profile_ref", "supporting_event_refs", "disputed_transitions" ] }, { "id": "question-timeline-2", "text": "When did work start, pause, resume and cease relative to the planned interval?", "kind": "temporal", "answer_data": [ "data-timeline-2", "planned_interval", "actual_intervals", "event_time", "recorded_time", "precision" ] }, { "id": "question-timeline-3", "text": "Which observed interruption or deviation changed the execution record?", "kind": "event", "answer_data": [ "data-timeline-3", "event_ref", "affected_interval", "deviation_class", "reporting_actor" ] }, { "id": "question-timeline-4", "text": "What external decision supports resumption after a stop condition?", "kind": "authority", "answer_data": [ "data-timeline-4", "stop_notice_ref", "resumption_decision_ref", "decision_scope", "unresolved_state" ] } ], "data_elements": [ { "id": "data-timeline-1", "name": "Execution intervals and exceptions - lifecycle", "description": "Candidate answer group: state_code; state_profile_ref; supporting_event_refs; disputed_transitions. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-008" ] }, { "id": "data-timeline-2", "name": "Execution intervals and exceptions - temporal", "description": "Candidate answer group: planned_interval; actual_intervals; event_time; recorded_time; precision. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-008" ] }, { "id": "data-timeline-3", "name": "Execution intervals and exceptions - event", "description": "Candidate answer group: event_ref; affected_interval; deviation_class; reporting_actor. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-008" ] }, { "id": "data-timeline-4", "name": "Execution intervals and exceptions - authority", "description": "Candidate answer group: stop_notice_ref; resumption_decision_ref; decision_scope; unresolved_state. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-timeline", "name": "Campaign chronology", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-002", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-outputs", "name": "Outputs and measurement", "description": "Operation-specific context for outputs and measurement.", "rationale": "Proposed grouping of related evidence questions; external masters retain their own authority and lifecycle.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "layers": [ { "id": "layer-observations", "name": "Measured and estimated removals", "description": "Preserve observation provenance and the resource-specific measurement basis. Estimates, corrected observations and actual measurements remain distinguishable; a report is not automatically verified.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "findings": [ { "id": "finding-observations", "name": "Measured and estimated removals", "description": "Preserve observation provenance and the resource-specific measurement basis. Estimates, corrected observations and actual measurements remain distinguishable; a report is not automatically verified.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "questions": [ { "id": "question-observations-1", "text": "What quantity or effort was observed and on which unit and reference basis?", "kind": "measurement", "answer_data": [ "data-observations-1", "value", "unit", "resource_or_species_code", "gross_net_basis", "period" ] }, { "id": "question-observations-2", "text": "Which method, conditions, uncertainty and calibration or sampling evidence qualify the value?", "kind": "quality", "answer_data": [ "data-observations-2", "method_ref", "conditions", "uncertainty", "calibration_ref", "sampling_ref" ] }, { "id": "question-observations-3", "text": "Who produced the observation and which source revision supports it?", "kind": "provenance", "answer_data": [ "data-observations-3", "observer_ref", "instrument_ref", "source_revision", "observed_at", "ingested_at" ] }, { "id": "question-observations-4", "text": "How are estimates, missing observations, zero output and corrections distinguished?", "kind": "exception", "answer_data": [ "data-observations-4", "measurement_state", "missing_reason", "supersedes_ref", "correction_reason" ] } ], "data_elements": [ { "id": "data-observations-1", "name": "Measured and estimated removals - measurement", "description": "Candidate answer group: value; unit; resource_or_species_code; gross_net_basis; period. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-observations-2", "name": "Measured and estimated removals - quality", "description": "Candidate answer group: method_ref; conditions; uncertainty; calibration_ref; sampling_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-observations-3", "name": "Measured and estimated removals - provenance", "description": "Candidate answer group: observer_ref; instrument_ref; source_revision; observed_at; ingested_at. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-observations-4", "name": "Measured and estimated removals - exception", "description": "Candidate answer group: measurement_state; missing_reason; supersedes_ref; correction_reason. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-observations", "name": "Output observation record", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-disposition", "name": "Output attribution and handoff", "description": "Connect output categories to separately mastered lots, landings and downstream records. Removal, retained product, discards, losses and sales are not interchangeable totals; sector profiles define categories.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "findings": [ { "id": "finding-disposition", "name": "Output attribution and handoff", "description": "Connect output categories to separately mastered lots, landings and downstream records. Removal, retained product, discards, losses and sales are not interchangeable totals; sector profiles define categories.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "questions": [ { "id": "question-disposition-1", "text": "Which outputs are retained product, incidental catch, discards, waste or loss under this profile?", "kind": "classification", "answer_data": [ "data-disposition-1", "output_category", "category_profile_ref", "quantity_refs", "applicability" ] }, { "id": "question-disposition-2", "text": "Which lot or stream allocations connect this episode to commingled or split outputs?", "kind": "composition", "answer_data": [ "data-disposition-2", "lot_refs", "allocation_edges", "fractions_or_quantities", "allocation_method_ref" ] }, { "id": "question-disposition-3", "text": "Which receipt or transfer evidence links extraction to landing, custody or downstream processing?", "kind": "relationship", "answer_data": [ "data-disposition-3", "handoff_ref", "recipient_role", "receipt_evidence", "downstream_run_ref" ] }, { "id": "question-disposition-4", "text": "Which discrepancies or overlapping categories prevent a reconciled output total?", "kind": "validation", "answer_data": [ "data-disposition-4", "reconciliation_ref", "category_overlap", "unmatched_quantities", "unresolved_delta" ] } ], "data_elements": [ { "id": "data-disposition-1", "name": "Output attribution and handoff - classification", "description": "Candidate answer group: output_category; category_profile_ref; quantity_refs; applicability. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-disposition-2", "name": "Output attribution and handoff - composition", "description": "Candidate answer group: lot_refs; allocation_edges; fractions_or_quantities; allocation_method_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-disposition-3", "name": "Output attribution and handoff - relationship", "description": "Candidate answer group: handoff_ref; recipient_role; receipt_evidence; downstream_run_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-disposition-4", "name": "Output attribution and handoff - validation", "description": "Candidate answer group: reconciliation_ref; category_overlap; unmatched_quantities; unresolved_delta. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-disposition", "name": "Output linkage statement", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-conditions", "name": "Conditions and adverse outcomes", "description": "Operation-specific context for conditions and adverse outcomes.", "rationale": "Proposed grouping of related evidence questions; external masters retain their own authority and lifecycle.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-environment", "name": "Environmental and community condition evidence", "description": "Bind condition references to evidence of effects on the affected area or community. Baseline and impact assertions need dates and evaluation context; no causal or sustainable-use conclusion follows from a single reading.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "finding-environment", "name": "Environmental and community condition evidence", "description": "Bind condition references to evidence of effects on the affected area or community. Baseline and impact assertions need dates and evaluation context; no causal or sustainable-use conclusion follows from a single reading.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "question-environment-1", "text": "Which environmental and community obligations apply to the campaign footprint?", "kind": "requirement", "answer_data": [ "data-environment-1", "obligation_refs", "affected_party_refs", "scope", "applicability_basis" ] }, { "id": "question-environment-2", "text": "Which baseline and monitoring observations support the reported condition status?", "kind": "evidence", "answer_data": [ "data-environment-2", "baseline_refs", "monitoring_refs", "evaluation_ref", "observation_interval" ] }, { "id": "question-environment-3", "text": "Which exceedance, complaint or unexpected effect remains unresolved?", "kind": "exception", "answer_data": [ "data-environment-3", "issue_refs", "allegation_or_confirmed", "affected_area", "escalation_ref" ] }, { "id": "question-environment-4", "text": "What limitations prevent the available observations from proving compliance or causation?", "kind": "quality", "answer_data": [ "data-environment-4", "coverage_gaps", "temporal_mismatch", "competing_explanations", "reviewer_ref" ] } ], "data_elements": [ { "id": "data-environment-1", "name": "Environmental and community condition evidence - requirement", "description": "Candidate answer group: obligation_refs; affected_party_refs; scope; applicability_basis. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "data-environment-2", "name": "Environmental and community condition evidence - evidence", "description": "Candidate answer group: baseline_refs; monitoring_refs; evaluation_ref; observation_interval. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "data-environment-3", "name": "Environmental and community condition evidence - exception", "description": "Candidate answer group: issue_refs; allegation_or_confirmed; affected_area; escalation_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "data-environment-4", "name": "Environmental and community condition evidence - quality", "description": "Candidate answer group: coverage_gaps; temporal_mismatch; competing_explanations; reviewer_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-environment", "name": "Condition evidence matrix", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-safety", "name": "Safety and incident linkage", "description": "Keep hazards, controls, stop-work evidence and incident links at policy level. Incident investigation, emergency response and equipment control remain owned by qualified external systems.", "source_refs": [ "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-safety", "name": "Safety and incident linkage", "description": "Keep hazards, controls, stop-work evidence and incident links at policy level. Incident investigation, emergency response and equipment control remain owned by qualified external systems.", "source_refs": [ "SRC-006", "SRC-007" ], "questions": [ { "id": "question-safety-1", "text": "Which hazard review and control-verification records cover the current plan revision?", "kind": "security", "answer_data": [ "data-safety-1", "hazard_review_ref", "control_evidence_refs", "plan_revision", "review_time" ] }, { "id": "question-safety-2", "text": "Which role can stop work and which authority evaluates readiness to resume?", "kind": "authority", "answer_data": [ "data-safety-2", "stop_role", "resume_authority_ref", "applicable_policy_ref", "notification_route" ] }, { "id": "question-safety-3", "text": "Which incident or near-miss records are linked to this campaign?", "kind": "event", "answer_data": [ "data-safety-3", "incident_refs", "occurrence_time", "report_time", "affected_scope" ] }, { "id": "question-safety-4", "text": "Which worker or reporter details require restricted handling while preserving necessary safety evidence?", "kind": "privacy", "answer_data": [ "data-safety-4", "sensitive_field_classes", "authorized_recipient_roles", "redaction_policy", "retention_basis" ] } ], "data_elements": [ { "id": "data-safety-1", "name": "Safety and incident linkage - security", "description": "Candidate answer group: hazard_review_ref; control_evidence_refs; plan_revision; review_time. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "data-safety-2", "name": "Safety and incident linkage - authority", "description": "Candidate answer group: stop_role; resume_authority_ref; applicable_policy_ref; notification_route. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "data-safety-3", "name": "Safety and incident linkage - event", "description": "Candidate answer group: incident_refs; occurrence_time; report_time; affected_scope. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "data-safety-4", "name": "Safety and incident linkage - privacy", "description": "Candidate answer group: sensitive_field_classes; authorized_recipient_roles; redaction_policy; retention_basis. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-safety", "name": "Safety evidence linkage", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-closure", "name": "Cessation and residual duties", "description": "Operation-specific context for cessation and residual duties.", "rationale": "Proposed grouping of related evidence questions; external masters retain their own authority and lifecycle.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "layers": [ { "id": "layer-duties", "name": "Restoration and financial assurance references", "description": "Where applicable, link restoration, rehabilitation, monitoring or decommissioning obligations and supporting assurance instruments. These are not universal or necessarily owed only after cessation.", "source_refs": [ "SRC-003", "SRC-004" ], "findings": [ { "id": "finding-duties", "name": "Restoration and financial assurance references", "description": "Where applicable, link restoration, rehabilitation, monitoring or decommissioning obligations and supporting assurance instruments. These are not universal or necessarily owed only after cessation.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "question-duties-1", "text": "Which restoration or aftercare obligations are triggered and which have an explicit non-applicability basis?", "kind": "requirement", "answer_data": [ "data-duties-1", "duty_refs", "trigger", "applicability", "reason", "affected_area" ] }, { "id": "question-duties-2", "text": "What milestones and monitoring periods survive the end of extraction?", "kind": "temporal", "answer_data": [ "data-duties-2", "milestone_refs", "due_dates", "monitoring_period", "time_basis" ] }, { "id": "question-duties-3", "text": "Who remains responsible after an operator change or abandonment?", "kind": "ownership", "answer_data": [ "data-duties-3", "responsibility_intervals", "transfer_evidence_ref", "unresolved_liability", "successor_ref" ] }, { "id": "question-duties-4", "text": "Which financial assurance reference covers the applicable duty and what coverage is uncertain?", "kind": "relationship", "answer_data": [ "data-duties-4", "assurance_ref", "duty_scope", "validity_evidence", "adequacy_review_ref" ] } ], "data_elements": [ { "id": "data-duties-1", "name": "Restoration and financial assurance references - requirement", "description": "Candidate answer group: duty_refs; trigger; applicability; reason; affected_area. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-duties-2", "name": "Restoration and financial assurance references - temporal", "description": "Candidate answer group: milestone_refs; due_dates; monitoring_period; time_basis. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-duties-3", "name": "Restoration and financial assurance references - ownership", "description": "Candidate answer group: responsibility_intervals; transfer_evidence_ref; unresolved_liability; successor_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-duties-4", "name": "Restoration and financial assurance references - relationship", "description": "Candidate answer group: assurance_ref; duty_scope; validity_evidence; adequacy_review_ref. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-duties", "name": "Residual duty register", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-acceptance", "name": "Closure evidence and acceptance", "description": "Cessation, completion of remedial work, acceptance of a duty and release of assurance are separate assertions. The local record links decisions without issuing them or extinguishing liability.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "findings": [ { "id": "finding-acceptance", "name": "Closure evidence and acceptance", "description": "Cessation, completion of remedial work, acceptance of a duty and release of assurance are separate assertions. The local record links decisions without issuing them or extinguishing liability.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "questions": [ { "id": "question-acceptance-1", "text": "Which extraction work has ceased and which residual duties remain open?", "kind": "state", "answer_data": [ "data-acceptance-1", "ceased_scope", "open_duty_refs", "status_evidence", "as_of_time" ] }, { "id": "question-acceptance-2", "text": "What work and observation records support a claimed restoration outcome?", "kind": "evidence", "answer_data": [ "data-acceptance-2", "work_refs", "monitoring_refs", "criterion_ref", "evidence_limitations" ] }, { "id": "question-acceptance-3", "text": "Which competent reviewer accepted a specific duty and what qualifications remain?", "kind": "decision", "answer_data": [ "data-acceptance-3", "acceptance_decision_ref", "reviewer_role", "accepted_scope", "conditions" ] }, { "id": "question-acceptance-4", "text": "What evidence distinguishes partial acceptance, later failure and reopening from final release?", "kind": "exception", "answer_data": [ "data-acceptance-4", "partial_scope", "reopening_event_ref", "release_decision_ref", "outstanding_items" ] } ], "data_elements": [ { "id": "data-acceptance-1", "name": "Closure evidence and acceptance - state", "description": "Candidate answer group: ceased_scope; open_duty_refs; status_evidence; as_of_time. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-acceptance-2", "name": "Closure evidence and acceptance - evidence", "description": "Candidate answer group: work_refs; monitoring_refs; criterion_ref; evidence_limitations. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-acceptance-3", "name": "Closure evidence and acceptance - decision", "description": "Candidate answer group: acceptance_decision_ref; reviewer_role; accepted_scope; conditions. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-acceptance-4", "name": "Closure evidence and acceptance - exception", "description": "Candidate answer group: partial_scope; reopening_event_ref; release_decision_ref; outstanding_items. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-acceptance", "name": "Closure and acceptance index", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Reporting and record assurance", "description": "Operation-specific context for reporting and record assurance.", "rationale": "Proposed grouping of related evidence questions; external masters retain their own authority and lifecycle.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008" ], "layers": [ { "id": "layer-returns", "name": "Reporting and disclosure evidence", "description": "Keep the reporting obligation, submitted revision, acknowledgement and acceptance distinct. Recipient-specific disclosure is governed; neither all data nor all regulator views have a universal exclusion list.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-returns", "name": "Reporting and disclosure evidence", "description": "Keep the reporting obligation, submitted revision, acknowledgement and acceptance distinct. Recipient-specific disclosure is governed; neither all data nor all regulator views have a universal exclusion list.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "question-returns-1", "text": "Which returns are required for which recipient, period and applicable reporting profile?", "kind": "requirement", "answer_data": [ "data-returns-1", "obligation_ref", "recipient_role", "reporting_period", "deadline", "profile_revision" ] }, { "id": "question-returns-2", "text": "Which revision was prepared, submitted, acknowledged or rejected?", "kind": "state", "answer_data": [ "data-returns-2", "return_id", "revision", "submission_evidence", "receipt_ref", "rejection_reason" ] }, { "id": "question-returns-3", "text": "What purpose and authority govern the fields visible to each recipient?", "kind": "access", "answer_data": [ "data-returns-3", "recipient_policy_ref", "purpose", "allowed_fields", "restriction_basis" ] }, { "id": "question-returns-4", "text": "Which mapping preserves local units, categories and identifiers in a required reporting format?", "kind": "interoperability", "answer_data": [ "data-returns-4", "mapping_ref", "mapping_revision", "code_lists", "unit_conversion", "loss_report" ] } ], "data_elements": [ { "id": "data-returns-1", "name": "Reporting and disclosure evidence - requirement", "description": "Candidate answer group: obligation_ref; recipient_role; reporting_period; deadline; profile_revision. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-returns-2", "name": "Reporting and disclosure evidence - state", "description": "Candidate answer group: return_id; revision; submission_evidence; receipt_ref; rejection_reason. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-returns-3", "name": "Reporting and disclosure evidence - access", "description": "Candidate answer group: recipient_policy_ref; purpose; allowed_fields; restriction_basis. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-returns-4", "name": "Reporting and disclosure evidence - interoperability", "description": "Candidate answer group: mapping_ref; mapping_revision; code_lists; unit_conversion; loss_report. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-returns", "name": "Reporting receipt index", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-lineage", "name": "Lineage, correction and disposal", "description": "Maintain source-linked assertions with explicit uncertainty, controlled correction and retention dependencies. These record-governance choices are proposed locally; provenance vocabulary does not mandate retention durations.", "source_refs": [ "SRC-008" ], "findings": [ { "id": "finding-lineage", "name": "Lineage, correction and disposal", "description": "Maintain source-linked assertions with explicit uncertainty, controlled correction and retention dependencies. These record-governance choices are proposed locally; provenance vocabulary does not mandate retention durations.", "source_refs": [ "SRC-008" ], "questions": [ { "id": "question-lineage-1", "text": "Which source, actor and derivation chain support each material assertion?", "kind": "provenance", "answer_data": [ "data-lineage-1", "assertion_id", "source_ref", "attributed_actor", "derivation_refs" ] }, { "id": "question-lineage-2", "text": "How are conflicting observations and superseded assertions preserved without double counting?", "kind": "validation", "answer_data": [ "data-lineage-2", "conflict_set", "preferred_revision", "review_reason", "historical_link" ] }, { "id": "question-lineage-3", "text": "Which retention rule or hold controls disposal of this campaign record and its sensitive payloads?", "kind": "retention", "answer_data": [ "data-lineage-3", "retention_policy_ref", "hold_ref", "disposition_authority", "payload_scope" ] }, { "id": "question-lineage-4", "text": "What identifiers and loss annotations allow a recipient to trace an exported assertion back to its source?", "kind": "interoperability", "answer_data": [ "data-lineage-4", "master_id", "assertion_revision", "export_mapping_ref", "loss_annotations" ] } ], "data_elements": [ { "id": "data-lineage-1", "name": "Lineage, correction and disposal - provenance", "description": "Candidate answer group: assertion_id; source_ref; attributed_actor; derivation_refs. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "data-lineage-2", "name": "Lineage, correction and disposal - validation", "description": "Candidate answer group: conflict_set; preferred_revision; review_reason; historical_link. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "data-lineage-3", "name": "Lineage, correction and disposal - retention", "description": "Candidate answer group: retention_policy_ref; hold_ref; disposition_authority; payload_scope. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "data-lineage-4", "name": "Lineage, correction and disposal - interoperability", "description": "Candidate answer group: master_id; assertion_revision; export_mapping_ref; loss_annotations. Preserve unknown, not applicable and disputed states; nested schemas require a pinned implementation profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [ { "id": "artifact-lineage", "name": "Assertion lineage index", "description": "Versioned evidence view answering this finding; payload may be referenced rather than copied.", "media_or_form": [ "Structured record", "Evidence index" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and revision; otherwise governed IRI, then adopting-Dimension UUID. Campaign linkage is explicit; a date or permit number alone is not artifact identity.", "source_refs": [ "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-register", "name": "Register campaign evidence", "description": "Proposed, unimplemented local operation. Create a local evidence record for an asserted campaign, including incomplete or unauthorized cases.", "inputs": [ "Master namespace", "Boundary profile", "Actor and source references" ], "outputs": [ "Campaign record or duplicate/authority refusal" ], "preconditions": [ "Authorized record writer", "Duplicate check", "Explicit evidence status" ], "effects": [ "Creates local record only; does not authorize or initiate extraction" ], "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "function-bind", "name": "Bind external authority and plan", "description": "Proposed, unimplemented local operation. Pin applicable authority, plan and limit revisions without altering their masters.", "inputs": [ "Campaign revision", "External references", "Applicability evidence" ], "outputs": [ "Binding snapshot or unresolved-reference result" ], "preconditions": [ "Authorized writer", "Resolvable reference or explicit unresolved state", "Expected campaign revision" ], "effects": [ "Adds source-qualified local bindings; no grant issuance or plan approval" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "function-observe", "name": "Record output observation", "description": "Proposed, unimplemented local operation. Append a measured, estimated or corrected observation with sector-specific units and evidence.", "inputs": [ "Campaign revision", "Observation group", "Evidence and correction link" ], "outputs": [ "Observation revision or rejected incomplete input" ], "preconditions": [ "Record authority", "Measurement basis supplied or marked unknown", "No silent overwrite of prior values" ], "effects": [ "Updates local evidence; does not change a quota ledger or certify output" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "function-reconcile", "name": "Prepare output reconciliation", "description": "Proposed, unimplemented local operation. Prepare a local arithmetic comparison from pinned compatible observations and allocation evidence.", "inputs": [ "Accepted observation revisions", "Category and unit profile", "Allocation evidence" ], "outputs": [ "Reconciliation candidate or indeterminate result with gaps" ], "preconditions": [ "Authorized analyst", "Disjoint categories", "Compatible units and bases", "Known input completeness" ], "effects": [ "Records candidate delta and exclusions only; no regulatory compliance decision or shared allowance reservation" ], "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "function-link-condition", "name": "Link condition or incident evidence", "description": "Proposed, unimplemented local operation. Associate an external assessment, stop notice, complaint or incident with the affected interval.", "inputs": [ "Campaign revision", "External evidence reference", "Scope and event interval" ], "outputs": [ "Qualified linkage or scope-conflict result" ], "preconditions": [ "Need-to-know access", "Source and reporter protection", "Expected revision" ], "effects": [ "Records linkage and unresolved status; no emergency execution or incident closure" ], "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "function-record-closure", "name": "Record cessation and acceptance evidence", "description": "Proposed, unimplemented local operation. Attach cessation, remedial work and acceptance decisions as separately qualified assertions.", "inputs": [ "Campaign revision", "Duty references", "Cessation and acceptance evidence" ], "outputs": [ "Closure view with outstanding duties or indeterminate state" ], "preconditions": [ "Authorized recorder", "Competent decision evidence for accepted scope", "Release evidence separate from work completion" ], "effects": [ "Updates local closure view; does not discharge a duty or release security" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "function-prepare-return", "name": "Prepare controlled return", "description": "Proposed, unimplemented local operation. Construct a local reporting projection with traceable source revisions and loss annotations.", "inputs": [ "Recipient policy", "Reporting profile", "Campaign snapshot" ], "outputs": [ "Draft return and mapping report or access refusal" ], "preconditions": [ "Authorized purpose", "Field-level disclosure evaluation by governing system", "Pinned schema and input revision" ], "effects": [ "Creates local draft only; no transmission, publication or claim of recipient acceptance" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "composition": [ { "target": "WM-ACT-002", "relation": "ALIGN", "purpose": "Candidate reconciliation of legacy K2 EXTEND: a campaign can contain several acts and is not necessarily one atomic act. Pin act references; do not inherit an unverified schema.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "WM-ACT-010", "relation": "REFERENCE", "purpose": "Downstream production runs master processing and transformation; only output handoff references live here.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "WM-EAR-004", "relation": "REFERENCE", "purpose": "Mineral deposits and assessments are resource-owned; legacy P5 is not a site model. Only applicable mining or drilling resource references live here.", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] }, { "target": "WM-BLT-008", "relation": "REFERENCE", "purpose": "Candidate managed site reference where applicable; mobile fishing operations may instead reference geographic areas. Site lifecycle is external.", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] }, { "target": "WM-POL-014", "relation": "REFERENCE", "purpose": "Candidate legal rights and entitlement reference; physical extraction authority is separate from permission to read data.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "target": "WM-XCT-001", "relation": "REFERENCE", "purpose": "Candidate stewardship binding for the record, distinct from title to land or natural resources; no generic ownership machinery duplicated.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "WM-XCT-002", "relation": "REFERENCE", "purpose": "Candidate data-access policy binding only. A legacy S2 data permission is not an extraction licence.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "https://www.w3.org/TR/prov-o/", "relation": "ALIGN", "purpose": "Conceptual activity, entity, agent and derivation mapping only; executable mappings and conformance fixtures are deferred.", "required": false, "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Owner designated by the adopting Dimension; no fixed commercial owner", "Declare campaign boundary, master namespace, jurisdiction and extraction profile", "Pin authority, measurement, safety, disclosure and retention profiles with review roles", "Separate record stewardship from resource title and physical operating authority" ], "namespace_guidance": "Stable namespace plus operation ID and separately versioned assertions; no dates as primary identity and no licence-plus-site uniqueness assumption.", "registry_links": [ "vr.wm-act-012", "Pinned candidate neighbors from composition; no required runtime inheritance claimed" ] }, "canon_and_patch": { "canonicalization_rules": [ "Maintain campaign identity while preserving the source and status of each assertion", "Normalize units only with a documented basis; preserve original observations and unknown precision" ], "patch_rules": [ "Require expected revision, reason, actor and evidence for local correction", "Append a superseding assertion; never lower recorded output to hide a breach", "Record revoked external references without rewriting historical applicability" ], "compatibility_rules": [ "Version code lists, measurement bases and boundary rules; flag lossy conversions", "Splitting or merging campaign boundaries requires explicit lineage and no automatic identifier reuse" ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with namespace", "Governed global identifier or IRI", "UUID or ULID assigned by the adopting Dimension" ], "timestamp_rule": "Use RFC 3339 with seconds and an explicit offset or Z for precise timestamps. Separate event time from observation and ingestion time. Preserve unknown precision; date-only reporting periods remain dates and are not fabricated timestamps.", "serial_naming_rule": "Stable artifact ID plus revision and campaign reference; human dates are labels only.", "integrity_rule": "Keep source locator, version, attribution and digest where available. A hash proves byte continuity, not truth, legal validity or sustainability." }, "policies": [ "Record unauthorized or contested extraction as evidence without granting physical operating permission", "Safety, hazardous materials and controlled resources remain at policy and oversight level; this model issues no machine-control or extraction instructions", "Legal applicability, community rights, trade sensitivity and worker privacy require qualified profile review", "No automatic public disclosure or universal regulator-view exclusion; disclose by lawful recipient scope", "External grants, limits, incident investigations, restoration decisions and enforcement retain their master systems" ], "crud": { "read": [ "Resolve tenant, recipient purpose and field policy before returning campaign or artifact data" ], "create": [ "Require authorized evidence recorder, stable identity and explicit missing or disputed authority state" ], "update": [ "Use revision concurrency, reason and provenance; preserve corrections and contrary evidence under retention policy" ], "delete": [ "Apply adopting-Dimension retention and disposal policy and active legal or investigation holds before deleting local payloads", "Authorized records system executes disposal; preserve only lawful minimal tombstones and dependency links, not perpetual personal data", "Deleting a local record never cancels a permit, incident, liability or restoration duty" ] }, "roles": [ { "name": "Record steward", "responsibilities": [ "Maintain identity, boundary and revisions" ] }, { "name": "Evidence recorder", "responsibilities": [ "Attribute observations and disclose gaps" ] }, { "name": "Qualified profile reviewer", "responsibilities": [ "Review sector, jurisdiction, safety and measurement applicability" ] }, { "name": "Authority liaison", "responsibilities": [ "Link external decisions without issuing them locally" ] }, { "name": "Disclosure and records custodian", "responsibilities": [ "Apply access, retention and lawful disposition rules" ] } ], "access": { "default_rule": "Deny by default; grant least-privilege access by campaign, purpose and recipient, with separate sensitive evidence controls.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Legally required disclosure or emergency access needs a recorded authority basis and minimum necessary scope", "Protect precise locations, commercial allocation and worker or reporter details according to the applicable policy" ], "audit_requirements": [ "Record actor, purpose, scope, policy revision, time and result in the designated external audit system", "Log exports, corrections and disposal approvals without exposing restricted payloads in broadly visible logs" ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md", "spec.yaml and visible research holds", "Adopting Dimension authority, safety, measurement, access and retention policies", "Pinned external masters and source evidence" ] } }, "coverage": { "claim": "Source-grounded proposed kernel for one persistent extraction campaign record across mining, drilling, logging and fishing. Separate local no-tools self-audit completed. Selected primary guidance and catalogue structures support a reviewable draft; independent review, source verification, specialist profiles and executable conformance remain held.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Campaign identity distinct from asset, permit, place and report interval." }, { "dimension": "lifecycle", "status": "covered", "notes": "Planned, observed, interrupted and ceased work distinguished from residual duty acceptance." }, { "dimension": "relationships", "status": "covered", "notes": "Candidate bindings preserve external rights, resource, site, processing and data-access masters." }, { "dimension": "temporal", "status": "covered", "notes": "Effective authority, actual intervals, observation times and reporting periods remain separate." }, { "dimension": "provenance", "status": "covered", "notes": "Sources, actors, derivation, supersession and uncertainty attached to assertions." }, { "dimension": "ownership", "status": "covered", "notes": "Record steward, operator, rights holder and duty bearer need not be the same party." }, { "dimension": "validation", "status": "gap", "notes": "Research schema validated; nested instance schemas and executable profiles remain gaps." }, { "dimension": "access", "status": "covered", "notes": "Purpose and field-scoped recipient views with safety and sensitive-location restrictions." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Policy-bound disposal with holds and minimal lawful tombstones." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual alignments and loss-aware export candidates only; no format conformance claimed." }, { "dimension": "physical properties", "status": "covered", "notes": "Quantities, units, basis, uncertainty, location and time belong to observations of the operation; asset dimensions remain external." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Distinguish alleged, measured, estimated, missing, corrected and independently assessed evidence." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Plan and readiness evidence separated from permission; proposed functions mutate local records only." }, { "dimension": "sector breadth", "status": "gap", "notes": "Mining, drilling, logging and fishing share a proposed kernel; detailed sector and legal profiles remain incomplete." } ], "known_omissions": [ "Executable nested schemas, acceptance fixtures and unit/category mappings are not implemented.", "Detailed onshore drilling, artisanal and subsistence practices, indigenous rights processes, protected species and resource-specific controls require specialist profiles.", "UNFC full text retrieval failed; CRIRSCO was not reviewed. Neither wildcard legacy import is admitted as a conformance claim.", "No independent external provider review; source currency and direct HTTP status remain unverified.", "Global resource or reserve estimates, ecosystem regeneration models, royalty accounting, commodity custody, enforcement, incident response and financial assurance execution are delegated." ], "conflicts": [], "regional_assumptions": [ "FAO materials inform a voluntary international pattern; fisheries and forest rules require local profiles.", "Mining guidance covers selected US public-land and Nevada examples; offshore guidance is US-specific. No worldwide legal applicability is inferred.", "Safety kit summaries and catalogue pages are not full normative implementations." ], "adversarial_checks": [ "A revoked permit must not erase evidence of activity that still occurred.", "Two trips or campaigns sharing one permit and site must retain distinct identities.", "A shared quota cannot be evaluated from one campaign without ledger completeness.", "Estimated gross output, retained output and sales cannot silently share one total.", "Cessation does not prove restoration acceptance or release of assurance.", "Source provenance and schema validity cannot establish truth, independent review or legal compliance." ] }, "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 bounded campaign record across planning, observations, interruptions and closure evidence. It is neither a physical asset nor necessarily one atomic act. The registry standalone-mm plane does not determine the subject-kind enum; external events and masters retain distinct identity." }, "decisions": [ { "concept": "Campaign identity", "disposition": "accepted", "rationale": "An explicit episode boundary and master identifier distinguish repeated operations sharing a permit, site or asset. Identity does not depend on a reporting date." }, { "concept": "Atomic act inheritance", "disposition": "deferred as inheritance", "rationale": "Legacy K2 EXTEND is overbroad for campaigns containing several acts. ALIGN and referenced acts preserve the proposed boundary without claiming runtime inheritance." }, { "concept": "Commons tenure and legal authority", "disposition": "qualified", "rationale": "The kernel asks for the actual tenure and authority basis and preserves contested or absent evidence. It does not universalize a commons grant or equate data access with physical permission." }, { "concept": "Unauthorized activity evidence", "disposition": "accepted for recording", "rationale": "Record creation requires evidence-recording authority, not a valid extraction permit. Documenting suspected unauthorized activity neither authorizes it nor conceals its occurrence." }, { "concept": "Legacy P5 site mapping", "disposition": "corrected in local proposal", "rationale": "P5 resolves to the mineral-resource neighbor. Managed sites and mobile geographic areas remain distinct references; the registry and shared relation ledger are not changed." }, { "concept": "Quota and shared allowance", "disposition": "qualified", "rationale": "Optional limits bind resource, unit, period and external accounting scope. Incomplete, duplicate or late observations cannot establish final shared utilization from one campaign alone." }, { "concept": "Plan and readiness", "disposition": "accepted as evidence bindings", "rationale": "Assets and competency references provide context but do not confer operating permission. Plan changes, stop conditions and resumption depend on externally evidenced authority." }, { "concept": "Measurement and output attribution", "disposition": "accepted with profile hold", "rationale": "Observed, estimated and corrected quantities remain distinct. Category overlap, commingling and incompatible bases yield discrepancies or indeterminate reconciliation rather than a fabricated total." }, { "concept": "Safety and environmental effects", "disposition": "bounded to evidence", "rationale": "The model links reviews, controls, incidents and complaints without performing response or proving causation from one observation. Hazardous subjects remain at policy level." }, { "concept": "Cessation and residual duty", "disposition": "separated", "rationale": "Ending extraction, performing remedial work, accepting a duty and releasing assurance have separate evidence. Local record status neither extinguishes liability nor releases security." }, { "concept": "Reporting and disclosure", "disposition": "qualified", "rationale": "Prepared, submitted, acknowledged and accepted returns are separate states. Recipient-purpose policies replace universal public disclosure and fixed regulator-view omissions." }, { "concept": "Local proposed functions", "disposition": "accepted as unimplemented", "rationale": "All seven functions have local effects, preconditions and refusal or unresolved outcomes. They do not issue grants, execute extraction, submit returns or discharge duties." }, { "concept": "Retention and provenance", "disposition": "accepted with policy dependency", "rationale": "Revision history is bounded by lawful retention and holds, with minimal tombstones after authorized disposal. Provenance and digests do not establish truth or legal status." }, { "concept": "Legacy imports and sector scope", "disposition": "limited", "rationale": "No wildcard conformance survives migration. UNFC retrieval failed, CRIRSCO was unreviewed and selected FAO concepts do not supply every sector, community-rights or jurisdiction profile." }, { "concept": "Instance conformance", "disposition": "deferred", "rationale": "Candidate object groups, mappings and neighbor links express research questions but not executable nested schemas, acceptance fixtures or certified runtime interoperability." }, { "concept": "Provider and source assurance", "disposition": "waived and held", "rationale": "Codex alone authored and self-audited the result. Eight browser sources do not establish direct HTTP status or current normative versions; skipped providers contribute no agreement or evidence." } ], "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 review.", "Source and version verification remains incomplete. Direct HTTP checks were not attempted under the owner-reported sandbox restriction, so zero HTTP 200 responses were measured. Selected browser evidence, regional guidance, living pages, kit summaries and catalogue structures are documented in source-review.md; source currency, licensing and full normative coverage remain unverified.", "Qualified sector and jurisdiction profiles are required for legal authority, community and indigenous rights, safety, environmental conditions, resource categories, measurement bases, shared-limit accounting and closure decisions. No operational, legal-compliance or sustainability certification is claimed.", "Nested instance schemas, pinned candidate neighbor bindings, versioned unit/category mappings, executable conformance and adversarial acceptance fixtures remain incomplete. All seven functions are proposed local record operations, not implemented controls.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify admitted source versions and applicability; resolve deferred UNFC and CRIRSCO leads before adding any alignment or conformance claim.", "Develop qualified sector profiles and executable fixtures for repeated campaigns, unauthorized evidence, shared limits, uncertain measurements, commingled outputs, operator changes, partial restoration acceptance and lawful disposal.", "Restore independent external review before canonical or publishable-draft promotion." ] }, "statistics": { "sources": 8, "bundles": 7, "layers": 14, "findings": 14, "questions": 56, "artifacts": 14, "functions": 7 } }