# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-21T17:05:35Z", "synthesisSha256": "7402baf94b01ed4902c545e105fe18bc7b48160f1b456717815c4b94328a1273", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-DAT-013", "registryId": "vr.wm-dat-013", "name": "Metric Definition", "version": "0.1.0-reviewable-draft", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.DAT.MET" ], "tags": [ "metric", "definition", "inf.dat.met" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-dat-013-metric-definition/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-dat-013", "model": { "registry_id": "vr.wm-dat-013", "model_id": "WM-DAT-013", "name": "Metric Definition", "entry_kind": "entity", "purpose": "Describe a governed business metric through its meaning, formula, grain, filters, time basis, accountable roles and revision-specific interpretation.", "scope_statement": "One identifiable metric definition with versioned semantic contracts. The definition specifies how a value should be interpreted and derived; it does not contain measured values or run calculations. All structures and functions are proposed research design, not an implemented runtime.", "in_scope": [ "Business meaning, intended use, aliases and applicability", "Formula operands, parameters, unit and numeric behavior", "Population, input grain, output grain, filter stages and aggregation restrictions", "Time basis, reference bindings, version continuity and acceptance evidence", "Local stewardship and controlled access to definition metadata" ], "out_of_scope": [ "Observation values, dashboards, targets, incentives and decisions using the metric", "Dataset storage, ingestion, transformations, query execution and pipeline scheduling", "Dimension members, hierarchy maintenance and organization-wide semantic model ownership", "Generic policy evaluation, authorization enforcement and audit-trail infrastructure", "Accounting, statistical estimation, clinical or safety-critical metric certification" ], "boundary_notes": [ { "neighbor": "WM-DAT-001 Dataset", "distinction": "The registry parent is a navigation/classification lead, not proven subclass inheritance: a definition is not a dataset. Reference source/output datasets without owning their contents or lifecycle.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-DAT-010 Time Series / Observation Collection", "distinction": "Values and observation histories reference the metric revision. A formula or fixture does not become a production observation collection.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-DAT-014 Dimension and Hierarchy", "distinction": "Select dimension references, levels and version semantics locally; member lists and hierarchy changes remain externally mastered.", "source_refs": [ "SRC-001", "SRC-005" ] }, { "neighbor": "WM-DAT-015 Semantic Model", "distinction": "Carry a metric binding into a larger semantic model. Shared join graphs and query planning remain outside this entity.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "WM-DAT-004 Data Schema / Data Contract; WM-DAT-005 Data Pipeline", "distinction": "Pin expected input fields and evaluator contract references; schema lifecycle, data movement and execution belong to their masters.", "source_refs": [ "SRC-004", "SRC-006" ] }, { "neighbor": "WM-DAT-006 Data Lineage; WM-DAT-007 Data Quality Evaluation", "distinction": "Reference derivation and evaluation evidence. Do not claim to generate operational lineage or conduct a dataset quality assessment.", "source_refs": [ "SRC-002", "SRC-003" ] } ] }, "sources": [ { "id": "SRC-001", "title": "The RDF Data Cube Vocabulary", "organization": "W3C", "url": "https://www.w3.org/TR/2014/REC-vocab-data-cube-20140116/", "version_or_date": "Recommendation, 2014-01-16", "source_type": "standard", "authority_tier": 1, "primary_source": true, "accessed_at": "2026-10-21T17:03:37Z", "relevance": "Sections 5-8 and 11 distinguish dimensions, measures, attributes and observations. Section 8.4 explicitly leaves aggregation operations unspecified." }, { "id": "SRC-002", "title": "Data on the Web Best Practices: Data Quality Vocabulary", "organization": "W3C", "url": "https://www.w3.org/TR/2016/NOTE-vocab-dqv-20161215/", "version_or_date": "Working Group Note, 2016-12-15", "source_type": "ontology", "authority_tier": 2, "primary_source": true, "accessed_at": "2026-10-21T17:03:37Z", "relevance": "Sections 4.1-4.2 distinguish a quality metric from its measurement and expected datatype. This is an analogy for business metrics, not a universal business-metric standard." }, { "id": "SRC-003", "title": "PROV-O: The PROV Ontology", "organization": "W3C", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation, 2013-04-30", "source_type": "ontology", "authority_tier": 1, "primary_source": true, "accessed_at": "2026-10-21T17:03:37Z", "relevance": "Sections 3.1-3.3 support attribution, revision and derivation references; provenance does not establish truth or approval authority." }, { "id": "SRC-004", "title": "Apache Calcite SQL language reference", "organization": "Apache Software Foundation", "url": "https://calcite.apache.org/docs/reference.html", "version_or_date": "Living documentation accessed 2026-10-21; release pin unresolved", "source_type": "first-party-doc", "authority_tier": 2, "primary_source": true, "accessed_at": "2026-10-21T17:03:37Z", "relevance": "Grammar, aggregate functions and window functions expose filter stages, distinctness, null handling and operator differences. Dialect-specific evidence only, not universal SQL conformance." }, { "id": "SRC-005", "title": "SKOS Simple Knowledge Organization System Reference", "organization": "W3C", "url": "https://www.w3.org/TR/skos-reference/", "version_or_date": "Recommendation, 2009-08-18", "source_type": "ontology", "authority_tier": 1, "primary_source": true, "accessed_at": "2026-10-21T17:03:37Z", "relevance": "Sections 5, 7 and 10 support labels, documentation and qualified concept mappings; concept similarity does not prove computational equivalence." }, { "id": "SRC-006", "title": "Shapes Constraint Language (SHACL)", "organization": "W3C", "url": "https://www.w3.org/TR/2017/REC-shacl-20170720/", "version_or_date": "Recommendation, 2017-07-20", "source_type": "standard", "authority_tier": 1, "primary_source": true, "accessed_at": "2026-10-21T17:03:37Z", "relevance": "Sections 2-4 distinguish constraints, data graphs and validation reports. Proposed metadata checks are not a supplied SHACL implementation." }, { "id": "SRC-007", "title": "The International System of Units (SI)", "organization": "BIPM", "url": "https://www.bipm.org/documents/20126/41483022/SI-Brochure-9-EN.pdf/2d2b50bf-f2b4-9661-f402-5f9d66e4b507?download=true&t=1780410776583&version=7.0", "version_or_date": "Ninth edition, 2019; English update listed as 2026; retrieved title version 4.01", "source_type": "standard", "authority_tier": 1, "primary_source": true, "accessed_at": "2026-10-21T17:03:37Z", "relevance": "Sections 2.3.3 and 5.4 distinguish quantities, units, uncertainty and ratios with unit one. Monetary and accounting conventions need separate profiles." }, { "id": "SRC-008", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "authority_tier": 1, "primary_source": true, "accessed_at": "2026-10-21T17:03:37Z", "relevance": "Sections 1 and 5.6 describe timestamp syntax. Business calendars, interval closure and daylight-saving policies are outside this specification." }, { "id": "SRC-009", "title": "ODRL Information Model 2.2", "organization": "W3C", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "Recommendation, 2018-02-15", "source_type": "standard", "authority_tier": 1, "primary_source": true, "accessed_at": "2026-10-21T17:03:37Z", "relevance": "Sections 2.1-2.6 distinguish policies, assets, parties, permissions, prohibitions and duties. Policy references here do not implement enforcement." } ], "structure": { "bundles": [ { "id": "b-meaning", "name": "Meaning and accountability", "description": "Identify the metric and the responsibility for its interpretation.", "rationale": "A reusable calculation needs a stable subject and a declared business meaning.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-009" ], "layers": [ { "id": "l-identity", "name": "Identity and interpretation", "description": "Distinguish the metric identity from names and intended applications.", "source_refs": [ "SRC-002", "SRC-005" ], "findings": [ { "id": "f-identity", "name": "Stable metric identity", "description": "Proposed identity separates an enduring metric from its immutable revisions and localized labels. Identical names do not establish identical semantics.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "q-identity-1", "kind": "identity", "text": "Which master identifier and namespace distinguish this metric from similarly named metrics?", "answer_data": [ "master_system", "metric_id", "namespace", "collision_resolution" ] }, { "id": "q-identity-2", "kind": "lifecycle", "text": "How are immutable revision identifiers associated with the enduring metric identifier?", "answer_data": [ "metric_id", "revision_id", "predecessor_ref", "revision_policy_ref" ] }, { "id": "q-identity-3", "kind": "classification", "text": "Which preferred labels, aliases and concept references describe the metric without merging distinct definitions?", "answer_data": [ "preferred_labels_by_language", "aliases", "concept_refs", "mapping_strength" ] } ], "data_elements": [ { "id": "d-identity-metric-id", "name": "metric id", "description": "Enduring identifier in the declaring master namespace.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "d-identity-revision-id", "name": "revision id", "description": "Immutable semantic revision identifier, distinct from creation time.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "d-identity-labels", "name": "labels", "description": "Preferred and alternate labels with language and namespace context.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "a-identity", "name": "Metric identity record", "description": "Version-bound evidence for stable metric identity. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "f-meaning", "name": "Business meaning and intended use", "description": "Record the measured concept and decision context. DQV provides a metric/measurement distinction for quality metrics only; extension to business metrics is a local design choice.", "source_refs": [ "SRC-002", "SRC-005" ], "questions": [ { "id": "q-meaning-1", "kind": "definition", "text": "What business concept does this metric quantify and what similar concepts does it exclude?", "answer_data": [ "concept_definition", "included_meaning", "excluded_meanings", "examples" ] }, { "id": "q-meaning-2", "kind": "requirement", "text": "For which use cases is this definition suitable and where is use explicitly unsupported?", "answer_data": [ "intended_uses", "unsupported_uses", "profile_refs" ] }, { "id": "q-meaning-3", "kind": "decision", "text": "Where are any targets, desired direction or decision thresholds governed separately from the metric definition?", "answer_data": [ "target_or_policy_refs", "interpretation_notes", "no_target_if_absent" ] } ], "data_elements": [ { "id": "d-meaning-meaning", "name": "meaning", "description": "Human-readable meaning independent of a query expression.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "d-meaning-use-scope", "name": "use scope", "description": "Supported and unsupported uses, with profile references.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "d-meaning-decision-refs", "name": "decision refs", "description": "Optional externally mastered targets or decision policies.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "a-meaning", "name": "Interpretation statement", "description": "Version-bound evidence for business meaning and intended use. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "l-stewardship", "name": "Stewardship and use controls", "description": "Identify responsible roles and metadata disclosure constraints.", "source_refs": [ "SRC-003", "SRC-009" ], "findings": [ { "id": "f-responsibility", "name": "Accountable roles and permitted use", "description": "Assign role references without naming a company as owner. Authorship, approval authority and execution permission remain distinct. Access rules are local proposals interpreted by an external policy service.", "source_refs": [ "SRC-003", "SRC-009" ], "questions": [ { "id": "q-responsibility-1", "kind": "ownership", "text": "Which accountable role maintains the meaning and which technical role maintains implementation bindings?", "answer_data": [ "accountable_role_ref", "technical_steward_ref", "responsibility_scope" ] }, { "id": "q-responsibility-2", "kind": "authority", "text": "What evidence authorizes approval or retirement of a metric revision?", "answer_data": [ "approver_role_ref", "delegation_ref", "approval_evidence_ref", "effective_scope" ] }, { "id": "q-responsibility-3", "kind": "access", "text": "Which audiences may see formulas, source bindings and examples, and what disclosure exceptions apply?", "answer_data": [ "metadata_classification", "policy_refs", "audience_scopes", "redacted_view_rules", "exception_approver" ] } ], "data_elements": [ { "id": "d-responsibility-responsibilities", "name": "responsibilities", "description": "Role references and scoped responsibilities.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003", "SRC-009" ] }, { "id": "d-responsibility-authority-ref", "name": "authority ref", "description": "Reference to authority evidence, not a permission inferred from attribution.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-009" ] }, { "id": "d-responsibility-access-policy", "name": "access policy", "description": "Pinned access and permitted-use policy reference.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-009" ] } ], "artifacts": [ { "id": "a-responsibility", "name": "Stewardship and access declaration", "description": "Version-bound evidence for accountable roles and permitted use. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-003", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-computation", "name": "Computation contract", "description": "Specify the intended transformation without executing it.", "rationale": "Expression text alone cannot resolve dependencies or exceptional numeric behavior.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ], "layers": [ { "id": "l-expression", "name": "Expression and parameters", "description": "Define operands, ordering and admissible parameter variation.", "source_refs": [ "SRC-002", "SRC-004" ], "findings": [ { "id": "f-formula", "name": "Formula and operand roles", "description": "The proposed formula contract includes operator order and distinct numerator/denominator roles where applicable. A source expression is inert metadata; untrusted text is never executed during registration.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "q-formula-1", "kind": "definition", "text": "What expression and language/version define the metric, including numerator and denominator when relevant?", "answer_data": [ "expression", "language_ref", "language_version", "operand_roles", "expression_digest" ] }, { "id": "q-formula-2", "kind": "composition", "text": "Which input measures or other metric revisions supply each operand, and how are dependency cycles rejected?", "answer_data": [ "operand_bindings", "dependency_revision_refs", "cycle_check_evidence" ] }, { "id": "q-formula-3", "kind": "process", "text": "In what order do row-level derivation, filtering, aggregation and final arithmetic occur?", "answer_data": [ "ordered_semantic_stages", "precedence", "stage_inputs_outputs" ] } ], "data_elements": [ { "id": "d-formula-expression", "name": "expression", "description": "Declared expression with language and revision pin; not executable permission.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "d-formula-operands", "name": "operands", "description": "Named operands and exact dependency bindings.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "d-formula-stage-order", "name": "stage order", "description": "Ordered semantics distinguishing pre-aggregation from post-aggregation arithmetic.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "a-formula", "name": "Formula contract", "description": "Version-bound evidence for formula and operand roles. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "f-parameters", "name": "Parameter contract", "description": "Separate a metric family parameter from a changed definition. Record defaults and allowed domains explicitly, with rejection for missing required values or unauthorized overrides.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "questions": [ { "id": "q-parameters-1", "kind": "constraint", "text": "Which parameters are permitted and what type, unit, range or code set constrains each one?", "answer_data": [ "parameter_names", "types", "units", "domains", "required_flags" ] }, { "id": "q-parameters-2", "kind": "exception", "text": "What happens when a parameter is absent, invalid or attempts to override a fixed semantic choice?", "answer_data": [ "defaults", "invalid_value_result", "override_policy", "refusal_reason" ] }, { "id": "q-parameters-3", "kind": "identity", "text": "Which parameter changes preserve this revision and which require a new metric or revision?", "answer_data": [ "identity_affecting_parameters", "revision_rules", "parameterization_examples" ] } ], "data_elements": [ { "id": "d-parameters-parameters", "name": "parameters", "description": "Explicit parameter inventory; an empty inventory means no parameters.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "d-parameters-default-rules", "name": "default rules", "description": "Defaults and distinction between omitted, null and explicit values.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "d-parameters-change-boundary", "name": "change boundary", "description": "Parameter variations that cross the semantic identity boundary.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "a-parameters", "name": "Parameter specification", "description": "Version-bound evidence for parameter contract. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "l-value", "name": "Value semantics", "description": "Declare units, numeric representation and abnormal results.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ], "findings": [ { "id": "f-numeric", "name": "Units, precision and exceptional values", "description": "Record quantity meaning separately from presentation scale. Ratios, percentages and counts need explicit interpretation; monetary conventions are profile dependencies, not SI rules.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-numeric-1", "kind": "measurement", "text": "What quantity, unit, scale and output datatype define the result before display formatting?", "answer_data": [ "quantity_kind", "unit_ref", "scale_factor", "datatype", "currency_profile_ref_if_applicable" ] }, { "id": "q-numeric-2", "kind": "quality", "text": "Which precision, rounding stage and approximation or uncertainty declarations apply?", "answer_data": [ "precision", "rounding_mode", "rounding_stage", "exact_or_approximate", "uncertainty_method_ref" ] }, { "id": "q-numeric-3", "kind": "exception", "text": "How are empty input, missing operands, zero denominators, overflow and nonfinite values represented?", "answer_data": [ "condition_result_table", "null_semantics", "undefined_status", "error_policy" ] } ], "data_elements": [ { "id": "d-numeric-quantity", "name": "quantity", "description": "Quantity meaning, unit, scale and output datatype.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ] }, { "id": "d-numeric-precision", "name": "precision", "description": "Precision and approximation policy including explicit not-applicable values.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ] }, { "id": "d-numeric-exceptions", "name": "exceptions", "description": "Condition-to-result/status rules; do not silently turn unknown into zero.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "a-numeric", "name": "Numeric interpretation contract", "description": "Version-bound evidence for units, precision and exceptional values. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-population", "name": "Population and grain", "description": "Define which entities and records can contribute to a value.", "rationale": "Population, grain and filter scope can change a metric even when its label and formula are unchanged.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "layers": [ { "id": "l-grain", "name": "Input and output grain", "description": "Record the counted entity and the grouping coordinates.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "f-population", "name": "Population and counting unit", "description": "A business population is a definition-level eligibility rule. No actual subject records are stored here. Deduplication choices must not be mistaken for source-data repair.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "q-population-1", "kind": "definition", "text": "What entity or event is counted and what eligibility rule defines the population?", "answer_data": [ "counting_unit", "population_rule", "eligibility_basis", "excluded_categories" ] }, { "id": "q-population-2", "kind": "identity", "text": "Which key distinguishes contributions and how are repeats, reversals or duplicate events treated?", "answer_data": [ "contribution_key", "deduplication_rule", "reversal_rule", "event_identity_ref" ] }, { "id": "q-population-3", "kind": "quality", "text": "What evidence distinguishes an absent contribution from an unobserved or excluded one?", "answer_data": [ "coverage_indicator_contract", "missingness_status", "exclusion_reason_contract" ] } ], "data_elements": [ { "id": "d-population-population-rule", "name": "population rule", "description": "Versioned eligibility definition independent of actual data rows.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "d-population-counting-unit", "name": "counting unit", "description": "Entity/event type and contribution identity.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "d-population-repeat-rules", "name": "repeat rules", "description": "Duplicate, reversal and repeated-event interpretation rules.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "a-population", "name": "Population contract", "description": "Version-bound evidence for population and counting unit. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "f-grain", "name": "Grain and dimension bindings", "description": "Input grain and result grain are separate. Local dimension bindings do not own hierarchy members. Join multiplicity must be documented before a metric binding is accepted.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "questions": [ { "id": "q-grain-1", "kind": "composition", "text": "What input grain and output grouping key determine one result cell?", "answer_data": [ "input_grain", "output_grain", "coordinate_keys", "uniqueness_requirement" ] }, { "id": "q-grain-2", "kind": "relationship", "text": "Which dimension levels and hierarchy revisions may be used for slicing or rollup?", "answer_data": [ "dimension_refs", "level_refs", "hierarchy_revision_refs", "allowed_paths" ] }, { "id": "q-grain-3", "kind": "validation", "text": "How does the binding prevent join fan-out, missing-key loss or accidental many-to-many multiplication?", "answer_data": [ "join_contract_ref", "cardinality_expectations", "unmatched_key_policy", "fanout_fixture_refs" ] } ], "data_elements": [ { "id": "d-grain-grain", "name": "grain", "description": "Input contribution grain and output cell coordinates.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "d-grain-dimension-bindings", "name": "dimension bindings", "description": "Pinned dimension and level references; no copied member masters.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "d-grain-join-assumptions", "name": "join assumptions", "description": "Cardinality and key assumptions of external semantic bindings.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "a-grain", "name": "Grain and binding record", "description": "Version-bound evidence for grain and dimension bindings. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "l-selection", "name": "Selection semantics", "description": "Make fixed predicates and optional slices explicit.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "f-filters", "name": "Filters and evaluation stage", "description": "Proposed filter metadata distinguishes population eligibility, pre-aggregation filters, post-aggregation tests and user slices. Access enforcement may restrict visible data but cannot silently redefine a metric.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ], "questions": [ { "id": "q-filters-1", "kind": "constraint", "text": "Which predicates are fixed and which may consumers supply as slices?", "answer_data": [ "fixed_predicates", "allowed_slice_dimensions", "override_constraints" ] }, { "id": "q-filters-2", "kind": "process", "text": "At which stage is each predicate applied and how do null or unknown predicate values behave?", "answer_data": [ "predicate_stage", "three_valued_logic_policy", "null_inclusion_rule" ] }, { "id": "q-filters-3", "kind": "privacy", "text": "How are access-based data restrictions or suppression disclosed so differently authorized results are not presented as equivalent?", "answer_data": [ "policy_binding_ref", "visibility_scope_marker", "suppression_status_contract", "comparison_limits" ] } ], "data_elements": [ { "id": "d-filters-predicates", "name": "predicates", "description": "Typed predicates with stage and fixed/variable status.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] }, { "id": "d-filters-unknown-rules", "name": "unknown rules", "description": "Explicit treatment of unknown predicate values.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] }, { "id": "d-filters-restricted-view", "name": "restricted view", "description": "Required scope and suppression metadata in separately produced results.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] } ], "artifacts": [ { "id": "a-filters", "name": "Selection specification", "description": "Version-bound evidence for filters and evaluation stage. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-time-rollup", "name": "Time and aggregation", "description": "State temporal interpretation and safe combination rules.", "rationale": "Timestamp syntax and dimension labels do not define valid business aggregation.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-008" ], "layers": [ { "id": "l-time", "name": "Temporal basis", "description": "Separate the time being measured from collection and revision times.", "source_refs": [ "SRC-004", "SRC-008" ], "findings": [ { "id": "f-window", "name": "Time basis and windows", "description": "A metric declares which time field governs inclusion and the calendar/window semantics required of its evaluator. RFC 3339 encodes instants, not business calendar policy.", "source_refs": [ "SRC-004", "SRC-008" ], "questions": [ { "id": "q-window-1", "kind": "temporal", "text": "Which event, effective, snapshot or ingestion time determines membership in the measurement period?", "answer_data": [ "time_basis", "time_field_ref", "fallback_rule", "time_basis_rationale" ] }, { "id": "q-window-2", "kind": "temporal", "text": "What calendar, time zone, interval boundaries and window anchor define a period?", "answer_data": [ "calendar_ref", "zone_rules_ref", "start_end_inclusivity", "window_type", "anchor", "daylight_saving_rule" ] }, { "id": "q-window-3", "kind": "exception", "text": "How are incomplete periods, ambiguous local times and events exactly on a boundary handled?", "answer_data": [ "partial_period_rule", "ambiguity_rule", "boundary_examples", "refusal_conditions" ] } ], "data_elements": [ { "id": "d-window-time-basis", "name": "time basis", "description": "Reference to the intended time field and fallback prohibition or rule.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] }, { "id": "d-window-window", "name": "window", "description": "Calendar and interval/window contract, or explicit timeless applicability.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] }, { "id": "d-window-boundary-rules", "name": "boundary rules", "description": "Boundary and incomplete-period interpretation examples.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "a-window", "name": "Temporal interpretation record", "description": "Version-bound evidence for time basis and windows. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "f-restatement", "name": "Late data and restatement semantics", "description": "Declare how consumers should distinguish original-as-reported and restated results. Runtime ingestion, recalculation and publication of values remain external responsibilities.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "questions": [ { "id": "q-restatement-1", "kind": "temporal", "text": "What cutoff, lateness allowance and snapshot reference define an as-reported result?", "answer_data": [ "cutoff_contract", "lateness_rule", "snapshot_ref_requirement", "recorded_time_requirement" ] }, { "id": "q-restatement-2", "kind": "lifecycle", "text": "Which late-data or correction cases permit restatement, and how is the original result distinguished?", "answer_data": [ "restatement_policy_ref", "trigger_classes", "original_result_ref_requirement", "restatement_status" ] }, { "id": "q-restatement-3", "kind": "provenance", "text": "Which definition revision and data snapshot must accompany a reproduced historical result?", "answer_data": [ "metric_revision_ref", "input_snapshot_refs", "evaluator_version_ref", "reproduction_limits" ] } ], "data_elements": [ { "id": "d-restatement-cutoff", "name": "cutoff", "description": "Definition-level cutoff and late-arrival policy.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "d-restatement-restatement", "name": "restatement", "description": "Correction semantics with external execution responsibility.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "d-restatement-reproduction-contract", "name": "reproduction contract", "description": "Required provenance references for historical reproduction.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "a-restatement", "name": "Restatement policy binding", "description": "Version-bound evidence for late data and restatement semantics. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "l-rollup", "name": "Permitted aggregation", "description": "Define where values can be combined and where recomputation is required.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "findings": [ { "id": "f-aggregation", "name": "Aggregation and comparability", "description": "Data Cube deliberately does not define aggregation operators. This proposal requires a per-axis rule and evidence for combining values, including ratios, distinct counts and snapshot measures.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-aggregation-1", "kind": "measurement", "text": "Across which axes is the metric additive, conditionally additive or non-additive?", "answer_data": [ "axis_rules", "combination_operator", "preconditions", "forbidden_rollups" ] }, { "id": "q-aggregation-2", "kind": "process", "text": "When must a total be recomputed from components instead of summing or averaging displayed values?", "answer_data": [ "recomputation_formula", "required_components", "weighting_rule", "distinct_overlap_rule" ] }, { "id": "q-aggregation-3", "kind": "validation", "text": "What prevents comparison across incompatible units, periods, population scopes or definition revisions?", "answer_data": [ "comparability_dimensions", "compatibility_evidence_refs", "incompatibility_result" ] } ], "data_elements": [ { "id": "d-aggregation-axis-rules", "name": "axis rules", "description": "Allowed operator and conditions for each aggregation axis.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "d-aggregation-component-contract", "name": "component contract", "description": "Sufficient component requirements for lawful semantic recombination.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "d-aggregation-comparability", "name": "comparability", "description": "Required agreements before comparing or combining values.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "a-aggregation", "name": "Aggregation contract", "description": "Version-bound evidence for aggregation and comparability. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-dependencies", "name": "Dependencies and exchange", "description": "Pin external semantic inputs and disclose translation losses.", "rationale": "A metric may have many bindings while retaining one controlled meaning.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "l-bindings", "name": "Source and implementation bindings", "description": "Record references required for reproducible interpretation.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "f-sources", "name": "Source field and lineage references", "description": "Define logical inputs and evidence references without copying datasets or owning lineage collection. A derivation link records a claim; it does not prove data correctness.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "q-sources-1", "kind": "relationship", "text": "Which dataset and schema revisions supply the required logical input fields?", "answer_data": [ "dataset_refs", "schema_revision_refs", "field_paths", "expected_types" ] }, { "id": "q-sources-2", "kind": "provenance", "text": "What evidence links each operand to its source or derived dependency?", "answer_data": [ "operand_to_source_map", "lineage_record_refs", "derivation_claim_status" ] }, { "id": "q-sources-3", "kind": "exception", "text": "What happens when a dependency is unavailable, changes type or loses its required version pin?", "answer_data": [ "binding_status", "breaking_change_conditions", "refusal_or_review_rule" ] } ], "data_elements": [ { "id": "d-sources-input-bindings", "name": "input bindings", "description": "Logical field paths, types and revision-pinned external contracts.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "d-sources-lineage-refs", "name": "lineage refs", "description": "Externally mastered lineage records associated with operands.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "d-sources-dependency-status", "name": "dependency status", "description": "Resolved, unresolved or incompatible status with reason.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "a-sources", "name": "Dependency binding record", "description": "Version-bound evidence for source field and lineage references. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "f-implementations", "name": "Implementation equivalence claims", "description": "Keep executable representations separate from the semantic definition. Syntax acceptance or a shared metric name is insufficient evidence of equivalent results.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "q-implementations-1", "kind": "interoperability", "text": "Which evaluator, language version and implementation digest are bound to this revision?", "answer_data": [ "evaluator_contract_ref", "language_profile", "implementation_digest", "binding_id" ] }, { "id": "q-implementations-2", "kind": "evidence", "text": "What fixture evidence supports equivalent behavior for each implementation binding?", "answer_data": [ "fixture_suite_ref", "execution_report_ref", "binding_revision", "pass_fail_unknown" ] }, { "id": "q-implementations-3", "kind": "constraint", "text": "Which unsupported operators or semantic differences prohibit a binding from being treated as equivalent?", "answer_data": [ "unsupported_features", "numeric_differences", "window_differences", "equivalence_limitations" ] } ], "data_elements": [ { "id": "d-implementations-implementation-refs", "name": "implementation refs", "description": "Candidate implementation records, not executable payload authority.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "d-implementations-equivalence-evidence", "name": "equivalence evidence", "description": "Evidence references and scope of a compatibility claim.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "d-implementations-binding-limitations", "name": "binding limitations", "description": "Known translation or evaluator mismatches.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "a-implementations", "name": "Implementation compatibility statement", "description": "Version-bound evidence for implementation equivalence claims. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "l-exchange", "name": "Mappings and projections", "description": "Expose conceptual alignment and preservation limits.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ], "findings": [ { "id": "f-mapping", "name": "Semantic mappings and loss disclosure", "description": "Map only compatible concepts. A quality-metric profile may align to DQV; general business metrics are not automatically instances of that vocabulary. No serialization is the definition itself.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-mapping-1", "kind": "interoperability", "text": "Which external concept or specification term is mapped, and what is the exact scope of the mapping?", "answer_data": [ "target_term", "mapping_relation", "profile_scope", "mapping_evidence" ] }, { "id": "q-mapping-2", "kind": "quality", "text": "Which formula, grain, time or policy semantics are lost in each export projection?", "answer_data": [ "projection_ref", "preserved_fields", "lost_semantics", "loss_warning" ] }, { "id": "q-mapping-3", "kind": "validation", "text": "What round-trip evidence shows that import and export preserve the declared revision semantics?", "answer_data": [ "round_trip_fixture_ref", "comparison_report_ref", "unsupported_fields", "acceptance_decision" ] } ], "data_elements": [ { "id": "d-mapping-mappings", "name": "mappings", "description": "Qualified term mappings without universal equivalence assertions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "d-mapping-projection-losses", "name": "projection losses", "description": "Per-projection preservation and loss declaration.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "d-mapping-round-trip-evidence", "name": "round trip evidence", "description": "Optional externally produced mapping validation reports.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "a-mapping", "name": "Alignment and projection record", "description": "Version-bound evidence for semantic mappings and loss disclosure. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-assurance", "name": "Revision and assurance", "description": "Govern revision continuity and the evidence needed for acceptance.", "rationale": "A structurally complete definition remains unproven until its intended behavior is tested under an adopting profile.", "source_refs": [ "SRC-003", "SRC-006", "SRC-009" ], "layers": [ { "id": "l-revision", "name": "Revision and disposition", "description": "Describe local release and retirement rules.", "source_refs": [ "SRC-003", "SRC-008", "SRC-009" ], "findings": [ { "id": "f-revision", "name": "Semantic revision and approval", "description": "Proposed states are draft, in-review, approved, deprecated and retired. Approval is a scoped local decision; it is neither canonical research status nor proof of runtime correctness.", "source_refs": [ "SRC-003", "SRC-006", "SRC-009" ], "questions": [ { "id": "q-revision-1", "kind": "state", "text": "What is the current revision state and which evidence permits the next transition?", "answer_data": [ "state", "transition_rule", "approval_ref", "blocking_issues" ] }, { "id": "q-revision-2", "kind": "lifecycle", "text": "Which changes to formula, grain, filters, units or time basis require a breaking revision or a new metric identity?", "answer_data": [ "change_classification", "compatibility_decision", "successor_ref", "migration_note" ] }, { "id": "q-revision-3", "kind": "temporal", "text": "When does a revision apply and how are overlapping applicability intervals or historical corrections resolved?", "answer_data": [ "effective_interval", "recorded_at", "precedence_policy", "overlap_resolution" ] } ], "data_elements": [ { "id": "d-revision-revision-state", "name": "revision state", "description": "Local definition state with evidence; not publication research assurance.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-009" ] }, { "id": "d-revision-change-assessment", "name": "change assessment", "description": "Semantic impact and identity continuity decision.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-009" ] }, { "id": "d-revision-applicability", "name": "applicability", "description": "Effective interval and recording time kept distinct.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "a-revision", "name": "Revision decision record", "description": "Version-bound evidence for semantic revision and approval. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-003", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "f-retirement", "name": "Retirement and retained interpretability", "description": "Retiring a definition does not erase existing observations. Retention follows the adopting policy, with controlled evidence disposal and minimal tombstones where permitted; no indefinite personal-data retention is implied.", "source_refs": [ "SRC-003", "SRC-009" ], "questions": [ { "id": "q-retirement-1", "kind": "retention", "text": "Which policy controls retention or deletion of definitions, approvals and sensitive examples?", "answer_data": [ "retention_policy_ref", "record_categories", "hold_refs", "disposal_authority_ref" ] }, { "id": "q-retirement-2", "kind": "relationship", "text": "Which consumers and observations depend on the retired revision and how are replacement references disclosed?", "answer_data": [ "consumer_ref_inventory", "successor_ref", "dependency_impact", "notification_record_ref" ] }, { "id": "q-retirement-3", "kind": "privacy", "text": "What minimal reference remains after authorized disposal, without retaining restricted payloads?", "answer_data": [ "tombstone_fields", "redaction_rule", "payload_deletion_evidence_ref", "unresolvable_reason" ] } ], "data_elements": [ { "id": "d-retirement-disposition-policy", "name": "disposition policy", "description": "Policy reference governing local record disposal.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-009" ] }, { "id": "d-retirement-dependency-impact", "name": "dependency impact", "description": "Reference-level impact assessment; no deletion of external records.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-009" ] }, { "id": "d-retirement-tombstone-contract", "name": "tombstone contract", "description": "Minimal continuity metadata and permitted erasure rules.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-009" ] } ], "artifacts": [ { "id": "a-retirement", "name": "Retirement and disposition record", "description": "Version-bound evidence for retirement and retained interpretability. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-003", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "l-acceptance", "name": "Acceptance evidence", "description": "Specify discriminating examples and honest validation status.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "findings": [ { "id": "f-fixtures", "name": "Semantic acceptance fixtures", "description": "Propose fixture expectations for metric bindings, not a new evaluator. Metadata schema success, fixture success and domain fitness are separate claims. No execution reports are supplied by this research.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-fixtures-1", "kind": "validation", "text": "Which positive and negative fixtures test the declared metric semantics?", "answer_data": [ "fixture_refs", "inputs", "expected_values_or_statuses", "boundary_case_inventory" ] }, { "id": "q-fixtures-2", "kind": "measurement", "text": "What expected results and tolerances distinguish weighted ratios, duplicate contributions and time-boundary cases?", "answer_data": [ "expected_components", "expected_result", "tolerance_basis", "comparison_rule" ] }, { "id": "q-fixtures-3", "kind": "evidence", "text": "Which evidence supports acceptance and which untested cases remain explicitly unknown?", "answer_data": [ "report_refs", "tested_binding_version", "acceptance_scope", "untested_cases", "reviewer_role_ref" ] } ], "data_elements": [ { "id": "d-fixtures-fixture-contract", "name": "fixture contract", "description": "Fixture inventory with expected behavior and coverage gaps.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "d-fixtures-tolerance", "name": "tolerance", "description": "Exact comparison or justified tolerance rules.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "d-fixtures-acceptance-evidence", "name": "acceptance evidence", "description": "Evidence references with separate metadata, behavior and fitness status.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "a-fixtures", "name": "Acceptance fixture specification", "description": "Version-bound evidence for semantic acceptance fixtures. Candidate artifact; no completed instance or runtime is claimed.", "media_or_form": [ "Structured record", "Human-readable review note" ], "serial": true, "identity_strategy": "Use the authoritative artifact master ID; otherwise governed IRI, otherwise assigned UUID/ULID. Bind metric ID and revision. Keep digest separate from identity and timestamps separate from names.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "fn-register", "name": "Register definition draft", "description": "Proposed local operation, not implemented: reserve an identity and record a draft contract without executing an expression.", "inputs": [ "Master namespace", "Identity and meaning", "Role authorization" ], "outputs": [ "Draft revision reference or collision/refusal report" ], "preconditions": [ "Authorized steward", "Namespace resolved", "No implicit dataset inheritance" ], "effects": [ "Create only local definition metadata", "Preserve unresolved fields as unknown" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "fn-inspect", "name": "Inspect semantic contract", "description": "Proposed local operation, not implemented: report missing or contradictory formula, grain, time and value declarations.", "inputs": [ "Pinned revision", "Declared profile", "Dependency metadata" ], "outputs": [ "Issue list with pass/fail/unknown per check" ], "preconditions": [ "Read authority", "Profile version available" ], "effects": [ "Produce a local inspection report", "Never infer business correctness from schema success" ], "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "fn-bind", "name": "Record implementation binding", "description": "Proposed local operation, not implemented: attach externally supplied implementation and evidence references.", "inputs": [ "Metric revision", "Implementation contract reference", "Fixture report reference" ], "outputs": [ "Binding record or incompatibility/refusal report" ], "preconditions": [ "Authorized technical steward", "Dependency pins resolved", "Expected current revision matches" ], "effects": [ "Record bounded equivalence claim", "Do not run queries, fetch production data or deploy an evaluator" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "fn-assess-change", "name": "Assess proposed semantic change", "description": "Proposed local operation, not implemented: compare explicit contracts and prepare a compatibility recommendation.", "inputs": [ "Prior revision", "Candidate revision", "Consumer reference inventory" ], "outputs": [ "Change assessment with unresolved impacts" ], "preconditions": [ "Both revisions readable", "Comparison profile pinned" ], "effects": [ "Classify changed meaning, formula, grain, units, filters and time basis", "No automatic consumer migration" ], "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "fn-approve", "name": "Record revision approval", "description": "Proposed local operation, not implemented: record an authorized decision and applicability interval.", "inputs": [ "Candidate revision", "Approval evidence reference", "Applicability interval" ], "outputs": [ "Approved revision reference or refusal" ], "preconditions": [ "Authorized approver", "Required semantic fields resolved", "No unresolved blocking issue", "Concurrency token matches" ], "effects": [ "Freeze semantic content and approval reference", "Do not certify values or change external runtime access" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-009" ] }, { "id": "fn-retire", "name": "Retire definition revision", "description": "Proposed local operation, not implemented: mark a revision unavailable for new bindings while preserving policy-permitted interpretation references.", "inputs": [ "Revision reference", "Authority evidence", "Disposition policy", "Successor reference if any" ], "outputs": [ "Retirement record or dependency/refusal report" ], "preconditions": [ "Authorized steward", "Consumer impact reviewed", "Retention and holds checked" ], "effects": [ "Change only local revision state", "Delegate payload deletion to the record custodian under explicit policy; never delete source datasets or observations" ], "source_refs": [ "SRC-003", "SRC-009" ] } ], "composition": [ { "target": "WM-DAT-001", "relation": "REFERENCE", "purpose": "Candidate registry-parent reconciliation: source/output dataset reference, not inheritance or containment.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-DAT-004", "relation": "REFERENCE", "purpose": "Candidate binding to input schema and field contracts; target owns schema lifecycle.", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "target": "WM-DAT-005", "relation": "REFERENCE", "purpose": "Candidate reference to an implementation pipeline; target owns execution and scheduling.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "WM-DAT-006", "relation": "REFERENCE", "purpose": "Candidate reference to derivation evidence; target owns lineage graph maintenance.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "WM-DAT-007", "relation": "REFERENCE", "purpose": "Candidate reference to independent quality evaluations; target owns assessment execution.", "required": false, "source_refs": [ "SRC-002", "SRC-006" ] }, { "target": "WM-DAT-010", "relation": "REFERENCE", "purpose": "Candidate link to values or observation collections governed elsewhere.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-DAT-014", "relation": "REFERENCE", "purpose": "Candidate binding to dimension levels and hierarchy revisions; no member ownership.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "WM-DAT-015", "relation": "REFERENCE", "purpose": "Candidate reference to semantic context and shared join contracts; no query planner ownership.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "W3C RDF Data Cube", "relation": "ALIGN", "purpose": "Conceptual dimension/measure/observation alignment; no aggregation-language conformance asserted.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "W3C DQV", "relation": "ALIGN", "purpose": "Only a qualified data-quality metric profile may map to dqv:Metric.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "W3C PROV-O", "relation": "ALIGN", "purpose": "Revision, attribution and derivation evidence alignment only.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "W3C SHACL", "relation": "ALIGN", "purpose": "Candidate constraint/report mapping; no executable shapes delivered.", "required": false, "source_refs": [ "SRC-006" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare an adopting Dimension and accountable metric-steward role without commercial owner names.", "Pin metric identity, revision, namespace and semantic profile.", "Declare storage, interface and process bindings separately from metric semantics.", "Bind authorization, retention and disclosure policies; no policy inference from authorship." ], "namespace_guidance": "Use a governed namespace for metric identities and immutable revision IDs; local extensions must declare their owner role and compatibility impact.", "registry_links": [ "vr.wm-dat-013", "WM-DAT-001 parent is classification only pending reconciliation", "Candidate neighbor bindings require separate acceptance and version pins" ] }, "canon_and_patch": { "canonicalization_rules": [ "Within an adopting package, distinguish stable metric identity from immutable revision identity. This does not make the research canonical.", "Preserve expression language, operator order, units, parameter types and time rules; normalize display whitespace only when semantics are proven unchanged.", "Separate formula metadata from executable artifacts and preserve source IDs." ], "patch_rules": [ "Require expected revision and authorized role; reject stale concurrent writes.", "Record reason, changed paths and evidence; never rewrite an approved semantic revision in place.", "Semantic changes create a new revision or identity with an explicit continuity decision." ], "compatibility_rules": [ "A label change alone is not computational equivalence evidence.", "Treat changes to formula, population, grain, filters, numeric behavior, time basis and aggregation as potentially breaking.", "No automatic rebinding to latest dependencies; unresolved or untested mappings remain unknown." ] }, "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 instants. Keep event/effective time separate from observation or ingestion time. Calendar periods and intervals carry their own calendar, zone, closure and granularity rules; never invent an instant for a date-only value.", "serial_naming_rule": "Use metric ID, immutable revision ID, artifact role and assigned artifact ID. Sequence or time may order records but cannot supply identity.", "integrity_rule": "Retain digest, media type, issuer role, provenance and revision binding. A matching digest establishes byte consistency only, not authenticity, truth or semantic equivalence." }, "policies": [ "All hierarchy nodes and functions are proposed local design informed by sources; none asserts a universal business-metric standard.", "External policy services govern access and disclosure; this definition records policy references and required result-scope markers.", "Do not store production personal data, credentials or unrestricted executable expressions in examples. Use minimal synthetic fixtures.", "Keep the research reviewable-draft with independent-review and source-verification holds visible.", "For consequential uses, require an independently reviewed domain profile; this model does not authorize individual decisions." ], "crud": { "read": [ "Resolve exact revision and permitted view; disclose unknown or restricted bindings." ], "create": [ "Reserve master identity, check collisions and initialize a draft with declared unknowns." ], "update": [ "Require authority and expected revision; preserve prior approved semantics and attach compatibility evidence." ], "delete": [ "Prefer retirement with policy-permitted reference continuity.", "Apply the adopting Dimension retention policy and legal holds to local definitions, approvals and fixtures; authorized custodians execute payload deletion and record minimal lawful tombstones.", "Do not cascade deletion to referenced datasets, dimensions, pipelines or observation collections." ] }, "roles": [ { "name": "Metric steward", "responsibilities": [ "Maintain meaning, population and semantic change proposals." ] }, { "name": "Technical steward", "responsibilities": [ "Maintain dependency and evaluator contract references without claiming business approval." ] }, { "name": "Metric approver", "responsibilities": [ "Accept or reject scoped revisions using delegated authority and evidence." ] }, { "name": "Evidence reviewer", "responsibilities": [ "Review fixture coverage, provenance and compatibility limitations." ] }, { "name": "Record custodian", "responsibilities": [ "Apply retention, access restrictions and authorized disposal policy." ] }, { "name": "Consumer", "responsibilities": [ "Resolve exact revision and report incompatible or ambiguous interpretation." ] } ], "access": { "default_rule": "Deny access unless the adopting policy grants the requested view or action; publication of a definition grants no access to its data sources.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Public metadata requires an explicit policy decision; redact sensitive formulas or source bindings as needed.", "A time-limited exception needs authority, scope, expiry and an evidence reference; no self-approval by an automated consumer." ], "audit_requirements": [ "Reference externally maintained audit records for approvals, changes, access exceptions and disposal.", "Record actor role, purpose, target revision, timestamp and outcome without retaining secrets or unnecessary payloads." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read AGENTS.md and adopting Dimension policy.", "Read the pinned specification and exact metric revision, including holds.", "Resolve dependency, authority and access references.", "Inspect declared fixture coverage and unknowns before any authorized local mutation." ] } }, "coverage": { "claim": "Source-grounded proposed structure for one governed metric definition with stable identity and immutable semantic revisions. A separate frozen local no-tools self-audit found no critical contradiction. Independent review, source verification, adopting profiles and executable conformance remain open. This is a reviewable draft, not a universal business-metric standard or implemented evaluator.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable metric and revision identity with namespace and alias rules." }, { "dimension": "lifecycle", "status": "covered", "notes": "Proposed local review, approval, deprecation and retirement states." }, { "dimension": "relationships", "status": "covered", "notes": "Eight candidate neighbor references; no recorded relation-ledger edges for this model." }, { "dimension": "temporal", "status": "covered", "notes": "Time basis, windows, applicability and restatement contracts; no calendar implementation." }, { "dimension": "provenance", "status": "covered", "notes": "Source, derivation, approval and fixture evidence references." }, { "dimension": "ownership", "status": "covered", "notes": "Role accountability and external master boundaries; attribution is not authority." }, { "dimension": "validation", "status": "gap", "notes": "Research structure validated separately; instance schemas and executed metric fixtures are absent." }, { "dimension": "access", "status": "covered", "notes": "Metadata scopes, restricted result markers and policy references; enforcement delegated." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Local disposition rules, dependency protection and minimal tombstones under policy." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual mappings only; version-pinned adapters and round-trip results not supplied." }, { "dimension": "formula and grain", "status": "covered", "notes": "Operand roles, stage order, population, dimensions and join multiplicity assumptions." }, { "dimension": "units and aggregation", "status": "covered", "notes": "Quantity and representation rules with per-axis combination restrictions." }, { "dimension": "physical properties", "status": "not-applicable", "notes": "The definition is an information entity; physical units concern its declared output, not the root object." }, { "dimension": "regional profiles", "status": "gap", "notes": "Business calendar, currency, accounting and regulated-use semantics need profile review." } ], "known_omissions": [ "Independent second-provider review is absent under the owner-authorized waiver.", "Direct HTTP checks are not run because the owner reports the sandbox blocks them; response status and content hashes remain unmeasured.", "Release pin for living Apache Calcite documentation and independent verification of source versions/errata remain open.", "Nested instance schemas, evaluator adapters, executed fixtures and round-trip evidence are not delivered.", "Domain-specific accounting, estimation, sampling, exchange-rate, confidentiality and calendar profiles need separate review.", "The registry parent relationship and candidate neighbor bindings need coordinator reconciliation; no shared registry edits are made." ], "conflicts": [], "regional_assumptions": [ "No jurisdiction, accounting framework, currency or business calendar is a default.", "SI conventions support physical quantity representation; they do not define business concepts or monetary conversion.", "Access, retention and disclosure requirements come from the adopting policies and applicable profiles." ], "adversarial_checks": [ "Reject treating a metric definition as a dataset or a collection of measured values.", "Challenge averaging ratios, summing distinct counts, snapshot rollups and many-to-many fan-out.", "Challenge null-to-zero replacement, zero denominator, rounding before aggregation and undefined precision.", "Challenge window closure, daylight-saving ambiguity, late-data revisions and unpinned historical definitions.", "Challenge name-based equivalence, arbitrary expression execution and approval inferred from authorship.", "Challenge visibility-induced population changes and indefinite retention of sensitive fixtures." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The root is a persistent governed definition, with immutable revisions specifying interpretation. It is neither an observation collection nor a dataset. The registry standalone-mm value classifies the record plane, while its Dataset parent is reconciled as a classification lead and candidate reference rather than subtype inheritance." }, "decisions": [ { "concept": "Definition identity and revisions", "disposition": "accepted", "rationale": "Stable metric identity and immutable revision identity support an entity boundary without conflating labels, observations or expression artifacts with the root." }, { "concept": "Dataset parent inheritance", "disposition": "rejected as subtype inference", "rationale": "The registry parent does not establish that a definition is a dataset. The result preserves a candidate Dataset reference and records coordinator reconciliation without editing shared state." }, { "concept": "Neighbor ownership and optional bindings", "disposition": "qualified", "rationale": "All eight neighbor links are proposed references. Unbound drafts are possible, but approval requires applicable dependencies and semantic fields to be resolved. Target lifecycles and execution remain external." }, { "concept": "DQV and Data Cube applicability", "disposition": "limited", "rationale": "DQV concerns data-quality metrics and Data Cube does not define aggregation operations. The business hierarchy and aggregation contracts are explicit local design proposals, not universal normative claims." }, { "concept": "Formula and parameter contracts", "disposition": "accepted", "rationale": "Operand roles, ordering, fixed versus variable semantics and revision boundaries are distinguished. Formula registration records inert metadata and does not authorize expression execution." }, { "concept": "Population, grain and joins", "disposition": "accepted", "rationale": "Questions distinguish counting unit, deduplication, input/output grain and join cardinality. Dimension members and shared join graphs remain separately mastered." }, { "concept": "Aggregation and exceptional values", "disposition": "accepted with profile dependency", "rationale": "Per-axis rules and recomputation requirements address ratios, distinct counts and snapshots. Missing, zero, undefined and approximate results remain explicit rather than receiving universal defaults." }, { "concept": "Time windows and historical restatement", "disposition": "qualified", "rationale": "Timestamp syntax is separated from calendars and window boundaries. Restatement references the relevant data snapshot and definition revision without rewriting prior semantics." }, { "concept": "Approval and access authority", "disposition": "separated", "rationale": "Attribution does not grant approval or execution permission. Published metadata does not grant dataset access, and restricted-result populations require scope disclosure." }, { "concept": "Local functions and external execution", "disposition": "accepted as proposals only", "rationale": "The six functions manage local definition and evidence records. None executes a metric, moves data, runs a dataset quality evaluation or implements a policy engine." }, { "concept": "Retirement and deletion", "disposition": "accepted with policy dependency", "rationale": "Retirement protects external observations and references. Payload deletion is delegated to authorized custodians, and minimal continuity records do not justify indefinite sensitive-data retention." }, { "concept": "Artifact identity and integrity", "disposition": "accepted", "rationale": "Master identifier precedence, immutable revision bindings and explicit timestamps are preserved. Hashes are separated from identity, authenticity and truth claims." }, { "concept": "Instance schemas and equivalence evidence", "disposition": "deferred", "rationale": "Candidate fields, conceptual mappings and proposed fixtures do not supply executable instance schemas, tested evaluator bindings or round-trip equivalence evidence." }, { "concept": "Source and provider assurance", "disposition": "held", "rationale": "Web text access supports selected claims only. Direct HTTP was not run, living source pins remain open and the local no-tools assessment is not independent second-provider review." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the local Codex no-tools self-audit is not independent review.", "Live source and version verification remains incomplete. Selected text from all nine sources was reviewed through web retrieval, but direct HTTP checks were not attempted because the owner reports sandbox blocking. HTTP status and content hashes are unmeasured. The coordinator must run check_sources.py and review source versions, errata, licensing and the living documentation release pin.", "Business-calendar, currency, accounting, statistical-estimation, confidentiality and consequential-use profiles need qualified domain review before operational adoption. No universal metric semantics or compliance certification is claimed.", "Nested instance schemas, pinned evaluator adapters, executed semantic fixtures and round-trip mapping evidence remain absent. Research schema validity is not proof of metric calculation correctness or executable conformance.", "The registry Dataset parent and proposed neighbor reference bindings require coordinator reconciliation and versioned acceptance. No shared registry change or mandatory runtime dependency is implied by this package.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Restore independent second-provider review before canonical or publishable-draft promotion.", "Run the supplied source checker outside the sandbox and verify claim support, exact editions, errata, licenses and a release pin for living documentation.", "Develop nested schemas and evaluator fixtures for weighted ratios, distinct overlap, nulls, zero denominators, join fan-out, window boundaries, restatements and restricted populations.", "Review domain profiles and reconcile the Dataset parent and candidate neighbor bindings without duplicating target-owned operations." ] }, "statistics": { "sources": 9, "bundles": 6, "layers": 12, "findings": 18, "questions": 54, "artifacts": 18, "functions": 6 } }