{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-knw-018","code":"wm-knw-018-taxonomy-classification-scheme","url":"https://ver.cy/models/wm-knw-018-taxonomy-classification-scheme/","name":"Taxonomy / Classification Scheme","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Information and virtual systems","entryKind":"aggregate","plane":"","domain":["INF.KNW.TAX"],"industry":["Cross-industry"],"navPath":"NAV.INF.KNW.TAX","tags":["taxonomy","classification","scheme","inf.knw.tax"],"facets":{}},"whatItIs":"Owns scheme identity, namespace, canonical URI, profile, purpose, scope, subject, audience, language, jurisdiction, owner, publisher and steward; immutable releases and change sets; concept identity, scheme membership and top concepts; labels, definitions, notes, examples and notations; broader, narrower and related relations; hierarchy profiles, polyhierarchy, facets, arrays, collections and ordered membership; cross-scheme mappings with versions, method, confidence and provenance; proposal, approval, publication, deprecation, replacement, split, merge and retirement; validation, quality, access, licensing, retention and loss-aware projections. Classified real-world objects, classification bindings, source evidence, policies, workflows, datasets and search indexes remain external.","purpose":"Represent one governed versioned knowledge-organization scheme containing concept definitions, labels, notations, semantic relations, mappings and release governance.","scope":{"in":["Scheme identity, namespace, profile, scope, authority, release and concept membership","Labels, definitions, notations, hierarchy, association, facets, collections, mappings, lifecycle and validation","Provenance, governance, access, licensing, retention and interoperability"],"out":["Owning classified objects, classification bindings, evidence, organization, policy, workflow, dataset or search-index lifecycles","Equating labels with identity, concepts with referents, broader with part-of, closeMatch with exactMatch, or mapping with proved equivalence","Executing release approval, object reassignment, protected disclosure, external system mutation or irreversible deletion without authority"],"boundaries":[{"neighbor":"WM-XCT-020 Classification Binding","distinction":"A classification binding assigns an external object to a concept in a pinned scheme release. The scheme defines that concept; the registry parent direction appears reversed or navigational and remains held for review."},{"neighbor":"Concept and real-world referent","distinction":"A concept is a unit of thought or authority entry with its own URI. The person, place, product or other referent remains a separate mastered object."},{"neighbor":"Ontology and schema","distinction":"OWL and RDFS can express formal class axioms while SHACL validates graphs. A taxonomy may project to them but does not inherit formal semantics unless the profile declares them."},{"neighbor":"Metadata registry","distinction":"ISO/IEC 11179 defines generic registration, identification, designation, definition, classification and mapping facilities. This model specializes them for a knowledge-organization scheme."},{"neighbor":"Vocabulary distribution and dataset","distinction":"DCAT, DataCite and RO-Crate distributions package or describe a release. They do not replace canonical scheme, concept or mapping identity."},{"neighbor":"Search index","distinction":"An index may tokenize labels and materialize hierarchy for retrieval. Ranking, cache, deployment and query-log lifecycles remain external."},{"neighbor":"Mapping assessment","distinction":"The scheme owns mapping assertions and their status, while evidence and reviewer decisions remain attributable external records. Mapping never silently merges concept identity."}]},"distinguishingFeatures":["Holds the scheme and its concepts, not the assignment of concepts to objects, which is the classification binding model.","A concept has a stable identifier; labels and codes are names for it and may change or repeat.","Broader and narrower express generality, not part-of; close match is weaker than exact match.","Differs from an ontology, which defines formal axioms, and from a schema, which defines data structure."],"structure":{"bundles":[{"id":"scheme-identity-profile-scope-and-release","name":"Scheme identity, profile, scope and release","description":"Groups the governed Resource Consumption concern for scheme identity, profile, scope and release.","layers":[{"id":"identity-namespace-version-and-distribution","name":"Identity, namespace, version and distribution","description":"Groups Resource Consumption context for identity, namespace, version and distribution without importing neighboring master lifecycles.","findings":[{"id":"scheme-identifier-canonical-uri-namespace-prefix-and-local-id-policy","name":"Scheme identifier, canonical URI, namespace, prefix and local-ID policy","description":"Records scheme identifier, canonical uri, namespace, prefix and local-id policy as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish scheme identifier, canonical uri, namespace, prefix and local-id policy?","id":"scheme-identifier-canonical-uri-namespace-prefix-and-local-id-policy-q01","kind":"identity"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses scheme identifier, canonical uri, namespace, prefix and local-id policy, and under which authority?","id":"scheme-identifier-canonical-uri-namespace-prefix-and-local-id-policy-q02","kind":"ownership"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify scheme identifier, canonical uri, namespace, prefix and local-id policy?","id":"scheme-identifier-canonical-uri-namespace-prefix-and-local-id-policy-q03","kind":"validation"}]},{"id":"version-edition-release-status-date-predecessor-successor-and-distribution","name":"Version, edition, release status, date, predecessor, successor and distribution","description":"Records version, edition, release status, date, predecessor, successor and distribution as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish version, edition, release status, date, predecessor, successor and distribution?","id":"version-edition-release-status-date-predecessor-successor-and-distribution-q01","kind":"lifecycle"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses version, edition, release status, date, predecessor, successor and distribution, and under which authority?","id":"version-edition-release-status-date-predecessor-successor-and-distribution-q02","kind":"authority"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify version, edition, release status, date, predecessor, successor and distribution?","id":"version-edition-release-status-date-predecessor-successor-and-distribution-q03","kind":"security"}]}]},{"id":"scheme-kind-purpose-scope-audience-language-and-authority","name":"Scheme kind, purpose, scope, audience, language and authority","description":"Groups Resource Consumption context for scheme kind, purpose, scope, audience, language and authority without importing neighboring master lifecycles.","findings":[{"id":"taxonomy-thesaurus-classification-list-synonym-ring-ontology-and-hybrid-profile","name":"Taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile","description":"Records taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile?","id":"taxonomy-thesaurus-classification-list-synonym-ring-ontology-and-hybrid-profile-q01","kind":"classification"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile, and under which authority?","id":"taxonomy-thesaurus-classification-list-synonym-ring-ontology-and-hybrid-profile-q02","kind":"requirement"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile?","id":"taxonomy-thesaurus-classification-list-synonym-ring-ontology-and-hybrid-profile-q03","kind":"privacy"}]},{"id":"purpose-subject-scope-audience-language-jurisdiction-owner-publisher-and-steward","name":"Purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward","description":"Records purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward?","id":"purpose-subject-scope-audience-language-jurisdiction-owner-publisher-and-steward-q01","kind":"authority"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward, and under which authority?","id":"purpose-subject-scope-audience-language-jurisdiction-owner-publisher-and-steward-q02","kind":"constraint"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward?","id":"purpose-subject-scope-audience-language-jurisdiction-owner-publisher-and-steward-q03","kind":"retention"}]}]}]},{"id":"concepts-labels-definitions-notations-and-notes","name":"Concepts, labels, definitions, notations and notes","description":"Groups the governed Resource Consumption concern for concepts, labels, definitions, notations and notes.","layers":[{"id":"concept-identity-membership-type-and-referent-boundary","name":"Concept identity, membership, type and referent boundary","description":"Groups Resource Consumption context for concept identity, membership, type and referent boundary without importing neighboring master lifecycles.","findings":[{"id":"concept-uri-local-identifier-in-scheme-top-concept-and-concept-type","name":"Concept URI, local identifier, in-scheme, top concept and concept type","description":"Records concept uri, local identifier, in-scheme, top concept and concept type as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish concept uri, local identifier, in-scheme, top concept and concept type?","id":"concept-uri-local-identifier-in-scheme-top-concept-and-concept-type-q01","kind":"identity"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses concept uri, local identifier, in-scheme, top concept and concept type, and under which authority?","id":"concept-uri-local-identifier-in-scheme-top-concept-and-concept-type-q02","kind":"process"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify concept uri, local identifier, in-scheme, top concept and concept type?","id":"concept-uri-local-identifier-in-scheme-top-concept-and-concept-type-q03","kind":"access"}]},{"id":"concept-characteristics-extension-intension-referent-authority-and-rwo-distinction","name":"Concept characteristics, extension, intension, referent, authority and RWO distinction","description":"Records concept characteristics, extension, intension, referent, authority and rwo distinction as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish concept characteristics, extension, intension, referent, authority and rwo distinction?","id":"concept-characteristics-extension-intension-referent-authority-and-rwo-distinction-q01","kind":"definition"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses concept characteristics, extension, intension, referent, authority and rwo distinction, and under which authority?","id":"concept-characteristics-extension-intension-referent-authority-and-rwo-distinction-q02","kind":"event"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify concept characteristics, extension, intension, referent, authority and rwo distinction?","id":"concept-characteristics-extension-intension-referent-authority-and-rwo-distinction-q03","kind":"exception"}]}]},{"id":"lexical-label-definition-note-example-and-notation","name":"Lexical label, definition, note, example and notation","description":"Groups Resource Consumption context for lexical label, definition, note, example and notation without importing neighboring master lifecycles.","findings":[{"id":"preferred-alternative-hidden-label-language-script-direction-and-uniqueness","name":"Preferred, alternative and hidden label, language, script, direction and uniqueness","description":"Records preferred, alternative and hidden label, language, script, direction and uniqueness as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish preferred, alternative and hidden label, language, script, direction and uniqueness?","id":"preferred-alternative-hidden-label-language-script-direction-and-uniqueness-q01","kind":"classification"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses preferred, alternative and hidden label, language, script, direction and uniqueness, and under which authority?","id":"preferred-alternative-hidden-label-language-script-direction-and-uniqueness-q02","kind":"measurement"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify preferred, alternative and hidden label, language, script, direction and uniqueness?","id":"preferred-alternative-hidden-label-language-script-direction-and-uniqueness-q03","kind":"interoperability"}]},{"id":"definition-scope-note-example-history-change-editorial-note-notation-and-code","name":"Definition, scope note, example, history, change, editorial note, notation and code","description":"Records definition, scope note, example, history, change, editorial note, notation and code as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish definition, scope note, example, history, change, editorial note, notation and code?","id":"definition-scope-note-example-history-change-editorial-note-notation-and-code-q01","kind":"definition"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses definition, scope note, example, history, change, editorial note, notation and code, and under which authority?","id":"definition-scope-note-example-history-change-editorial-note-notation-and-code-q02","kind":"evidence"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify definition, scope note, example, history, change, editorial note, notation and code?","id":"definition-scope-note-example-history-change-editorial-note-notation-and-code-q03","kind":"decision"}]}]}]},{"id":"hierarchy-association-facets-collections-and-integrity","name":"Hierarchy, association, facets, collections and integrity","description":"Groups the governed Resource Consumption concern for hierarchy, association, facets, collections and integrity.","layers":[{"id":"broader-narrower-association-polyhierarchy-and-topology","name":"Broader, narrower, association, polyhierarchy and topology","description":"Groups Resource Consumption context for broader, narrower, association, polyhierarchy and topology without importing neighboring master lifecycles.","findings":[{"id":"broader-narrower-generic-instance-partitive-top-concept-and-transitive-closure","name":"Broader, narrower, generic, instance, partitive, top-concept and transitive closure","description":"Records broader, narrower, generic, instance, partitive, top-concept and transitive closure as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish broader, narrower, generic, instance, partitive, top-concept and transitive closure?","id":"broader-narrower-generic-instance-partitive-top-concept-and-transitive-closure-q01","kind":"relationship"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses broader, narrower, generic, instance, partitive, top-concept and transitive closure, and under which authority?","id":"broader-narrower-generic-instance-partitive-top-concept-and-transitive-closure-q02","kind":"quality"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify broader, narrower, generic, instance, partitive, top-concept and transitive closure?","id":"broader-narrower-generic-instance-partitive-top-concept-and-transitive-closure-q03","kind":"identity"}]},{"id":"related-see-also-direction-role-symmetry-polyhierarchy-cycle-and-orphan","name":"Related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan","description":"Records related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan?","id":"related-see-also-direction-role-symmetry-polyhierarchy-cycle-and-orphan-q01","kind":"relationship"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan, and under which authority?","id":"related-see-also-direction-role-symmetry-polyhierarchy-cycle-and-orphan-q02","kind":"validation"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan?","id":"related-see-also-direction-role-symmetry-polyhierarchy-cycle-and-orphan-q03","kind":"classification"}]}]},{"id":"facets-arrays-collections-compounds-and-structural-rules","name":"Facets, arrays, collections, compounds and structural rules","description":"Groups Resource Consumption context for facets, arrays, collections, compounds and structural rules without importing neighboring master lifecycles.","findings":[{"id":"facet-facet-value-array-node-guide-term-and-systematic-display","name":"Facet, facet value, array, node label, guide term and systematic display","description":"Records facet, facet value, array, node label, guide term and systematic display as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish facet, facet value, array, node label, guide term and systematic display?","id":"facet-facet-value-array-node-guide-term-and-systematic-display-q01","kind":"composition"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses facet, facet value, array, node label, guide term and systematic display, and under which authority?","id":"facet-facet-value-array-node-guide-term-and-systematic-display-q02","kind":"security"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify facet, facet value, array, node label, guide term and systematic display?","id":"facet-facet-value-array-node-guide-term-and-systematic-display-q03","kind":"composition"}]},{"id":"collection-ordered-collection-member-list-compound-concept-and-precoordination","name":"Collection, ordered collection, member list, compound concept and precoordination","description":"Records collection, ordered collection, member list, compound concept and precoordination as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish collection, ordered collection, member list, compound concept and precoordination?","id":"collection-ordered-collection-member-list-compound-concept-and-precoordination-q01","kind":"composition"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses collection, ordered collection, member list, compound concept and precoordination, and under which authority?","id":"collection-ordered-collection-member-list-compound-concept-and-precoordination-q02","kind":"privacy"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify collection, ordered collection, member list, compound concept and precoordination?","id":"collection-ordered-collection-member-list-compound-concept-and-precoordination-q03","kind":"relationship"}]}]}]},{"id":"mapping-alignment-method-confidence-and-dispute","name":"Mapping, alignment, method, confidence and dispute","description":"Groups the governed Resource Consumption concern for mapping, alignment, method, confidence and dispute.","layers":[{"id":"mapping-relation-source-target-version-and-direction","name":"Mapping relation, source, target, version and direction","description":"Groups Resource Consumption context for mapping relation, source, target, version and direction without importing neighboring master lifecycles.","findings":[{"id":"exact-close-broad-narrow-related-equivalent-subclass-and-same-as-distinction","name":"Exact, close, broad, narrow, related, equivalent, subclass and same-as distinction","description":"Records exact, close, broad, narrow, related, equivalent, subclass and same-as distinction as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish exact, close, broad, narrow, related, equivalent, subclass and same-as distinction?","id":"exact-close-broad-narrow-related-equivalent-subclass-and-same-as-distinction-q01","kind":"interoperability"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses exact, close, broad, narrow, related, equivalent, subclass and same-as distinction, and under which authority?","id":"exact-close-broad-narrow-related-equivalent-subclass-and-same-as-distinction-q02","kind":"retention"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify exact, close, broad, narrow, related, equivalent, subclass and same-as distinction?","id":"exact-close-broad-narrow-related-equivalent-subclass-and-same-as-distinction-q03","kind":"state"}]},{"id":"source-concept-target-concept-scheme-version-direction-symmetry-and-transitivity","name":"Source concept, target concept, scheme version, direction, symmetry and transitivity","description":"Records source concept, target concept, scheme version, direction, symmetry and transitivity as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish source concept, target concept, scheme version, direction, symmetry and transitivity?","id":"source-concept-target-concept-scheme-version-direction-symmetry-and-transitivity-q01","kind":"relationship"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses source concept, target concept, scheme version, direction, symmetry and transitivity, and under which authority?","id":"source-concept-target-concept-scheme-version-direction-symmetry-and-transitivity-q02","kind":"access"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify source concept, target concept, scheme version, direction, symmetry and transitivity?","id":"source-concept-target-concept-scheme-version-direction-symmetry-and-transitivity-q03","kind":"lifecycle"}]}]},{"id":"mapping-method-evidence-confidence-review-and-conflict","name":"Mapping method, evidence, confidence, review and conflict","description":"Groups Resource Consumption context for mapping method, evidence, confidence, review and conflict without importing neighboring master lifecycles.","findings":[{"id":"mapping-method-actor-tool-date-rationale-evidence-confidence-and-quality","name":"Mapping method, actor, tool, date, rationale, evidence, confidence and quality","description":"Records mapping method, actor, tool, date, rationale, evidence, confidence and quality as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish mapping method, actor, tool, date, rationale, evidence, confidence and quality?","id":"mapping-method-actor-tool-date-rationale-evidence-confidence-and-quality-q01","kind":"provenance"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses mapping method, actor, tool, date, rationale, evidence, confidence and quality, and under which authority?","id":"mapping-method-actor-tool-date-rationale-evidence-confidence-and-quality-q02","kind":"exception"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify mapping method, actor, tool, date, rationale, evidence, confidence and quality?","id":"mapping-method-actor-tool-date-rationale-evidence-confidence-and-quality-q03","kind":"temporal"}]},{"id":"candidate-accepted-rejected-contested-superseded-conflict-and-resolution","name":"Candidate, accepted, rejected, contested, superseded, conflict and resolution","description":"Records candidate, accepted, rejected, contested, superseded, conflict and resolution as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish candidate, accepted, rejected, contested, superseded, conflict and resolution?","id":"candidate-accepted-rejected-contested-superseded-conflict-and-resolution-q01","kind":"state"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses candidate, accepted, rejected, contested, superseded, conflict and resolution, and under which authority?","id":"candidate-accepted-rejected-contested-superseded-conflict-and-resolution-q02","kind":"interoperability"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify candidate, accepted, rejected, contested, superseded, conflict and resolution?","id":"candidate-accepted-rejected-contested-superseded-conflict-and-resolution-q03","kind":"spatial"}]}]}]},{"id":"governance-change-lifecycle-quality-and-validation","name":"Governance, change, lifecycle, quality and validation","description":"Groups the governed Resource Consumption concern for governance, change, lifecycle, quality and validation.","layers":[{"id":"proposal-review-approval-change-and-retirement","name":"Proposal, review, approval, change and retirement","description":"Groups Resource Consumption context for proposal, review, approval, change and retirement without importing neighboring master lifecycles.","findings":[{"id":"draft-proposed-reviewed-approved-published-deprecated-superseded-and-retired-state","name":"Draft, proposed, reviewed, approved, published, deprecated, superseded and retired state","description":"Records draft, proposed, reviewed, approved, published, deprecated, superseded and retired state as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish draft, proposed, reviewed, approved, published, deprecated, superseded and retired state?","id":"draft-proposed-reviewed-approved-published-deprecated-superseded-and-retired-state-q01","kind":"lifecycle"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses draft, proposed, reviewed, approved, published, deprecated, superseded and retired state, and under which authority?","id":"draft-proposed-reviewed-approved-published-deprecated-superseded-and-retired-state-q02","kind":"decision"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify draft, proposed, reviewed, approved, published, deprecated, superseded and retired state?","id":"draft-proposed-reviewed-approved-published-deprecated-superseded-and-retired-state-q03","kind":"provenance"}]},{"id":"change-set-add-update-move-split-merge-replace-delete-rationale-and-impact","name":"Change set, add, update, move, split, merge, replace, delete, rationale and impact","description":"Records change set, add, update, move, split, merge, replace, delete, rationale and impact as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish change set, add, update, move, split, merge, replace, delete, rationale and impact?","id":"change-set-add-update-move-split-merge-replace-delete-rationale-and-impact-q01","kind":"event"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses change set, add, update, move, split, merge, replace, delete, rationale and impact, and under which authority?","id":"change-set-add-update-move-split-merge-replace-delete-rationale-and-impact-q02","kind":"identity"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify change set, add, update, move, split, merge, replace, delete, rationale and impact?","id":"change-set-add-update-move-split-merge-replace-delete-rationale-and-impact-q03","kind":"ownership"}]}]},{"id":"validation-quality-completeness-consistency-and-release-gate","name":"Validation, quality, completeness, consistency and release gate","description":"Groups Resource Consumption context for validation, quality, completeness, consistency and release gate without importing neighboring master lifecycles.","findings":[{"id":"identity-label-language-notation-domain-range-hierarchy-cycle-and-mapping-check","name":"Identity, label, language, notation, domain, range, hierarchy, cycle and mapping check","description":"Records identity, label, language, notation, domain, range, hierarchy, cycle and mapping check as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish identity, label, language, notation, domain, range, hierarchy, cycle and mapping check?","id":"identity-label-language-notation-domain-range-hierarchy-cycle-and-mapping-check-q01","kind":"validation"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses identity, label, language, notation, domain, range, hierarchy, cycle and mapping check, and under which authority?","id":"identity-label-language-notation-domain-range-hierarchy-cycle-and-mapping-check-q02","kind":"classification"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify identity, label, language, notation, domain, range, hierarchy, cycle and mapping check?","id":"identity-label-language-notation-domain-range-hierarchy-cycle-and-mapping-check-q03","kind":"authority"}]},{"id":"coverage-completeness-freshness-consistency-accuracy-usability-and-release-assurance","name":"Coverage, completeness, freshness, consistency, accuracy, usability and release assurance","description":"Records coverage, completeness, freshness, consistency, accuracy, usability and release assurance as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish coverage, completeness, freshness, consistency, accuracy, usability and release assurance?","id":"coverage-completeness-freshness-consistency-accuracy-usability-and-release-assurance-q01","kind":"quality"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses coverage, completeness, freshness, consistency, accuracy, usability and release assurance, and under which authority?","id":"coverage-completeness-freshness-consistency-accuracy-usability-and-release-assurance-q02","kind":"composition"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify coverage, completeness, freshness, consistency, accuracy, usability and release assurance?","id":"coverage-completeness-freshness-consistency-accuracy-usability-and-release-assurance-q03","kind":"requirement"}]}]}]},{"id":"access-license-retention-publication-and-interoperability","name":"Access, license, retention, publication and interoperability","description":"Groups the governed Resource Consumption concern for access, license, retention, publication and interoperability.","layers":[{"id":"rights-access-sensitivity-retention-and-audit","name":"Rights, access, sensitivity, retention and audit","description":"Groups Resource Consumption context for rights, access, sensitivity, retention and audit without importing neighboring master lifecycles.","findings":[{"id":"license-rights-holder-attribution-purpose-role-sensitivity-and-minimum-disclosure","name":"License, rights holder, attribution, purpose, role, sensitivity and minimum disclosure","description":"Records license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure?","id":"license-rights-holder-attribution-purpose-role-sensitivity-and-minimum-disclosure-q01","kind":"access"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure, and under which authority?","id":"license-rights-holder-attribution-purpose-role-sensitivity-and-minimum-disclosure-q02","kind":"relationship"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure?","id":"license-rights-holder-attribution-purpose-role-sensitivity-and-minimum-disclosure-q03","kind":"constraint"}]},{"id":"retention-legal-hold-tombstone-withdrawal-audit-and-resolution-continuity","name":"Retention, legal hold, tombstone, withdrawal, audit and resolution continuity","description":"Records retention, legal hold, tombstone, withdrawal, audit and resolution continuity as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish retention, legal hold, tombstone, withdrawal, audit and resolution continuity?","id":"retention-legal-hold-tombstone-withdrawal-audit-and-resolution-continuity-q01","kind":"retention"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses retention, legal hold, tombstone, withdrawal, audit and resolution continuity, and under which authority?","id":"retention-legal-hold-tombstone-withdrawal-audit-and-resolution-continuity-q02","kind":"state"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify retention, legal hold, tombstone, withdrawal, audit and resolution continuity?","id":"retention-legal-hold-tombstone-withdrawal-audit-and-resolution-continuity-q03","kind":"process"}]}]},{"id":"serialization-profile-import-export-and-loss","name":"Serialization, profile, import, export and loss","description":"Groups Resource Consumption context for serialization, profile, import, export and loss without importing neighboring master lifecycles.","findings":[{"id":"skos-rdf-rdfs-owl-jsonld-mads-dcmi-dcat-datacite-and-rocrate-projection","name":"SKOS, RDF, RDFS, OWL, JSON-LD, MADS, DCMI, DCAT, DataCite and RO-Crate projection","description":"Records skos, rdf, rdfs, owl, json-ld, mads, dcmi, dcat, datacite and ro-crate projection as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish skos, rdf, rdfs, owl, json-ld, mads, dcmi, dcat, datacite and ro-crate projection?","id":"skos-rdf-rdfs-owl-jsonld-mads-dcmi-dcat-datacite-and-rocrate-projection-q01","kind":"interoperability"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses skos, rdf, rdfs, owl, json-ld, mads, dcmi, dcat, datacite and ro-crate projection, and under which authority?","id":"skos-rdf-rdfs-owl-jsonld-mads-dcmi-dcat-datacite-and-rocrate-projection-q02","kind":"lifecycle"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify skos, rdf, rdfs, owl, json-ld, mads, dcmi, dcat, datacite and ro-crate projection?","id":"skos-rdf-rdfs-owl-jsonld-mads-dcmi-dcat-datacite-and-rocrate-projection-q03","kind":"event"}]},{"id":"profile-version-context-shape-conformance-round-trip-migration-and-semantic-loss","name":"Profile, version, context, shape, conformance, round trip, migration and semantic loss","description":"Records profile, version, context, shape, conformance, round trip, migration and semantic loss as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.","questions":[{"text":"Which scheme and concept identities, profile, scope, language, relation semantics and release establish profile, version, context, shape, conformance, round trip, migration and semantic loss?","id":"profile-version-context-shape-conformance-round-trip-migration-and-semantic-loss-q01","kind":"validation"},{"text":"Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses profile, version, context, shape, conformance, round trip, migration and semantic loss, and under which authority?","id":"profile-version-context-shape-conformance-round-trip-migration-and-semantic-loss-q02","kind":"temporal"},{"text":"Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify profile, version, context, shape, conformance, round trip, migration and semantic loss?","id":"profile-version-context-shape-conformance-round-trip-migration-and-semantic-loss-q03","kind":"measurement"}]}]}]}]},"agentConduct":{"may":["Propose new concepts, labels and definitions for review.","Propose candidate mappings to other schemes with a match type.","Validate a scheme for cycles, orphan concepts and duplicate labels.","Publish read-only views of an approved release."],"mustNot":["Treat a label or code as the identity of a concept.","Publish or approve a scheme release.","Delete or redefine a concept that objects are still classified under.","Assert an exact match where only a close match is supported.","Reassign classified objects after a scheme change."],"requiresHuman":["Approving a release or a namespace.","Splitting, merging or deprecating concepts in use."]},"ethics":{"considerations":["Categories describing people, such as ethnicity, disability or gender, can stigmatise and need careful wording.","Classifications decide access to services, statistics and funding, so errors affect real people.","Offering labels in only one language excludes communities that use others."],"affectedParties":["People and groups that the categories describe","Users and systems that classify with the scheme","Language communities","Scheme maintainers"]},"owners":{"steward":"Declare the Dimension owner, scheme owner, publisher, vocabulary steward, concept editors, mapping reviewers, release approvers and access roles.","roles":[{"name":"Dimension owner","responsibilities":["Own namespace, mastership, delegation, access, retention and federation rules."]},{"name":"Scheme owner or publisher","responsibilities":["Own purpose, scope, authority, releases, license and public commitments."]},{"name":"Vocabulary steward","responsibilities":["Own scheme profile, concept model, relation semantics, lifecycle and editorial policy."]},{"name":"Concept editor or terminologist","responsibilities":["Propose identifiers, definitions, labels, notations, notes and internal relations."]},{"name":"Mapping curator","responsibilities":["Own mapping methods, evidence, confidence, review and conflict handling."]},{"name":"Release approver","responsibilities":["Own change-set acceptance, validation gate, effective time and publication decision."]},{"name":"Consumer or classifier","responsibilities":["Use pinned releases and keep external classification bindings in their owning model."]},{"name":"Reviewer or auditor","responsibilities":["Review authority, quality, mappings, changes, access and retention without rewriting originals."]}],"masterSystems":[]},"relations":[{"target":"WM-XCT-020 Classification Binding","type":"references","note":"Resolve assignments of external objects to concepts while the registry parent direction remains under review."},{"target":"Classified object, evidence, policy, dataset, distribution and search-index masters","type":"references","note":"Resolve external referents, sources, governance and delivery context without importing their lifecycles."},{"target":"W3C SKOS Reference and Primer","type":"aligned","note":"Project concepts, schemes, labels, notations, notes, semantic relations, collections, mappings and integrity conditions."},{"target":"RDF Schema 1.1, OWL 2 and JSON-LD 1.1","type":"aligned","note":"Project linked-data classes, properties, axioms, annotations, contexts, language maps and graph serialization."},{"target":"SHACL, PROV-O and DQV","type":"aligned","note":"Project validation, attribution, revision, invalidation and quality measurement semantics."},{"target":"DCAT 3, DataCite 4.7 and RO-Crate 1.3","type":"aligned","note":"Project catalog, distribution, persistent metadata and portable release packaging views."},{"target":"ISO 25964 parts 1 and 2","type":"aligned","note":"Project multilingual thesaurus construction, maintenance, exchange and cross-vocabulary mapping profiles."},{"target":"ISO 704:2022, ISO 1087:2019 and NISO Z39.19","type":"aligned","note":"Project terminology, concept, designation, definition and controlled-vocabulary management profiles."},{"target":"DCMI Metadata Terms and Library of Congress MADS/RDF","type":"aligned","note":"Project vocabulary metadata, authority data, variants, schemes, collections and RWO separation."},{"target":"BCP 47 language tags and matching","type":"aligned","note":"Project language-tag identity, validation, filtering and lookup for labels and notes."},{"target":"ODRL 2.2, RFC 3339 and RFC 8785","type":"aligned","note":"Project rights constraints, unambiguous clocks and deterministic JSON serialization."},{"target":"ISO/IEC 11179-3:2023","type":"aligned","note":"Project registry-item identification, designation, definition, registration, classification and mapping facilities."},{"target":"WM-XCT-020 Classification Binding","type":"neighbor","note":"A classification binding assigns an external object to a concept in a pinned scheme release. The scheme defines that concept; the registry parent direction appears reversed or navigational and remains held for review."},{"target":"Concept and real-world referent","type":"neighbor","note":"A concept is a unit of thought or authority entry with its own URI. The person, place, product or other referent remains a separate mastered object."},{"target":"Ontology and schema","type":"neighbor","note":"OWL and RDFS can express formal class axioms while SHACL validates graphs. A taxonomy may project to them but does not inherit formal semantics unless the profile declares them."},{"target":"Metadata registry","type":"neighbor","note":"ISO/IEC 11179 defines generic registration, identification, designation, definition, classification and mapping facilities. This model specializes them for a knowledge-organization scheme."},{"target":"Vocabulary distribution and dataset","type":"neighbor","note":"DCAT, DataCite and RO-Crate distributions package or describe a release. They do not replace canonical scheme, concept or mapping identity."},{"target":"Search index","type":"neighbor","note":"An index may tokenize labels and materialize hierarchy for retrieval. Ranking, cache, deployment and query-log lifecycles remain external."},{"target":"Mapping assessment","type":"neighbor","note":"The scheme owns mapping assertions and their status, while evidence and reviewer decisions remain attributable external records. Mapping never silently merges concept identity."},{"target":"WM-XCT-020","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier for the scheme, concept, mapping, release or change assertion.","Governed globally resolvable scheme or concept IRI.","Adopting-Dimension UUID or ULID when no authoritative external identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A scheme has a namespace, a set of concepts with identifiers, labels, definitions, hierarchical relations and versioned releases.","Often confused with an ontology, a code list, a glossary and a classification binding."]},"capabilities":{"applicability":"required","items":["Register scheme: Create stable scheme identity, namespace, profile, purpose, scope, owner and initial release.","Define concept: Create or revise one concept with stable identity, definition, characteristics and scheme membership.","Manage labels and notations: Append language-tagged preferred, alternative or hidden labels, notes and typed notations.","Relate concepts: Append typed broader, narrower, related or custom semantic relations with explicit hierarchy profile.","Manage facets and collections: Create facets, arrays, collections, ordered membership and compound structures without changing concept identity.","Map schemes: Append source-qualified cross-scheme mappings with exact semantics, versions, method and confidence.","Validate scheme: Run identity, lexical, structural, mapping, quality and profile checks against a pinned release.","Review and publish change: Review a proposal, append approval or rejection and issue an immutable release and change set.","Deprecate, split, merge or replace: Append deprecation and successor relations while retaining old identifiers and affected-binding impact.","Project scheme view: Produce an authorized version-pinned standards projection with declared loss and round-trip limits."]},"hazards":{"applicability":"required","items":["Breaking changes that orphan classified records.","Wrong mappings that merge distinct concepts.","Offensive or outdated terms remaining in use.","Identifiers reused for different meanings."]},"interfaces":{"applicability":"required","items":["W3C SKOS and SKOS-XL.","ISO 25964 thesauri and interoperability.","ANSI/NISO Z39.19 controlled vocabularies.","ISO 1087 terminology work.","W3C PROV-O for change provenance."]},"context":{"applicability":"required","items":["ISO and NISO vocabulary standards, W3C linked-data vocabularies and Library of Congress authority data are complementary profiles rather than universal law.","Labels, definitions, preferred terms, mapping judgments and publication authority depend on language, community, discipline and jurisdiction.","ISO 25964 parts are under revision and licensed details require exact release pins before production conformance claims."]}},"sources":[{"title":"SKOS Simple Knowledge Organization System Reference","url":"https://www.w3.org/TR/skos-reference/","note":"World Wide Web Consortium"},{"title":"SKOS Simple Knowledge Organization System Primer","url":"https://www.w3.org/TR/skos-primer/","note":"World Wide Web Consortium"},{"title":"RDF Schema 1.1","url":"https://www.w3.org/TR/rdf-schema/","note":"World Wide Web Consortium"},{"title":"OWL 2 Web Ontology Language Structural Specification","url":"https://www.w3.org/TR/owl2-syntax/","note":"World Wide Web Consortium"},{"title":"JSON-LD 1.1","url":"https://www.w3.org/TR/json-ld11/","note":"World Wide Web Consortium"},{"title":"Shapes Constraint Language","url":"https://www.w3.org/TR/shacl/","note":"World Wide Web Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Data Quality Vocabulary","url":"https://www.w3.org/TR/vocab-dqv/","note":"World Wide Web Consortium"},{"title":"Data Catalog Vocabulary Version 3","url":"https://www.w3.org/TR/vocab-dcat-3/","note":"World Wide Web Consortium"},{"title":"Thesauri for information retrieval","url":"https://www.iso.org/standard/53657.html","note":"International Organization for Standardization"},{"title":"Interoperability with other vocabularies","url":"https://www.iso.org/standard/53658.html","note":"International Organization for Standardization"},{"title":"Terminology work principles and methods","url":"https://www.iso.org/standard/79077.html","note":"International Organization for Standardization"},{"title":"Terminology work and terminology science vocabulary","url":"https://www.iso.org/standard/62330.html","note":"International Organization for Standardization"},{"title":"Guidelines for Controlled Vocabularies","url":"https://www.niso.org/publications/ansiniso-z3919-2005-r2010","note":"National Information Standards Organization"},{"title":"DCMI Metadata Terms","url":"https://www.dublincore.org/specifications/dublin-core/dcmi-terms/","note":"Dublin Core Metadata Initiative"},{"title":"MADS/RDF Documentation","url":"https://www.loc.gov/standards/mads/rdf/","note":"Library of Congress"},{"title":"Tags for Identifying Languages","url":"https://www.rfc-editor.org/rfc/rfc5646.html","note":"Internet Engineering Task Force"},{"title":"Matching of Language Tags","url":"https://www.rfc-editor.org/rfc/rfc4647.html","note":"Internet Engineering Task Force"},{"title":"DataCite Metadata Schema","url":"https://schema.datacite.org/","note":"DataCite"},{"title":"RO-Crate Specification","url":"https://www.researchobject.org/ro-crate/specification.html","note":"RO-Crate Community"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"World Wide Web Consortium"},{"title":"Date and Time on the Internet","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"Internet Engineering Task Force"},{"title":"JSON Canonicalization Scheme","url":"https://www.rfc-editor.org/rfc/rfc8785.html","note":"Internet Engineering Task Force"},{"title":"Metadata registries common facilities","url":"https://www.iso.org/standard/78915.html","note":"International Organization for Standardization"}],"openQuestions":["Resolve whether the WM-XCT-020 Classification Binding parent signal is navigational, reversed or should be replaced by an outbound reference from the binding to the scheme.","Develop domain-specific taxonomy, thesaurus, classification, ontology, multilingual, hierarchy, facet and mapping profiles.","Pin ISO 25964 replacements and every production crosswalk to exact releases and run bidirectional conformance, inference and semantic-loss tests.","Obtain independent terminology, library science, ontology, domain, accessibility, legal, privacy, security and records review.","Domain, language, jurisdiction, legal, safety, privacy, licensing, reasoning and retention profiles require expert review.","Classified objects, classification bindings, evidence, policies, datasets, search indexes and operational workflows remain neighboring masters.","Automatic concept induction, universal mapping, ontology theorem proving and silent reassignment after taxonomy change remain future work."],"resources":{"spec":"/models/wm-knw-018-taxonomy-classification-scheme/spec.yaml","agents":"/models/wm-knw-018-taxonomy-classification-scheme/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-knw-018"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-knw-018-taxonomy-classification-scheme/spec.yaml","ver-cy/world-models/card-supplements/wm-knw-018-taxonomy-classification-scheme.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-07T09:22:01Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}