{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-dat-014","code":"wm-dat-014-dimension-and-hierarchy","url":"https://ver.cy/models/wm-dat-014-dimension-and-hierarchy/","name":"Dimension and Hierarchy","alternateNames":[],"kind":"world-model","status":"published","version":"1.0.0","language":"en","classifiers":{"family":"World Models","category":"Information and virtual systems","entryKind":"entity","plane":"","domain":["INF.DAT.DIM"],"industry":["Cross-industry"],"navPath":"NAV.INF.DAT.DIM","tags":["dimension","hierarchy","inf.dat.dim"],"facets":{}},"whatItIs":"One governed analytical dimension definition is the root. It carries a value-domain binding, contextual roles and zero or more hierarchy-view bindings. Hierarchy views have their own identities and revisions; externally maintained codes remain references. This is a proposed format-neutral metadata contract, not an executable analytics engine.","purpose":"Describe a reusable analytical dimension and its versioned hierarchy bindings so consumers can select, group and interpret measures without inventing member identity or roll-up semantics.","scope":{"in":["Dimension identity, semantic concept, representation and analytical grain bindings.","Member references, local exceptional-value policy, labels and hierarchy occurrences.","Named hierarchy views, edge meaning, optional levels, roots, topology and contextual selection.","Effective revisions, provenance, consumer mappings and declared aggregation eligibility.","Local governance, change evidence, validation requirements and access policy for these metadata records."],"out":["Dataset rows, observations, materialized cubes and query execution.","Metric formulas, units, numerical aggregation algorithms and certification of statistical validity.","Ownership of external business entities, taxonomies, code lists, geographical boundaries or calendars.","Physical dimensions, vector-space dimensions and the platform owner-package service named Dimension.","Runtime authorization, disclosure-control engines, pipeline execution and global audit-trail operations."],"boundaries":[{"neighbor":"WM-DAT-001 Dataset","distinction":"Registry parent is a catalog organization lead. A dimension can be reused across datasets, so do not infer exclusive containment or dataset lifecycle inheritance. Store only pinned consumer references."},{"neighbor":"WM-DAT-013 Metric Definition","distinction":"This model records whether a hierarchy is eligible under a referenced measure aggregation contract; formulas and computation belong to the metric master."},{"neighbor":"WM-DAT-015 Semantic Model","distinction":"Role-specific dimension bindings are local metadata; semantic joins, query planning and model-wide evaluation remain external."},{"neighbor":"WM-DAT-004 Data Schema / Data Contract","distinction":"Concrete record schemas and physical keys are external bindings; candidate answer fields here are not a complete instance schema."},{"neighbor":"WM-DAT-006 Data Lineage and WM-DAT-007 Data Quality Evaluation","distinction":"Carry derivation and validation-report references; do not own pipeline lineage execution or a global quality evaluator."},{"neighbor":"External concept and code schemes","distinction":"Hierarchy occurrence identity differs from referenced code identity. Local aliases and revision pins do not transfer maintenance authority over source codes."}]},"distinguishingFeatures":["Unlike WM-DAT-001 Dataset: Registry parent is a catalog organization lead. A dimension can be reused across datasets, so do not infer exclusive containment or dataset lifecycle inheritance. Store only pinned consumer references.","Unlike WM-DAT-013 Metric Definition: This model records whether a hierarchy is eligible under a referenced measure aggregation contract; formulas and computation belong to the metric master.","Unlike WM-DAT-015 Semantic Model: Role-specific dimension bindings are local metadata; semantic joins, query planning and model-wide evaluation remain external.","Unlike WM-DAT-004 Data Schema / Data Contract: Concrete record schemas and physical keys are external bindings; candidate answer fields here are not a complete instance schema.","Unlike WM-DAT-006 Data Lineage and WM-DAT-007 Data Quality Evaluation: Carry derivation and validation-report references; do not own pipeline lineage execution or a global quality evaluator.","Unlike External concept and code schemes: Hierarchy occurrence identity differs from referenced code identity. Local aliases and revision pins do not transfer maintenance authority over source codes."],"structure":{"bundles":[{"id":"b-definition","name":"Identity and analytical meaning","description":"Context for identity and analytical meaning.","layers":[{"id":"l-identity","name":"Dimension identity context","description":"Keep a stable dimension identifier separate from semantic concept, revision and any physical column. A dimension definition can exist before a dataset consumes it.","findings":[{"id":"f-identity","name":"Dimension identity","description":"Keep a stable dimension identifier separate from semantic concept, revision and any physical column. A dimension definition can exist before a dataset consumes it.","questions":[{"text":"Which master identifier and namespace identify this analytical dimension?","id":"f-identity-q01","kind":"identity"},{"text":"What analytical distinction does the dimension express?","id":"f-identity-q02","kind":"definition"},{"text":"Which accountable role maintains its definition and approves revisions?","id":"f-identity-q03","kind":"ownership"},{"text":"Which representation is coded, typed or explicitly mixed under the adopting profile?","id":"f-identity-q04","kind":"classification"}]}]},{"id":"l-usage","name":"Grain and role bindings context","description":"A usage binding names a dataset or semantic context, analytical role and expected grain. Reusing a date-like domain for separate roles does not make those roles interchangeable.","findings":[{"id":"f-usage","name":"Grain and role bindings","description":"A usage binding names a dataset or semantic context, analytical role and expected grain. Reusing a date-like domain for separate roles does not make those roles interchangeable.","questions":[{"text":"Which consumer and role use this dimension revision?","id":"f-usage-q01","kind":"relationship"},{"text":"Which other dimensions jointly define the consumer observation key?","id":"f-usage-q02","kind":"composition"},{"text":"What prevents a join from multiplying observations through ambiguous member matches?","id":"f-usage-q03","kind":"constraint"},{"text":"How is a dimension with no current consumer distinguished from a broken binding?","id":"f-usage-q04","kind":"exception"}]}]}]},{"id":"b-values","name":"Values and member references","description":"Context for values and member references.","layers":[{"id":"l-members","name":"Member identity and representation context","description":"A code is qualified by its source scheme and revision. A member occurrence in a hierarchy also needs a hierarchy-scoped identity. Labels and notation are presentation and exchange values, not sufficient global keys.","findings":[{"id":"f-members","name":"Member identity and representation","description":"A code is qualified by its source scheme and revision. A member occurrence in a hierarchy also needs a hierarchy-scoped identity. Labels and notation are presentation and exchange values, not sufficient global keys.","questions":[{"text":"Which source scheme, revision and member identifier resolve a coded value?","id":"f-members-q01","kind":"identity"},{"text":"How are typed values normalized without losing their declared datatype?","id":"f-members-q02","kind":"interoperability"},{"text":"Where did each label, notation and language tag originate?","id":"f-members-q03","kind":"provenance"},{"text":"How are duplicate labels and reused codes distinguished before matching?","id":"f-members-q04","kind":"quality"}]}]},{"id":"l-exceptions","name":"Missing and partial domain semantics context","description":"Missing, unknown, not applicable, suppressed and aggregate-all values require explicit distinct policies when used. Partial domain extracts cannot prove global absence; a synthetic total is not silently inserted as a source member.","findings":[{"id":"f-exceptions","name":"Missing and partial domain semantics","description":"Missing, unknown, not applicable, suppressed and aggregate-all values require explicit distinct policies when used. Partial domain extracts cannot prove global absence; a synthetic total is not silently inserted as a source member.","questions":[{"text":"Which exceptional states are represented and how are they distinguished?","id":"f-exceptions-q01","kind":"exception"},{"text":"Does a blank or absent value fail the selected consumer key contract?","id":"f-exceptions-q02","kind":"constraint"},{"text":"Is the supplied member list complete for the claimed scope and revision?","id":"f-exceptions-q03","kind":"quality"},{"text":"How is a suppressed value prevented from being interpreted as zero or an ordinary member?","id":"f-exceptions-q04","kind":"access"}]}]}]},{"id":"b-hierarchies","name":"Hierarchy views and topology","description":"Context for hierarchy views and topology.","layers":[{"id":"l-graph","name":"Typed hierarchy edges context","description":"Give each view and occurrence a stable identity. Declare edge direction, meaning, roots and parent multiplicity. A selected analytical profile may require an acyclic graph; this is stronger than bare SKOS semantics. A flat dimension needs no artificial parent.","findings":[{"id":"f-graph","name":"Typed hierarchy edges","description":"Give each view and occurrence a stable identity. Declare edge direction, meaning, roots and parent multiplicity. A selected analytical profile may require an acyclic graph; this is stronger than bare SKOS semantics. A flat dimension needs no artificial parent.","questions":[{"text":"Which hierarchy view and occurrence identifiers define this arrangement?","id":"f-graph-q01","kind":"composition"},{"text":"What does each directed parent-child edge mean in this view?","id":"f-graph-q02","kind":"relationship"},{"text":"Are multiple parents, disconnected roots or no hierarchy permitted by the selected profile?","id":"f-graph-q03","kind":"constraint"},{"text":"What evidence detects cycles, dangling edges and unintended duplicate occurrences?","id":"f-graph-q04","kind":"validation"}]}]},{"id":"l-levels","name":"Levels, paths and ordering context","description":"Formal levels are optional and differ from graph depth. Views may have skipped levels and uneven paths. Display ordering is not a numerical distance or an additive relationship.","findings":[{"id":"f-levels","name":"Levels, paths and ordering","description":"Formal levels are optional and differ from graph depth. Views may have skipped levels and uneven paths. Display ordering is not a numerical distance or an additive relationship.","questions":[{"text":"Which levels are formal semantic categories and which depths are only derived?","id":"f-levels-q01","kind":"classification"},{"text":"How are skipped levels and leaves at unequal depths represented?","id":"f-levels-q02","kind":"composition"},{"text":"How does a consumer select a default or alternate hierarchy without changing member identity?","id":"f-levels-q03","kind":"process"},{"text":"Which ordering rules are presentation-only rather than analytical comparisons?","id":"f-levels-q04","kind":"constraint"}]}]}]},{"id":"b-change","name":"Time and controlled change","description":"Context for time and controlled change.","layers":[{"id":"l-validity","name":"Effective and recorded revisions context","description":"Maintain revision identity and separate effective applicability from recorded time. A corrected historical assignment need not take effect when it was ingested. Period-valued analytical members remain calendar-qualified values, not fabricated instants.","findings":[{"id":"f-validity","name":"Effective and recorded revisions","description":"Maintain revision identity and separate effective applicability from recorded time. A corrected historical assignment need not take effect when it was ingested. Period-valued analytical members remain calendar-qualified values, not fabricated instants.","questions":[{"text":"What effective interval and boundary convention qualify this member assignment?","id":"f-validity-q01","kind":"temporal"},{"text":"When was the assertion recorded and from which source revision?","id":"f-validity-q02","kind":"provenance"},{"text":"How are overlapping effective assignments resolved for an as-of request?","id":"f-validity-q03","kind":"constraint"},{"text":"Which calendar, granularity and offset rules distinguish time members from audit instants?","id":"f-validity-q04","kind":"interoperability"}]}]},{"id":"l-revision","name":"Revision and migration evidence context","description":"Changing a label, reparenting a member, splitting a code and replacing a meaning have different compatibility consequences. Supersession preserves a reference trail but does not imply semantic equivalence or indefinite payload retention.","findings":[{"id":"f-revision","name":"Revision and migration evidence","description":"Changing a label, reparenting a member, splitting a code and replacing a meaning have different compatibility consequences. Supersession preserves a reference trail but does not imply semantic equivalence or indefinite payload retention.","questions":[{"text":"Which state and approval evidence allow this revision to be used?","id":"f-revision-q01","kind":"lifecycle"},{"text":"What semantic change caused the new revision?","id":"f-revision-q02","kind":"event"},{"text":"Which consumers need explicit migration after splits, merges or reparenting?","id":"f-revision-q03","kind":"interoperability"},{"text":"What retention rule permits retirement or payload removal while preserving necessary reference continuity?","id":"f-revision-q04","kind":"retention"}]}]}]},{"id":"b-analysis","name":"Analytical use and exchange","description":"Context for analytical use and exchange.","layers":[{"id":"l-rollup","name":"Aggregation eligibility contract context","description":"A hierarchy supplies navigation and grouping context, not proof that child measures sum to a parent. Record eligibility only against a pinned metric contract and explicit coverage, overlap, allocation and temporal conditions. Unknown eligibility blocks automatic roll-up.","findings":[{"id":"f-rollup","name":"Aggregation eligibility contract","description":"A hierarchy supplies navigation and grouping context, not proof that child measures sum to a parent. Record eligibility only against a pinned metric contract and explicit coverage, overlap, allocation and temporal conditions. Unknown eligibility blocks automatic roll-up.","questions":[{"text":"Which metric contract and operator permit aggregation along this particular hierarchy?","id":"f-rollup-q01","kind":"measurement"},{"text":"What evidence shows complete disjoint coverage or an approved treatment of overlapping members?","id":"f-rollup-q02","kind":"constraint"},{"text":"Which non-additive or time-sensitive measure cases forbid a simple sum?","id":"f-rollup-q03","kind":"exception"},{"text":"How is repeated ancestry handled so an observation is not counted through multiple paths?","id":"f-rollup-q04","kind":"validation"}]}]},{"id":"l-mapping","name":"Crosswalks and projection limits context","description":"Crosswalks identify source and target schemes, revisions, direction and relationship strength. A similar label is not identity, and mapping equivalence does not establish aggregate preservation. Every exchange projection names its standard version and known losses.","findings":[{"id":"f-mapping","name":"Crosswalks and projection limits","description":"Crosswalks identify source and target schemes, revisions, direction and relationship strength. A similar label is not identity, and mapping equivalence does not establish aggregate preservation. Every exchange projection names its standard version and known losses.","questions":[{"text":"Which source and target revisions and mapping relation define this crosswalk?","id":"f-mapping-q01","kind":"interoperability"},{"text":"What evidence supports each match rather than label similarity alone?","id":"f-mapping-q02","kind":"quality"},{"text":"Which one-to-many or unmapped members require explicit loss or allocation decisions?","id":"f-mapping-q03","kind":"exception"},{"text":"Which target specification version and profile must a projection satisfy?","id":"f-mapping-q04","kind":"requirement"}]}]}]},{"id":"b-assurance","name":"Assurance and accountable use","description":"Context for assurance and accountable use.","layers":[{"id":"l-validation","name":"Evidence and validation scope context","description":"A check result is bound to a dimension revision, profile, evidence snapshot and evaluator reference. Passing structural checks does not prove factual correctness, representative coverage, aggregation safety or privacy. Local functions below are proposed operations, not implementations.","findings":[{"id":"f-validation","name":"Evidence and validation scope","description":"A check result is bound to a dimension revision, profile, evidence snapshot and evaluator reference. Passing structural checks does not prove factual correctness, representative coverage, aggregation safety or privacy. Local functions below are proposed operations, not implementations.","questions":[{"text":"Which pinned shapes or equivalent rules validate this exact revision?","id":"f-validation-q01","kind":"validation"},{"text":"Which fixtures expose multi-parent overlap, cycles, ragged paths and code reuse?","id":"f-validation-q02","kind":"evidence"},{"text":"Who produced the report and which source snapshots were examined?","id":"f-validation-q03","kind":"provenance"},{"text":"Which failures, warnings and untested cases prevent operational approval?","id":"f-validation-q04","kind":"quality"}]}]},{"id":"l-governance","name":"Authority, access and disclosure context","description":"Proposed local governance rules assign accountable roles and policy bindings. Member labels, mapping paths and small-group structure can be sensitive. Derived visible views must not reveal restricted members or imply complete coverage after filtering. The cited vocabularies do not grant authority or supply a disclosure-control algorithm.","findings":[{"id":"f-governance","name":"Authority, access and disclosure","description":"Proposed local governance rules assign accountable roles and policy bindings. Member labels, mapping paths and small-group structure can be sensitive. Derived visible views must not reveal restricted members or imply complete coverage after filtering. The cited vocabularies do not grant authority or supply a disclosure-control algorithm.","questions":[{"text":"Which role and policy authorize definition, hierarchy or mapping changes?","id":"f-governance-q01","kind":"authority"},{"text":"Which namespace and revision checks prevent an untrusted import from replacing an approved view?","id":"f-governance-q02","kind":"security"},{"text":"Which member attributes or relationships need restricted visibility for the stated purpose?","id":"f-governance-q03","kind":"privacy"},{"text":"How are filtered paths and hidden totals reported without leaking restricted members?","id":"f-governance-q04","kind":"access"}]}]}]}]},"agentConduct":{"may":["Resolve a dimension binding: Proposed local operation, not implemented. Resolve qualified identifiers and the requested revision without substituting the latest revision or matching labels alone.","Propose a hierarchy revision: Proposed local operation, not implemented. Prepare a candidate view from authorized member references and explicit topology rules.","Assess local metadata against a profile: Proposed local operation, not implemented. Request or bind a check report for a fixed metadata snapshot; no implemented validator or conformance certification is claimed.","Record roll-up eligibility: Proposed local operation, not implemented. Evaluate whether supplied evidence supports a declared eligibility decision under a referenced metric contract; never calculate aggregates.","Propose a versioned crosswalk: Proposed local operation, not implemented. Record supported mappings and unresolved differences without collapsing identities.","Propose retirement of a revision: Proposed local operation, not implemented. Assess consumer references and retention policy before marking a local revision superseded or proposing payload disposition."],"mustNot":["Use guarded revision proposals, provenance and affected-consumer review; never overwrite source code masters or change past facts by implicit rebinding.","Deny mutation unless an accountable policy authorizes the role; restrict sensitive metadata reads by purpose and scope."],"requiresHuman":[]},"ethics":{"considerations":["Domain-specific aggregation operators, allocation formulas, fiscal calendars, geographic boundary histories and privacy controls require qualified profiles.","Local authority, licensing, privacy and retention decisions require the adopting governance profile."],"affectedParties":[]},"owners":{"steward":"Name an accountable dimension steward role and adopting governance package.","roles":[{"name":"Dimension steward","responsibilities":["Maintain semantic scope, namespaces and revision proposals."]},{"name":"Hierarchy curator","responsibilities":["Maintain authorized view edges and temporal assignment evidence."]},{"name":"Accountable reviewer","responsibilities":["Approve compatibility, mapping and roll-up eligibility evidence."]},{"name":"Consumer integrator","responsibilities":["Pin consumer roles and report projection loss or ambiguous joins."]},{"name":"Access custodian","responsibilities":["Bind access, disclosure and retention policies; review sensitive views."]}],"masterSystems":[]},"relations":[{"target":"WM-DAT-001","type":"references","note":"Candidate consumer dataset binding, not containment or inherited lifecycle."},{"target":"WM-DAT-013","type":"references","note":"Candidate metric contract for aggregation eligibility; formulas and computed measures stay external."},{"target":"WM-DAT-015","type":"references","note":"Candidate semantic context and role binding; query execution and joins stay external."},{"target":"WM-DAT-004","type":"references","note":"Candidate concrete instance-schema binding and projection contract."},{"target":"WM-DAT-006","type":"references","note":"Candidate provenance master binding; record derivation references only."},{"target":"WM-DAT-007","type":"references","note":"Candidate external validation report/evaluator binding, not evaluator ownership."},{"target":"SKOS","type":"aligned","note":"Optional concept and mapping projection; analytical acyclicity requires additional rules."},{"target":"SDMX 3.0 Information Model","type":"aligned","note":"Optional version-pinned hierarchy and representation mapping; 3.1 mapping remains held."},{"target":"WM-DAT-001 Dataset","type":"neighbor","note":"Registry parent is a catalog organization lead. A dimension can be reused across datasets, so do not infer exclusive containment or dataset lifecycle inheritance. Store only pinned consumer references."},{"target":"WM-DAT-013 Metric Definition","type":"neighbor","note":"This model records whether a hierarchy is eligible under a referenced measure aggregation contract; formulas and computation belong to the metric master."},{"target":"WM-DAT-015 Semantic Model","type":"neighbor","note":"Role-specific dimension bindings are local metadata; semantic joins, query planning and model-wide evaluation remain external."},{"target":"WM-DAT-004 Data Schema / Data Contract","type":"neighbor","note":"Concrete record schemas and physical keys are external bindings; candidate answer fields here are not a complete instance schema."},{"target":"WM-DAT-006 Data Lineage and WM-DAT-007 Data Quality Evaluation","type":"neighbor","note":"Carry derivation and validation-report references; do not own pipeline lineage execution or a global quality evaluator."},{"target":"External concept and code schemes","type":"neighbor","note":"Hierarchy occurrence identity differs from referenced code identity. Local aliases and revision pins do not transfer maintenance authority over source codes."},{"target":"WM-DAT-001","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier with namespace","Governed global identifier or IRI","UUID or ULID assigned by the adopting governance package"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":[]},"capabilities":{"applicability":"required","items":["Resolve a dimension binding: Proposed local operation, not implemented. Resolve qualified identifiers and the requested revision without substituting the latest revision or matching labels alone.","Propose a hierarchy revision: Proposed local operation, not implemented. Prepare a candidate view from authorized member references and explicit topology rules.","Assess local metadata against a profile: Proposed local operation, not implemented. Request or bind a check report for a fixed metadata snapshot; no implemented validator or conformance certification is claimed.","Record roll-up eligibility: Proposed local operation, not implemented. Evaluate whether supplied evidence supports a declared eligibility decision under a referenced metric contract; never calculate aggregates.","Propose a versioned crosswalk: Proposed local operation, not implemented. Record supported mappings and unresolved differences without collapsing identities.","Propose retirement of a revision: Proposed local operation, not implemented. Assess consumer references and retention policy before marking a local revision superseded or proposing payload disposition."]},"hazards":{"applicability":"optional","items":[]},"interfaces":{"applicability":"required","items":["PROV-O: The PROV Ontology","RFC 3339: Date and Time on the Internet: Timestamps","RFC 6902: JavaScript Object Notation (JSON) Patch"]},"context":{"applicability":"required","items":["No jurisdiction, fiscal calendar, language, timezone or geographic classifier is universal.","Local authority, licensing, privacy and retention decisions require the adopting governance profile."]}},"sources":[{"title":"The RDF Data Cube Vocabulary","url":"https://www.w3.org/TR/vocab-data-cube/","note":"W3C"},{"title":"SKOS Simple Knowledge Organization System Reference","url":"https://www.w3.org/TR/skos-reference/","note":"W3C"},{"title":"SDMX Standards Section 2: Information Model","url":"https://sdmx.org/wp-content/uploads/SDMX_3-0-0_SECTION_2_FINAL-1_0.pdf","note":"SDMX"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"W3C"},{"title":"Shapes Constraint Language (SHACL)","url":"https://www.w3.org/TR/shacl/","note":"W3C"},{"title":"RFC 3339: Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"IETF"},{"title":"RFC 6902: JavaScript Object Notation (JSON) Patch","url":"https://www.rfc-editor.org/rfc/rfc6902","note":"IETF"},{"title":"SDMX Technical Specifications","url":"https://sdmx.org/standards-2/","note":"SDMX"}],"openQuestions":["Run the prepared direct-HTTP checker outside the sandbox and complete claim-level, version, errata and licensing review, including the target SDMX version.","Implement and test nested profiles with flat, multi-root, multi-parent, cyclic, ragged, incomplete, overlapping-time and sensitive filtered-view cases; verify metric-specific roll-up and mapping loss without importing metric execution into this model.","Pin consumer and neighbor revisions and obtain independent external review before any canonical or publishable-draft promotion.","Independent external review is absent under the owner waiver.","Direct HTTP checks are not attempted because the owner reports sandbox blocking; no response statuses or body hashes were measured.","Full version and errata review is incomplete; SDMX 3.1 Information Model retrieval failed, and 3.0 conceptual claims must not be promoted to 3.1 conformance.","Nested instance schemas, exchange round trips and adversarial fixtures are designed but not implemented.","Domain-specific aggregation operators, allocation formulas, fiscal calendars, geographic boundary histories and privacy controls require qualified profiles.","Neighbor references are proposed bindings with no guaranteed deployed runtime or pinned neighbor version."],"resources":{"spec":"/models/wm-dat-014-dimension-and-hierarchy/spec.yaml","agents":"/models/wm-dat-014-dimension-and-hierarchy/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-dat-014"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-dat-014-dimension-and-hierarchy/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-21T17:04:49Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"derived","structure":"filled","agentConduct":"derived","ethics":"derived","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"missing","interaction.capabilities":"filled","interaction.hazards":"missing","interaction.interfaces":"derived","interaction.context":"filled","sources":"filled"},"notes":{"distinguishingFeatures":"Derived from boundary notes against neighbouring models.","agentConduct":"Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.","ethics":"Sentences mentioning harm, privacy, consent or similar, collected from the specification.","interaction.properties":"Institutional or informational subject: no invented physical properties."},"score":0.75}}