@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.
- package/dist/cvcs/index.cjs +222 -120
- package/dist/cvcs/index.cjs.map +1 -1
- package/dist/cvcs/index.d.cts +223 -117
- package/dist/cvcs/index.d.ts +223 -117
- package/dist/cvcs/index.js +222 -120
- package/dist/cvcs/index.js.map +1 -1
- package/dist/enums/index.cjs.map +1 -1
- package/dist/enums/index.d.cts +4 -4
- package/dist/enums/index.d.ts +4 -4
- package/dist/enums/index.js.map +1 -1
- package/dist/{index-I-DiX9eQ.d.ts → index-CDoqrfc1.d.ts} +1 -1
- package/dist/{index-CoVr1jIV.d.cts → index-Zu_mOJRn.d.cts} +1 -1
- package/dist/index.cjs +320 -137
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +3 -3
- package/dist/index.d.ts +3 -3
- package/dist/index.js +319 -137
- package/dist/index.js.map +1 -1
- package/dist/information-scope/index.cjs +98 -17
- package/dist/information-scope/index.cjs.map +1 -1
- package/dist/information-scope/index.d.cts +142 -13
- package/dist/information-scope/index.d.ts +142 -13
- package/dist/information-scope/index.js +97 -17
- package/dist/information-scope/index.js.map +1 -1
- package/dist/models/index.d.cts +2 -2
- package/dist/models/index.d.ts +2 -2
- package/dist/schemas/index.d.cts +25 -25
- package/dist/schemas/index.d.ts +25 -25
- package/dist/services/index.cjs +98 -17
- package/dist/services/index.cjs.map +1 -1
- package/dist/services/index.d.cts +1 -1
- package/dist/services/index.d.ts +1 -1
- package/dist/services/index.js +97 -17
- package/dist/services/index.js.map +1 -1
- package/package.json +1 -1
- package/src/__tests__/__snapshots__/cvc-sot.snap +2 -2
- package/src/__tests__/core-information-scope-invariant.test.ts +141 -15
- package/src/__tests__/cvc-sot-snapshot.test.ts +4 -3
- package/src/__tests__/cvc-structural.test.ts +2 -2
- package/src/__tests__/location-type-routing-invariant.test.ts +1 -1
- package/src/cvcs/{coreInformationScope.v2.0.0.json → coreInformationScope.v2.1.0.json} +190 -88
- package/src/cvcs/index.ts +2 -2
- package/src/cvcs/{roiScope.v1.3.0.json → roiScope.v1.4.0.json} +26 -26
- package/src/generated/cvc-enums.ts +4 -4
- package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v3_placements.projection.csv +12 -0
- package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v4.migrations.csv +27 -27
- package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v4.rows.csv +1 -1
- package/src/services/__tests__/fixtures/infoscope-v4/loadInfoscopeV4Fixtures.ts +85 -14
- package/src/services/__tests__/informationScopeResolver.test.ts +336 -22
- package/src/services/informationScopeResolver.ts +226 -19
- package/src/services/informationScopeSot.ts +50 -8
- package/dist/{cvcEntry-BCj1OWqL.d.cts → cvcEntry-0BIB9sen.d.cts} +8 -8
- package/dist/{cvcEntry-BCj1OWqL.d.ts → cvcEntry-0BIB9sen.d.ts} +8 -8
package/dist/cvcs/index.d.cts
CHANGED
|
@@ -30351,10 +30351,10 @@ var needsAssessmentChangeType_v1_0_0 = {
|
|
|
30351
30351
|
|
|
30352
30352
|
var domain$E = "core_information_scope";
|
|
30353
30353
|
var name$E = "Core Information Scope";
|
|
30354
|
-
var version$E = "2.
|
|
30354
|
+
var version$E = "2.1.0";
|
|
30355
30355
|
var scopeVersion = 4;
|
|
30356
|
-
var _status$D = "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.";
|
|
30357
|
-
var _source$D = "htilabstech/prototype/core_information_scope.v4.draft.yaml @
|
|
30356
|
+
var _status$D = "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.";
|
|
30357
|
+
var _source$D = "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";
|
|
30358
30358
|
var _supersedes$1 = {
|
|
30359
30359
|
version: "1.1.0",
|
|
30360
30360
|
keyMap: {
|
|
@@ -30435,7 +30435,7 @@ var _supersedes$1 = {
|
|
|
30435
30435
|
retiredCodes: [
|
|
30436
30436
|
],
|
|
30437
30437
|
notes: {
|
|
30438
|
-
summary: "Every v1.1.0 key is still an entry in v2.
|
|
30438
|
+
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).",
|
|
30439
30439
|
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`).",
|
|
30440
30440
|
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`).",
|
|
30441
30441
|
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`).",
|
|
@@ -30449,21 +30449,21 @@ var _supersedes$1 = {
|
|
|
30449
30449
|
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`).",
|
|
30450
30450
|
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`).",
|
|
30451
30451
|
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`).",
|
|
30452
|
-
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
|
|
30453
|
-
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
|
|
30454
|
-
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
|
|
30455
|
-
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
|
|
30456
|
-
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
|
|
30452
|
+
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`).",
|
|
30453
|
+
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`).",
|
|
30454
|
+
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`).",
|
|
30455
|
+
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`).",
|
|
30456
|
+
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`).",
|
|
30457
30457
|
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`).",
|
|
30458
30458
|
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`).",
|
|
30459
30459
|
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`).",
|
|
30460
|
-
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
|
|
30461
|
-
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
|
|
30462
|
-
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
|
|
30463
|
-
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
|
|
30460
|
+
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`).",
|
|
30461
|
+
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`).",
|
|
30462
|
+
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`).",
|
|
30463
|
+
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`).",
|
|
30464
30464
|
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.",
|
|
30465
30465
|
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.",
|
|
30466
|
-
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.
|
|
30466
|
+
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)."
|
|
30467
30467
|
}
|
|
30468
30468
|
};
|
|
30469
30469
|
var levels$E = {
|
|
@@ -30481,11 +30481,26 @@ var migrations = {
|
|
|
30481
30481
|
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.",
|
|
30482
30482
|
rules: {
|
|
30483
30483
|
identity: "code unchanged; a v3 list naming it reads the same in v4",
|
|
30484
|
-
row: "the v3 code is retired; a stored list naming it reads as the listed v4 successor(s)",
|
|
30484
|
+
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)",
|
|
30485
30485
|
category: "a category-grain v3 selection (a purpose payload, a partner rule, a policy) reads as the listed v4 codes only — never widened",
|
|
30486
30486
|
subtract: "a v3 RESTRICTION (a policy that forbids a code) keeps restricting the listed v4 rows",
|
|
30487
|
-
"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)",
|
|
30488
|
-
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;
|
|
30487
|
+
"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)`",
|
|
30488
|
+
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`)",
|
|
30489
|
+
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",
|
|
30490
|
+
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)",
|
|
30491
|
+
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"
|
|
30492
|
+
},
|
|
30493
|
+
ruling: {
|
|
30494
|
+
date: "2026-10-09",
|
|
30495
|
+
by: "Crysta",
|
|
30496
|
+
source: "Slack DM thread, https://htilabs-us.slack.com/archives/D0811D2R6QN/p1791581735053759?thread_ts=1791580621.618429&cid=D0811D2R6QN (16:35 CDT)",
|
|
30497
|
+
text: [
|
|
30498
|
+
"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.",
|
|
30499
|
+
"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."
|
|
30500
|
+
],
|
|
30501
|
+
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",
|
|
30502
|
+
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`).",
|
|
30503
|
+
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`)."
|
|
30489
30504
|
},
|
|
30490
30505
|
table: [
|
|
30491
30506
|
{
|
|
@@ -30746,7 +30761,10 @@ var migrations = {
|
|
|
30746
30761
|
"236-007-001-000-000-000-000"
|
|
30747
30762
|
],
|
|
30748
30763
|
note: "code unchanged",
|
|
30749
|
-
widens: true
|
|
30764
|
+
widens: true,
|
|
30765
|
+
releaseReading: "successor",
|
|
30766
|
+
policyReading: "successor",
|
|
30767
|
+
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."
|
|
30750
30768
|
},
|
|
30751
30769
|
{
|
|
30752
30770
|
from: "screen_indicators",
|
|
@@ -31462,8 +31480,10 @@ var migrations = {
|
|
|
31462
31480
|
toCodes: [
|
|
31463
31481
|
"236-006-010-000-000-000-000"
|
|
31464
31482
|
],
|
|
31465
|
-
note: "
|
|
31466
|
-
widens: true
|
|
31483
|
+
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)",
|
|
31484
|
+
widens: true,
|
|
31485
|
+
releaseReading: "retain",
|
|
31486
|
+
policyReading: "successor"
|
|
31467
31487
|
},
|
|
31468
31488
|
{
|
|
31469
31489
|
from: "substance_use_status",
|
|
@@ -31475,8 +31495,10 @@ var migrations = {
|
|
|
31475
31495
|
toCodes: [
|
|
31476
31496
|
"236-006-010-000-000-000-000"
|
|
31477
31497
|
],
|
|
31478
|
-
note: "
|
|
31479
|
-
widens: true
|
|
31498
|
+
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)",
|
|
31499
|
+
widens: true,
|
|
31500
|
+
releaseReading: "retain",
|
|
31501
|
+
policyReading: "successor"
|
|
31480
31502
|
},
|
|
31481
31503
|
{
|
|
31482
31504
|
from: "chronic_health_status",
|
|
@@ -31488,8 +31510,10 @@ var migrations = {
|
|
|
31488
31510
|
toCodes: [
|
|
31489
31511
|
"236-006-010-000-000-000-000"
|
|
31490
31512
|
],
|
|
31491
|
-
note: "
|
|
31492
|
-
widens: true
|
|
31513
|
+
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)",
|
|
31514
|
+
widens: true,
|
|
31515
|
+
releaseReading: "retain",
|
|
31516
|
+
policyReading: "successor"
|
|
31493
31517
|
},
|
|
31494
31518
|
{
|
|
31495
31519
|
from: "disability_subtypes",
|
|
@@ -31501,8 +31525,10 @@ var migrations = {
|
|
|
31501
31525
|
toCodes: [
|
|
31502
31526
|
"236-006-010-000-000-000-000"
|
|
31503
31527
|
],
|
|
31504
|
-
note: "
|
|
31505
|
-
widens: true
|
|
31528
|
+
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)",
|
|
31529
|
+
widens: true,
|
|
31530
|
+
releaseReading: "retain",
|
|
31531
|
+
policyReading: "successor"
|
|
31506
31532
|
},
|
|
31507
31533
|
{
|
|
31508
31534
|
from: "hiv_status",
|
|
@@ -31514,8 +31540,10 @@ var migrations = {
|
|
|
31514
31540
|
toCodes: [
|
|
31515
31541
|
"236-006-010-000-000-000-000"
|
|
31516
31542
|
],
|
|
31517
|
-
note: "
|
|
31518
|
-
widens: true
|
|
31543
|
+
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)",
|
|
31544
|
+
widens: true,
|
|
31545
|
+
releaseReading: "retain",
|
|
31546
|
+
policyReading: "successor"
|
|
31519
31547
|
},
|
|
31520
31548
|
{
|
|
31521
31549
|
from: "uscis_alien_number",
|
|
@@ -31527,8 +31555,10 @@ var migrations = {
|
|
|
31527
31555
|
toCodes: [
|
|
31528
31556
|
"236-007-001-000-000-000-000"
|
|
31529
31557
|
],
|
|
31530
|
-
note: "
|
|
31531
|
-
widens: true
|
|
31558
|
+
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)",
|
|
31559
|
+
widens: true,
|
|
31560
|
+
releaseReading: "retain",
|
|
31561
|
+
policyReading: "successor"
|
|
31532
31562
|
},
|
|
31533
31563
|
{
|
|
31534
31564
|
from: "federal_protection_applications",
|
|
@@ -31540,8 +31570,10 @@ var migrations = {
|
|
|
31540
31570
|
toCodes: [
|
|
31541
31571
|
"236-007-006-000-000-000-000"
|
|
31542
31572
|
],
|
|
31543
|
-
note: "
|
|
31544
|
-
widens: true
|
|
31573
|
+
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)",
|
|
31574
|
+
widens: true,
|
|
31575
|
+
releaseReading: "retain",
|
|
31576
|
+
policyReading: "successor"
|
|
31545
31577
|
},
|
|
31546
31578
|
{
|
|
31547
31579
|
from: "tvap_enrollment",
|
|
@@ -31553,8 +31585,10 @@ var migrations = {
|
|
|
31553
31585
|
toCodes: [
|
|
31554
31586
|
"236-007-006-000-000-000-000"
|
|
31555
31587
|
],
|
|
31556
|
-
note: "
|
|
31557
|
-
widens: true
|
|
31588
|
+
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)",
|
|
31589
|
+
widens: true,
|
|
31590
|
+
releaseReading: "retain",
|
|
31591
|
+
policyReading: "successor"
|
|
31558
31592
|
},
|
|
31559
31593
|
{
|
|
31560
31594
|
from: "le_report_status",
|
|
@@ -31566,8 +31600,10 @@ var migrations = {
|
|
|
31566
31600
|
toCodes: [
|
|
31567
31601
|
"236-007-006-000-000-000-000"
|
|
31568
31602
|
],
|
|
31569
|
-
note: "
|
|
31570
|
-
widens: true
|
|
31603
|
+
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)",
|
|
31604
|
+
widens: true,
|
|
31605
|
+
releaseReading: "retain",
|
|
31606
|
+
policyReading: "successor"
|
|
31571
31607
|
},
|
|
31572
31608
|
{
|
|
31573
31609
|
from: "risk",
|
|
@@ -31620,8 +31656,9 @@ var migrations = {
|
|
|
31620
31656
|
"236-013-002-006-000-000-000",
|
|
31621
31657
|
"236-013-001-006-000-000-000"
|
|
31622
31658
|
],
|
|
31623
|
-
note: "via v3: full_ida summary_ida",
|
|
31624
|
-
widens: false
|
|
31659
|
+
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",
|
|
31660
|
+
widens: false,
|
|
31661
|
+
informational: true
|
|
31625
31662
|
},
|
|
31626
31663
|
{
|
|
31627
31664
|
from: "ida_consid",
|
|
@@ -31633,8 +31670,9 @@ var migrations = {
|
|
|
31633
31670
|
toCodes: [
|
|
31634
31671
|
"236-013-001-006-000-000-000"
|
|
31635
31672
|
],
|
|
31636
|
-
note: "via v3: summary_ida",
|
|
31637
|
-
widens: false
|
|
31673
|
+
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",
|
|
31674
|
+
widens: false,
|
|
31675
|
+
informational: true
|
|
31638
31676
|
},
|
|
31639
31677
|
{
|
|
31640
31678
|
from: "initial_screen",
|
|
@@ -31646,8 +31684,9 @@ var migrations = {
|
|
|
31646
31684
|
toCodes: [
|
|
31647
31685
|
"236-013-001-001-000-000-000"
|
|
31648
31686
|
],
|
|
31649
|
-
note: "via v3: summary_initial_screen",
|
|
31650
|
-
widens: false
|
|
31687
|
+
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",
|
|
31688
|
+
widens: false,
|
|
31689
|
+
informational: true
|
|
31651
31690
|
},
|
|
31652
31691
|
{
|
|
31653
31692
|
from: "tra",
|
|
@@ -31659,8 +31698,9 @@ var migrations = {
|
|
|
31659
31698
|
toCodes: [
|
|
31660
31699
|
"236-013-001-013-000-000-000"
|
|
31661
31700
|
],
|
|
31662
|
-
note: "via v3: summary_tra",
|
|
31663
|
-
widens: false
|
|
31701
|
+
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",
|
|
31702
|
+
widens: false,
|
|
31703
|
+
informational: true
|
|
31664
31704
|
},
|
|
31665
31705
|
{
|
|
31666
31706
|
from: "lap",
|
|
@@ -31672,8 +31712,9 @@ var migrations = {
|
|
|
31672
31712
|
toCodes: [
|
|
31673
31713
|
"236-013-001-007-000-000-000"
|
|
31674
31714
|
],
|
|
31675
|
-
note: "via v3: summary_lap",
|
|
31676
|
-
widens: false
|
|
31715
|
+
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",
|
|
31716
|
+
widens: false,
|
|
31717
|
+
informational: true
|
|
31677
31718
|
},
|
|
31678
31719
|
{
|
|
31679
31720
|
from: "danger_assessment",
|
|
@@ -31685,8 +31726,9 @@ var migrations = {
|
|
|
31685
31726
|
toCodes: [
|
|
31686
31727
|
"236-013-001-008-000-000-000"
|
|
31687
31728
|
],
|
|
31688
|
-
note: "via v3: summary_danger_assessment",
|
|
31689
|
-
widens: false
|
|
31729
|
+
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",
|
|
31730
|
+
widens: false,
|
|
31731
|
+
informational: true
|
|
31690
31732
|
},
|
|
31691
31733
|
{
|
|
31692
31734
|
from: "injury_and_strangulation",
|
|
@@ -31698,8 +31740,9 @@ var migrations = {
|
|
|
31698
31740
|
toCodes: [
|
|
31699
31741
|
"236-013-001-010-000-000-000"
|
|
31700
31742
|
],
|
|
31701
|
-
note: "via v3: summary_injury_and_strangulation",
|
|
31702
|
-
widens: false
|
|
31743
|
+
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",
|
|
31744
|
+
widens: false,
|
|
31745
|
+
informational: true
|
|
31703
31746
|
},
|
|
31704
31747
|
{
|
|
31705
31748
|
from: "stalking_assessment",
|
|
@@ -31711,8 +31754,9 @@ var migrations = {
|
|
|
31711
31754
|
toCodes: [
|
|
31712
31755
|
"236-013-001-009-000-000-000"
|
|
31713
31756
|
],
|
|
31714
|
-
note: "via v3: summary_stalking_assessment",
|
|
31715
|
-
widens: false
|
|
31757
|
+
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",
|
|
31758
|
+
widens: false,
|
|
31759
|
+
informational: true
|
|
31716
31760
|
},
|
|
31717
31761
|
{
|
|
31718
31762
|
from: "ae_intake",
|
|
@@ -31724,8 +31768,9 @@ var migrations = {
|
|
|
31724
31768
|
toCodes: [
|
|
31725
31769
|
"236-013-001-005-000-000-000"
|
|
31726
31770
|
],
|
|
31727
|
-
note: "via v3: summary_ae_intake",
|
|
31728
|
-
widens: false
|
|
31771
|
+
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",
|
|
31772
|
+
widens: false,
|
|
31773
|
+
informational: true
|
|
31729
31774
|
},
|
|
31730
31775
|
{
|
|
31731
31776
|
from: "hope_scale",
|
|
@@ -31737,8 +31782,9 @@ var migrations = {
|
|
|
31737
31782
|
toCodes: [
|
|
31738
31783
|
"236-013-001-011-000-000-000"
|
|
31739
31784
|
],
|
|
31740
|
-
note: "via v3: summary_hope_scale",
|
|
31741
|
-
widens: false
|
|
31785
|
+
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",
|
|
31786
|
+
widens: false,
|
|
31787
|
+
informational: true
|
|
31742
31788
|
},
|
|
31743
31789
|
{
|
|
31744
31790
|
from: "assessment_records",
|
|
@@ -31748,8 +31794,9 @@ var migrations = {
|
|
|
31748
31794
|
],
|
|
31749
31795
|
toCodes: [
|
|
31750
31796
|
],
|
|
31751
|
-
note: "retired with no successor row (R30); the lifecycle lines are not share content",
|
|
31752
|
-
widens: false
|
|
31797
|
+
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",
|
|
31798
|
+
widens: false,
|
|
31799
|
+
informational: true
|
|
31753
31800
|
},
|
|
31754
31801
|
{
|
|
31755
31802
|
from: "determinations",
|
|
@@ -31761,8 +31808,9 @@ var migrations = {
|
|
|
31761
31808
|
toCodes: [
|
|
31762
31809
|
"236-013-001-014-000-000-000"
|
|
31763
31810
|
],
|
|
31764
|
-
note: "via v3: summary_findings",
|
|
31765
|
-
widens: false
|
|
31811
|
+
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",
|
|
31812
|
+
widens: false,
|
|
31813
|
+
informational: true
|
|
31766
31814
|
},
|
|
31767
31815
|
{
|
|
31768
31816
|
from: "mental_health_screen",
|
|
@@ -31774,8 +31822,9 @@ var migrations = {
|
|
|
31774
31822
|
toCodes: [
|
|
31775
31823
|
"236-013-001-002-000-000-000"
|
|
31776
31824
|
],
|
|
31777
|
-
note: "via v3: summary_mental_health_screen",
|
|
31778
|
-
widens: false
|
|
31825
|
+
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",
|
|
31826
|
+
widens: false,
|
|
31827
|
+
informational: true
|
|
31779
31828
|
},
|
|
31780
31829
|
{
|
|
31781
31830
|
from: "trauma_and_coping_screen",
|
|
@@ -31787,8 +31836,9 @@ var migrations = {
|
|
|
31787
31836
|
toCodes: [
|
|
31788
31837
|
"236-013-001-004-000-000-000"
|
|
31789
31838
|
],
|
|
31790
|
-
note: "via v3: summary_trauma_and_coping_screen",
|
|
31791
|
-
widens: false
|
|
31839
|
+
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",
|
|
31840
|
+
widens: false,
|
|
31841
|
+
informational: true
|
|
31792
31842
|
},
|
|
31793
31843
|
{
|
|
31794
31844
|
from: "behavioral_health_intake",
|
|
@@ -31800,8 +31850,9 @@ var migrations = {
|
|
|
31800
31850
|
toCodes: [
|
|
31801
31851
|
"236-013-001-003-000-000-000"
|
|
31802
31852
|
],
|
|
31803
|
-
note: "via v3: summary_behavioral_health_intake",
|
|
31804
|
-
widens: false
|
|
31853
|
+
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",
|
|
31854
|
+
widens: false,
|
|
31855
|
+
informational: true
|
|
31805
31856
|
},
|
|
31806
31857
|
{
|
|
31807
31858
|
from: "screen_notes",
|
|
@@ -31811,8 +31862,9 @@ var migrations = {
|
|
|
31811
31862
|
],
|
|
31812
31863
|
toCodes: [
|
|
31813
31864
|
],
|
|
31814
|
-
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",
|
|
31815
|
-
widens: false
|
|
31865
|
+
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",
|
|
31866
|
+
widens: false,
|
|
31867
|
+
informational: true
|
|
31816
31868
|
},
|
|
31817
31869
|
{
|
|
31818
31870
|
from: "background",
|
|
@@ -31822,8 +31874,9 @@ var migrations = {
|
|
|
31822
31874
|
],
|
|
31823
31875
|
toCodes: [
|
|
31824
31876
|
],
|
|
31825
|
-
note: "retired 2026-10-05 — nothing ever captured it (Crysta to Nate: Eliminate)",
|
|
31826
|
-
widens: false
|
|
31877
|
+
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",
|
|
31878
|
+
widens: false,
|
|
31879
|
+
informational: true
|
|
31827
31880
|
}
|
|
31828
31881
|
]
|
|
31829
31882
|
};
|
|
@@ -33048,7 +33101,7 @@ var entries$E = [
|
|
|
33048
33101
|
],
|
|
33049
33102
|
childKeys: [
|
|
33050
33103
|
],
|
|
33051
|
-
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
|
|
33104
|
+
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.",
|
|
33052
33105
|
retired: true,
|
|
33053
33106
|
status: "retired",
|
|
33054
33107
|
successors: [
|
|
@@ -33057,7 +33110,13 @@ var entries$E = [
|
|
|
33057
33110
|
successorCodes: [
|
|
33058
33111
|
"236-006-010-000-000-000-000"
|
|
33059
33112
|
],
|
|
33060
|
-
migrationRule: "row"
|
|
33113
|
+
migrationRule: "row",
|
|
33114
|
+
v3Fields: [
|
|
33115
|
+
"capture.has_disability"
|
|
33116
|
+
],
|
|
33117
|
+
v3Domains: [
|
|
33118
|
+
"access_accommodations"
|
|
33119
|
+
]
|
|
33061
33120
|
},
|
|
33062
33121
|
{
|
|
33063
33122
|
code: "236-006-003-000-000-000-000",
|
|
@@ -33070,7 +33129,7 @@ var entries$E = [
|
|
|
33070
33129
|
],
|
|
33071
33130
|
childKeys: [
|
|
33072
33131
|
],
|
|
33073
|
-
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
|
|
33132
|
+
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.",
|
|
33074
33133
|
retired: true,
|
|
33075
33134
|
status: "retired",
|
|
33076
33135
|
successors: [
|
|
@@ -33079,7 +33138,13 @@ var entries$E = [
|
|
|
33079
33138
|
successorCodes: [
|
|
33080
33139
|
"236-006-010-000-000-000-000"
|
|
33081
33140
|
],
|
|
33082
|
-
migrationRule: "row"
|
|
33141
|
+
migrationRule: "row",
|
|
33142
|
+
v3Fields: [
|
|
33143
|
+
"capture.mental_health_status"
|
|
33144
|
+
],
|
|
33145
|
+
v3Domains: [
|
|
33146
|
+
"access_accommodations"
|
|
33147
|
+
]
|
|
33083
33148
|
},
|
|
33084
33149
|
{
|
|
33085
33150
|
code: "236-006-004-000-000-000-000",
|
|
@@ -33092,7 +33157,7 @@ var entries$E = [
|
|
|
33092
33157
|
],
|
|
33093
33158
|
childKeys: [
|
|
33094
33159
|
],
|
|
33095
|
-
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
|
|
33160
|
+
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.",
|
|
33096
33161
|
retired: true,
|
|
33097
33162
|
status: "retired",
|
|
33098
33163
|
successors: [
|
|
@@ -33101,7 +33166,13 @@ var entries$E = [
|
|
|
33101
33166
|
successorCodes: [
|
|
33102
33167
|
"236-006-010-000-000-000-000"
|
|
33103
33168
|
],
|
|
33104
|
-
migrationRule: "row"
|
|
33169
|
+
migrationRule: "row",
|
|
33170
|
+
v3Fields: [
|
|
33171
|
+
"capture.substance_use_status"
|
|
33172
|
+
],
|
|
33173
|
+
v3Domains: [
|
|
33174
|
+
"access_accommodations"
|
|
33175
|
+
]
|
|
33105
33176
|
},
|
|
33106
33177
|
{
|
|
33107
33178
|
code: "236-006-005-000-000-000-000",
|
|
@@ -33114,7 +33185,7 @@ var entries$E = [
|
|
|
33114
33185
|
],
|
|
33115
33186
|
childKeys: [
|
|
33116
33187
|
],
|
|
33117
|
-
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
|
|
33188
|
+
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.",
|
|
33118
33189
|
retired: true,
|
|
33119
33190
|
status: "retired",
|
|
33120
33191
|
successors: [
|
|
@@ -33123,7 +33194,14 @@ var entries$E = [
|
|
|
33123
33194
|
successorCodes: [
|
|
33124
33195
|
"236-006-010-000-000-000-000"
|
|
33125
33196
|
],
|
|
33126
|
-
migrationRule: "row"
|
|
33197
|
+
migrationRule: "row",
|
|
33198
|
+
v3Fields: [
|
|
33199
|
+
"capture.chronic_health_severity",
|
|
33200
|
+
"capture.long_term_conditions"
|
|
33201
|
+
],
|
|
33202
|
+
v3Domains: [
|
|
33203
|
+
"access_accommodations"
|
|
33204
|
+
]
|
|
33127
33205
|
},
|
|
33128
33206
|
{
|
|
33129
33207
|
code: "236-006-006-000-000-000-000",
|
|
@@ -33136,7 +33214,7 @@ var entries$E = [
|
|
|
33136
33214
|
],
|
|
33137
33215
|
childKeys: [
|
|
33138
33216
|
],
|
|
33139
|
-
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
|
|
33217
|
+
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.",
|
|
33140
33218
|
retired: true,
|
|
33141
33219
|
status: "retired",
|
|
33142
33220
|
successors: [
|
|
@@ -33145,7 +33223,13 @@ var entries$E = [
|
|
|
33145
33223
|
successorCodes: [
|
|
33146
33224
|
"236-006-010-000-000-000-000"
|
|
33147
33225
|
],
|
|
33148
|
-
migrationRule: "row"
|
|
33226
|
+
migrationRule: "row",
|
|
33227
|
+
v3Fields: [
|
|
33228
|
+
"capture.hiv_status"
|
|
33229
|
+
],
|
|
33230
|
+
v3Domains: [
|
|
33231
|
+
"access_accommodations"
|
|
33232
|
+
]
|
|
33149
33233
|
},
|
|
33150
33234
|
{
|
|
33151
33235
|
code: "236-006-007-000-000-000-000",
|
|
@@ -33326,7 +33410,7 @@ var entries$E = [
|
|
|
33326
33410
|
],
|
|
33327
33411
|
childKeys: [
|
|
33328
33412
|
],
|
|
33329
|
-
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
|
|
33413
|
+
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.",
|
|
33330
33414
|
retired: true,
|
|
33331
33415
|
status: "retired",
|
|
33332
33416
|
successors: [
|
|
@@ -33335,7 +33419,12 @@ var entries$E = [
|
|
|
33335
33419
|
successorCodes: [
|
|
33336
33420
|
"236-007-001-000-000-000-000"
|
|
33337
33421
|
],
|
|
33338
|
-
migrationRule: "row"
|
|
33422
|
+
migrationRule: "row",
|
|
33423
|
+
v3Fields: [
|
|
33424
|
+
],
|
|
33425
|
+
v3Domains: [
|
|
33426
|
+
],
|
|
33427
|
+
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."
|
|
33339
33428
|
},
|
|
33340
33429
|
{
|
|
33341
33430
|
code: "236-007-003-000-000-000-000",
|
|
@@ -33348,7 +33437,7 @@ var entries$E = [
|
|
|
33348
33437
|
],
|
|
33349
33438
|
childKeys: [
|
|
33350
33439
|
],
|
|
33351
|
-
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
|
|
33440
|
+
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.",
|
|
33352
33441
|
retired: true,
|
|
33353
33442
|
status: "retired",
|
|
33354
33443
|
successors: [
|
|
@@ -33357,7 +33446,13 @@ var entries$E = [
|
|
|
33357
33446
|
successorCodes: [
|
|
33358
33447
|
"236-007-006-000-000-000-000"
|
|
33359
33448
|
],
|
|
33360
|
-
migrationRule: "row"
|
|
33449
|
+
migrationRule: "row",
|
|
33450
|
+
v3Fields: [
|
|
33451
|
+
"capture.legal_action_type"
|
|
33452
|
+
],
|
|
33453
|
+
v3Domains: [
|
|
33454
|
+
"immigration_legal_status"
|
|
33455
|
+
]
|
|
33361
33456
|
},
|
|
33362
33457
|
{
|
|
33363
33458
|
code: "236-007-004-000-000-000-000",
|
|
@@ -33370,7 +33465,7 @@ var entries$E = [
|
|
|
33370
33465
|
],
|
|
33371
33466
|
childKeys: [
|
|
33372
33467
|
],
|
|
33373
|
-
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
|
|
33468
|
+
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.",
|
|
33374
33469
|
retired: true,
|
|
33375
33470
|
status: "retired",
|
|
33376
33471
|
successors: [
|
|
@@ -33379,7 +33474,12 @@ var entries$E = [
|
|
|
33379
33474
|
successorCodes: [
|
|
33380
33475
|
"236-007-006-000-000-000-000"
|
|
33381
33476
|
],
|
|
33382
|
-
migrationRule: "row"
|
|
33477
|
+
migrationRule: "row",
|
|
33478
|
+
v3Fields: [
|
|
33479
|
+
],
|
|
33480
|
+
v3Domains: [
|
|
33481
|
+
],
|
|
33482
|
+
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."
|
|
33383
33483
|
},
|
|
33384
33484
|
{
|
|
33385
33485
|
code: "236-007-005-000-000-000-000",
|
|
@@ -33392,7 +33492,7 @@ var entries$E = [
|
|
|
33392
33492
|
],
|
|
33393
33493
|
childKeys: [
|
|
33394
33494
|
],
|
|
33395
|
-
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
|
|
33495
|
+
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.",
|
|
33396
33496
|
retired: true,
|
|
33397
33497
|
status: "retired",
|
|
33398
33498
|
successors: [
|
|
@@ -33401,7 +33501,13 @@ var entries$E = [
|
|
|
33401
33501
|
successorCodes: [
|
|
33402
33502
|
"236-007-006-000-000-000-000"
|
|
33403
33503
|
],
|
|
33404
|
-
migrationRule: "row"
|
|
33504
|
+
migrationRule: "row",
|
|
33505
|
+
v3Fields: [
|
|
33506
|
+
"capture.le_report_status"
|
|
33507
|
+
],
|
|
33508
|
+
v3Domains: [
|
|
33509
|
+
"immigration_legal_status"
|
|
33510
|
+
]
|
|
33405
33511
|
},
|
|
33406
33512
|
{
|
|
33407
33513
|
code: "236-007-006-000-000-000-000",
|
|
@@ -36106,7 +36212,7 @@ var entries$E = [
|
|
|
36106
36212
|
kindRow: "relationships_household"
|
|
36107
36213
|
}
|
|
36108
36214
|
];
|
|
36109
|
-
var
|
|
36215
|
+
var coreInformationScope_v2_1_0 = {
|
|
36110
36216
|
domain: domain$E,
|
|
36111
36217
|
name: name$E,
|
|
36112
36218
|
version: version$E,
|
|
@@ -36121,9 +36227,9 @@ var coreInformationScope_v2_0_0 = {
|
|
|
36121
36227
|
|
|
36122
36228
|
var domain$D = "roi_scope";
|
|
36123
36229
|
var name$D = "ROI Scope";
|
|
36124
|
-
var version$D = "1.
|
|
36125
|
-
var _status$C = "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`
|
|
36126
|
-
var _source$C = "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.
|
|
36230
|
+
var version$D = "1.4.0";
|
|
36231
|
+
var _status$C = "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`).";
|
|
36232
|
+
var _source$C = "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)";
|
|
36127
36233
|
var _supersedes = {
|
|
36128
36234
|
version: "1.2.0",
|
|
36129
36235
|
keyMap: {
|
|
@@ -36162,18 +36268,18 @@ var _supersedes = {
|
|
|
36162
36268
|
retiredCodes: [
|
|
36163
36269
|
],
|
|
36164
36270
|
notes: {
|
|
36165
|
-
summary: "Every v1.2.0 key is still an entry
|
|
36166
|
-
ida_full: "v1.2.0 `ida_full` was a selectable item. CVC-236
|
|
36167
|
-
ida_consid: "v1.2.0 `ida_consid` was a selectable item. CVC-236
|
|
36168
|
-
disability_subtypes: "v1.2.0 `disability_subtypes` was a selectable item. CVC-236
|
|
36169
|
-
mental_health_status: "v1.2.0 `mental_health_status` was a selectable item. CVC-236
|
|
36170
|
-
substance_use_status: "v1.2.0 `substance_use_status` was a selectable item. CVC-236
|
|
36171
|
-
chronic_health_status: "v1.2.0 `chronic_health_status` was a selectable item. CVC-236
|
|
36172
|
-
hiv_status: "v1.2.0 `hiv_status` was a selectable item. CVC-236
|
|
36173
|
-
uscis_alien_number: "v1.2.0 `uscis_alien_number` was a selectable item. CVC-236
|
|
36174
|
-
federal_protection_applications: "v1.2.0 `federal_protection_applications` was a selectable item. CVC-236
|
|
36175
|
-
tvap_enrollment: "v1.2.0 `tvap_enrollment` was a selectable item. CVC-236
|
|
36176
|
-
le_report_status: "v1.2.0 `le_report_status` was a selectable item. CVC-236
|
|
36271
|
+
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.",
|
|
36272
|
+
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).",
|
|
36273
|
+
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).",
|
|
36274
|
+
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`).",
|
|
36275
|
+
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`).",
|
|
36276
|
+
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`).",
|
|
36277
|
+
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`).",
|
|
36278
|
+
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`).",
|
|
36279
|
+
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`).",
|
|
36280
|
+
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`).",
|
|
36281
|
+
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`).",
|
|
36282
|
+
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`)."
|
|
36177
36283
|
}
|
|
36178
36284
|
};
|
|
36179
36285
|
var levels$D = {
|
|
@@ -36302,7 +36408,7 @@ var entries$D = [
|
|
|
36302
36408
|
parentCode: null,
|
|
36303
36409
|
childCodes: [
|
|
36304
36410
|
],
|
|
36305
|
-
definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.
|
|
36411
|
+
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.",
|
|
36306
36412
|
retired: true
|
|
36307
36413
|
},
|
|
36308
36414
|
{
|
|
@@ -36313,7 +36419,7 @@ var entries$D = [
|
|
|
36313
36419
|
parentCode: null,
|
|
36314
36420
|
childCodes: [
|
|
36315
36421
|
],
|
|
36316
|
-
definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.
|
|
36422
|
+
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.",
|
|
36317
36423
|
retired: true
|
|
36318
36424
|
},
|
|
36319
36425
|
{
|
|
@@ -36406,7 +36512,7 @@ var entries$D = [
|
|
|
36406
36512
|
parentCode: null,
|
|
36407
36513
|
childCodes: [
|
|
36408
36514
|
],
|
|
36409
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
36515
|
+
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.",
|
|
36410
36516
|
retired: true
|
|
36411
36517
|
},
|
|
36412
36518
|
{
|
|
@@ -36417,7 +36523,7 @@ var entries$D = [
|
|
|
36417
36523
|
parentCode: null,
|
|
36418
36524
|
childCodes: [
|
|
36419
36525
|
],
|
|
36420
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
36526
|
+
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.",
|
|
36421
36527
|
retired: true
|
|
36422
36528
|
},
|
|
36423
36529
|
{
|
|
@@ -36428,7 +36534,7 @@ var entries$D = [
|
|
|
36428
36534
|
parentCode: null,
|
|
36429
36535
|
childCodes: [
|
|
36430
36536
|
],
|
|
36431
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
36537
|
+
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.",
|
|
36432
36538
|
retired: true
|
|
36433
36539
|
},
|
|
36434
36540
|
{
|
|
@@ -36439,7 +36545,7 @@ var entries$D = [
|
|
|
36439
36545
|
parentCode: null,
|
|
36440
36546
|
childCodes: [
|
|
36441
36547
|
],
|
|
36442
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
36548
|
+
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.",
|
|
36443
36549
|
retired: true
|
|
36444
36550
|
},
|
|
36445
36551
|
{
|
|
@@ -36450,7 +36556,7 @@ var entries$D = [
|
|
|
36450
36556
|
parentCode: null,
|
|
36451
36557
|
childCodes: [
|
|
36452
36558
|
],
|
|
36453
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
36559
|
+
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.",
|
|
36454
36560
|
retired: true
|
|
36455
36561
|
},
|
|
36456
36562
|
{
|
|
@@ -36471,7 +36577,7 @@ var entries$D = [
|
|
|
36471
36577
|
parentCode: null,
|
|
36472
36578
|
childCodes: [
|
|
36473
36579
|
],
|
|
36474
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
36580
|
+
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.",
|
|
36475
36581
|
retired: true
|
|
36476
36582
|
},
|
|
36477
36583
|
{
|
|
@@ -36482,7 +36588,7 @@ var entries$D = [
|
|
|
36482
36588
|
parentCode: null,
|
|
36483
36589
|
childCodes: [
|
|
36484
36590
|
],
|
|
36485
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
36591
|
+
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.",
|
|
36486
36592
|
retired: true
|
|
36487
36593
|
},
|
|
36488
36594
|
{
|
|
@@ -36493,7 +36599,7 @@ var entries$D = [
|
|
|
36493
36599
|
parentCode: null,
|
|
36494
36600
|
childCodes: [
|
|
36495
36601
|
],
|
|
36496
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
36602
|
+
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.",
|
|
36497
36603
|
retired: true
|
|
36498
36604
|
},
|
|
36499
36605
|
{
|
|
@@ -36504,11 +36610,11 @@ var entries$D = [
|
|
|
36504
36610
|
parentCode: null,
|
|
36505
36611
|
childCodes: [
|
|
36506
36612
|
],
|
|
36507
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR § 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
36613
|
+
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.",
|
|
36508
36614
|
retired: true
|
|
36509
36615
|
}
|
|
36510
36616
|
];
|
|
36511
|
-
var
|
|
36617
|
+
var roiScope_v1_4_0 = {
|
|
36512
36618
|
domain: domain$D,
|
|
36513
36619
|
name: name$D,
|
|
36514
36620
|
version: version$D,
|
|
@@ -53907,4 +54013,4 @@ var criminalOrgCategory_v1_0_0 = {
|
|
|
53907
54013
|
entries: entries
|
|
53908
54014
|
};
|
|
53909
54015
|
|
|
53910
|
-
export { accommodationType_v1_0_0 as accommodationTypeSot, actionStepCompletionStatus_v1_0_0 as actionStepCompletionStatusSot, actionStepType_v1_0_0 as actionStepTypeSot, activityType_v1_0_0 as activityTypeSot, adminRoles_v1_0_0 as adminRolesSot, administeringJurisdiction_v1_0_0 as administeringJurisdictionSot, ageBinReporting_v1_0_0 as ageBinReportingSot, announcementAudienceScope_v1_0_0 as announcementAudienceScopeSot, announcementResponseType_v1_0_0 as announcementResponseTypeSot, assertionDomain_v1_1_0 as assertionDomainSot, assertionStatus_v1_0_0 as assertionStatusSot, basisQuickPicks_v1_0_0 as basisQuickPicksSot, carCorrectionReason_v1_0_0 as carCorrectionReasonSot, caseShareState_v1_0_0 as caseShareStateSot, checkInActivity_v1_0_0 as checkInActivitySot, checkInPhase_v1_1_0 as checkInPhaseSot, childBehavioralConcerns_v1_0_0 as childBehavioralConcernsSot, childChangeType_v1_0_0 as childChangeTypeSot, childCustodyArrangement_v1_0_0 as childCustodyArrangementSot, citizenship_v1_0_0 as citizenshipSot, collectionContext_v1_0_0 as collectionContextSot, contactInfoTypes_v1_0_0 as contactInfoTypesSot, contactInfoUseType_v1_0_0 as contactInfoUseTypeSot, contactLinkType_v1_0_0 as contactLinkTypeSot, contactSafetyStatus_v1_0_0 as contactSafetyStatusSot, coreDhState_v1_0_0 as coreDhStateSot, coreFunctions_v1_1_0 as coreFunctionsSot, coreIndicators_v1_1_0 as coreIndicatorsSot,
|
|
54016
|
+
export { accommodationType_v1_0_0 as accommodationTypeSot, actionStepCompletionStatus_v1_0_0 as actionStepCompletionStatusSot, actionStepType_v1_0_0 as actionStepTypeSot, activityType_v1_0_0 as activityTypeSot, adminRoles_v1_0_0 as adminRolesSot, administeringJurisdiction_v1_0_0 as administeringJurisdictionSot, ageBinReporting_v1_0_0 as ageBinReportingSot, announcementAudienceScope_v1_0_0 as announcementAudienceScopeSot, announcementResponseType_v1_0_0 as announcementResponseTypeSot, assertionDomain_v1_1_0 as assertionDomainSot, assertionStatus_v1_0_0 as assertionStatusSot, basisQuickPicks_v1_0_0 as basisQuickPicksSot, carCorrectionReason_v1_0_0 as carCorrectionReasonSot, caseShareState_v1_0_0 as caseShareStateSot, checkInActivity_v1_0_0 as checkInActivitySot, checkInPhase_v1_1_0 as checkInPhaseSot, childBehavioralConcerns_v1_0_0 as childBehavioralConcernsSot, childChangeType_v1_0_0 as childChangeTypeSot, childCustodyArrangement_v1_0_0 as childCustodyArrangementSot, citizenship_v1_0_0 as citizenshipSot, collectionContext_v1_0_0 as collectionContextSot, contactInfoTypes_v1_0_0 as contactInfoTypesSot, contactInfoUseType_v1_0_0 as contactInfoUseTypeSot, contactLinkType_v1_0_0 as contactLinkTypeSot, contactSafetyStatus_v1_0_0 as contactSafetyStatusSot, coreDhState_v1_0_0 as coreDhStateSot, coreFunctions_v1_1_0 as coreFunctionsSot, coreIndicators_v1_1_0 as coreIndicatorsSot, coreInformationScope_v2_1_0 as coreInformationScopeSot, coreReferralOutcome_v1_0_0 as coreReferralOutcomeSot, countries_v1_0_0 as countriesSot, createdBySystem_v1_0_0 as createdBySystemSot, criminalOrgCategory_v1_0_0 as criminalOrgCategorySot, daIncidentArchiveReason_v1_0_0 as daIncidentArchiveReasonSot, daIncidentConfidence_v1_0_0 as daIncidentConfidenceSot, daIncidentDayApprox_v1_0_0 as daIncidentDayApproxSot, daIncidentSeverity_v1_0_0 as daIncidentSeveritySot, determinationHelperCategories_v1_0_0 as determinationHelperCategoriesSot, determinationLevel_v1_0_0 as determinationLevelSot, disabilitySubtype_v1_0_0 as disabilitySubtypeSot, discretionLevel_v1_0_0 as discretionLevelSot, emergencyContactCallReason_v1_0_0 as emergencyContactCallReasonSot, emergencyContactPermissions_v1_0_0 as emergencyContactPermissionsSot, emergencyExitCascade_v1_0_0 as emergencyExitCascadeSot, employmentStatus_v1_0_0 as employmentStatusSot, enrollmentApplicationStatus_v1_0_0 as enrollmentApplicationStatusSot, exitProcessChecklistItem_v1_0_0 as exitProcessChecklistItemSot, exitReasons_v1_0_0 as exitReasonsSot, exploitationType_v1_0_0 as exploitationTypeSot, eyeColor_v1_0_0 as eyeColorSot, facialHair_v1_0_0 as facialHairSot, facilitatorEntityType_v1_0_0 as facilitatorEntityTypeSot, facilitatorLabelUsedInSource_v1_0_0 as facilitatorLabelUsedInSourceSot, facilitatorSubrole_v1_0_0 as facilitatorSubroleSot, frequencyCadence_v1_0_0 as frequencyCadenceSot, funder_v1_0_0 as funderSot, genderIdentity_v1_0_0 as genderIdentitySot, goalCategory_v1_0_0 as goalCategorySot, goalPriority_v1_0_0 as goalPrioritySot, goalStatus_v1_0_0 as goalStatusSot, goalWithdrawalReason_v1_0_0 as goalWithdrawalReasonSot, hairColor_v1_0_0 as hairColorSot, hasTattoos_v1_0_0 as hasTattoosSot, highestEducationLevelCompleted_v1_1_0 as highestEducationLevelCompletedSot, hivStatus_v1_0_0 as hivStatusSot, hmisCurrentLivingSituation_v1_0_0 as hmisCurrentLivingSituationSot, hmisProjectType_v1_0_0 as hmisProjectTypeSot, hmisRelationshipToHoh_v1_0_0 as hmisRelationshipToHohSot, hmisSex_v1_0_0 as hmisSexSot, homelessStatus_v1_0_0 as homelessStatusSot, hopeScaleCaptureContext_v1_0_0 as hopeScaleCaptureContextSot, hopeScaleResponseOptions_v1_0_0 as hopeScaleResponseOptionsSot, hopeScaleTier_v1_0_0 as hopeScaleTierSot, housingSubsidyTypes_v1_0_0 as housingSubsidyTypesSot, htType_v1_0_0 as htTypeSot, identificationStatus_v1_0_0 as identificationStatusSot, immigrationLegalStatusChangeType_v1_0_0 as immigrationLegalStatusChangeTypeSot, incarcerationEpisodeType_v1_0_0 as incarcerationEpisodeTypeSot, incidentInvolvementRoles_v1_0_0 as incidentInvolvementRolesSot, incidentParticipationRoles_v1_1_0 as incidentParticipationRolesSot, incomeBenefitsSources_v1_1_0 as incomeBenefitsSourcesSot, inferenceType_v1_0_0 as inferenceTypeSot, investigativeRequestType_v1_0_0 as investigativeRequestTypeSot, juvenileJusticeEpisodeType_v1_0_0 as juvenileJusticeEpisodeTypeSot, juvenileJusticeInvolvementStatus_v1_0_0 as juvenileJusticeInvolvementStatusSot, languages_v1_0_0 as languagesSot, leReportStatus_v1_0_0 as leReportStatusSot, legalActionType_v1_0_0 as legalActionTypeSot, livingSituation_v1_0_0 as livingSituationSot, locationType_v1_0_0 as locationTypeSot, maritalStatusLegal_v1_0_0 as maritalStatusLegalSot, mentalHealthStatus_v1_0_0 as mentalHealthStatusSot, messageReportReason_v1_0_0 as messageReportReasonSot, midStayEventType_v1_0_0 as midStayEventTypeSot, milestoneType_v1_0_0 as milestoneTypeSot, militaryBranch_v1_0_0 as militaryBranchSot, militaryStatus_v1_0_0 as militaryStatusSot, minorAdultStatus_v1_0_0 as minorAdultStatusSot, nameType_v1_0_0 as nameTypeSot, needsAssessmentChangeType_v1_0_0 as needsAssessmentChangeTypeSot, needsResidentialAgain_v1_0_0 as needsResidentialAgainSot, offenderStatusFamily_v1_0_0 as offenderStatusFamilySot, offenderStatus_v1_0_0 as offenderStatusSot, orientationIdentity_v1_0_0 as orientationIdentitySot, personRelationships_v1_0_0 as personRelationshipsSot, petExitReason_v1_0_0 as petExitReasonSot, petRelationshipBasis_v1_0_0 as petRelationshipBasisSot, poPetitionBasis_v1_0_0 as poPetitionBasisSot, poStatus_v1_0_0 as poStatusSot, poViolationStatus_v1_0_0 as poViolationStatusSot, preferredContactMethod_v1_0_0 as preferredContactMethodSot, primaryLanguage_v1_0_0 as primaryLanguageSot, programEnrollmentChangeType_v1_0_0 as programEnrollmentChangeTypeSot, programSpecificCode_v1_0_0 as programSpecificCodeSot, pronouns_v1_0_0 as pronounsSot, proofOfIdType_v1_0_0 as proofOfIdTypeSot, provenanceSourceId_v1_0_0 as provenanceSourceIdSot, qualityFlags_v1_0_0 as qualityFlagsSot, raceEthnicity_v1_0_0 as raceEthnicitySot, radiusBucket_v1_0_0 as radiusBucketSot, recencyBand_v1_0_0 as recencyBandSot, referenceLinkType_v1_0_0 as referenceLinkTypeSot, referralEntityCategory_v1_2_0 as referralEntityCategorySot, referralOrigin_v1_0_0 as referralOriginSot, relationshipConcern_v1_0_0 as relationshipConcernSot, relationshipDynamics_v1_0_0 as relationshipDynamicsSot, relationshipStatusCurrent_v1_0_0 as relationshipStatusCurrentSot, relationshipTies_v1_0_0 as relationshipTiesSot, returnedToAbuserStatus_v1_0_0 as returnedToAbuserStatusSot, riskCategory_v1_0_0 as riskCategorySot, riskIdentificationMilestone_v1_0_0 as riskIdentificationMilestoneSot, riskSeverityBand_v1_0_0 as riskSeverityBandSot, roiMethod_v1_0_0 as roiMethodSot, roiScope_v1_4_0 as roiScopeSot, roiStatus_v1_0_0 as roiStatusSot, roleContext_v1_0_0 as roleContextSot, romanticRelationshipChangeType_v1_0_0 as romanticRelationshipChangeTypeSot, rsvpResponse_v1_0_0 as rsvpResponseSot, serviceAudience_v1_0_0 as serviceAudienceSot, serviceCategories_v1_2_0 as serviceCategoriesSot, serviceDeliveryChannel_v1_0_0 as serviceDeliveryChannelSot, serviceMechanisms_v1_0_0 as serviceMechanismsSot, servicePlanClosureReason_v1_0_0 as servicePlanClosureReasonSot, servicePlanReviewSnoozeReason_v1_0_0 as servicePlanReviewSnoozeReasonSot, serviceSource_v1_0_0 as serviceSourceSot, serviceStates_v1_1_0 as serviceStatesSot, sessionNoteVisibility_v1_0_0 as sessionNoteVisibilitySot, sessionState_v1_0_0 as sessionStateSot, sessionTemplate_v1_0_0 as sessionTemplateSot, severityFollowUp_v1_0_0 as severityFollowUpSot, sexProviderSubrole_v1_0_0 as sexProviderSubroleSot, sharePurpose_v1_0_0 as sharePurposeSot, shareResponseReason_v1_0_0 as shareResponseReasonSot, signatureMethod_v1_0_0 as signatureMethodSot, signatureType_v1_0_0 as signatureTypeSot, smtBodyLocation_v1_0_0 as smtBodyLocationSot, smtNameRelation_v1_0_0 as smtNameRelationSot, smtSignificanceFlags_v1_0_0 as smtSignificanceFlagsSot, smtType_v1_0_0 as smtTypeSot, sourceCategory_v1_1_0 as sourceCategorySot, sourceInstrument_v1_0_0 as sourceInstrumentSot, sourceSubtype_v1_2_0 as sourceSubtypeSot, sourceSystem_v1_0_0 as sourceSystemSot, specialNeedsDisabilities_v1_0_0 as specialNeedsDisabilitiesSot, subjectType_v1_0_0 as subjectTypeSot, substanceUseStatus_v1_0_0 as substanceUseStatusSot, suggestionSource_v1_0_0 as suggestionSourceSot, supportStrength_v1_0_0 as supportStrengthSot, supportTopic_v1_0_0 as supportTopicSot, threadStatus_v1_0_0 as threadStatusSot, threadType_v1_0_0 as threadTypeSot, timeScope_v1_0_0 as timeScopeSot, traffickingRelevantRole_v1_0_0 as traffickingRelevantRoleSot, tribes_v1_0_0 as tribesSot, userRoles_v1_0_0 as userRolesSot, verificationMethod_v1_1_0 as verificationMethodSot, verificationStatus_v1_0_0 as verificationStatusSot, victimAbuseTypes_v1_1_0 as victimAbuseTypesSot, victimStatusFamily_v1_0_0 as victimStatusFamilySot, visaType_v1_0_0 as visaTypeSot, whyNots_v1_0_0 as whyNotsSot };
|