{
  "format": "vercy-enterprise-profile-fixtures/v1",
  "profileName": "Enterprise Document, Knowledge and Terminology",
  "cases": [
    {
      "id": "url-move",
      "kind": "positive",
      "input": "An unchanged record moves to a new URL.",
      "expect": "Record and version identity persist; only the location or instantiation changes."
    },
    {
      "id": "format-migration-preserved",
      "kind": "positive",
      "input": "A migration creates a new format while all declared significant properties remain unchanged.",
      "expect": "A new instantiation with provenance and digest remains attached to the same record version."
    },
    {
      "id": "transformative-migration",
      "kind": "positive",
      "input": "A migration changes a declared significant content property.",
      "expect": "A fixing event creates a new immutable record version without renumbering history."
    },
    {
      "id": "same-word-different-fields",
      "kind": "positive",
      "input": "The same word appears in two distinct subject fields with different essential characteristics.",
      "expect": "Distinct concept IRIs remain; lexical equality establishes no identity."
    },
    {
      "id": "same-intension-conflicting-definitions",
      "kind": "positive",
      "input": "Two authorities publish conflicting definitions for the same intension.",
      "expect": "One concept may retain both sourced contextual definitions with language, status, access and dispute state."
    },
    {
      "id": "different-intension",
      "kind": "positive",
      "input": "Two definitions use one label but differ in essential characteristics.",
      "expect": "Distinct concepts are required and may be related only by an authorized mapping."
    },
    {
      "id": "exact-release-classification",
      "kind": "positive",
      "input": "A record classification identifies the subject, concept IRI, scheme IRI and exact release.",
      "expect": "WM-XCT-020 owns a reproducible binding; any copied label is display-only."
    },
    {
      "id": "scheme-less-concept",
      "kind": "positive",
      "input": "A concept exists before joining a scheme and is later withdrawn from one release.",
      "expect": "Concept identity persists with zero memberships; entry and withdrawal remain release-local assertions."
    },
    {
      "id": "global-retirement-versus-local-withdrawal",
      "kind": "positive",
      "input": "One scheme withdraws an active concept and the concept is later globally retired.",
      "expect": "The local withdrawal and global tombstoned retirement remain separate events with separate masters."
    },
    {
      "id": "scheme-local-preference",
      "kind": "positive",
      "input": "Different schemes prefer different designations for one concept.",
      "expect": "The designation inventory stays concept-owned while each preference is owned by its pinned scheme release."
    },
    {
      "id": "scope-note-versus-definition",
      "kind": "positive",
      "input": "A scheme publishes a scope note that narrows use without changing concept intension.",
      "expect": "The scope note remains release-owned and cannot overwrite the intrinsic concept definition."
    },
    {
      "id": "label-only-classification",
      "kind": "negative",
      "input": "A record is classified using only a display label.",
      "expect": "The classification is rejected because concept, scheme and exact release pins are absent."
    },
    {
      "id": "digest-equals-identity",
      "kind": "negative",
      "input": "Matching bytes are treated as proof that two records or concepts are identical.",
      "expect": "The identity inference is rejected."
    },
    {
      "id": "dual-editable-master",
      "kind": "negative",
      "input": "Concept and scheme stores both edit the same membership or hierarchy assertion.",
      "expect": "Validation rejects dual mastership and requires one release-owned assertion plus derived views."
    },
    {
      "id": "identifier-reuse",
      "kind": "negative",
      "input": "A retired concept identifier is silently repointed to a new meaning.",
      "expect": "Validation rejects reuse and requires the original tombstone and an explicitly new identifier."
    },
    {
      "id": "concept-merge-split",
      "kind": "positive",
      "input": "A concept is merged or split after use in published releases.",
      "expect": "New concept lifecycle assertions preserve old tombstones and identifiers; published release assertions remain immutable and successors pin new identities."
    },
    {
      "id": "mapping-both-releases",
      "kind": "positive",
      "input": "A mapping relates concepts across two schemes.",
      "expect": "One source-release-owned mapping assertion pins exact source and target releases; the target view is derived and read-only."
    },
    {
      "id": "re-entry-after-withdrawal",
      "kind": "positive",
      "input": "A concept withdrawn in one release re-enters a later release.",
      "expect": "Both release-local assertions remain append-only and concept identity stays unchanged."
    },
    {
      "id": "licensed-definition",
      "kind": "positive",
      "input": "A definition is licensed for a restricted audience.",
      "expect": "Concept identity remains visible as permitted while definition content obeys its own access scope."
    },
    {
      "id": "digest-mismatch",
      "kind": "negative",
      "input": "A stored instantiation digest no longer matches and the system silently rewrites it.",
      "expect": "Validation rejects silent repair and requires an integrity event with retained prior evidence."
    },
    {
      "id": "release-renumber-or-repoint",
      "kind": "negative",
      "input": "A published scheme release is renumbered or its identifier is repointed.",
      "expect": "Validation rejects mutation and requires an append-only successor release."
    },
    {
      "id": "dispute-as-deprecation",
      "kind": "negative",
      "input": "A disputed definition automatically deprecates or redirects its concept.",
      "expect": "Validation rejects the inference; dispute, deprecation and redirect are distinct."
    },
    {
      "id": "supersession-destroys",
      "kind": "negative",
      "input": "A superseded record or concept is destroyed solely because a successor exists.",
      "expect": "Validation rejects destruction without separate retention and disposition authority."
    },
    {
      "id": "contradictory-scope-note",
      "kind": "negative",
      "input": "A scheme note contradicts the concept's intrinsic intension.",
      "expect": "Validation rejects the note as a scope refinement and requires a distinct concept or governed correction."
    }
  ]
}