# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T20:29:39Z", "synthesisSha256": "329d8ad17cc06bc7c7027015bbcc3e5851c1b41a8d63a6d45c835b128bd292cd", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-EAR-012", "registryId": "vr.wm-ear-012", "name": "Environmental Monitoring Station", "version": "0.1.0-reviewable", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.EAR.MON" ], "tags": [ "environmental", "monitoring", "station", "phy.ear.mon" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-ear-012-environmental-monitoring-station/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-ear-012", "model": { "registry_id": "vr.wm-ear-012", "model_id": "WM-EAR-012", "name": "Environmental Monitoring Station", "entry_kind": "entity", "purpose": "Describe one persistent environmental observing facility, its effective configuration and accountable links to programmes and observations.", "scope_statement": "One steward-recognized station or observing facility with continuing identity across documented operational periods. Fixed sites are the default adoption profile; a mobile or repositionable facility is admitted only with explicit profile, platform and trajectory bindings. Stable means identity continuity, not immutable coordinates. All proposed structures and local functions are research design, not normative requirements of the cited sources.", "in_scope": [ "Station identifiers and aliases, responsible roles, network and programme participation", "Effective locations, exposure evidence, instrument deployment references and capability assertions", "Station-specific acquisition bindings, maintenance and quality evidence references, operational periods and controlled metadata revisions" ], "out_of_scope": [ "Instrument asset and calibration execution, physical platform lifecycle and land ownership master records", "Individual observations, samples, laboratory analyses and dataset processing lifecycles; only bindings and evidence references are local", "Network and programme master definitions, regulatory compliance decisions, environmental warning issuance and remote equipment control", "A single measurement event, an entire observing network or an unregistered campaign activity without persistent facility identity" ], "boundary_notes": [ { "neighbor": "WM-OBJ-023 Meter / Measuring Instrument", "distinction": "Registry parent is an unratified alignment candidate. A facility hosting instruments is not automatically a subtype of each instrument. Record deployment references; instrument identity, calibration execution and device lifecycle stay external.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "Observation, sample and dataset masters", "distinction": "A station is neither the observed environmental feature nor its results. Link immutable observation or dataset revisions and sampled features without taking ownership of their processing or quality engines.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "neighbor": "Monitoring programme, network and campaign", "distinction": "Membership and contribution intervals are station-local assertions. Definitions, coordination and network-level coverage remain external. A temporary facility may qualify if it retains identity; a campaign alone does not.", "source_refs": [ "SRC-001" ] }, { "neighbor": "Site, platform and responsible organization", "distinction": "Coordinates and host references locate the station; a mast silhouette or co-location does not establish identity. Platform, site and organization master lifecycles are separately governed.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ] }, "sources": [ { "id": "SRC-001", "title": "INSPIRE Data Specification on Environmental Monitoring Facilities - Technical Guidelines", "organization": "European Commission INSPIRE Maintenance and Implementation Group", "url": "https://inspire-mif.github.io/technical-guidelines/data/ef/dataspecification_ef.html", "version_or_date": "3.2.0 header, 2024-01-31; body retains some 3.0 wording", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:28:26Z", "relevance": "Sections 2.2, 2.4 and 5.3.2 distinguish facility, network, programme and activity; mobile and operational periods support qualified facility profiles. Guidance alignment, not a legal-compliance claim." }, { "id": "SRC-002", "title": "OGC SensorThings API Part 1: Sensing Version 1.1", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/18-088/18-088.html", "version_or_date": "18-088, 1.1, 2021-08-04", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:28:26Z", "relevance": "Sections 8.1 and 8.2 separate service-local identity, Thing, historical location, sensor, stream, observed property and feature of interest; observation times and quality remain observation metadata. No API implementation is claimed." }, { "id": "SRC-003", "title": "Semantic Sensor Network Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-ssn/", "version_or_date": "2017 recommendation with December 2017 editorial status note; rolling URL", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:28:26Z", "relevance": "Sections 4.9 and 5.1 separate platform, system and deployment and qualify capability by conditions. Used as conceptual vocabulary, not an asserted ontology conformance." }, { "id": "SRC-004", "title": "Frequently Asked Questions on WIGOS Station Identifier", "organization": "World Meteorological Organization", "url": "https://community.wmo.int/site/knowledge-hub/programmes-and-initiatives/wmo-integrated-global-observing-system-wigos/implementation-of-wmo-integrated-global-observing-system-wigos/frequently-asked-questions-faqs-wigos-station-identifier-wsi", "version_or_date": "FAQ version 1.0; page accessed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:28:26Z", "relevance": "Questions 4-11 and 15 support issuer-qualified identity, primary and alias identifiers, authorized metadata editors and a qualified relocation decision. Applies to the WIGOS profile, not every station." }, { "id": "SRC-005", "title": "Guidelines and standard procedures for continuous water-quality monitors: Station operation, record computation, and data reporting", "organization": "United States Geological Survey", "url": "https://www.usgs.gov/publications/guidelines-and-standard-procedures-continuous-water-quality-monitors-station-operation", "version_or_date": "Techniques and Methods 1-D3, 2006-04-28; official abstract only reviewed", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:28:26Z", "relevance": "Official abstract supports separate site selection, inspection, calibration, correction and record review concerns. Full manual not retrieved; no numeric calibration thresholds or water-domain rules generalized." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation 2013-04-30; rolling URL", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:28:26Z", "relevance": "Entity, activity, agent and qualified derivation/revision support evidence attribution and supersession. They do not establish truth, retention obligations or publication authority." } ], "structure": { "bundles": [ { "id": "b-identity", "name": "Station identity and responsibility", "description": "Station-specific context for station identity and responsibility.", "rationale": "Proposed grouping of evidence-backed station concerns; references remain owned by their authoritative masters.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "layers": [ { "id": "l-registration", "name": "Identifiers and classification", "description": "Effective assertions and evidence about identifiers and classification.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "findings": [ { "id": "f-station-identity", "name": "Qualified station identity", "description": "Resolve a persistent facility against the relevant issuer and master; preserve aliases without merging by name or coordinates.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "q-station-identity-1", "text": "Which master and issuer establish this station identity, and which identifiers are aliases?", "kind": "identity", "answer_data": [ "d-station-identity-identity-map" ] }, { "id": "q-station-identity-2", "text": "Which facility profile admits this object as a station rather than an instrument, campaign or network?", "kind": "classification", "answer_data": [ "d-station-identity-facility-profile" ] }, { "id": "q-station-identity-3", "text": "What evidence distinguishes co-located stations or justifies a proposed duplicate match?", "kind": "evidence", "answer_data": [ "d-station-identity-identity-evidence" ] } ], "data_elements": [ { "id": "d-station-identity-identity-map", "name": "Identity map", "description": "Master namespace and identifier, issuing authority reference, alias namespace, primary flag and validity interval.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "d-station-identity-facility-profile", "name": "Facility profile", "description": "Versioned profile reference, facility class, fixed or mobile applicability and rationale.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "d-station-identity-identity-evidence", "name": "Identity evidence", "description": "Registry assertions, source dates, conflicting identifiers and unresolved duplicate candidates; coordinates alone are insufficient.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "a-station-identity", "name": "Qualified station identity evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "f-identity-continuity", "name": "Continuity and reassignment decisions", "description": "Relocation, reopening and identifier changes require an evidenced continuity decision under the issuing profile.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "q-identity-continuity-1", "text": "Who decided whether a move retains station identity or creates a successor?", "kind": "authority", "answer_data": [ "d-identity-continuity-continuity-decision" ] }, { "id": "q-identity-continuity-2", "text": "How are closure, reopening and identifier reassignment distinguished in the history?", "kind": "lifecycle", "answer_data": [ "d-identity-continuity-identity-events" ] }, { "id": "q-identity-continuity-3", "text": "Which unresolved identity conflict prevents an automatic merge or historical data join?", "kind": "exception", "answer_data": [ "d-identity-continuity-identity-conflicts" ] } ], "data_elements": [ { "id": "d-identity-continuity-continuity-decision", "name": "Continuity decision", "description": "Decision maker role, profile version, rationale, old and new master references and effective time.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "d-identity-continuity-identity-events", "name": "Identity events", "description": "Event type, station reference, issuer decision and predecessor or successor links; no automatic reuse.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "d-identity-continuity-identity-conflicts", "name": "Identity conflicts", "description": "Competing assertions, affected interval, blocked operation and resolution evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "a-identity-continuity", "name": "Continuity and reassignment decisions evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "l-responsibility", "name": "Responsibility and affiliations", "description": "Effective assertions and evidence about responsibility and affiliations.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "f-stewardship", "name": "Accountable roles and memberships", "description": "Separate station stewardship, site rights, instrument custody and data publishing responsibility, with dated network participation.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "q-stewardship-1", "text": "Which responsible roles govern the station metadata, instruments, site access and data release?", "kind": "ownership", "answer_data": [ "d-stewardship-responsibility-assignments" ] }, { "id": "q-stewardship-2", "text": "Which networks and programmes receive station contributions during each membership period?", "kind": "relationship", "answer_data": [ "d-stewardship-affiliations" ] }, { "id": "q-stewardship-3", "text": "What happens when stewardship changes or membership evidence is missing?", "kind": "process", "answer_data": [ "d-stewardship-handover-record" ] } ], "data_elements": [ { "id": "d-stewardship-responsibility-assignments", "name": "Responsibility assignments", "description": "Role, external party identifier, responsibility scope, authority evidence and validity interval; use role labels rather than named company owners.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "d-stewardship-affiliations", "name": "Affiliations", "description": "External network and programme references, contribution scope and start/end times.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "d-stewardship-handover-record", "name": "Handover record", "description": "Outgoing and incoming role references, unresolved obligations, evidence transfer status and escalation route.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "a-stewardship", "name": "Accountable roles and memberships evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-space", "name": "Location and environmental context", "description": "Station-specific context for location and environmental context.", "rationale": "Proposed grouping of evidence-backed station concerns; references remain owned by their authoritative masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-005" ], "layers": [ { "id": "l-location", "name": "Effective spatial context", "description": "Effective assertions and evidence about effective spatial context.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "findings": [ { "id": "f-position", "name": "Position and spatial reference", "description": "Keep the station reference position distinct from sensor positions and observed features, with uncertainty and validity.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "q-position-1", "text": "What station geometry, horizontal reference system and vertical datum apply for this interval?", "kind": "spatial", "answer_data": [ "d-position-station-position" ] }, { "id": "q-position-2", "text": "How was the position established and what positional uncertainty or precision is reported?", "kind": "measurement", "answer_data": [ "d-position-position-evidence" ] }, { "id": "q-position-3", "text": "How does a mobile profile bind timestamped positions to a platform without using the latest location for old data?", "kind": "temporal", "answer_data": [ "d-position-trajectory-binding" ] } ], "data_elements": [ { "id": "d-position-station-position", "name": "Station position", "description": "Geometry, CRS identifier, axis order, elevation or depth, units, vertical datum and effective interval.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "d-position-position-evidence", "name": "Position evidence", "description": "Survey or reporting method, evidence reference, uncertainty units, observation time and unknown status.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "d-position-trajectory-binding", "name": "Trajectory binding", "description": "Platform master reference, trajectory dataset revision, time reference and resolution; not applicable reason for fixed profiles.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "a-position", "name": "Position and spatial reference evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "f-geometry-history", "name": "Siting change evidence", "description": "Separate changed coordinates, corrected metadata and actual facility movement; do not infer a homogeneous series from identity continuity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "questions": [ { "id": "q-geometry-history-1", "text": "Was a geometry change a relocation, a survey correction or a changed coordinate representation?", "kind": "event", "answer_data": [ "d-geometry-history-location-change" ] }, { "id": "q-geometry-history-2", "text": "Which observations or deployments might be affected by the change interval?", "kind": "relationship", "answer_data": [ "d-geometry-history-spatial-impact-links" ] }, { "id": "q-geometry-history-3", "text": "What evidence supports continuity across the change and what comparability limitations remain?", "kind": "quality", "answer_data": [ "d-geometry-history-comparability-review" ] } ], "data_elements": [ { "id": "d-geometry-history-location-change", "name": "Location change", "description": "Change classification, old and new geometry references, evidence and decision time.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "d-geometry-history-spatial-impact-links", "name": "Spatial impact links", "description": "External record or deployment references, uncertainty interval and review status; no automatic reprocessing.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "d-geometry-history-comparability-review", "name": "Comparability review", "description": "Review reference, exposure differences, reviewer role and unresolved discontinuity statement.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "a-geometry-history", "name": "Siting change evidence evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "l-exposure", "name": "Exposure and representativeness", "description": "Effective assertions and evidence about exposure and representativeness.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "f-site-context", "name": "Site exposure evidence", "description": "Represent exposure as a dated assessment relative to a monitoring purpose; station appearance alone is not verification.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "q-site-context-1", "text": "Which surroundings and sampling context matter for the declared environmental monitoring objective?", "kind": "spatial", "answer_data": [ "d-site-context-exposure-context" ] }, { "id": "q-site-context-2", "text": "What domain-specific siting or representativeness assessment was applied and by whom?", "kind": "validation", "answer_data": [ "d-site-context-siting-assessment" ] }, { "id": "q-site-context-3", "text": "Which site changes trigger a new review of representativeness?", "kind": "constraint", "answer_data": [ "d-site-context-exposure-triggers" ] } ], "data_elements": [ { "id": "d-site-context-exposure-context", "name": "Exposure context", "description": "Environmental medium, terrain or water-body context, obstructions or nearby influences, evidence and assessment interval.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "d-site-context-siting-assessment", "name": "Siting assessment", "description": "Assessment artifact reference, profile version, reviewer role and limitations; no universal siting score.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "d-site-context-exposure-triggers", "name": "Exposure triggers", "description": "Profile-specific triggers, detected changes, monitoring evidence and assigned review status.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "a-site-context", "name": "Site exposure evidence evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-configuration", "name": "Installed systems and capabilities", "description": "Station-specific context for installed systems and capabilities.", "rationale": "Proposed grouping of evidence-backed station concerns; references remain owned by their authoritative masters.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ], "layers": [ { "id": "l-deployment", "name": "Deployment bindings", "description": "Effective assertions and evidence about deployment bindings.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ], "findings": [ { "id": "f-instrument-deployment", "name": "Effective instrument and sampler deployment", "description": "Track installation relationships without copying the instrument master or treating serial number as station identity.", "source_refs": [ "SRC-003", "SRC-005" ], "questions": [ { "id": "q-instrument-deployment-1", "text": "Which instrument, sampler or procedure is deployed for each station channel and interval?", "kind": "composition", "answer_data": [ "d-instrument-deployment-deployment-links" ] }, { "id": "q-instrument-deployment-2", "text": "Where is each sensing or sampling point relative to its host and reference surface?", "kind": "spatial", "answer_data": [ "d-instrument-deployment-sampling-position" ] }, { "id": "q-instrument-deployment-3", "text": "Which deployment conflicts or unrecorded replacements block reliable attribution?", "kind": "exception", "answer_data": [ "d-instrument-deployment-deployment-conflicts" ] } ], "data_elements": [ { "id": "d-instrument-deployment-deployment-links", "name": "Deployment links", "description": "External master references, channel identifier, installation/removal times and deployment evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] }, { "id": "d-instrument-deployment-sampling-position", "name": "Sampling position", "description": "Instrument reference, height/depth or offset, units, datum, orientation where relevant and valid interval.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] }, { "id": "d-instrument-deployment-deployment-conflicts", "name": "Deployment conflicts", "description": "Overlapping assignments, missing device identifiers, affected channels and resolution evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "a-instrument-deployment", "name": "Effective instrument and sampler deployment evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "f-configuration-revision", "name": "Configuration and method revisions", "description": "Pin configuration assertions and method references to effective periods; local recording does not reconfigure devices.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "q-configuration-revision-1", "text": "Which configuration and procedure revisions applied when a channel acquired data?", "kind": "provenance", "answer_data": [ "d-configuration-revision-configuration-pins" ] }, { "id": "q-configuration-revision-2", "text": "What approved change evidence connects the previous and replacement configuration?", "kind": "authority", "answer_data": [ "d-configuration-revision-configuration-change" ] }, { "id": "q-configuration-revision-3", "text": "How is a late metadata correction distinguished from an actual equipment change?", "kind": "temporal", "answer_data": [ "d-configuration-revision-configuration-times" ] } ], "data_elements": [ { "id": "d-configuration-revision-configuration-pins", "name": "Configuration pins", "description": "Channel, device, configuration digest or revision, method reference and valid interval.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "d-configuration-revision-configuration-change", "name": "Configuration change", "description": "Approval record reference, responsible role, reason, predecessor and effective time.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "d-configuration-revision-configuration-times", "name": "Configuration times", "description": "Asserted effective interval, recorded time, correction reason and superseded assertion identifier.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "a-configuration-revision", "name": "Configuration and method revisions evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "l-capability", "name": "Capability and constraints", "description": "Effective assertions and evidence about capability and constraints.", "source_refs": [ "SRC-003" ], "findings": [ { "id": "f-measurement-capability", "name": "Qualified measurement capability", "description": "Separate advertised capability, verified capability and current operating status; properties depend on conditions and methods.", "source_refs": [ "SRC-003" ], "questions": [ { "id": "q-measurement-capability-1", "text": "What variable range, resolution and uncertainty are claimed for a station channel under stated conditions?", "kind": "measurement", "answer_data": [ "d-measurement-capability-capability-assertion" ] }, { "id": "q-measurement-capability-2", "text": "Which environmental or infrastructure constraints limit the usable capability?", "kind": "constraint", "answer_data": [ "d-measurement-capability-operating-constraints" ] }, { "id": "q-measurement-capability-3", "text": "What evidence or expiry condition makes a capability verified, stale or unverified?", "kind": "validation", "answer_data": [ "d-measurement-capability-capability-review" ] } ], "data_elements": [ { "id": "d-measurement-capability-capability-assertion", "name": "Capability assertion", "description": "Observed property, quantity units, range, resolution, uncertainty definition, conditions, evidence and claim status.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "d-measurement-capability-operating-constraints", "name": "Operating constraints", "description": "Condition ranges, power or communications dependencies, profile limits, evidence and unknowns.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "d-measurement-capability-capability-review", "name": "Capability review", "description": "Review reference, verification scope, effective period, next review rule and unverified reasons.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "a-measurement-capability", "name": "Qualified measurement capability evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-programme", "name": "Monitoring commitments and acquisition", "description": "Station-specific context for monitoring commitments and acquisition.", "rationale": "Proposed grouping of evidence-backed station concerns; references remain owned by their authoritative masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ], "layers": [ { "id": "l-commitment", "name": "Programme commitments", "description": "Effective assertions and evidence about programme commitments.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "findings": [ { "id": "f-monitoring-objective", "name": "Station contribution to a programme", "description": "Bind a station contribution to an external programme and target feature without absorbing programme governance.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "q-monitoring-objective-1", "text": "What purpose, environmental medium and feature of interest define this station contribution?", "kind": "definition", "answer_data": [ "d-monitoring-objective-contribution-scope" ] }, { "id": "q-monitoring-objective-2", "text": "Which station contribution is required by the applicable programme and which is voluntary or experimental?", "kind": "requirement", "answer_data": [ "d-monitoring-objective-contribution-obligations" ] }, { "id": "q-monitoring-objective-3", "text": "Which linked samples or remote targets differ from the station location?", "kind": "relationship", "answer_data": [ "d-monitoring-objective-target-bindings" ] } ], "data_elements": [ { "id": "d-monitoring-objective-contribution-scope", "name": "Contribution scope", "description": "Objective reference, medium, target feature master identifier and observed property vocabulary.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "d-monitoring-objective-contribution-obligations", "name": "Contribution obligations", "description": "Programme revision, obligation reference, scope, applicability and effective interval.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "d-monitoring-objective-target-bindings", "name": "Target bindings", "description": "Feature or sample references, spatial relation and evidence; never infer target solely from host coordinates.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "a-monitoring-objective", "name": "Station contribution to a programme evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "f-sampling-schedule", "name": "Sampling and reporting expectations", "description": "Distinguish intended cadence, actual acquisition and transmission; a reporting gap is not necessarily a measurement outage.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "questions": [ { "id": "q-sampling-schedule-1", "text": "What sampling, aggregation and reporting intervals are intended for each channel?", "kind": "temporal", "answer_data": [ "d-sampling-schedule-schedule" ] }, { "id": "q-sampling-schedule-2", "text": "What actual coverage and missing-period evidence are available against that schedule?", "kind": "quality", "answer_data": [ "d-sampling-schedule-coverage-evidence" ] }, { "id": "q-sampling-schedule-3", "text": "How are manual visits, event-triggered acquisition and approved schedule exceptions represented?", "kind": "exception", "answer_data": [ "d-sampling-schedule-schedule-exceptions" ] } ], "data_elements": [ { "id": "d-sampling-schedule-schedule", "name": "Schedule", "description": "Channel, schedule rule, sample duration, aggregation method reference, reporting interval, time zone and validity.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "d-sampling-schedule-coverage-evidence", "name": "Coverage evidence", "description": "External coverage report revision, expected denominator, excluded intervals, missing/late flags and assessment time.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "d-sampling-schedule-schedule-exceptions", "name": "Schedule exceptions", "description": "Exception kind, trigger or visit reference, authorized interval and rationale without assuming continuous sampling.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "a-sampling-schedule", "name": "Sampling and reporting expectations evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "l-data-binding", "name": "Observation and delivery bindings", "description": "Effective assertions and evidence about observation and delivery bindings.", "source_refs": [ "SRC-002", "SRC-006" ], "findings": [ { "id": "f-data-streams", "name": "Observation streams and delivery references", "description": "Link data services and record revisions using full namespaces, preserving target feature, quality and time semantics.", "source_refs": [ "SRC-002", "SRC-006" ], "questions": [ { "id": "q-data-streams-1", "text": "Which external streams or datasets bind this station, sensor, observed property and feature of interest?", "kind": "interoperability", "answer_data": [ "d-data-streams-stream-bindings" ] }, { "id": "q-data-streams-2", "text": "How are phenomenon time, result time and ingestion time preserved at the binding boundary?", "kind": "temporal", "answer_data": [ "d-data-streams-time-mapping" ] }, { "id": "q-data-streams-3", "text": "Which delivery, licensing or mapping failure prevents a usable observation reference?", "kind": "access", "answer_data": [ "d-data-streams-delivery-status" ] } ], "data_elements": [ { "id": "d-data-streams-stream-bindings", "name": "Stream bindings", "description": "Service namespace, entity type and identifier, dataset revision, channel and semantic mapping version.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006" ] }, { "id": "d-data-streams-time-mapping", "name": "Time mapping", "description": "Source time fields, clock/timezone assumptions, interval semantics, mapping and known precision loss.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-006" ] }, { "id": "d-data-streams-delivery-status", "name": "Delivery status", "description": "Endpoint reference, access policy, license reference, last verified time and missing/unavailable/lossy status; no embedded credentials.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "a-data-streams", "name": "Observation streams and delivery references evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-assurance", "name": "Operational and quality evidence", "description": "Station-specific context for operational and quality evidence.", "rationale": "Proposed grouping of evidence-backed station concerns; references remain owned by their authoritative masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-001", "SRC-003", "SRC-002" ], "layers": [ { "id": "l-maintenance", "name": "Maintenance and operational status", "description": "Effective assertions and evidence about maintenance and operational status.", "source_refs": [ "SRC-005", "SRC-006", "SRC-001", "SRC-003" ], "findings": [ { "id": "f-maintenance-evidence", "name": "Maintenance and calibration evidence links", "description": "Keep service and calibration evidence as references to accountable records; the station model does not perform calibration.", "source_refs": [ "SRC-005", "SRC-006" ], "questions": [ { "id": "q-maintenance-evidence-1", "text": "Which inspection, cleaning, repair or calibration record applies to the deployed instrument?", "kind": "evidence", "answer_data": [ "d-maintenance-evidence-maintenance-links" ] }, { "id": "q-maintenance-evidence-2", "text": "What profile establishes calibration validity, review intervals and reference traceability?", "kind": "requirement", "answer_data": [ "d-maintenance-evidence-calibration-policy" ] }, { "id": "q-maintenance-evidence-3", "text": "Which affected station periods require review following failed or missing maintenance evidence?", "kind": "process", "answer_data": [ "d-maintenance-evidence-maintenance-impact" ] } ], "data_elements": [ { "id": "d-maintenance-evidence-maintenance-links", "name": "Maintenance links", "description": "Instrument and deployment reference, service record revision, event time, performer role and result.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] }, { "id": "d-maintenance-evidence-calibration-policy", "name": "Calibration policy", "description": "Profile version, reference standard identifier, evidence location, validity conditions and unknown status; no invented universal interval.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] }, { "id": "d-maintenance-evidence-maintenance-impact", "name": "Maintenance impact", "description": "Affected deployment/channel intervals, issue reference, review assignment and disposition; external data corrections remain delegated.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "a-maintenance-evidence", "name": "Maintenance and calibration evidence links evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "f-operational-state", "name": "Observed availability and outages", "description": "Record station and channel states separately, with dated evidence and freshness; connectivity is not measurement health.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "questions": [ { "id": "q-operational-state-1", "text": "What operational state is evidenced for the station and each channel at the assessment time?", "kind": "state", "answer_data": [ "d-operational-state-availability-assertions" ] }, { "id": "q-operational-state-2", "text": "Was a gap caused by acquisition, power, transmission, processing or an unresolved cause?", "kind": "event", "answer_data": [ "d-operational-state-outage-record" ] }, { "id": "q-operational-state-3", "text": "What evidence supports return to service and what restrictions remain?", "kind": "decision", "answer_data": [ "d-operational-state-return-review" ] } ], "data_elements": [ { "id": "d-operational-state-availability-assertions", "name": "Availability assertions", "description": "Station/channel scope, state, evidence, observation time, expiry and unknown status.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "d-operational-state-outage-record", "name": "Outage record", "description": "Start/end bounds, affected scope, cause classification, uncertainty and external incident reference.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "d-operational-state-return-review", "name": "Return review", "description": "Responsible reviewer role, acceptance evidence, restored capabilities and restricted intervals; no physical activation effect.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "a-operational-state", "name": "Observed availability and outages evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "l-quality", "name": "Quality review and lineage", "description": "Effective assertions and evidence about quality review and lineage.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ], "findings": [ { "id": "f-quality-disposition", "name": "Quality status and correction provenance", "description": "Preserve separate raw, corrected and released record references; quality judgments apply to explicit scopes and profiles.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-quality-disposition-1", "text": "Which quality flags, uncertainty statements or review outcomes apply to each referenced record interval?", "kind": "quality", "answer_data": [ "d-quality-disposition-quality-links" ] }, { "id": "q-quality-disposition-2", "text": "What derivation connects raw data, corrections and released versions?", "kind": "provenance", "answer_data": [ "d-quality-disposition-derivation-links" ] }, { "id": "q-quality-disposition-3", "text": "Who authorized a quality disposition and what prevents provisional or invalid data from appearing as approved?", "kind": "authority", "answer_data": [ "d-quality-disposition-release-disposition" ] } ], "data_elements": [ { "id": "d-quality-disposition-quality-links", "name": "Quality links", "description": "Dataset revision, flag vocabulary version, assessment scope, reviewer, evidence and unknown status.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "d-quality-disposition-derivation-links", "name": "Derivation links", "description": "Input and output record identifiers, processing activity reference, method revision and attribution; payload remains external.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "d-quality-disposition-release-disposition", "name": "Release disposition", "description": "Release decision reference, responsible role, allowed use, visible status and unresolved exceptions; no safety certification.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "a-quality-disposition", "name": "Quality status and correction provenance evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-continuity", "name": "Record governance and continuity", "description": "Station-specific context for record governance and continuity.", "rationale": "Proposed grouping of evidence-backed station concerns; references remain owned by their authoritative masters.", "source_refs": [ "SRC-006", "SRC-004", "SRC-002", "SRC-001", "SRC-003" ], "layers": [ { "id": "l-history", "name": "History and retention", "description": "Effective assertions and evidence about history and retention.", "source_refs": [ "SRC-006", "SRC-004", "SRC-002" ], "findings": [ { "id": "f-station-history", "name": "Versioned station evidence history", "description": "Maintain effective and recorded metadata history while delegating retention policy and source-data custody to their owners.", "source_refs": [ "SRC-006", "SRC-004" ], "questions": [ { "id": "q-station-history-1", "text": "Which evidence and assertion version supports a station fact for the requested historical interval?", "kind": "provenance", "answer_data": [ "d-station-history-assertion-history" ] }, { "id": "q-station-history-2", "text": "What retention schedule, hold and disposal authority applies to local station metadata and linked evidence?", "kind": "retention", "answer_data": [ "d-station-history-retention-binding" ] }, { "id": "q-station-history-3", "text": "How are retirement and lawful erasure represented without reusing identifiers or falsely preserving unavailable payloads?", "kind": "lifecycle", "answer_data": [ "d-station-history-retirement-record" ] } ], "data_elements": [ { "id": "d-station-history-assertion-history", "name": "Assertion history", "description": "Assertion ID, subject scope, value reference, effective interval, recorded time, author role and supporting artifact.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-004" ] }, { "id": "d-station-history-retention-binding", "name": "Retention binding", "description": "Policy reference, retention class, active holds, custodian and permitted disposal action; observation custody remains external.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-004" ] }, { "id": "d-station-history-retirement-record", "name": "Retirement record", "description": "Retirement reason, successor link, minimal lawful tombstone, disposed scopes and access limitations.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-004" ] } ], "artifacts": [ { "id": "a-station-history", "name": "Versioned station evidence history evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-006", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "f-controlled-access", "name": "Disclosure and permitted actions", "description": "Proposed local governance separates metadata visibility from equipment authority and protects sensitive locations and contacts.", "source_refs": [ "SRC-002", "SRC-006" ], "questions": [ { "id": "q-controlled-access-1", "text": "Which station facts and artifacts are public, restricted or available only for an approved purpose?", "kind": "access", "answer_data": [ "d-controlled-access-disclosure-policy" ] }, { "id": "q-controlled-access-2", "text": "What permissions distinguish metadata editing, data release and physical or remote equipment actions?", "kind": "security", "answer_data": [ "d-controlled-access-action-authority" ] }, { "id": "q-controlled-access-3", "text": "How are exceptional access, revocation and redacted views recorded for review?", "kind": "privacy", "answer_data": [ "d-controlled-access-access-evidence" ] } ], "data_elements": [ { "id": "d-controlled-access-disclosure-policy", "name": "Disclosure policy", "description": "Adopting policy revision with scopes, subject roles, permitted purposes and restricted-location handling.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-006" ] }, { "id": "d-controlled-access-action-authority", "name": "Action authority", "description": "Action classes, responsible roles, required authority evidence and refusal conditions; local edit rights grant no control permission.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-006" ] }, { "id": "d-controlled-access-access-evidence", "name": "Access evidence", "description": "Decision reference, recipient role, scope, reason, expiry and external audit link without secrets or unnecessary personal data.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "a-controlled-access", "name": "Disclosure and permitted actions evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "l-mapping", "name": "Mapping and adoption readiness", "description": "Effective assertions and evidence about mapping and adoption readiness.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "f-profile-conformance", "name": "Profile mapping and unresolved conformance", "description": "Treat standards as versioned alignments; adoption requires explicit instance schemas and tested mappings.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "q-profile-conformance-1", "text": "Which exact profile revisions and optional fields does this station instance adopt?", "kind": "interoperability", "answer_data": [ "d-profile-conformance-profile-pins" ] }, { "id": "q-profile-conformance-2", "text": "What evidence demonstrates that an export preserves identity, times, quantities, relationships and quality flags?", "kind": "validation", "answer_data": [ "d-profile-conformance-mapping-evidence" ] }, { "id": "q-profile-conformance-3", "text": "Which unresolved fields or bindings prevent operational or canonical use?", "kind": "constraint", "answer_data": [ "d-profile-conformance-adoption-gaps" ] } ], "data_elements": [ { "id": "d-profile-conformance-profile-pins", "name": "Profile pins", "description": "Profile identifier, version, field applicability, units and vocabulary pins with unknown/not-applicable distinctions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "d-profile-conformance-mapping-evidence", "name": "Mapping evidence", "description": "Mapping version, directional test report, fixture references and documented losses; absent tests mean unverified.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "d-profile-conformance-adoption-gaps", "name": "Adoption gaps", "description": "Gap, affected scope, consequence, responsible review role and acceptance evidence still required.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "a-profile-conformance", "name": "Profile mapping and unresolved conformance evidence record", "description": "Versioned evidence index for this finding; carries attributed assertions and references, not a duplicate master for instruments or observations.", "media_or_form": [ "Structured metadata record", "Linked evidence manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus record revision; otherwise a governed IRI, then a Dimension-issued UUID or ULID. Station, record and payload digest have distinct roles. Dates alone are not identifiers.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "fn-resolve-station", "name": "Resolve a station reference", "description": "Proposed, unimplemented local function. Resolve identifiers without auto-merging facilities.", "inputs": [ "Issuer-qualified identifiers", "Candidate master bindings" ], "outputs": [ "Resolved reference or ambiguous/unresolved report" ], "preconditions": [ "Authorized read scope and issuer namespace available" ], "effects": [ "Returns a local resolution report; changes no identifier assignments" ], "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "fn-record-deployment", "name": "Record a deployment assertion", "description": "Proposed, unimplemented local function. Record an evidenced relationship; does not install or configure instruments.", "inputs": [ "Station and device references", "Effective interval and evidence", "Expected local revision" ], "outputs": [ "New local assertion revision or refusal" ], "preconditions": [ "Authorized metadata editor", "Evidence and referenced masters resolvable", "No unreviewed contradictory interval" ], "effects": [ "Appends station deployment metadata and predecessor link; device master unchanged" ], "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "fn-record-change", "name": "Record a station change", "description": "Proposed, unimplemented local function. Record an approved move, profile or configuration decision without executing it.", "inputs": [ "Change decision reference", "Old and new assertions", "Effective and recorded times" ], "outputs": [ "Revision with affected-scope report or refusal" ], "preconditions": [ "Authority evidence", "Expected revision matches", "Identity impact reviewed when relocation changes issuer rules" ], "effects": [ "Versions local assertions; creates no physical change or external notification" ], "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "fn-check-bindings", "name": "Check observation bindings", "description": "Proposed, unimplemented local function. Proposed metadata checks of identity, channel and time compatibility; no scientific quality certification.", "inputs": [ "Station revision", "Dataset and stream references", "Pinned mapping profile" ], "outputs": [ "Pass, failed or unverified binding report with reasons" ], "preconditions": [ "Read access", "Explicit time/unit vocabularies", "No guessing unresolved semantic fields" ], "effects": [ "Produces local discrepancy evidence; does not correct or ingest source observations" ], "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "fn-record-review", "name": "Record an operational or quality review", "description": "Proposed, unimplemented local function. Link an authorized outcome while retaining unresolved and contrary evidence.", "inputs": [ "Reviewer role and decision", "Scoped record references", "Evidence and expiry" ], "outputs": [ "Versioned review link or refusal" ], "preconditions": [ "Review authority matches scope", "Evidence available", "Provisional and approved states distinguished" ], "effects": [ "Updates local review assertions; grants no release permission or equipment activation" ], "source_refs": [ "SRC-005", "SRC-006" ] }, { "id": "fn-retire-record", "name": "Retire a local station record", "description": "Proposed, unimplemented local function. Deprecate local metadata under an adopting retention policy; no physical closure.", "inputs": [ "Retirement decision", "Successor mapping", "Retention and hold checks" ], "outputs": [ "Retired local revision or refusal" ], "preconditions": [ "Authorized steward", "Hold review completed", "External custodians identified" ], "effects": [ "Preserves lawful tombstone and referential continuity; payload disposal requires separately authorized policy execution" ], "source_refs": [ "SRC-004", "SRC-006" ] } ], "composition": [ { "target": "WM-OBJ-023 Meter / Measuring Instrument", "relation": "ALIGN", "purpose": "Qualified registry parent candidate, not automatic inheritance; station records deployment references while device identity and calibration execution remain external.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "Instrument and sampler masters", "relation": "REFERENCE", "purpose": "Bind deployed items and procedures by master identifier and revision; no duplication of device lifecycle.", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] }, { "target": "Monitoring programme and network masters", "relation": "REFERENCE", "purpose": "Reference station contributions and membership intervals without copying network governance.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "Observation, sample and dataset masters", "relation": "REFERENCE", "purpose": "Bind features, streams, quality dispositions and lineage; external custodians own observations and processing.", "required": false, "source_refs": [ "SRC-002", "SRC-006" ] }, { "target": "Site and platform masters", "relation": "REFERENCE", "purpose": "Locate and host the facility using applicable fixed or mobile profiles; platform control remains external.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "OGC SensorThings 1.1; SSN/SOSA; INSPIRE EF", "relation": "ALIGN", "purpose": "Conceptual alignment only; implementation mappings, required cardinalities and conformance fixtures remain adoption work.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Accountable station steward role and issuer-qualified identity authority", "Declared fixed or mobile facility profile, environmental domain and jurisdiction", "Versioned access, retention, quality-review and metadata-change policies", "Pinned external masters, vocabulary/unit choices and service bindings" ], "namespace_guidance": "Use a governed station namespace. Keep station, deployment, channel, observation, artifact and assertion IDs distinct. An API-local integer requires service namespace and entity type.", "registry_links": [ "vr.wm-ear-012", "WM-OBJ-023 as qualified alignment candidate" ] }, "canon_and_patch": { "canonicalization_rules": [ "This single-provider result is a noncanonical reviewable draft; source presence does not prove standards conformance.", "Preserve issuer-qualified identity, explicit unknown values and effective intervals; no identity merge from labels, coordinates or device serial numbers." ], "patch_rules": [ "Require role, purpose, expected revision, evidence and effective/recorded times for each patch. Conflicting evidence remains visible.", "Separate corrected metadata from actual station changes; material scope changes require a new reviewed model version." ], "compatibility_rules": [ "Preserve stable IDs and provide explicit migration mappings; quantity, CRS, quality-flag or time semantics must not change silently.", "Breaking profile changes require a versioned mapping and evidence of losses; no automatic reinterpretation of old observations." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with issuer namespace", "Governed global identifier or IRI", "Dimension-issued UUID or ULID" ], "timestamp_rule": "RFC 3339 timestamps include seconds and an explicit offset or Z. Preserve effective/event time, observation time, result time and ingestion/recorded time separately. Keep source precision and uncertainty; unknown seconds must not be presented as measured precision.", "serial_naming_rule": "Use station and artifact master identifiers plus immutable revision; dates are sortable labels only and never sole identity.", "integrity_rule": "Record payload digest, algorithm, media type, source reference and revision. A matching digest establishes byte integrity, not measurement validity or authority. Preserve redaction and disposal state." }, "policies": [ "These are proposed adopting-Dimension rules, not access or retention requirements attributed to environmental standards.", "Do not infer data validity from station connectivity, calibration date alone, an empty error list or a publication flag.", "External release, remote control and physical work require their separately authorized process; a local metadata function grants none of these permissions.", "Keep sensitive site details and personal contacts purpose-limited; publish an authorized redacted view when appropriate. Safety and hazard matters remain policy references, not operating instructions." ], "crud": { "read": [ "Return policy-filtered metadata with effective interval, recorded time, evidence and review status; disclose unresolved references." ], "create": [ "Require authority, master identity resolution and explicit profile before creating a local record; tentative assertions remain labelled." ], "update": [ "Use expected-revision checks and append an attributed assertion revision; retain conflicting and superseded evidence subject to lawful retention." ], "delete": [ "Retire local station metadata using the declared retention schedule, holds and authorized disposition. Preserve a minimal lawful tombstone where permitted; erase restricted payloads when required.", "Observation, device and site masters own execution of their own deletion. Local retirement neither closes a physical station nor deletes referenced observations." ] }, "roles": [ { "name": "Station steward", "responsibilities": [ "Resolve identity and approve local metadata continuity decisions" ] }, { "name": "Metadata editor", "responsibilities": [ "Record evidence-backed assertions within authorized scope" ] }, { "name": "Instrument custodian", "responsibilities": [ "Provide deployment and service evidence; owns instrument actions externally" ] }, { "name": "Quality reviewer", "responsibilities": [ "Provide scoped quality and return-to-service evidence" ] }, { "name": "Data custodian", "responsibilities": [ "Govern observation records, release and retention in the external master" ] }, { "name": "Consumer", "responsibilities": [ "Read authorized views with limitations and hold status" ] } ], "access": { "default_rule": "Deny mutation and restricted evidence access unless a versioned policy grants the role and purpose; public read access is an explicit projection decision.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Time-limited exceptional access requires authority evidence, scope and expiry.", "Sensitive coordinates or contacts may be redacted without falsely claiming absence of the underlying evidence." ], "audit_requirements": [ "Record actor role, purpose, scope, policy version, previous/new revision and decision reference.", "Link to an external audit master for enforcement and retention; never store credentials in station artifacts." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and adopting Dimension policies", "spec.yaml review state and publication holds", "Station profile, identifiers and authority evidence", "Effective configuration and external master bindings", "Scoped findings, evidence and unresolved issues" ] } }, "coverage": { "claim": "Source-grounded proposed context for one persistent environmental monitoring station with explicit fixed or mobile facility profiles. Separate local no-tools self-audit completed. Source/version review, domain applicability, executable mappings and independent external review remain holds. This is a noncanonical reviewable draft, not an operational station controller or a universal environmental compliance model.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Issuer-qualified facility identity and relocation decisions; co-location is insufficient." }, { "dimension": "lifecycle", "status": "covered", "notes": "Operational periods, temporary suspension, reopening and local retirement." }, { "dimension": "relationships", "status": "covered", "notes": "Optional network, programme, device, site and observation master bindings." }, { "dimension": "temporal", "status": "covered", "notes": "Effective, event, result and recorded times remain distinct; schedules do not imply acquisition." }, { "dimension": "provenance", "status": "covered", "notes": "Attributed assertions, revision links and external correction lineage." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based stewardship, custodianship and release authority remain separate." }, { "dimension": "validation", "status": "gap", "notes": "Research schema valid when checked; nested instance schemas and domain acceptance tests remain missing." }, { "dimension": "access", "status": "covered", "notes": "Proposed policy-bound scopes, sensitive locations and revocable views." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Local disposition and tombstones are policy-qualified; external data remains separately controlled." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual standards alignments only; executable and directional mappings are untested." }, { "dimension": "properties and recognition", "status": "covered", "notes": "CRS, vertical datum, exposure, position evidence and channel quantities; appearance is not station identity." }, { "dimension": "capabilities and behaviour", "status": "covered", "notes": "Claimed capability, conditions, observed status, outage and return review remain distinct." }, { "dimension": "source verification", "status": "gap", "notes": "Web content access supports selected claims; direct HTTP status unmeasured and edition/applicability review incomplete." }, { "dimension": "independent review", "status": "gap", "notes": "Claude and Grok skipped under owner waiver; separate local audit is not independent external review." } ], "known_omissions": [ "Nested data schemas, validation fixtures and pinned neighbor-model versions are incomplete.", "No exhaustive air, soil, biodiversity, radiation or marine profile; hydrology evidence is limited to an official report abstract.", "No physical maintenance procedures, numeric siting/calibration limits, warning thresholds or regulatory certification.", "Direct HTTP checks not attempted under the owner-reported sandbox block; version, licensing and applicability verification remain open.", "Independent external review is absent under the single-provider waiver." ], "conflicts": [], "regional_assumptions": [ "INSPIRE is European technical guidance; it is used as a conceptual alignment without imposing EU duties globally.", "WIGOS identifier decisions apply only within the relevant issuing scheme. Fixed relocation and closed-site reopening need distinct review.", "USGS 2006 abstract supports a water-quality evidence pattern, not current universal operating requirements." ], "adversarial_checks": [ "A replaced sensor does not automatically create a new station, and retained station identity does not establish homogeneous data.", "A mobile platform position is not necessarily the observation feature location; late location updates must not rewrite historical positions.", "A connected station can have invalid measurements; missing transmissions can coexist with valid buffered acquisition.", "No local metadata operation calibrates, activates, publishes observations, issues warnings or overrides an external master.", "A source URL and a digest cannot prove current source versions, scientific truth or implementation conformance." ] }, "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": "One steward-recognized observing facility retains identity through documented operational periods and configuration changes. It is distinct from a device, observation event, programme or network. Fixed is an adoption default; mobility requires an explicit facility profile. Registry standalone-mm is not a research subject-kind enum." }, "decisions": [ { "concept": "Persistent facility boundary", "disposition": "accepted", "rationale": "Identity continuity and effective relationships support entity. The scope excludes a campaign without facility identity and an entire monitoring network." }, { "concept": "Fixed-only supplement definition", "disposition": "qualified", "rationale": "The source material admits mobile facilities. The result requires a declared profile and platform/trajectory bindings instead of imposing the unreviewed supplement's fixed-only rule." }, { "concept": "Registry instrument parent", "disposition": "qualified alignment", "rationale": "Hosting instruments does not prove subtype inheritance. The WM-OBJ-023 candidate is explicitly alignment, with device masters and calibration execution external." }, { "concept": "Relocation and reopening identity", "disposition": "accepted with issuer qualification", "rationale": "Questions require the governing issuer decision and distinguish closed-site reopening from a move. Neither identifier reuse nor replacement is automatic." }, { "concept": "Spatial and observation identity", "disposition": "separated", "rationale": "Station position, instrument offset, platform trajectory and observed feature remain distinct. Coordinates alone cannot establish facility identity or rewrite historical positions." }, { "concept": "Programme and network ownership", "disposition": "reference only", "rationale": "The local model carries contribution and membership intervals. Programme definitions, network governance and system-wide coverage remain external." }, { "concept": "Capability and availability", "disposition": "separated", "rationale": "Claimed range and uncertainty require conditions and evidence. Operating status, connectivity and measured quality do not imply one another." }, { "concept": "Schedules and observation records", "disposition": "accepted with external custody", "rationale": "Intended sampling and reporting schedules are compared with referenced coverage evidence. The functions neither acquire physical observations nor correct dataset payloads." }, { "concept": "Maintenance and quality authority", "disposition": "reference only", "rationale": "Service and calibration evidence stays in external records. Local review links do not perform calibration, authorize source-data release or certify scientific fitness." }, { "concept": "Proposed local functions", "disposition": "accepted as unimplemented design", "rationale": "Each function specifies inputs, outputs, preconditions and limited metadata effects. Physical action, external writes, warning issuance and instrument control are outside scope." }, { "concept": "Record history and access", "disposition": "accepted with adopting policies", "rationale": "Effective and recorded times remain distinct. Role-based scopes, retention holds, lawful disposal and minimal tombstones avoid interpreting history as perpetual payload retention." }, { "concept": "Instance schemas and mappings", "disposition": "deferred", "rationale": "Optional candidate groups and descriptive external references are adequate research context but do not provide required instance cardinalities, nested schemas, pinned neighbors or tested mappings." }, { "concept": "Source assurance", "disposition": "limited", "rationale": "Selected web-accessed primary material supports the conceptual design. Abstract-only hydrology evidence, edition wording, rolling URLs and unmeasured direct HTTP status remain explicit limitations." }, { "concept": "Independent review", "disposition": "waived and held", "rationale": "Claude and Grok were skipped with zero attempts under the owner override. This frozen Codex self-audit cannot be counted as independent provider agreement." } ], "publicationHolds": [ "Independent external review is absent. Claude and Grok were skipped under the owner-authorized single-provider waiver; the separate local Codex no-tools self-audit is not an independent second-provider review.", "Source and version verification remains incomplete. Selected primary-source content was reviewed through the web tool, but direct HTTP was not attempted under the owner-reported sandbox block. All six HTTP statuses are unmeasured. USGS full-report review, INSPIRE edition wording and current source/profile pins remain unresolved; coordinator HTTP checks alone cannot close substantive review.", "Environmental-domain, jurisdiction, licensing, station identity, site access, retention, hazard and scientific quality profiles require qualified adoption review. No numeric siting or calibration requirements, regulatory certification or fitness for warning decisions are claimed.", "Nested instance schemas, required field cardinalities, pinned neighbor bindings, executable standards mappings and adversarial conformance fixtures are incomplete. All six local functions are proposed and unimplemented.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Restore independent external review and verify exact editions, full source documents and adoption applicability before canonical promotion.", "Develop domain profiles for fixed, mobile and temporary facilities with issuer-specific relocation and reopening cases.", "Implement nested instance schemas and test mappings against co-located stations, late positions, replaced sensors, buffered data, quality corrections and lawful disposal." ] }, "statistics": { "sources": 6, "bundles": 6, "layers": 12, "findings": 18, "questions": 54, "artifacts": 18, "functions": 6 } }