# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T19:59:30Z", "synthesisSha256": "4cf0e91fbe0152eabe6d24311fd0890faec26427f9a10c3f8664a16ed6a3cf75", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-050", "registryId": "vr.wm-act-050", "name": "Environmental Impact Assessment", "version": "0.1.0-reviewable-draft", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.ENV" ], "tags": [ "environmental", "impact", "assessment", "act.env" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-050-environmental-impact-assessment/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-050", "model": { "registry_id": "vr.wm-act-050", "model_id": "WM-ACT-050", "name": "Environmental Impact Assessment", "entry_kind": "entity", "purpose": "Represent one project environmental assessment case with traceable scope, evidence, alternatives, participation, conclusions and follow-up references.", "scope_statement": "A persistent assessment case is the root. It can begin with screening and end without full EIA, remain pending or withdrawn, or link an examined report and reasoned conclusion to a separate development decision. This authored case envelope records the procedure; it is neither the legal process definition nor a single report. Applicable jurisdiction and sector profiles determine requirements.", "in_scope": [ "Case identity, proposal revision and applicable route evidence", "Screening and scoped study requirements, alternatives and baseline assumptions", "Assessed effects, cumulative context, mitigation and residual uncertainty", "Report, consultation and transboundary exchange references", "Authority examination, conclusion currency, consent linkage and follow-up interfaces", "Assessment-specific revisions, controlled renditions, access and disposition policy" ], "out_of_scope": [ "Project design and construction master lifecycle", "Strategic assessment of plans or programmes and standalone habitats or other specialist assessments", "Issuing development consent, enforcing permits or adjudicating challenges", "Operating environmental monitoring equipment, simulation models or incident response", "Enterprise sustainability reporting, product life-cycle assessment and carbon accounting engines", "Universal screening thresholds, significance equations, statutory time limits or automatic legal advice" ], "boundary_notes": [ { "neighbor": "WM-ACT-034 Assessment / Evaluation", "distinction": "Registry parent is a conceptual generalization. No relationship-ledger edge exists for this model. ALIGN is proposed; no inherited runtime or generic evaluation machinery is asserted.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "Project and proposed activity", "distinction": "Reference the assessed project and revision; store only the snapshot needed to interpret environmental evidence, not project execution.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "Strategic and habitats assessments", "distinction": "Reuse pinned evidence where applicable while maintaining separate scope and conclusions. Plan assessment is not silently a project EIA.", "source_refs": [ "SRC-005", "SRC-001" ] }, { "neighbor": "Report and development consent", "distinction": "A developer report, authority conclusion and consent decision are distinct. The case references authoritative artifacts and never grants the right to proceed.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "Monitoring, enforcement and review cases", "distinction": "Keep conditions, programme and review references with feedback to assessment assumptions. Delivery, legal enforcement and remedy adjudication remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Directive 2011/92/EU on environmental impact assessment, consolidated text", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02011L0092-20140515", "version_or_date": "Consolidation 2014-05-15 incorporating Directive 2014/52/EU; authentic acts and national implementation still require verification", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T19:57:07Z", "relevance": "Articles 1-9a and Annexes III-IV: project assessment procedure, report, consultation, conclusion and monitoring. Consolidation is a documentation tool. The local data structure is an authored proposal, not a prescribed EU schema." }, { "id": "SRC-002", "title": "Environmental Impact Assessment - planning practice guidance", "organization": "Ministry of Housing, Communities and Local Government", "url": "https://www.gov.uk/guidance/environmental-impact-assessment", "version_or_date": "England planning guidance; selected paragraphs including 033-036 and 063 revised 2017-07-28; accessed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T19:57:07Z", "relevance": "England example for project changes, proportionate studies, expert report preparation, optional formal scoping and monitoring. Historical links on the page are not current-law certification." }, { "id": "SRC-003", "title": "Convention on Environmental Impact Assessment in a Transboundary Context - text", "organization": "United Nations Economic Commission for Europe", "url": "https://unece.org/environmental-policy/convention-environmental-impact-assessment-transboundary-context-espoo-3", "version_or_date": "Espoo Convention 1991; indexed page describes reissued 2017 text and amendments; treaty participation and amendment applicability unverified", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T19:57:07Z", "relevance": "Indexed official text of Articles 1-7 and Appendix II supports transboundary notification, participation, alternatives and follow-up links. Browser open failed; selected indexed content only was admitted." }, { "id": "SRC-004", "title": "Public participation - content of the Aarhus Convention", "organization": "United Nations Economic Commission for Europe", "url": "https://unece.org/environment-policy/public-participation/public-participation", "version_or_date": "Undated official explanatory page; indexed text accessed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T19:57:07Z", "relevance": "Official summary of Article 6 participation: early notice, meaningful opportunity and decision response. It is explanatory guidance, not a verified complete treaty text or universal right." }, { "id": "SRC-005", "title": "Strategic environmental assessment and sustainability appraisal", "organization": "Ministry of Housing, Communities and Local Government", "url": "https://www.gov.uk/guidance/strategic-environmental-assessment-and-sustainability-appraisal", "version_or_date": "Page updated 2020-12-31; boundary paragraph 003 revised 2019-07-22", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T19:57:07Z", "relevance": "Paragraph 003 distinguishes plan assessment, individual project EIA and habitats assessment. Used only for conceptual boundary, not present-day England legal advice." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation 2013-04-30; sections 3.1-3.3", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T19:57:07Z", "relevance": "Entities, activities, agents, derivation and attribution inform evidence lineage. A proposed conceptual alignment cannot certify scientific correctness, legal competence or implemented conformance." }, { "id": "SRC-007", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002, section 5.6", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T19:57:07Z", "relevance": "Timestamp syntax informs the local instant profile. Legal dates, unknown precision, elapsed periods and jurisdictional calendars require separate treatment." } ], "structure": { "bundles": [ { "id": "mandate-bundle", "name": "Case mandate and screening", "description": "Identity and route evidence precede any claim of completed EIA.", "rationale": "Groups related evidence and decisions within the single assessment case; this grouping is a local research design rather than a mandated legal hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ], "layers": [ { "id": "registration-layer", "name": "Registration and applicability", "description": "Assessment-specific context for registration and applicability. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ], "findings": [ { "id": "case-identity", "name": "Assessment case identity", "description": "A persistent local case binds one identified proposal and its assessment route. Screening-only cases are tracked without asserting that a full legal EIA occurred.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "questions": [ { "id": "case-identity-q-1", "text": "Which master case identifier distinguishes this assessment from another assessment of the same project?", "kind": "identity", "answer_data": [ "case-identity-data-1", "case_id", "issuer_namespace", "project_ref", "project_revision", "related_case_refs" ] }, { "id": "case-identity-q-2", "text": "Which accountable role stewards the case and which distinct roles propose, study and examine the project?", "kind": "ownership", "answer_data": [ "case-identity-data-2", "steward_role_ref", "developer_ref", "expert_refs", "authority_refs", "mandate_evidence" ] }, { "id": "case-identity-q-3", "text": "What is the evidenced case stage and which transitions remain unresolved?", "kind": "state", "answer_data": [ "case-identity-data-3", "stage", "event_ref", "event_time", "recorded_time", "pending_transition", "transition_basis" ] } ], "data_elements": [ { "id": "case-identity-data-1", "name": "Assessment case identity answer group 1", "description": "Candidate group: case_id, issuer_namespace, project_ref, project_revision, related_case_refs. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "case-identity-data-2", "name": "Assessment case identity answer group 2", "description": "Candidate group: steward_role_ref, developer_ref, expert_refs, authority_refs, mandate_evidence. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "case-identity-data-3", "name": "Assessment case identity answer group 3", "description": "Candidate group: stage, event_ref, event_time, recorded_time, pending_transition, transition_basis. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "case-identity-artifact", "name": "Case registration record", "description": "Versioned evidence for assessment case identity. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "assessment-profile", "name": "Applicable assessment profile", "description": "Jurisdiction, sector and legal route are pinned locally; neither a model link nor a project category alone establishes legal applicability.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "questions": [ { "id": "assessment-profile-q-1", "text": "Which jurisdiction and sector profile governs this project assessment route?", "kind": "classification", "answer_data": [ "assessment-profile-data-1", "jurisdiction", "sector", "legal_instrument_refs", "effective_versions", "profile_ref" ] }, { "id": "assessment-profile-q-2", "text": "Which competence evidence authorizes each screening, examination and decision role for this route?", "kind": "authority", "answer_data": [ "assessment-profile-data-2", "role_ref", "competence_basis", "territorial_scope", "delegation_limits", "conflict_review" ] }, { "id": "assessment-profile-q-3", "text": "Which strategic, habitats or other assessments inform this case while keeping separate conclusions?", "kind": "relationship", "answer_data": [ "assessment-profile-data-3", "assessment_refs", "assessment_types", "revision_pins", "reused_scope", "unresolved_gaps" ] } ], "data_elements": [ { "id": "assessment-profile-data-1", "name": "Applicable assessment profile answer group 1", "description": "Candidate group: jurisdiction, sector, legal_instrument_refs, effective_versions, profile_ref. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "assessment-profile-data-2", "name": "Applicable assessment profile answer group 2", "description": "Candidate group: role_ref, competence_basis, territorial_scope, delegation_limits, conflict_review. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "assessment-profile-data-3", "name": "Applicable assessment profile answer group 3", "description": "Candidate group: assessment_refs, assessment_types, revision_pins, reused_scope, unresolved_gaps. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "assessment-profile-artifact", "name": "Applicability and competence note", "description": "Versioned evidence for applicable assessment profile. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "screening-layer", "name": "Screening and determination", "description": "Assessment-specific context for screening and determination. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "screening-basis", "name": "Screening basis", "description": "Classification evidence covers the whole proposal and relevant changes. Screening is a reasoned route determination rather than an automatic threshold score.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "screening-basis-q-1", "text": "Which associated works, phases and changes belong to the whole proposal considered for screening?", "kind": "composition", "answer_data": [ "screening-basis-data-1", "project_parts", "associated_works", "phase_refs", "excluded_parts", "exclusion_reasons" ] }, { "id": "screening-basis-q-2", "text": "Which applicable lists, thresholds and case-specific criteria must the screening reviewer consider?", "kind": "requirement", "answer_data": [ "screening-basis-data-2", "category_codes", "threshold_rules", "units", "sensitive_locations", "case_criteria", "rule_versions" ] }, { "id": "screening-basis-q-3", "text": "Which evidence supports the screening inputs and which requested information is still missing?", "kind": "evidence", "answer_data": [ "screening-basis-data-3", "submission_refs", "criterion_evidence_map", "missing_information", "requests", "uncertainty" ] } ], "data_elements": [ { "id": "screening-basis-data-1", "name": "Screening basis answer group 1", "description": "Candidate group: project_parts, associated_works, phase_refs, excluded_parts, exclusion_reasons. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "screening-basis-data-2", "name": "Screening basis answer group 2", "description": "Candidate group: category_codes, threshold_rules, units, sensitive_locations, case_criteria, rule_versions. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "screening-basis-data-3", "name": "Screening basis answer group 3", "description": "Candidate group: submission_refs, criterion_evidence_map, missing_information, requests, uncertainty. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "screening-basis-artifact", "name": "Screening evidence schedule", "description": "Versioned evidence for screening basis. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "screening-outcome", "name": "Screening outcome and exceptions", "description": "Preserve the competent determination, its reasons and applicable exception basis. A local record of no EIA required is not project consent.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "screening-outcome-q-1", "text": "What determination was issued and what evidence and reasons support requiring or not requiring EIA?", "kind": "decision", "answer_data": [ "screening-outcome-data-1", "determination", "issuer", "reasons", "criteria_refs", "decision_ref" ] }, { "id": "screening-outcome-q-2", "text": "What specific exemption or special route is claimed and who verified its scope and conditions?", "kind": "exception", "answer_data": [ "screening-outcome-data-2", "exception_basis", "verifier", "conditions", "alternative_assessment_ref", "unresolved_applicability" ] }, { "id": "screening-outcome-q-3", "text": "Which submission, determination, disclosure and extension dates establish the screening chronology?", "kind": "temporal", "answer_data": [ "screening-outcome-data-3", "submission_complete_date", "determination_date", "disclosure_date", "extension_basis", "deadline_profile" ] } ], "data_elements": [ { "id": "screening-outcome-data-1", "name": "Screening outcome and exceptions answer group 1", "description": "Candidate group: determination, issuer, reasons, criteria_refs, decision_ref. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "screening-outcome-data-2", "name": "Screening outcome and exceptions answer group 2", "description": "Candidate group: exception_basis, verifier, conditions, alternative_assessment_ref, unresolved_applicability. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "screening-outcome-data-3", "name": "Screening outcome and exceptions answer group 3", "description": "Candidate group: submission_complete_date, determination_date, disclosure_date, extension_basis, deadline_profile. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "screening-outcome-artifact", "name": "Screening determination reference", "description": "Versioned evidence for screening outcome and exceptions. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "scope-bundle", "name": "Scope and proposal options", "description": "Freeze what is being studied and preserve alternatives and boundaries.", "rationale": "Groups related evidence and decisions within the single assessment case; this grouping is a local research design rather than a mandated legal hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "layers": [ { "id": "study-scope-layer", "name": "Scope and study domain", "description": "Assessment-specific context for scope and study domain. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "scope-topics", "name": "Topics and study requirements", "description": "Keep an explicit topic register, including population and health, biodiversity, land, soil, water, air, climate, assets, heritage, landscape and interactions where relevant.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "scope-topics-q-1", "text": "Which receptors and topics are included or excluded from study and why?", "kind": "requirement", "answer_data": [ "scope-topics-data-1", "topic_register", "receptor_refs", "inclusion_basis", "exclusion_evidence", "reviewer" ] }, { "id": "scope-topics-q-2", "text": "Was a formal scoping opinion requested or required and what is its actual authority and revision?", "kind": "authority", "answer_data": [ "scope-topics-data-2", "scoping_route", "opinion_ref", "issuer", "revision", "binding_status", "no_opinion_reason" ] }, { "id": "scope-topics-q-3", "text": "Which scoping issues remain disputed or unstudied and what review is assigned?", "kind": "quality", "answer_data": [ "scope-topics-data-3", "scope_issue", "contrary_evidence", "study_gap", "responsible_role", "resolution_due" ] } ], "data_elements": [ { "id": "scope-topics-data-1", "name": "Topics and study requirements answer group 1", "description": "Candidate group: topic_register, receptor_refs, inclusion_basis, exclusion_evidence, reviewer. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "scope-topics-data-2", "name": "Topics and study requirements answer group 2", "description": "Candidate group: scoping_route, opinion_ref, issuer, revision, binding_status, no_opinion_reason. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "scope-topics-data-3", "name": "Topics and study requirements answer group 3", "description": "Candidate group: scope_issue, contrary_evidence, study_gap, responsible_role, resolution_due. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "scope-topics-artifact", "name": "Topic and scope register", "description": "Versioned evidence for topics and study requirements. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "study-boundaries", "name": "Spatial and temporal study boundaries", "description": "Study domains may differ by receptor and pathway; the application boundary does not limit the area of potential effects.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "study-boundaries-q-1", "text": "What study area and coordinate reference apply to each receptor and impact pathway?", "kind": "spatial", "answer_data": [ "study-boundaries-data-1", "receptor_ref", "geometry_ref", "coordinate_reference", "extent_rationale", "cross_boundary_links" ] }, { "id": "study-boundaries-q-2", "text": "Which project phases, seasons and forecast horizons does each study cover?", "kind": "temporal", "answer_data": [ "study-boundaries-data-2", "study_ref", "phase", "season", "baseline_period", "forecast_horizon", "time_basis" ] }, { "id": "study-boundaries-q-3", "text": "Which boundary assumptions could exclude relevant effects and how will they be challenged?", "kind": "constraint", "answer_data": [ "study-boundaries-data-3", "boundary_assumptions", "excluded_pathways", "sensitivity_checks", "review_triggers" ] } ], "data_elements": [ { "id": "study-boundaries-data-1", "name": "Spatial and temporal study boundaries answer group 1", "description": "Candidate group: receptor_ref, geometry_ref, coordinate_reference, extent_rationale, cross_boundary_links. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "study-boundaries-data-2", "name": "Spatial and temporal study boundaries answer group 2", "description": "Candidate group: study_ref, phase, season, baseline_period, forecast_horizon, time_basis. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "study-boundaries-data-3", "name": "Spatial and temporal study boundaries answer group 3", "description": "Candidate group: boundary_assumptions, excluded_pathways, sensitivity_checks, review_triggers. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "study-boundaries-artifact", "name": "Study boundary specification", "description": "Versioned evidence for spatial and temporal study boundaries. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "proposal-options-layer", "name": "Proposal and alternatives", "description": "Assessment-specific context for proposal and alternatives. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "project-envelope", "name": "Assessed project envelope", "description": "Snapshot the proposal characteristics actually assessed while preserving the external project master. Do not treat an uncertain design envelope as a final design.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "project-envelope-q-1", "text": "What purpose, location and design revision define the proposal being assessed?", "kind": "definition", "answer_data": [ "project-envelope-data-1", "purpose", "site_ref", "design_revision", "project_description_ref", "revision_date" ] }, { "id": "project-envelope-q-2", "text": "Which resource demands, emissions and waste estimates describe each project phase with units and assumptions?", "kind": "measurement", "answer_data": [ "project-envelope-data-2", "phase", "quantity", "unit", "estimation_method", "range", "source_ref" ] }, { "id": "project-envelope-q-3", "text": "What parameters bound design flexibility and which combinations were actually assessed?", "kind": "constraint", "answer_data": [ "project-envelope-data-3", "parameter_bounds", "assessed_combinations", "worst_case_basis", "incompatible_assumptions", "reassessment_trigger" ] } ], "data_elements": [ { "id": "project-envelope-data-1", "name": "Assessed project envelope answer group 1", "description": "Candidate group: purpose, site_ref, design_revision, project_description_ref, revision_date. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "project-envelope-data-2", "name": "Assessed project envelope answer group 2", "description": "Candidate group: phase, quantity, unit, estimation_method, range, source_ref. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "project-envelope-data-3", "name": "Assessed project envelope answer group 3", "description": "Candidate group: parameter_bounds, assessed_combinations, worst_case_basis, incompatible_assumptions, reassessment_trigger. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "project-envelope-artifact", "name": "Assessed proposal snapshot", "description": "Versioned evidence for assessed project envelope. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "alternatives", "name": "Alternatives and option reasoning", "description": "Compare documented options on a consistent basis. Record the no-project scenario distinctly and justify any limits on the alternatives examined.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "alternatives-q-1", "text": "Which location, design, technology or scale alternatives were studied and which were excluded with reasons?", "kind": "composition", "answer_data": [ "alternatives-data-1", "alternative_ids", "option_description_refs", "exclusion_reasons", "feasibility_basis" ] }, { "id": "alternatives-q-2", "text": "What environmental differences between options are supported on comparable assumptions?", "kind": "measurement", "answer_data": [ "alternatives-data-2", "option_pair", "receptor_ref", "effect_comparison", "common_baseline", "uncertainty", "tradeoffs" ] }, { "id": "alternatives-q-3", "text": "What reasons support the preferred option and what remains unresolved about the no-action comparison?", "kind": "decision", "answer_data": [ "alternatives-data-3", "preferred_option", "reasoning_ref", "no_action_ref", "unresolved_tradeoffs", "decision_role" ] } ], "data_elements": [ { "id": "alternatives-data-1", "name": "Alternatives and option reasoning answer group 1", "description": "Candidate group: alternative_ids, option_description_refs, exclusion_reasons, feasibility_basis. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "alternatives-data-2", "name": "Alternatives and option reasoning answer group 2", "description": "Candidate group: option_pair, receptor_ref, effect_comparison, common_baseline, uncertainty, tradeoffs. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "alternatives-data-3", "name": "Alternatives and option reasoning answer group 3", "description": "Candidate group: preferred_option, reasoning_ref, no_action_ref, unresolved_tradeoffs, decision_role. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "alternatives-artifact", "name": "Alternatives comparison record", "description": "Versioned evidence for alternatives and option reasoning. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "evidence-bundle", "name": "Baseline and prediction evidence", "description": "Distinguish observed conditions, counterfactual assumptions and assessed effects.", "rationale": "Groups related evidence and decisions within the single assessment case; this grouping is a local research design rather than a mandated legal hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "layers": [ { "id": "baseline-layer", "name": "Baseline and counterfactual", "description": "Assessment-specific context for baseline and counterfactual. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "baseline-observations", "name": "Baseline observations", "description": "Link observations to their methods, provenance and representativeness. Evidence custody is external; a case records assessed relevance and limitations.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "baseline-observations-q-1", "text": "Which observations establish current receptor conditions and who produced each dataset?", "kind": "provenance", "answer_data": [ "baseline-observations-data-1", "dataset_ref", "revision", "producer", "method", "sampling_design", "observation_period" ] }, { "id": "baseline-observations-q-2", "text": "How are quantities, units, detection limits and uncertainty retained for baseline observations?", "kind": "measurement", "answer_data": [ "baseline-observations-data-2", "observation_ref", "value", "unit", "detection_limit", "uncertainty", "quality_flag" ] }, { "id": "baseline-observations-q-3", "text": "What seasonal, geographic or sampling gaps limit baseline representativeness?", "kind": "quality", "answer_data": [ "baseline-observations-data-3", "coverage_gap", "bias_risk", "age", "representativeness_assessment", "supplementary_study_ref" ] } ], "data_elements": [ { "id": "baseline-observations-data-1", "name": "Baseline observations answer group 1", "description": "Candidate group: dataset_ref, revision, producer, method, sampling_design, observation_period. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "baseline-observations-data-2", "name": "Baseline observations answer group 2", "description": "Candidate group: observation_ref, value, unit, detection_limit, uncertainty, quality_flag. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "baseline-observations-data-3", "name": "Baseline observations answer group 3", "description": "Candidate group: coverage_gap, bias_risk, age, representativeness_assessment, supplementary_study_ref. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "baseline-observations-artifact", "name": "Baseline evidence index", "description": "Versioned evidence for baseline observations. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "future-baseline", "name": "Baseline evolution without the proposal", "description": "Describe the counterfactual trajectory separately from project predictions and retain competing assumptions where evidence is insufficient.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "future-baseline-q-1", "text": "What future conditions are assumed without implementation of this proposal?", "kind": "definition", "answer_data": [ "future-baseline-data-1", "scenario_id", "baseline_ref", "forecast_period", "assumed_trends", "supporting_evidence" ] }, { "id": "future-baseline-q-2", "text": "Which existing or approved developments and environmental trends influence the counterfactual?", "kind": "relationship", "answer_data": [ "future-baseline-data-2", "external_project_refs", "approval_status", "trend_refs", "included_contributions", "exclusion_reasons" ] }, { "id": "future-baseline-q-3", "text": "Which alternative counterfactual assumptions materially change the comparison?", "kind": "quality", "answer_data": [ "future-baseline-data-3", "assumption_set", "sensitivity_result", "uncertainty_range", "information_gap", "reviewer" ] } ], "data_elements": [ { "id": "future-baseline-data-1", "name": "Baseline evolution without the proposal answer group 1", "description": "Candidate group: scenario_id, baseline_ref, forecast_period, assumed_trends, supporting_evidence. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "future-baseline-data-2", "name": "Baseline evolution without the proposal answer group 2", "description": "Candidate group: external_project_refs, approval_status, trend_refs, included_contributions, exclusion_reasons. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "future-baseline-data-3", "name": "Baseline evolution without the proposal answer group 3", "description": "Candidate group: assumption_set, sensitivity_result, uncertainty_range, information_gap, reviewer. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "future-baseline-artifact", "name": "Counterfactual scenario note", "description": "Versioned evidence for baseline evolution without the proposal. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "prediction-layer", "name": "Methods and significance", "description": "Assessment-specific context for methods and significance. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "prediction-method", "name": "Prediction method and reproducibility", "description": "Retain the causal pathway and method behind an asserted effect. The case does not own a simulation engine or certify a consultant model.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "prediction-method-q-1", "text": "What method links each project action to the receptor response?", "kind": "process", "answer_data": [ "prediction-method-data-1", "action_ref", "pathway", "receptor_ref", "method_ref", "model_version", "assumptions" ] }, { "id": "prediction-method-q-2", "text": "What calibration, validation or expert review supports the method for this study domain?", "kind": "validation", "answer_data": [ "prediction-method-data-2", "validation_evidence", "applicability_limits", "reviewer", "reproducibility_state", "failed_checks" ] }, { "id": "prediction-method-q-3", "text": "Which input versions and transformations produced the prediction submitted for review?", "kind": "provenance", "answer_data": [ "prediction-method-data-3", "input_refs", "revision_pins", "transformation_refs", "run_ref", "output_ref", "attribution" ] } ], "data_elements": [ { "id": "prediction-method-data-1", "name": "Prediction method and reproducibility answer group 1", "description": "Candidate group: action_ref, pathway, receptor_ref, method_ref, model_version, assumptions. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "prediction-method-data-2", "name": "Prediction method and reproducibility answer group 2", "description": "Candidate group: validation_evidence, applicability_limits, reviewer, reproducibility_state, failed_checks. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "prediction-method-data-3", "name": "Prediction method and reproducibility answer group 3", "description": "Candidate group: input_refs, revision_pins, transformation_refs, run_ref, output_ref, attribution. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "prediction-method-artifact", "name": "Prediction provenance record", "description": "Versioned evidence for prediction method and reproducibility. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "effect-significance", "name": "Effect characterization and significance", "description": "Keep magnitude, sensitivity, probability and significance distinguishable. The local profile records the assessor and reasoning rather than imposing a universal significance formula.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "effect-significance-q-1", "text": "What direction, magnitude, extent, duration and reversibility characterize the predicted effect?", "kind": "measurement", "answer_data": [ "effect-significance-data-1", "effect_id", "receptor_ref", "phase", "direction", "magnitude", "unit", "extent", "duration", "reversibility" ] }, { "id": "effect-significance-q-2", "text": "Which significance criteria and receptor sensitivity support the assigned judgement?", "kind": "classification", "answer_data": [ "effect-significance-data-2", "criteria_ref", "sensitivity_basis", "significance", "assessor", "reasoning", "threshold_context" ] }, { "id": "effect-significance-q-3", "text": "How do uncertainty and contrary evidence affect confidence in the significance judgement?", "kind": "quality", "answer_data": [ "effect-significance-data-3", "probability_basis", "confidence", "uncertainty", "contrary_evidence_refs", "sensitivity_results" ] } ], "data_elements": [ { "id": "effect-significance-data-1", "name": "Effect characterization and significance answer group 1", "description": "Candidate group: effect_id, receptor_ref, phase, direction, magnitude, unit, extent, duration, reversibility. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "effect-significance-data-2", "name": "Effect characterization and significance answer group 2", "description": "Candidate group: criteria_ref, sensitivity_basis, significance, assessor, reasoning, threshold_context. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "effect-significance-data-3", "name": "Effect characterization and significance answer group 3", "description": "Candidate group: probability_basis, confidence, uncertainty, contrary_evidence_refs, sensitivity_results. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "effect-significance-artifact", "name": "Effect assessment register", "description": "Versioned evidence for effect characterization and significance. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "effects-bundle", "name": "Interactions and mitigation", "description": "Test combined effects and the assumptions behind measures and residual effects.", "rationale": "Groups related evidence and decisions within the single assessment case; this grouping is a local research design rather than a mandated legal hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "layers": [ { "id": "interactions-layer", "name": "Cumulative and climate context", "description": "Assessment-specific context for cumulative and climate context. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "cumulative-effects", "name": "Cumulative effects and interactions", "description": "Review combined effects and interacting receptors within a declared scenario. Listing nearby projects alone is insufficient evidence of a cumulative assessment.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "cumulative-effects-q-1", "text": "Which other projects and effect pathways are included in the cumulative scenario?", "kind": "relationship", "answer_data": [ "cumulative-effects-data-1", "project_refs", "status_dates", "pathway_refs", "spatial_overlap", "temporal_overlap", "exclusions" ] }, { "id": "cumulative-effects-q-2", "text": "How are interactions and combined effects assessed without double counting the baseline?", "kind": "process", "answer_data": [ "cumulative-effects-data-2", "combination_method", "baseline_allocation", "interaction_assumptions", "double_count_checks" ] }, { "id": "cumulative-effects-q-3", "text": "What combined significance and uncertainty are reported for shared receptors?", "kind": "quality", "answer_data": [ "cumulative-effects-data-3", "receptor_ref", "combined_effect", "significance_basis", "data_gaps", "confidence", "review_ref" ] } ], "data_elements": [ { "id": "cumulative-effects-data-1", "name": "Cumulative effects and interactions answer group 1", "description": "Candidate group: project_refs, status_dates, pathway_refs, spatial_overlap, temporal_overlap, exclusions. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "cumulative-effects-data-2", "name": "Cumulative effects and interactions answer group 2", "description": "Candidate group: combination_method, baseline_allocation, interaction_assumptions, double_count_checks. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "cumulative-effects-data-3", "name": "Cumulative effects and interactions answer group 3", "description": "Candidate group: receptor_ref, combined_effect, significance_basis, data_gaps, confidence, review_ref. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "cumulative-effects-artifact", "name": "Cumulative effects scenario", "description": "Versioned evidence for cumulative effects and interactions. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "climate-and-hazards", "name": "Climate and major hazard context", "description": "Address emissions and climate vulnerability separately; relevant major accident and disaster effects are considered at assessment and policy level only.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "climate-and-hazards-q-1", "text": "What climate-related effects are attributed to the proposal and within what accounting boundary?", "kind": "measurement", "answer_data": [ "climate-and-hazards-data-1", "emission_estimates", "units", "period", "boundary", "method_ref", "uncertainty" ] }, { "id": "climate-and-hazards-q-2", "text": "Which climate scenarios and relevant accident or disaster contexts test project vulnerability?", "kind": "constraint", "answer_data": [ "climate-and-hazards-data-2", "scenario_refs", "hazard_categories", "vulnerability_basis", "affected_receptors", "limitations" ] }, { "id": "climate-and-hazards-q-3", "text": "Which specialist risk assessments and resilience commitments are referenced for environmental review?", "kind": "relationship", "answer_data": [ "climate-and-hazards-data-3", "risk_assessment_refs", "revision_pins", "coverage_map", "resilience_commitments", "unresolved_interfaces" ] } ], "data_elements": [ { "id": "climate-and-hazards-data-1", "name": "Climate and major hazard context answer group 1", "description": "Candidate group: emission_estimates, units, period, boundary, method_ref, uncertainty. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "climate-and-hazards-data-2", "name": "Climate and major hazard context answer group 2", "description": "Candidate group: scenario_refs, hazard_categories, vulnerability_basis, affected_receptors, limitations. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "climate-and-hazards-data-3", "name": "Climate and major hazard context answer group 3", "description": "Candidate group: risk_assessment_refs, revision_pins, coverage_map, resilience_commitments, unresolved_interfaces. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "climate-and-hazards-artifact", "name": "Climate and hazard assessment interface", "description": "Versioned evidence for climate and major hazard context. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "measures-layer", "name": "Measures and residual effects", "description": "Assessment-specific context for measures and residual effects. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "mitigation-commitments", "name": "Mitigation commitments", "description": "Track measures by effect, responsible role and evidence of feasibility. Proposed, adopted and implemented states remain distinct.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "mitigation-commitments-q-1", "text": "Which measure addresses each effect and what avoidance or reduction rationale supports it?", "kind": "requirement", "answer_data": [ "mitigation-commitments-data-1", "measure_id", "effect_refs", "measure_type", "rationale", "alternatives_considered" ] }, { "id": "mitigation-commitments-q-2", "text": "Who is responsible for delivering each commitment and where is its authority or funding basis recorded?", "kind": "ownership", "answer_data": [ "mitigation-commitments-data-2", "responsible_role", "commitment_ref", "implementation_dependency", "funding_evidence", "acceptance_state" ] }, { "id": "mitigation-commitments-q-3", "text": "When must each measure operate and what evidence can demonstrate delivery?", "kind": "temporal", "answer_data": [ "mitigation-commitments-data-3", "phase", "milestone", "duration", "performance_criterion", "verification_ref", "failure_response_ref" ] } ], "data_elements": [ { "id": "mitigation-commitments-data-1", "name": "Mitigation commitments answer group 1", "description": "Candidate group: measure_id, effect_refs, measure_type, rationale, alternatives_considered. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "mitigation-commitments-data-2", "name": "Mitigation commitments answer group 2", "description": "Candidate group: responsible_role, commitment_ref, implementation_dependency, funding_evidence, acceptance_state. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "mitigation-commitments-data-3", "name": "Mitigation commitments answer group 3", "description": "Candidate group: phase, milestone, duration, performance_criterion, verification_ref, failure_response_ref. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "mitigation-commitments-artifact", "name": "Mitigation commitments schedule", "description": "Versioned evidence for mitigation commitments. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "residual-effects", "name": "Residual effects and measure uncertainty", "description": "Record effects remaining after assumed measures and preserve dependencies on uncertain effectiveness. Offsetting is not presumed feasible or legally acceptable.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "residual-effects-q-1", "text": "What residual effect is predicted after each specified measure and against which baseline?", "kind": "measurement", "answer_data": [ "residual-effects-data-1", "effect_ref", "measure_refs", "residual_value", "unit", "baseline_ref", "effectiveness_assumptions" ] }, { "id": "residual-effects-q-2", "text": "What residual significance and unresolved tradeoffs remain for the examining authority?", "kind": "decision", "answer_data": [ "residual-effects-data-2", "residual_significance", "criteria_ref", "tradeoffs", "unresolved_adverse_effects", "reviewer" ] }, { "id": "residual-effects-q-3", "text": "What happens to the assessment if a measure or proposed offset proves unavailable or ineffective?", "kind": "exception", "answer_data": [ "residual-effects-data-3", "failure_scenario", "feasibility_evidence", "alternative_measure_ref", "reassessment_need", "decision_dependency" ] } ], "data_elements": [ { "id": "residual-effects-data-1", "name": "Residual effects and measure uncertainty answer group 1", "description": "Candidate group: effect_ref, measure_refs, residual_value, unit, baseline_ref, effectiveness_assumptions. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "residual-effects-data-2", "name": "Residual effects and measure uncertainty answer group 2", "description": "Candidate group: residual_significance, criteria_ref, tradeoffs, unresolved_adverse_effects, reviewer. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "residual-effects-data-3", "name": "Residual effects and measure uncertainty answer group 3", "description": "Candidate group: failure_scenario, feasibility_evidence, alternative_measure_ref, reassessment_need, decision_dependency. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "residual-effects-artifact", "name": "Residual effects review", "description": "Versioned evidence for residual effects and measure uncertainty. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "participation-bundle", "name": "Information and participation", "description": "Preserve report identity, accessible participation and traceable consultation issues.", "rationale": "Groups related evidence and decisions within the single assessment case; this grouping is a local research design rather than a mandated legal hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006" ], "layers": [ { "id": "disclosure-layer", "name": "Report and participation arrangements", "description": "Assessment-specific context for report and participation arrangements. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ], "findings": [ { "id": "report-package", "name": "Report and accessible summary", "description": "Index the assessed report, supporting studies and understandable summary as related revisions. A report is one input to the procedure, not its conclusion.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "questions": [ { "id": "report-package-q-1", "text": "Which report revision, appendices and datasets constitute the submitted assessment package?", "kind": "composition", "answer_data": [ "report-package-data-1", "report_id", "revision", "appendix_refs", "dataset_refs", "completeness_map" ] }, { "id": "report-package-q-2", "text": "Who prepared and checked the report and what evidence supports relevant competence?", "kind": "validation", "answer_data": [ "report-package-data-2", "author_roles", "competence_evidence", "quality_review_ref", "limitations", "approval_status" ] }, { "id": "report-package-q-3", "text": "How does the non-technical summary preserve material adverse effects and uncertainty for its intended audience?", "kind": "access", "answer_data": [ "report-package-data-3", "summary_ref", "language", "accessibility_format", "report_revision_link", "omissions_review" ] } ], "data_elements": [ { "id": "report-package-data-1", "name": "Report and accessible summary answer group 1", "description": "Candidate group: report_id, revision, appendix_refs, dataset_refs, completeness_map. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "report-package-data-2", "name": "Report and accessible summary answer group 2", "description": "Candidate group: author_roles, competence_evidence, quality_review_ref, limitations, approval_status. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "report-package-data-3", "name": "Report and accessible summary answer group 3", "description": "Candidate group: summary_ref, language, accessibility_format, report_revision_link, omissions_review. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "report-package-artifact", "name": "Assessment report package index", "description": "Versioned evidence for report and accessible summary. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "participation-design", "name": "Participation arrangements", "description": "Capture applicable notice and access arrangements with evidence of an effective opportunity to comment. Generic public availability is not proof of adequate participation.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "participation-design-q-1", "text": "Which authorities and affected public groups have an opportunity to participate in this case?", "kind": "relationship", "answer_data": [ "participation-design-data-1", "consultee_groups", "identification_basis", "affected_area", "authority_refs", "engagement_gaps" ] }, { "id": "participation-design-q-2", "text": "What notice and response periods apply and how were extensions or changed documents handled?", "kind": "temporal", "answer_data": [ "participation-design-data-2", "notice_ref", "opening_time", "closing_time", "calendar_basis", "extension_ref", "document_change_notice" ] }, { "id": "participation-design-q-3", "text": "What information and accessible channels were available while meaningful options remained open?", "kind": "access", "answer_data": [ "participation-design-data-3", "disclosed_revision_refs", "channels", "languages", "accessibility_support", "availability_evidence", "restrictions_basis" ] } ], "data_elements": [ { "id": "participation-design-data-1", "name": "Participation arrangements answer group 1", "description": "Candidate group: consultee_groups, identification_basis, affected_area, authority_refs, engagement_gaps. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "participation-design-data-2", "name": "Participation arrangements answer group 2", "description": "Candidate group: notice_ref, opening_time, closing_time, calendar_basis, extension_ref, document_change_notice. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "participation-design-data-3", "name": "Participation arrangements answer group 3", "description": "Candidate group: disclosed_revision_refs, channels, languages, accessibility_support, availability_evidence, restrictions_basis. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "participation-design-artifact", "name": "Participation arrangements record", "description": "Versioned evidence for participation arrangements. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "responses-layer", "name": "Responses and transboundary links", "description": "Assessment-specific context for responses and transboundary links. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "consultation-responses", "name": "Consultation issues and responses", "description": "Retain submissions and a traceable response to substantive issues, including disagreement. An automated summary does not replace the submitted record or authority consideration.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "consultation-responses-q-1", "text": "Which submissions and consultation events raised each substantive issue?", "kind": "evidence", "answer_data": [ "consultation-responses-data-1", "submission_refs", "event_refs", "issue_id", "attribution", "receipt_time", "duplicate_group" ] }, { "id": "consultation-responses-q-2", "text": "How was each issue considered and where is the resulting change or reasoned response recorded?", "kind": "decision", "answer_data": [ "consultation-responses-data-2", "issue_ref", "response_ref", "considering_role", "design_change_ref", "unresolved_disagreement" ] }, { "id": "consultation-responses-q-3", "text": "Which personal or sensitive information needs a controlled rendition while preserving a usable public issue record?", "kind": "privacy", "answer_data": [ "consultation-responses-data-3", "restricted_fields", "public_rendition_ref", "restriction_basis", "review_role", "retention_policy_ref" ] } ], "data_elements": [ { "id": "consultation-responses-data-1", "name": "Consultation issues and responses answer group 1", "description": "Candidate group: submission_refs, event_refs, issue_id, attribution, receipt_time, duplicate_group. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "consultation-responses-data-2", "name": "Consultation issues and responses answer group 2", "description": "Candidate group: issue_ref, response_ref, considering_role, design_change_ref, unresolved_disagreement. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "consultation-responses-data-3", "name": "Consultation issues and responses answer group 3", "description": "Candidate group: restricted_fields, public_rendition_ref, restriction_basis, review_role, retention_policy_ref. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "consultation-responses-artifact", "name": "Consultation issue-response matrix", "description": "Versioned evidence for consultation issues and responses. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "transboundary-process", "name": "Transboundary procedure interface", "description": "Track evidence of state-to-state notification and participation where applicable. Local case operators cannot create diplomatic authority through a workflow status.", "source_refs": [ "SRC-003", "SRC-001" ], "questions": [ { "id": "transboundary-process-q-1", "text": "Which potentially affected jurisdictions and applicable instruments trigger transboundary consideration?", "kind": "classification", "answer_data": [ "transboundary-process-data-1", "origin_jurisdiction", "affected_jurisdictions", "pathway_refs", "instrument_refs", "applicability_review" ] }, { "id": "transboundary-process-q-2", "text": "What authorized notifications, responses and consultation exchanges are evidenced?", "kind": "event", "answer_data": [ "transboundary-process-data-2", "notification_refs", "sender_role", "receipt_evidence", "participation_response", "exchange_refs", "agreed_period" ] }, { "id": "transboundary-process-q-3", "text": "How were affected-state public comments, translations and final information linked back to the domestic case?", "kind": "access", "answer_data": [ "transboundary-process-data-3", "public_comment_refs", "translation_refs", "domestic_issue_links", "decision_transmission_ref", "participation_gaps" ] } ], "data_elements": [ { "id": "transboundary-process-data-1", "name": "Transboundary procedure interface answer group 1", "description": "Candidate group: origin_jurisdiction, affected_jurisdictions, pathway_refs, instrument_refs, applicability_review. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-001" ] }, { "id": "transboundary-process-data-2", "name": "Transboundary procedure interface answer group 2", "description": "Candidate group: notification_refs, sender_role, receipt_evidence, participation_response, exchange_refs, agreed_period. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-001" ] }, { "id": "transboundary-process-data-3", "name": "Transboundary procedure interface answer group 3", "description": "Candidate group: public_comment_refs, translation_refs, domestic_issue_links, decision_transmission_ref, participation_gaps. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-001" ] } ], "artifacts": [ { "id": "transboundary-process-artifact", "name": "Transboundary exchange index", "description": "Versioned evidence for transboundary procedure interface. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-003", "SRC-001" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "conclusion-bundle", "name": "Examination and continuity", "description": "Bind examined evidence to competent conclusions and retain follow-up interfaces.", "rationale": "Groups related evidence and decisions within the single assessment case; this grouping is a local research design rather than a mandated legal hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "layers": [ { "id": "examination-layer", "name": "Authority examination and conclusion", "description": "Assessment-specific context for authority examination and conclusion. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "authority-examination", "name": "Examination and supplementary information", "description": "Document the authority review of evidence and unresolved deficiencies. The local operation tracks review evidence rather than legally determining report adequacy.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "authority-examination-q-1", "text": "Which report contents and consultation evidence were examined and by whom?", "kind": "validation", "answer_data": [ "authority-examination-data-1", "examiner_role", "competence_ref", "reviewed_revisions", "review_scope", "review_ref" ] }, { "id": "authority-examination-q-2", "text": "Which deficiencies led to supplementary information requests and what responses address them?", "kind": "requirement", "answer_data": [ "authority-examination-data-2", "deficiency_id", "request_ref", "response_ref", "adequacy_review", "open_issue" ] }, { "id": "authority-examination-q-3", "text": "What conflicts of interest or role overlap require an independently evidenced arrangement?", "kind": "authority", "answer_data": [ "authority-examination-data-3", "role_overlap", "conflict_declaration_ref", "separation_arrangement", "reviewer", "unresolved_conflict" ] } ], "data_elements": [ { "id": "authority-examination-data-1", "name": "Examination and supplementary information answer group 1", "description": "Candidate group: examiner_role, competence_ref, reviewed_revisions, review_scope, review_ref. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "authority-examination-data-2", "name": "Examination and supplementary information answer group 2", "description": "Candidate group: deficiency_id, request_ref, response_ref, adequacy_review, open_issue. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "authority-examination-data-3", "name": "Examination and supplementary information answer group 3", "description": "Candidate group: role_overlap, conflict_declaration_ref, separation_arrangement, reviewer, unresolved_conflict. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "authority-examination-artifact", "name": "Examination and deficiency record", "description": "Versioned evidence for examination and supplementary information. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "conclusion-and-consent", "name": "Reasoned conclusion and consent linkage", "description": "The competent conclusion, its currency and its integration into a separate consent decision are distinct assertions. A favorable study or completed local checklist grants no permission.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "conclusion-and-consent-q-1", "text": "What reasoned conclusion on significant effects was issued and which evidence revisions support it?", "kind": "decision", "answer_data": [ "conclusion-and-consent-data-1", "conclusion_ref", "issuer", "conclusion_date", "effect_refs", "evidence_revision_refs", "reasoning" ] }, { "id": "conclusion-and-consent-q-2", "text": "What review establishes that the conclusion remains applicable to the proposal at the decision date?", "kind": "temporal", "answer_data": [ "conclusion-and-consent-data-2", "currency_review_ref", "proposal_revision", "review_date", "expiry_rule", "new_information" ] }, { "id": "conclusion-and-consent-q-3", "text": "Which consent or refusal record incorporates or addresses the conclusion and consultation outcome?", "kind": "relationship", "answer_data": [ "conclusion-and-consent-data-3", "decision_ref", "decision_type", "conditions_refs", "integration_evidence", "public_notice_ref", "review_route_ref" ] } ], "data_elements": [ { "id": "conclusion-and-consent-data-1", "name": "Reasoned conclusion and consent linkage answer group 1", "description": "Candidate group: conclusion_ref, issuer, conclusion_date, effect_refs, evidence_revision_refs, reasoning. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "conclusion-and-consent-data-2", "name": "Reasoned conclusion and consent linkage answer group 2", "description": "Candidate group: currency_review_ref, proposal_revision, review_date, expiry_rule, new_information. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "conclusion-and-consent-data-3", "name": "Reasoned conclusion and consent linkage answer group 3", "description": "Candidate group: decision_ref, decision_type, conditions_refs, integration_evidence, public_notice_ref, review_route_ref. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "conclusion-and-consent-artifact", "name": "Conclusion and decision cross-reference", "description": "Versioned evidence for reasoned conclusion and consent linkage. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "continuity-layer", "name": "Monitoring and change", "description": "Assessment-specific context for monitoring and change. External master records remain authoritative.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "findings": [ { "id": "monitoring-interface", "name": "Monitoring and follow-up linkage", "description": "Record commitments and relevant results from external monitoring, including post-project analysis where applicable. The EIA case does not operate sensors, enforce permits or declare compliance.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "monitoring-interface-q-1", "text": "Which effects or measures require follow-up and what makes the selected parameters proportionate?", "kind": "requirement", "answer_data": [ "monitoring-interface-data-1", "effect_refs", "measure_refs", "parameter", "method_ref", "frequency", "duration", "monitoring_basis" ] }, { "id": "monitoring-interface-q-2", "text": "Which role and external programme own monitoring delivery, reporting and remedial action?", "kind": "ownership", "answer_data": [ "monitoring-interface-data-2", "programme_ref", "responsible_role", "reporting_route", "remedial_authority_ref", "handover_evidence" ] }, { "id": "monitoring-interface-q-3", "text": "What observed results differ from predictions and what review or escalation was recorded?", "kind": "evidence", "answer_data": [ "monitoring-interface-data-3", "monitoring_result_refs", "prediction_refs", "observed_difference", "uncertainty", "trigger", "review_ref" ] } ], "data_elements": [ { "id": "monitoring-interface-data-1", "name": "Monitoring and follow-up linkage answer group 1", "description": "Candidate group: effect_refs, measure_refs, parameter, method_ref, frequency, duration, monitoring_basis. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "monitoring-interface-data-2", "name": "Monitoring and follow-up linkage answer group 2", "description": "Candidate group: programme_ref, responsible_role, reporting_route, remedial_authority_ref, handover_evidence. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "monitoring-interface-data-3", "name": "Monitoring and follow-up linkage answer group 3", "description": "Candidate group: monitoring_result_refs, prediction_refs, observed_difference, uncertainty, trigger, review_ref. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "monitoring-interface-artifact", "name": "Monitoring handover and results index", "description": "Versioned evidence for monitoring and follow-up linkage. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "change-and-retirement", "name": "Change, review and record continuity", "description": "Changes and new information may require review of the route or evidence. Case retirement and record disposal do not cancel externally issued decisions or erase lawful review needs.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "change-and-retirement-q-1", "text": "Which proposal change, withdrawal or new information triggers a new revision, related case or reassessment request?", "kind": "lifecycle", "answer_data": [ "change-and-retirement-data-1", "trigger_ref", "change_type", "affected_scope", "case_link", "authorized_route_review" ] }, { "id": "change-and-retirement-q-2", "text": "How are superseded reports and exchanged records linked without presenting obsolete conclusions as current?", "kind": "interoperability", "answer_data": [ "change-and-retirement-data-2", "supersession_links", "revision_pins", "mapping_profile", "loss_report", "current_view_rule" ] }, { "id": "change-and-retirement-q-3", "text": "What retention, review hold and authorized disposition apply to this case and its controlled renditions?", "kind": "retention", "answer_data": [ "change-and-retirement-data-3", "record_class", "retention_basis", "hold_ref", "disposition_authority", "payload_action", "minimal_tombstone" ] } ], "data_elements": [ { "id": "change-and-retirement-data-1", "name": "Change, review and record continuity answer group 1", "description": "Candidate group: trigger_ref, change_type, affected_scope, case_link, authorized_route_review. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "change-and-retirement-data-2", "name": "Change, review and record continuity answer group 2", "description": "Candidate group: supersession_links, revision_pins, mapping_profile, loss_report, current_view_rule. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "change-and-retirement-data-3", "name": "Change, review and record continuity answer group 3", "description": "Candidate group: record_class, retention_basis, hold_ref, disposition_authority, payload_action, minimal_tombstone. Preserve unknown, not applicable with reason, and contested values distinctly. Nested typing and conditional requirements await profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "change-and-retirement-artifact", "name": "Change and disposition record", "description": "Versioned evidence for change, review and record continuity. A stored copy does not become the issuing authority or underlying dataset master.", "media_or_form": [ "structured record", "document or external record reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus issuer namespace first; governed global identifier second; Dimension-issued UUID or ULID third. Keep revision, digest and publication rendition separate; dates and filenames are not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-case", "name": "Register assessment case", "description": "Proposed local operation; unimplemented. Create an assessment envelope with explicit route uncertainty.", "inputs": [ "Project master reference and revision", "Issuer namespace and case identifier", "Profile and steward role" ], "outputs": [ "Registered case or duplicate candidate report", "Refusal record for missing authority, evidence or revision mismatch" ], "preconditions": [ "Authorized case role and pinned current revision", "Applicable profile and access policy resolved", "Identity resolution complete" ], "effects": [ "Bind proposal snapshot and record initial stage without inferring EIA requirement", "Append attributable local revision; preserve previous evidence subject to lawful retention", "No external transmission, legal decision or operational enforcement" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "record-route", "name": "Record screening and scope evidence", "description": "Proposed local operation; unimplemented. Attach an already evidenced route determination or scoping record.", "inputs": [ "Authoritative determination reference", "Criteria and reasons", "Scoping applicability and revision" ], "outputs": [ "Route evidence index", "Unresolved scope or authority issues", "Refusal record for missing authority, evidence or revision mismatch" ], "preconditions": [ "Authorized case role and pinned current revision", "Applicable profile and access policy resolved", "Issuer and record authenticity reviewed", "No generated determination substituted for source" ], "effects": [ "Link determination and qualified scope to this case", "Append attributable local revision; preserve previous evidence subject to lawful retention", "No external transmission, legal decision or operational enforcement" ], "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "index-assessment-evidence", "name": "Index assessment evidence", "description": "Proposed local operation; unimplemented. Preserve baseline, prediction and mitigation lineage for review.", "inputs": [ "Dataset and report revisions", "Effect and measure links", "Methods and uncertainty" ], "outputs": [ "Traceability index", "Missing input and incompatible revision report", "Refusal record for missing authority, evidence or revision mismatch" ], "preconditions": [ "Authorized case role and pinned current revision", "Applicable profile and access policy resolved", "No unauthorized alteration of source measurements" ], "effects": [ "Record provenance and contrary material without certifying scientific validity", "Append attributable local revision; preserve previous evidence subject to lawful retention", "No external transmission, legal decision or operational enforcement" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "reconcile-consultation", "name": "Reconcile consultation issues", "description": "Proposed local operation; unimplemented. Build a reviewable local issue-response mapping.", "inputs": [ "Authorized submission references", "Response evidence", "Disclosure and privacy policy" ], "outputs": [ "Issue-response mapping", "Unaddressed issue list", "Controlled public rendition proposal", "Refusal record for missing authority, evidence or revision mismatch" ], "preconditions": [ "Authorized case role and pinned current revision", "Applicable profile and access policy resolved", "Preserve original submissions and source attribution", "Publication authority is separate" ], "effects": [ "Record suggested mappings for review; do not send responses or dismiss objections", "Append attributable local revision; preserve previous evidence subject to lawful retention", "No external transmission, legal decision or operational enforcement" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "bind-conclusion", "name": "Bind conclusion and decision", "description": "Proposed local operation; unimplemented. Link an issued conclusion and an optional separate development decision.", "inputs": [ "Conclusion revision and issuer", "Evidence and currency review", "Optional decision record and conditions" ], "outputs": [ "Conclusion-to-evidence map", "Decision integration gap report", "Refusal record for missing authority, evidence or revision mismatch" ], "preconditions": [ "Authorized case role and pinned current revision", "Applicable profile and access policy resolved", "Competent reviewer confirms identity and currency evidence" ], "effects": [ "Record only evidenced stage and links; absent consent remains absent", "Append attributable local revision; preserve previous evidence subject to lawful retention", "No external transmission, legal decision or operational enforcement" ], "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "review-case-change", "name": "Review case change and follow-up", "description": "Proposed local operation; unimplemented. Identify evidence needing renewed review after a change or monitoring result.", "inputs": [ "Changed proposal or new information", "Monitoring or review record references", "Retention and hold policy" ], "outputs": [ "Affected evidence list", "Reassessment request draft", "Authorized continuity or disposition proposal", "Refusal record for missing authority, evidence or revision mismatch" ], "preconditions": [ "Authorized case role and pinned current revision", "Applicable profile and access policy resolved", "Responsible reviewer validates trigger and scope", "No autonomous legal reopening or payload deletion" ], "effects": [ "Flag affected assertions and preserve supersession links for authorized action", "Append attributable local revision; preserve previous evidence subject to lawful retention", "No external transmission, legal decision or operational enforcement" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] } ], "composition": [ { "target": "WM-ACT-034", "relation": "ALIGN", "purpose": "Proposed conceptual alignment to Assessment / Evaluation from the registry parent. Pin and review before adoption; no existing inheritance or runtime implementation is claimed.", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "Project master record", "relation": "REFERENCE", "purpose": "Resolve identity and immutable proposal revision. The adopting profile supplies the actual system binding; project execution remains outside this case.", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "Strategic or specialist assessment record", "relation": "REFERENCE", "purpose": "Reuse relevant pinned evidence and report differences without importing another assessment lifecycle.", "required": false, "source_refs": [ "SRC-005", "SRC-001" ] }, { "target": "Development consent or refusal record", "relation": "REFERENCE", "purpose": "Bind the competent decision when it exists, including conditions and reasons; never require consent for an open, screened-out or withdrawn case.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "Environmental monitoring programme", "relation": "REFERENCE", "purpose": "Link applicable follow-up commitments and results; monitoring operation and compliance enforcement remain externally mastered.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "target": "PROV-O", "relation": "ALIGN", "purpose": "Candidate attribution and derivation mapping only; no conformance implementation or truth certification.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "RFC 3339", "relation": "ALIGN", "purpose": "Timestamp representation alignment. Legal date calculations and notice effectiveness remain profile-specific.", "required": false, "source_refs": [ "SRC-007" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Designate an accountable steward role and the separate competent authority, developer and expert roles", "Pin jurisdiction, sector, effective legal profile, conflict controls and escalation route", "Declare project, document, decision and monitoring master bindings with revision semantics", "Declare retention, access, public disclosure, sensitive-location protection and privacy policies", "Supply Name, Type, Specification URL, Storage type URL, Interface URL and Processes URL" ], "namespace_guidance": "Use an adopting Dimension namespace with stable opaque identifiers. Stewardship is assigned to roles, not named companies. Keep case, project, report, observation and decision identifiers distinct.", "registry_links": [ "vr.wm-act-050", "WM-ACT-034 conceptual parent; binding unreviewed" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonical here means a governed local representation, not canonical research assurance. Keep this research reviewable-draft.", "Preserve original units, coordinate reference, precision and source text alongside any normalized value; record transformations.", "Do not collapse unknown, omitted, screened out, not applicable, disputed and no adverse effect into a single empty value.", "Pin project, report and conclusion revisions; preserve predictions separately from observations." ], "patch_rules": [ "Require actor, purpose, source, base revision and attributable change description; reject stale concurrent edits.", "Correct errors by superseding the local assertion and retaining lawful provenance; never rewrite a source determination.", "Route design or scope changes to an authorized reassessment review; do not silently reuse an obsolete conclusion." ], "compatibility_rules": [ "Material changes to scope, significance categories, units or legal route require a versioned profile and impact review.", "External alignments require explicit mappings and loss reports before claiming interoperability; do not invent neighbor identifiers." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with issuer namespace", "Governed global identifier or IRI", "UUID or ULID assigned by the adopting Dimension" ], "timestamp_rule": "Represent known instants using RFC 3339 with seconds and an explicit offset or Z. Keep event time separate from observation and ingestion time. Preserve legal date-only values and unknown precision without inventing midnight or a deadline calendar.", "serial_naming_rule": "Use stable artifact identity plus distinct revision and rendition identifiers; dates and filenames cannot identify the logical artifact. Bind each public summary or redaction to its source revision.", "integrity_rule": "Record digest, algorithm, source location, retrieval time and custody/derivation references. A matching digest proves byte consistency only, not scientific truth, authority, completeness or lawful consent." }, "policies": [ "This is a source-grounded proposed research model with a local self-audit, not independent review, legal advice or a conformance certificate.", "Legal duties and exceptions require a qualified applicable profile. Do not generalize England or EU rules to other jurisdictions.", "Protect personal data and sensitive environmental locations under the applicable policy while maintaining required public access; document restriction reasons and review.", "Never suppress adverse effects, uncertainty, contrary evidence or material objections to favor an outcome.", "Hazard context remains at environmental assessment and policy level; no instructions for dangerous operations are modeled." ], "crud": { "read": [ "Resolve current and historical revision separately; apply recipient access and show evidence status and source limitations." ], "create": [ "Require distinct case identity, project reference, profile and authorized steward; unknown route must remain explicit." ], "update": [ "Authorize per role and scope; check base revision and preserve attribution, conditional requirements and unresolved review issues." ], "delete": [ "Retire or supersede the case separately from disposing payloads. The adopting Dimension records policy and authorized records custodian own retention, legal holds and deletion execution.", "Apply lawful erasure or disposal to controlled payloads and copies when authorized; keep only a lawful minimal tombstone. Do not promise perpetual personal-data history or delete externally mastered project and decision records." ] }, "roles": [ { "name": "Case steward", "responsibilities": [ "Maintain identity, revisions, access and evidence links within assigned authority" ] }, { "name": "Project proponent", "responsibilities": [ "Supply attributable proposal information, alternatives and report references" ] }, { "name": "Assessment expert", "responsibilities": [ "Document methods, competence, uncertainty and study limitations" ] }, { "name": "Examining authority role", "responsibilities": [ "Review adequacy, conflicts, conclusion and applicable legal requirements through authorized procedures" ] }, { "name": "Participation coordinator", "responsibilities": [ "Record accessible participation arrangements and traceable issues without deciding them" ] }, { "name": "Records custodian", "responsibilities": [ "Apply disclosure, restriction, retention and authorized disposition policy" ] }, { "name": "Monitoring liaison", "responsibilities": [ "Link external programme ownership, results and relevant reassessment triggers" ] } ], "access": { "default_rule": "Protect unpublished working material and personal data by role and purpose; provide the public renditions required by the applicable participation and disclosure profile. A default restriction cannot override a legal access right.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Record the specific basis, scope, approving role and review point for each confidentiality or sensitive-location restriction.", "Provide a reasoned and reviewable restricted or redacted rendition where lawful; avoid blanket withholding of the entire case." ], "audit_requirements": [ "Record actor, purpose, scope, revision, authorization and outcome for mutations, disclosure and disposition.", "Reference the adopting audit system; this case does not own generic audit execution or equate a local log with proof of legal service." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Owner and Dimension policies", "AGENTS.md", "Specification boundary, profile and publication holds", "Master bindings and current case revision", "Evidence, permissions and applicable workflow before mutation" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one persistent project EIA case, bounded by selected EU, England and UNECE evidence and conceptual provenance/time alignments. A separate local no-tools self-audit found no critical conflict. Independent review, source/version checks, jurisdiction profiles and executable conformance remain holds; this is a noncanonical reviewable draft.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable case identity is separate from proposal, report and consent identities." }, { "dimension": "lifecycle", "status": "covered", "notes": "Screening-only, pending, withdrawn, examined and superseded states remain possible; no universal linear workflow." }, { "dimension": "relationships", "status": "covered", "notes": "External project, specialist assessment, decision and monitoring masters remain distinct." }, { "dimension": "temporal", "status": "covered", "notes": "Event, observation and ingestion time, study horizons and conclusion currency are separate." }, { "dimension": "provenance", "status": "covered", "notes": "Dataset revisions, method lineage and attributed evidence are explicit." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based case stewardship does not confer scientific or legal competence." }, { "dimension": "validation", "status": "gap", "notes": "Research schema validation is available; nested instance schemas and operational fixtures are not implemented." }, { "dimension": "access", "status": "covered", "notes": "Public participation and controlled renditions require applicable access rules." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Custodian-owned retention and legal holds govern lawful payload disposal and minimal tombstones." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual PROV and time alignments are proposed; mappings and neighbor bindings need testing." }, { "dimension": "direct properties", "status": "covered", "notes": "Case stage, route, jurisdiction, assessed revision and uncertainty are direct nonphysical properties. Environmental quantities describe referenced receptors and studies." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Identify the case by master references and issuing evidence, not by a report title or apparent environmental benefit." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Six proposed local operations have authority and revision preconditions, refusal outputs and limited effects; no automatic consent or enforcement." }, { "dimension": "context and evidence", "status": "covered", "notes": "Regional examples and source support constrain the design; the hierarchy is authored research." }, { "dimension": "independent review", "status": "gap", "notes": "Claude and Grok skipped under the owner waiver; a separate local no-tools self-audit is not a second provider." }, { "dimension": "source verification", "status": "gap", "notes": "Browser content and indexed text support selected claims; direct HTTP not attempted under owner-reported sandbox block and complete version verification remains open." } ], "known_omissions": [ "Independent external review is absent.", "Direct HTTP status, authentic legal acts, treaty participation and amendment applicability remain unverified.", "Jurisdiction-specific thresholds, sector methods, indigenous participation and consent regimes, specialist biodiversity and health methods need additional primary research.", "Nested instance schemas, detailed enumerations, conditional mandatory fields, executable mappings and adversarial case fixtures remain incomplete.", "This candidate does not implement scientific prediction, statutory calendars, legal remedy adjudication or enforcement." ], "conflicts": [], "regional_assumptions": [ "EU consolidated text is a documentation source, not a universal legal regime.", "England guidance is a bounded example with historical references; current national reforms and project applicability require review.", "UNECE indexed text supports selected concepts only; accession, reservations and amendments cannot be inferred from the page.", "No legacy alias or registered previous specification exists; supplement is unreviewed and not an independent provider result." ], "adversarial_checks": [ "A screening-out record cannot be mistaken for consent or completed full EIA.", "An optional formal scoping opinion cannot become a universal mandatory artifact.", "A favorable report, issue count or local completion flag cannot substitute for a competent reasoned conclusion.", "Counterfactual conditions, project predictions and monitoring observations must not be conflated.", "Missing or disputed evidence remains visible; cumulative scenario design cannot hide connected works.", "Record retirement cannot erase applicable review holds or annul external decisions." ] }, "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 assessment case recording a procedure across screening, study, consultation, conclusion and follow-up references. It is not the legal process definition, report, project or consent. Preliminary screening does not assert full legal EIA. The registry standalone-mm value is a record-plane classification, not a subject-kind enum." }, "decisions": [ { "concept": "Case and process boundary", "disposition": "accepted with explicit scope", "rationale": "Stable case identity and revision continuity support entity. The scope expressly distinguishes the legal procedure, and includes screening-only records without claiming full EIA occurred." }, { "concept": "Generic assessment parent", "disposition": "alignment only", "rationale": "The registry parent exists but the relationship ledger has no edges for this model. The authored ALIGN is optional and does not manufacture inheritance or operational bindings." }, { "concept": "Screening and exception authority", "disposition": "accepted with profile qualification", "rationale": "Questions require actual lists, criteria, reasons and competence. A no-EIA-required determination is neither consent nor an automated local model decision." }, { "concept": "Universal scoping opinion", "disposition": "rejected", "rationale": "The scope questions admit requested, required or absent formal opinions. An opinion artifact is a candidate representation rather than a universal instance requirement." }, { "concept": "Whole proposal and alternatives", "disposition": "accepted", "rationale": "Proposal revisions, associated works, flexible design bounds, option comparisons and a distinct no-action scenario constrain fragmentation and incomparable alternatives." }, { "concept": "Baseline, prediction and significance", "disposition": "separated", "rationale": "Observed conditions, counterfactual evolution, modeled effects and significance judgements have separate findings. Units, assumptions, uncertainty and contrary evidence are retained without claiming a universal scoring engine." }, { "concept": "Cumulative, climate and hazard context", "disposition": "accepted at assessment level", "rationale": "Shared receptors, scenario boundaries and interactions are explicit. Climate effects and vulnerability are distinct; hazard references do not supply dangerous operational instructions." }, { "concept": "Mitigation and residual effects", "disposition": "accepted with feasibility limits", "rationale": "Proposed, adopted and delivered measures differ. Residual effects retain effectiveness assumptions, and offset feasibility or acceptability is not presumed." }, { "concept": "Participation and sensitive information", "disposition": "accepted with applicable rights", "rationale": "Notice, access, substantive issues and response evidence are distinguished. Controlled renditions require a reasoned basis, and default restrictions cannot override applicable public access rights." }, { "concept": "Transboundary authority", "disposition": "reference only", "rationale": "Notification and exchanges require actual jurisdiction, instrument and issuer evidence. Local recording cannot confer diplomatic authority or prove treaty applicability." }, { "concept": "Conclusion, consent and follow-up", "disposition": "separated", "rationale": "Report review, reasoned conclusion, currency check and external consent remain distinct. Monitoring results and changed proposals can trigger review but do not import enforcement or automatic legal reopening." }, { "concept": "Proposed local operations", "disposition": "accepted with implementation hold", "rationale": "Six unimplemented functions record or reconcile evidence with role and revision checks. Registration pins input proposal/profile versions; mutations additionally check current case revision. No external action is authorized by their outputs." }, { "concept": "Identity, time and retention", "disposition": "accepted with policy dependency", "rationale": "Master identifiers precede generated identifiers, revisions and renditions stay distinct, and timestamp syntax does not invent date precision. Lawful payload disposal and minimal tombstones qualify historical preservation." }, { "concept": "Nested schemas and bindings", "disposition": "deferred", "rationale": "Optional candidate object groups, conceptual alignments and a required project-master label do not provide an executable instance schema or resolved runtime dependency. Those limitations are visible in coverage and holds." }, { "concept": "Evidence and review limits", "disposition": "limited and held", "rationale": "Five URLs yielded browser text and two UNECE URLs yielded indexed official content after browser failure. Direct HTTP was not attempted. The local self-audit and waiver cannot establish independent review, current-law verification or universal completeness." } ], "publicationHolds": [ "Independent external review is absent. Claude and Grok were skipped with zero attempts under the owner override and existing single-provider waiver; the separate local Codex no-tools self-audit is not an independent second-provider review.", "Live source and version verification remains incomplete. Five sources were browser-readable and two UNECE pages were reviewed through indexed official text after browser opens failed. Direct HTTP was not attempted under the owner-reported sandbox block: no statuses were measured. The coordinator must run check_sources.py; authentic texts, legal versions, treaty participation and amendment applicability remain open.", "Jurisdiction and sector profiles require qualified review before operational use, including current national rules, thresholds, significance methods, participation and consent regimes, privacy, sensitive-location access, retention, exceptions and review routes. No legal or scientific compliance certification is claimed.", "Nested instance schemas, conditional mandatory fields, executable function preconditions, pinned master bindings, PROV mappings and adversarial case fixtures are incomplete. The hierarchy and six local functions are research proposals, not an implemented assessment, permitting or enforcement system.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Restore independent external review before any canonical or publishable-draft promotion.", "Run the coordinator HTTP checker and verify authentic legal acts, relevant national versions, treaty party status and amendment applicability for an adopting profile.", "Research sector-specific methods, Indigenous participation and consent regimes, biodiversity and health assessment methods and current national reforms using additional primary sources.", "Build and test nested schemas and mappings against screened-out, optional-scoping, withdrawn, multi-stage, transboundary, disputed-evidence, changed-project and lawful-disposal cases." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 6 } }