# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-07T08:49:24Z", "synthesisSha256": "2fe7c375bb99dd5b7fc0ab88f0d64d1ed7bb025bd4ac8e086445b9bcce98effc", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-LIV-006", "registryId": "vr.wm-liv-006", "name": "Ecosystem / Biome", "version": "0.3.0-reviewable-draft", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.LIV.ECO" ], "tags": [ "ecosystem", "biome", "phy.liv.eco" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-liv-006-ecosystem-biome/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-liv-006", "model": { "registry_id": "vr.wm-liv-006", "model_id": "WM-LIV-006", "name": "Ecosystem / Biome", "entry_kind": "entity", "purpose": "Describe a delineated ecosystem as a changing biophysical system with qualified class assignments, evidence and assessments.", "scope_statement": "The root is one steward-identified ecological unit with versioned delineations and assertions. Biomes and ecosystem types are externally governed classifier references. Physical processes, extent, condition and capacity context are local; economic valuation, species masters, land rights and physical intervention are external.", "in_scope": [ "Persistent unit identity and versioned spatial extent", "Qualified biome/type assignments, crosswalks and uncertainty", "Biotic and abiotic evidence, ecological processes, condition and change", "Physical capacity context and controlled evidence projections" ], "out_of_scope": [ "Global classifier authoring and universal ecosystem inventory", "Species, specimen, water, soil, weather and climate master lifecycles", "Land ownership, protected-area designation and access-right adjudication", "Monetary valuation, credits, offsets and certified sustainability claims", "Physical restoration, extraction, hazard response and autonomous environmental intervention", "Official collapse-risk assessment algorithms and executable conformance certification" ], "boundary_notes": [ { "neighbor": "Biome and ecosystem-type classifiers", "distinction": "A type is a concept and the unit is a referent. Preserve scheme, release and assertion status; do not confuse biome with realm or create a second classifier root.", "source_refs": [ "SRC-002" ] }, { "neighbor": "Vegetation, wildlife and other biological record masters", "distinction": "Carry composition summaries and supporting references only. Individual populations, taxa and observations retain their own master identities.", "source_refs": [ "SRC-001", "SRC-005" ] }, { "neighbor": "Habitat, protected area and land tenure", "distinction": "A habitat or designated area may overlap a unit but is not automatically coextensive with it. Record stewardship confers no land or resource rights.", "source_refs": [ "SRC-001", "SRC-007" ] }, { "neighbor": "Environmental substrate and climate models", "distinction": "Reference unit-specific setting and observations without owning the source water, soil, terrain, weather or climate record lifecycle.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "Valuation and official accounts", "distinction": "Physical evidence may feed external accounts or valuation, but the unit neither prices services nor certifies an official account.", "source_refs": [ "SRC-003" ] }, { "neighbor": "Risk assessment and operational activities", "distinction": "Reference the assessed type, scope and issuing authority; a local change or milestone does not establish a global risk class or authorize intervention.", "source_refs": [ "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Convention on Biological Diversity, Article 2: Use of Terms", "organization": "Convention on Biological Diversity Secretariat", "url": "https://www.cbd.int/convention/articles/default.shtml?a=cbd-02", "version_or_date": "Convention 1992; Article 2 web text consulted 2026-10-07", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-07T08:47:45Z", "relevance": "Functional ecosystem boundary; habitat and protected area are distinct concepts." }, { "id": "SRC-002", "title": "IUCN Global Ecosystem Typology: conservation tool", "organization": "International Union for Conservation of Nature", "url": "https://iucn.org/resources/conservation-tool/iucn-global-ecosystem-typology", "version_or_date": "Web resource referring to Global Ecosystem Typology 2.0 (2020); consulted 2026-10-07", "source_type": "classifier", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-07T08:47:45Z", "relevance": "Functional and compositional classification, hierarchy and transition contexts; exact codes require a pinned release." }, { "id": "SRC-003", "title": "SEEA Ecosystem Accounting: methodology overview", "organization": "United Nations Statistics Division", "url": "https://seea.un.org/en/methodology/ecosystem-accounting", "version_or_date": "SEEA EA adopted 2021; indexed official overview consulted 2026-10-07", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-07T08:47:45Z", "relevance": "Indexed official excerpts support extent by type and area, and condition at specified times. Full page and normative text retrieval incomplete." }, { "id": "SRC-004", "title": "Semantic Sensor Network Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-ssn/", "version_or_date": "W3C Recommendation 19 October 2017; selected sections consulted 2026-10-07", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-07T08:47:45Z", "relevance": "Observation feature, property, procedure, sample and distinct phenomenon/result time; alignment only." }, { "id": "SRC-005", "title": "Darwin Core Quick Reference Guide", "organization": "Biodiversity Information Standards", "url": "https://dwc.tdwg.org/terms/", "version_or_date": "Living quick reference consulted 2026-10-07; term release pin pending", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-07T08:47:45Z", "relevance": "Taxon, occurrence, event, sampling effort and location references; occurrence records do not constitute a complete ecosystem inventory." }, { "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": "W3C Recommendation 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-07T08:47:45Z", "relevance": "Derivation, revision, agent attribution and generated entities; provenance is not verification of ecological truth." }, { "id": "SRC-007", "title": "Current Best Practices for Generalizing Sensitive Species Occurrence Data", "organization": "Global Biodiversity Information Facility Secretariat", "url": "https://docs.gbif.org/sensitive-species-best-practices/master/en/", "version_or_date": "Chapman 2020; living master rendering consulted 2026-10-07", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-07T08:47:45Z", "relevance": "Sensitive locations, documented generalization, original versus released precision and provider-controlled authorization." }, { "id": "SRC-008", "title": "Red List of Ecosystems: Categories and Criteria", "organization": "International Union for Conservation of Nature", "url": "https://www.iucnrle.org/rle-categ-and-criteria", "version_or_date": "Undated official overview consulted 2026-10-07; detailed assessment guidelines not admitted", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-07T08:47:45Z", "relevance": "Distribution, environmental degradation, biotic disruption and quantitative collapse risk criteria; category refers to an assessed ecosystem type and scope." }, { "id": "SRC-009", "title": "SEEA Frequently Asked Questions", "organization": "United Nations Statistics Division", "url": "https://seea.un.org/en/about-seea/frequently-asked-questions", "version_or_date": "Undated official FAQ; indexed excerpt consulted 2026-10-07", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-07T08:47:45Z", "relevance": "Indexed excerpt supports selected characteristics and reference condition; detailed scaling and aggregation rules remain profile design." } ], "structure": { "bundles": [ { "id": "ecosystem-identity", "name": "Unit identity and continuity", "description": "Proposed ecosystem context for unit identity and continuity.", "rationale": "Keep this subject concern explicit while referencing independently mastered evidence and vocabularies.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "layers": [ { "id": "ecosystem-unit-layer", "name": "Ecological unit", "description": "Represent one delineated ecological system with a persistent steward-assigned identity. Record the operational boundary and map revision separately; the unit is neither a taxon nor a protected-area designation.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "ecosystem-unit-boundary", "name": "Identified ecosystem unit", "description": "Represent one delineated ecological system with a persistent steward-assigned identity. Record the operational boundary and map revision separately; the unit is neither a taxon nor a protected-area designation.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "ecosystem-unit-boundary-q1", "text": "Which authoritative identifier identifies this unit independently of its map epoch?", "kind": "identity", "answer_data": [ "unit_identifier", "master_reference" ] }, { "id": "ecosystem-unit-boundary-q2", "text": "Which interacting living and nonliving components justify treating the subject as a functional unit?", "kind": "definition", "answer_data": [ "boundary_rationale", "component_scope" ] }, { "id": "ecosystem-unit-boundary-q3", "text": "Who stewards the record, and which distinct tenure or customary-rights references govern the location?", "kind": "ownership", "answer_data": [ "record_steward", "rights_references" ] }, { "id": "ecosystem-unit-boundary-q4", "text": "How are split, merge, supersession and uncertain continuity recorded without reusing a retired identifier?", "kind": "lifecycle", "answer_data": [ "continuity_links", "continuity_decision" ] } ], "data_elements": [ { "id": "ecosystem-unit-boundary-unit-identifier", "name": "unit_identifier", "description": "Proposed unit identifier answer field for identified ecosystem unit. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "ecosystem-unit-boundary-master-reference", "name": "master_reference", "description": "Proposed master reference answer field for identified ecosystem unit. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "ecosystem-unit-boundary-boundary-rationale", "name": "boundary_rationale", "description": "Proposed boundary rationale answer field for identified ecosystem unit. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "ecosystem-unit-boundary-component-scope", "name": "component_scope", "description": "Proposed component scope answer field for identified ecosystem unit. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "ecosystem-unit-boundary-record-steward", "name": "record_steward", "description": "Proposed record steward answer field for identified ecosystem unit. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "ecosystem-unit-boundary-rights-references", "name": "rights_references", "description": "Proposed rights references answer field for identified ecosystem unit. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "ecosystem-unit-boundary-continuity-links", "name": "continuity_links", "description": "Proposed continuity links answer field for identified ecosystem unit. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "ecosystem-unit-boundary-continuity-decision", "name": "continuity_decision", "description": "Proposed continuity decision answer field for identified ecosystem unit. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "ecosystem-unit-boundary-record", "name": "Identified ecosystem unit evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "ecosystem-classification-layer", "name": "Classification assertions", "description": "Attach a qualified type assignment using a named classification release. Biome, realm and ecosystem type are classification concepts, not interchangeable root instances. Crosswalks may be partial, disputed or many-to-many.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "findings": [ { "id": "ecosystem-type-assignment", "name": "Versioned type and biome assignment", "description": "Attach a qualified type assignment using a named classification release. Biome, realm and ecosystem type are classification concepts, not interchangeable root instances. Crosswalks may be partial, disputed or many-to-many.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "questions": [ { "id": "ecosystem-type-assignment-q1", "text": "Which scheme, release, code and hierarchy level define the assigned class?", "kind": "classification", "answer_data": [ "classification_reference", "hierarchy_level" ] }, { "id": "ecosystem-type-assignment-q2", "text": "Which diagnostic observations support this assignment and what alternatives remain plausible?", "kind": "evidence", "answer_data": [ "diagnostic_evidence", "assignment_confidence", "alternative_classes" ] }, { "id": "ecosystem-type-assignment-q3", "text": "What mapping relation and loss of detail apply when translating to another scheme?", "kind": "interoperability", "answer_data": [ "crosswalk_reference", "mapping_relation", "mapping_limits" ] }, { "id": "ecosystem-type-assignment-q4", "text": "How are transitional, mixed, artificial or unclassified units represented without forcing an unsupported single class?", "kind": "exception", "answer_data": [ "assignment_status", "mixture_profile" ] } ], "data_elements": [ { "id": "ecosystem-type-assignment-classification-reference", "name": "classification_reference", "description": "Proposed classification reference answer field for versioned type and biome assignment. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "ecosystem-type-assignment-hierarchy-level", "name": "hierarchy_level", "description": "Proposed hierarchy level answer field for versioned type and biome assignment. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "ecosystem-type-assignment-diagnostic-evidence", "name": "diagnostic_evidence", "description": "Proposed diagnostic evidence answer field for versioned type and biome assignment. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "ecosystem-type-assignment-assignment-confidence", "name": "assignment_confidence", "description": "Proposed assignment confidence answer field for versioned type and biome assignment. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "ecosystem-type-assignment-alternative-classes", "name": "alternative_classes", "description": "Proposed alternative classes answer field for versioned type and biome assignment. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "ecosystem-type-assignment-crosswalk-reference", "name": "crosswalk_reference", "description": "Proposed crosswalk reference answer field for versioned type and biome assignment. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "ecosystem-type-assignment-mapping-relation", "name": "mapping_relation", "description": "Proposed mapping relation answer field for versioned type and biome assignment. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "ecosystem-type-assignment-mapping-limits", "name": "mapping_limits", "description": "Proposed mapping limits answer field for versioned type and biome assignment. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "ecosystem-type-assignment-assignment-status", "name": "assignment_status", "description": "Proposed assignment status answer field for versioned type and biome assignment. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "ecosystem-type-assignment-mixture-profile", "name": "mixture_profile", "description": "Proposed mixture profile answer field for versioned type and biome assignment. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "ecosystem-type-assignment-record", "name": "Versioned type and biome assignment evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "ecosystem-extent", "name": "Extent and spatial context", "description": "Proposed ecosystem context for extent and spatial context.", "rationale": "Keep this subject concern explicit while referencing independently mastered evidence and vocabularies.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ], "layers": [ { "id": "ecosystem-delineation-layer", "name": "Delineation and geometry", "description": "Bind the unit to a delineation product and valid period, preserving mapping grain and vertical or tidal context where relevant. An accounting partition is a selected projection, not a claim that ecological boundaries never overlap.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "findings": [ { "id": "ecosystem-mapped-extent", "name": "Qualified spatial extent", "description": "Bind the unit to a delineation product and valid period, preserving mapping grain and vertical or tidal context where relevant. An accounting partition is a selected projection, not a claim that ecological boundaries never overlap.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "ecosystem-mapped-extent-q1", "text": "What geometry, coordinate reference system and vertical or depth range describe the unit for the stated period?", "kind": "spatial", "answer_data": [ "geometry_reference", "crs_reference", "vertical_scope", "valid_period" ] }, { "id": "ecosystem-mapped-extent-q2", "text": "How was area or volume derived, in which units and with what uncertainty?", "kind": "measurement", "answer_data": [ "extent_quantity", "calculation_method", "extent_uncertainty" ] }, { "id": "ecosystem-mapped-extent-q3", "text": "Which spatial resolution, minimum mapping unit and boundary limitations constrain use?", "kind": "quality", "answer_data": [ "mapping_grain", "boundary_limitations" ] }, { "id": "ecosystem-mapped-extent-q4", "text": "What overlap, gap and coverage rules apply within the selected accounting area?", "kind": "constraint", "answer_data": [ "accounting_area_reference", "topology_policy" ] } ], "data_elements": [ { "id": "ecosystem-mapped-extent-geometry-reference", "name": "geometry_reference", "description": "Proposed geometry reference answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "ecosystem-mapped-extent-crs-reference", "name": "crs_reference", "description": "Proposed crs reference answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "ecosystem-mapped-extent-vertical-scope", "name": "vertical_scope", "description": "Proposed vertical scope answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "ecosystem-mapped-extent-valid-period", "name": "valid_period", "description": "Proposed valid period answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "ecosystem-mapped-extent-extent-quantity", "name": "extent_quantity", "description": "Proposed extent quantity answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "quantity", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "ecosystem-mapped-extent-calculation-method", "name": "calculation_method", "description": "Proposed calculation method answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "ecosystem-mapped-extent-extent-uncertainty", "name": "extent_uncertainty", "description": "Proposed extent uncertainty answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "ecosystem-mapped-extent-mapping-grain", "name": "mapping_grain", "description": "Proposed mapping grain answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "ecosystem-mapped-extent-boundary-limitations", "name": "boundary_limitations", "description": "Proposed boundary limitations answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "ecosystem-mapped-extent-accounting-area-reference", "name": "accounting_area_reference", "description": "Proposed accounting area reference answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "ecosystem-mapped-extent-topology-policy", "name": "topology_policy", "description": "Proposed topology policy answer field for qualified spatial extent. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "ecosystem-mapped-extent-record", "name": "Qualified spatial extent evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "ecosystem-connections-layer", "name": "Spatial and environmental relationships", "description": "Reference water, soil, terrain and climate masters and describe the unit-specific context. Connectivity assertions require a process, organism group, scale and method; adjacency alone is not functional connectivity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "ecosystem-connected-setting", "name": "Qualified setting and connectivity", "description": "Reference water, soil, terrain and climate masters and describe the unit-specific context. Connectivity assertions require a process, organism group, scale and method; adjacency alone is not functional connectivity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "ecosystem-connected-setting-q1", "text": "Which external water, soil, terrain and climate records describe the unit at compatible scales and times?", "kind": "relationship", "answer_data": [ "setting_references", "compatibility_notes" ] }, { "id": "ecosystem-connected-setting-q2", "text": "What connectivity or fragmentation metric is being claimed, for which process or organism group?", "kind": "measurement", "answer_data": [ "connectivity_metric", "focal_process", "analysis_scale" ] }, { "id": "ecosystem-connected-setting-q3", "text": "Which neighboring units, corridors or barriers are included in the analysis boundary?", "kind": "spatial", "answer_data": [ "neighbor_references", "analysis_boundary" ] }, { "id": "ecosystem-connected-setting-q4", "text": "How do missing neighbors, seasonal barriers or resolution changes limit the connection claim?", "kind": "quality", "answer_data": [ "connection_uncertainty", "seasonal_context" ] } ], "data_elements": [ { "id": "ecosystem-connected-setting-setting-references", "name": "setting_references", "description": "Proposed setting references answer field for qualified setting and connectivity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-connected-setting-compatibility-notes", "name": "compatibility_notes", "description": "Proposed compatibility notes answer field for qualified setting and connectivity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-connected-setting-connectivity-metric", "name": "connectivity_metric", "description": "Proposed connectivity metric answer field for qualified setting and connectivity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-connected-setting-focal-process", "name": "focal_process", "description": "Proposed focal process answer field for qualified setting and connectivity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-connected-setting-analysis-scale", "name": "analysis_scale", "description": "Proposed analysis scale answer field for qualified setting and connectivity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-connected-setting-neighbor-references", "name": "neighbor_references", "description": "Proposed neighbor references answer field for qualified setting and connectivity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-connected-setting-analysis-boundary", "name": "analysis_boundary", "description": "Proposed analysis boundary answer field for qualified setting and connectivity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "geometry", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-connected-setting-connection-uncertainty", "name": "connection_uncertainty", "description": "Proposed connection uncertainty answer field for qualified setting and connectivity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-connected-setting-seasonal-context", "name": "seasonal_context", "description": "Proposed seasonal context answer field for qualified setting and connectivity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "ecosystem-connected-setting-record", "name": "Qualified setting and connectivity evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "ecosystem-evidence", "name": "Composition and observations", "description": "Proposed ecosystem context for composition and observations.", "rationale": "Keep this subject concern explicit while referencing independently mastered evidence and vocabularies.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "ecosystem-community-layer", "name": "Biotic composition and structure", "description": "Link biotic observations to the ecosystem without copying species or specimen masters. Community summaries may include microbial groups, abundance, cover and vertical structure when evidenced; missing observations are not absence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "findings": [ { "id": "ecosystem-community-evidence", "name": "Community composition evidence", "description": "Link biotic observations to the ecosystem without copying species or specimen masters. Community summaries may include microbial groups, abundance, cover and vertical structure when evidenced; missing observations are not absence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "questions": [ { "id": "ecosystem-community-evidence-q1", "text": "Which taxa or functional groups and structural strata are evidenced in this unit?", "kind": "composition", "answer_data": [ "biotic_references", "strata_description" ] }, { "id": "ecosystem-community-evidence-q2", "text": "Which abundance, cover or diversity measure is reported with units and spatial support?", "kind": "measurement", "answer_data": [ "community_measurements", "spatial_support" ] }, { "id": "ecosystem-community-evidence-q3", "text": "Which survey events, sampling protocols and effort support the summary?", "kind": "evidence", "answer_data": [ "survey_references", "sampling_effort" ] }, { "id": "ecosystem-community-evidence-q4", "text": "How are nondetection, confirmed absence, taxonomic uncertainty and unsurveyed areas distinguished?", "kind": "exception", "answer_data": [ "observation_status", "taxonomic_uncertainty", "survey_gaps" ] } ], "data_elements": [ { "id": "ecosystem-community-evidence-biotic-references", "name": "biotic_references", "description": "Proposed biotic references answer field for community composition evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "ecosystem-community-evidence-strata-description", "name": "strata_description", "description": "Proposed strata description answer field for community composition evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "ecosystem-community-evidence-community-measurements", "name": "community_measurements", "description": "Proposed community measurements answer field for community composition evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "ecosystem-community-evidence-spatial-support", "name": "spatial_support", "description": "Proposed spatial support answer field for community composition evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "ecosystem-community-evidence-survey-references", "name": "survey_references", "description": "Proposed survey references answer field for community composition evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "ecosystem-community-evidence-sampling-effort", "name": "sampling_effort", "description": "Proposed sampling effort answer field for community composition evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "ecosystem-community-evidence-observation-status", "name": "observation_status", "description": "Proposed observation status answer field for community composition evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "ecosystem-community-evidence-taxonomic-uncertainty", "name": "taxonomic_uncertainty", "description": "Proposed taxonomic uncertainty answer field for community composition evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "ecosystem-community-evidence-survey-gaps", "name": "survey_gaps", "description": "Proposed survey gaps answer field for community composition evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "ecosystem-community-evidence-record", "name": "Community composition evidence evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "ecosystem-observation-layer", "name": "Observation attribution", "description": "Distinguish direct measurement, remote sensing, model output and expert interpretation. A sample has its own identity and spatial support; a derived unit estimate must disclose extrapolation and uncertainty.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "ecosystem-observation-basis", "name": "Qualified observation and estimate", "description": "Distinguish direct measurement, remote sensing, model output and expert interpretation. A sample has its own identity and spatial support; a derived unit estimate must disclose extrapolation and uncertainty.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "ecosystem-observation-basis-q1", "text": "Which feature, property, procedure and source dataset generated this result?", "kind": "provenance", "answer_data": [ "feature_reference", "property_reference", "procedure_reference", "dataset_reference" ] }, { "id": "ecosystem-observation-basis-q2", "text": "What phenomenon interval, result time and ingestion time apply, including seasonal coverage?", "kind": "temporal", "answer_data": [ "phenomenon_period", "result_time", "ingestion_time", "seasonal_coverage" ] }, { "id": "ecosystem-observation-basis-q3", "text": "What measurement or model uncertainty, quality flags and validation limits accompany the value?", "kind": "quality", "answer_data": [ "result_value", "uncertainty", "quality_flags" ] }, { "id": "ecosystem-observation-basis-q4", "text": "How is the sample-to-unit inference justified and which conditions invalidate its reuse?", "kind": "validation", "answer_data": [ "support_relationship", "inference_method", "reuse_limits" ] } ], "data_elements": [ { "id": "ecosystem-observation-basis-feature-reference", "name": "feature_reference", "description": "Proposed feature reference answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-property-reference", "name": "property_reference", "description": "Proposed property reference answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-procedure-reference", "name": "procedure_reference", "description": "Proposed procedure reference answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-dataset-reference", "name": "dataset_reference", "description": "Proposed dataset reference answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-phenomenon-period", "name": "phenomenon_period", "description": "Proposed phenomenon period answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-result-time", "name": "result_time", "description": "Proposed result time answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-ingestion-time", "name": "ingestion_time", "description": "Proposed ingestion time answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-seasonal-coverage", "name": "seasonal_coverage", "description": "Proposed seasonal coverage answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-result-value", "name": "result_value", "description": "Proposed result value answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-uncertainty", "name": "uncertainty", "description": "Proposed uncertainty answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-quality-flags", "name": "quality_flags", "description": "Proposed quality flags answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-support-relationship", "name": "support_relationship", "description": "Proposed support relationship answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-inference-method", "name": "inference_method", "description": "Proposed inference method answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-observation-basis-reuse-limits", "name": "reuse_limits", "description": "Proposed reuse limits answer field for qualified observation and estimate. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "ecosystem-observation-basis-record", "name": "Qualified observation and estimate evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "ecosystem-condition", "name": "Condition and ecological processes", "description": "Proposed ecosystem context for condition and ecological processes.", "rationale": "Keep this subject concern explicit while referencing independently mastered evidence and vocabularies.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-009" ], "layers": [ { "id": "ecosystem-assessment-layer", "name": "Condition assessment", "description": "Keep measured characteristics distinct from scored indicators and any aggregate. The proposed assessment contract requires an explicit reference basis, missingness policy and comparison limits; no universal good-condition threshold is supplied.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ], "findings": [ { "id": "ecosystem-condition-basis", "name": "Condition relative to an explicit reference", "description": "Keep measured characteristics distinct from scored indicators and any aggregate. The proposed assessment contract requires an explicit reference basis, missingness policy and comparison limits; no universal good-condition threshold is supplied.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ], "questions": [ { "id": "ecosystem-condition-basis-q1", "text": "Which characteristic, reference condition and eligible ecosystem types define this indicator?", "kind": "definition", "answer_data": [ "indicator_definition", "reference_basis", "applicable_types" ] }, { "id": "ecosystem-condition-basis-q2", "text": "Which raw values, units, normalization and direction of interpretation produced the score?", "kind": "measurement", "answer_data": [ "raw_values", "normalization_rule", "indicator_score" ] }, { "id": "ecosystem-condition-basis-q3", "text": "How are missing values, weights and aggregation limits reported for any composite assessment?", "kind": "validation", "answer_data": [ "missingness_policy", "aggregation_method", "assessment_limits" ] }, { "id": "ecosystem-condition-basis-q4", "text": "Are compared assessments compatible in reference basis, season, method and boundary revision?", "kind": "temporal", "answer_data": [ "comparison_periods", "comparability_decision" ] } ], "data_elements": [ { "id": "ecosystem-condition-basis-indicator-definition", "name": "indicator_definition", "description": "Proposed indicator definition answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-condition-basis-reference-basis", "name": "reference_basis", "description": "Proposed reference basis answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-condition-basis-applicable-types", "name": "applicable_types", "description": "Proposed applicable types answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-condition-basis-raw-values", "name": "raw_values", "description": "Proposed raw values answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-condition-basis-normalization-rule", "name": "normalization_rule", "description": "Proposed normalization rule answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-condition-basis-indicator-score", "name": "indicator_score", "description": "Proposed indicator score answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-condition-basis-missingness-policy", "name": "missingness_policy", "description": "Proposed missingness policy answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-condition-basis-aggregation-method", "name": "aggregation_method", "description": "Proposed aggregation method answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-condition-basis-assessment-limits", "name": "assessment_limits", "description": "Proposed assessment limits answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-condition-basis-comparison-periods", "name": "comparison_periods", "description": "Proposed comparison periods answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-condition-basis-comparability-decision", "name": "comparability_decision", "description": "Proposed comparability decision answer field for condition relative to an explicit reference. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] } ], "artifacts": [ { "id": "ecosystem-condition-basis-record", "name": "Condition relative to an explicit reference evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "ecosystem-process-layer", "name": "Processes and fluxes", "description": "Describe ecosystem processes through qualified observations or estimates. Quantities retain system boundary, stock/rate distinction and evidence basis; ecological behaviour is not a permission for an agent to alter the physical system.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "ecosystem-process-quantity", "name": "Biophysical process and flux assertion", "description": "Describe ecosystem processes through qualified observations or estimates. Quantities retain system boundary, stock/rate distinction and evidence basis; ecological behaviour is not a permission for an agent to alter the physical system.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "ecosystem-process-quantity-q1", "text": "Which ecological process and system boundary does the assertion describe?", "kind": "definition", "answer_data": [ "process_reference", "system_boundary" ] }, { "id": "ecosystem-process-quantity-q2", "text": "What quantity, unit, sign convention and integration interval distinguish the stock or flux?", "kind": "measurement", "answer_data": [ "process_quantity", "quantity_kind", "sign_convention", "integration_interval" ] }, { "id": "ecosystem-process-quantity-q3", "text": "Is the value measured, modelled or inferred, and which method and input revisions support it?", "kind": "provenance", "answer_data": [ "evidence_mode", "method_reference", "input_revisions" ] }, { "id": "ecosystem-process-quantity-q4", "text": "Which uncertainty, scale and boundary conditions limit aggregation or interpretation?", "kind": "constraint", "answer_data": [ "process_uncertainty", "aggregation_limits", "boundary_conditions" ] } ], "data_elements": [ { "id": "ecosystem-process-quantity-process-reference", "name": "process_reference", "description": "Proposed process reference answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-system-boundary", "name": "system_boundary", "description": "Proposed system boundary answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-process-quantity", "name": "process_quantity", "description": "Proposed process quantity answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "quantity", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-quantity-kind", "name": "quantity_kind", "description": "Proposed quantity kind answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-sign-convention", "name": "sign_convention", "description": "Proposed sign convention answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-integration-interval", "name": "integration_interval", "description": "Proposed integration interval answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-evidence-mode", "name": "evidence_mode", "description": "Proposed evidence mode answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-method-reference", "name": "method_reference", "description": "Proposed method reference answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-input-revisions", "name": "input_revisions", "description": "Proposed input revisions answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-process-uncertainty", "name": "process_uncertainty", "description": "Proposed process uncertainty answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-aggregation-limits", "name": "aggregation_limits", "description": "Proposed aggregation limits answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "ecosystem-process-quantity-boundary-conditions", "name": "boundary_conditions", "description": "Proposed boundary conditions answer field for biophysical process and flux assertion. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "ecosystem-process-quantity-record", "name": "Biophysical process and flux assertion evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "ecosystem-change", "name": "Change and disturbance", "description": "Proposed ecosystem context for change and disturbance.", "rationale": "Keep this subject concern explicit while referencing independently mastered evidence and vocabularies.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-008" ], "layers": [ { "id": "ecosystem-transition-layer", "name": "Extent and classification changes", "description": "A new map can reflect physical conversion, better delineation or a classification revision. Preserve before/after support and a reasoned change category. The local record does not infer a physical loss merely from a changed code or polygon.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "ecosystem-change-attribution", "name": "Comparable change with continuity", "description": "A new map can reflect physical conversion, better delineation or a classification revision. Preserve before/after support and a reasoned change category. The local record does not infer a physical loss merely from a changed code or polygon.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "ecosystem-change-attribution-q1", "text": "Which before and after epochs, unit revisions and common comparison area are used?", "kind": "temporal", "answer_data": [ "before_revision", "after_revision", "comparison_area", "change_period" ] }, { "id": "ecosystem-change-attribution-q2", "text": "What evidence distinguishes ecological conversion from map correction or typology revision?", "kind": "event", "answer_data": [ "change_category", "change_evidence" ] }, { "id": "ecosystem-change-attribution-q3", "text": "What gross gains, losses and net change can be reported without counting overlapping units twice?", "kind": "measurement", "answer_data": [ "change_quantities", "overlap_treatment" ] }, { "id": "ecosystem-change-attribution-q4", "text": "How are split and merge lineage, reclassification and unresolved transitions preserved?", "kind": "lifecycle", "answer_data": [ "transition_links", "unresolved_changes" ] } ], "data_elements": [ { "id": "ecosystem-change-attribution-before-revision", "name": "before_revision", "description": "Proposed before revision answer field for comparable change with continuity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "ecosystem-change-attribution-after-revision", "name": "after_revision", "description": "Proposed after revision answer field for comparable change with continuity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "ecosystem-change-attribution-comparison-area", "name": "comparison_area", "description": "Proposed comparison area answer field for comparable change with continuity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "geometry", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "ecosystem-change-attribution-change-period", "name": "change_period", "description": "Proposed change period answer field for comparable change with continuity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "ecosystem-change-attribution-change-category", "name": "change_category", "description": "Proposed change category answer field for comparable change with continuity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "ecosystem-change-attribution-change-evidence", "name": "change_evidence", "description": "Proposed change evidence answer field for comparable change with continuity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "ecosystem-change-attribution-change-quantities", "name": "change_quantities", "description": "Proposed change quantities answer field for comparable change with continuity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "ecosystem-change-attribution-overlap-treatment", "name": "overlap_treatment", "description": "Proposed overlap treatment answer field for comparable change with continuity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "ecosystem-change-attribution-transition-links", "name": "transition_links", "description": "Proposed transition links answer field for comparable change with continuity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "ecosystem-change-attribution-unresolved-changes", "name": "unresolved_changes", "description": "Proposed unresolved changes answer field for comparable change with continuity. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "ecosystem-change-attribution-record", "name": "Comparable change with continuity evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "ecosystem-pressure-layer", "name": "Pressures and assessed outcomes", "description": "Link pressures or disturbance events to observed responses with qualified attribution. Local condition, restoration progress and an external type-level collapse-risk assessment remain separate assertions. No official category is calculated by this draft.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ], "findings": [ { "id": "ecosystem-disturbance-response", "name": "Disturbance, recovery and risk context", "description": "Link pressures or disturbance events to observed responses with qualified attribution. Local condition, restoration progress and an external type-level collapse-risk assessment remain separate assertions. No official category is calculated by this draft.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ], "questions": [ { "id": "ecosystem-disturbance-response-q1", "text": "Which event or continuing pressure affected what portion of the unit and when?", "kind": "event", "answer_data": [ "pressure_reference", "affected_extent", "pressure_period" ] }, { "id": "ecosystem-disturbance-response-q2", "text": "What observations support the response and what alternative causes or uncertainty remain?", "kind": "evidence", "answer_data": [ "response_evidence", "attribution_basis", "alternative_causes" ] }, { "id": "ecosystem-disturbance-response-q3", "text": "Which recovery or restoration target and follow-up observations support a reported milestone?", "kind": "state", "answer_data": [ "target_reference", "followup_evidence", "milestone_status" ] }, { "id": "ecosystem-disturbance-response-q4", "text": "What ecosystem type, assessment region, date and authority bound any linked collapse-risk category?", "kind": "constraint", "answer_data": [ "risk_assessment_reference", "risk_scope", "risk_category" ] } ], "data_elements": [ { "id": "ecosystem-disturbance-response-pressure-reference", "name": "pressure_reference", "description": "Proposed pressure reference answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-affected-extent", "name": "affected_extent", "description": "Proposed affected extent answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-pressure-period", "name": "pressure_period", "description": "Proposed pressure period answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-response-evidence", "name": "response_evidence", "description": "Proposed response evidence answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-attribution-basis", "name": "attribution_basis", "description": "Proposed attribution basis answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-alternative-causes", "name": "alternative_causes", "description": "Proposed alternative causes answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-target-reference", "name": "target_reference", "description": "Proposed target reference answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-followup-evidence", "name": "followup_evidence", "description": "Proposed followup evidence answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-milestone-status", "name": "milestone_status", "description": "Proposed milestone status answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-risk-assessment-reference", "name": "risk_assessment_reference", "description": "Proposed risk assessment reference answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-risk-scope", "name": "risk_scope", "description": "Proposed risk scope answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "ecosystem-disturbance-response-risk-category", "name": "risk_category", "description": "Proposed risk category answer field for disturbance, recovery and risk context. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "ecosystem-disturbance-response-record", "name": "Disturbance, recovery and risk context evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "ecosystem-use", "name": "Biophysical use and accountable exchange", "description": "Proposed ecosystem context for biophysical use and accountable exchange.", "rationale": "Keep this subject concern explicit while referencing independently mastered evidence and vocabularies.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009" ], "layers": [ { "id": "ecosystem-capacity-layer", "name": "Physical service context", "description": "Record proposed physical capacity estimates separately from observed service flows, use and monetary appraisal. Capacity claims require a scenario, conditions and method; positive capacity does not establish sustainable extraction or restoration success.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ], "findings": [ { "id": "ecosystem-capacity-estimate", "name": "Qualified capacity and realized flow", "description": "Record proposed physical capacity estimates separately from observed service flows, use and monetary appraisal. Capacity claims require a scenario, conditions and method; positive capacity does not establish sustainable extraction or restoration success.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ], "questions": [ { "id": "ecosystem-capacity-estimate-q1", "text": "Which physical output and recipient context does the capacity or flow claim concern?", "kind": "definition", "answer_data": [ "output_reference", "recipient_context", "claim_kind" ] }, { "id": "ecosystem-capacity-estimate-q2", "text": "What physical quantity, units, period and spatial support are reported?", "kind": "measurement", "answer_data": [ "service_quantity", "service_period", "service_support" ] }, { "id": "ecosystem-capacity-estimate-q3", "text": "Which ecological conditions, scenario assumptions and sustainability limits qualify the estimate?", "kind": "constraint", "answer_data": [ "scenario_reference", "capacity_conditions", "sustainability_limits" ] }, { "id": "ecosystem-capacity-estimate-q4", "text": "How are capacity, realized flow and downstream valuation separated to avoid duplicate claims?", "kind": "interoperability", "answer_data": [ "flow_reference", "valuation_reference", "double_counting_rule" ] } ], "data_elements": [ { "id": "ecosystem-capacity-estimate-output-reference", "name": "output_reference", "description": "Proposed output reference answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-recipient-context", "name": "recipient_context", "description": "Proposed recipient context answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-claim-kind", "name": "claim_kind", "description": "Proposed claim kind answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-service-quantity", "name": "service_quantity", "description": "Proposed service quantity answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "quantity", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-service-period", "name": "service_period", "description": "Proposed service period answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-service-support", "name": "service_support", "description": "Proposed service support answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-scenario-reference", "name": "scenario_reference", "description": "Proposed scenario reference answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-capacity-conditions", "name": "capacity_conditions", "description": "Proposed capacity conditions answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-sustainability-limits", "name": "sustainability_limits", "description": "Proposed sustainability limits answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-flow-reference", "name": "flow_reference", "description": "Proposed flow reference answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-valuation-reference", "name": "valuation_reference", "description": "Proposed valuation reference answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-capacity-estimate-double-counting-rule", "name": "double_counting_rule", "description": "Proposed double counting rule answer field for qualified capacity and realized flow. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] } ], "artifacts": [ { "id": "ecosystem-capacity-estimate-record", "name": "Qualified capacity and realized flow evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "ecosystem-release-layer", "name": "Governed evidence exchange", "description": "A released map or assessment has its own revision and derivation trail. Access to precise evidence is governed separately from record stewardship. Preserve a documented generalized view without implying that its coordinates are the original precision.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "ecosystem-release-provenance", "name": "Reviewable release and sensitive evidence", "description": "A released map or assessment has its own revision and derivation trail. Access to precise evidence is governed separately from record stewardship. Preserve a documented generalized view without implying that its coordinates are the original precision.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "ecosystem-release-provenance-q1", "text": "Which steward authorization, evidence-use rights and review decision support this release?", "kind": "authority", "answer_data": [ "release_authority", "use_rights", "review_decision" ] }, { "id": "ecosystem-release-provenance-q2", "text": "Which sensitive fields, locations or linked records require restricted or generalized views?", "kind": "access", "answer_data": [ "sensitivity_assessment", "release_view", "generalization_record" ] }, { "id": "ecosystem-release-provenance-q3", "text": "Which source revisions, derivation steps and integrity checks identify the released artifact?", "kind": "provenance", "answer_data": [ "source_revisions", "derivation_record", "integrity_digest" ] }, { "id": "ecosystem-release-provenance-q4", "text": "What retention, withdrawal and permitted deletion rules govern originals, public views and minimal tombstones?", "kind": "retention", "answer_data": [ "retention_policy", "withdrawal_links", "deletion_authority" ] } ], "data_elements": [ { "id": "ecosystem-release-provenance-release-authority", "name": "release_authority", "description": "Proposed release authority answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-use-rights", "name": "use_rights", "description": "Proposed use rights answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-review-decision", "name": "review_decision", "description": "Proposed review decision answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-sensitivity-assessment", "name": "sensitivity_assessment", "description": "Proposed sensitivity assessment answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-release-view", "name": "release_view", "description": "Proposed release view answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-generalization-record", "name": "generalization_record", "description": "Proposed generalization record answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-source-revisions", "name": "source_revisions", "description": "Proposed source revisions answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-derivation-record", "name": "derivation_record", "description": "Proposed derivation record answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-integrity-digest", "name": "integrity_digest", "description": "Proposed integrity digest answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-retention-policy", "name": "retention_policy", "description": "Proposed retention policy answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-withdrawal-links", "name": "withdrawal_links", "description": "Proposed withdrawal links answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "ecosystem-release-provenance-deletion-authority", "name": "deletion_authority", "description": "Proposed deletion authority answer field for reviewable release and sensitive evidence. Nested validation and vocabulary bindings require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "ecosystem-release-provenance-record", "name": "Reviewable release and sensitive evidence evidence record", "description": "Versioned evidence-bearing record for this finding; references may point to controlled external payloads.", "media_or_form": [ "Structured record", "Human-readable evidence summary" ], "serial": true, "identity_strategy": "Authoritative master-system record ID first; governed persistent IRI second; Dimension UUID or ULID otherwise. Revision and sequence are separate fields, never a date-only identifier.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "ecosystem-register-unit", "name": "Register a local unit proposal", "description": "Proposed, unimplemented local record operation. Create a proposed local record; do not establish tenure or designate protected land.", "inputs": [ "unit identity", "boundary rationale", "steward and map reference" ], "outputs": [ "Draft unit revision or identity-conflict report" ], "preconditions": [ "An authorized steward has resolved the authoritative master and continuity rules.", "Require an authorized role, current expected revision and recorded purpose; refuse stale concurrent writes." ], "effects": [ "Create a proposed local record; do not establish tenure or designate protected land.", "Record actor, input and output revisions, evidence links and explicit refusal reason on failure." ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "ecosystem-attach-classification", "name": "Attach a qualified classification assertion", "description": "Proposed, unimplemented local record operation. Link the assignment without altering the external classifier or converting the ecosystem physically.", "inputs": [ "unit revision", "scheme release", "code", "diagnostic evidence and assignment confidence" ], "outputs": [ "Versioned assignment or unresolved-code report" ], "preconditions": [ "The class exists in a pinned scheme or is explicitly recorded as unresolved; mixed units follow a declared profile.", "Require an authorized role, current expected revision and recorded purpose; refuse stale concurrent writes." ], "effects": [ "Link the assignment without altering the external classifier or converting the ecosystem physically.", "Record actor, input and output revisions, evidence links and explicit refusal reason on failure." ], "source_refs": [ "SRC-002", "SRC-006" ] }, { "id": "ecosystem-link-observation", "name": "Link evidence to a unit revision", "description": "Proposed, unimplemented local record operation. Append provenance and uncertainty; do not infer absence from missing survey data.", "inputs": [ "observation reference", "property", "procedure", "support", "time and rights" ], "outputs": [ "Qualified evidence link or incompatibility report" ], "preconditions": [ "The caller may use the source; feature identity and spatial/temporal support are known.", "Require an authorized role, current expected revision and recorded purpose; refuse stale concurrent writes." ], "effects": [ "Append provenance and uncertainty; do not infer absence from missing survey data.", "Record actor, input and output revisions, evidence links and explicit refusal reason on failure." ], "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "ecosystem-record-assessment", "name": "Record a reviewed condition assessment", "description": "Proposed, unimplemented local record operation. Record supplied results and review status; do not execute a universal condition or collapse classifier.", "inputs": [ "raw observations", "indicator definition", "reference basis", "scoring method and reviewer" ], "outputs": [ "Versioned assessment or missing-basis report" ], "preconditions": [ "The reviewer confirms type applicability, uncertainty and missingness policy; incomparable inputs are rejected.", "Require an authorized role, current expected revision and recorded purpose; refuse stale concurrent writes." ], "effects": [ "Record supplied results and review status; do not execute a universal condition or collapse classifier.", "Record actor, input and output revisions, evidence links and explicit refusal reason on failure." ], "source_refs": [ "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "ecosystem-record-transition", "name": "Record an evidenced unit transition", "description": "Proposed, unimplemented local record operation. Add lineage and qualified quantities; preserve superseded records according to retention policy.", "inputs": [ "before/after revisions", "comparison support", "reason category and evidence" ], "outputs": [ "Transition record or unresolved-attribution report" ], "preconditions": [ "Continuity and overlap treatment are reviewed; the reason distinguishes correction, reclassification and ecological change.", "Require an authorized role, current expected revision and recorded purpose; refuse stale concurrent writes." ], "effects": [ "Add lineage and qualified quantities; preserve superseded records according to retention policy.", "Record actor, input and output revisions, evidence links and explicit refusal reason on failure." ], "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "ecosystem-prepare-release", "name": "Prepare an authorized evidence projection", "description": "Proposed, unimplemented local record operation. Generate a local candidate only; do not publish externally or grant new access.", "inputs": [ "accepted revisions", "audience", "policy", "sensitivity review and source-use rights" ], "outputs": [ "Local release candidate with lineage or refusal report" ], "preconditions": [ "An authorized data custodian has specified permissible fields and generalization; restrictions on linked evidence are inherited.", "Require an authorized role, current expected revision and recorded purpose; refuse stale concurrent writes." ], "effects": [ "Generate a local candidate only; do not publish externally or grant new access.", "Record actor, input and output revisions, evidence links and explicit refusal reason on failure." ], "source_refs": [ "SRC-006", "SRC-007" ] } ], "composition": [ { "target": "WM-LIV-004", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Vegetation evidence and structure references; preserve vegetation record masters.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "WM-LIV-005", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Wildlife observation references; no population lifecycle duplication.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "WM-PLC-003", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Water-body and hydrological setting references, with explicit temporal support.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-EAR-003", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Soil setting and property evidence remain separately mastered.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-PLC-001", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Terrain and landform context remains external.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-EAR-001", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Observed weather context is separate from long-term climatic class.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "WM-EAR-002", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Climate regime references and applicable periods are not copied as climate masters.", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] }, { "target": "WM-EAR-005", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Hazard occurrence references support disturbance attribution only.", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] }, { "target": "WM-FLW-006", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Emission flow references retain their own accounting boundary; legacy F6 is ambiguous and does not justify sustainability-claim inheritance.", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "target": "WM-ACT-011", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Agricultural activity references may evidence pressures; no operational controls are imported.", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "target": "WM-ACT-012", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. Extraction activity references may evidence pressures; no resource-use permission follows.", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "target": "WM-DAT-002", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. External statistical releases may consume extent and condition projections; official production remains external.", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "target": "WM-ECO-002", "relation": "REFERENCE", "purpose": "Candidate binding requiring a version pin. External valuation receives physical references; monetary appraisal remains out of scope.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "IUCN Global Ecosystem Typology", "relation": "ALIGN", "purpose": "Candidate binding requiring a version pin. Versioned class references only; no classifier conformance claim.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "SEEA Ecosystem Accounting", "relation": "ALIGN", "purpose": "Candidate binding requiring a version pin. Conceptual extent/condition projection only, replacing unsupported legacy COMPOSE semantics.", "required": false, "source_refs": [ "SRC-003", "SRC-009" ] }, { "target": "SOSA/SSN", "relation": "ALIGN", "purpose": "Candidate binding requiring a version pin. Observation-feature and time mapping proposal; serialization is unimplemented.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "Darwin Core", "relation": "ALIGN", "purpose": "Candidate binding requiring a version pin. Biotic event, occurrence and location reference mapping proposal.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "PROV-O", "relation": "ALIGN", "purpose": "Candidate binding requiring a version pin. Provenance and revision mapping proposal; does not certify truth.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "IUCN Red List of Ecosystems", "relation": "ALIGN", "purpose": "Candidate binding requiring a version pin. Referenced assessment categories and scope only; no automatic category assignment.", "required": false, "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Identify the adopting ecology data steward by role and governing authority; stewardship is not land ownership.", "Declare namespace, master identifiers, profile version, spatial grain and applicable ecosystem realms.", "Record licenses, evidence-use rights, affected rights-holder agreements, sensitivity and retention policies.", "Select explicit classifier and neighbor versions before operational exchange." ], "namespace_guidance": "Use a steward-governed ecosystem namespace; keep unit, map revision, class concept, observation and assessment identifiers distinct.", "registry_links": [ "vr.wm-liv-006", "WM-LIV-006; legacy P8 is a migration alias only" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve qualified assertions and unknown values; labels and dates do not establish identity.", "Accept a reviewed unit revision only with evidence, author and scope; this research remains noncanonical reviewable-draft." ], "patch_rules": [ "Require expected revision and authorized role; record changed fields, rationale and derivation.", "Separate mapping corrections from ecological transitions; no silent overwrite of prior assessments." ], "compatibility_rules": [ "A changed classifier release, CRS, grain, indicator reference or method can invalidate comparisons; require a recorded migration mapping.", "Historical payload retention remains subject to rights, withdrawal and deletion policy; retain minimal non-sensitive continuity metadata where allowed." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system artifact identifier", "Governed persistent global identifier or IRI", "Dimension-assigned UUID or ULID" ], "timestamp_rule": "Use RFC 3339 with seconds and an explicit offset or Z for known instants. Preserve source date precision or intervals separately; never invent seconds for uncertain historical observations. Separate phenomenon, result and ingestion time.", "serial_naming_rule": "Use stable artifact ID with a separate revision and sequence. A timestamp is metadata and cannot be the sole artifact identity.", "integrity_rule": "Record content digest, media type, source revision, derivation, license and access class. Hashes establish byte integrity, not ecological correctness; do not expose restricted originals through derivatives." }, "policies": [ "All service rules are proposed local governance requirements, not obligations asserted by ecological standards.", "No map, record or model link establishes tenure, consent, protection designation or resource-use authority.", "No modelled quantity is presented as a field measurement; no missing evidence is converted to zero or confirmed absence.", "Sensitive species and community-provided knowledge require an evidence-use policy and qualified custodian review; do not infer access from a public summary.", "Independent external review, source/version verification, ecological profile review and executable conformance remain publication holds." ], "crud": { "read": [ "Resolve revision, rights and audience scope before returning precise evidence or generalized views." ], "create": [ "Create a proposed record only with stable identity, spatial/temporal support, steward and source evidence." ], "update": [ "Append a revision with concurrency check and reviewer; preserve dissenting and superseded assertions subject to policy." ], "delete": [ "Retire mistaken or superseded records with authorized continuity links; physical disappearance does not delete evidence.", "Honor lawful payload erasure or withdrawal with authorized retention/hold review and minimal permitted tombstones. Do not promise indefinite storage of sensitive originals." ] }, "roles": [ { "name": "Ecology data steward", "responsibilities": [ "Own the local namespace and profile decisions; resolve continuity and references." ] }, { "name": "Observation contributor", "responsibilities": [ "Submit attributable evidence, uncertainty and use-rights metadata." ] }, { "name": "Ecological reviewer", "responsibilities": [ "Evaluate classification, comparison basis and assessment claims within documented expertise." ] }, { "name": "Data custodian", "responsibilities": [ "Apply audience restrictions, retention and controlled release rules." ] }, { "name": "Consumer or auditor", "responsibilities": [ "Inspect applicable limitations and report errors without modifying source masters." ] } ], "access": { "default_rule": "Restrict unpublished precise evidence by default; release only a policy-authorized view with its uncertainty and generalization metadata.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Custodian-approved access may permit finer resolution for a documented purpose; expiry and downstream restrictions remain explicit.", "Public aggregate access never permits reconstructing withheld sites through linked artifacts or metadata." ], "audit_requirements": [ "Log actor, purpose, policy version, requested scope, decision and released view without copying secret coordinates into public logs.", "Record release lineage and withdrawal propagation; audit metadata has its own retention policy." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read AGENTS.md and the current research holds.", "Read spec.yaml, the adopting Dimension policies and pinned neighbor bindings.", "Resolve source rights and current unit revision before proposing local operations." ] } }, "coverage": { "claim": "Source-grounded proposed structure for a steward-identified ecosystem unit with referenced biome and ecosystem-type concepts. The separate frozen local no-tools self-audit found no critical contradiction. This is a noncanonical reviewable draft; independent review, source/version verification, ecological profile review and executable conformance remain open.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Unit identity is stable; class, map and observation identities are separate." }, { "dimension": "lifecycle", "status": "covered", "notes": "Split, merge, retirement, uncertain continuity and ecological transition differ from record revision." }, { "dimension": "relationships", "status": "covered", "notes": "Candidate neighbor references preserve external master boundaries; runtime pins remain pending." }, { "dimension": "temporal", "status": "covered", "notes": "Phenomenon, result, ingestion and map validity are explicit, with seasonal comparability." }, { "dimension": "provenance", "status": "covered", "notes": "Evidence mode, derivation, revision, source rights and uncertainty are carried." }, { "dimension": "ownership", "status": "covered", "notes": "Record stewardship is separate from tenure, customary rights and operational authority." }, { "dimension": "validation", "status": "gap", "notes": "Research schema validation is possible; nested instance schemas, controlled vocabularies and profile fixtures are unimplemented." }, { "dimension": "access", "status": "covered", "notes": "Audience-specific evidence views preserve sensitivity and generalization metadata." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Authorized withdrawal and payload erasure coexist with minimal permitted continuity metadata." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual alignments only; exact classifier releases and neighboring schemas require pinning." }, { "dimension": "direct properties", "status": "covered", "notes": "Extent, biotic structure, condition and processes retain method, units and support." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Survey and diagnostic evidence distinguish uncertainty, modelled estimates and nondetection." }, { "dimension": "capabilities and behaviour", "status": "covered", "notes": "Ecological processes and physical capacity are separate from proposed record operations and physical intervention." }, { "dimension": "source verification", "status": "gap", "notes": "Seven documents were readable in the web tool; two official SEEA pages had indexed support only. Direct HTTP checks were not attempted." }, { "dimension": "independent review", "status": "gap", "notes": "Claude and Grok skipped under waiver; a separate local no-tools self-audit does not provide external independence." } ], "known_omissions": [ "Full normative SEEA text and exact typology/term releases were not retrieved and verified.", "Nested instance schemas, uncertainty propagation, geometry engines and conformance fixtures remain unimplemented.", "Marine depth, subterranean, microbial, seasonal, managed and transitional ecosystem profiles need qualified examples.", "Community knowledge governance, jurisdiction-specific tenure, licensing and retention require local review.", "ENVO and SWEET imports from the legacy card were not admitted without separate source verification." ], "conflicts": [], "regional_assumptions": [ "No jurisdiction, universal mapping grain, ecological reference state, risk threshold or land-rights regime is assumed.", "Classifier terminology differs across schemes; the draft selects no exclusive global classification." ], "adversarial_checks": [ "A changed map code alone cannot prove physical conversion.", "A type-level threat category cannot be copied onto every mapped unit as a local condition score.", "A generalized site and a missing occurrence are not exact coordinates and confirmed absence.", "Capacity is not realized use, money, sustainable extraction permission or restoration certification.", "A steward namespace and source provenance do not establish land ownership or truth." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The root retains unit identity across map revisions, observations and assessed changes. Biome and ecosystem-type concepts are externally governed references, not a competing classifier root. The registry standalone-mm value classifies the record plane and does not determine the subject-kind enum. Operational delineation and record stewardship confer no tenure or physical authority." }, "decisions": [ { "concept": "Unit versus type root", "disposition": "accepted", "rationale": "Identity, classification and scope consistently distinguish one ecological unit from externally mastered biome/type concepts. The combined title does not require classifier authoring within this root." }, { "concept": "Epoch as identity", "disposition": "rejected", "rationale": "The legacy and supplement epoch-based suggestion cannot supply persistent identity alone. Unit IDs, revision IDs and explicit split/merge continuity decisions remain separate." }, { "concept": "Realm and biome equivalence", "disposition": "rejected", "rationale": "The proposal asks for classification scheme, release and hierarchy level. It avoids treating realm and biome as synonyms or asserting unverified current class counts." }, { "concept": "One exclusive classification and geometry", "disposition": "qualified", "rationale": "Mixed, transitional and unresolved assignments remain possible. Accounting projections require declared topology and comparison support instead of assuming every ecological unit partitions space without overlap." }, { "concept": "Physical properties and connectivity", "disposition": "accepted as proposed contracts", "rationale": "Extent and connection questions require units, method, scale, support and limits. They do not prescribe a universal metric or infer functional connectivity from adjacency." }, { "concept": "Composition and observation uncertainty", "disposition": "accepted", "rationale": "Biotic summaries reference separately mastered evidence, and the questions preserve effort, survey gaps and sample-to-unit inference. Missing data cannot silently become absence or zero." }, { "concept": "Condition and reference basis", "disposition": "qualified", "rationale": "Raw values, reference basis, scoring and composite assessments are distinct. Indexed SEEA evidence supports the broad concepts only; normalization, weights and missingness rules remain explicit profile choices." }, { "concept": "Map change versus ecological transition", "disposition": "accepted", "rationale": "Before/after revisions and change evidence distinguish physical conversion, correction and typology revision. Overlap treatment and lineage prevent silent double counting or identity reuse." }, { "concept": "Collapse risk and restoration status", "disposition": "separated", "rationale": "Local condition and restoration milestones do not establish a type-level risk class. A linked risk assessment retains ecosystem type, region, date and authority, and no category algorithm is implemented." }, { "concept": "Capacity, use and valuation", "disposition": "separated", "rationale": "Physical capacity claims require contextual conditions and limits. Realized flows and external valuation references do not turn estimates into money, sustainable extraction permission or restoration certification." }, { "concept": "Neighbor ownership and legacy imports", "disposition": "qualified", "rationale": "The relation ledger is empty and all bindings are candidates. Legacy F6 is ambiguous, SEEA is alignment only, and unverified ENVO/SWEET imports remain deferred instead of importing unsupported ownership." }, { "concept": "Local operation effects", "disposition": "accepted as unimplemented proposals", "rationale": "All six operations record or prepare local evidence with role and revision checks and refusal results. They do not intervene physically, grant rights, publish remotely or claim operational conformance." }, { "concept": "Sensitive evidence and retention", "disposition": "accepted with local policy dependency", "rationale": "Custody and release authority remain distinct from tenure. Generalized views preserve their limitations, while controlled withdrawal and payload erasure coexist with minimal permitted continuity records." }, { "concept": "Source assurance and external review", "disposition": "held", "rationale": "Seven documents were readable and two official pages had indexed support only. Direct HTTP was not attempted. The Codex self-audit cannot replace the absent independent provider or verify current normative releases." }, { "concept": "Executable schemas and domain completeness", "disposition": "deferred", "rationale": "Candidate fields and conceptual mappings do not provide nested validation, geometry calculations, uncertainty propagation or complete realm-specific fixtures. These gaps are visible holds rather than contradictions in a reviewable research proposal." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not independent second-provider review.", "Live source and version verification remains incomplete. Seven admitted documents exposed readable web-tool text and two official SEEA pages exposed indexed excerpts only. Full normative SEEA retrieval and exact classifier/term release pins remain unverified. Direct HTTP checks were not attempted under the owner-reported sandbox restriction; zero response statuses were measured. Coordinator check_sources.py is supplied, and HTTP success alone cannot close substantive verification.", "Ecological realm, mapping grain, temporal support, reference condition, mixed-type treatment, capacity method, community knowledge use, tenure, licensing, sensitivity and retention require qualified adopting-profile review. No universal assessment threshold, land-rights determination or restoration certification is claimed.", "Nested instance schemas, pinned neighbor bindings, classifier crosswalks, geometry and uncertainty calculations, create/update concurrency semantics and executable conformance fixtures remain incomplete. All functions and alignments are proposed and unimplemented.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Retrieve and verify full SEEA documentation and pinned typology, term and risk-assessment releases; complete claim-level, license and direct HTTP review.", "Develop profiles and adversarial fixtures for marine/depth, subterranean, microbial, seasonal, transitional and managed ecosystems, including incompatible comparisons and map-only changes.", "Implement nested schemas, mapping and uncertainty contracts, local operation validation and privacy-preserving release tests without importing external master lifecycles.", "Restore independent external review before canonical or publishable-draft promotion." ] }, "statistics": { "sources": 9, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }