# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-21T17:08:26Z", "synthesisSha256": "4413dc88a83d33eff16877fe12f77b7f5fe99fe16b0c6065dfb41a4e8e64ef80", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-DAT-015", "registryId": "vr.wm-dat-015", "name": "Semantic Model", "version": "0.1.0-reviewable", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.DAT.SEM" ], "tags": [ "semantic", "model", "inf.dat.sem" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-dat-015-semantic-model/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-dat-015", "model": { "registry_id": "vr.wm-dat-015", "model_id": "WM-DAT-015", "name": "Semantic Model", "entry_kind": "entity", "purpose": "Describe the business meaning of datasets through a governed, versioned composition of entity roles, relationships, metric bindings and dimension bindings.", "scope_statement": "One semantic definition with stable identity and separately identified revisions. It specifies how selected datasets are interpreted for a stated use, including conceptual entities, grain, relationships and bindings to separately governed metrics and dimensions. It may be drafted before data is available. Storage, query execution and physical schemas are external. All structure and operations below are proposed local design, informed by open specifications rather than claimed universal requirements.", "in_scope": [ "Model-specific scope, term bindings, entity roles and declared populations or observation grain", "Relationship meaning, admissible analytical paths, metric and dimension bindings with contextual restrictions", "Interpretation of time, units and missingness; physical binding references and scoped acceptance evidence", "Provenance, release applicability and policy references for the semantic definition itself" ], "out_of_scope": [ "Dataset contents, distributions and storage lifecycle; physical schema and producer-consumer agreement masters", "Independent metric formula authoring, dimension member and hierarchy maintenance, ontology or glossary lifecycle", "Query compilation and execution, actual authorization, data transformation, runtime lineage capture and monitoring", "A universal ontology, commercial analytical platform configuration or a claim of executable standard conformance" ], "boundary_notes": [ { "neighbor": "WM-DAT-004 Data Schema / Data Contract", "distinction": "The registry parent is a taxonomy lead. Align the specialized semantic composition to an external schema or contract; do not infer a producer-consumer agreement from the existence of business meaning. Generic schema constraints and contractual obligations stay with that master. No executable inheritance or mandatory contract instance is ratified.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "neighbor": "WM-DAT-001 Dataset", "distinction": "A semantic definition can describe several datasets or an intended dataset role. A source binding references the selected asset and revision, while records, access enforcement and asset lifecycle remain external.", "source_refs": [ "SRC-003", "SRC-006" ] }, { "neighbor": "WM-DAT-013 Metric Definition", "distinction": "This model selects a metric revision and binds its inputs and permitted dimensions. Formula, generic aggregation semantics and metric ownership remain in the metric master. A local override that changes meaning requires a separately governed metric revision.", "source_refs": [ "SRC-003", "SRC-008" ] }, { "neighbor": "WM-DAT-014 Dimension and Hierarchy", "distinction": "This model assigns analytical roles, permitted levels and context restrictions to pinned dimension references. It does not maintain member lists, hierarchy edges or their lifecycle.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ] }, { "neighbor": "WM-KNW-001 Model / Ontology and WM-DAT-011 Knowledge Graph", "distinction": "Term and ontology references constrain interpretation but do not turn this definition into a universal ontology or the graph of instance assertions. Graph publication is a projection, not the aggregate root.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-DAT-005 Data Pipeline and external evaluators", "distinction": "Mapping and assessment references document intended interpretation and supplied evidence. They do not own data transformation runs, query plans, metric calculation, evaluator internals or enforcement state.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-009" ] } ] }, "sources": [ { "id": "SRC-001", "title": "RDF 1.1 Concepts and Abstract Syntax", "organization": "W3C", "url": "https://www.w3.org/TR/rdf11-concepts/", "version_or_date": "Recommendation, 25 February 2014", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:07:08Z", "relevance": "Sections 1 and 3 distinguish resource identifiers, graph statements and literal values. Used as an identity and representation foundation, not a mandate to store this model as RDF." }, { "id": "SRC-002", "title": "SKOS Simple Knowledge Organization System Reference", "organization": "W3C", "url": "https://www.w3.org/TR/skos-reference/", "version_or_date": "Recommendation, 18 August 2009", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:07:08Z", "relevance": "Sections 3-8 and 10 support concept identifiers, language-aware labels, schemes and qualified mappings. Concept similarity is not unrestricted identity or evidence of safe analytical roll-up." }, { "id": "SRC-003", "title": "The RDF Data Cube Vocabulary", "organization": "W3C", "url": "https://www.w3.org/TR/vocab-data-cube/", "version_or_date": "Recommendation, 16 January 2014", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:07:08Z", "relevance": "Sections 5-6 distinguish observations, dimensions, attributes, measures and reusable structure definitions. This is an analytical alignment; arbitrary business metric formulas and safe join policies are local design questions." }, { "id": "SRC-004", "title": "Shapes Constraint Language (SHACL)", "organization": "W3C", "url": "https://www.w3.org/TR/shacl/", "version_or_date": "Recommendation, 20 July 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:07:08Z", "relevance": "Sections 2-3 describe shapes, targets, validation and reports over selected inputs. A report is scoped evidence and does not establish business truth, complete target coverage or runtime permission." }, { "id": "SRC-005", "title": "PROV-O: The PROV Ontology", "organization": "W3C", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:07:08Z", "relevance": "Sections 3-4 provide entity, activity, attribution, derivation and revision vocabulary. This supports provenance links for definitions and evidence without owning execution lineage or certifying claims." }, { "id": "SRC-006", "title": "R2RML: RDB to RDF Mapping Language", "organization": "W3C", "url": "https://www.w3.org/TR/r2rml/", "version_or_date": "Recommendation, 27 September 2012", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:07:08Z", "relevance": "Sections 3-8 describe mapping resources, logical tables, term maps and join conditions. Used as a concrete mapping alignment; no universal mapping language or cardinality guarantee is inferred." }, { "id": "SRC-007", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "July 2002, selected Sections 4-5; update applicability pending", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:07:08Z", "relevance": "Section 5.6 supplies timestamp syntax with seconds and an offset. Calendar periods, fiscal calendars and analytical validity windows require separate profile rules." }, { "id": "SRC-008", "title": "SDMX Standards Section 2: Information Model - UML Conceptual Design", "organization": "SDMX initiative", "url": "https://sdmx.org/wp-content/uploads/SDMX_3-1-0_SECTION_2_FINAL.pdf", "version_or_date": "Version 3.1, May 2025; revision-history chronology requires verification", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:07:08Z", "relevance": "Sections 3.2, 4.5 and 5 distinguish maintained versions, concepts and data structure components. Selected prose was reviewed; diagrams and full conformance were not evaluated." }, { "id": "SRC-009", "title": "ODRL Information Model 2.2", "organization": "W3C", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "Recommendation, 15 February 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:07:08Z", "relevance": "Sections 1-3 distinguish policy expression, constraints, permissions, prohibitions, duties and profiles. A declaration does not execute access control; enforcement remains external." } ], "structure": { "bundles": [ { "id": "b-mandate", "name": "Identity and meaning", "description": "Identify the definition and the business vocabulary it applies.", "rationale": "Stable identity and explicit meaning allow multiple revisions and viewpoints without conflating labels with entities.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "layers": [ { "id": "l-identity", "name": "Definition mandate", "description": "Proposed root record identifies one semantic definition, its intended use and authoritative steward. A composed view remains one governed entity; referenced definitions keep their own identities.", "source_refs": [ "SRC-001", "SRC-008" ], "findings": [ { "id": "f-identity", "name": "Semantic definition identity and remit", "description": "Proposed root record identifies one semantic definition, its intended use and authoritative steward. A composed view remains one governed entity; referenced definitions keep their own identities.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "q-identity-01", "text": "Which master identifier denotes this semantic definition across revisions?", "kind": "identity", "answer_data": [ "model_id", "master_reference", "namespace" ] }, { "id": "q-identity-02", "text": "Which business questions and dataset roles fall within this model?", "kind": "definition", "answer_data": [ "use_cases", "population_scope", "exclusions" ] }, { "id": "q-identity-03", "text": "Which accountable role can approve this definition for its stated use?", "kind": "ownership", "answer_data": [ "steward_reference", "approval_scope", "authority_evidence" ] }, { "id": "q-identity-04", "text": "Is this revision conceptual, bound to data, or retired from use?", "kind": "classification", "answer_data": [ "readiness_class", "binding_status", "reason" ] } ], "data_elements": [ { "id": "d-identity-01", "name": "Model identifier", "description": "Stable definition identity, independent of release.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "d-identity-02", "name": "Mandate", "description": "Intended business use, subject area, exclusions and accountable role reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "d-identity-03", "name": "Readiness", "description": "Declared conceptual, bound or retired status; not an execution status.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "a-identity", "name": "Semantic mandate record", "description": "Proposed versioned evidence or declaration for semantic definition identity and remit. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "l-terms", "name": "Business vocabulary", "description": "Bind local business terms to concept references with language and context. Similar names do not establish shared meaning, and mapping strength remains explicit.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "f-terms", "name": "Contextual term and concept bindings", "description": "Bind local business terms to concept references with language and context. Similar names do not establish shared meaning, and mapping strength remains explicit.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "q-terms-01", "text": "Which concept and definition does each local business term denote?", "kind": "definition", "answer_data": [ "local_term_id", "concept_reference", "definition", "context" ] }, { "id": "q-terms-02", "text": "Which labels and language tags distinguish synonyms from homonyms?", "kind": "classification", "answer_data": [ "preferred_label", "alternative_labels", "language", "disambiguation_note" ] }, { "id": "q-terms-03", "text": "What mapping strength and evidence justify each external concept alignment?", "kind": "interoperability", "answer_data": [ "target_scheme_version", "relation_type", "mapping_evidence" ] }, { "id": "q-terms-04", "text": "How is an unresolved or disputed business term represented without silently selecting a meaning?", "kind": "exception", "answer_data": [ "candidate_meanings", "dispute_status", "responsible_role" ] } ], "data_elements": [ { "id": "d-terms-01", "name": "Term bindings", "description": "Local term identifiers, definitions, context and pinned concept references.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "d-terms-02", "name": "Mapping decisions", "description": "Typed alignment assertions, evidence and unresolved alternatives.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "a-terms", "name": "Term binding catalogue", "description": "Proposed versioned evidence or declaration for contextual term and concept bindings. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-entities", "name": "Entities and relationships", "description": "Declare the semantic units represented and the paths allowed between them.", "rationale": "A physical key or join does not by itself establish a business entity or safe analytical relationship.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "layers": [ { "id": "l-grain", "name": "Semantic units", "description": "Declare what one record or observation represents in each dataset role. Distinguish a business entity from an observation about it and from its storage key.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "f-grain", "name": "Entity role and observation grain", "description": "Declare what one record or observation represents in each dataset role. Distinguish a business entity from an observation about it and from its storage key.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "q-grain-01", "text": "What distinguishes one business entity from one observation in each role?", "kind": "identity", "answer_data": [ "entity_role", "identity_reference", "observation_key", "identity_scope" ] }, { "id": "q-grain-02", "text": "At what grain is each selected dataset role interpreted?", "kind": "composition", "answer_data": [ "dataset_role", "grain_components", "population_definition" ] }, { "id": "q-grain-03", "text": "Which key and uniqueness assumptions are declared and which have supporting evidence?", "kind": "constraint", "answer_data": [ "candidate_keys", "uniqueness_assertion", "evidence_reference", "unverified_assumptions" ] }, { "id": "q-grain-04", "text": "How are duplicate observations, absent keys and changing entity identifiers handled?", "kind": "exception", "answer_data": [ "duplicate_policy_reference", "identity_resolution_reference", "unresolved_case" ] } ], "data_elements": [ { "id": "d-grain-01", "name": "Entity roles", "description": "Local semantic roles with external concept and master-identity references.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "d-grain-02", "name": "Grain declarations", "description": "Observation unit, population and key assumptions for intended or actual dataset roles.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "a-grain", "name": "Entity and grain declaration", "description": "Proposed versioned evidence or declaration for entity role and observation grain. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "l-relations", "name": "Analytical paths", "description": "Keep the semantic predicate separate from its physical join binding. Proposed path restrictions require explicit cardinality and grain evidence; executable join safety is not claimed.", "source_refs": [ "SRC-001", "SRC-006" ], "findings": [ { "id": "f-relations", "name": "Relationship meaning and join admissibility", "description": "Keep the semantic predicate separate from its physical join binding. Proposed path restrictions require explicit cardinality and grain evidence; executable join safety is not claimed.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "q-relations-01", "text": "What predicate, direction and role distinguish the endpoints of each relationship?", "kind": "relationship", "answer_data": [ "relationship_id", "source_role", "target_role", "predicate_reference" ] }, { "id": "q-relations-02", "text": "Which endpoint cardinalities and temporal conditions must hold for an analytical path?", "kind": "constraint", "answer_data": [ "declared_cardinality", "join_condition_reference", "time_condition", "evidence_reference" ] }, { "id": "q-relations-03", "text": "How will reviewers detect fan-out, unmatched rows and ambiguous paths before admitting a binding?", "kind": "quality", "answer_data": [ "test_reference", "expected_multiplicity", "unmatched_policy", "path_selection_rule" ] }, { "id": "q-relations-04", "text": "What restriction applies when a many-to-many path lacks an approved allocation rule?", "kind": "exception", "answer_data": [ "blocked_use", "allocation_definition_reference", "decision_reason" ] } ], "data_elements": [ { "id": "d-relations-01", "name": "Relationship bindings", "description": "Semantic predicate, endpoints and separately pinned join representation.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "d-relations-02", "name": "Path admission", "description": "Declared multiplicity, grain-preservation evidence and blocked or permitted uses.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "a-relations", "name": "Relationship admission matrix", "description": "Proposed versioned evidence or declaration for relationship meaning and join admissibility. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-analytics", "name": "Analytical composition", "description": "Bind independently governed metrics and dimensions into a meaningful view.", "rationale": "A view selects and contextualizes reusable components without taking over their definition lifecycle.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ], "layers": [ { "id": "l-metrics", "name": "Metric bindings", "description": "Select metric definitions and map their input roles to the model. Formula changes belong to a metric revision; this definition records contextual admissibility and loss of meaning.", "source_refs": [ "SRC-003", "SRC-008" ], "findings": [ { "id": "f-metrics", "name": "Contextual metric selection", "description": "Select metric definitions and map their input roles to the model. Formula changes belong to a metric revision; this definition records contextual admissibility and loss of meaning.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "q-metrics-01", "text": "Which metric identifiers and revisions are exposed by this semantic model?", "kind": "composition", "answer_data": [ "metric_reference", "metric_revision", "local_alias" ] }, { "id": "q-metrics-02", "text": "Which source roles, units and grain satisfy each metric input contract?", "kind": "measurement", "answer_data": [ "input_binding", "expected_unit", "input_grain", "compatibility_evidence" ] }, { "id": "q-metrics-03", "text": "Which dimensions and aggregation levels are allowed or prohibited for each selected metric?", "kind": "constraint", "answer_data": [ "metric_dimension_matrix", "aggregation_rule_reference", "prohibited_rollups" ] }, { "id": "q-metrics-04", "text": "What happens if a metric dependency changes or its required input becomes unavailable?", "kind": "exception", "answer_data": [ "dependency_change", "affected_bindings", "blocked_state", "remediation_owner" ] } ], "data_elements": [ { "id": "d-metrics-01", "name": "Metric references", "description": "Pinned metric masters and aliases; empty is allowed for a non-metric semantic model.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "d-metrics-02", "name": "Metric context", "description": "Input bindings, compatible grains and restrictions; no independently authored formula copies.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "a-metrics", "name": "Metric exposure matrix", "description": "Proposed versioned evidence or declaration for contextual metric selection. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "l-dimensions", "name": "Dimension roles", "description": "Assign local analytical roles and eligible levels to separately maintained dimensions. Hierarchy membership and semantic similarity do not prove that a measure can be summed.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ], "findings": [ { "id": "f-dimensions", "name": "Dimension and hierarchy selection", "description": "Assign local analytical roles and eligible levels to separately maintained dimensions. Hierarchy membership and semantic similarity do not prove that a measure can be summed.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ], "questions": [ { "id": "q-dimensions-01", "text": "Which dimension and hierarchy revisions serve each analytical role?", "kind": "composition", "answer_data": [ "dimension_reference", "hierarchy_reference", "revision", "role" ] }, { "id": "q-dimensions-02", "text": "Which levels or code subsets are applicable to this view?", "kind": "classification", "answer_data": [ "permitted_levels", "subset_reference", "selection_basis" ] }, { "id": "q-dimensions-03", "text": "Which dimension validity rules apply to historical and current views?", "kind": "temporal", "answer_data": [ "validity_binding", "as_of_policy", "history_rule_reference" ] }, { "id": "q-dimensions-04", "text": "How are unknown members, overlapping groups and non-additive roll-ups exposed?", "kind": "exception", "answer_data": [ "unknown_member_policy", "overlap_evidence", "restricted_metric_bindings" ] } ], "data_elements": [ { "id": "d-dimensions-01", "name": "Dimension bindings", "description": "Pinned external dimension and hierarchy identifiers with local roles.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ] }, { "id": "d-dimensions-02", "name": "Level restrictions", "description": "Allowed levels, subsets and metric-specific restrictions; external hierarchy remains authoritative.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "a-dimensions", "name": "Dimension role map", "description": "Proposed versioned evidence or declaration for dimension and hierarchy selection. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-interpretation", "name": "Value and time interpretation", "description": "Make context-dependent interpretation explicit before combining observations.", "rationale": "Representation compatibility is weaker than semantic compatibility; temporal and value rules must be stated.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008" ], "layers": [ { "id": "l-values", "name": "Value interpretation", "description": "Record semantic interpretation for bound values, with conversion and missing-value rules delegated to approved definitions. Unknown, absent, suppressed, not applicable and zero are distinct proposed statuses.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "f-values", "name": "Units, missingness and comparability", "description": "Record semantic interpretation for bound values, with conversion and missing-value rules delegated to approved definitions. Unknown, absent, suppressed, not applicable and zero are distinct proposed statuses.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "questions": [ { "id": "q-values-01", "text": "Which unit, scale and representation apply to each value role?", "kind": "measurement", "answer_data": [ "role_id", "unit_reference", "scale", "representation_reference" ] }, { "id": "q-values-02", "text": "How are zero, missing, suppressed and not-applicable values distinguished?", "kind": "definition", "answer_data": [ "missingness_codes", "meaning", "default_policy" ] }, { "id": "q-values-03", "text": "Which conversions or comparisons require a separately approved rule?", "kind": "constraint", "answer_data": [ "conversion_reference", "comparison_scope", "rounding_rule_reference" ] }, { "id": "q-values-04", "text": "What evidence supports comparability across sources or changed measurement methods?", "kind": "quality", "answer_data": [ "comparability_assessment", "method_reference", "known_bias", "limitation" ] } ], "data_elements": [ { "id": "d-values-01", "name": "Value interpretation", "description": "Unit, scale, datatype and missingness meaning for bound or intended roles.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "d-values-02", "name": "Comparability references", "description": "Approved conversion or assessment references; never assume identical labels imply equivalent values.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "a-values", "name": "Value interpretation profile", "description": "Proposed versioned evidence or declaration for units, missingness and comparability. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "l-time", "name": "Temporal context", "description": "Separate observation period, event time, processing time and definition validity. RFC 3339 timestamps do not encode a complete reporting calendar or a fiscal period.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "findings": [ { "id": "f-time", "name": "Analytical time and applicability", "description": "Separate observation period, event time, processing time and definition validity. RFC 3339 timestamps do not encode a complete reporting calendar or a fiscal period.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "questions": [ { "id": "q-time-01", "text": "Which time role governs each observation and each metric binding?", "kind": "temporal", "answer_data": [ "time_role", "event_time_binding", "observation_period_binding", "processing_time_binding" ] }, { "id": "q-time-02", "text": "What timezone, calendar and boundary convention determine period membership?", "kind": "constraint", "answer_data": [ "timezone_reference", "calendar_reference", "inclusive_bounds", "daylight_saving_policy" ] }, { "id": "q-time-03", "text": "Which revision applies to an as-of query after a retroactive correction?", "kind": "lifecycle", "answer_data": [ "model_revision", "validity_interval", "recorded_at", "correction_reference" ] }, { "id": "q-time-04", "text": "How are late observations, incomplete periods and unknown time precision declared?", "kind": "exception", "answer_data": [ "lateness_policy_reference", "period_completeness", "precision", "unknown_time_status" ] } ], "data_elements": [ { "id": "d-time-01", "name": "Temporal bindings", "description": "Temporal roles and profile references; explicitly mark inapplicability where no analytical time exists.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] }, { "id": "d-time-02", "name": "Applicability interval", "description": "Effective boundaries and recording timestamp, without inventing precision for dates or periods.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "a-time", "name": "Temporal interpretation profile", "description": "Proposed versioned evidence or declaration for analytical time and applicability. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-binding", "name": "Bindings and acceptance", "description": "Connect the semantic definition to representations and scoped test evidence.", "rationale": "Mappings require explicit loss declarations; successful structural checks do not settle meaning or correct use.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "l-mapping", "name": "Source mappings", "description": "Reference approved mappings between conceptual roles and source fields or expressions. A mapping describes intended correspondence; execution and transformation lineage remain external.", "source_refs": [ "SRC-001", "SRC-006" ], "findings": [ { "id": "f-mapping", "name": "Representation binding and semantic loss", "description": "Reference approved mappings between conceptual roles and source fields or expressions. A mapping describes intended correspondence; execution and transformation lineage remain external.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "q-mapping-01", "text": "Which schema revisions and field paths implement each semantic role?", "kind": "interoperability", "answer_data": [ "source_asset_reference", "schema_revision", "field_path", "semantic_role" ] }, { "id": "q-mapping-02", "text": "Who supplied the mapping and which evidence supports its meaning?", "kind": "provenance", "answer_data": [ "mapping_author_role", "mapping_revision", "evidence_reference", "review_state" ] }, { "id": "q-mapping-03", "text": "Which casts, filters or transformations may change the interpreted population or value?", "kind": "constraint", "answer_data": [ "transformation_reference", "loss_declaration", "affected_roles", "approval_reference" ] }, { "id": "q-mapping-04", "text": "How is an unresolved field, changed schema or lossy export reported?", "kind": "exception", "answer_data": [ "unresolved_binding", "drift_evidence", "blocked_capability", "projection_loss" ] } ], "data_elements": [ { "id": "d-mapping-01", "name": "Mapping references", "description": "Pinned source-schema and mapping records; a conceptual draft can have none.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "d-mapping-02", "name": "Projection losses", "description": "Dropped constraints, unsupported terms, precision loss and blocked capabilities.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "a-mapping", "name": "Semantic mapping register", "description": "Proposed versioned evidence or declaration for representation binding and semantic loss. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "l-acceptance", "name": "Evidence and acceptance", "description": "Record acceptance criteria and links to supplied reports for this revision and binding set. Distinguish report failure, nonconformance, absence of evidence and accepted limitations.", "source_refs": [ "SRC-004", "SRC-005" ], "findings": [ { "id": "f-acceptance", "name": "Scoped semantic acceptance evidence", "description": "Record acceptance criteria and links to supplied reports for this revision and binding set. Distinguish report failure, nonconformance, absence of evidence and accepted limitations.", "source_refs": [ "SRC-004", "SRC-005" ], "questions": [ { "id": "q-acceptance-01", "text": "Which acceptance criteria test meaning, grain and the selected metric-dimension combinations?", "kind": "validation", "answer_data": [ "criterion_id", "scope", "fixture_reference", "expected_outcome" ] }, { "id": "q-acceptance-02", "text": "Which exact model, source snapshot and validator configuration produced a supplied report?", "kind": "evidence", "answer_data": [ "model_revision", "source_snapshot", "shape_or_rule_revision", "processor_profile", "report_reference" ] }, { "id": "q-acceptance-03", "text": "Which targets or paths were untested even if a report says the selected inputs conform?", "kind": "quality", "answer_data": [ "target_coverage", "inactive_constraints", "untested_paths", "report_limitations" ] }, { "id": "q-acceptance-04", "text": "Who accepts residual limitations and what prevents an untested binding from being labelled ready?", "kind": "decision", "answer_data": [ "acceptance_role", "decision_reference", "remaining_gaps", "readiness_gate" ] } ], "data_elements": [ { "id": "d-acceptance-01", "name": "Acceptance criteria", "description": "Model-specific criteria and synthetic fixture references; executable fixtures remain a hold.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-004", "SRC-005" ] }, { "id": "d-acceptance-02", "name": "Evidence links", "description": "Version-bound externally produced reports with scope, status and limitations.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "a-acceptance", "name": "Acceptance evidence index", "description": "Proposed versioned evidence or declaration for scoped semantic acceptance evidence. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-stewardship", "name": "Revision and use governance", "description": "Govern the definition and its disclosures without operating underlying systems.", "rationale": "Attribution and scoped policies support accountable release decisions; they are distinct from enforcement.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009" ], "layers": [ { "id": "l-revision", "name": "Change and provenance", "description": "Maintain the semantic definition revision chain and dependency pins. Proposed change reviews classify meaning changes and notify affected roles through a separate authorized process.", "source_refs": [ "SRC-005", "SRC-008" ], "findings": [ { "id": "f-revision", "name": "Revision lineage and dependency impact", "description": "Maintain the semantic definition revision chain and dependency pins. Proposed change reviews classify meaning changes and notify affected roles through a separate authorized process.", "source_refs": [ "SRC-005", "SRC-008" ], "questions": [ { "id": "q-revision-01", "text": "Which prior revision and evidence explain each semantic change?", "kind": "provenance", "answer_data": [ "prior_revision", "change_reason", "evidence_reference", "attribution" ] }, { "id": "q-revision-02", "text": "Which review and approval evidence authorizes activation or retirement of a revision?", "kind": "lifecycle", "answer_data": [ "lifecycle_state", "approval_reference", "effective_time", "retirement_reason" ] }, { "id": "q-revision-03", "text": "Which dependent views or bindings are incompatible with a change in grain, term or component revision?", "kind": "constraint", "answer_data": [ "dependency_inventory", "impact_assessment", "compatibility_scope" ] }, { "id": "q-revision-04", "text": "What record disposition preserves necessary references while removing restricted payloads when required?", "kind": "retention", "answer_data": [ "retention_policy_reference", "hold_reference", "minimal_tombstone", "disposal_authority" ] } ], "data_elements": [ { "id": "d-revision-01", "name": "Revision record", "description": "Revision identifier, predecessor, author role, reason and review state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "d-revision-02", "name": "Dependency pins", "description": "Exact component versions, resolution state and impact evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "a-revision", "name": "Revision and impact record", "description": "Proposed versioned evidence or declaration for revision lineage and dependency impact. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "l-use", "name": "Policy context", "description": "Reference policies applying to definitions, mappings and evidence. Public vocabulary does not grant access to underlying data or authorize inference from combined sensitive dimensions.", "source_refs": [ "SRC-009" ], "findings": [ { "id": "f-use", "name": "Use restrictions and disclosure boundary", "description": "Reference policies applying to definitions, mappings and evidence. Public vocabulary does not grant access to underlying data or authorize inference from combined sensitive dimensions.", "source_refs": [ "SRC-009" ], "questions": [ { "id": "q-use-01", "text": "Who may inspect the definition, mappings and linked evidence at each structural scope?", "kind": "access", "answer_data": [ "policy_reference", "role_scope", "artifact_classification" ] }, { "id": "q-use-02", "text": "Which combinations of exposed roles or measures require restricted disclosure review?", "kind": "privacy", "answer_data": [ "sensitive_combination", "review_reference", "permitted_purpose" ] }, { "id": "q-use-03", "text": "Which external authority decides actual data access and permitted execution?", "kind": "authority", "answer_data": [ "enforcement_owner_role", "authorization_reference", "execution_boundary" ] }, { "id": "q-use-04", "text": "How is a time-limited policy exception recorded without silently widening the default access rule?", "kind": "exception", "answer_data": [ "exception_approval", "scope", "expiry", "revocation_reference" ] } ], "data_elements": [ { "id": "d-use-01", "name": "Use policy references", "description": "Purpose, audience and disclosure restrictions; enforcement is external.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "d-use-02", "name": "Exception references", "description": "Approved scoped exceptions with expiry and authority references.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "a-use", "name": "Semantic use policy index", "description": "Proposed versioned evidence or declaration for use restrictions and disclosure boundary. Content must preserve unresolved items and source references.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier, else governed IRI, else owner-assigned UUID; revision and content digest separate from stable identity. Neither filename nor timestamp is the identity.", "source_refs": [ "SRC-009" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "fn-draft", "name": "Prepare semantic revision", "description": "Proposed local operation, not implemented: prepare a candidate revision with explicit unresolved terms and dataset roles.", "inputs": [ "current revision or new identity authority", "mandate and term evidence" ], "outputs": [ "candidate revision or refusal reasons" ], "preconditions": [ "Authorized steward role and current expected revision", "Namespace and source attribution checked" ], "effects": [ "Creates a local candidate definition; does not activate it or modify external masters" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "fn-bind", "name": "Propose component bindings", "description": "Proposed local operation, not implemented: bind supplied metric, dimension and dataset revisions to local roles.", "inputs": [ "candidate revision", "pinned component references", "declared grain and policy context" ], "outputs": [ "binding proposal with unresolved or incompatible entries" ], "preconditions": [ "Editor authorization", "No silent formula, hierarchy or source-schema overrides" ], "effects": [ "Records a local binding proposal; it performs no data retrieval, join or calculation" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] }, { "id": "fn-inspect", "name": "Inspect declaration completeness", "description": "Proposed local operation, not implemented: check the proposed record for unresolved references and missing admission evidence.", "inputs": [ "model revision", "reference inventory", "acceptance requirements" ], "outputs": [ "scoped completeness report, unknowns and blocked uses" ], "preconditions": [ "Read authority over the selected scope", "Pinned declaration and rule revisions; unavailable dependencies marked unknown" ], "effects": [ "Reports local declaration gaps without claiming live data validation or business correctness" ], "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "fn-evidence", "name": "Attach supplied acceptance evidence", "description": "Proposed local operation, not implemented: index externally produced results against an exact revision and scope.", "inputs": [ "report reference", "model and binding revisions", "source snapshot reference" ], "outputs": [ "evidence-index revision or mismatch refusal" ], "preconditions": [ "Evidence-access permission", "Attribution and integrity recorded", "Reject revision mismatch or preserve as explicitly inapplicable evidence" ], "effects": [ "Links evidence locally; does not run an evaluator or convert a report into universal approval" ], "source_refs": [ "SRC-004", "SRC-005" ] }, { "id": "fn-impact", "name": "Prepare semantic change assessment", "description": "Proposed local operation, not implemented: compare supplied revision declarations and dependency pins.", "inputs": [ "old and proposed revision", "dependency inventory", "change rationale" ], "outputs": [ "review proposal with compatibility unknowns and affected roles" ], "preconditions": [ "Access to both revisions", "Inventory completeness declared", "Current expected revision checked" ], "effects": [ "Records proposed impact classification; no consumer migration, notifications or query execution" ], "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "fn-retire", "name": "Record authorized retirement", "description": "Proposed local operation, not implemented: mark a definition revision unavailable for new use after a supplied decision.", "inputs": [ "revision", "retirement approval", "successor or tombstone reference", "retention policy" ], "outputs": [ "retirement record or refusal reasons" ], "preconditions": [ "Authorized decision and concurrency check", "Referenced dependencies assessed", "Retention holds and restricted-payload disposition resolved by responsible authority" ], "effects": [ "Updates local revision state and minimal references; does not delete datasets, revoke access or rewrite external histories" ], "source_refs": [ "SRC-005", "SRC-009" ] } ], "composition": [ { "target": "WM-DAT-004", "relation": "ALIGN", "purpose": "Candidate taxonomy alignment to the parent Data Schema / Data Contract; bindings use pinned external constraints. No mandatory producer-consumer agreement or executable inheritance is assumed.", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "target": "WM-DAT-001", "relation": "REFERENCE", "purpose": "Dataset role and source snapshot reference; records and catalogue lifecycle remain in the dataset master.", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "target": "WM-DAT-013", "relation": "REFERENCE", "purpose": "Select metric revisions and input roles; formula ownership, generic aggregation semantics and metric lifecycle remain external.", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] }, { "target": "WM-DAT-014", "relation": "REFERENCE", "purpose": "Select dimension roles and eligible hierarchy levels; member and hierarchy maintenance remain external.", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ] }, { "target": "WM-KNW-001", "relation": "REFERENCE", "purpose": "Pin concept and ontology references without importing ontology governance or arbitrary entailment into local identity.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-DAT-011", "relation": "REFERENCE", "purpose": "Optional assertion graph or evidence view; the semantic definition does not own instance graph contents.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "WM-DAT-005", "relation": "REFERENCE", "purpose": "Optional mapping implementation and run evidence references; transformation and runtime lineage stay with their masters.", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Accountable semantic steward role and namespace authority, identified without a commercial owner label", "Declared model purpose, dataset-role boundary, component masters and approval scope", "Adoption profile with retention, access, language, calendar, unit and dependency-resolution policies" ], "namespace_guidance": "Keep stable model identity, revision identity and local role IDs separate. Resolve external namespace prefixes against pinned declarations. Never rename external IRIs to imply local ownership.", "registry_links": [ "vr.wm-dat-015", "WM-DAT-004 taxonomy alignment; binding pending", "WM-DAT-013 and WM-DAT-014 component master candidates" ] }, "canon_and_patch": { "canonicalization_rules": [ "Normalize the local declaration representation under a declared algorithm while preserving original labels, numeric precision, missingness and external identifiers. A byte digest is not semantic equivalence.", "Do not call this reviewable research draft canonical. Instance release authority is an adopting-profile decision." ], "patch_rules": [ "Patches name the expected revision and affected local paths, author role, reason and evidence. Reject stale revisions and unresolved authorization.", "Never silently widen scope, replace component pins or modify a metric formula through a view-local patch." ], "compatibility_rules": [ "Assess meaning and permissible use, not just syntactic shape. Grain, identity, unit, time, metric or dimension changes can invalidate dependent uses.", "Record compatible, incompatible or unknown per consumer profile; unknown blocks automatic promotion. Preserve mapping losses and a successor path." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "UUID or ULID assigned by the adopting Dimension" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and an explicit offset or Z for recording and event instants. Separate event time from observation or ingestion time. Preserve dates, reporting periods, timezone rules and unknown precision separately; do not invent midnight instants.", "serial_naming_rule": "Use stable artifact ID plus revision and an optional descriptive label. Serial evidence reports have distinct run or report IDs; dates are metadata, not identities.", "integrity_rule": "Record media type, algorithm and digest for the exact bytes plus provenance. Restricted evidence may be a resolvable authorized reference. Hash equality does not establish truth, equivalence or permission." }, "policies": [ "Proposed local policy: no external data access, query execution or broader disclosure follows from a semantic-model declaration. Actual enforcement belongs to the authorized system and owner role.", "Proposed local policy: allow only versioned, reviewed meaning changes; preserve unknown, disputed, unsupported and not-applicable states distinctly.", "Proposed local policy: exclude credentials and real sensitive sample data from public mappings and fixtures. Treat combined metric and dimension disclosure at policy level.", "Open specifications are conceptual alignments; profile-specific rights, licensing and conformance require independent verification." ], "crud": { "read": [ "Resolve model revision, source provenance and caller scope before exposing term bindings, mapping details or evidence. Return explicit redaction and unresolved-reference markers." ], "create": [ "Reserve stable identity in the authorized namespace, declare mandate and steward role, and create a draft with incomplete bindings marked as such." ], "update": [ "Use revision-aware patches and preserve prior attributable declarations subject to retention. Require role authorization and an impact record before changing meaning or scope." ], "delete": [ "Prefer retirement and minimal reference tombstones for the definition. Apply the adopting Dimension retention policy and holds before removing restricted payloads; preserve only permitted metadata.", "The external data owner executes dataset deletion and enforcement changes. Local retirement neither deletes source data nor preserves personal data indefinitely." ] }, "roles": [ { "name": "Semantic steward", "responsibilities": [ "Accountable for scope, business interpretation and proposed release decisions." ] }, { "name": "Component custodian", "responsibilities": [ "Maintains external metric, dimension, ontology or schema masters and approves referenced revisions." ] }, { "name": "Binding editor", "responsibilities": [ "Proposes local source and role bindings with provenance and declared loss." ] }, { "name": "Independent reviewer", "responsibilities": [ "Challenges semantic assumptions, acceptance scope and source support before promotion; absent in this run." ] }, { "name": "Access and records authority", "responsibilities": [ "Approves disclosure, exceptions and retention disposition in the adopting profile; executes enforcement externally." ] } ], "access": { "default_rule": "Deny access to restricted mapping and evidence details until purpose and role scope are authorized. Public definitions do not imply permission to access data.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Require a referenced approval with purpose, scope, expiry and revocation route; an exception cannot silently propagate to external data." ], "audit_requirements": [ "Record actor role, requested scope, purpose, revision, decision reference and redactions. Store sensitive audit details under the external audit policy.", "Record unresolved policy references and deny automatic expansion; definition annotations are not enforcement receipts." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and adopting Dimension authority and access policy", "spec.yaml boundary, review holds and component references", "Pinned semantic revision, evidence scope and only then permitted artifacts" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one governed semantic definition of dataset business meaning, with contextual bindings to separately mastered metrics and dimensions. A separate frozen local no-tools self-audit found no critical contradictions. Independent review, live source/version verification, domain profiles and executable conformance remain holds. This reviewable draft does not claim universal analytical coverage or runtime correctness.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable model, revision, concept and artifact identities are distinct." }, { "dimension": "lifecycle", "status": "covered", "notes": "Draft, binding readiness, review, revision and retirement are proposed local states." }, { "dimension": "relationships", "status": "covered", "notes": "Semantic predicate, physical join and supported cardinality are separated." }, { "dimension": "temporal", "status": "covered", "notes": "Event, observation, processing and validity time have explicit role bindings." }, { "dimension": "provenance", "status": "covered", "notes": "Definition changes, mappings and external reports retain attribution and revision context." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based stewardship and separate metric, dimension, schema and dataset masters are explicit." }, { "dimension": "validation", "status": "covered", "notes": "Declaration and supplied-report scope is specified; executable fixtures remain a gap." }, { "dimension": "access", "status": "covered", "notes": "Definition and evidence visibility are separate from underlying data authorization." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Local retirement, restricted payload disposition and external deletion authority are separated." }, { "dimension": "interoperability", "status": "covered", "notes": "Conceptual RDF, SKOS, Data Cube, SDMX, R2RML, SHACL, PROV-O and ODRL alignments retain loss declarations." }, { "dimension": "physical properties", "status": "not-applicable", "notes": "The root is an abstract definition. Units and quantities apply to described values, not its physical mass or location." }, { "dimension": "capabilities and behavior", "status": "covered", "notes": "Six proposed local record operations have preconditions, effects and refusal boundaries; no runtime capability is claimed." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Source mappings and scoped external test reports help identify an applicable revision without proving its universal correctness." }, { "dimension": "executable conformance", "status": "gap", "notes": "No complete instance schema, mapping implementation, query engine or adversarial fixture suite has been delivered." }, { "dimension": "independent review and live verification", "status": "gap", "notes": "Single-provider waiver applies; direct HTTP statuses and full latest-version checks remain unresolved." } ], "known_omissions": [ "Independent second-provider review is absent; local self-audit cannot replace it.", "Full source-version, errata, rights and current-profile verification remains incomplete. SDMX revision-history dates require clarification; no chronology is inferred beyond the stated cover version.", "Executable nested instance schemas, pinned neighbor specifications and acceptance fixtures are not implemented.", "Domain-specific aggregation, fiscal calendars, exchange rates, slowly changing dimensions and disclosure thresholds require qualified profiles.", "Non-relational mappings and formal reasoning profiles need additional evidence and testing." ], "conflicts": [], "regional_assumptions": [ "English research with language-tagged term bindings; no universal jurisdiction, fiscal calendar, unit system or access law is assumed.", "Analytical and statistical specifications are alignments to business semantics, not mandates that every semantic model is a cube or an RDF graph." ], "adversarial_checks": [ "Same labels must not collapse distinct business concepts or make SKOS mapping into unrestricted identity.", "An accepted relationship or R2RML mapping must not certify a many-to-many analytical path or prevent double counting without evidence.", "A passing validation report with empty targets must not imply complete semantic acceptance.", "Metric and hierarchy masters cannot be overridden through local aliases or bindings.", "A metadata permission or public schema must not imply underlying data access.", "Historical revision preservation must not override lawful restricted-payload disposition." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "Stable semantic-definition identity persists across separately identified revisions and component bindings. This is neither dataset contents nor a runtime graph. The registry standalone-mm value is a record-plane classification; its parent taxonomy is qualified as alignment without an inferred producer-consumer agreement or executable inheritance." }, "decisions": [ { "concept": "Semantic definition root", "disposition": "accepted", "rationale": "The declared unit is a governed business-meaning definition with stable identity and revisions. Referenced datasets, metrics and dimensions remain independently mastered." }, { "concept": "Parent taxonomy and agreement ownership", "disposition": "qualified", "rationale": "The ledger has no touching relation rows. ALIGN records the registry parent as a conceptual taxonomy lead while generic schema constraints and producer-consumer obligations stay external." }, { "concept": "Metric and hierarchy duplication", "disposition": "rejected", "rationale": "Local questions concern pinned component roles and compatible uses. Formula changes and hierarchy maintenance require action in the external component master, not an implicit local override." }, { "concept": "Metric-free and conceptual models", "disposition": "accepted", "rationale": "Optional metric, dimension and physical-mapping collections permit unbound or non-metric definitions. Required mandate, role and interpretation records still provide a meaningful draft boundary." }, { "concept": "Term equivalence and identity", "disposition": "separated", "rationale": "Contextual labels, concept references and mapping strength are explicit. The structure never treats a lexical match or SKOS mapping as unrestricted business-entity identity." }, { "concept": "Grain and analytical paths", "disposition": "accepted with evidence requirement", "rationale": "Semantic predicate, physical mapping, declared cardinality and observed multiplicity remain distinct. Fan-out, ambiguous paths and unsupported allocation rules remain blocked-use questions rather than assumed guarantees." }, { "concept": "Value and temporal interpretation", "disposition": "accepted with profile qualification", "rationale": "Missingness, units, calendars, effective intervals and recording timestamps are explicit. The result neither converts unknown periods into precise instants nor assumes universal comparability." }, { "concept": "Validation and business truth", "disposition": "separated", "rationale": "Acceptance evidence is tied to a revision, source snapshot and selected targets. Untested paths and inactive constraints prevent a passing report from being represented as universal semantic correctness." }, { "concept": "Proposed operation authority", "disposition": "accepted as unimplemented design", "rationale": "All six functions modify or inspect local declarations only with role and revision preconditions. None executes queries, computes metrics, transforms data, enforces access or deletes source datasets." }, { "concept": "Artifact identity and retention", "disposition": "accepted", "rationale": "Master identity, revision, timestamp and digest are separate. Retirement and minimum tombstones are qualified by retention and restricted-payload policy rather than imposing indefinite preservation." }, { "concept": "Disclosure and inference restrictions", "disposition": "accepted at policy level", "rationale": "Public vocabulary is not a data entitlement. Sensitive combinations and exceptions require external authority, and policy references are not enforcement receipts." }, { "concept": "Source currency and SDMX chronology", "disposition": "limited", "rationale": "Selected readable primary text supports conceptual foundations. Direct HTTP was not attempted, and the stated SDMX cover date is not used to invent a corrected revision chronology. Latest versions and errata remain open." }, { "concept": "Operational conformance", "disposition": "deferred", "rationale": "Candidate object groups, mapping references and proposed acceptance cases do not supply complete nested schemas, pinned neighbor implementations or executable adversarial fixtures." }, { "concept": "Provider independence", "disposition": "waived and held", "rationale": "Claude and Grok were skipped with zero attempts under the owner override. The frozen local Codex self-audit is a separate assessment phase but is not independent external review." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit does not supply a second-provider review.", "Live source and version verification remains incomplete. All nine URLs supplied selected web-service document text, but direct HTTP checks were not attempted under the sandbox restriction: zero measured responses, zero measured HTTP 200s, and null statuses. Full-text coverage, latest versions, errata and the SDMX revision-history chronology require coordinator review.", "Domain and adoption profiles must establish metric-grain compatibility, aggregation and allocation rules, calendars, units, comparability, privacy, disclosure thresholds, rights and retention before operational use. Source alignments do not certify these decisions.", "Executable nested instance schemas, pinned neighbor specifications, mapping implementations and adversarial acceptance fixtures remain incomplete. No runtime query capability, standard conformance or automatic compatibility certification is claimed.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Restore independent external review before canonical or publishable-draft promotion.", "Run the coordinator HTTP checker, verify exact source versions and errata, and clarify the SDMX chronology without treating HTTP success as claim verification.", "Develop profile-specific mappings and acceptance fixtures for ambiguous joins, non-additive metrics, historical dimensions, missingness, empty validation targets and restricted disclosures.", "Pin external metric, dimension, dataset, schema and ontology specifications and test change impact before operational adoption." ] }, "statistics": { "sources": 9, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }