# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T13:45:29Z", "synthesisSha256": "8da673d3e599adbe5835971f93c406216485e9538cdfa920a3d5ff2258f3467d", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-DAT-010", "registryId": "vr.wm-dat-010", "name": "Time Series / Observation Collection", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.DAT.TS" ], "tags": [ "time", "series", "observation", "collection", "inf.dat.ts" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-dat-010-time-series-observation-collection/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/publications/wm-dat-010-time-series-observation-collection", "model": { "registry_id": "vr.wm-dat-010", "model_id": "WM-DAT-010", "name": "Time Series / Observation Collection", "entry_kind": "aggregate", "purpose": "Represent one governed, versioned collection of ordered observations so agents can interpret values, dimensions, time, vintages, quality and provenance without confusing a series definition, individual observation, release or forecast.", "scope_statement": "Owns collection and series identity, versions, keys and lifecycle; variable, indicator, measure, unit, dimension and classification bindings; observation membership and order; qualified values, components, status, flags and missingness; phenomenon, reference, validity, result, availability, release, revision, recorded, ingestion and knowledge times; frequency, calendars and time zones; coverage, sampling and granularity; transformations, adjustments, forecasts and uncertainty; source, procedure, sensor, processing and lineage bindings; validation, quality, anomaly, correction and restatement evidence; access, retention, distribution and interoperability projections. External variable, sensor, procedure, feature, statistical unit, source dataset, processing run, release, audit and records masters remain independently authoritative.", "in_scope": [ "Collection and series identity, structure, dimensions, variables, measures, units, observations, order, values, flags, missingness and multi-time semantics", "Vintages, coverage, sampling, transformations, forecasts, provenance, quality, corrections, lifecycle, access, distributions and interoperability projections" ], "out_of_scope": [ "Owning Variable, Classification, Unit, Sensor, Procedure, Feature of Interest, Statistical Unit, Population, Source Dataset, Processing Run, Release, Audit or Records masters", "Treating an observation assertion as timeless ground truth or collapsing observed, estimated, imputed, adjusted, forecast and scenario values", "Autonomous ingestion, imputation, recalculation, revision, suppression, publication, certification, unit change, access widening or physical records disposition" ], "boundary_notes": [ { "neighbor": "WM-MAT-008 parent signal", "distinction": "The unfrozen parent signal may identify a matrix or tabular context, but no approved relation row exists and it grants no ownership, mutation or cascade authority.", "source_refs": [ "SRC-001", "SRC-004", "SRC-010" ] }, { "neighbor": "Series definition, observation collection and observation", "distinction": "The definition fixes meaning and key space, the collection governs membership and versions, and each observation is a separately qualified assertion.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ] }, { "neighbor": "Sensor, procedure, feature, statistical unit, source dataset and processing run", "distinction": "These external masters explain what produced or is described by values; the collection stores non-owning references and lineage only.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-010", "SRC-015" ] }, { "neighbor": "Release, vintage, revision and distribution", "distinction": "Release and availability decisions, knowledge vintages, correction lineage and transport packages are distinct from the semantic collection head.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008", "SRC-013" ] }, { "neighbor": "SDMX, OMS, SSN, RDF Data Cube, OWL-Time, PROV, DQV, DCAT, CSVW, GSIM, RFC 3339, ISO 8601, DataCite, CF and FHIR profiles", "distinction": "Each source has a distinct scope and normative force. Every mapping is version-pinned, profile-qualified and loss-declaring.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ] } ] }, "sources": [ { "id": "SRC-001", "title": "SDMX Technical Specifications", "organization": "SDMX", "url": "https://sdmx.org/standards-2/", "version_or_date": "SDMX 3.1 released May 2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines syntax-neutral statistical structures, series keys, observations, attributes and versioned exchange projections." }, { "id": "SRC-002", "title": "Observations, measurements and samples", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/as/20-082r4/20-082r4.html", "version_or_date": "OGC 20-082r4 version 3.0.0 published 26 May 2023; identical technical content to ISO 19156:2023", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines observation acts, results, procedures, observed properties, features of interest and sampling features." }, { "id": "SRC-003", "title": "Semantic Sensor Network Ontology 2023 Edition", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-ssn-2023/", "version_or_date": "W3C Recommendation 5 December 2024", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines observations, sensors, procedures, properties, features and ObservationCollection semantics including time-series examples." }, { "id": "SRC-004", "title": "The RDF Data Cube Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-data-cube/", "version_or_date": "W3C Recommendation 16 January 2014", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines datasets, observations, dimensions, measures, attributes, slices and integrity constraints for multidimensional data." }, { "id": "SRC-005", "title": "Time Ontology in OWL", "organization": "World Wide Web Consortium and Open Geospatial Consortium", "url": "https://www.w3.org/TR/owl-time/", "version_or_date": "W3C Candidate Recommendation Draft 15 November 2022; OGC 16-071r3", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines instants, intervals, duration, ordering, temporal position, calendars and alternative temporal reference systems." }, { "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-09-06T13:42:00Z", "relevance": "Defines entities, activities, agents, attribution, generation, derivation, revision and qualified provenance." }, { "id": "SRC-007", "title": "Data on the Web Best Practices: Data Quality Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "W3C Working Group Note 15 December 2016", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines quality dimensions, metrics, measurements, annotations, policies and certificates." }, { "id": "SRC-008", "title": "Data Catalog Vocabulary DCAT Version 3", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dcat-3/", "version_or_date": "W3C Recommendation 22 August 2024", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines datasets, distributions, data services, versions, temporal coverage and catalog interoperability." }, { "id": "SRC-009", "title": "Model for Tabular Data and Metadata on the Web", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/tabular-data-model/", "version_or_date": "W3C Recommendation 17 December 2015", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines annotated tables, schemas, datatypes, nulls, foreign keys and metadata needed for CSV projections." }, { "id": "SRC-010", "title": "Generic Statistical Information Model version 2.0 User Guide", "organization": "United Nations Economic Commission for Europe", "url": "https://unece.org/info/publications/pub/400014", "version_or_date": "GSIM 2.0 released December 2023; User Guide November 2024", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines reusable statistical information classes, variables, data structures, datasets and production relationships." }, { "id": "SRC-011", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/info/rfc3339/", "version_or_date": "RFC 3339 July 2002, updated by RFC 9557", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines interoperable Internet timestamps with seconds and explicit relationship to UTC." }, { "id": "SRC-012", "title": "Date and time - Representations for information interchange - Part 1", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/70907.html", "version_or_date": "ISO 8601-1:2019 confirmed 2024; Amendment 1:2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Public metadata grounds machine-readable date, time and UTC-shift representation; restricted text was not inferred." }, { "id": "SRC-013", "title": "DataCite Metadata Schema", "organization": "DataCite", "url": "https://schema.datacite.org/", "version_or_date": "Metadata Schema 4.7 released 3 March 2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines current dataset citation, creator, publisher, version, relation, rights, dates and coverage metadata." }, { "id": "SRC-014", "title": "NetCDF Climate and Forecast Metadata Conventions", "organization": "CF Conventions Committee", "url": "https://cfconventions.org/conventions.html", "version_or_date": "CF 1.13 released December 2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Defines multidimensional scientific variables, coordinates, time units, calendars, bounds, missing values and quality flags." }, { "id": "SRC-015", "title": "Observation - FHIR R5", "organization": "Health Level Seven International", "url": "https://hl7.org/fhir/R5/observation-definitions.html", "version_or_date": "FHIR R5 5.0.0 generated 26 March 2023", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T13:42:00Z", "relevance": "Healthcare profile distinguishes effective time, issued time, status, value, data-absent reason, method, device and derivation." } ], "structure": { "bundles": [ { "id": "series-identity-semantics-and-dimensional-structure", "name": "Series identity, semantics and dimensional structure", "description": "Groups governed collection context for series identity, semantics and dimensional structure.", "rationale": "Make each collection and series definition stable, comparable and independently governed.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-010", "SRC-013", "SRC-014", "SRC-015" ], "layers": [ { "id": "collection-series-identity-version-and-authority", "name": "Collection and series identity, version and authority", "description": "Groups source-qualified time-series context for collection and series identity, version and authority.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-010", "SRC-013" ], "findings": [ { "id": "collection-series-id-version-head-status-owner-and-purpose", "name": "Collection, series ID, version, head, status, owner and purpose", "description": "Records collection, series id, version, head, status, owner and purpose as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-010", "SRC-013" ], "questions": [ { "id": "collection-series-id-version-head-status-owner-and-purpose-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish collection, series id, version, head, status, owner and purpose?", "kind": "identity", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "collection-series-id-version-head-status-owner-and-purpose-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use collection, series id, version, head, status, owner and purpose, for which purpose and under what authority?", "kind": "authority", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "collection-series-id-version-head-status-owner-and-purpose-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify collection, series id, version, head, status, owner and purpose?", "kind": "security", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "collection-series-id-version-head-status-owner-and-purpose-data", "name": "Collection, series ID, version, head, status, owner and purpose data", "description": "Typed time-series data for collection, series id, version, head, status, owner and purpose, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-010", "SRC-013" ] } ], "artifacts": [ { "id": "collection-series-id-version-head-status-owner-and-purpose-record", "name": "Collection, series ID, version, head, status, owner and purpose record", "description": "Immutable or successor-versioned evidence for collection, series id, version, head, status, owner and purpose.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for collection-series-id-version-head-status-owner-and-purpose; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "series-key-boundary-membership-profile-and-compatibility", "name": "Series key, boundary, membership profile and compatibility", "description": "Records series key, boundary, membership profile and compatibility as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-010", "SRC-013" ], "questions": [ { "id": "series-key-boundary-membership-profile-and-compatibility-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish series key, boundary, membership profile and compatibility?", "kind": "constraint", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "series-key-boundary-membership-profile-and-compatibility-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use series key, boundary, membership profile and compatibility, for which purpose and under what authority?", "kind": "requirement", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "series-key-boundary-membership-profile-and-compatibility-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify series key, boundary, membership profile and compatibility?", "kind": "privacy", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "series-key-boundary-membership-profile-and-compatibility-data", "name": "Series key, boundary, membership profile and compatibility data", "description": "Typed time-series data for series key, boundary, membership profile and compatibility, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-010", "SRC-013" ] } ], "artifacts": [ { "id": "series-key-boundary-membership-profile-and-compatibility-record", "name": "Series key, boundary, membership profile and compatibility record", "description": "Immutable or successor-versioned evidence for series key, boundary, membership profile and compatibility.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for series-key-boundary-membership-profile-and-compatibility; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "variable-measure-unit-dimensions-and-classifications", "name": "Variable, measure, unit, dimensions and classifications", "description": "Groups source-qualified time-series context for variable, measure, unit, dimensions and classifications.", "source_refs": [ "SRC-001", "SRC-004", "SRC-010", "SRC-014", "SRC-015" ], "findings": [ { "id": "variable-indicator-observed-property-measure-unit-scale-and-datatype", "name": "Variable, indicator, observed property, measure, unit, scale and datatype", "description": "Records variable, indicator, observed property, measure, unit, scale and datatype as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-010", "SRC-014", "SRC-015" ], "questions": [ { "id": "variable-indicator-observed-property-measure-unit-scale-and-datatype-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish variable, indicator, observed property, measure, unit, scale and datatype?", "kind": "measurement", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "variable-indicator-observed-property-measure-unit-scale-and-datatype-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use variable, indicator, observed property, measure, unit, scale and datatype, for which purpose and under what authority?", "kind": "constraint", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "variable-indicator-observed-property-measure-unit-scale-and-datatype-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify variable, indicator, observed property, measure, unit, scale and datatype?", "kind": "retention", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "variable-indicator-observed-property-measure-unit-scale-and-datatype-data", "name": "Variable, indicator, observed property, measure, unit, scale and datatype data", "description": "Typed time-series data for variable, indicator, observed property, measure, unit, scale and datatype, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-010", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "variable-indicator-observed-property-measure-unit-scale-and-datatype-record", "name": "Variable, indicator, observed property, measure, unit, scale and datatype record", "description": "Immutable or successor-versioned evidence for variable, indicator, observed property, measure, unit, scale and datatype.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for variable-indicator-observed-property-measure-unit-scale-and-datatype; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-010", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "dimension-key-coordinate-classification-code-list-and-concept", "name": "Dimension, key, coordinate, classification, code list and concept", "description": "Records dimension, key, coordinate, classification, code list and concept as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-010", "SRC-014", "SRC-015" ], "questions": [ { "id": "dimension-key-coordinate-classification-code-list-and-concept-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish dimension, key, coordinate, classification, code list and concept?", "kind": "classification", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "dimension-key-coordinate-classification-code-list-and-concept-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use dimension, key, coordinate, classification, code list and concept, for which purpose and under what authority?", "kind": "process", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "dimension-key-coordinate-classification-code-list-and-concept-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify dimension, key, coordinate, classification, code list and concept?", "kind": "access", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "dimension-key-coordinate-classification-code-list-and-concept-data", "name": "Dimension, key, coordinate, classification, code list and concept data", "description": "Typed time-series data for dimension, key, coordinate, classification, code list and concept, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-010", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "dimension-key-coordinate-classification-code-list-and-concept-record", "name": "Dimension, key, coordinate, classification, code list and concept record", "description": "Immutable or successor-versioned evidence for dimension, key, coordinate, classification, code list and concept.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for dimension-key-coordinate-classification-code-list-and-concept; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-010", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "observation-membership-values-and-states", "name": "Observation membership, values and states", "description": "Groups governed collection context for observation membership, values and states.", "rationale": "Represent ordered observations without confusing a value with its meaning or collection.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-014", "SRC-015" ], "layers": [ { "id": "observation-identity-membership-order-and-integrity", "name": "Observation identity, membership, order and integrity", "description": "Groups source-qualified time-series context for observation identity, membership, order and integrity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010" ], "findings": [ { "id": "observation-id-series-membership-dimension-key-and-order", "name": "Observation ID, series membership, dimension key and order", "description": "Records observation id, series membership, dimension key and order as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010" ], "questions": [ { "id": "observation-id-series-membership-dimension-key-and-order-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish observation id, series membership, dimension key and order?", "kind": "composition", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "observation-id-series-membership-dimension-key-and-order-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use observation id, series membership, dimension key and order, for which purpose and under what authority?", "kind": "event", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "observation-id-series-membership-dimension-key-and-order-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify observation id, series membership, dimension key and order?", "kind": "exception", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "observation-id-series-membership-dimension-key-and-order-data", "name": "Observation ID, series membership, dimension key and order data", "description": "Typed time-series data for observation id, series membership, dimension key and order, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010" ] } ], "artifacts": [ { "id": "observation-id-series-membership-dimension-key-and-order-record", "name": "Observation ID, series membership, dimension key and order record", "description": "Immutable or successor-versioned evidence for observation id, series membership, dimension key and order.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for observation-id-series-membership-dimension-key-and-order; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "collection-cardinality-completeness-duplicate-gap-and-overlap", "name": "Collection cardinality, completeness, duplicate, gap and overlap", "description": "Records collection cardinality, completeness, duplicate, gap and overlap as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010" ], "questions": [ { "id": "collection-cardinality-completeness-duplicate-gap-and-overlap-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish collection cardinality, completeness, duplicate, gap and overlap?", "kind": "validation", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "collection-cardinality-completeness-duplicate-gap-and-overlap-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use collection cardinality, completeness, duplicate, gap and overlap, for which purpose and under what authority?", "kind": "measurement", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "collection-cardinality-completeness-duplicate-gap-and-overlap-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify collection cardinality, completeness, duplicate, gap and overlap?", "kind": "interoperability", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "collection-cardinality-completeness-duplicate-gap-and-overlap-data", "name": "Collection cardinality, completeness, duplicate, gap and overlap data", "description": "Typed time-series data for collection cardinality, completeness, duplicate, gap and overlap, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010" ] } ], "artifacts": [ { "id": "collection-cardinality-completeness-duplicate-gap-and-overlap-record", "name": "Collection cardinality, completeness, duplicate, gap and overlap record", "description": "Immutable or successor-versioned evidence for collection cardinality, completeness, duplicate, gap and overlap.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for collection-cardinality-completeness-duplicate-gap-and-overlap; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "result-value-status-flags-and-missingness", "name": "Result value, status, flags and missingness", "description": "Groups source-qualified time-series context for result value, status, flags and missingness.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-014", "SRC-015" ], "findings": [ { "id": "result-value-type-unit-precision-resolution-range-and-component", "name": "Result value, type, unit, precision, resolution, range and component", "description": "Records result value, type, unit, precision, resolution, range and component as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-014", "SRC-015" ], "questions": [ { "id": "result-value-type-unit-precision-resolution-range-and-component-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish result value, type, unit, precision, resolution, range and component?", "kind": "measurement", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "result-value-type-unit-precision-resolution-range-and-component-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use result value, type, unit, precision, resolution, range and component, for which purpose and under what authority?", "kind": "evidence", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "result-value-type-unit-precision-resolution-range-and-component-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify result value, type, unit, precision, resolution, range and component?", "kind": "decision", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "result-value-type-unit-precision-resolution-range-and-component-data", "name": "Result value, type, unit, precision, resolution, range and component data", "description": "Typed time-series data for result value, type, unit, precision, resolution, range and component, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "result-value-type-unit-precision-resolution-range-and-component-record", "name": "Result value, type, unit, precision, resolution, range and component record", "description": "Immutable or successor-versioned evidence for result value, type, unit, precision, resolution, range and component.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for result-value-type-unit-precision-resolution-range-and-component; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "status-flag-missing-not-applicable-suppressed-confidential-and-provisional", "name": "Status, flag, missing, not applicable, suppressed, confidential and provisional", "description": "Records status, flag, missing, not applicable, suppressed, confidential and provisional as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-014", "SRC-015" ], "questions": [ { "id": "status-flag-missing-not-applicable-suppressed-confidential-and-provisional-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish status, flag, missing, not applicable, suppressed, confidential and provisional?", "kind": "state", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "status-flag-missing-not-applicable-suppressed-confidential-and-provisional-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use status, flag, missing, not applicable, suppressed, confidential and provisional, for which purpose and under what authority?", "kind": "quality", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "status-flag-missing-not-applicable-suppressed-confidential-and-provisional-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify status, flag, missing, not applicable, suppressed, confidential and provisional?", "kind": "identity", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "status-flag-missing-not-applicable-suppressed-confidential-and-provisional-data", "name": "Status, flag, missing, not applicable, suppressed, confidential and provisional data", "description": "Typed time-series data for status, flag, missing, not applicable, suppressed, confidential and provisional, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "status-flag-missing-not-applicable-suppressed-confidential-and-provisional-record", "name": "Status, flag, missing, not applicable, suppressed, confidential and provisional record", "description": "Immutable or successor-versioned evidence for status, flag, missing, not applicable, suppressed, confidential and provisional.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for status-flag-missing-not-applicable-suppressed-confidential-and-provisional; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "temporal-semantics-frequency-calendars-and-vintages", "name": "Temporal semantics, frequency, calendars and vintages", "description": "Groups governed collection context for temporal semantics, frequency, calendars and vintages.", "rationale": "Keep real-world, observation, publication and system times distinct.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "layers": [ { "id": "reference-phenomenon-validity-period-and-calendar", "name": "Reference, phenomenon, validity period and calendar", "description": "Groups source-qualified time-series context for reference, phenomenon, validity period and calendar.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "findings": [ { "id": "phenomenon-reference-effective-validity-instant-interval-and-bounds", "name": "Phenomenon, reference, effective, validity, instant, interval and bounds", "description": "Records phenomenon, reference, effective, validity, instant, interval and bounds as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "phenomenon-reference-effective-validity-instant-interval-and-bounds-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish phenomenon, reference, effective, validity, instant, interval and bounds?", "kind": "temporal", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "phenomenon-reference-effective-validity-instant-interval-and-bounds-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use phenomenon, reference, effective, validity, instant, interval and bounds, for which purpose and under what authority?", "kind": "validation", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "phenomenon-reference-effective-validity-instant-interval-and-bounds-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify phenomenon, reference, effective, validity, instant, interval and bounds?", "kind": "classification", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "phenomenon-reference-effective-validity-instant-interval-and-bounds-data", "name": "Phenomenon, reference, effective, validity, instant, interval and bounds data", "description": "Typed time-series data for phenomenon, reference, effective, validity, instant, interval and bounds, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "phenomenon-reference-effective-validity-instant-interval-and-bounds-record", "name": "Phenomenon, reference, effective, validity, instant, interval and bounds record", "description": "Immutable or successor-versioned evidence for phenomenon, reference, effective, validity, instant, interval and bounds.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for phenomenon-reference-effective-validity-instant-interval-and-bounds; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "frequency-periodicity-cadence-calendar-time-zone-offset-and-precision", "name": "Frequency, periodicity, cadence, calendar, time zone, offset and precision", "description": "Records frequency, periodicity, cadence, calendar, time zone, offset and precision as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "frequency-periodicity-cadence-calendar-time-zone-offset-and-precision-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish frequency, periodicity, cadence, calendar, time zone, offset and precision?", "kind": "temporal", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "frequency-periodicity-cadence-calendar-time-zone-offset-and-precision-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use frequency, periodicity, cadence, calendar, time zone, offset and precision, for which purpose and under what authority?", "kind": "security", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "frequency-periodicity-cadence-calendar-time-zone-offset-and-precision-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify frequency, periodicity, cadence, calendar, time zone, offset and precision?", "kind": "composition", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "frequency-periodicity-cadence-calendar-time-zone-offset-and-precision-data", "name": "Frequency, periodicity, cadence, calendar, time zone, offset and precision data", "description": "Typed time-series data for frequency, periodicity, cadence, calendar, time zone, offset and precision, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "frequency-periodicity-cadence-calendar-time-zone-offset-and-precision-record", "name": "Frequency, periodicity, cadence, calendar, time zone, offset and precision record", "description": "Immutable or successor-versioned evidence for frequency, periodicity, cadence, calendar, time zone, offset and precision.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for frequency-periodicity-cadence-calendar-time-zone-offset-and-precision; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "result-availability-release-revision-vintage-and-knowledge-time", "name": "Result, availability, release, revision, vintage and knowledge time", "description": "Groups source-qualified time-series context for result, availability, release, revision, vintage and knowledge time.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008", "SRC-011", "SRC-012", "SRC-015" ], "findings": [ { "id": "result-issued-available-release-embargo-and-publication-time", "name": "Result, issued, available, release, embargo and publication time", "description": "Records result, issued, available, release, embargo and publication time as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008", "SRC-011", "SRC-012", "SRC-015" ], "questions": [ { "id": "result-issued-available-release-embargo-and-publication-time-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish result, issued, available, release, embargo and publication time?", "kind": "temporal", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "result-issued-available-release-embargo-and-publication-time-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use result, issued, available, release, embargo and publication time, for which purpose and under what authority?", "kind": "privacy", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "result-issued-available-release-embargo-and-publication-time-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify result, issued, available, release, embargo and publication time?", "kind": "relationship", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "result-issued-available-release-embargo-and-publication-time-data", "name": "Result, issued, available, release, embargo and publication time data", "description": "Typed time-series data for result, issued, available, release, embargo and publication time, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008", "SRC-011", "SRC-012", "SRC-015" ] } ], "artifacts": [ { "id": "result-issued-available-release-embargo-and-publication-time-record", "name": "Result, issued, available, release, embargo and publication time record", "description": "Immutable or successor-versioned evidence for result, issued, available, release, embargo and publication time.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for result-issued-available-release-embargo-and-publication-time; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008", "SRC-011", "SRC-012", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "revision-vintage-recorded-ingestion-transaction-and-knowledge-time", "name": "Revision, vintage, recorded, ingestion, transaction and knowledge time", "description": "Records revision, vintage, recorded, ingestion, transaction and knowledge time as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008", "SRC-011", "SRC-012", "SRC-015" ], "questions": [ { "id": "revision-vintage-recorded-ingestion-transaction-and-knowledge-time-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish revision, vintage, recorded, ingestion, transaction and knowledge time?", "kind": "provenance", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "revision-vintage-recorded-ingestion-transaction-and-knowledge-time-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use revision, vintage, recorded, ingestion, transaction and knowledge time, for which purpose and under what authority?", "kind": "retention", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "revision-vintage-recorded-ingestion-transaction-and-knowledge-time-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify revision, vintage, recorded, ingestion, transaction and knowledge time?", "kind": "state", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "revision-vintage-recorded-ingestion-transaction-and-knowledge-time-data", "name": "Revision, vintage, recorded, ingestion, transaction and knowledge time data", "description": "Typed time-series data for revision, vintage, recorded, ingestion, transaction and knowledge time, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008", "SRC-011", "SRC-012", "SRC-015" ] } ], "artifacts": [ { "id": "revision-vintage-recorded-ingestion-transaction-and-knowledge-time-record", "name": "Revision, vintage, recorded, ingestion, transaction and knowledge time record", "description": "Immutable or successor-versioned evidence for revision, vintage, recorded, ingestion, transaction and knowledge time.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for revision-vintage-recorded-ingestion-transaction-and-knowledge-time; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008", "SRC-011", "SRC-012", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "coverage-sampling-transformations-and-forecast-qualifiers", "name": "Coverage, sampling, transformations and forecast qualifiers", "description": "Groups governed collection context for coverage, sampling, transformations and forecast qualifiers.", "rationale": "Describe what a sequence covers and how values were formed or projected.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-013", "SRC-014" ], "layers": [ { "id": "feature-population-space-sample-and-granularity", "name": "Feature, population, space, sample and granularity", "description": "Groups source-qualified time-series context for feature, population, space, sample and granularity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010", "SRC-013", "SRC-014" ], "findings": [ { "id": "feature-of-interest-population-domain-spatial-and-thematic-coverage", "name": "Feature of interest, population, domain, spatial and thematic coverage", "description": "Records feature of interest, population, domain, spatial and thematic coverage as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010", "SRC-013", "SRC-014" ], "questions": [ { "id": "feature-of-interest-population-domain-spatial-and-thematic-coverage-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish feature of interest, population, domain, spatial and thematic coverage?", "kind": "relationship", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "feature-of-interest-population-domain-spatial-and-thematic-coverage-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use feature of interest, population, domain, spatial and thematic coverage, for which purpose and under what authority?", "kind": "access", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "feature-of-interest-population-domain-spatial-and-thematic-coverage-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify feature of interest, population, domain, spatial and thematic coverage?", "kind": "lifecycle", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "feature-of-interest-population-domain-spatial-and-thematic-coverage-data", "name": "Feature of interest, population, domain, spatial and thematic coverage data", "description": "Typed time-series data for feature of interest, population, domain, spatial and thematic coverage, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "feature-of-interest-population-domain-spatial-and-thematic-coverage-record", "name": "Feature of interest, population, domain, spatial and thematic coverage record", "description": "Immutable or successor-versioned evidence for feature of interest, population, domain, spatial and thematic coverage.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for feature-of-interest-population-domain-spatial-and-thematic-coverage; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "sample-frame-specimen-sampling-method-cadence-granularity-and-weight", "name": "Sample frame, specimen, sampling method, cadence, granularity and weight", "description": "Records sample frame, specimen, sampling method, cadence, granularity and weight as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010", "SRC-013", "SRC-014" ], "questions": [ { "id": "sample-frame-specimen-sampling-method-cadence-granularity-and-weight-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish sample frame, specimen, sampling method, cadence, granularity and weight?", "kind": "measurement", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "sample-frame-specimen-sampling-method-cadence-granularity-and-weight-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use sample frame, specimen, sampling method, cadence, granularity and weight, for which purpose and under what authority?", "kind": "exception", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "sample-frame-specimen-sampling-method-cadence-granularity-and-weight-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify sample frame, specimen, sampling method, cadence, granularity and weight?", "kind": "temporal", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "sample-frame-specimen-sampling-method-cadence-granularity-and-weight-data", "name": "Sample frame, specimen, sampling method, cadence, granularity and weight data", "description": "Typed time-series data for sample frame, specimen, sampling method, cadence, granularity and weight, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "sample-frame-specimen-sampling-method-cadence-granularity-and-weight-record", "name": "Sample frame, specimen, sampling method, cadence, granularity and weight record", "description": "Immutable or successor-versioned evidence for sample frame, specimen, sampling method, cadence, granularity and weight.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for sample-frame-specimen-sampling-method-cadence-granularity-and-weight; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "aggregation-transformation-adjustment-forecast-and-scenario", "name": "Aggregation, transformation, adjustment, forecast and scenario", "description": "Groups source-qualified time-series context for aggregation, transformation, adjustment, forecast and scenario.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ], "findings": [ { "id": "aggregation-weighting-index-base-normalization-seasonal-adjustment-and-chain", "name": "Aggregation, weighting, index base, normalization, seasonal adjustment and chain", "description": "Records aggregation, weighting, index base, normalization, seasonal adjustment and chain as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ], "questions": [ { "id": "aggregation-weighting-index-base-normalization-seasonal-adjustment-and-chain-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish aggregation, weighting, index base, normalization, seasonal adjustment and chain?", "kind": "process", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "aggregation-weighting-index-base-normalization-seasonal-adjustment-and-chain-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use aggregation, weighting, index base, normalization, seasonal adjustment and chain, for which purpose and under what authority?", "kind": "interoperability", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "aggregation-weighting-index-base-normalization-seasonal-adjustment-and-chain-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify aggregation, weighting, index base, normalization, seasonal adjustment and chain?", "kind": "provenance", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "aggregation-weighting-index-base-normalization-seasonal-adjustment-and-chain-data", "name": "Aggregation, weighting, index base, normalization, seasonal adjustment and chain data", "description": "Typed time-series data for aggregation, weighting, index base, normalization, seasonal adjustment and chain, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "aggregation-weighting-index-base-normalization-seasonal-adjustment-and-chain-record", "name": "Aggregation, weighting, index base, normalization, seasonal adjustment and chain record", "description": "Immutable or successor-versioned evidence for aggregation, weighting, index base, normalization, seasonal adjustment and chain.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for aggregation-weighting-index-base-normalization-seasonal-adjustment-and-chain; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "observed-estimated-nowcast-forecast-scenario-horizon-quantile-and-confidence", "name": "Observed, estimated, nowcast, forecast, scenario, horizon, quantile and confidence", "description": "Records observed, estimated, nowcast, forecast, scenario, horizon, quantile and confidence as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ], "questions": [ { "id": "observed-estimated-nowcast-forecast-scenario-horizon-quantile-and-confidence-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish observed, estimated, nowcast, forecast, scenario, horizon, quantile and confidence?", "kind": "classification", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "observed-estimated-nowcast-forecast-scenario-horizon-quantile-and-confidence-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use observed, estimated, nowcast, forecast, scenario, horizon, quantile and confidence, for which purpose and under what authority?", "kind": "decision", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "observed-estimated-nowcast-forecast-scenario-horizon-quantile-and-confidence-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify observed, estimated, nowcast, forecast, scenario, horizon, quantile and confidence?", "kind": "ownership", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "observed-estimated-nowcast-forecast-scenario-horizon-quantile-and-confidence-data", "name": "Observed, estimated, nowcast, forecast, scenario, horizon, quantile and confidence data", "description": "Typed time-series data for observed, estimated, nowcast, forecast, scenario, horizon, quantile and confidence, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "observed-estimated-nowcast-forecast-scenario-horizon-quantile-and-confidence-record", "name": "Observed, estimated, nowcast, forecast, scenario, horizon, quantile and confidence record", "description": "Immutable or successor-versioned evidence for observed, estimated, nowcast, forecast, scenario, horizon, quantile and confidence.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for observed-estimated-nowcast-forecast-scenario-horizon-quantile-and-confidence; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "source-provenance-quality-and-revision", "name": "Source, provenance, quality and revision", "description": "Groups governed collection context for source, provenance, quality and revision.", "rationale": "Make every value traceable and every quality or correction claim evidence-qualified.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-010", "SRC-014", "SRC-015" ], "layers": [ { "id": "source-procedure-sensor-run-and-lineage", "name": "Source, procedure, sensor, run and lineage", "description": "Groups source-qualified time-series context for source, procedure, sensor, run and lineage.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010", "SRC-014", "SRC-015" ], "findings": [ { "id": "source-dataset-api-sensor-device-procedure-method-and-feature-binding", "name": "Source dataset, API, sensor, device, procedure, method and feature binding", "description": "Records source dataset, api, sensor, device, procedure, method and feature binding as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010", "SRC-014", "SRC-015" ], "questions": [ { "id": "source-dataset-api-sensor-device-procedure-method-and-feature-binding-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish source dataset, api, sensor, device, procedure, method and feature binding?", "kind": "provenance", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "source-dataset-api-sensor-device-procedure-method-and-feature-binding-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use source dataset, api, sensor, device, procedure, method and feature binding, for which purpose and under what authority?", "kind": "identity", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "source-dataset-api-sensor-device-procedure-method-and-feature-binding-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify source dataset, api, sensor, device, procedure, method and feature binding?", "kind": "authority", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "source-dataset-api-sensor-device-procedure-method-and-feature-binding-data", "name": "Source dataset, API, sensor, device, procedure, method and feature binding data", "description": "Typed time-series data for source dataset, api, sensor, device, procedure, method and feature binding, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "source-dataset-api-sensor-device-procedure-method-and-feature-binding-record", "name": "Source dataset, API, sensor, device, procedure, method and feature binding record", "description": "Immutable or successor-versioned evidence for source dataset, api, sensor, device, procedure, method and feature binding.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for source-dataset-api-sensor-device-procedure-method-and-feature-binding; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "collection-processing-run-software-operator-input-output-and-lineage", "name": "Collection, processing run, software, operator, input, output and lineage", "description": "Records collection, processing run, software, operator, input, output and lineage as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010", "SRC-014", "SRC-015" ], "questions": [ { "id": "collection-processing-run-software-operator-input-output-and-lineage-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish collection, processing run, software, operator, input, output and lineage?", "kind": "provenance", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "collection-processing-run-software-operator-input-output-and-lineage-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use collection, processing run, software, operator, input, output and lineage, for which purpose and under what authority?", "kind": "classification", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "collection-processing-run-software-operator-input-output-and-lineage-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify collection, processing run, software, operator, input, output and lineage?", "kind": "requirement", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "collection-processing-run-software-operator-input-output-and-lineage-data", "name": "Collection, processing run, software, operator, input, output and lineage data", "description": "Typed time-series data for collection, processing run, software, operator, input, output and lineage, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "collection-processing-run-software-operator-input-output-and-lineage-record", "name": "Collection, processing run, software, operator, input, output and lineage record", "description": "Immutable or successor-versioned evidence for collection, processing run, software, operator, input, output and lineage.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for collection-processing-run-software-operator-input-output-and-lineage; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "validation-quality-uncertainty-anomaly-and-correction", "name": "Validation, quality, uncertainty, anomaly and correction", "description": "Groups source-qualified time-series context for validation, quality, uncertainty, anomaly and correction.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-010", "SRC-014", "SRC-015" ], "findings": [ { "id": "validation-rule-quality-dimension-metric-uncertainty-confidence-anomaly-and-outlier", "name": "Validation rule, quality dimension, metric, uncertainty, confidence, anomaly and outlier", "description": "Records validation rule, quality dimension, metric, uncertainty, confidence, anomaly and outlier as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-010", "SRC-014", "SRC-015" ], "questions": [ { "id": "validation-rule-quality-dimension-metric-uncertainty-confidence-anomaly-and-outlier-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish validation rule, quality dimension, metric, uncertainty, confidence, anomaly and outlier?", "kind": "quality", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "validation-rule-quality-dimension-metric-uncertainty-confidence-anomaly-and-outlier-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use validation rule, quality dimension, metric, uncertainty, confidence, anomaly and outlier, for which purpose and under what authority?", "kind": "composition", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "validation-rule-quality-dimension-metric-uncertainty-confidence-anomaly-and-outlier-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify validation rule, quality dimension, metric, uncertainty, confidence, anomaly and outlier?", "kind": "constraint", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "validation-rule-quality-dimension-metric-uncertainty-confidence-anomaly-and-outlier-data", "name": "Validation rule, quality dimension, metric, uncertainty, confidence, anomaly and outlier data", "description": "Typed time-series data for validation rule, quality dimension, metric, uncertainty, confidence, anomaly and outlier, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-010", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "validation-rule-quality-dimension-metric-uncertainty-confidence-anomaly-and-outlier-record", "name": "Validation rule, quality dimension, metric, uncertainty, confidence, anomaly and outlier record", "description": "Immutable or successor-versioned evidence for validation rule, quality dimension, metric, uncertainty, confidence, anomaly and outlier.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for validation-rule-quality-dimension-metric-uncertainty-confidence-anomaly-and-outlier; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-010", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "revision-correction-benchmark-restatement-backcast-retraction-and-supersession", "name": "Revision, correction, benchmark, restatement, backcast, retraction and supersession", "description": "Records revision, correction, benchmark, restatement, backcast, retraction and supersession as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-010", "SRC-014", "SRC-015" ], "questions": [ { "id": "revision-correction-benchmark-restatement-backcast-retraction-and-supersession-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish revision, correction, benchmark, restatement, backcast, retraction and supersession?", "kind": "lifecycle", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "revision-correction-benchmark-restatement-backcast-retraction-and-supersession-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use revision, correction, benchmark, restatement, backcast, retraction and supersession, for which purpose and under what authority?", "kind": "relationship", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "revision-correction-benchmark-restatement-backcast-retraction-and-supersession-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify revision, correction, benchmark, restatement, backcast, retraction and supersession?", "kind": "process", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "revision-correction-benchmark-restatement-backcast-retraction-and-supersession-data", "name": "Revision, correction, benchmark, restatement, backcast, retraction and supersession data", "description": "Typed time-series data for revision, correction, benchmark, restatement, backcast, retraction and supersession, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-010", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "revision-correction-benchmark-restatement-backcast-retraction-and-supersession-record", "name": "Revision, correction, benchmark, restatement, backcast, retraction and supersession record", "description": "Immutable or successor-versioned evidence for revision, correction, benchmark, restatement, backcast, retraction and supersession.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for revision-correction-benchmark-restatement-backcast-retraction-and-supersession; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-010", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-access-distribution-and-interoperability", "name": "Lifecycle, access, distribution and interoperability", "description": "Groups governed collection context for lifecycle, access, distribution and interoperability.", "rationale": "Publish usable projections while preserving governance, history and semantic loss.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ], "layers": [ { "id": "lifecycle-release-access-rights-and-records", "name": "Lifecycle, release, access, rights and records", "description": "Groups source-qualified time-series context for lifecycle, release, access, rights and records.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-013" ], "findings": [ { "id": "draft-validated-released-superseded-withdrawn-and-data-availability", "name": "Draft, validated, released, superseded, withdrawn and data availability", "description": "Records draft, validated, released, superseded, withdrawn and data availability as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-013" ], "questions": [ { "id": "draft-validated-released-superseded-withdrawn-and-data-availability-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish draft, validated, released, superseded, withdrawn and data availability?", "kind": "lifecycle", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "draft-validated-released-superseded-withdrawn-and-data-availability-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use draft, validated, released, superseded, withdrawn and data availability, for which purpose and under what authority?", "kind": "state", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "draft-validated-released-superseded-withdrawn-and-data-availability-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify draft, validated, released, superseded, withdrawn and data availability?", "kind": "event", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "draft-validated-released-superseded-withdrawn-and-data-availability-data", "name": "Draft, validated, released, superseded, withdrawn and data availability data", "description": "Typed time-series data for draft, validated, released, superseded, withdrawn and data availability, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-013" ] } ], "artifacts": [ { "id": "draft-validated-released-superseded-withdrawn-and-data-availability-record", "name": "Draft, validated, released, superseded, withdrawn and data availability record", "description": "Immutable or successor-versioned evidence for draft, validated, released, superseded, withdrawn and data availability.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for draft-validated-released-superseded-withdrawn-and-data-availability; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "access-privacy-license-embargo-retention-legal-hold-tombstone-and-audit", "name": "Access, privacy, license, embargo, retention, legal hold, tombstone and audit", "description": "Records access, privacy, license, embargo, retention, legal hold, tombstone and audit as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-013" ], "questions": [ { "id": "access-privacy-license-embargo-retention-legal-hold-tombstone-and-audit-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish access, privacy, license, embargo, retention, legal hold, tombstone and audit?", "kind": "access", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "access-privacy-license-embargo-retention-legal-hold-tombstone-and-audit-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use access, privacy, license, embargo, retention, legal hold, tombstone and audit, for which purpose and under what authority?", "kind": "lifecycle", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "access-privacy-license-embargo-retention-legal-hold-tombstone-and-audit-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify access, privacy, license, embargo, retention, legal hold, tombstone and audit?", "kind": "measurement", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "access-privacy-license-embargo-retention-legal-hold-tombstone-and-audit-data", "name": "Access, privacy, license, embargo, retention, legal hold, tombstone and audit data", "description": "Typed time-series data for access, privacy, license, embargo, retention, legal hold, tombstone and audit, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-013" ] } ], "artifacts": [ { "id": "access-privacy-license-embargo-retention-legal-hold-tombstone-and-audit-record", "name": "Access, privacy, license, embargo, retention, legal hold, tombstone and audit record", "description": "Immutable or successor-versioned evidence for access, privacy, license, embargo, retention, legal hold, tombstone and audit.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for access-privacy-license-embargo-retention-legal-hold-tombstone-and-audit; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "distribution-api-packaging-integrity-and-projections", "name": "Distribution, API, packaging, integrity and projections", "description": "Groups source-qualified time-series context for distribution, api, packaging, integrity and projections.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ], "findings": [ { "id": "distribution-format-media-type-api-query-pagination-chunk-compression-and-checksum", "name": "Distribution, format, media type, API, query, pagination, chunk, compression and checksum", "description": "Records distribution, format, media type, api, query, pagination, chunk, compression and checksum as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ], "questions": [ { "id": "distribution-format-media-type-api-query-pagination-chunk-compression-and-checksum-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish distribution, format, media type, api, query, pagination, chunk, compression and checksum?", "kind": "interoperability", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "distribution-format-media-type-api-query-pagination-chunk-compression-and-checksum-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use distribution, format, media type, api, query, pagination, chunk, compression and checksum, for which purpose and under what authority?", "kind": "temporal", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "distribution-format-media-type-api-query-pagination-chunk-compression-and-checksum-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify distribution, format, media type, api, query, pagination, chunk, compression and checksum?", "kind": "evidence", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "distribution-format-media-type-api-query-pagination-chunk-compression-and-checksum-data", "name": "Distribution, format, media type, API, query, pagination, chunk, compression and checksum data", "description": "Typed time-series data for distribution, format, media type, api, query, pagination, chunk, compression and checksum, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "distribution-format-media-type-api-query-pagination-chunk-compression-and-checksum-record", "name": "Distribution, format, media type, API, query, pagination, chunk, compression and checksum record", "description": "Immutable or successor-versioned evidence for distribution, format, media type, api, query, pagination, chunk, compression and checksum.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for distribution-format-media-type-api-query-pagination-chunk-compression-and-checksum; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "sdmx-oms-ssn-data-cube-time-prov-dqv-dcat-csvw-gsim-rfc-iso-datacite-cf-and-fhir-projection", "name": "SDMX, OMS, SSN, Data Cube, Time, PROV, DQV, DCAT, CSVW, GSIM, RFC, ISO, DataCite, CF and FHIR projection", "description": "Records sdmx, oms, ssn, data cube, time, prov, dqv, dcat, csvw, gsim, rfc, iso, datacite, cf and fhir projection as source-qualified collection context while observation, sensor, procedure, feature, statistical unit, source dataset, processing run, release and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ], "questions": [ { "id": "sdmx-oms-ssn-data-cube-time-prov-dqv-dcat-csvw-gsim-rfc-iso-datacite-cf-and-fhir-projection-q01", "text": "What stable identity, version, typed value, dimensions, unit, scope and explicit unknown establish sdmx, oms, ssn, data cube, time, prov, dqv, dcat, csvw, gsim, rfc, iso, datacite, cf and fhir projection?", "kind": "interoperability", "answer_data": [ "collection, series, observation, dimension and external master identifiers", "typed value, unit, scale, vocabulary, schema, profile and algorithm version", "unknown, missing, suppressed, provisional, disputed and not-applicable states" ] }, { "id": "sdmx-oms-ssn-data-cube-time-prov-dqv-dcat-csvw-gsim-rfc-iso-datacite-cf-and-fhir-projection-q02", "text": "Who owns, observes, supplies, transforms, asserts, reviews, approves or may use sdmx, oms, ssn, data cube, time, prov, dqv, dcat, csvw, gsim, rfc, iso, datacite, cf and fhir projection, for which purpose and under what authority?", "kind": "provenance", "answer_data": [ "actor, agent, role, organization, sensor, software and contact", "purpose, authority, policy, access, license, confidentiality and retention", "conflict, exception, escalation and accountability" ] }, { "id": "sdmx-oms-ssn-data-cube-time-prov-dqv-dcat-csvw-gsim-rfc-iso-datacite-cf-and-fhir-projection-q03", "text": "Which phenomenon, reference, result, availability, release, revision, recorded, ingestion and knowledge times, evidence and uncertainty qualify sdmx, oms, ssn, data cube, time, prov, dqv, dcat, csvw, gsim, rfc, iso, datacite, cf and fhir projection?", "kind": "quality", "answer_data": [ "distinct real-world, observation, publication, revision and system times", "source, procedure, method, run, lineage, metric, confidence and limitation", "successor, correction, supersession, legal hold and audit" ] } ], "data_elements": [ { "id": "sdmx-oms-ssn-data-cube-time-prov-dqv-dcat-csvw-gsim-rfc-iso-datacite-cf-and-fhir-projection-data", "name": "SDMX, OMS, SSN, Data Cube, Time, PROV, DQV, DCAT, CSVW, GSIM, RFC, ISO, DataCite, CF and FHIR projection data", "description": "Typed time-series data for sdmx, oms, ssn, data cube, time, prov, dqv, dcat, csvw, gsim, rfc, iso, datacite, cf and fhir projection, qualified by series key, version, time, unit, authority, uncertainty and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "sdmx-oms-ssn-data-cube-time-prov-dqv-dcat-csvw-gsim-rfc-iso-datacite-cf-and-fhir-projection-record", "name": "SDMX, OMS, SSN, Data Cube, Time, PROV, DQV, DCAT, CSVW, GSIM, RFC, ISO, DataCite, CF and FHIR projection record", "description": "Immutable or successor-versioned evidence for sdmx, oms, ssn, data cube, time, prov, dqv, dcat, csvw, gsim, rfc, iso, datacite, cf and fhir projection.", "media_or_form": [ "logical time-series specification assertion", "definition, observation, value, flag, method, quality, correction, release or projection record" ], "serial": true, "identity_strategy": "Series ID plus independent series version, observation ID or dimension-key and phenomenon time, then revision or vintage ID and artifact kind for sdmx-oms-ssn-data-cube-time-prov-dqv-dcat-csvw-gsim-rfc-iso-datacite-cf-and-fhir-projection; a timestamp, row number, label or digest never identifies an observation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-series", "name": "Register a time series or observation collection", "description": "Governed operation to register a time series or observation collection without autonomous ingestion, imputation, recalculation, revision, suppression, release, certification, unit change, access widening or records disposition.", "inputs": [ "owner", "purpose", "series definition and initial scope" ], "outputs": [ "stable collection and series version head" ], "preconditions": [ "namespace, identity, authority, purpose, variable, unit and duplicate checks pass" ], "effects": [ "a versioned collection exists without creating observations" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010" ] }, { "id": "define-series-structure", "name": "Define series dimensions, measures and keys", "description": "Governed operation to define series dimensions, measures and keys without autonomous ingestion, imputation, recalculation, revision, suppression, release, certification, unit change, access widening or records disposition.", "inputs": [ "series version", "variables", "dimensions and code lists" ], "outputs": [ "versioned series structure" ], "preconditions": [ "measure, unit, dimension, classification, key uniqueness and profile checks pass" ], "effects": [ "permitted observation coordinates become explicit" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-010", "SRC-014" ] }, { "id": "append-observation", "name": "Append or bind an observation", "description": "Governed operation to append or bind an observation without autonomous ingestion, imputation, recalculation, revision, suppression, release, certification, unit change, access widening or records disposition.", "inputs": [ "series head", "observation assertion", "source authority" ], "outputs": [ "successor membership assertion" ], "preconditions": [ "identity, dimension key, value, unit, time, status, source and expected revision checks pass" ], "effects": [ "the observation becomes a qualified member without rewriting history" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-015" ] }, { "id": "validate-order-gaps-and-duplicates", "name": "Validate order, gaps, overlaps and duplicates", "description": "Governed operation to validate order, gaps, overlaps and duplicates without autonomous ingestion, imputation, recalculation, revision, suppression, release, certification, unit change, access widening or records disposition.", "inputs": [ "collection version", "frequency and calendar", "validation rules" ], "outputs": [ "validation and exception evidence" ], "preconditions": [ "time, key, cadence, boundary, missing-state and rule-version checks pass" ], "effects": [ "issues are asserted without imputing or deleting values" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-014" ] }, { "id": "qualify-time-and-vintage", "name": "Qualify temporal semantics and vintage", "description": "Governed operation to qualify temporal semantics and vintage without autonomous ingestion, imputation, recalculation, revision, suppression, release, certification, unit change, access widening or records disposition.", "inputs": [ "observation or series", "temporal assertion", "clock and calendar profile" ], "outputs": [ "multi-time and vintage binding" ], "preconditions": [ "phenomenon, result, release, revision, recorded, ingestion and knowledge times are disambiguated" ], "effects": [ "later knowledge does not overwrite earlier vintages" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] }, { "id": "record-transformation", "name": "Record aggregation, adjustment or derivation", "description": "Governed operation to record aggregation, adjustment or derivation without autonomous ingestion, imputation, recalculation, revision, suppression, release, certification, unit change, access widening or records disposition.", "inputs": [ "input observations", "method and parameters", "processing run" ], "outputs": [ "derived series or observations with lineage" ], "preconditions": [ "algorithm, version, unit, weighting, base, calendar, input, output and uncertainty checks pass" ], "effects": [ "derived values remain separate from source observations" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ] }, { "id": "record-forecast-or-scenario", "name": "Record forecast, nowcast or scenario values", "description": "Governed operation to record forecast, nowcast or scenario values without autonomous ingestion, imputation, recalculation, revision, suppression, release, certification, unit change, access widening or records disposition.", "inputs": [ "series definition", "model run", "scenario and horizon" ], "outputs": [ "qualified projected observation collection" ], "preconditions": [ "estimate class, cutoff, horizon, scenario, quantile, confidence, run and source checks pass" ], "effects": [ "projected values cannot masquerade as observed facts" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-010" ] }, { "id": "assess-quality-and-correct", "name": "Assess quality and issue a correction", "description": "Governed operation to assess quality and issue a correction without autonomous ingestion, imputation, recalculation, revision, suppression, release, certification, unit change, access widening or records disposition.", "inputs": [ "collection version", "quality evidence", "authorized correction decision" ], "outputs": [ "quality assertion and successor correction" ], "preconditions": [ "metric, method, scope, confidence, reason, authority, revision and audit checks pass" ], "effects": [ "issued observations remain immutable and successors are linked" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-010", "SRC-015" ] }, { "id": "release-supersede-or-withdraw", "name": "Release, supersede or withdraw a collection", "description": "Governed operation to release, supersede or withdraw a collection without autonomous ingestion, imputation, recalculation, revision, suppression, release, certification, unit change, access widening or records disposition.", "inputs": [ "collection head", "review evidence", "authorized lifecycle decision" ], "outputs": [ "successor lifecycle and availability assertion" ], "preconditions": [ "expected revision, approval, rights, access, embargo, effective time and retention checks pass" ], "effects": [ "data lifecycle stays distinct from distribution availability" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-008", "SRC-013" ] }, { "id": "query-project-retain-and-audit", "name": "Query, project, retain and audit", "description": "Governed operation to query, project, retain and audit without autonomous ingestion, imputation, recalculation, revision, suppression, release, certification, unit change, access widening or records disposition.", "inputs": [ "collection", "target profile", "purpose-bound access and records policy" ], "outputs": [ "filtered projection, retention result or audit event" ], "preconditions": [ "purpose, authority, mapping, loss, confidentiality, hold, checksum and retention checks pass" ], "effects": [ "protected values stay governed and projections declare loss" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ] } ], "composition": [ { "target": "WM-MAT-008", "relation": "REFERENCE", "purpose": "Represent the unfrozen matrix or tabular context without approved ownership, mutation or cascade authority.", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-010" ] }, { "target": "Variable, Classification, Code List and Unit models", "relation": "REFERENCE", "purpose": "Resolve independently governed observation meaning, dimensions and units.", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-010", "SRC-014", "SRC-015" ] }, { "target": "Observation, Sensor, Procedure, Feature, Statistical Unit, Population and Source Dataset models", "relation": "REFERENCE", "purpose": "Resolve authoritative observations, producers, subjects, populations and sources without absorbing their lifecycles.", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-010", "SRC-015" ] }, { "target": "Processing Run, Release, Audit and Records models", "relation": "REFERENCE", "purpose": "Resolve derivation, operational publication, audit and disposition authorities.", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-008", "SRC-010", "SRC-013" ] }, { "target": "SDMX 3.1, OMS 3.0, SSN 2023, RDF Data Cube, OWL-Time, PROV-O, DQV, DCAT 3, CSVW, GSIM 2.0, RFC 3339, ISO 8601-1:2019, DataCite 4.7, CF 1.13 and FHIR R5", "relation": "ALIGN", "purpose": "Project version-pinned statistical, observation, sensor, linked-data, temporal, provenance, quality, catalog, tabular, citation, scientific and health views with declared loss.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension owner, namespace authority, data governance mandate and accountable series owner", "Authoritative Series, Observation, Variable, Classification, Unit, Sensor, Procedure, Feature, Population, Source Dataset, Processing Run, Release, Audit and Records registries", "Approved terminology, units, calendars, quality, privacy, access, retention and interoperability profiles", "Role, delegation, validation, correction, publication, withdrawal and agent-operation policies" ], "namespace_guidance": "Mint collection, series, series-version, observation, dimension-key, vintage, processing-run, quality, correction, release, distribution and projection IDs; preserve every external master identifier.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize a series by authoritative series identifier, owner namespace, versioned structure and series key, never by title, URL, timestamp or file digest alone.", "Keep collection, series definition, observation, variable, sensor, procedure, feature, source dataset, processing run, release, vintage and distribution independently identifiable." ], "patch_rules": [ "Extensions declare dimension, measure, unit, time, value, quality, provenance, privacy, lifecycle and interoperability effects.", "Released series and observations are immutable; changes create linked successors or explicit new vintages with reason, compatibility, migration and review.", "Never silently change a series key, dimension, classification, measure, unit, calendar, frequency, value, flag, missing state, source, method or time semantics." ], "compatibility_rules": [ "Ignore additive fields only when identity, dimensions, measure, unit, time, value, status, authority, privacy and provenance survive.", "Every projection pins standard, schema, vocabulary, calendar, unit and mapping versions and declares information loss." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier for each collection, series, observation, run, vintage, release, distribution or artifact, qualified by issuer, namespace and record kind.", "Governed globally resolvable series or observation IRI.", "Dimension UUID or ULID when neither preceding identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; distinguish phenomenon, reference, validity, result, availability, release, revision, recorded, ingestion, transaction and knowledge times whenever they differ.", "serial_naming_rule": "Use {series-id}--{series-version}--{observation-id-or-dimension-key}--{vintage-or-revision-id}--{artifact-kind}.", "integrity_rule": "Store digest, media type, record kind, series and coverage scope, schema and profile versions, actor or process, distinct event and knowledge times, confidentiality marking and provenance." }, "policies": [ "The collection owns series definitions, observation membership, qualified values, versions and projections but not external variable, sensor, procedure, feature, statistical unit, source dataset, processing run, release, audit or records masters.", "An observation value is an assertion qualified by property, unit, time, method, source, quality, uncertainty, status and provenance; it is not timeless ground truth.", "Observed, estimated, imputed, adjusted, nowcast, forecast and scenario values must remain distinguishable.", "Agents cannot autonomously ingest, impute, recalculate, revise, suppress, publish, certify, change units, widen access or dispose records without delegated authority." ], "crud": { "read": [ "Resolve collection head, series structure, observations, distinct times, vintages, values, flags, coverage, transformations, provenance, quality, access, lifecycle and projection loss under the permitted view." ], "create": [ "Bind stable identity, owner, purpose, series key, variable, measure, unit, dimensions, calendars, source authority and initial lifecycle before observations are accepted." ], "update": [ "Append successor definitions, observations, vintages, flags, methods, quality assertions, corrections, releases and lifecycle events with reason, authority, expected revision, event time and knowledge time." ], "delete": [ "Apply legal hold, reproducibility, privacy, security and adopting-Dimension records policy; withdraw or tombstone only the catalog view without cascading to external masters, and let authoritative systems execute physical disposition." ] }, "roles": [ { "name": "Series owner", "responsibilities": [ "Own purpose, scope, series definitions, lifecycle, compatibility and accountable use." ] }, { "name": "Data steward", "responsibilities": [ "Own identifiers, dimensions, variables, units, classifications, missing states and metadata quality." ] }, { "name": "Method and measurement owner", "responsibilities": [ "Own sampling, sensor, procedure, transformation, adjustment, forecast and uncertainty semantics." ] }, { "name": "Source and pipeline custodian", "responsibilities": [ "Own source bindings, processing runs, lineage, ingestion evidence, checksums and operational controls." ] }, { "name": "Quality reviewer", "responsibilities": [ "Own validation rules, quality metrics, anomaly review, limitations, corrections and certification decisions." ] }, { "name": "Access, privacy and records authority", "responsibilities": [ "Own purpose, confidentiality, access, license, embargo, retention, legal hold and disposition policy." ] }, { "name": "Publication and interoperability steward", "responsibilities": [ "Own releases, withdrawals, distributions, APIs, projection versions, declared loss and auditability." ] } ], "access": { "default_rule": "Deny unreleased, confidential, personal, security-sensitive, embargoed, fine-grained or reconstruction-capable values unless a purpose-bound policy permits the minimum necessary view.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Declared research, safety, incident, privacy, legal, audit or subject-rights access must cite authority, scope, purpose and time limit and must be logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, collection and series version, operation, authority, policy, RFC 3339 time, affected observations or keys, source revision and outcome without duplicating restricted values." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension data governance, namespace, variable, unit, calendar, privacy, access, retention and agent policies.", "Read this collection and linked observation, sensor, procedure, feature, population, source dataset, processing run, release, audit and records models before mutation." ] } }, "coverage": { "claim": "WM-DAT-010 covers one governed time series or observation collection from identity and dimensional structure through observations, values, multi-time semantics, vintages, coverage, transformations, forecasts, provenance, quality, corrections, lifecycle, access, distributions and projections. Domain profiles, restricted ISO clauses and independent external review remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Identity is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "classification and direct properties", "status": "covered", "notes": "Classification and direct properties is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Recognition and observation is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Capabilities and possible actions is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "composition", "status": "covered", "notes": "Composition is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "lifecycle", "status": "covered", "notes": "Lifecycle is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "relationships", "status": "covered", "notes": "Relationships is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "temporal", "status": "covered", "notes": "Temporal is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "spatial", "status": "covered", "notes": "Spatial is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "provenance", "status": "covered", "notes": "Provenance is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Ownership and stewardship is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "validation and quality", "status": "covered", "notes": "Validation and quality is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "access and privacy", "status": "covered", "notes": "Access and privacy is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retention and deletion is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "interoperability", "status": "covered", "notes": "Interoperability is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." }, { "dimension": "authority and ethics", "status": "covered", "notes": "Authority and ethics is explicit; domain, jurisdiction, measurement, forecast, quality, privacy and external-review profiles remain held where applicable." } ], "known_omissions": [ "Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.", "No relation row is frozen; the WM-MAT-008 parent signal grants no approved ownership or cascade behavior.", "Financial market ticks, industrial telemetry, climate grids, clinical observations, event sourcing, streaming systems and jurisdiction-specific statistics require separate profiles.", "ISO 8601-1:2019 is used only from public scope and lifecycle metadata; access-restricted requirements were not inferred.", "SSN ObservationCollection is identified by its 2023 Edition text as non-normative pending implementation experience and is treated as an alignment profile, not sole canon." ], "conflicts": [ "Series definition, observation collection, individual observation, sensor, feature, statistical unit, source dataset, processing run, release, vintage and distribution are not interchangeable identities.", "Phenomenon, reference, validity, result, availability, release, revision, recorded, ingestion, transaction and knowledge times are not one timestamp.", "Observed, estimated, imputed, adjusted, nowcast, forecast and scenario values require distinct classes and provenance.", "Missing, not applicable, suppressed, confidential, below detection, invalid, provisional and absent require distinct states." ], "regional_assumptions": [ "Privacy, confidentiality, disclosure control, embargo, retention, audit, legal hold and certification depend on jurisdiction, organization, population and domain.", "SDMX, OMS, SSN, RDF Data Cube, CF and FHIR are overlapping statistical, geospatial, sensor, linked-data, climate and healthcare profiles; none is universal." ], "adversarial_checks": [ "Reject a package that collapses the series definition, collection and observation into one identity.", "Reject a value without measure or observed property, unit or datatype, dimensions, time semantics, status, source and provenance.", "Reject a timestamp without seconds and explicit offset or Z, or a model that collapses event and knowledge time.", "Reject silent imputation, aggregation, unit conversion, seasonal adjustment, revision, suppression or forecast-to-observation conversion.", "Reject autonomous ingestion, recalculation, publication, certification, access widening or records disposition.", "Reject a projection that hides dimensions, units, calendars, missing states, vintages, provenance, quality or information loss." ] }, "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": "aggregate", "status": "accepted", "rationale": "The root is a versioned series-definition and observation-collection aggregate. Individual observation, variable, sensor, procedure, feature, statistical unit, source dataset, processing run, release, audit and records masters remain independently identifiable." }, "decisions": [ { "concept": "Series definition, collection and observation boundary", "disposition": "accepted-with-explicit-boundary", "rationale": "The series definition fixes semantic and dimensional structure, the collection governs membership and versions, and each observation is a separately qualified assertion." }, { "concept": "WM-MAT-008 parent signal", "disposition": "accepted-as-unapproved-reference", "rationale": "No relation row is frozen; the parent signal grants no ownership, mutation or cascade authority." }, { "concept": "Multiple temporal axes", "disposition": "accepted", "rationale": "Phenomenon, reference, validity, result, availability, release, revision, recorded, ingestion, transaction and knowledge times remain distinct and RFC 3339-qualified where represented as timestamps." }, { "concept": "Observed and projected values", "disposition": "accepted-with-classification-hold", "rationale": "Observed, estimated, imputed, adjusted, nowcast, forecast and scenario values remain explicitly classified and provenance-qualified." }, { "concept": "Missingness and value status", "disposition": "accepted", "rationale": "Missing, not applicable, suppressed, confidential, below detection, invalid, provisional and absent remain distinct states rather than overloaded nulls." }, { "concept": "Transformations and revisions", "disposition": "accepted-with-immutable-history", "rationale": "Aggregation, weighting, unit conversion, normalization, seasonal adjustment, revision, correction and restatement create explicit derived or successor assertions and never silently rewrite issued observations." }, { "concept": "Quality and fitness", "disposition": "accepted-with-evidence-hold", "rationale": "Validation, quality, anomaly, uncertainty, confidence and certification claims remain metric, method, scope, version, source and limitation qualified." }, { "concept": "External profiles", "disposition": "accepted-with-profile-hold", "rationale": "SDMX, OMS, SSN, RDF Data Cube, CF and FHIR are overlapping sector profiles. ISO claims are limited to public metadata and SSN ObservationCollection retains its published non-normative caveat." }, { "concept": "Authority and records", "disposition": "accepted-with-mandatory-authority", "rationale": "Ingestion, imputation, recalculation, revision, suppression, publication, certification, unit change, access widening and physical disposition require accountable external authority." }, { "concept": "Single-provider waiver and no-tools audit", "disposition": "accepted-with-mandatory-hold", "rationale": "One bounded Claude Sonnet and one bounded Grok attempt each timed out after 120 seconds. Codex separately audits the frozen validated result and comparison locally without tools or new research facts; assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-DAT-010 each timed out after 120 seconds; no external research result was admitted.", "Relation hold: no relation row is frozen and the WM-MAT-008 parent signal grants no approved ownership, mutation or cascade behavior.", "Boundary hold: series definition, collection, observation, variable, sensor, procedure, feature, statistical unit, source dataset, processing run, release, audit and records must remain separate identities.", "Temporal hold: phenomenon, reference, validity, result, availability, release, revision, recorded, ingestion, transaction and knowledge times must never be silently collapsed.", "Meaning hold: observed, estimated, imputed, adjusted, nowcast, forecast and scenario values require explicit classification, source, method and uncertainty.", "Authority hold: ingestion, imputation, recalculation, revision, suppression, publication, certification, unit change, access widening and records disposition require delegated authority.", "Restricted-source hold: ISO 8601-1:2019 is used only from public scope and lifecycle metadata; access-restricted clauses were not inspected or inferred.", "Profile hold: SSN ObservationCollection is non-normative in the cited edition, and SDMX, OMS, SSN, RDF Data Cube, CF and FHIR mappings require version pins, conformance tests and loss declarations.", "Privacy hold: confidential, personal, embargoed, security-sensitive, fine-grained and reconstruction-capable observations require purpose-bound access and minimization.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Approve or reject the WM-MAT-008 relation and register Variable, Unit, Observation, Sensor, Procedure, Feature, Statistical Unit, Population, Source Dataset, Processing Run, Release, Audit and Records edges.", "Create financial ticks, industrial telemetry, climate-grid, clinical observation, event-sourcing, stream-processing and jurisdiction-specific statistical profiles.", "Conformance-test series keys, calendars, time axes, missing states, vintages, transformations, forecasts, quality flags and distributions against concrete engines and datasets.", "Validate organization-specific ingestion, disclosure control, publication, certification, legal hold, retention and disposition policies.", "Inspect licensed ISO requirements under authorized access before making clause-level conformance claims.", "Obtain independent external review before promoting beyond reviewable-draft assurance." ] }, "statistics": { "sources": 15, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }