@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
package/src/cvcs/index.ts CHANGED
@@ -164,8 +164,8 @@ import romanticRelationshipChangeTypeSot from "./romanticRelationshipChangeType.
164
164
  import riskCategorySot from "./riskCategory.v1.0.0.json" with { type: "json" };
165
165
  import coreFunctionsSot from "./coreFunctions.v1.1.0.json" with { type: "json" };
166
166
  import needsAssessmentChangeTypeSot from "./needsAssessmentChangeType.v1.0.0.json" with { type: "json" };
167
- import coreInformationScopeSot from "./coreInformationScope.v2.0.0.json" with { type: "json" };
168
- import roiScopeSot from "./roiScope.v1.3.0.json" with { type: "json" };
167
+ import coreInformationScopeSot from "./coreInformationScope.v2.1.0.json" with { type: "json" };
168
+ import roiScopeSot from "./roiScope.v1.4.0.json" with { type: "json" };
169
169
  import roiStatusSot from "./roiStatus.v1.0.0.json" with { type: "json" };
170
170
  import coreReferralOutcomeSot from "./coreReferralOutcome.v1.0.0.json" with { type: "json" };
171
171
  import coreIndicatorsSot from "./coreIndicators.v1.1.0.json" with { type: "json" };
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "domain": "roi_scope",
3
3
  "name": "ROI Scope",
4
- "version": "1.3.0",
5
- "_status": "DRAFT — 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 — 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 — 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`).",
6
- "_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)",
4
+ "version": "1.4.0",
5
+ "_status": "DRAFT — 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 — 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 — 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`).",
6
+ "_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)",
7
7
  "_supersedes": {
8
8
  "version": "1.2.0",
9
9
  "keyMap": {
@@ -41,18 +41,18 @@
41
41
  },
42
42
  "retiredCodes": [],
43
43
  "notes": {
44
- "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.",
45
- "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`) — canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
46
- "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`) — canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
47
- "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 § 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`).",
48
- "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 § 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`).",
49
- "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 § 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`).",
50
- "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 § 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`).",
51
- "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 § 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`).",
52
- "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 § 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`).",
53
- "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 § 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`).",
54
- "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 § 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`).",
55
- "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 § 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`)."
44
+ "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.",
45
+ "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`) — canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
46
+ "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`) — canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
47
+ "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 § 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`).",
48
+ "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 § 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`).",
49
+ "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 § 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`).",
50
+ "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 § 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`).",
51
+ "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 § 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`).",
52
+ "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 § 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`).",
53
+ "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 § 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`).",
54
+ "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 § 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`).",
55
+ "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 § 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`)."
56
56
  }
57
57
  },
58
58
  "levels": {
@@ -170,7 +170,7 @@
170
170
  "selectable": false,
171
171
  "parentCode": null,
172
172
  "childCodes": [],
173
- "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`) — 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.",
173
+ "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`) — 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.",
174
174
  "retired": true
175
175
  },
176
176
  {
@@ -180,7 +180,7 @@
180
180
  "selectable": false,
181
181
  "parentCode": null,
182
182
  "childCodes": [],
183
- "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`) — 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.",
183
+ "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`) — 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.",
184
184
  "retired": true
185
185
  },
186
186
  {
@@ -264,7 +264,7 @@
264
264
  "selectable": false,
265
265
  "parentCode": null,
266
266
  "childCodes": [],
267
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
267
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
268
268
  "retired": true
269
269
  },
270
270
  {
@@ -274,7 +274,7 @@
274
274
  "selectable": false,
275
275
  "parentCode": null,
276
276
  "childCodes": [],
277
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
277
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
278
278
  "retired": true
279
279
  },
280
280
  {
@@ -284,7 +284,7 @@
284
284
  "selectable": false,
285
285
  "parentCode": null,
286
286
  "childCodes": [],
287
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
287
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
288
288
  "retired": true
289
289
  },
290
290
  {
@@ -294,7 +294,7 @@
294
294
  "selectable": false,
295
295
  "parentCode": null,
296
296
  "childCodes": [],
297
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
297
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
298
298
  "retired": true
299
299
  },
300
300
  {
@@ -304,7 +304,7 @@
304
304
  "selectable": false,
305
305
  "parentCode": null,
306
306
  "childCodes": [],
307
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
307
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
308
308
  "retired": true
309
309
  },
310
310
  {
@@ -323,7 +323,7 @@
323
323
  "selectable": false,
324
324
  "parentCode": null,
325
325
  "childCodes": [],
326
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
326
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
327
327
  "retired": true
328
328
  },
329
329
  {
@@ -333,7 +333,7 @@
333
333
  "selectable": false,
334
334
  "parentCode": null,
335
335
  "childCodes": [],
336
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
336
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
337
337
  "retired": true
338
338
  },
339
339
  {
@@ -343,7 +343,7 @@
343
343
  "selectable": false,
344
344
  "parentCode": null,
345
345
  "childCodes": [],
346
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
346
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
347
347
  "retired": true
348
348
  },
349
349
  {
@@ -353,7 +353,7 @@
353
353
  "selectable": false,
354
354
  "parentCode": null,
355
355
  "childCodes": [],
356
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
356
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
357
357
  "retired": true
358
358
  }
359
359
  ]
@@ -4102,9 +4102,9 @@ export const NeedsAssessmentChangeTypeKeys = {
4102
4102
  export type NeedsAssessmentChangeTypeKey = keyof typeof NeedsAssessmentChangeTypeKeys;
4103
4103
 
4104
4104
  /**
4105
- * Key → positional code map for the `core_information_scope` CVC domain (DRAFT-TEMPORARY; canonical CVC-236 v4 tree, SOT v2.0.0: 115 live rows + 27 RETIRED tombstones. Canon depth 0–3 — top layer (System metadata · Narrative notes · Primary client · Other named persons), then client category / person type, then sub-category / a person type's category, then instrument row / a person type's sub-category — read off parentCode / parentKey, NOT the code: every v1.1.0 code is unchanged and new rows append. A canon `.` is `__` in the key (`offenders__identifying`; canon spelling on `canonicalCode`). Every LIVE row but the 28 instrument rows and `identifying__other` is selectable (select-all at any level); detect a category by `rowType`, not `selectable`. Tombstones keep their codes so a stored value resolves, are `selectable: false` + `retired: true`, and name their SELECTION reading in `successors` (a restriction resolves via the `subtract` lines: `restrictionSuccessors`); the envelope `migrations` block is the v3 → v4 from-to table, applied at READ time (a v2-era or unstamped list goes through canon's v2 → v3 table first; `widens: true` marks readings wider than v3). Distinct from the sibling `roi_scope` domain, the LEGACY flat item vocabulary: every one of its 27 substantive keys is an entry here, spelled identically)
4105
+ * Key → positional code map for the `core_information_scope` CVC domain (DRAFT-TEMPORARY; canonical CVC-236 v4 tree, SOT v2.1.0: 115 live rows + 27 RETIRED tombstones. Canon depth 0–3 — top layer (System metadata · Narrative notes · Primary client · Other named persons), then client category / person type, then sub-category / a person type's category, then instrument row / a person type's sub-category — read off parentCode / parentKey, NOT the code: every v1.1.0 code is unchanged and new rows append. A canon `.` is `__` in the key (`offenders__identifying`; canon spelling on `canonicalCode`). Every LIVE row but the 28 instrument rows and `identifying__other` is selectable (select-all at any level); detect a category by `rowType`, not `selectable`. Tombstones keep their codes so a stored value resolves, are `selectable: false` + `retired: true`, and name their SELECTION reading in `successors` (a restriction resolves via the `subtract` lines: `restrictionSuccessors`); the envelope `migrations` block is the v3 → v4 from-to table, applied at READ time (a v2-era or unstamped list goes through canon's v2 → v3 table first; `widens: true` marks readings wider than v3; on those lines `releaseReading` says whether a signed release or share keeps the code's v3 grain (`retain`: the tombstone's `v3Fields`, read-only) or reads its successor, and `policyReading: successor` that a policy or preset takes the successor with a dated version row). Distinct from the sibling `roi_scope` domain, the LEGACY flat item vocabulary: every one of its 27 substantive keys is an entry here, spelled identically)
4106
4106
  *
4107
- * Domain: `core_information_scope` · Version: 2.0.0 · Entries: 146
4107
+ * Domain: `core_information_scope` · Version: 2.1.0 · Entries: 146
4108
4108
  */
4109
4109
  export const CoreInformationScopeKeys = {
4110
4110
  missingness_root: "236-000-000-000-000-000-000",
@@ -4258,9 +4258,9 @@ export const CoreInformationScopeKeys = {
4258
4258
  export type CoreInformationScopeKey = keyof typeof CoreInformationScopeKeys;
4259
4259
 
4260
4260
  /**
4261
- * Key → positional code map for the `roi_scope` CVC domain (DRAFT-TEMPORARY; LEGACY flat item vocabulary, superseded for new work by `core_information_scope` (CVC-236). 27 ROI scope ITEMS: 14 live + 13 RETIRED tombstones, each matching its CVC-236 twin (`screen_notes`, `background` retired 2026-10-05 and include nothing; 11 more retired by the CVC-236 v4 tree, SOT v2.0.0, each reading as its twin's `successors`). Tombstones keep their codes so a stored value resolves, but are `selectable: false` + `retired: true` — never offer them. The item axis only — named bundles over these items are ROI_SCOPE_PRESET_NAMES).
4261
+ * Key → positional code map for the `roi_scope` CVC domain (DRAFT-TEMPORARY; LEGACY flat item vocabulary, superseded for new work by `core_information_scope` (CVC-236). 27 ROI scope ITEMS: 14 live + 13 RETIRED tombstones, each matching its CVC-236 twin (`screen_notes`, `background` retired 2026-10-05 and include nothing; 11 more retired by the CVC-236 v4 tree, each read through its twin's CVC-236 SOT v2.1.0 `migrations` line: a stored ROI is a signed release, so the 9 health / immigration twins keep the twin's v3 grain (`v3Fields`, read-only) while a policy or preset takes the successor; `ida_full` / `ida_consid` read as their twin's informational line). Tombstones keep their codes so a stored value resolves, but are `selectable: false` + `retired: true` — never offer them. The item axis only — named bundles over these items are ROI_SCOPE_PRESET_NAMES).
4262
4262
  *
4263
- * Domain: `roi_scope` · Version: 1.3.0 · Entries: 31
4263
+ * Domain: `roi_scope` · Version: 1.4.0 · Entries: 31
4264
4264
  */
4265
4265
  export const RoiScopeKeys = {
4266
4266
  missingness_root: "983-000-000-000-000-000-000",
@@ -0,0 +1,12 @@
1
+ # source: htilabstech/prototype INFOSCOPE_FIELD_PLACEMENTS_V4_2026-10-08.csv @ 00179edcb3f0c00a8b55beeffd1618c8a5c98937 (blob 9c10b39d4dfabc0b4c72fb8f7011415710ab29ff, unchanged at 7ca7e586) — PROJECTION: columns field assertion_domain home_category_today home_unit_today home_grain_today controls of every row homed on, or with a control naming, one of the ten widening units; regenerate with the command in loadInfoscopeV4Fixtures.ts, never hand-edit (the test checks this body's git blob hash)
2
+ field,assertion_domain,home_category_today,home_unit_today,home_grain_today,controls
3
+ capture.legal_action_type,immigration_legal_status,immigration_legal_status,federal_protection_applications,unit,js:legalActionModalView:#la-activated-at|js:legalActionModalView:#la-applied-at|js:legalActionModalView:#la-approved-at|js:legalActionModalView:#la-closed-at|js:legalActionModalView:#la-denied-at|js:legalActionModalView:#la-expires-at|js:legalActionModalView:#la-notes|js:legalActionModalView:la-status|js:legalActionModalView:la-verif
4
+ capture.immigration_status,immigration_legal_status,immigration_legal_status,immigration_status,unit,js:immigrationLegalStatusCorePaint:[data-ils-field=proof_of_id_other_text]|js:immigrationLegalStatusCorePaint:[data-ils-field=trafficking_screening_date]|js:immigrationLegalStatusCorePaint:[data-ils-field=uscis_alien_number]|js:immigrationLegalStatusCorePaint:[data-ils-field=visa_expires_at]|js:immigrationLegalStatusCorePaint:[data-ils-q2-id-type]|js:immigrationLegalStatusCorePaint:ils-has-id|js:immigrationLegalStatusCorePaint:ils-platform|js:immigrationLegalStatusCorePaint:ils-tk-screened|st:sub-core-profile:[data-adlc-field=immigrant_status]|st:sub-core-profile:adlc-immigrant
5
+ capture.visa_type,immigration_legal_status,immigration_legal_status,immigration_status,unit,js:immigrationLegalStatusCorePaint:[data-ils-visa-more]|js:immigrationLegalStatusCorePaint:[data-ils-visa-subpick]|js:immigrationLegalStatusCorePaint:[data-ils-visa]
6
+ capture.le_report_status,immigration_legal_status,immigration_legal_status,le_report_status,unit,js:immigrationLegalStatusCorePaint:[data-ils-field=le_interview_scheduled_at]|js:immigrationLegalStatusCorePaint:[data-ils-field=le_report_agency]|js:immigrationLegalStatusCorePaint:[data-ils-field=le_report_agent]|js:immigrationLegalStatusCorePaint:[data-ils-field=le_report_filed_at]|js:immigrationLegalStatusCorePaint:[data-ils-field=le_report_number]|js:immigrationLegalStatusCorePaint:ils-le-arrangement|js:immigrationLegalStatusCorePaint:ils-le-status
7
+ capture.chronic_health_severity,access_accommodations,health_accommodation,chronic_health_status,unit,js:accessAccommodationsCorePaint:aa-chronic-severity
8
+ capture.long_term_conditions,access_accommodations,health_accommodation,chronic_health_status,unit,st:sub-core-profile:[data-mh-field=long_term_conditions_description]|st:sub-core-profile:mh-long-term-conditions
9
+ capture.has_disability,access_accommodations,health_accommodation,disability_subtypes,unit,js:accessAccommodationsCorePaint:[data-aa-disability-other]|js:accessAccommodationsCorePaint:[data-aa-disability-subtype]|js:accessAccommodationsCorePaint:aa-cogdev-onset|js:accessAccommodationsCorePaint:aa-has-disability|js:accessAccommodationsCorePaint:aa-physical-severity|js:accessAccommodationsCorePaint:aa-subtype-severity-{}
10
+ capture.hiv_status,access_accommodations,health_accommodation,hiv_status,unit,js:accessAccommodationsCorePaint:aa-hiv-status
11
+ capture.mental_health_status,access_accommodations,health_accommodation,mental_health_status,unit,js:accessAccommodationsCorePaint:aa-mh-severity|js:accessAccommodationsCorePaint:aa-mh-status
12
+ capture.substance_use_status,access_accommodations,health_accommodation,substance_use_status,unit,js:accessAccommodationsCorePaint:aa-su-severity|js:accessAccommodationsCorePaint:aa-su-status
@@ -1,4 +1,4 @@
1
- # source: htilabstech/prototype docs/share-roi/information_scope_v4.migrations.csv @ 6dab8a9532cf1b94cdce3e475906df839359ad80 (byte-identical at 00179edc); verbatim below this line, re-copy never hand-edit (the test checks the git blob hash)
1
+ # source: htilabstech/prototype docs/share-roi/information_scope_v4.migrations.csv @ e86dd89cdba5cbb39ccfc7fb35aff8cbf0774790 (SIGNED-GRAIN; byte-identical at 7ca7e586); verbatim below this line, re-copy never hand-edit (the test checks the git blob hash)
2
2
  v3_code,v4_reads_as,rule,note
3
3
  system,system,identity,code unchanged
4
4
  notes,notes,identity,code unchanged
@@ -75,32 +75,32 @@ object_identifiers,object_identifiers,identity,code unchanged
75
75
  phone_identifiers,phone_identifiers,identity,code unchanged
76
76
  object_identity_attributes,object_identity_attributes,identity,code unchanged
77
77
  offender_facilitator,offenders.identifying offenders.risk,row,retired in v4; a stored selection naming it reads as the successor(s)
78
- mental_health_status,health_status,row,retired in v4; a stored selection naming it reads as the successor(s)
79
- substance_use_status,health_status,row,retired in v4; a stored selection naming it reads as the successor(s)
80
- chronic_health_status,health_status,row,retired in v4; a stored selection naming it reads as the successor(s)
81
- disability_subtypes,health_status,row,retired in v4; a stored selection naming it reads as the successor(s)
82
- hiv_status,health_status,row,retired in v4; a stored selection naming it reads as the successor(s)
83
- uscis_alien_number,immigration_status,row,retired in v4; a stored selection naming it reads as the successor(s)
84
- federal_protection_applications,immigration_applications,row,retired in v4; a stored selection naming it reads as the successor(s)
85
- tvap_enrollment,immigration_applications,row,retired in v4; a stored selection naming it reads as the successor(s)
86
- le_report_status,immigration_applications,row,retired in v4; a stored selection naming it reads as the successor(s)
78
+ mental_health_status,health_status,row (merge; signed release keeps its grain),MERGE fold — 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)
79
+ substance_use_status,health_status,row (merge; signed release keeps its grain),MERGE fold — 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)
80
+ chronic_health_status,health_status,row (merge; signed release keeps its grain),MERGE fold — 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)
81
+ disability_subtypes,health_status,row (merge; signed release keeps its grain),MERGE fold — 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)
82
+ hiv_status,health_status,row (merge; signed release keeps its grain),MERGE fold — 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)
83
+ uscis_alien_number,immigration_status,row (merge; signed release keeps its grain),MERGE fold — 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)
84
+ federal_protection_applications,immigration_applications,row (merge; signed release keeps its grain),MERGE fold — 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)
85
+ tvap_enrollment,immigration_applications,row (merge; signed release keeps its grain),MERGE fold — 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)
86
+ le_report_status,immigration_applications,row (merge; signed release keeps its grain),MERGE fold — 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)
87
87
  risk,risk,category,category-grain selection; maps to the listed codes only (never widened)
88
88
  identifying,identifying,category,category-grain selection; maps to the listed codes only (never widened)
89
89
  offender_facilitator,offenders,subtract,a v3 RESTRICTION on this code keeps restricting the listed v4 rows
90
- ida_full,full_ida summary_ida,retired before v4,via v3: full_ida summary_ida
91
- ida_consid,summary_ida,retired before v4,via v3: summary_ida
92
- initial_screen,summary_initial_screen,retired before v4,via v3: summary_initial_screen
93
- tra,summary_tra,retired before v4,via v3: summary_tra
94
- lap,summary_lap,retired before v4,via v3: summary_lap
95
- danger_assessment,summary_danger_assessment,retired before v4,via v3: summary_danger_assessment
96
- injury_and_strangulation,summary_injury_and_strangulation,retired before v4,via v3: summary_injury_and_strangulation
97
- stalking_assessment,summary_stalking_assessment,retired before v4,via v3: summary_stalking_assessment
98
- ae_intake,summary_ae_intake,retired before v4,via v3: summary_ae_intake
99
- hope_scale,summary_hope_scale,retired before v4,via v3: summary_hope_scale
100
- assessment_records,(nothing),retired before v4,retired with no successor row (R30); the lifecycle lines are not share content
101
- determinations,summary_findings,retired before v4,via v3: summary_findings
102
- mental_health_screen,summary_mental_health_screen,retired before v4,via v3: summary_mental_health_screen
103
- trauma_and_coping_screen,summary_trauma_and_coping_screen,retired before v4,via v3: summary_trauma_and_coping_screen
104
- behavioral_health_intake,summary_behavioral_health_intake,retired before v4,via v3: summary_behavioral_health_intake
105
- screen_notes,(nothing),retired before v4,retired 2026-10-05 — an Initial Screen note is an instrument note and rides full_initial_screen; a stored selection naming it includes nothing
106
- background,(nothing),retired before v4,retired 2026-10-05 — nothing ever captured it (Crysta to Nate: Eliminate)
90
+ ida_full,full_ida summary_ida,retired before v4 (informational),"via v3: full_ida summary_ida — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
91
+ ida_consid,summary_ida,retired before v4 (informational),"via v3: summary_ida — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
92
+ initial_screen,summary_initial_screen,retired before v4 (informational),"via v3: summary_initial_screen — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
93
+ tra,summary_tra,retired before v4 (informational),"via v3: summary_tra — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
94
+ lap,summary_lap,retired before v4 (informational),"via v3: summary_lap — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
95
+ danger_assessment,summary_danger_assessment,retired before v4 (informational),"via v3: summary_danger_assessment — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
96
+ injury_and_strangulation,summary_injury_and_strangulation,retired before v4 (informational),"via v3: summary_injury_and_strangulation — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
97
+ stalking_assessment,summary_stalking_assessment,retired before v4 (informational),"via v3: summary_stalking_assessment — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
98
+ ae_intake,summary_ae_intake,retired before v4 (informational),"via v3: summary_ae_intake — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
99
+ hope_scale,summary_hope_scale,retired before v4 (informational),"via v3: summary_hope_scale — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
100
+ assessment_records,(nothing),retired before v4 (informational),"retired with no successor row (R30); the lifecycle lines are not share content — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
101
+ determinations,summary_findings,retired before v4 (informational),"via v3: summary_findings — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
102
+ mental_health_screen,summary_mental_health_screen,retired before v4 (informational),"via v3: summary_mental_health_screen — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
103
+ trauma_and_coping_screen,summary_trauma_and_coping_screen,retired before v4 (informational),"via v3: summary_trauma_and_coping_screen — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
104
+ behavioral_health_intake,summary_behavioral_health_intake,retired before v4 (informational),"via v3: summary_behavioral_health_intake — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
105
+ screen_notes,(nothing),retired before v4 (informational),"retired 2026-10-05 — an Initial Screen note is an instrument note and rides full_initial_screen; a stored selection naming it includes nothing — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
106
+ background,(nothing),retired before v4 (informational),"retired 2026-10-05 — nothing ever captured it (Crysta to Nate: Eliminate) — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one"
@@ -1,4 +1,4 @@
1
- # source: htilabstech/prototype docs/share-roi/information_scope_v4.rows.csv @ 6dab8a9532cf1b94cdce3e475906df839359ad80 (byte-identical at 00179edc); verbatim below this line, re-copy never hand-edit (the test checks the git blob hash)
1
+ # source: htilabstech/prototype docs/share-roi/information_scope_v4.rows.csv @ e86dd89cdba5cbb39ccfc7fb35aff8cbf0774790 (byte-identical at 6dab8a95, 00179edc and 7ca7e586); verbatim below this line, re-copy never hand-edit (the test checks the git blob hash)
2
2
  code,label,parent,depth,row_type,kind_branch,PAVE,Thread,LEADS,selectable,shareable_default,platform_floor,level_floor,special_data_type,status,replaces_v3,notes
3
3
  system,System metadata,,0,category,,yes,yes,yes,yes,on,,1,none,as_today,,"Always included: viewing-side force-added to every visible set; sharing-side system_info is required on every ROI and share and cannot be deselected. 260 fields (platform directories, policies, grants, sessions, the rails) — one branch, one sub-category, by design (Phase 2 § 4)."
4
4
  system_info,System info,system,1,subcategory,,yes,yes,yes,yes,on,,1,none,as_today,,
@@ -1,8 +1,9 @@
1
1
  /**
2
2
  * Loads the canon's generated CVC-236 v4 CSV pair (prototype
3
- * docs/share-roi/information_scope_v4.{rows,migrations}.csv @ 6dab8a95,
4
- * byte-identical at 00179edc) into the resolver's input shapes. Test-only:
5
- * the resolver tests bind to the SOT; this pair is the cross-check.
3
+ * docs/share-roi/information_scope_v4.{rows,migrations}.csv @ e86dd89c,
4
+ * SIGNED-GRAIN, byte-identical at 7ca7e586; the rows CSV is unchanged since
5
+ * 6dab8a95) into the resolver's input shapes. Test-only: the resolver tests
6
+ * bind to the SOT; this pair is the cross-check.
6
7
  */
7
8
 
8
9
  import { createHash } from "node:crypto";
@@ -22,15 +23,69 @@ import type {
22
23
 
23
24
  const here = path.dirname(fileURLToPath(import.meta.url));
24
25
 
25
- export const INFOSCOPE_V4_CANON_SHA = "6dab8a9532cf1b94cdce3e475906df839359ad80";
26
+ export const INFOSCOPE_V4_CANON_SHA = "e86dd89cdba5cbb39ccfc7fb35aff8cbf0774790";
26
27
 
27
- /** `git rev-parse <sha>:docs/share-roi/<file>` at 6dab8a95 and at 00179edc. */
28
+ /** `git rev-parse <sha>:docs/share-roi/<file>` at e86dd89c and at 7ca7e586. */
28
29
  export const INFOSCOPE_V4_CANON_BLOBS = {
29
30
  "information_scope_v4.rows.csv": "f2106e7b107a8bf3de7e266f720f2c0af40ee236",
30
- "information_scope_v4.migrations.csv": "24ffeda4b5185d6c7a17ca907a531a7879557fb8",
31
+ "information_scope_v4.migrations.csv": "dbb7dbf6856b35d313d67c526cf47007f69989fb",
31
32
  } as const;
32
33
 
33
- export type InfoscopeFixture = keyof typeof INFOSCOPE_V4_CANON_BLOBS;
34
+ /**
35
+ * Canon's exporter QUALIFIES two rules in its labels since SIGNED-GRAIN
36
+ * (e86dd89c): the base rule a resolver binds, and the qualifier the SOT
37
+ * carries as a field (`releaseReading: "retain"` / `informational`).
38
+ */
39
+ export const CANON_RULE_LABELS: Readonly<
40
+ Record<string, { rule: ScopeMigrationRule; qualifier: "retain" | "informational" }>
41
+ > = {
42
+ "row (merge; signed release keeps its grain)": { rule: "row", qualifier: "retain" },
43
+ "retired before v4 (informational)": { rule: "retired before v4", qualifier: "informational" },
44
+ };
45
+
46
+ /**
47
+ * The v3 field placements the SOT's `v3Fields` derive from: a PROJECTION of
48
+ * canon `INFOSCOPE_FIELD_PLACEMENTS_V4_2026-10-08.csv` (957 KB, too large to
49
+ * vendor into a published `src/`) — the six columns below, for every row
50
+ * homed on, or with a control naming, one of the ten widening units. The
51
+ * projection's own body blob is pinned; re-derive it, never hand-edit. The body
52
+ * (below the `# source:` line) is exactly, with U = `units` and C = `columns`:
53
+ *
54
+ * rows = csv.DictReader(<the canon file at canonSha, decoded utf-8-sig>)
55
+ * keep r if r.home_unit_today in U, or re.search(r"\b" + u + r"\b", r.controls) for a u in U
56
+ * csv.writer(out, lineterminator="\n"): the row C, then [r[c] for c in C] per kept row
57
+ */
58
+ export const INFOSCOPE_V3_PLACEMENTS = {
59
+ file: "information_scope_v3_placements.projection.csv",
60
+ canonSha: "00179edcb3f0c00a8b55beeffd1618c8a5c98937",
61
+ /** `git rev-parse <sha>:INFOSCOPE_FIELD_PLACEMENTS_V4_2026-10-08.csv`, at 00179edc and 7ca7e586. */
62
+ canonBlob: "9c10b39d4dfabc0b4c72fb8f7011415710ab29ff",
63
+ projectionBlob: "20ee82db4ac1d8cbcd0fba8e5fe61d8d03e40fba",
64
+ columns: [
65
+ "field",
66
+ "assertion_domain",
67
+ "home_category_today",
68
+ "home_unit_today",
69
+ "home_grain_today",
70
+ "controls",
71
+ ],
72
+ units: [
73
+ "chronic_health_status",
74
+ "disability_subtypes",
75
+ "federal_protection_applications",
76
+ "hiv_status",
77
+ "immigration_status",
78
+ "le_report_status",
79
+ "mental_health_status",
80
+ "substance_use_status",
81
+ "tvap_enrollment",
82
+ "uscis_alien_number",
83
+ ],
84
+ } as const;
85
+
86
+ export type InfoscopeFixture =
87
+ | keyof typeof INFOSCOPE_V4_CANON_BLOBS
88
+ | typeof INFOSCOPE_V3_PLACEMENTS.file;
34
89
 
35
90
  export const fixtureText = (f: InfoscopeFixture): string => readFileSync(path.join(here, f), "utf8");
36
91
 
@@ -106,11 +161,27 @@ export function loadCsvRows(): ScopeRow[] {
106
161
  });
107
162
  }
108
163
 
109
- export function loadCsvMigrations(): ScopeMigration[] {
110
- return parseCsv(fixtureText("information_scope_v4.migrations.csv")).map((m) => ({
111
- from: m.v3_code,
112
- to: m.v4_reads_as === "(nothing)" ? [] : m.v4_reads_as.split(/\s+/).filter(Boolean),
113
- rule: m.rule as ScopeMigrationRule,
114
- note: m.note,
115
- }));
164
+ /**
165
+ * The migrations CSV as `ScopeMigration`s, its qualified labels reduced to the
166
+ * base rule (`label` keeps canon's). A merge fold is NOT bound as `retain`
167
+ * here: the CSV carries no v3 field lists, so the CSV-bound resolver reads it
168
+ * as the plain fold (a policy's reading).
169
+ */
170
+ export function loadCsvMigrations(): (ScopeMigration & { label: string })[] {
171
+ return parseCsv(fixtureText("information_scope_v4.migrations.csv")).map((m) => {
172
+ const q = CANON_RULE_LABELS[m.rule];
173
+ return {
174
+ from: m.v3_code,
175
+ to: m.v4_reads_as === "(nothing)" ? [] : m.v4_reads_as.split(/\s+/).filter(Boolean),
176
+ rule: q ? q.rule : (m.rule as ScopeMigrationRule),
177
+ label: m.rule,
178
+ note: m.note,
179
+ ...(q?.qualifier === "informational" ? { informational: true } : {}),
180
+ };
181
+ });
182
+ }
183
+
184
+ /** The v3 placements projection, row for row. */
185
+ export function loadV3Placements(): Record<string, string>[] {
186
+ return parseCsv(fixtureText(INFOSCOPE_V3_PLACEMENTS.file));
116
187
  }