@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
@@ -1,10 +1,10 @@
1
1
  {
2
2
  "domain": "core_information_scope",
3
3
  "name": "Core Information Scope",
4
- "version": "2.0.0",
4
+ "version": "2.1.0",
5
5
  "scopeVersion": 4,
6
- "_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 · Narrative notes · Primary client / case subject · Other named persons); 1 a client category or a person type (People who caused harm · Eligible family members · 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 § 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 — 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 § 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 § 8 list omits (rowType `branch` and `sub-category` — the exporter's label for a LEADS unit — 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.",
7
- "_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",
6
+ "_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 · Narrative notes · Primary client / case subject · Other named persons); 1 a client category or a person type (People who caused harm · Eligible family members · 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 § 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 — 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 § 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 § 8 list omits (rowType `branch` and `sub-category` — the exporter's label for a LEADS unit — and specialDataType `evidence`). VERSION 2.1.0 amends 2.0.0 (MINOR, additive: the release-grain fields and canon's SIGNED-GRAIN migration notes — 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.",
7
+ "_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",
8
8
  "_supersedes": {
9
9
  "version": "1.1.0",
10
10
  "keyMap": {
@@ -84,7 +84,7 @@
84
84
  },
85
85
  "retiredCodes": [],
86
86
  "notes": {
87
- "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 · depth · kindBranch · platformFloor · status · 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).",
87
+ "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 · depth · kindBranch · platformFloor · status · 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).",
88
88
  "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` — so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
89
89
  "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` — so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
90
90
  "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` — so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
@@ -98,21 +98,21 @@
98
98
  "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`).",
99
99
  "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` — so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
100
100
  "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 › 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`).",
101
- "disability_subtypes": "v1.1.0 `disability_subtypes` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
102
- "mental_health_status": "v1.1.0 `mental_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
103
- "substance_use_status": "v1.1.0 `substance_use_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
104
- "chronic_health_status": "v1.1.0 `chronic_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
105
- "hiv_status": "v1.1.0 `hiv_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
101
+ "disability_subtypes": "v1.1.0 `disability_subtypes` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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` — 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`).",
102
+ "mental_health_status": "v1.1.0 `mental_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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` — 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`).",
103
+ "substance_use_status": "v1.1.0 `substance_use_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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` — 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`).",
104
+ "chronic_health_status": "v1.1.0 `chronic_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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` — 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`).",
105
+ "hiv_status": "v1.1.0 `hiv_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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` — 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`).",
106
106
  "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` — so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
107
107
  "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` — so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
108
108
  "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` — so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
109
- "uscis_alien_number": "v1.1.0 `uscis_alien_number` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
110
- "federal_protection_applications": "v1.1.0 `federal_protection_applications` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
111
- "tvap_enrollment": "v1.1.0 `tvap_enrollment` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
112
- "le_report_status": "v1.1.0 `le_report_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
109
+ "uscis_alien_number": "v1.1.0 `uscis_alien_number` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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` — 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`).",
110
+ "federal_protection_applications": "v1.1.0 `federal_protection_applications` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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` — 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`).",
111
+ "tvap_enrollment": "v1.1.0 `tvap_enrollment` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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` — 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`).",
112
+ "le_report_status": "v1.1.0 `le_report_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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` — 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`).",
113
113
  "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 › 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`) — the content its retired per-instrument units carried — and those pass through this table unchanged.",
114
114
  "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.",
115
- "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."
115
+ "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)."
116
116
  }
117
117
  },
118
118
  "levels": {
@@ -130,11 +130,26 @@
130
130
  "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.",
131
131
  "rules": {
132
132
  "identity": "code unchanged; a v3 list naming it reads the same in v4",
133
- "row": "the v3 code is retired; a stored list naming it reads as the listed v4 successor(s)",
133
+ "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)",
134
134
  "category": "a category-grain v3 selection (a purpose payload, a partner rule, a policy) reads as the listed v4 codes only — never widened",
135
135
  "subtract": "a v3 RESTRICTION (a policy that forbids a code) keeps restricting the listed v4 rows",
136
- "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)",
137
- "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)"
136
+ "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)`",
137
+ "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`)",
138
+ "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 § 3), that names the `from` code at scopeVersion 3 keeps the grain it was signed at — 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",
139
+ "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 § 3)",
140
+ "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"
141
+ },
142
+ "ruling": {
143
+ "date": "2026-10-09",
144
+ "by": "Crysta",
145
+ "source": "Slack DM thread, https://htilabs-us.slack.com/archives/D0811D2R6QN/p1791581735053759?thread_ts=1791580621.618429&cid=D0811D2R6QN (16:35 CDT)",
146
+ "text": [
147
+ "Good catch — 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 — 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 § 3 to say this explicitly.",
148
+ "Your reading is the intended one. A v2-era list goes through v2→v3 first (which carries the conjunction: lap AND screen_indicators → summary_lap), then v3→v4. The retired_v3 rows are informational — they give every old code a stated v4 reading — 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→v4 reading. We'll mark those rows `informational` in the yaml so it's not ambiguous."
149
+ ],
150
+ "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",
151
+ "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`).",
152
+ "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 § 3 amended. Canon carries no v3 field lists: `v3Fields` is this package's derivation (`membership`)."
138
153
  },
139
154
  "table": [
140
155
  {
@@ -395,7 +410,10 @@
395
410
  "236-007-001-000-000-000-000"
396
411
  ],
397
412
  "note": "code unchanged",
398
- "widens": true
413
+ "widens": true,
414
+ "releaseReading": "successor",
415
+ "policyReading": "successor",
416
+ "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 — `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) — so a v3 release naming it delivered it, and no consent widens in practice."
399
417
  },
400
418
  {
401
419
  "from": "screen_indicators",
@@ -1111,8 +1129,10 @@
1111
1129
  "toCodes": [
1112
1130
  "236-006-010-000-000-000-000"
1113
1131
  ],
1114
- "note": "retired in v4; a stored selection naming it reads as the successor(s)",
1115
- "widens": true
1132
+ "note": "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)",
1133
+ "widens": true,
1134
+ "releaseReading": "retain",
1135
+ "policyReading": "successor"
1116
1136
  },
1117
1137
  {
1118
1138
  "from": "substance_use_status",
@@ -1124,8 +1144,10 @@
1124
1144
  "toCodes": [
1125
1145
  "236-006-010-000-000-000-000"
1126
1146
  ],
1127
- "note": "retired in v4; a stored selection naming it reads as the successor(s)",
1128
- "widens": true
1147
+ "note": "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)",
1148
+ "widens": true,
1149
+ "releaseReading": "retain",
1150
+ "policyReading": "successor"
1129
1151
  },
1130
1152
  {
1131
1153
  "from": "chronic_health_status",
@@ -1137,8 +1159,10 @@
1137
1159
  "toCodes": [
1138
1160
  "236-006-010-000-000-000-000"
1139
1161
  ],
1140
- "note": "retired in v4; a stored selection naming it reads as the successor(s)",
1141
- "widens": true
1162
+ "note": "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)",
1163
+ "widens": true,
1164
+ "releaseReading": "retain",
1165
+ "policyReading": "successor"
1142
1166
  },
1143
1167
  {
1144
1168
  "from": "disability_subtypes",
@@ -1150,8 +1174,10 @@
1150
1174
  "toCodes": [
1151
1175
  "236-006-010-000-000-000-000"
1152
1176
  ],
1153
- "note": "retired in v4; a stored selection naming it reads as the successor(s)",
1154
- "widens": true
1177
+ "note": "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)",
1178
+ "widens": true,
1179
+ "releaseReading": "retain",
1180
+ "policyReading": "successor"
1155
1181
  },
1156
1182
  {
1157
1183
  "from": "hiv_status",
@@ -1163,8 +1189,10 @@
1163
1189
  "toCodes": [
1164
1190
  "236-006-010-000-000-000-000"
1165
1191
  ],
1166
- "note": "retired in v4; a stored selection naming it reads as the successor(s)",
1167
- "widens": true
1192
+ "note": "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)",
1193
+ "widens": true,
1194
+ "releaseReading": "retain",
1195
+ "policyReading": "successor"
1168
1196
  },
1169
1197
  {
1170
1198
  "from": "uscis_alien_number",
@@ -1176,8 +1204,10 @@
1176
1204
  "toCodes": [
1177
1205
  "236-007-001-000-000-000-000"
1178
1206
  ],
1179
- "note": "retired in v4; a stored selection naming it reads as the successor(s)",
1180
- "widens": true
1207
+ "note": "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)",
1208
+ "widens": true,
1209
+ "releaseReading": "retain",
1210
+ "policyReading": "successor"
1181
1211
  },
1182
1212
  {
1183
1213
  "from": "federal_protection_applications",
@@ -1189,8 +1219,10 @@
1189
1219
  "toCodes": [
1190
1220
  "236-007-006-000-000-000-000"
1191
1221
  ],
1192
- "note": "retired in v4; a stored selection naming it reads as the successor(s)",
1193
- "widens": true
1222
+ "note": "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)",
1223
+ "widens": true,
1224
+ "releaseReading": "retain",
1225
+ "policyReading": "successor"
1194
1226
  },
1195
1227
  {
1196
1228
  "from": "tvap_enrollment",
@@ -1202,8 +1234,10 @@
1202
1234
  "toCodes": [
1203
1235
  "236-007-006-000-000-000-000"
1204
1236
  ],
1205
- "note": "retired in v4; a stored selection naming it reads as the successor(s)",
1206
- "widens": true
1237
+ "note": "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)",
1238
+ "widens": true,
1239
+ "releaseReading": "retain",
1240
+ "policyReading": "successor"
1207
1241
  },
1208
1242
  {
1209
1243
  "from": "le_report_status",
@@ -1215,8 +1249,10 @@
1215
1249
  "toCodes": [
1216
1250
  "236-007-006-000-000-000-000"
1217
1251
  ],
1218
- "note": "retired in v4; a stored selection naming it reads as the successor(s)",
1219
- "widens": true
1252
+ "note": "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)",
1253
+ "widens": true,
1254
+ "releaseReading": "retain",
1255
+ "policyReading": "successor"
1220
1256
  },
1221
1257
  {
1222
1258
  "from": "risk",
@@ -1269,8 +1305,9 @@
1269
1305
  "236-013-002-006-000-000-000",
1270
1306
  "236-013-001-006-000-000-000"
1271
1307
  ],
1272
- "note": "via v3: full_ida summary_ida",
1273
- "widens": false
1308
+ "note": "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",
1309
+ "widens": false,
1310
+ "informational": true
1274
1311
  },
1275
1312
  {
1276
1313
  "from": "ida_consid",
@@ -1282,8 +1319,9 @@
1282
1319
  "toCodes": [
1283
1320
  "236-013-001-006-000-000-000"
1284
1321
  ],
1285
- "note": "via v3: summary_ida",
1286
- "widens": false
1322
+ "note": "via v3: summary_ida — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one",
1323
+ "widens": false,
1324
+ "informational": true
1287
1325
  },
1288
1326
  {
1289
1327
  "from": "initial_screen",
@@ -1295,8 +1333,9 @@
1295
1333
  "toCodes": [
1296
1334
  "236-013-001-001-000-000-000"
1297
1335
  ],
1298
- "note": "via v3: summary_initial_screen",
1299
- "widens": false
1336
+ "note": "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",
1337
+ "widens": false,
1338
+ "informational": true
1300
1339
  },
1301
1340
  {
1302
1341
  "from": "tra",
@@ -1308,8 +1347,9 @@
1308
1347
  "toCodes": [
1309
1348
  "236-013-001-013-000-000-000"
1310
1349
  ],
1311
- "note": "via v3: summary_tra",
1312
- "widens": false
1350
+ "note": "via v3: summary_tra — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one",
1351
+ "widens": false,
1352
+ "informational": true
1313
1353
  },
1314
1354
  {
1315
1355
  "from": "lap",
@@ -1321,8 +1361,9 @@
1321
1361
  "toCodes": [
1322
1362
  "236-013-001-007-000-000-000"
1323
1363
  ],
1324
- "note": "via v3: summary_lap",
1325
- "widens": false
1364
+ "note": "via v3: summary_lap — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one",
1365
+ "widens": false,
1366
+ "informational": true
1326
1367
  },
1327
1368
  {
1328
1369
  "from": "danger_assessment",
@@ -1334,8 +1375,9 @@
1334
1375
  "toCodes": [
1335
1376
  "236-013-001-008-000-000-000"
1336
1377
  ],
1337
- "note": "via v3: summary_danger_assessment",
1338
- "widens": false
1378
+ "note": "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",
1379
+ "widens": false,
1380
+ "informational": true
1339
1381
  },
1340
1382
  {
1341
1383
  "from": "injury_and_strangulation",
@@ -1347,8 +1389,9 @@
1347
1389
  "toCodes": [
1348
1390
  "236-013-001-010-000-000-000"
1349
1391
  ],
1350
- "note": "via v3: summary_injury_and_strangulation",
1351
- "widens": false
1392
+ "note": "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",
1393
+ "widens": false,
1394
+ "informational": true
1352
1395
  },
1353
1396
  {
1354
1397
  "from": "stalking_assessment",
@@ -1360,8 +1403,9 @@
1360
1403
  "toCodes": [
1361
1404
  "236-013-001-009-000-000-000"
1362
1405
  ],
1363
- "note": "via v3: summary_stalking_assessment",
1364
- "widens": false
1406
+ "note": "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",
1407
+ "widens": false,
1408
+ "informational": true
1365
1409
  },
1366
1410
  {
1367
1411
  "from": "ae_intake",
@@ -1373,8 +1417,9 @@
1373
1417
  "toCodes": [
1374
1418
  "236-013-001-005-000-000-000"
1375
1419
  ],
1376
- "note": "via v3: summary_ae_intake",
1377
- "widens": false
1420
+ "note": "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",
1421
+ "widens": false,
1422
+ "informational": true
1378
1423
  },
1379
1424
  {
1380
1425
  "from": "hope_scale",
@@ -1386,8 +1431,9 @@
1386
1431
  "toCodes": [
1387
1432
  "236-013-001-011-000-000-000"
1388
1433
  ],
1389
- "note": "via v3: summary_hope_scale",
1390
- "widens": false
1434
+ "note": "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",
1435
+ "widens": false,
1436
+ "informational": true
1391
1437
  },
1392
1438
  {
1393
1439
  "from": "assessment_records",
@@ -1395,8 +1441,9 @@
1395
1441
  "rule": "retired before v4",
1396
1442
  "to": [],
1397
1443
  "toCodes": [],
1398
- "note": "retired with no successor row (R30); the lifecycle lines are not share content",
1399
- "widens": false
1444
+ "note": "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",
1445
+ "widens": false,
1446
+ "informational": true
1400
1447
  },
1401
1448
  {
1402
1449
  "from": "determinations",
@@ -1408,8 +1455,9 @@
1408
1455
  "toCodes": [
1409
1456
  "236-013-001-014-000-000-000"
1410
1457
  ],
1411
- "note": "via v3: summary_findings",
1412
- "widens": false
1458
+ "note": "via v3: summary_findings — a v2-era list is read through the LIVE v2→v3 table first (which carries the condition), then this one",
1459
+ "widens": false,
1460
+ "informational": true
1413
1461
  },
1414
1462
  {
1415
1463
  "from": "mental_health_screen",
@@ -1421,8 +1469,9 @@
1421
1469
  "toCodes": [
1422
1470
  "236-013-001-002-000-000-000"
1423
1471
  ],
1424
- "note": "via v3: summary_mental_health_screen",
1425
- "widens": false
1472
+ "note": "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",
1473
+ "widens": false,
1474
+ "informational": true
1426
1475
  },
1427
1476
  {
1428
1477
  "from": "trauma_and_coping_screen",
@@ -1434,8 +1483,9 @@
1434
1483
  "toCodes": [
1435
1484
  "236-013-001-004-000-000-000"
1436
1485
  ],
1437
- "note": "via v3: summary_trauma_and_coping_screen",
1438
- "widens": false
1486
+ "note": "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",
1487
+ "widens": false,
1488
+ "informational": true
1439
1489
  },
1440
1490
  {
1441
1491
  "from": "behavioral_health_intake",
@@ -1447,8 +1497,9 @@
1447
1497
  "toCodes": [
1448
1498
  "236-013-001-003-000-000-000"
1449
1499
  ],
1450
- "note": "via v3: summary_behavioral_health_intake",
1451
- "widens": false
1500
+ "note": "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",
1501
+ "widens": false,
1502
+ "informational": true
1452
1503
  },
1453
1504
  {
1454
1505
  "from": "screen_notes",
@@ -1456,8 +1507,9 @@
1456
1507
  "rule": "retired before v4",
1457
1508
  "to": [],
1458
1509
  "toCodes": [],
1459
- "note": "retired 2026-10-05 — an Initial Screen note is an instrument note and rides full_initial_screen; a stored selection naming it includes nothing",
1460
- "widens": false
1510
+ "note": "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",
1511
+ "widens": false,
1512
+ "informational": true
1461
1513
  },
1462
1514
  {
1463
1515
  "from": "background",
@@ -1465,8 +1517,9 @@
1465
1517
  "rule": "retired before v4",
1466
1518
  "to": [],
1467
1519
  "toCodes": [],
1468
- "note": "retired 2026-10-05 — nothing ever captured it (Crysta to Nate: Eliminate)",
1469
- "widens": false
1520
+ "note": "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",
1521
+ "widens": false,
1522
+ "informational": true
1470
1523
  }
1471
1524
  ]
1472
1525
  },
@@ -2581,7 +2634,7 @@
2581
2634
  "parentKey": "health_accommodation",
2582
2635
  "childCodes": [],
2583
2636
  "childKeys": [],
2584
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2637
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2585
2638
  "retired": true,
2586
2639
  "status": "retired",
2587
2640
  "successors": [
@@ -2590,7 +2643,13 @@
2590
2643
  "successorCodes": [
2591
2644
  "236-006-010-000-000-000-000"
2592
2645
  ],
2593
- "migrationRule": "row"
2646
+ "migrationRule": "row",
2647
+ "v3Fields": [
2648
+ "capture.has_disability"
2649
+ ],
2650
+ "v3Domains": [
2651
+ "access_accommodations"
2652
+ ]
2594
2653
  },
2595
2654
  {
2596
2655
  "code": "236-006-003-000-000-000-000",
@@ -2601,7 +2660,7 @@
2601
2660
  "parentKey": "health_accommodation",
2602
2661
  "childCodes": [],
2603
2662
  "childKeys": [],
2604
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2663
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2605
2664
  "retired": true,
2606
2665
  "status": "retired",
2607
2666
  "successors": [
@@ -2610,7 +2669,13 @@
2610
2669
  "successorCodes": [
2611
2670
  "236-006-010-000-000-000-000"
2612
2671
  ],
2613
- "migrationRule": "row"
2672
+ "migrationRule": "row",
2673
+ "v3Fields": [
2674
+ "capture.mental_health_status"
2675
+ ],
2676
+ "v3Domains": [
2677
+ "access_accommodations"
2678
+ ]
2614
2679
  },
2615
2680
  {
2616
2681
  "code": "236-006-004-000-000-000-000",
@@ -2621,7 +2686,7 @@
2621
2686
  "parentKey": "health_accommodation",
2622
2687
  "childCodes": [],
2623
2688
  "childKeys": [],
2624
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2689
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2625
2690
  "retired": true,
2626
2691
  "status": "retired",
2627
2692
  "successors": [
@@ -2630,7 +2695,13 @@
2630
2695
  "successorCodes": [
2631
2696
  "236-006-010-000-000-000-000"
2632
2697
  ],
2633
- "migrationRule": "row"
2698
+ "migrationRule": "row",
2699
+ "v3Fields": [
2700
+ "capture.substance_use_status"
2701
+ ],
2702
+ "v3Domains": [
2703
+ "access_accommodations"
2704
+ ]
2634
2705
  },
2635
2706
  {
2636
2707
  "code": "236-006-005-000-000-000-000",
@@ -2641,7 +2712,7 @@
2641
2712
  "parentKey": "health_accommodation",
2642
2713
  "childCodes": [],
2643
2714
  "childKeys": [],
2644
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2715
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2645
2716
  "retired": true,
2646
2717
  "status": "retired",
2647
2718
  "successors": [
@@ -2650,7 +2721,14 @@
2650
2721
  "successorCodes": [
2651
2722
  "236-006-010-000-000-000-000"
2652
2723
  ],
2653
- "migrationRule": "row"
2724
+ "migrationRule": "row",
2725
+ "v3Fields": [
2726
+ "capture.chronic_health_severity",
2727
+ "capture.long_term_conditions"
2728
+ ],
2729
+ "v3Domains": [
2730
+ "access_accommodations"
2731
+ ]
2654
2732
  },
2655
2733
  {
2656
2734
  "code": "236-006-006-000-000-000-000",
@@ -2661,7 +2739,7 @@
2661
2739
  "parentKey": "health_accommodation",
2662
2740
  "childCodes": [],
2663
2741
  "childKeys": [],
2664
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2742
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2665
2743
  "retired": true,
2666
2744
  "status": "retired",
2667
2745
  "successors": [
@@ -2670,7 +2748,13 @@
2670
2748
  "successorCodes": [
2671
2749
  "236-006-010-000-000-000-000"
2672
2750
  ],
2673
- "migrationRule": "row"
2751
+ "migrationRule": "row",
2752
+ "v3Fields": [
2753
+ "capture.hiv_status"
2754
+ ],
2755
+ "v3Domains": [
2756
+ "access_accommodations"
2757
+ ]
2674
2758
  },
2675
2759
  {
2676
2760
  "code": "236-006-007-000-000-000-000",
@@ -2838,7 +2922,7 @@
2838
2922
  "parentKey": "immigration_legal_status",
2839
2923
  "childCodes": [],
2840
2924
  "childKeys": [],
2841
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2925
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2842
2926
  "retired": true,
2843
2927
  "status": "retired",
2844
2928
  "successors": [
@@ -2847,7 +2931,10 @@
2847
2931
  "successorCodes": [
2848
2932
  "236-007-001-000-000-000-000"
2849
2933
  ],
2850
- "migrationRule": "row"
2934
+ "migrationRule": "row",
2935
+ "v3Fields": [],
2936
+ "v3Domains": [],
2937
+ "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."
2851
2938
  },
2852
2939
  {
2853
2940
  "code": "236-007-003-000-000-000-000",
@@ -2858,7 +2945,7 @@
2858
2945
  "parentKey": "immigration_legal_status",
2859
2946
  "childCodes": [],
2860
2947
  "childKeys": [],
2861
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2948
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2862
2949
  "retired": true,
2863
2950
  "status": "retired",
2864
2951
  "successors": [
@@ -2867,7 +2954,13 @@
2867
2954
  "successorCodes": [
2868
2955
  "236-007-006-000-000-000-000"
2869
2956
  ],
2870
- "migrationRule": "row"
2957
+ "migrationRule": "row",
2958
+ "v3Fields": [
2959
+ "capture.legal_action_type"
2960
+ ],
2961
+ "v3Domains": [
2962
+ "immigration_legal_status"
2963
+ ]
2871
2964
  },
2872
2965
  {
2873
2966
  "code": "236-007-004-000-000-000-000",
@@ -2878,7 +2971,7 @@
2878
2971
  "parentKey": "immigration_legal_status",
2879
2972
  "childCodes": [],
2880
2973
  "childKeys": [],
2881
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2974
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2882
2975
  "retired": true,
2883
2976
  "status": "retired",
2884
2977
  "successors": [
@@ -2887,7 +2980,10 @@
2887
2980
  "successorCodes": [
2888
2981
  "236-007-006-000-000-000-000"
2889
2982
  ],
2890
- "migrationRule": "row"
2983
+ "migrationRule": "row",
2984
+ "v3Fields": [],
2985
+ "v3Domains": [],
2986
+ "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."
2891
2987
  },
2892
2988
  {
2893
2989
  "code": "236-007-005-000-000-000-000",
@@ -2898,7 +2994,7 @@
2898
2994
  "parentKey": "immigration_legal_status",
2899
2995
  "childCodes": [],
2900
2996
  "childKeys": [],
2901
- "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2997
+ "definition": "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 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.",
2902
2998
  "retired": true,
2903
2999
  "status": "retired",
2904
3000
  "successors": [
@@ -2907,7 +3003,13 @@
2907
3003
  "successorCodes": [
2908
3004
  "236-007-006-000-000-000-000"
2909
3005
  ],
2910
- "migrationRule": "row"
3006
+ "migrationRule": "row",
3007
+ "v3Fields": [
3008
+ "capture.le_report_status"
3009
+ ],
3010
+ "v3Domains": [
3011
+ "immigration_legal_status"
3012
+ ]
2911
3013
  },
2912
3014
  {
2913
3015
  "code": "236-007-006-000-000-000-000",