@htilabs/platform-common-models 0.20.0 → 0.21.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (53) hide show
  1. package/dist/cvcs/index.cjs +222 -120
  2. package/dist/cvcs/index.cjs.map +1 -1
  3. package/dist/cvcs/index.d.cts +223 -117
  4. package/dist/cvcs/index.d.ts +223 -117
  5. package/dist/cvcs/index.js +222 -120
  6. package/dist/cvcs/index.js.map +1 -1
  7. package/dist/enums/index.cjs.map +1 -1
  8. package/dist/enums/index.d.cts +4 -4
  9. package/dist/enums/index.d.ts +4 -4
  10. package/dist/enums/index.js.map +1 -1
  11. package/dist/{index-I-DiX9eQ.d.ts → index-CDoqrfc1.d.ts} +1 -1
  12. package/dist/{index-CoVr1jIV.d.cts → index-Zu_mOJRn.d.cts} +1 -1
  13. package/dist/index.cjs +320 -137
  14. package/dist/index.cjs.map +1 -1
  15. package/dist/index.d.cts +3 -3
  16. package/dist/index.d.ts +3 -3
  17. package/dist/index.js +319 -137
  18. package/dist/index.js.map +1 -1
  19. package/dist/information-scope/index.cjs +98 -17
  20. package/dist/information-scope/index.cjs.map +1 -1
  21. package/dist/information-scope/index.d.cts +142 -13
  22. package/dist/information-scope/index.d.ts +142 -13
  23. package/dist/information-scope/index.js +97 -17
  24. package/dist/information-scope/index.js.map +1 -1
  25. package/dist/models/index.d.cts +2 -2
  26. package/dist/models/index.d.ts +2 -2
  27. package/dist/schemas/index.d.cts +25 -25
  28. package/dist/schemas/index.d.ts +25 -25
  29. package/dist/services/index.cjs +98 -17
  30. package/dist/services/index.cjs.map +1 -1
  31. package/dist/services/index.d.cts +1 -1
  32. package/dist/services/index.d.ts +1 -1
  33. package/dist/services/index.js +97 -17
  34. package/dist/services/index.js.map +1 -1
  35. package/package.json +1 -1
  36. package/src/__tests__/__snapshots__/cvc-sot.snap +2 -2
  37. package/src/__tests__/core-information-scope-invariant.test.ts +141 -15
  38. package/src/__tests__/cvc-sot-snapshot.test.ts +4 -3
  39. package/src/__tests__/cvc-structural.test.ts +2 -2
  40. package/src/__tests__/location-type-routing-invariant.test.ts +1 -1
  41. package/src/cvcs/{coreInformationScope.v2.0.0.json → coreInformationScope.v2.1.0.json} +190 -88
  42. package/src/cvcs/index.ts +2 -2
  43. package/src/cvcs/{roiScope.v1.3.0.json → roiScope.v1.4.0.json} +26 -26
  44. package/src/generated/cvc-enums.ts +4 -4
  45. package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v3_placements.projection.csv +12 -0
  46. package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v4.migrations.csv +27 -27
  47. package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v4.rows.csv +1 -1
  48. package/src/services/__tests__/fixtures/infoscope-v4/loadInfoscopeV4Fixtures.ts +85 -14
  49. package/src/services/__tests__/informationScopeResolver.test.ts +336 -22
  50. package/src/services/informationScopeResolver.ts +226 -19
  51. package/src/services/informationScopeSot.ts +50 -8
  52. package/dist/{cvcEntry-BCj1OWqL.d.cts → cvcEntry-0BIB9sen.d.cts} +8 -8
  53. package/dist/{cvcEntry-BCj1OWqL.d.ts → cvcEntry-0BIB9sen.d.ts} +8 -8
@@ -27336,14 +27336,14 @@ var needsAssessmentChangeType_v1_0_0_default = {
27336
27336
  ]
27337
27337
  };
27338
27338
 
27339
- // src/cvcs/coreInformationScope.v2.0.0.json
27340
- var coreInformationScope_v2_0_0_default = {
27339
+ // src/cvcs/coreInformationScope.v2.1.0.json
27340
+ var coreInformationScope_v2_1_0_default = {
27341
27341
  domain: "core_information_scope",
27342
27342
  name: "Core Information Scope",
27343
- version: "2.0.0",
27343
+ version: "2.1.0",
27344
27344
  scopeVersion: 4,
27345
- _status: "DRAFT: canonical number 236, self-declared by the source YAML (`cvc_id: CVC-236`); CVC_INDEX.md carries no row for it yet, so the drift gate classifies it INDEX_ABSENT. Sourced from the canonical CVC-236 v4 tree (the categories DECIDED 2026-10-08/09, Crysta; INFOSCOPE_V4_DEV_HANDOFF_2026-10-09; the draft yaml is stamped SIGNED 2026-10-09): 115 live rows + 27 retired tombstones + 4 missingness entries. DEPTH 0-3 (canon's `depth`): 0 the top layer (System metadata \xB7 Narrative notes \xB7 Primary client / case subject \xB7 Other named persons); 1 a client category or a person type (People who caused harm \xB7 Eligible family members \xB7 Other people on the case) or a top-layer group's sub-category; 2 a client sub-category or rest row, or a person type's category; 3 an instrument row or a person type's sub-category. The four LEADS categories sit beside the top layer at depth 1. The tree is `parentCode` / `childCodes` (and `parentKey` / `childKeys`), never the code. A stored selection is a flat list of keys (handoff \xA7 2): a row is covered when it or any ancestor is listed; `shareableDefault: false` rows need enabling as well as selecting; `platformFloor` rows never leave on a share; every LIVE row is selectable except the 28 instrument rows and `identifying__other`, which are never offered on their own; `levelFloor` is the viewing side only. KEYS: a canon `.` is `__` in the key (`offenders__identifying`), the canon spelling rides on `canonicalCode` (package keys must match /^[a-z][a-z0-9_]*$/). CODES: every v1.1.0 code is byte-identical (the generator's FROZEN ledger); new rows APPEND \u2014 236-001-006 `identifying__other`, 236-006-010 `health_status`, 236-007-006 `immigration_applications`; 236-013 `instruments` (Summary & outcome -001, Full -002; instrument rows 236-013-00P-NNN, NNN the instrument's slot, the same for both parts); 236-014 `relationships_household`; 236-015 `primary_client`; 236-016 `other_named_persons` with the person types at 236-016-001/002/003 and every per-kind row MIRRORING the kind-tree row it copies (`offenders__safe_locations` = 236-016-001 + 003-002). A code is an identifier, not a tree path: the twelve published categories keep 236-001..012, the six now under `primary_client` included; `levels` name code slots, not tree depth. RETIRED TOMBSTONES (27): `ida_full` (236-002-003); `ida_consid` (236-002-004); `initial_screen` (236-002-005); `tra` (236-002-006); `lap` (236-002-007); `danger_assessment` (236-002-008); `injury_and_strangulation` (236-002-009); `stalking_assessment` (236-002-010); `ae_intake` (236-002-011); `hope_scale` (236-002-012); `assessment_records` (236-002-013); `determinations` (236-002-014); `offender_facilitator` (236-002-015); `screen_notes` (236-005-001); `background` (236-005-003); `disability_subtypes` (236-006-002); `mental_health_status` (236-006-003); `substance_use_status` (236-006-004); `chronic_health_status` (236-006-005); `hiv_status` (236-006-006); `mental_health_screen` (236-006-007); `trauma_and_coping_screen` (236-006-008); `behavioral_health_intake` (236-006-009); `uscis_alien_number` (236-007-002); `federal_protection_applications` (236-007-003); `tvap_enrollment` (236-007-004); `le_report_status` (236-007-005). Each keeps its published code and title (never reused), is `selectable: false` + `retired: true` + `status: retired`, carries no decision attributes, and names its canon SELECTION reading in `successors` (keys) / `successorCodes` (empty = includes nothing); a RESTRICTION naming it resolves through the `subtract` lines (`restrictionSuccessors`, on `offender_facilitator`). Every entry carries the tree by key too (`parentKey` / `childKeys`). MIGRATIONS: the canon v3 -> v4 from-to table is the envelope's `migrations` block, resolved at READ time, never by rewriting a stored list (handoff \xA7 3); a v2-era or unstamped list goes through canon's pinned v2 -> v3 table first (`migrations.readAt` / `unstamped`); lines that read WIDER than v3 carry `widens: true`. CROSS-CHECK: the yaml is re-walked and compared, column by column, with the generated information_scope_v4 rows and migrations CSVs; the Notion codebook is NOT cross-checked in v4 (it carries no v4 rows by design: Notion is a confirmation copy, updated after the repo). Canon enum values are carried verbatim, including three the handoff \xA7 8 list omits (rowType `branch` and `sub-category` \u2014 the exporter's label for a LEADS unit \u2014 and specialDataType `evidence`). VERSION 2.0.0 supersedes 1.1.0 (see `_supersedes`). `safe_locations` is CANON since CVC236-AUDIT R1 (Crysta, 2026-09-08). PENDING canonical Notion authoring + steward ratification.",
27346
- _source: "htilabstech/prototype/core_information_scope.v4.draft.yaml @ 615ed0b9 (CVC-236 v4, based on v3, proposed 2026-10-08); structural cross-check against htilabstech/prototype/docs/share-roi/information_scope_v4.rows.csv and docs/share-roi/information_scope_v4.migrations.csv @ 615ed0b9; 1 duplicate migration line(s) emitted once: immigration_status; v2-era readings via canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc",
27345
+ _status: "DRAFT: canonical number 236, self-declared by the source YAML (`cvc_id: CVC-236`); CVC_INDEX.md carries no row for it yet, so the drift gate classifies it INDEX_ABSENT. Sourced from the canonical CVC-236 v4 tree (the categories DECIDED 2026-10-08/09, Crysta; INFOSCOPE_V4_DEV_HANDOFF_2026-10-09; the draft yaml is stamped SIGNED 2026-10-09): 115 live rows + 27 retired tombstones + 4 missingness entries. DEPTH 0-3 (canon's `depth`): 0 the top layer (System metadata \xB7 Narrative notes \xB7 Primary client / case subject \xB7 Other named persons); 1 a client category or a person type (People who caused harm \xB7 Eligible family members \xB7 Other people on the case) or a top-layer group's sub-category; 2 a client sub-category or rest row, or a person type's category; 3 an instrument row or a person type's sub-category. The four LEADS categories sit beside the top layer at depth 1. The tree is `parentCode` / `childCodes` (and `parentKey` / `childKeys`), never the code. A stored selection is a flat list of keys (handoff \xA7 2): a row is covered when it or any ancestor is listed; `shareableDefault: false` rows need enabling as well as selecting; `platformFloor` rows never leave on a share; every LIVE row is selectable except the 28 instrument rows and `identifying__other`, which are never offered on their own; `levelFloor` is the viewing side only. KEYS: a canon `.` is `__` in the key (`offenders__identifying`), the canon spelling rides on `canonicalCode` (package keys must match /^[a-z][a-z0-9_]*$/). CODES: every v1.1.0 code is byte-identical (the generator's FROZEN ledger); new rows APPEND \u2014 236-001-006 `identifying__other`, 236-006-010 `health_status`, 236-007-006 `immigration_applications`; 236-013 `instruments` (Summary & outcome -001, Full -002; instrument rows 236-013-00P-NNN, NNN the instrument's slot, the same for both parts); 236-014 `relationships_household`; 236-015 `primary_client`; 236-016 `other_named_persons` with the person types at 236-016-001/002/003 and every per-kind row MIRRORING the kind-tree row it copies (`offenders__safe_locations` = 236-016-001 + 003-002). A code is an identifier, not a tree path: the twelve published categories keep 236-001..012, the six now under `primary_client` included; `levels` name code slots, not tree depth. RETIRED TOMBSTONES (27): `ida_full` (236-002-003); `ida_consid` (236-002-004); `initial_screen` (236-002-005); `tra` (236-002-006); `lap` (236-002-007); `danger_assessment` (236-002-008); `injury_and_strangulation` (236-002-009); `stalking_assessment` (236-002-010); `ae_intake` (236-002-011); `hope_scale` (236-002-012); `assessment_records` (236-002-013); `determinations` (236-002-014); `offender_facilitator` (236-002-015); `screen_notes` (236-005-001); `background` (236-005-003); `disability_subtypes` (236-006-002); `mental_health_status` (236-006-003); `substance_use_status` (236-006-004); `chronic_health_status` (236-006-005); `hiv_status` (236-006-006); `mental_health_screen` (236-006-007); `trauma_and_coping_screen` (236-006-008); `behavioral_health_intake` (236-006-009); `uscis_alien_number` (236-007-002); `federal_protection_applications` (236-007-003); `tvap_enrollment` (236-007-004); `le_report_status` (236-007-005). Each keeps its published code and title (never reused), is `selectable: false` + `retired: true` + `status: retired`, carries no decision attributes, and names its canon SELECTION reading in `successors` (keys) / `successorCodes` (empty = includes nothing); a RESTRICTION naming it resolves through the `subtract` lines (`restrictionSuccessors`, on `offender_facilitator`). Every entry carries the tree by key too (`parentKey` / `childKeys`). MIGRATIONS: the canon v3 -> v4 from-to table is the envelope's `migrations` block, resolved at READ time, never by rewriting a stored list (handoff \xA7 3); a v2-era or unstamped list goes through canon's pinned v2 -> v3 table first (`migrations.readAt` / `unstamped`); lines that read WIDER than v3 carry `widens: true`. RULED 2026-10-09 (Crysta, `migrations.ruling`; canon SIGNED-GRAIN): a signed release or share naming one of the nine merge-fold codes at scopeVersion 3 keeps its v3 grain (`releaseReading: retain`; the entry's `v3Fields`, read-only) and a policy or preset takes the successor with a dated version row (`policyReading: successor`); the widening identity line `immigration_status` reads as itself for every subject (`releaseReading: successor`); the `retired before v4` lines are `informational`. CROSS-CHECK: the yaml is re-walked and compared, column by column, with the generated information_scope_v4 rows and migrations CSVs; the Notion codebook is NOT cross-checked in v4 (it carries no v4 rows by design: Notion is a confirmation copy, updated after the repo). Canon enum values are carried verbatim, including three the handoff \xA7 8 list omits (rowType `branch` and `sub-category` \u2014 the exporter's label for a LEADS unit \u2014 and specialDataType `evidence`). VERSION 2.1.0 amends 2.0.0 (MINOR, additive: the release-grain fields and canon's SIGNED-GRAIN migration notes \u2014 no code, key, tree position or table `to` changed) and, like it, supersedes 1.1.0 (see `_supersedes`). `safe_locations` is CANON since CVC236-AUDIT R1 (Crysta, 2026-09-08). PENDING canonical Notion authoring + steward ratification.",
27346
+ _source: "htilabstech/prototype/core_information_scope.v4.draft.yaml @ e86dd89c (CVC-236 v4, based on v3, proposed 2026-10-08); structural cross-check against htilabstech/prototype/docs/share-roi/information_scope_v4.rows.csv and docs/share-roi/information_scope_v4.migrations.csv @ e86dd89c; 1 duplicate migration line(s) emitted once: immigration_status; v2-era readings via canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc; v3 field membership via canon's v3 field placements, htilabstech/prototype/INFOSCOPE_FIELD_PLACEMENTS_V4_2026-10-08.csv (`home_unit_today`) @ 00179edc, its domain grain checked against htilabstech/prototype/data/cvcs/core_information_scope.yaml `domain_map` @ 00179edc",
27347
27347
  _supersedes: {
27348
27348
  version: "1.1.0",
27349
27349
  keyMap: {
@@ -27423,7 +27423,7 @@ var coreInformationScope_v2_0_0_default = {
27423
27423
  },
27424
27424
  retiredCodes: [],
27425
27425
  notes: {
27426
- summary: "Every v1.1.0 key is still an entry in v2.0.0, at its v1.1.0 code, so `keyMap` is the identity and `retiredCodes` is empty: no code was withdrawn. BREAKING because 25 more published units are now RETIRED tombstones (each with its canon `successors`, notes below), the twelve published categories became selectable (v4 rule 6: select-all at any level) and six of them (identifying, risk, contact, services, health_accommodation, immigration_legal_status) gained `primary_client` as their parent, 2 categories read narrower, `appRelevance` became `apps` ({pave, thread, leads}), and every live row now carries the full v4 column set (rowType \xB7 depth \xB7 kindBranch \xB7 platformFloor \xB7 status \xB7 replacesV3). Relabelled by canon (code unchanged): `screen_indicators`, `victimization`, `health_accommodation`, `immigration_legal_status`. Added: 73 rows (status `new` in canon, plus the v3 instruments rows this package had not exported).",
27426
+ summary: "Every v1.1.0 key is still an entry in v2.1.0, at its v1.1.0 code, so `keyMap` is the identity and `retiredCodes` is empty: no code was withdrawn. BREAKING because 25 more published units are now RETIRED tombstones (each with its canon `successors`, notes below), the twelve published categories became selectable (v4 rule 6: select-all at any level) and six of them (identifying, risk, contact, services, health_accommodation, immigration_legal_status) gained `primary_client` as their parent, 2 categories read narrower, `appRelevance` became `apps` ({pave, thread, leads}), and every live row now carries the full v4 column set (rowType \xB7 depth \xB7 kindBranch \xB7 platformFloor \xB7 status \xB7 replacesV3). Relabelled by canon (code unchanged): `screen_indicators`, `victimization`, `health_accommodation`, `immigration_legal_status`. Added: 73 rows (status `new` in canon, plus the v3 instruments rows this package had not exported).",
27427
27427
  ida_full: "v1.1.0 `ida_full` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-002-003 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `full_ida`, `summary_ida` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_ida` needs `screen_indicators` AND one of `ida_full`, `ida_consid`; `full_ida` needs `ida_full` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
27428
27428
  ida_consid: "v1.1.0 `ida_consid` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-002-004 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_ida` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_ida` needs `screen_indicators` AND one of `ida_full`, `ida_consid` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
27429
27429
  initial_screen: "v1.1.0 `initial_screen` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-002-005 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_initial_screen` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_initial_screen` needs `initial_screen` AND `screen_indicators` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
@@ -27437,21 +27437,21 @@ var coreInformationScope_v2_0_0_default = {
27437
27437
  assessment_records: "v1.1.0 `assessment_records` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): The cross-instrument lifecycle lines are not share content. It stays at 236-002-013 as a tombstone (`selectable: false`, `retired: true`); a stored code includes nothing by itself (`migrations` rule `retired before v4`); in a v2-era list, read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc first, it is a CONDITION of another reading: `summary_hope_scale` needs `hope_scale` AND `assessment_records`. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
27438
27438
  determinations: "v1.1.0 `determinations` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-002-014 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_findings` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_findings` needs `victimization` AND `determinations` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
27439
27439
  offender_facilitator: "v1.1.0 `offender_facilitator` was a selectable unit. Retired 2026-10-08 (INFOSCOPE v4 rules 1-2 + ruling P2, Crysta; Phase 4 repair 2026-10-09): The offender's own record moves to Other named persons \u203A People who caused harm; the v3 unit carried identity and status/role, so it reads as those two per-kind rows. It stays at 236-002-015 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `offenders__identifying`, `offenders__risk` (selection reading, `migrations` rule `row`); a RESTRICTION naming it keeps restricting `offenders` (`subtract`, see `restrictionSuccessors`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
27440
- disability_subtypes: "v1.1.0 `disability_subtypes` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-002 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `disability_subtypes` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `hiv_status`, `mental_health_status`, `substance_use_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
27441
- mental_health_status: "v1.1.0 `mental_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-003 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `mental_health_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `hiv_status`, `substance_use_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
27442
- substance_use_status: "v1.1.0 `substance_use_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-004 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `substance_use_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `hiv_status`, `mental_health_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
27443
- chronic_health_status: "v1.1.0 `chronic_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-005 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `chronic_health_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `disability_subtypes`, `hiv_status`, `mental_health_status`, `substance_use_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
27444
- hiv_status: "v1.1.0 `hiv_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-006 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `hiv_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `mental_health_status`, `substance_use_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
27440
+ disability_subtypes: "v1.1.0 `disability_subtypes` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-002 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.has_disability`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `disability_subtypes` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `hiv_status`, `mental_health_status`, `substance_use_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
27441
+ mental_health_status: "v1.1.0 `mental_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-003 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.mental_health_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `mental_health_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `hiv_status`, `substance_use_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
27442
+ substance_use_status: "v1.1.0 `substance_use_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-004 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.substance_use_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `substance_use_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `hiv_status`, `mental_health_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
27443
+ chronic_health_status: "v1.1.0 `chronic_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-005 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.chronic_health_severity`, `capture.long_term_conditions`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `chronic_health_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `disability_subtypes`, `hiv_status`, `mental_health_status`, `substance_use_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
27444
+ hiv_status: "v1.1.0 `hiv_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-006 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.hiv_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `hiv_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `mental_health_status`, `substance_use_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
27445
27445
  mental_health_screen: "v1.1.0 `mental_health_screen` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-006-007 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_mental_health_screen` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_mental_health_screen` needs `mental_health_screen` AND `screen_indicators` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
27446
27446
  trauma_and_coping_screen: "v1.1.0 `trauma_and_coping_screen` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-006-008 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_trauma_and_coping_screen` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_trauma_and_coping_screen` needs `trauma_and_coping_screen` AND `screen_indicators` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
27447
27447
  behavioral_health_intake: "v1.1.0 `behavioral_health_intake` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-006-009 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_behavioral_health_intake` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_behavioral_health_intake` needs `behavioral_health_intake` AND `screen_indicators` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
27448
- uscis_alien_number: "v1.1.0 `uscis_alien_number` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. It stays at 236-007-002 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `immigration_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `uscis_alien_number` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_status` also carries what `immigration_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
27449
- federal_protection_applications: "v1.1.0 `federal_protection_applications` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-003 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `federal_protection_applications` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `le_report_status`, `tvap_enrollment` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
27450
- tvap_enrollment: "v1.1.0 `tvap_enrollment` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-004 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `tvap_enrollment` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `federal_protection_applications`, `le_report_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
27451
- le_report_status: "v1.1.0 `le_report_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-005 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `le_report_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `federal_protection_applications`, `tvap_enrollment` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
27448
+ uscis_alien_number: "v1.1.0 `uscis_alien_number` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. It stays at 236-007-002 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `immigration_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): it RETAINS NOTHING, no v3 field was homed on it (`v3FieldsNote`), until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `uscis_alien_number` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_status` also carries what `immigration_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
27449
+ federal_protection_applications: "v1.1.0 `federal_protection_applications` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-003 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.legal_action_type`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `federal_protection_applications` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `le_report_status`, `tvap_enrollment` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
27450
+ tvap_enrollment: "v1.1.0 `tvap_enrollment` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-004 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): it RETAINS NOTHING, no v3 field was homed on it (`v3FieldsNote`), until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `tvap_enrollment` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `federal_protection_applications`, `le_report_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
27451
+ le_report_status: "v1.1.0 `le_report_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-005 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.le_report_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `le_report_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `federal_protection_applications`, `tvap_enrollment` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
27452
27452
  risk: "v1.1.0 `risk` keeps 236-002 and reads NARROWER: canon migrations.categories maps a category-grain `risk` to `risk` only. The offender's own record (v1.1.0 `offender_facilitator`) is no longer under Risk-related; it rides Other named persons \u203A People who caused harm, hand-selected only. Canon: 'Risk-related sends the offender's name' was the 2026-10-02 defect this closes. That is the scopeVersion-3 reading. A v1.1.0 (v2-era, unstamped) category-grain `risk` is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc first, where it ALSO selects the seven risk instruments' Summary rows (`summary_initial_screen`, `summary_lap`, `summary_danger_assessment`, `summary_stalking_assessment`, `summary_injury_and_strangulation`, `summary_ae_intake`, `summary_tra`) \u2014 the content its retired per-instrument units carried \u2014 and those pass through this table unchanged.",
27453
27453
  identifying: "v1.1.0 `identifying` keeps 236-001 and reads NARROWER: canon migrations.categories maps it to `identifying` only. The relationship records, household roster, other people's person tiles, the pets and the relationship dynamic moved out (to `relationships_household`, the person's own branch, `victimization`) and are not added to a v3 category-grain selection.",
27454
- immigration_status: "v1.1.0 `immigration_status` keeps 236-007-001 and its key, but canon now homes `uscis_alien_number` on it (`replacesV3`). A stored list naming `immigration_status` ALONE now reads WIDER (`migrations` line `identity`, `widens: true`): `immigration_status` also carries what `uscis_alien_number` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta."
27454
+ immigration_status: "v1.1.0 `immigration_status` keeps 236-007-001 and its key, but canon now homes `uscis_alien_number` on it (`replacesV3`). A stored list naming `immigration_status` ALONE now reads WIDER (`migrations` line `identity`, `widens: true`): `immigration_status` also carries what `uscis_alien_number` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon leaves this identity line unmarked, and it is followed: every subject reads it as itself (`releaseReading: successor`; the line's `releaseReadingNote` states why no consent widens in practice)."
27455
27455
  }
27456
27456
  },
27457
27457
  levels: {
@@ -27469,11 +27469,26 @@ var coreInformationScope_v2_0_0_default = {
27469
27469
  unstamped: "A list with NO `scopeVersion` was written against core_information_scope <= 1.1.0 or roi_scope <= 1.2.0 and is v2-era: read it through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc first, then through this table. None was ever persisted in platform-prod or platform-dev (clean cut, 2026-10-09); the rule exists so a reader never guesses. This package ships no second table.",
27470
27470
  rules: {
27471
27471
  identity: "code unchanged; a v3 list naming it reads the same in v4",
27472
- row: "the v3 code is retired; a stored list naming it reads as the listed v4 successor(s)",
27472
+ row: "the v3 code is retired; a stored list naming it reads as the listed v4 successor(s). Canon exports a merge fold as `row (merge; signed release keeps its grain)` (`releaseReading: retain` here)",
27473
27473
  category: "a category-grain v3 selection (a purpose payload, a partner rule, a policy) reads as the listed v4 codes only \u2014 never widened",
27474
27474
  subtract: "a v3 RESTRICTION (a policy that forbids a code) keeps restricting the listed v4 rows",
27475
- "retired before v4": "a code already retired in v3, so only a v2-era list carries it: read that list through canon's v2 -> v3 table first (see `readAt`); `to` is canon's flattened v3 reading (empty = includes nothing)",
27476
- widens: "true on an identity or row line whose v4 target is also another v3 code's target: a stored list naming the `from` code ALONE reads WIDER than it did in v3. Canon's mapping is kept; the flag lets a reader gate it (consent widening, OPEN, owner Crysta)"
27475
+ "retired before v4": "a code already retired in v3, so only a v2-era list carries it: read that list through canon's v2 -> v3 table first (see `readAt`); `to` is canon's flattened v3 reading (empty = includes nothing). Every such line is `informational: true` (ruling 2 below): a v3-era list can never contain the code, and the flattened value is kept as the v3 -> v4 reading. Canon exports it as `retired before v4 (informational)`",
27476
+ widens: "true on an identity or row line whose v4 target is also another v3 code's target: a stored list naming the `from` code ALONE reads WIDER than it did in v3. Canon's mapping is kept; whether a signed release or share takes it is `releaseReading`. RULED 2026-10-09, Crysta (`ruling`)",
27477
+ releaseReading: "on every `widens` line. `retain` on canon's nine merge folds (`signed_release_grain: keep`; ruling 1): a SIGNED RELEASE, and a share (frozen at send, handoff \xA7 3), that names the `from` code at scopeVersion 3 keeps the grain it was signed at \u2014 the code is NOT mapped to `to`; the builder delivers exactly the unit's v3 field membership (`v3Fields` on the `from` entry), read-only: never offered, never widened, never narrowed. It moves to `to` only when the survivor re-signs on v4. `successor` on a widening IDENTITY line canon leaves unmarked: every subject reads `to` (`releaseReadingNote` says why). Absent = not a widening line; `to` is every subject's reading",
27478
+ policyReading: "`successor` on every `widens` line (ruling 1): a POLICY or PRESET (agency-authored, not consent) takes `to`, with a dated version row on the record (handoff \xA7 3)",
27479
+ informational: "true on every `retired before v4` line (ruling 2): the line states the code's v4 reading for completeness; only a v2-era list can carry the code"
27480
+ },
27481
+ ruling: {
27482
+ date: "2026-10-09",
27483
+ by: "Crysta",
27484
+ source: "Slack DM thread, https://htilabs-us.slack.com/archives/D0811D2R6QN/p1791581735053759?thread_ts=1791580621.618429&cid=D0811D2R6QN (16:35 CDT)",
27485
+ text: [
27486
+ "Good catch \u2014 the yaml should have declared all nine, not just HIV. Ruling: a SIGNED RELEASE keeps the grain it was signed at. A v3 release naming only mental_health_status keeps delivering exactly what mental_health_status delivered \u2014 the nine retired codes stay recognisable and the builder keeps their field membership read-only (never offered, never widened, never narrowed). It moves to health_status only when the survivor re-signs on v4. Policies and presets (agency-authored, not consent) take the merged successor with a dated version row. We'll amend the yaml's rows rule + the handoff \xA7 3 to say this explicitly.",
27487
+ "Your reading is the intended one. A v2-era list goes through v2\u2192v3 first (which carries the conjunction: lap AND screen_indicators \u2192 summary_lap), then v3\u2192v4. The retired_v3 rows are informational \u2014 they give every old code a stated v4 reading \u2014 and don't carry the condition because a v3-era list can never contain one of those codes (the v3 check rejects it). Keep the flattened value as the v3\u2192v4 reading. We'll mark those rows `informational` in the yaml so it's not ambiguous."
27488
+ ],
27489
+ applies: "ruling 1 -> `releaseReading: retain` + `policyReading: successor` on the 9 merge folds canon marks `signed_release_grain: keep`, with `v3Fields` / `v3Domains` on each retired tombstone; the 1 widening identity line(s) canon leaves unmarked (`immigration_status`) read as themselves for every subject (`releaseReading: successor`, `releaseReadingNote`), canon followed; ruling 2 -> `informational: true` on the 17 `retired before v4` lines",
27490
+ membership: "`v3Fields` is read from canon's v3 field placements, htilabstech/prototype/INFOSCOPE_FIELD_PLACEMENTS_V4_2026-10-08.csv (`home_unit_today`) @ 00179edc, never hand-typed: the fields whose v3 home is the unit. `v3Domains` is the distinct `assertion_domain` of those fields, and every one maps at CATEGORY grain in htilabstech/prototype/data/cvcs/core_information_scope.yaml `domain_map` @ 00179edc (no v3 domain_map entry names any of these units), so it is the field family, NOT the unit's membership: deliver by `v3Fields`. Units with no v3 field (`tvap_enrollment`, `uscis_alien_number`) retain nothing (`v3FieldsNote`).",
27491
+ canon: "Absorbed from canon at e86dd89c (SIGNED-GRAIN, 2026-10-09): core_information_scope.v4.draft.yaml `migrations.rows` `signed_release_grain: keep` on the nine merge folds and the header's `signed_release_grain` / INFORMATIONAL retired_v3 rules; the migrations CSV labels `row (merge; signed release keeps its grain)` / `retired before v4 (informational)`; INFOSCOPE_V4_DEV_HANDOFF_2026-10-09 \xA7 3 amended. Canon carries no v3 field lists: `v3Fields` is this package's derivation (`membership`)."
27477
27492
  },
27478
27493
  table: [
27479
27494
  {
@@ -27734,7 +27749,10 @@ var coreInformationScope_v2_0_0_default = {
27734
27749
  "236-007-001-000-000-000-000"
27735
27750
  ],
27736
27751
  note: "code unchanged",
27737
- widens: true
27752
+ widens: true,
27753
+ releaseReading: "successor",
27754
+ policyReading: "successor",
27755
+ releaseReadingNote: "2026-10-09, followed canon (SIGNED-GRAIN marks exactly the nine merge folds; the identity line is unmarked); flagged for Crysta's awareness. A signed release or share naming `immigration_status` reads as `immigration_status` (identity), like a policy. Two facts: (1) v4 homes `uscis_alien_number` on it (`replacesV3`), so the line is mechanically `widens`; (2) at v3 FIELD grain that content was already there \u2014 `uscis_alien_number`'s input is a v3 control of `capture.immigration_status`, homed on `immigration_status` (canon's v3 field placements, htilabstech/prototype/INFOSCOPE_FIELD_PLACEMENTS_V4_2026-10-08.csv (`home_unit_today`) @ 00179edc) \u2014 so a v3 release naming it delivered it, and no consent widens in practice."
27738
27756
  },
27739
27757
  {
27740
27758
  from: "screen_indicators",
@@ -28450,8 +28468,10 @@ var coreInformationScope_v2_0_0_default = {
28450
28468
  toCodes: [
28451
28469
  "236-006-010-000-000-000-000"
28452
28470
  ],
28453
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
28454
- widens: true
28471
+ note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
28472
+ widens: true,
28473
+ releaseReading: "retain",
28474
+ policyReading: "successor"
28455
28475
  },
28456
28476
  {
28457
28477
  from: "substance_use_status",
@@ -28463,8 +28483,10 @@ var coreInformationScope_v2_0_0_default = {
28463
28483
  toCodes: [
28464
28484
  "236-006-010-000-000-000-000"
28465
28485
  ],
28466
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
28467
- widens: true
28486
+ note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
28487
+ widens: true,
28488
+ releaseReading: "retain",
28489
+ policyReading: "successor"
28468
28490
  },
28469
28491
  {
28470
28492
  from: "chronic_health_status",
@@ -28476,8 +28498,10 @@ var coreInformationScope_v2_0_0_default = {
28476
28498
  toCodes: [
28477
28499
  "236-006-010-000-000-000-000"
28478
28500
  ],
28479
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
28480
- widens: true
28501
+ note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
28502
+ widens: true,
28503
+ releaseReading: "retain",
28504
+ policyReading: "successor"
28481
28505
  },
28482
28506
  {
28483
28507
  from: "disability_subtypes",
@@ -28489,8 +28513,10 @@ var coreInformationScope_v2_0_0_default = {
28489
28513
  toCodes: [
28490
28514
  "236-006-010-000-000-000-000"
28491
28515
  ],
28492
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
28493
- widens: true
28516
+ note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
28517
+ widens: true,
28518
+ releaseReading: "retain",
28519
+ policyReading: "successor"
28494
28520
  },
28495
28521
  {
28496
28522
  from: "hiv_status",
@@ -28502,8 +28528,10 @@ var coreInformationScope_v2_0_0_default = {
28502
28528
  toCodes: [
28503
28529
  "236-006-010-000-000-000-000"
28504
28530
  ],
28505
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
28506
- widens: true
28531
+ note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
28532
+ widens: true,
28533
+ releaseReading: "retain",
28534
+ policyReading: "successor"
28507
28535
  },
28508
28536
  {
28509
28537
  from: "uscis_alien_number",
@@ -28515,8 +28543,10 @@ var coreInformationScope_v2_0_0_default = {
28515
28543
  toCodes: [
28516
28544
  "236-007-001-000-000-000-000"
28517
28545
  ],
28518
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
28519
- widens: true
28546
+ note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
28547
+ widens: true,
28548
+ releaseReading: "retain",
28549
+ policyReading: "successor"
28520
28550
  },
28521
28551
  {
28522
28552
  from: "federal_protection_applications",
@@ -28528,8 +28558,10 @@ var coreInformationScope_v2_0_0_default = {
28528
28558
  toCodes: [
28529
28559
  "236-007-006-000-000-000-000"
28530
28560
  ],
28531
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
28532
- widens: true
28561
+ note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
28562
+ widens: true,
28563
+ releaseReading: "retain",
28564
+ policyReading: "successor"
28533
28565
  },
28534
28566
  {
28535
28567
  from: "tvap_enrollment",
@@ -28541,8 +28573,10 @@ var coreInformationScope_v2_0_0_default = {
28541
28573
  toCodes: [
28542
28574
  "236-007-006-000-000-000-000"
28543
28575
  ],
28544
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
28545
- widens: true
28576
+ note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
28577
+ widens: true,
28578
+ releaseReading: "retain",
28579
+ policyReading: "successor"
28546
28580
  },
28547
28581
  {
28548
28582
  from: "le_report_status",
@@ -28554,8 +28588,10 @@ var coreInformationScope_v2_0_0_default = {
28554
28588
  toCodes: [
28555
28589
  "236-007-006-000-000-000-000"
28556
28590
  ],
28557
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
28558
- widens: true
28591
+ note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
28592
+ widens: true,
28593
+ releaseReading: "retain",
28594
+ policyReading: "successor"
28559
28595
  },
28560
28596
  {
28561
28597
  from: "risk",
@@ -28608,8 +28644,9 @@ var coreInformationScope_v2_0_0_default = {
28608
28644
  "236-013-002-006-000-000-000",
28609
28645
  "236-013-001-006-000-000-000"
28610
28646
  ],
28611
- note: "via v3: full_ida summary_ida",
28612
- widens: false
28647
+ note: "via v3: full_ida summary_ida \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28648
+ widens: false,
28649
+ informational: true
28613
28650
  },
28614
28651
  {
28615
28652
  from: "ida_consid",
@@ -28621,8 +28658,9 @@ var coreInformationScope_v2_0_0_default = {
28621
28658
  toCodes: [
28622
28659
  "236-013-001-006-000-000-000"
28623
28660
  ],
28624
- note: "via v3: summary_ida",
28625
- widens: false
28661
+ note: "via v3: summary_ida \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28662
+ widens: false,
28663
+ informational: true
28626
28664
  },
28627
28665
  {
28628
28666
  from: "initial_screen",
@@ -28634,8 +28672,9 @@ var coreInformationScope_v2_0_0_default = {
28634
28672
  toCodes: [
28635
28673
  "236-013-001-001-000-000-000"
28636
28674
  ],
28637
- note: "via v3: summary_initial_screen",
28638
- widens: false
28675
+ note: "via v3: summary_initial_screen \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28676
+ widens: false,
28677
+ informational: true
28639
28678
  },
28640
28679
  {
28641
28680
  from: "tra",
@@ -28647,8 +28686,9 @@ var coreInformationScope_v2_0_0_default = {
28647
28686
  toCodes: [
28648
28687
  "236-013-001-013-000-000-000"
28649
28688
  ],
28650
- note: "via v3: summary_tra",
28651
- widens: false
28689
+ note: "via v3: summary_tra \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28690
+ widens: false,
28691
+ informational: true
28652
28692
  },
28653
28693
  {
28654
28694
  from: "lap",
@@ -28660,8 +28700,9 @@ var coreInformationScope_v2_0_0_default = {
28660
28700
  toCodes: [
28661
28701
  "236-013-001-007-000-000-000"
28662
28702
  ],
28663
- note: "via v3: summary_lap",
28664
- widens: false
28703
+ note: "via v3: summary_lap \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28704
+ widens: false,
28705
+ informational: true
28665
28706
  },
28666
28707
  {
28667
28708
  from: "danger_assessment",
@@ -28673,8 +28714,9 @@ var coreInformationScope_v2_0_0_default = {
28673
28714
  toCodes: [
28674
28715
  "236-013-001-008-000-000-000"
28675
28716
  ],
28676
- note: "via v3: summary_danger_assessment",
28677
- widens: false
28717
+ note: "via v3: summary_danger_assessment \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28718
+ widens: false,
28719
+ informational: true
28678
28720
  },
28679
28721
  {
28680
28722
  from: "injury_and_strangulation",
@@ -28686,8 +28728,9 @@ var coreInformationScope_v2_0_0_default = {
28686
28728
  toCodes: [
28687
28729
  "236-013-001-010-000-000-000"
28688
28730
  ],
28689
- note: "via v3: summary_injury_and_strangulation",
28690
- widens: false
28731
+ note: "via v3: summary_injury_and_strangulation \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28732
+ widens: false,
28733
+ informational: true
28691
28734
  },
28692
28735
  {
28693
28736
  from: "stalking_assessment",
@@ -28699,8 +28742,9 @@ var coreInformationScope_v2_0_0_default = {
28699
28742
  toCodes: [
28700
28743
  "236-013-001-009-000-000-000"
28701
28744
  ],
28702
- note: "via v3: summary_stalking_assessment",
28703
- widens: false
28745
+ note: "via v3: summary_stalking_assessment \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28746
+ widens: false,
28747
+ informational: true
28704
28748
  },
28705
28749
  {
28706
28750
  from: "ae_intake",
@@ -28712,8 +28756,9 @@ var coreInformationScope_v2_0_0_default = {
28712
28756
  toCodes: [
28713
28757
  "236-013-001-005-000-000-000"
28714
28758
  ],
28715
- note: "via v3: summary_ae_intake",
28716
- widens: false
28759
+ note: "via v3: summary_ae_intake \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28760
+ widens: false,
28761
+ informational: true
28717
28762
  },
28718
28763
  {
28719
28764
  from: "hope_scale",
@@ -28725,8 +28770,9 @@ var coreInformationScope_v2_0_0_default = {
28725
28770
  toCodes: [
28726
28771
  "236-013-001-011-000-000-000"
28727
28772
  ],
28728
- note: "via v3: summary_hope_scale",
28729
- widens: false
28773
+ note: "via v3: summary_hope_scale \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28774
+ widens: false,
28775
+ informational: true
28730
28776
  },
28731
28777
  {
28732
28778
  from: "assessment_records",
@@ -28734,8 +28780,9 @@ var coreInformationScope_v2_0_0_default = {
28734
28780
  rule: "retired before v4",
28735
28781
  to: [],
28736
28782
  toCodes: [],
28737
- note: "retired with no successor row (R30); the lifecycle lines are not share content",
28738
- widens: false
28783
+ note: "retired with no successor row (R30); the lifecycle lines are not share content \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28784
+ widens: false,
28785
+ informational: true
28739
28786
  },
28740
28787
  {
28741
28788
  from: "determinations",
@@ -28747,8 +28794,9 @@ var coreInformationScope_v2_0_0_default = {
28747
28794
  toCodes: [
28748
28795
  "236-013-001-014-000-000-000"
28749
28796
  ],
28750
- note: "via v3: summary_findings",
28751
- widens: false
28797
+ note: "via v3: summary_findings \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28798
+ widens: false,
28799
+ informational: true
28752
28800
  },
28753
28801
  {
28754
28802
  from: "mental_health_screen",
@@ -28760,8 +28808,9 @@ var coreInformationScope_v2_0_0_default = {
28760
28808
  toCodes: [
28761
28809
  "236-013-001-002-000-000-000"
28762
28810
  ],
28763
- note: "via v3: summary_mental_health_screen",
28764
- widens: false
28811
+ note: "via v3: summary_mental_health_screen \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28812
+ widens: false,
28813
+ informational: true
28765
28814
  },
28766
28815
  {
28767
28816
  from: "trauma_and_coping_screen",
@@ -28773,8 +28822,9 @@ var coreInformationScope_v2_0_0_default = {
28773
28822
  toCodes: [
28774
28823
  "236-013-001-004-000-000-000"
28775
28824
  ],
28776
- note: "via v3: summary_trauma_and_coping_screen",
28777
- widens: false
28825
+ note: "via v3: summary_trauma_and_coping_screen \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28826
+ widens: false,
28827
+ informational: true
28778
28828
  },
28779
28829
  {
28780
28830
  from: "behavioral_health_intake",
@@ -28786,8 +28836,9 @@ var coreInformationScope_v2_0_0_default = {
28786
28836
  toCodes: [
28787
28837
  "236-013-001-003-000-000-000"
28788
28838
  ],
28789
- note: "via v3: summary_behavioral_health_intake",
28790
- widens: false
28839
+ note: "via v3: summary_behavioral_health_intake \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28840
+ widens: false,
28841
+ informational: true
28791
28842
  },
28792
28843
  {
28793
28844
  from: "screen_notes",
@@ -28795,8 +28846,9 @@ var coreInformationScope_v2_0_0_default = {
28795
28846
  rule: "retired before v4",
28796
28847
  to: [],
28797
28848
  toCodes: [],
28798
- note: "retired 2026-10-05 \u2014 an Initial Screen note is an instrument note and rides full_initial_screen; a stored selection naming it includes nothing",
28799
- widens: false
28849
+ note: "retired 2026-10-05 \u2014 an Initial Screen note is an instrument note and rides full_initial_screen; a stored selection naming it includes nothing \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28850
+ widens: false,
28851
+ informational: true
28800
28852
  },
28801
28853
  {
28802
28854
  from: "background",
@@ -28804,8 +28856,9 @@ var coreInformationScope_v2_0_0_default = {
28804
28856
  rule: "retired before v4",
28805
28857
  to: [],
28806
28858
  toCodes: [],
28807
- note: "retired 2026-10-05 \u2014 nothing ever captured it (Crysta to Nate: Eliminate)",
28808
- widens: false
28859
+ note: "retired 2026-10-05 \u2014 nothing ever captured it (Crysta to Nate: Eliminate) \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
28860
+ widens: false,
28861
+ informational: true
28809
28862
  }
28810
28863
  ]
28811
28864
  },
@@ -29920,7 +29973,7 @@ var coreInformationScope_v2_0_0_default = {
29920
29973
  parentKey: "health_accommodation",
29921
29974
  childCodes: [],
29922
29975
  childKeys: [],
29923
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
29976
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.has_disability`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
29924
29977
  retired: true,
29925
29978
  status: "retired",
29926
29979
  successors: [
@@ -29929,7 +29982,13 @@ var coreInformationScope_v2_0_0_default = {
29929
29982
  successorCodes: [
29930
29983
  "236-006-010-000-000-000-000"
29931
29984
  ],
29932
- migrationRule: "row"
29985
+ migrationRule: "row",
29986
+ v3Fields: [
29987
+ "capture.has_disability"
29988
+ ],
29989
+ v3Domains: [
29990
+ "access_accommodations"
29991
+ ]
29933
29992
  },
29934
29993
  {
29935
29994
  code: "236-006-003-000-000-000-000",
@@ -29940,7 +29999,7 @@ var coreInformationScope_v2_0_0_default = {
29940
29999
  parentKey: "health_accommodation",
29941
30000
  childCodes: [],
29942
30001
  childKeys: [],
29943
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
30002
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.mental_health_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
29944
30003
  retired: true,
29945
30004
  status: "retired",
29946
30005
  successors: [
@@ -29949,7 +30008,13 @@ var coreInformationScope_v2_0_0_default = {
29949
30008
  successorCodes: [
29950
30009
  "236-006-010-000-000-000-000"
29951
30010
  ],
29952
- migrationRule: "row"
30011
+ migrationRule: "row",
30012
+ v3Fields: [
30013
+ "capture.mental_health_status"
30014
+ ],
30015
+ v3Domains: [
30016
+ "access_accommodations"
30017
+ ]
29953
30018
  },
29954
30019
  {
29955
30020
  code: "236-006-004-000-000-000-000",
@@ -29960,7 +30025,7 @@ var coreInformationScope_v2_0_0_default = {
29960
30025
  parentKey: "health_accommodation",
29961
30026
  childCodes: [],
29962
30027
  childKeys: [],
29963
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
30028
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.substance_use_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
29964
30029
  retired: true,
29965
30030
  status: "retired",
29966
30031
  successors: [
@@ -29969,7 +30034,13 @@ var coreInformationScope_v2_0_0_default = {
29969
30034
  successorCodes: [
29970
30035
  "236-006-010-000-000-000-000"
29971
30036
  ],
29972
- migrationRule: "row"
30037
+ migrationRule: "row",
30038
+ v3Fields: [
30039
+ "capture.substance_use_status"
30040
+ ],
30041
+ v3Domains: [
30042
+ "access_accommodations"
30043
+ ]
29973
30044
  },
29974
30045
  {
29975
30046
  code: "236-006-005-000-000-000-000",
@@ -29980,7 +30051,7 @@ var coreInformationScope_v2_0_0_default = {
29980
30051
  parentKey: "health_accommodation",
29981
30052
  childCodes: [],
29982
30053
  childKeys: [],
29983
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
30054
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.chronic_health_severity`, `capture.long_term_conditions`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
29984
30055
  retired: true,
29985
30056
  status: "retired",
29986
30057
  successors: [
@@ -29989,7 +30060,14 @@ var coreInformationScope_v2_0_0_default = {
29989
30060
  successorCodes: [
29990
30061
  "236-006-010-000-000-000-000"
29991
30062
  ],
29992
- migrationRule: "row"
30063
+ migrationRule: "row",
30064
+ v3Fields: [
30065
+ "capture.chronic_health_severity",
30066
+ "capture.long_term_conditions"
30067
+ ],
30068
+ v3Domains: [
30069
+ "access_accommodations"
30070
+ ]
29993
30071
  },
29994
30072
  {
29995
30073
  code: "236-006-006-000-000-000-000",
@@ -30000,7 +30078,7 @@ var coreInformationScope_v2_0_0_default = {
30000
30078
  parentKey: "health_accommodation",
30001
30079
  childCodes: [],
30002
30080
  childKeys: [],
30003
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
30081
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.hiv_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
30004
30082
  retired: true,
30005
30083
  status: "retired",
30006
30084
  successors: [
@@ -30009,7 +30087,13 @@ var coreInformationScope_v2_0_0_default = {
30009
30087
  successorCodes: [
30010
30088
  "236-006-010-000-000-000-000"
30011
30089
  ],
30012
- migrationRule: "row"
30090
+ migrationRule: "row",
30091
+ v3Fields: [
30092
+ "capture.hiv_status"
30093
+ ],
30094
+ v3Domains: [
30095
+ "access_accommodations"
30096
+ ]
30013
30097
  },
30014
30098
  {
30015
30099
  code: "236-006-007-000-000-000-000",
@@ -30177,7 +30261,7 @@ var coreInformationScope_v2_0_0_default = {
30177
30261
  parentKey: "immigration_legal_status",
30178
30262
  childCodes: [],
30179
30263
  childKeys: [],
30180
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `immigration_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
30264
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `immigration_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): it RETAINS NOTHING, no v3 field was homed on it (`v3FieldsNote`), until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
30181
30265
  retired: true,
30182
30266
  status: "retired",
30183
30267
  successors: [
@@ -30186,7 +30270,10 @@ var coreInformationScope_v2_0_0_default = {
30186
30270
  successorCodes: [
30187
30271
  "236-007-001-000-000-000-000"
30188
30272
  ],
30189
- migrationRule: "row"
30273
+ migrationRule: "row",
30274
+ v3Fields: [],
30275
+ v3Domains: [],
30276
+ v3FieldsNote: "canon's v3 field placements, htilabstech/prototype/INFOSCOPE_FIELD_PLACEMENTS_V4_2026-10-08.csv (`home_unit_today`) @ 00179edc homes NO field on `uscis_alien_number`: a signed release or share naming it RETAINS NOTHING (`v3Fields` is empty); a policy reads it as `immigration_status`. Recorded 2026-10-09, Lane E (co-o73.3); a derivation from canon's placements. Its input is a v3 control of `capture.immigration_status` (homed on `immigration_status`), so in v3 its content rode that field's unit."
30190
30277
  },
30191
30278
  {
30192
30279
  code: "236-007-003-000-000-000-000",
@@ -30197,7 +30284,7 @@ var coreInformationScope_v2_0_0_default = {
30197
30284
  parentKey: "immigration_legal_status",
30198
30285
  childCodes: [],
30199
30286
  childKeys: [],
30200
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
30287
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.legal_action_type`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
30201
30288
  retired: true,
30202
30289
  status: "retired",
30203
30290
  successors: [
@@ -30206,7 +30293,13 @@ var coreInformationScope_v2_0_0_default = {
30206
30293
  successorCodes: [
30207
30294
  "236-007-006-000-000-000-000"
30208
30295
  ],
30209
- migrationRule: "row"
30296
+ migrationRule: "row",
30297
+ v3Fields: [
30298
+ "capture.legal_action_type"
30299
+ ],
30300
+ v3Domains: [
30301
+ "immigration_legal_status"
30302
+ ]
30210
30303
  },
30211
30304
  {
30212
30305
  code: "236-007-004-000-000-000-000",
@@ -30217,7 +30310,7 @@ var coreInformationScope_v2_0_0_default = {
30217
30310
  parentKey: "immigration_legal_status",
30218
30311
  childCodes: [],
30219
30312
  childKeys: [],
30220
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
30313
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): it RETAINS NOTHING, no v3 field was homed on it (`v3FieldsNote`), until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
30221
30314
  retired: true,
30222
30315
  status: "retired",
30223
30316
  successors: [
@@ -30226,7 +30319,10 @@ var coreInformationScope_v2_0_0_default = {
30226
30319
  successorCodes: [
30227
30320
  "236-007-006-000-000-000-000"
30228
30321
  ],
30229
- migrationRule: "row"
30322
+ migrationRule: "row",
30323
+ v3Fields: [],
30324
+ v3Domains: [],
30325
+ v3FieldsNote: "canon's v3 field placements, htilabstech/prototype/INFOSCOPE_FIELD_PLACEMENTS_V4_2026-10-08.csv (`home_unit_today`) @ 00179edc homes NO field on `tvap_enrollment`: a signed release or share naming it RETAINS NOTHING (`v3Fields` is empty); a policy reads it as `immigration_applications`. Recorded 2026-10-09, Lane E (co-o73.3); a derivation from canon's placements."
30230
30326
  },
30231
30327
  {
30232
30328
  code: "236-007-005-000-000-000-000",
@@ -30237,7 +30333,7 @@ var coreInformationScope_v2_0_0_default = {
30237
30333
  parentKey: "immigration_legal_status",
30238
30334
  childCodes: [],
30239
30335
  childKeys: [],
30240
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
30336
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.le_report_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
30241
30337
  retired: true,
30242
30338
  status: "retired",
30243
30339
  successors: [
@@ -30246,7 +30342,13 @@ var coreInformationScope_v2_0_0_default = {
30246
30342
  successorCodes: [
30247
30343
  "236-007-006-000-000-000-000"
30248
30344
  ],
30249
- migrationRule: "row"
30345
+ migrationRule: "row",
30346
+ v3Fields: [
30347
+ "capture.le_report_status"
30348
+ ],
30349
+ v3Domains: [
30350
+ "immigration_legal_status"
30351
+ ]
30250
30352
  },
30251
30353
  {
30252
30354
  code: "236-007-006-000-000-000-000",
@@ -32734,13 +32836,13 @@ var coreInformationScope_v2_0_0_default = {
32734
32836
  ]
32735
32837
  };
32736
32838
 
32737
- // src/cvcs/roiScope.v1.3.0.json
32738
- var roiScope_v1_3_0_default = {
32839
+ // src/cvcs/roiScope.v1.4.0.json
32840
+ var roiScope_v1_4_0_default = {
32739
32841
  domain: "roi_scope",
32740
32842
  name: "ROI Scope",
32741
- version: "1.3.0",
32742
- _status: 'DRAFT \u2014 TEMPORARY: net-new value-CVC not yet in Notion; provisional 900+ numbering. 0.8.13: COMPLETED against the canonical 27-item source. 0.8.12 shipped 15 of the canonical 27; the missing 12 are added here. Nothing PAVE shipped was invented \u2014 this was purely a gap. Canonical source: `HTI_SHARE_SCOPE_GROUPS` in HTI-LEADS-PAVE-Thread-prototype.html @ HEAD a596eb9 (7 groups x items = 27): identifying (5) + risk (4) + contact (3) + notes (3) + health_accommodation (6) + immigration_legal_status (5) + system (1). The GROUP axis (identifying / risk / contact / notes / health_accommodation / immigration_legal_status / system) is a separate presentation concern and is deliberately NOT modelled as hierarchy rows here \u2014 this CVC is the flat item vocabulary that an ROI authorizes. PENDING canonical Notion authoring + steward ratification. VERSION 1.2.0 supersedes 1.1.0 (co-bwc): `screen_notes` (983-012) and `background` (983-014) are RETIRED TOMBSTONES, matching CVC-236 `core_information_scope` v1.1.0 (retired 2026-10-05, Narrative notes, signed Spec v2 rule 5). Each keeps its published code (never reused), is `selectable: false` + `retired: true`, and includes nothing: a stored ROI that names one resolves to "retired", not "unknown". Not additive, hence the version (ADR-CVC-0.8.13 Addendum 2026-10-05; see `_supersedes`). This flat vocabulary is LEGACY: new units (e.g. `session_summary`, 236-005-004) are minted in CVC-236 only and are not mirrored here. VERSION 1.3.0 supersedes 1.2.0: `ida_full`, `ida_consid`, `disability_subtypes`, `mental_health_status`, `substance_use_status`, `chronic_health_status`, `hiv_status`, `uscis_alien_number`, `federal_protection_applications`, `tvap_enrollment`, `le_report_status` are RETIRED TOMBSTONES too, matching CVC-236 `core_information_scope` v2.0.0 (the v4 tree: instrument-era retirements 2026-10-08, Health & accommodation and Immigration & legal status simplified 2026-10-09). Each keeps its code, is `selectable: false` + `retired: true`, and reads as its CVC-236 twin\'s `successors` (see `_supersedes`).',
32743
- _source: "htilabstech/prototype@a596eb9 HTI-LEADS-PAVE-Thread-prototype.html HTI_SHARE_SCOPE_GROUPS; v1.2.0 retirements: htilabstech/prototype/data/cvcs/core_information_scope.yaml @ 9ef79748 retired_units (L467); v1.3.0 retirements: platform-common-models coreInformationScope.v2.0.0.json (CVC-236 v4, prototype core_information_scope.v4.draft.yaml @ 615ed0b9)",
32843
+ version: "1.4.0",
32844
+ _status: 'DRAFT \u2014 TEMPORARY: net-new value-CVC not yet in Notion; provisional 900+ numbering. 0.8.13: COMPLETED against the canonical 27-item source. 0.8.12 shipped 15 of the canonical 27; the missing 12 are added here. Nothing PAVE shipped was invented \u2014 this was purely a gap. Canonical source: `HTI_SHARE_SCOPE_GROUPS` in HTI-LEADS-PAVE-Thread-prototype.html @ HEAD a596eb9 (7 groups x items = 27): identifying (5) + risk (4) + contact (3) + notes (3) + health_accommodation (6) + immigration_legal_status (5) + system (1). The GROUP axis (identifying / risk / contact / notes / health_accommodation / immigration_legal_status / system) is a separate presentation concern and is deliberately NOT modelled as hierarchy rows here \u2014 this CVC is the flat item vocabulary that an ROI authorizes. PENDING canonical Notion authoring + steward ratification. VERSION 1.2.0 supersedes 1.1.0 (co-bwc): `screen_notes` (983-012) and `background` (983-014) are RETIRED TOMBSTONES, matching CVC-236 `core_information_scope` v1.1.0 (retired 2026-10-05, Narrative notes, signed Spec v2 rule 5). Each keeps its published code (never reused), is `selectable: false` + `retired: true`, and includes nothing: a stored ROI that names one resolves to "retired", not "unknown". Not additive, hence the version (ADR-CVC-0.8.13 Addendum 2026-10-05; see `_supersedes`). This flat vocabulary is LEGACY: new units (e.g. `session_summary`, 236-005-004) are minted in CVC-236 only and are not mirrored here. VERSION 1.3.0 supersedes 1.2.0: `ida_full`, `ida_consid`, `disability_subtypes`, `mental_health_status`, `substance_use_status`, `chronic_health_status`, `hiv_status`, `uscis_alien_number`, `federal_protection_applications`, `tvap_enrollment`, `le_report_status` are RETIRED TOMBSTONES too, matching CVC-236 `core_information_scope` (the v4 tree: instrument-era retirements 2026-10-08, Health & accommodation and Immigration & legal status simplified 2026-10-09). Each keeps its code, is `selectable: false` + `retired: true`, and reads through its CVC-236 twin\'s `migrations` line (see `_supersedes`). VERSION 1.4.0 amends 1.3.0 (MINOR: readings only, no key, code or title changed) to follow CVC-236 v2.1.0: a stored ROI is a SIGNED RELEASE, so the 9 twins on a retained line (`disability_subtypes`, `mental_health_status`, `substance_use_status`, `chronic_health_status`, `hiv_status`, `uscis_alien_number`, `federal_protection_applications`, `tvap_enrollment`, `le_report_status`) keep their twin\'s v3 grain (`v3Fields`, read-only) until the survivor re-signs on v4, and a policy or preset naming the same code takes the successor with a dated version row (Crysta, 2026-10-09; CVC-236 `migrations.ruling`).',
32845
+ _source: "htilabstech/prototype@a596eb9 HTI-LEADS-PAVE-Thread-prototype.html HTI_SHARE_SCOPE_GROUPS; v1.2.0 retirements: htilabstech/prototype/data/cvcs/core_information_scope.yaml @ 9ef79748 retired_units (L467); v1.3.0 retirements and v1.4.0 readings: platform-common-models coreInformationScope.v2.1.0.json (CVC-236 v4, prototype core_information_scope.v4.draft.yaml @ e86dd89c)",
32744
32846
  _supersedes: {
32745
32847
  version: "1.2.0",
32746
32848
  keyMap: {
@@ -32778,18 +32880,18 @@ var roiScope_v1_3_0_default = {
32778
32880
  },
32779
32881
  retiredCodes: [],
32780
32882
  notes: {
32781
- summary: "Every v1.2.0 key is still an entry in v1.3.0, at its v1.2.0 code, so `keyMap` is the identity and `retiredCodes` is empty: no code was withdrawn. Non-additive because 11 more published items are now RETIRED tombstones (notes below), matching CVC-236 `core_information_scope` v2.0.0 (the v4 tree), which retired the same keys; nothing was added. Unlike the v1.2.0 pair, these tombstones are NOT empty: a stored roi_scope list is unstamped and v2-era, so it reads through canon's v2 -> v3 table first and then through the CVC-236 v2.0.0 `migrations` table (its twin's `successors`), and keeps a v4 reading. Keeps the co-bwc rule: one answer to \"is this offerable\" across both vocabularies.",
32782
- ida_full: "v1.2.0 `ida_full` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30). It stays at 983-008 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `full_ida`, `summary_ida` (rule `retired before v4`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
32783
- ida_consid: "v1.2.0 `ida_consid` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30). It stays at 983-009 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `summary_ida` (rule `retired before v4`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
32784
- disability_subtypes: "v1.2.0 `disability_subtypes` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-018 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`).",
32785
- mental_health_status: "v1.2.0 `mental_health_status` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-019 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`).",
32786
- substance_use_status: "v1.2.0 `substance_use_status` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-020 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`).",
32787
- chronic_health_status: "v1.2.0 `chronic_health_status` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-021 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`).",
32788
- hiv_status: "v1.2.0 `hiv_status` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-022 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`).",
32789
- uscis_alien_number: "v1.2.0 `uscis_alien_number` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-024 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_status` (rule `row`).",
32790
- federal_protection_applications: "v1.2.0 `federal_protection_applications` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-025 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`).",
32791
- tvap_enrollment: "v1.2.0 `tvap_enrollment` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-026 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`).",
32792
- le_report_status: "v1.2.0 `le_report_status` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-027 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`)."
32883
+ summary: "Every v1.2.0 key is still an entry, at its v1.2.0 code, so `keyMap` is the identity and `retiredCodes` is empty: no code was withdrawn. Non-additive (1.3.0) because 11 more published items are RETIRED tombstones (notes below), matching CVC-236 `core_information_scope` (the v4 tree), which retired the same keys; nothing was added. Unlike the v1.2.0 pair, these tombstones are NOT empty: a stored roi_scope list is unstamped and v2-era, so it reads through canon's v2 -> v3 table first and then through the CVC-236 v2.1.0 `migrations` table (its twin's line), and keeps a v4 reading. v1.4.0 re-words those readings for the release-grain ruling only. Keeps the co-bwc rule: one answer to \"is this offerable\" across both vocabularies.",
32884
+ ida_full: "v1.2.0 `ida_full` was a selectable item. CVC-236 retired the same key on 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30). It stays at 983-008 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `full_ida`, `summary_ida` (rule `retired before v4`, `informational`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
32885
+ ida_consid: "v1.2.0 `ida_consid` was a selectable item. CVC-236 retired the same key on 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30). It stays at 983-009 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `summary_ida` (rule `retired before v4`, `informational`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
32886
+ disability_subtypes: "v1.2.0 `disability_subtypes` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-018 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.has_disability`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`).",
32887
+ mental_health_status: "v1.2.0 `mental_health_status` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-019 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.mental_health_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`).",
32888
+ substance_use_status: "v1.2.0 `substance_use_status` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-020 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.substance_use_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`).",
32889
+ chronic_health_status: "v1.2.0 `chronic_health_status` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-021 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.chronic_health_severity`, `capture.long_term_conditions`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`).",
32890
+ hiv_status: "v1.2.0 `hiv_status` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-022 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.hiv_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`).",
32891
+ uscis_alien_number: "v1.2.0 `uscis_alien_number` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-024 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps the twin's v3 grain, which homed NO field (`v3Fields` is empty; the twin's `v3FieldsNote`): it RETAINS NOTHING, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_status` with a dated version row (`policyReading: successor`).",
32892
+ federal_protection_applications: "v1.2.0 `federal_protection_applications` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-025 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.legal_action_type`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`).",
32893
+ tvap_enrollment: "v1.2.0 `tvap_enrollment` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-026 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps the twin's v3 grain, which homed NO field (`v3Fields` is empty; the twin's `v3FieldsNote`): it RETAINS NOTHING, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`).",
32894
+ le_report_status: "v1.2.0 `le_report_status` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-027 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.le_report_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`)."
32793
32895
  }
32794
32896
  },
32795
32897
  levels: {
@@ -32907,7 +33009,7 @@ var roiScope_v1_3_0_default = {
32907
33009
  selectable: false,
32908
33010
  parentCode: null,
32909
33011
  childCodes: [],
32910
- definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.0.0 twin. Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `full_ida`, `summary_ida` (rule `retired before v4`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition). It resolves here so a reader can tell retired from unknown.",
33012
+ definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.1.0 twin. Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `full_ida`, `summary_ida` (rule `retired before v4`, `informational`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition). It resolves here so a reader can tell retired from unknown.",
32911
33013
  retired: true
32912
33014
  },
32913
33015
  {
@@ -32917,7 +33019,7 @@ var roiScope_v1_3_0_default = {
32917
33019
  selectable: false,
32918
33020
  parentCode: null,
32919
33021
  childCodes: [],
32920
- definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.0.0 twin. Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `summary_ida` (rule `retired before v4`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition). It resolves here so a reader can tell retired from unknown.",
33022
+ definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.1.0 twin. Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `summary_ida` (rule `retired before v4`, `informational`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition). It resolves here so a reader can tell retired from unknown.",
32921
33023
  retired: true
32922
33024
  },
32923
33025
  {
@@ -33001,7 +33103,7 @@ var roiScope_v1_3_0_default = {
33001
33103
  selectable: false,
33002
33104
  parentCode: null,
33003
33105
  childCodes: [],
33004
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
33106
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.has_disability`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
33005
33107
  retired: true
33006
33108
  },
33007
33109
  {
@@ -33011,7 +33113,7 @@ var roiScope_v1_3_0_default = {
33011
33113
  selectable: false,
33012
33114
  parentCode: null,
33013
33115
  childCodes: [],
33014
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
33116
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.mental_health_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
33015
33117
  retired: true
33016
33118
  },
33017
33119
  {
@@ -33021,7 +33123,7 @@ var roiScope_v1_3_0_default = {
33021
33123
  selectable: false,
33022
33124
  parentCode: null,
33023
33125
  childCodes: [],
33024
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
33126
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.substance_use_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
33025
33127
  retired: true
33026
33128
  },
33027
33129
  {
@@ -33031,7 +33133,7 @@ var roiScope_v1_3_0_default = {
33031
33133
  selectable: false,
33032
33134
  parentCode: null,
33033
33135
  childCodes: [],
33034
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
33136
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.chronic_health_severity`, `capture.long_term_conditions`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
33035
33137
  retired: true
33036
33138
  },
33037
33139
  {
@@ -33041,7 +33143,7 @@ var roiScope_v1_3_0_default = {
33041
33143
  selectable: false,
33042
33144
  parentCode: null,
33043
33145
  childCodes: [],
33044
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
33146
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.hiv_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
33045
33147
  retired: true
33046
33148
  },
33047
33149
  {
@@ -33060,7 +33162,7 @@ var roiScope_v1_3_0_default = {
33060
33162
  selectable: false,
33061
33163
  parentCode: null,
33062
33164
  childCodes: [],
33063
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
33165
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps the twin's v3 grain, which homed NO field (`v3Fields` is empty; the twin's `v3FieldsNote`): it RETAINS NOTHING, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
33064
33166
  retired: true
33065
33167
  },
33066
33168
  {
@@ -33070,7 +33172,7 @@ var roiScope_v1_3_0_default = {
33070
33172
  selectable: false,
33071
33173
  parentCode: null,
33072
33174
  childCodes: [],
33073
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`). It resolves here so a reader can tell retired from unknown.",
33175
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.legal_action_type`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
33074
33176
  retired: true
33075
33177
  },
33076
33178
  {
@@ -33080,7 +33182,7 @@ var roiScope_v1_3_0_default = {
33080
33182
  selectable: false,
33081
33183
  parentCode: null,
33082
33184
  childCodes: [],
33083
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`). It resolves here so a reader can tell retired from unknown.",
33185
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps the twin's v3 grain, which homed NO field (`v3Fields` is empty; the twin's `v3FieldsNote`): it RETAINS NOTHING, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
33084
33186
  retired: true
33085
33187
  },
33086
33188
  {
@@ -33090,7 +33192,7 @@ var roiScope_v1_3_0_default = {
33090
33192
  selectable: false,
33091
33193
  parentCode: null,
33092
33194
  childCodes: [],
33093
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`). It resolves here so a reader can tell retired from unknown.",
33195
+ definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.le_report_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
33094
33196
  retired: true
33095
33197
  }
33096
33198
  ]
@@ -49033,7 +49135,7 @@ export {
49033
49135
  coreDhState_v1_0_0_default as coreDhStateSot,
49034
49136
  coreFunctions_v1_1_0_default as coreFunctionsSot,
49035
49137
  coreIndicators_v1_1_0_default as coreIndicatorsSot,
49036
- coreInformationScope_v2_0_0_default as coreInformationScopeSot,
49138
+ coreInformationScope_v2_1_0_default as coreInformationScopeSot,
49037
49139
  coreReferralOutcome_v1_0_0_default as coreReferralOutcomeSot,
49038
49140
  countries_v1_0_0_default as countriesSot,
49039
49141
  createdBySystem_v1_0_0_default as createdBySystemSot,
@@ -49138,7 +49240,7 @@ export {
49138
49240
  riskIdentificationMilestone_v1_0_0_default as riskIdentificationMilestoneSot,
49139
49241
  riskSeverityBand_v1_0_0_default as riskSeverityBandSot,
49140
49242
  roiMethod_v1_0_0_default as roiMethodSot,
49141
- roiScope_v1_3_0_default as roiScopeSot,
49243
+ roiScope_v1_4_0_default as roiScopeSot,
49142
49244
  roiStatus_v1_0_0_default as roiStatusSot,
49143
49245
  roleContext_v1_0_0_default as roleContextSot,
49144
49246
  romanticRelationshipChangeType_v1_0_0_default as romanticRelationshipChangeTypeSot,