{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.profile.enterprise-classification-review","code":"enterprise-classification-review","url":"https://ver.cy/models/enterprise-classification-review/","name":"Enterprise Classification Review","alternateNames":["Category and code validation","Classification Review","Classifications, profiles and crosswalk","EM-XCT-09"],"kind":"enterprise-profile","status":"published","version":"0.1.0","language":"en","classifiers":{"family":"Enterprise profiles","category":"Cross-cutting context","entryKind":"companion-contract","plane":"","domain":["Enterprise","Classification","Reference data","Profiles"],"industry":["Cross-industry"],"navPath":"NAV.XCT","tags":["EM-XCT-09","classification","taxonomy","crosswalk","profile","mapping","code","review"],"facets":{}},"whatItIs":"A companion contract for a Company Dimension that reviews how company subjects are assigned to categories of pinned classification schemes, keeps crosswalks between schemes including ambiguous ones, and proposes migrations between scheme versions.","purpose":"Validate company category assignments and narrowing profiles, preserve ambiguous crosswalks, and propose version-migration candidates without changing subject identity.","scope":{"in":[],"out":[],"boundaries":[]},"distinguishingFeatures":["Reviews category assignments and crosswalks; it never changes the identity of the classified subject.","Keeps ambiguous correspondences between schemes instead of picking the most confident one.","Proposes version migrations as candidates; adopting them is a separate authorized change."],"structure":{"bundles":[{"id":"CR-B1","name":"Review context","description":"Govern review context within a bounded classification review.","layers":[{"id":"CR-L1","name":"Identity and custody","description":"Make identity and custody explicit through evidence and checks.","findings":[{"id":"CR-F1","name":"Packet identity","description":"Sealed packet. Assemble a new immutable revision under the host owner.","questions":[{"text":"Which local review is this?","id":"CR-Q1","kind":"evidence"},{"text":"Which revision and previous content digest does it preserve?","id":"CR-Q2","kind":"decision"}]},{"id":"CR-F2","name":"Source sovereignty","description":"Source and capture inventory. Reference original authorities and retain capture provenance.","questions":[{"text":"Who owns the scheme, binding and correspondence meanings?","id":"CR-Q3","kind":"evidence"},{"text":"Which copies are explicitly snapshots?","id":"CR-Q4","kind":"decision"}]},{"id":"CR-F3","name":"Read authority","description":"Host context. Ask the host for a current scoped context; never self-authorize.","questions":[{"text":"Which authenticated actor may read the complete packet for this purpose?","id":"CR-Q5","kind":"evidence"},{"text":"Does the independent grant match exact packet bytes and current interval?","id":"CR-Q6","kind":"decision"}]}]},{"id":"CR-L2","name":"Integrity and time","description":"Make integrity and time explicit through evidence and checks.","findings":[{"id":"CR-F4","name":"Byte integrity","description":"Integrity checks. Verify frozen bytes and ask the custodian about external authenticity.","questions":[{"text":"Do local snapshot digests match the captured envelopes?","id":"CR-Q7","kind":"evidence"},{"text":"What does the separately declared source digest actually prove?","id":"CR-Q8","kind":"decision"}]},{"id":"CR-F5","name":"Time frames","description":"Temporal frame table. Keep assertion, validity, capture and assessment clocks separate.","questions":[{"text":"What was known at the knowledge cut?","id":"CR-Q9","kind":"evidence"},{"text":"Which effective and target instants are being assessed?","id":"CR-Q10","kind":"decision"}]}]}]},{"id":"CR-B2","name":"Profiles and categories","description":"Govern profiles and categories within a bounded classification review.","layers":[{"id":"CR-L3","name":"Release membership","description":"Make release membership explicit through evidence and checks.","findings":[{"id":"CR-F6","name":"Qualified codes","description":"Qualified category set. Preserve exact strings; obtain missing qualifications.","questions":[{"text":"Which publisher scheme and release qualify this lexical code?","id":"CR-Q11","kind":"evidence"},{"text":"Could an identical label or code belong to another scheme?","id":"CR-Q12","kind":"decision"}]},{"id":"CR-F7","name":"Complete enumeration","description":"Completeness statement. Return insufficient-context when closure cannot be established.","questions":[{"text":"Is the frozen enumeration complete for this review?","id":"CR-Q13","kind":"evidence"},{"text":"Who verifies absent codes and missing expansions?","id":"CR-Q14","kind":"decision"}]},{"id":"CR-F8","name":"Historical selectability","description":"Historical and target checks. Preserve history and assess new eligibility independently.","questions":[{"text":"Was the recorded category valid at the effective instant?","id":"CR-Q15","kind":"evidence"},{"text":"Is it active and selectable for a new target assignment?","id":"CR-Q16","kind":"decision"}]}]},{"id":"CR-L4","name":"Profile restriction","description":"Make profile restriction explicit through evidence and checks.","findings":[{"id":"CR-F9","name":"Identity-preserving restriction","description":"Profile ancestry assessment. Refuse changed meaning or version as a disguised restriction.","questions":[{"text":"Does the child retain class, unit, slot and meaning?","id":"CR-Q17","kind":"evidence"},{"text":"Are parent and release pins exact?","id":"CR-Q18","kind":"decision"}]},{"id":"CR-F10","name":"Set and cardinality restriction","description":"Restriction and coverage findings. Inspect affected subjects before adopting narrower rules.","questions":[{"text":"Does the child only remove values and tighten counts?","id":"CR-Q19","kind":"evidence"},{"text":"Does removing categories leave subjects unclassifiable?","id":"CR-Q20","kind":"decision"}]}]}]},{"id":"CR-B3","name":"Assignments and correspondence","description":"Govern assignments and correspondence within a bounded classification review.","layers":[{"id":"CR-L5","name":"Assignment evidence","description":"Make assignment evidence explicit through evidence and checks.","findings":[{"id":"CR-F11","name":"Assertion versus suggestion","description":"Assignment snapshot. Retain stated origin and ask the source owner to resolve status.","questions":[{"text":"Is this an asserted, proposed, disputed or withdrawn source?","id":"CR-Q21","kind":"evidence"},{"text":"What method/version produced model suggestions?","id":"CR-Q22","kind":"decision"}]},{"id":"CR-F12","name":"Competing revisions","description":"Source selection decision. Keep competing revisions and request explicit host selection.","questions":[{"text":"Which single source assertion is authoritative for this review?","id":"CR-Q23","kind":"evidence"},{"text":"Is a correction preserved without editing its predecessor?","id":"CR-Q24","kind":"decision"}]}]},{"id":"CR-L6","name":"Correspondence evidence","description":"Make correspondence evidence explicit through evidence and checks.","findings":[{"id":"CR-F13","name":"Mapping meaning","description":"Captured correspondence. Keep n:m associations intact; never invent pairwise exactness.","questions":[{"text":"Is the relation exact, close, broader, narrower, related or compound?","id":"CR-Q25","kind":"evidence"},{"text":"Are multiple or empty sides preserved as one association?","id":"CR-Q26","kind":"decision"}]},{"id":"CR-F14","name":"Mapping authority","description":"Approval basis. Obtain independent acknowledgment; score is not approval.","questions":[{"text":"Who approved the exact snapshot/entry and on what evidence?","id":"CR-Q27","kind":"evidence"},{"text":"Does the host acknowledgment match after a changed snapshot?","id":"CR-Q28","kind":"decision"}]},{"id":"CR-F15","name":"Competing targets","description":"Alternative eligibility table. Route ambiguity to a steward without ranking by confidence.","questions":[{"text":"Are all applicable alternatives visible before profile filtering?","id":"CR-Q29","kind":"evidence"},{"text":"Does exclusion of one target conceal an unresolved conflict?","id":"CR-Q30","kind":"decision"}]}]}]},{"id":"CR-B4","name":"Assessment and adoption","description":"Govern assessment and adoption within a bounded classification review.","layers":[{"id":"CR-L7","name":"Disposition and limits","description":"Make disposition and limits explicit through evidence and checks.","findings":[{"id":"CR-F16","name":"Bounded migration candidate","description":"Candidate or refusal. Propose only; use a separate authorized workflow for any business change.","questions":[{"text":"Is there one eligible direct target under complete declared context?","id":"CR-Q31","kind":"evidence"},{"text":"Would a chain or a model-ID replacement exceed this contract?","id":"CR-Q32","kind":"decision"}]},{"id":"CR-F17","name":"Reproducible assessment","description":"Assessment snapshot. Recompute consistency and preserve distinct assessment identities.","questions":[{"text":"Can the exact evaluator reproduce the saved result?","id":"CR-Q33","kind":"evidence"},{"text":"Did input, approval basis or build change?","id":"CR-Q34","kind":"decision"}]}]},{"id":"CR-L8","name":"Native use and migration","description":"Make native use and migration explicit through evidence and checks.","findings":[{"id":"CR-F18","name":"Native binding and disclosure","description":"Native installation report. Validate separately and keep host disclosure controls.","questions":[{"text":"Were both outer V3 and installed nested validation run?","id":"CR-Q35","kind":"evidence"},{"text":"Does the restricted aggregate disclose only what its owner permits?","id":"CR-Q36","kind":"decision"}]},{"id":"CR-F19","name":"Version and records lifecycle","description":"Loss/refusal and retention decision. Refuse unsupported conversion; preserve the original sealed record.","questions":[{"text":"Can an older version preserve all meanings and evidence?","id":"CR-Q37","kind":"evidence"},{"text":"Who retains superseded packets and records repeated imports?","id":"CR-Q38","kind":"decision"}]}]}]}]},"agentConduct":{"may":["Validate an assignment against the pinned scheme and version.","List affected subjects before a narrower profile is adopted.","Route an ambiguous crosswalk to a steward with all candidates kept."],"mustNot":["Self-authorize a review context; it must come from the host.","Rank ambiguous mappings by confidence and keep only the top one.","Disguise a change of meaning as a restriction.","Treat a review score as approval."],"requiresHuman":["Selecting between competing revisions of a classification.","Adopting a migration that changes business reporting."]},"ethics":{"considerations":["Classifications of people, products or risks drive decisions; a silent reclassification can treat someone unfairly.","Keeping old assignments as history protects people from retroactive relabelling."],"affectedParties":["People and organizations whose records are classified","Teams whose reports depend on the classification"]},"owners":{"steward":"The reference data steward owns category schemes and profiles; subject records stay with their domain owners.","roles":[],"masterSystems":["Reference data management system","Scheme publishers (for example statistical or industry classification bodies)"]},"relations":[{"target":"WM-KNW-018","type":"references","note":"0.3.0-research.1"},{"target":"WM-XCT-020","type":"references","note":"0.3.0-research.1"},{"target":"vr.wm-knw-018","type":"aligned"},{"target":"vr.wm-xct-020","type":"aligned"}],"interaction":{"identity":{"applicability":"required","items":["Scheme ID and version pinned for every assignment.","Immutable revision ID for each profile."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["An assignment links one subject to one category of a pinned scheme version, with evidence and assessment."]},"capabilities":{"applicability":"required","items":["Assemble a new immutable revision under the host owner. Host permission and source verification remain required.","Reference original authorities and retain capture provenance. Host permission and source verification remain required.","Ask the host for a current scoped context; never self-authorize. Host permission and source verification remain required.","Verify frozen bytes and ask the custodian about external authenticity. Host permission and source verification remain required.","Keep assertion, validity, capture and assessment clocks separate. Host permission and source verification remain required.","Preserve exact strings; obtain missing qualifications. Host permission and source verification remain required.","Return insufficient-context when closure cannot be established. Host permission and source verification remain required.","Preserve history and assess new eligibility independently. Host permission and source verification remain required.","Refuse changed meaning or version as a disguised restriction. Host permission and source verification remain required.","Inspect affected subjects before adopting narrower rules. Host permission and source verification remain required.","Retain stated origin and ask the source owner to resolve status. Host permission and source verification remain required.","Keep competing revisions and request explicit host selection. Host permission and source verification remain required.","Keep n:m associations intact; never invent pairwise exactness. Host permission and source verification remain required.","Obtain independent acknowledgment; score is not approval. Host permission and source verification remain required.","Route ambiguity to a steward without ranking by confidence. Host permission and source verification remain required.","Propose only; use a separate authorized workflow for any business change. Host permission and source verification remain required.","Recompute consistency and preserve distinct assessment identities. Host permission and source verification remain required.","Validate separately and keep host disclosure controls. Host permission and source verification remain required.","Refuse unsupported conversion; preserve the original sealed record. Host permission and source verification remain required."]},"hazards":{"applicability":"required","items":["Silent semantic drift when a scheme version changes.","Lost nuance when an n-to-m crosswalk is forced to 1-to-1."]},"interfaces":{"applicability":"required","items":["W3C SKOS mapping relations.","Statistical classifications such as ISIC and NACE."]},"context":{"applicability":"required","items":["Used when company data is classified for reporting, compliance or analytics."]}},"sources":[{"title":"Research record EM-XCT-09: independent provider studies, audits and reconciled findings","url":"https://ver.cy/enterprise/research/em-xct-09/","note":"Evidence behind the release; claims in the card trace to it."},{"title":"Enterprise Classification Review 0.1.0 specification","url":"https://ver.cy/models/enterprise-classification-review/versions/0.1.0/spec.json","note":"Normative release, digest sha256:438269d5af6ec4dbec31b3fc3637421987198bb54a1aa307defe915b3c1ba7b9"}],"openQuestions":["Use the pinned companion schema/validator and trusted-host binding. Native outer validation alone does not enforce nested semantics. Consult the released adoption limits. Use only with a complete frozen scheme release, an exact finite profile and independently authorized host context. Preserve every applicable correspondence before profile filtering. Treat candidate-only as a proposal; read the capacity, custody and native-binding limits before installation. Required reading: https://ver.cy/models/enterprise-classification-review/versions/0.1.0/publication-addendum.md"],"resources":{"spec":"/models/enterprise-classification-review/versions/0.1.0/spec.json","agents":"/models/enterprise-classification-review/versions/0.1.0/AGENTS.md","package":"/models/enterprise-classification-review/versions/0.1.0/enterprise-classification-review-0.1.0.zip","source":"https://ver.cy/enterprise/research/em-xct-09/"},"provenance":{"origin":"enterprise research","builtFrom":["models/enterprise-classification-review/versions/0.1.0/spec.json","models/enterprise-classification-review/catalogue-entry.json","ver-cy/world-models/card-supplements/enterprise-classification-review.json"],"providers":["Claude","Grok"],"researchStatus":"reviewable-draft","generatedAt":"","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: it has no physical body to measure.","_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}}