@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.cjs
CHANGED
|
@@ -48,7 +48,7 @@ __export(cvcs_exports, {
|
|
|
48
48
|
coreDhStateSot: () => coreDhState_v1_0_0_default,
|
|
49
49
|
coreFunctionsSot: () => coreFunctions_v1_1_0_default,
|
|
50
50
|
coreIndicatorsSot: () => coreIndicators_v1_1_0_default,
|
|
51
|
-
coreInformationScopeSot: () =>
|
|
51
|
+
coreInformationScopeSot: () => coreInformationScope_v2_1_0_default,
|
|
52
52
|
coreReferralOutcomeSot: () => coreReferralOutcome_v1_0_0_default,
|
|
53
53
|
countriesSot: () => countries_v1_0_0_default,
|
|
54
54
|
createdBySystemSot: () => createdBySystem_v1_0_0_default,
|
|
@@ -153,7 +153,7 @@ __export(cvcs_exports, {
|
|
|
153
153
|
riskIdentificationMilestoneSot: () => riskIdentificationMilestone_v1_0_0_default,
|
|
154
154
|
riskSeverityBandSot: () => riskSeverityBand_v1_0_0_default,
|
|
155
155
|
roiMethodSot: () => roiMethod_v1_0_0_default,
|
|
156
|
-
roiScopeSot: () =>
|
|
156
|
+
roiScopeSot: () => roiScope_v1_4_0_default,
|
|
157
157
|
roiStatusSot: () => roiStatus_v1_0_0_default,
|
|
158
158
|
roleContextSot: () => roleContext_v1_0_0_default,
|
|
159
159
|
romanticRelationshipChangeTypeSot: () => romanticRelationshipChangeType_v1_0_0_default,
|
|
@@ -27542,14 +27542,14 @@ var needsAssessmentChangeType_v1_0_0_default = {
|
|
|
27542
27542
|
]
|
|
27543
27543
|
};
|
|
27544
27544
|
|
|
27545
|
-
// src/cvcs/coreInformationScope.v2.
|
|
27546
|
-
var
|
|
27545
|
+
// src/cvcs/coreInformationScope.v2.1.0.json
|
|
27546
|
+
var coreInformationScope_v2_1_0_default = {
|
|
27547
27547
|
domain: "core_information_scope",
|
|
27548
27548
|
name: "Core Information Scope",
|
|
27549
|
-
version: "2.
|
|
27549
|
+
version: "2.1.0",
|
|
27550
27550
|
scopeVersion: 4,
|
|
27551
|
-
_status: "DRAFT: canonical number 236, self-declared by the source YAML (`cvc_id: CVC-236`); CVC_INDEX.md carries no row for it yet, so the drift gate classifies it INDEX_ABSENT. Sourced from the canonical CVC-236 v4 tree (the categories DECIDED 2026-10-08/09, Crysta; INFOSCOPE_V4_DEV_HANDOFF_2026-10-09; the draft yaml is stamped SIGNED 2026-10-09): 115 live rows + 27 retired tombstones + 4 missingness entries. DEPTH 0-3 (canon's `depth`): 0 the top layer (System metadata \xB7 Narrative notes \xB7 Primary client / case subject \xB7 Other named persons); 1 a client category or a person type (People who caused harm \xB7 Eligible family members \xB7 Other people on the case) or a top-layer group's sub-category; 2 a client sub-category or rest row, or a person type's category; 3 an instrument row or a person type's sub-category. The four LEADS categories sit beside the top layer at depth 1. The tree is `parentCode` / `childCodes` (and `parentKey` / `childKeys`), never the code. A stored selection is a flat list of keys (handoff \xA7 2): a row is covered when it or any ancestor is listed; `shareableDefault: false` rows need enabling as well as selecting; `platformFloor` rows never leave on a share; every LIVE row is selectable except the 28 instrument rows and `identifying__other`, which are never offered on their own; `levelFloor` is the viewing side only. KEYS: a canon `.` is `__` in the key (`offenders__identifying`), the canon spelling rides on `canonicalCode` (package keys must match /^[a-z][a-z0-9_]*$/). CODES: every v1.1.0 code is byte-identical (the generator's FROZEN ledger); new rows APPEND \u2014 236-001-006 `identifying__other`, 236-006-010 `health_status`, 236-007-006 `immigration_applications`; 236-013 `instruments` (Summary & outcome -001, Full -002; instrument rows 236-013-00P-NNN, NNN the instrument's slot, the same for both parts); 236-014 `relationships_household`; 236-015 `primary_client`; 236-016 `other_named_persons` with the person types at 236-016-001/002/003 and every per-kind row MIRRORING the kind-tree row it copies (`offenders__safe_locations` = 236-016-001 + 003-002). A code is an identifier, not a tree path: the twelve published categories keep 236-001..012, the six now under `primary_client` included; `levels` name code slots, not tree depth. RETIRED TOMBSTONES (27): `ida_full` (236-002-003); `ida_consid` (236-002-004); `initial_screen` (236-002-005); `tra` (236-002-006); `lap` (236-002-007); `danger_assessment` (236-002-008); `injury_and_strangulation` (236-002-009); `stalking_assessment` (236-002-010); `ae_intake` (236-002-011); `hope_scale` (236-002-012); `assessment_records` (236-002-013); `determinations` (236-002-014); `offender_facilitator` (236-002-015); `screen_notes` (236-005-001); `background` (236-005-003); `disability_subtypes` (236-006-002); `mental_health_status` (236-006-003); `substance_use_status` (236-006-004); `chronic_health_status` (236-006-005); `hiv_status` (236-006-006); `mental_health_screen` (236-006-007); `trauma_and_coping_screen` (236-006-008); `behavioral_health_intake` (236-006-009); `uscis_alien_number` (236-007-002); `federal_protection_applications` (236-007-003); `tvap_enrollment` (236-007-004); `le_report_status` (236-007-005). Each keeps its published code and title (never reused), is `selectable: false` + `retired: true` + `status: retired`, carries no decision attributes, and names its canon SELECTION reading in `successors` (keys) / `successorCodes` (empty = includes nothing); a RESTRICTION naming it resolves through the `subtract` lines (`restrictionSuccessors`, on `offender_facilitator`). Every entry carries the tree by key too (`parentKey` / `childKeys`). MIGRATIONS: the canon v3 -> v4 from-to table is the envelope's `migrations` block, resolved at READ time, never by rewriting a stored list (handoff \xA7 3); a v2-era or unstamped list goes through canon's pinned v2 -> v3 table first (`migrations.readAt` / `unstamped`); lines that read WIDER than v3 carry `widens: true`. CROSS-CHECK: the yaml is re-walked and compared, column by column, with the generated information_scope_v4 rows and migrations CSVs; the Notion codebook is NOT cross-checked in v4 (it carries no v4 rows by design: Notion is a confirmation copy, updated after the repo). Canon enum values are carried verbatim, including three the handoff \xA7 8 list omits (rowType `branch` and `sub-category` \u2014 the exporter's label for a LEADS unit \u2014 and specialDataType `evidence`). VERSION 2.0.0 supersedes 1.1.0 (see `_supersedes`). `safe_locations` is CANON since CVC236-AUDIT R1 (Crysta, 2026-09-08). PENDING canonical Notion authoring + steward ratification.",
|
|
27552
|
-
_source: "htilabstech/prototype/core_information_scope.v4.draft.yaml @
|
|
27551
|
+
_status: "DRAFT: canonical number 236, self-declared by the source YAML (`cvc_id: CVC-236`); CVC_INDEX.md carries no row for it yet, so the drift gate classifies it INDEX_ABSENT. Sourced from the canonical CVC-236 v4 tree (the categories DECIDED 2026-10-08/09, Crysta; INFOSCOPE_V4_DEV_HANDOFF_2026-10-09; the draft yaml is stamped SIGNED 2026-10-09): 115 live rows + 27 retired tombstones + 4 missingness entries. DEPTH 0-3 (canon's `depth`): 0 the top layer (System metadata \xB7 Narrative notes \xB7 Primary client / case subject \xB7 Other named persons); 1 a client category or a person type (People who caused harm \xB7 Eligible family members \xB7 Other people on the case) or a top-layer group's sub-category; 2 a client sub-category or rest row, or a person type's category; 3 an instrument row or a person type's sub-category. The four LEADS categories sit beside the top layer at depth 1. The tree is `parentCode` / `childCodes` (and `parentKey` / `childKeys`), never the code. A stored selection is a flat list of keys (handoff \xA7 2): a row is covered when it or any ancestor is listed; `shareableDefault: false` rows need enabling as well as selecting; `platformFloor` rows never leave on a share; every LIVE row is selectable except the 28 instrument rows and `identifying__other`, which are never offered on their own; `levelFloor` is the viewing side only. KEYS: a canon `.` is `__` in the key (`offenders__identifying`), the canon spelling rides on `canonicalCode` (package keys must match /^[a-z][a-z0-9_]*$/). CODES: every v1.1.0 code is byte-identical (the generator's FROZEN ledger); new rows APPEND \u2014 236-001-006 `identifying__other`, 236-006-010 `health_status`, 236-007-006 `immigration_applications`; 236-013 `instruments` (Summary & outcome -001, Full -002; instrument rows 236-013-00P-NNN, NNN the instrument's slot, the same for both parts); 236-014 `relationships_household`; 236-015 `primary_client`; 236-016 `other_named_persons` with the person types at 236-016-001/002/003 and every per-kind row MIRRORING the kind-tree row it copies (`offenders__safe_locations` = 236-016-001 + 003-002). A code is an identifier, not a tree path: the twelve published categories keep 236-001..012, the six now under `primary_client` included; `levels` name code slots, not tree depth. RETIRED TOMBSTONES (27): `ida_full` (236-002-003); `ida_consid` (236-002-004); `initial_screen` (236-002-005); `tra` (236-002-006); `lap` (236-002-007); `danger_assessment` (236-002-008); `injury_and_strangulation` (236-002-009); `stalking_assessment` (236-002-010); `ae_intake` (236-002-011); `hope_scale` (236-002-012); `assessment_records` (236-002-013); `determinations` (236-002-014); `offender_facilitator` (236-002-015); `screen_notes` (236-005-001); `background` (236-005-003); `disability_subtypes` (236-006-002); `mental_health_status` (236-006-003); `substance_use_status` (236-006-004); `chronic_health_status` (236-006-005); `hiv_status` (236-006-006); `mental_health_screen` (236-006-007); `trauma_and_coping_screen` (236-006-008); `behavioral_health_intake` (236-006-009); `uscis_alien_number` (236-007-002); `federal_protection_applications` (236-007-003); `tvap_enrollment` (236-007-004); `le_report_status` (236-007-005). Each keeps its published code and title (never reused), is `selectable: false` + `retired: true` + `status: retired`, carries no decision attributes, and names its canon SELECTION reading in `successors` (keys) / `successorCodes` (empty = includes nothing); a RESTRICTION naming it resolves through the `subtract` lines (`restrictionSuccessors`, on `offender_facilitator`). Every entry carries the tree by key too (`parentKey` / `childKeys`). MIGRATIONS: the canon v3 -> v4 from-to table is the envelope's `migrations` block, resolved at READ time, never by rewriting a stored list (handoff \xA7 3); a v2-era or unstamped list goes through canon's pinned v2 -> v3 table first (`migrations.readAt` / `unstamped`); lines that read WIDER than v3 carry `widens: true`. RULED 2026-10-09 (Crysta, `migrations.ruling`; canon SIGNED-GRAIN): a signed release or share naming one of the nine merge-fold codes at scopeVersion 3 keeps its v3 grain (`releaseReading: retain`; the entry's `v3Fields`, read-only) and a policy or preset takes the successor with a dated version row (`policyReading: successor`); the widening identity line `immigration_status` reads as itself for every subject (`releaseReading: successor`); the `retired before v4` lines are `informational`. CROSS-CHECK: the yaml is re-walked and compared, column by column, with the generated information_scope_v4 rows and migrations CSVs; the Notion codebook is NOT cross-checked in v4 (it carries no v4 rows by design: Notion is a confirmation copy, updated after the repo). Canon enum values are carried verbatim, including three the handoff \xA7 8 list omits (rowType `branch` and `sub-category` \u2014 the exporter's label for a LEADS unit \u2014 and specialDataType `evidence`). VERSION 2.1.0 amends 2.0.0 (MINOR, additive: the release-grain fields and canon's SIGNED-GRAIN migration notes \u2014 no code, key, tree position or table `to` changed) and, like it, supersedes 1.1.0 (see `_supersedes`). `safe_locations` is CANON since CVC236-AUDIT R1 (Crysta, 2026-09-08). PENDING canonical Notion authoring + steward ratification.",
|
|
27552
|
+
_source: "htilabstech/prototype/core_information_scope.v4.draft.yaml @ e86dd89c (CVC-236 v4, based on v3, proposed 2026-10-08); structural cross-check against htilabstech/prototype/docs/share-roi/information_scope_v4.rows.csv and docs/share-roi/information_scope_v4.migrations.csv @ e86dd89c; 1 duplicate migration line(s) emitted once: immigration_status; v2-era readings via canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc; v3 field membership via canon's v3 field placements, htilabstech/prototype/INFOSCOPE_FIELD_PLACEMENTS_V4_2026-10-08.csv (`home_unit_today`) @ 00179edc, its domain grain checked against htilabstech/prototype/data/cvcs/core_information_scope.yaml `domain_map` @ 00179edc",
|
|
27553
27553
|
_supersedes: {
|
|
27554
27554
|
version: "1.1.0",
|
|
27555
27555
|
keyMap: {
|
|
@@ -27629,7 +27629,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
27629
27629
|
},
|
|
27630
27630
|
retiredCodes: [],
|
|
27631
27631
|
notes: {
|
|
27632
|
-
summary: "Every v1.1.0 key is still an entry in v2.
|
|
27632
|
+
summary: "Every v1.1.0 key is still an entry in v2.1.0, at its v1.1.0 code, so `keyMap` is the identity and `retiredCodes` is empty: no code was withdrawn. BREAKING because 25 more published units are now RETIRED tombstones (each with its canon `successors`, notes below), the twelve published categories became selectable (v4 rule 6: select-all at any level) and six of them (identifying, risk, contact, services, health_accommodation, immigration_legal_status) gained `primary_client` as their parent, 2 categories read narrower, `appRelevance` became `apps` ({pave, thread, leads}), and every live row now carries the full v4 column set (rowType \xB7 depth \xB7 kindBranch \xB7 platformFloor \xB7 status \xB7 replacesV3). Relabelled by canon (code unchanged): `screen_indicators`, `victimization`, `health_accommodation`, `immigration_legal_status`. Added: 73 rows (status `new` in canon, plus the v3 instruments rows this package had not exported).",
|
|
27633
27633
|
ida_full: "v1.1.0 `ida_full` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-002-003 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `full_ida`, `summary_ida` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_ida` needs `screen_indicators` AND one of `ida_full`, `ida_consid`; `full_ida` needs `ida_full` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
|
|
27634
27634
|
ida_consid: "v1.1.0 `ida_consid` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-002-004 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_ida` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_ida` needs `screen_indicators` AND one of `ida_full`, `ida_consid` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
|
|
27635
27635
|
initial_screen: "v1.1.0 `initial_screen` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-002-005 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_initial_screen` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_initial_screen` needs `initial_screen` AND `screen_indicators` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
|
|
@@ -27643,21 +27643,21 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
27643
27643
|
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`).",
|
|
27644
27644
|
determinations: "v1.1.0 `determinations` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-002-014 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_findings` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_findings` needs `victimization` AND `determinations` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
|
|
27645
27645
|
offender_facilitator: "v1.1.0 `offender_facilitator` was a selectable unit. Retired 2026-10-08 (INFOSCOPE v4 rules 1-2 + ruling P2, Crysta; Phase 4 repair 2026-10-09): The offender's own record moves to Other named persons \u203A People who caused harm; the v3 unit carried identity and status/role, so it reads as those two per-kind rows. It stays at 236-002-015 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `offenders__identifying`, `offenders__risk` (selection reading, `migrations` rule `row`); a RESTRICTION naming it keeps restricting `offenders` (`subtract`, see `restrictionSuccessors`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
|
|
27646
|
-
disability_subtypes: "v1.1.0 `disability_subtypes` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-002 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3
|
|
27647
|
-
mental_health_status: "v1.1.0 `mental_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-003 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3
|
|
27648
|
-
substance_use_status: "v1.1.0 `substance_use_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-004 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3
|
|
27649
|
-
chronic_health_status: "v1.1.0 `chronic_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-005 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3
|
|
27650
|
-
hiv_status: "v1.1.0 `hiv_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-006 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3
|
|
27646
|
+
disability_subtypes: "v1.1.0 `disability_subtypes` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-002 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.has_disability`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `disability_subtypes` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `hiv_status`, `mental_health_status`, `substance_use_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
|
|
27647
|
+
mental_health_status: "v1.1.0 `mental_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-003 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.mental_health_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `mental_health_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `hiv_status`, `substance_use_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
|
|
27648
|
+
substance_use_status: "v1.1.0 `substance_use_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-004 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.substance_use_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `substance_use_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `hiv_status`, `mental_health_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
|
|
27649
|
+
chronic_health_status: "v1.1.0 `chronic_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-005 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.chronic_health_severity`, `capture.long_term_conditions`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `chronic_health_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `disability_subtypes`, `hiv_status`, `mental_health_status`, `substance_use_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
|
|
27650
|
+
hiv_status: "v1.1.0 `hiv_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-006 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.hiv_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `hiv_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `mental_health_status`, `substance_use_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
|
|
27651
27651
|
mental_health_screen: "v1.1.0 `mental_health_screen` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-006-007 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_mental_health_screen` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_mental_health_screen` needs `mental_health_screen` AND `screen_indicators` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
|
|
27652
27652
|
trauma_and_coping_screen: "v1.1.0 `trauma_and_coping_screen` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-006-008 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_trauma_and_coping_screen` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_trauma_and_coping_screen` needs `trauma_and_coping_screen` AND `screen_indicators` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
|
|
27653
27653
|
behavioral_health_intake: "v1.1.0 `behavioral_health_intake` was a selectable unit. Retired 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30): Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. It stays at 236-006-009 as a tombstone (`selectable: false`, `retired: true`); `migrations` rule `retired before v4` names `summary_behavioral_health_intake` (canon's flattened v3 reading); only a v2-era list can carry it, and that list is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc FIRST, where `summary_behavioral_health_intake` needs `behavioral_health_intake` AND `screen_indicators` \u2014 so a list that lacks the other code(s) reads narrower. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`).",
|
|
27654
|
-
uscis_alien_number: "v1.1.0 `uscis_alien_number` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. It stays at 236-007-002 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3
|
|
27655
|
-
federal_protection_applications: "v1.1.0 `federal_protection_applications` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-003 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3
|
|
27656
|
-
tvap_enrollment: "v1.1.0 `tvap_enrollment` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-004 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3
|
|
27657
|
-
le_report_status: "v1.1.0 `le_report_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-005 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3
|
|
27654
|
+
uscis_alien_number: "v1.1.0 `uscis_alien_number` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. It stays at 236-007-002 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `immigration_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): it RETAINS NOTHING, no v3 field was homed on it (`v3FieldsNote`), until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `uscis_alien_number` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_status` also carries what `immigration_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
|
|
27655
|
+
federal_protection_applications: "v1.1.0 `federal_protection_applications` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-003 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.legal_action_type`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `federal_protection_applications` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `le_report_status`, `tvap_enrollment` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
|
|
27656
|
+
tvap_enrollment: "v1.1.0 `tvap_enrollment` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-004 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): it RETAINS NOTHING, no v3 field was homed on it (`v3FieldsNote`), until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `tvap_enrollment` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `federal_protection_applications`, `le_report_status` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
|
|
27657
|
+
le_report_status: "v1.1.0 `le_report_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-005 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.le_report_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `le_report_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `federal_protection_applications`, `tvap_enrollment` carried. RULED 2026-10-09 (Crysta, `migrations.ruling`): canon marks this fold `signed_release_grain: keep` \u2014 the reading is a POLICY's or preset's (`policyReading: successor`, with a dated version row); a signed release or share keeps its v3 grain (`releaseReading: retain`, the entry's `v3Fields`).",
|
|
27658
27658
|
risk: "v1.1.0 `risk` keeps 236-002 and reads NARROWER: canon migrations.categories maps a category-grain `risk` to `risk` only. The offender's own record (v1.1.0 `offender_facilitator`) is no longer under Risk-related; it rides Other named persons \u203A People who caused harm, hand-selected only. Canon: 'Risk-related sends the offender's name' was the 2026-10-02 defect this closes. That is the scopeVersion-3 reading. A v1.1.0 (v2-era, unstamped) category-grain `risk` is read through canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc first, where it ALSO selects the seven risk instruments' Summary rows (`summary_initial_screen`, `summary_lap`, `summary_danger_assessment`, `summary_stalking_assessment`, `summary_injury_and_strangulation`, `summary_ae_intake`, `summary_tra`) \u2014 the content its retired per-instrument units carried \u2014 and those pass through this table unchanged.",
|
|
27659
27659
|
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.",
|
|
27660
|
-
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.
|
|
27660
|
+
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)."
|
|
27661
27661
|
}
|
|
27662
27662
|
},
|
|
27663
27663
|
levels: {
|
|
@@ -27675,11 +27675,26 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
27675
27675
|
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.",
|
|
27676
27676
|
rules: {
|
|
27677
27677
|
identity: "code unchanged; a v3 list naming it reads the same in v4",
|
|
27678
|
-
row: "the v3 code is retired; a stored list naming it reads as the listed v4 successor(s)",
|
|
27678
|
+
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)",
|
|
27679
27679
|
category: "a category-grain v3 selection (a purpose payload, a partner rule, a policy) reads as the listed v4 codes only \u2014 never widened",
|
|
27680
27680
|
subtract: "a v3 RESTRICTION (a policy that forbids a code) keeps restricting the listed v4 rows",
|
|
27681
|
-
"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)",
|
|
27682
|
-
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;
|
|
27681
|
+
"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)`",
|
|
27682
|
+
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`)",
|
|
27683
|
+
releaseReading: "on every `widens` line. `retain` on canon's nine merge folds (`signed_release_grain: keep`; ruling 1): a SIGNED RELEASE, and a share (frozen at send, handoff \xA7 3), that names the `from` code at scopeVersion 3 keeps the grain it was signed at \u2014 the code is NOT mapped to `to`; the builder delivers exactly the unit's v3 field membership (`v3Fields` on the `from` entry), read-only: never offered, never widened, never narrowed. It moves to `to` only when the survivor re-signs on v4. `successor` on a widening IDENTITY line canon leaves unmarked: every subject reads `to` (`releaseReadingNote` says why). Absent = not a widening line; `to` is every subject's reading",
|
|
27684
|
+
policyReading: "`successor` on every `widens` line (ruling 1): a POLICY or PRESET (agency-authored, not consent) takes `to`, with a dated version row on the record (handoff \xA7 3)",
|
|
27685
|
+
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"
|
|
27686
|
+
},
|
|
27687
|
+
ruling: {
|
|
27688
|
+
date: "2026-10-09",
|
|
27689
|
+
by: "Crysta",
|
|
27690
|
+
source: "Slack DM thread, https://htilabs-us.slack.com/archives/D0811D2R6QN/p1791581735053759?thread_ts=1791580621.618429&cid=D0811D2R6QN (16:35 CDT)",
|
|
27691
|
+
text: [
|
|
27692
|
+
"Good catch \u2014 the yaml should have declared all nine, not just HIV. Ruling: a SIGNED RELEASE keeps the grain it was signed at. A v3 release naming only mental_health_status keeps delivering exactly what mental_health_status delivered \u2014 the nine retired codes stay recognisable and the builder keeps their field membership read-only (never offered, never widened, never narrowed). It moves to health_status only when the survivor re-signs on v4. Policies and presets (agency-authored, not consent) take the merged successor with a dated version row. We'll amend the yaml's rows rule + the handoff \xA7 3 to say this explicitly.",
|
|
27693
|
+
"Your reading is the intended one. A v2-era list goes through v2\u2192v3 first (which carries the conjunction: lap AND screen_indicators \u2192 summary_lap), then v3\u2192v4. The retired_v3 rows are informational \u2014 they give every old code a stated v4 reading \u2014 and don't carry the condition because a v3-era list can never contain one of those codes (the v3 check rejects it). Keep the flattened value as the v3\u2192v4 reading. We'll mark those rows `informational` in the yaml so it's not ambiguous."
|
|
27694
|
+
],
|
|
27695
|
+
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",
|
|
27696
|
+
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`).",
|
|
27697
|
+
canon: "Absorbed from canon at e86dd89c (SIGNED-GRAIN, 2026-10-09): core_information_scope.v4.draft.yaml `migrations.rows` `signed_release_grain: keep` on the nine merge folds and the header's `signed_release_grain` / INFORMATIONAL retired_v3 rules; the migrations CSV labels `row (merge; signed release keeps its grain)` / `retired before v4 (informational)`; INFOSCOPE_V4_DEV_HANDOFF_2026-10-09 \xA7 3 amended. Canon carries no v3 field lists: `v3Fields` is this package's derivation (`membership`)."
|
|
27683
27698
|
},
|
|
27684
27699
|
table: [
|
|
27685
27700
|
{
|
|
@@ -27940,7 +27955,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
27940
27955
|
"236-007-001-000-000-000-000"
|
|
27941
27956
|
],
|
|
27942
27957
|
note: "code unchanged",
|
|
27943
|
-
widens: true
|
|
27958
|
+
widens: true,
|
|
27959
|
+
releaseReading: "successor",
|
|
27960
|
+
policyReading: "successor",
|
|
27961
|
+
releaseReadingNote: "2026-10-09, followed canon (SIGNED-GRAIN marks exactly the nine merge folds; the identity line is unmarked); flagged for Crysta's awareness. A signed release or share naming `immigration_status` reads as `immigration_status` (identity), like a policy. Two facts: (1) v4 homes `uscis_alien_number` on it (`replacesV3`), so the line is mechanically `widens`; (2) at v3 FIELD grain that content was already there \u2014 `uscis_alien_number`'s input is a v3 control of `capture.immigration_status`, homed on `immigration_status` (canon's v3 field placements, htilabstech/prototype/INFOSCOPE_FIELD_PLACEMENTS_V4_2026-10-08.csv (`home_unit_today`) @ 00179edc) \u2014 so a v3 release naming it delivered it, and no consent widens in practice."
|
|
27944
27962
|
},
|
|
27945
27963
|
{
|
|
27946
27964
|
from: "screen_indicators",
|
|
@@ -28656,8 +28674,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28656
28674
|
toCodes: [
|
|
28657
28675
|
"236-006-010-000-000-000-000"
|
|
28658
28676
|
],
|
|
28659
|
-
note: "
|
|
28660
|
-
widens: true
|
|
28677
|
+
note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
|
|
28678
|
+
widens: true,
|
|
28679
|
+
releaseReading: "retain",
|
|
28680
|
+
policyReading: "successor"
|
|
28661
28681
|
},
|
|
28662
28682
|
{
|
|
28663
28683
|
from: "substance_use_status",
|
|
@@ -28669,8 +28689,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28669
28689
|
toCodes: [
|
|
28670
28690
|
"236-006-010-000-000-000-000"
|
|
28671
28691
|
],
|
|
28672
|
-
note: "
|
|
28673
|
-
widens: true
|
|
28692
|
+
note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
|
|
28693
|
+
widens: true,
|
|
28694
|
+
releaseReading: "retain",
|
|
28695
|
+
policyReading: "successor"
|
|
28674
28696
|
},
|
|
28675
28697
|
{
|
|
28676
28698
|
from: "chronic_health_status",
|
|
@@ -28682,8 +28704,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28682
28704
|
toCodes: [
|
|
28683
28705
|
"236-006-010-000-000-000-000"
|
|
28684
28706
|
],
|
|
28685
|
-
note: "
|
|
28686
|
-
widens: true
|
|
28707
|
+
note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
|
|
28708
|
+
widens: true,
|
|
28709
|
+
releaseReading: "retain",
|
|
28710
|
+
policyReading: "successor"
|
|
28687
28711
|
},
|
|
28688
28712
|
{
|
|
28689
28713
|
from: "disability_subtypes",
|
|
@@ -28695,8 +28719,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28695
28719
|
toCodes: [
|
|
28696
28720
|
"236-006-010-000-000-000-000"
|
|
28697
28721
|
],
|
|
28698
|
-
note: "
|
|
28699
|
-
widens: true
|
|
28722
|
+
note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
|
|
28723
|
+
widens: true,
|
|
28724
|
+
releaseReading: "retain",
|
|
28725
|
+
policyReading: "successor"
|
|
28700
28726
|
},
|
|
28701
28727
|
{
|
|
28702
28728
|
from: "hiv_status",
|
|
@@ -28708,8 +28734,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28708
28734
|
toCodes: [
|
|
28709
28735
|
"236-006-010-000-000-000-000"
|
|
28710
28736
|
],
|
|
28711
|
-
note: "
|
|
28712
|
-
widens: true
|
|
28737
|
+
note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
|
|
28738
|
+
widens: true,
|
|
28739
|
+
releaseReading: "retain",
|
|
28740
|
+
policyReading: "successor"
|
|
28713
28741
|
},
|
|
28714
28742
|
{
|
|
28715
28743
|
from: "uscis_alien_number",
|
|
@@ -28721,8 +28749,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28721
28749
|
toCodes: [
|
|
28722
28750
|
"236-007-001-000-000-000-000"
|
|
28723
28751
|
],
|
|
28724
|
-
note: "
|
|
28725
|
-
widens: true
|
|
28752
|
+
note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
|
|
28753
|
+
widens: true,
|
|
28754
|
+
releaseReading: "retain",
|
|
28755
|
+
policyReading: "successor"
|
|
28726
28756
|
},
|
|
28727
28757
|
{
|
|
28728
28758
|
from: "federal_protection_applications",
|
|
@@ -28734,8 +28764,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28734
28764
|
toCodes: [
|
|
28735
28765
|
"236-007-006-000-000-000-000"
|
|
28736
28766
|
],
|
|
28737
|
-
note: "
|
|
28738
|
-
widens: true
|
|
28767
|
+
note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
|
|
28768
|
+
widens: true,
|
|
28769
|
+
releaseReading: "retain",
|
|
28770
|
+
policyReading: "successor"
|
|
28739
28771
|
},
|
|
28740
28772
|
{
|
|
28741
28773
|
from: "tvap_enrollment",
|
|
@@ -28747,8 +28779,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28747
28779
|
toCodes: [
|
|
28748
28780
|
"236-007-006-000-000-000-000"
|
|
28749
28781
|
],
|
|
28750
|
-
note: "
|
|
28751
|
-
widens: true
|
|
28782
|
+
note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
|
|
28783
|
+
widens: true,
|
|
28784
|
+
releaseReading: "retain",
|
|
28785
|
+
policyReading: "successor"
|
|
28752
28786
|
},
|
|
28753
28787
|
{
|
|
28754
28788
|
from: "le_report_status",
|
|
@@ -28760,8 +28794,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28760
28794
|
toCodes: [
|
|
28761
28795
|
"236-007-006-000-000-000-000"
|
|
28762
28796
|
],
|
|
28763
|
-
note: "
|
|
28764
|
-
widens: true
|
|
28797
|
+
note: "MERGE fold \u2014 policies / presets / partner rules take the successor whole; a SIGNED RELEASE naming this code keeps delivering this code's own field set until re-signed (SIGNED-GRAIN 2026-10-09)",
|
|
28798
|
+
widens: true,
|
|
28799
|
+
releaseReading: "retain",
|
|
28800
|
+
policyReading: "successor"
|
|
28765
28801
|
},
|
|
28766
28802
|
{
|
|
28767
28803
|
from: "risk",
|
|
@@ -28814,8 +28850,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28814
28850
|
"236-013-002-006-000-000-000",
|
|
28815
28851
|
"236-013-001-006-000-000-000"
|
|
28816
28852
|
],
|
|
28817
|
-
note: "via v3: full_ida summary_ida",
|
|
28818
|
-
widens: false
|
|
28853
|
+
note: "via v3: full_ida summary_ida \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28854
|
+
widens: false,
|
|
28855
|
+
informational: true
|
|
28819
28856
|
},
|
|
28820
28857
|
{
|
|
28821
28858
|
from: "ida_consid",
|
|
@@ -28827,8 +28864,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28827
28864
|
toCodes: [
|
|
28828
28865
|
"236-013-001-006-000-000-000"
|
|
28829
28866
|
],
|
|
28830
|
-
note: "via v3: summary_ida",
|
|
28831
|
-
widens: false
|
|
28867
|
+
note: "via v3: summary_ida \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28868
|
+
widens: false,
|
|
28869
|
+
informational: true
|
|
28832
28870
|
},
|
|
28833
28871
|
{
|
|
28834
28872
|
from: "initial_screen",
|
|
@@ -28840,8 +28878,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28840
28878
|
toCodes: [
|
|
28841
28879
|
"236-013-001-001-000-000-000"
|
|
28842
28880
|
],
|
|
28843
|
-
note: "via v3: summary_initial_screen",
|
|
28844
|
-
widens: false
|
|
28881
|
+
note: "via v3: summary_initial_screen \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28882
|
+
widens: false,
|
|
28883
|
+
informational: true
|
|
28845
28884
|
},
|
|
28846
28885
|
{
|
|
28847
28886
|
from: "tra",
|
|
@@ -28853,8 +28892,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28853
28892
|
toCodes: [
|
|
28854
28893
|
"236-013-001-013-000-000-000"
|
|
28855
28894
|
],
|
|
28856
|
-
note: "via v3: summary_tra",
|
|
28857
|
-
widens: false
|
|
28895
|
+
note: "via v3: summary_tra \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28896
|
+
widens: false,
|
|
28897
|
+
informational: true
|
|
28858
28898
|
},
|
|
28859
28899
|
{
|
|
28860
28900
|
from: "lap",
|
|
@@ -28866,8 +28906,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28866
28906
|
toCodes: [
|
|
28867
28907
|
"236-013-001-007-000-000-000"
|
|
28868
28908
|
],
|
|
28869
|
-
note: "via v3: summary_lap",
|
|
28870
|
-
widens: false
|
|
28909
|
+
note: "via v3: summary_lap \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28910
|
+
widens: false,
|
|
28911
|
+
informational: true
|
|
28871
28912
|
},
|
|
28872
28913
|
{
|
|
28873
28914
|
from: "danger_assessment",
|
|
@@ -28879,8 +28920,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28879
28920
|
toCodes: [
|
|
28880
28921
|
"236-013-001-008-000-000-000"
|
|
28881
28922
|
],
|
|
28882
|
-
note: "via v3: summary_danger_assessment",
|
|
28883
|
-
widens: false
|
|
28923
|
+
note: "via v3: summary_danger_assessment \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28924
|
+
widens: false,
|
|
28925
|
+
informational: true
|
|
28884
28926
|
},
|
|
28885
28927
|
{
|
|
28886
28928
|
from: "injury_and_strangulation",
|
|
@@ -28892,8 +28934,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28892
28934
|
toCodes: [
|
|
28893
28935
|
"236-013-001-010-000-000-000"
|
|
28894
28936
|
],
|
|
28895
|
-
note: "via v3: summary_injury_and_strangulation",
|
|
28896
|
-
widens: false
|
|
28937
|
+
note: "via v3: summary_injury_and_strangulation \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28938
|
+
widens: false,
|
|
28939
|
+
informational: true
|
|
28897
28940
|
},
|
|
28898
28941
|
{
|
|
28899
28942
|
from: "stalking_assessment",
|
|
@@ -28905,8 +28948,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28905
28948
|
toCodes: [
|
|
28906
28949
|
"236-013-001-009-000-000-000"
|
|
28907
28950
|
],
|
|
28908
|
-
note: "via v3: summary_stalking_assessment",
|
|
28909
|
-
widens: false
|
|
28951
|
+
note: "via v3: summary_stalking_assessment \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28952
|
+
widens: false,
|
|
28953
|
+
informational: true
|
|
28910
28954
|
},
|
|
28911
28955
|
{
|
|
28912
28956
|
from: "ae_intake",
|
|
@@ -28918,8 +28962,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28918
28962
|
toCodes: [
|
|
28919
28963
|
"236-013-001-005-000-000-000"
|
|
28920
28964
|
],
|
|
28921
|
-
note: "via v3: summary_ae_intake",
|
|
28922
|
-
widens: false
|
|
28965
|
+
note: "via v3: summary_ae_intake \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28966
|
+
widens: false,
|
|
28967
|
+
informational: true
|
|
28923
28968
|
},
|
|
28924
28969
|
{
|
|
28925
28970
|
from: "hope_scale",
|
|
@@ -28931,8 +28976,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28931
28976
|
toCodes: [
|
|
28932
28977
|
"236-013-001-011-000-000-000"
|
|
28933
28978
|
],
|
|
28934
|
-
note: "via v3: summary_hope_scale",
|
|
28935
|
-
widens: false
|
|
28979
|
+
note: "via v3: summary_hope_scale \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28980
|
+
widens: false,
|
|
28981
|
+
informational: true
|
|
28936
28982
|
},
|
|
28937
28983
|
{
|
|
28938
28984
|
from: "assessment_records",
|
|
@@ -28940,8 +28986,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28940
28986
|
rule: "retired before v4",
|
|
28941
28987
|
to: [],
|
|
28942
28988
|
toCodes: [],
|
|
28943
|
-
note: "retired with no successor row (R30); the lifecycle lines are not share content",
|
|
28944
|
-
widens: false
|
|
28989
|
+
note: "retired with no successor row (R30); the lifecycle lines are not share content \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
28990
|
+
widens: false,
|
|
28991
|
+
informational: true
|
|
28945
28992
|
},
|
|
28946
28993
|
{
|
|
28947
28994
|
from: "determinations",
|
|
@@ -28953,8 +29000,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28953
29000
|
toCodes: [
|
|
28954
29001
|
"236-013-001-014-000-000-000"
|
|
28955
29002
|
],
|
|
28956
|
-
note: "via v3: summary_findings",
|
|
28957
|
-
widens: false
|
|
29003
|
+
note: "via v3: summary_findings \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
29004
|
+
widens: false,
|
|
29005
|
+
informational: true
|
|
28958
29006
|
},
|
|
28959
29007
|
{
|
|
28960
29008
|
from: "mental_health_screen",
|
|
@@ -28966,8 +29014,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28966
29014
|
toCodes: [
|
|
28967
29015
|
"236-013-001-002-000-000-000"
|
|
28968
29016
|
],
|
|
28969
|
-
note: "via v3: summary_mental_health_screen",
|
|
28970
|
-
widens: false
|
|
29017
|
+
note: "via v3: summary_mental_health_screen \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
29018
|
+
widens: false,
|
|
29019
|
+
informational: true
|
|
28971
29020
|
},
|
|
28972
29021
|
{
|
|
28973
29022
|
from: "trauma_and_coping_screen",
|
|
@@ -28979,8 +29028,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28979
29028
|
toCodes: [
|
|
28980
29029
|
"236-013-001-004-000-000-000"
|
|
28981
29030
|
],
|
|
28982
|
-
note: "via v3: summary_trauma_and_coping_screen",
|
|
28983
|
-
widens: false
|
|
29031
|
+
note: "via v3: summary_trauma_and_coping_screen \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
29032
|
+
widens: false,
|
|
29033
|
+
informational: true
|
|
28984
29034
|
},
|
|
28985
29035
|
{
|
|
28986
29036
|
from: "behavioral_health_intake",
|
|
@@ -28992,8 +29042,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
28992
29042
|
toCodes: [
|
|
28993
29043
|
"236-013-001-003-000-000-000"
|
|
28994
29044
|
],
|
|
28995
|
-
note: "via v3: summary_behavioral_health_intake",
|
|
28996
|
-
widens: false
|
|
29045
|
+
note: "via v3: summary_behavioral_health_intake \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
29046
|
+
widens: false,
|
|
29047
|
+
informational: true
|
|
28997
29048
|
},
|
|
28998
29049
|
{
|
|
28999
29050
|
from: "screen_notes",
|
|
@@ -29001,8 +29052,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
29001
29052
|
rule: "retired before v4",
|
|
29002
29053
|
to: [],
|
|
29003
29054
|
toCodes: [],
|
|
29004
|
-
note: "retired 2026-10-05 \u2014 an Initial Screen note is an instrument note and rides full_initial_screen; a stored selection naming it includes nothing",
|
|
29005
|
-
widens: false
|
|
29055
|
+
note: "retired 2026-10-05 \u2014 an Initial Screen note is an instrument note and rides full_initial_screen; a stored selection naming it includes nothing \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
29056
|
+
widens: false,
|
|
29057
|
+
informational: true
|
|
29006
29058
|
},
|
|
29007
29059
|
{
|
|
29008
29060
|
from: "background",
|
|
@@ -29010,8 +29062,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
29010
29062
|
rule: "retired before v4",
|
|
29011
29063
|
to: [],
|
|
29012
29064
|
toCodes: [],
|
|
29013
|
-
note: "retired 2026-10-05 \u2014 nothing ever captured it (Crysta to Nate: Eliminate)",
|
|
29014
|
-
widens: false
|
|
29065
|
+
note: "retired 2026-10-05 \u2014 nothing ever captured it (Crysta to Nate: Eliminate) \u2014 a v2-era list is read through the LIVE v2\u2192v3 table first (which carries the condition), then this one",
|
|
29066
|
+
widens: false,
|
|
29067
|
+
informational: true
|
|
29015
29068
|
}
|
|
29016
29069
|
]
|
|
29017
29070
|
},
|
|
@@ -30126,7 +30179,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30126
30179
|
parentKey: "health_accommodation",
|
|
30127
30180
|
childCodes: [],
|
|
30128
30181
|
childKeys: [],
|
|
30129
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3
|
|
30182
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.has_disability`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
|
|
30130
30183
|
retired: true,
|
|
30131
30184
|
status: "retired",
|
|
30132
30185
|
successors: [
|
|
@@ -30135,7 +30188,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30135
30188
|
successorCodes: [
|
|
30136
30189
|
"236-006-010-000-000-000-000"
|
|
30137
30190
|
],
|
|
30138
|
-
migrationRule: "row"
|
|
30191
|
+
migrationRule: "row",
|
|
30192
|
+
v3Fields: [
|
|
30193
|
+
"capture.has_disability"
|
|
30194
|
+
],
|
|
30195
|
+
v3Domains: [
|
|
30196
|
+
"access_accommodations"
|
|
30197
|
+
]
|
|
30139
30198
|
},
|
|
30140
30199
|
{
|
|
30141
30200
|
code: "236-006-003-000-000-000-000",
|
|
@@ -30146,7 +30205,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30146
30205
|
parentKey: "health_accommodation",
|
|
30147
30206
|
childCodes: [],
|
|
30148
30207
|
childKeys: [],
|
|
30149
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3
|
|
30208
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.mental_health_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
|
|
30150
30209
|
retired: true,
|
|
30151
30210
|
status: "retired",
|
|
30152
30211
|
successors: [
|
|
@@ -30155,7 +30214,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30155
30214
|
successorCodes: [
|
|
30156
30215
|
"236-006-010-000-000-000-000"
|
|
30157
30216
|
],
|
|
30158
|
-
migrationRule: "row"
|
|
30217
|
+
migrationRule: "row",
|
|
30218
|
+
v3Fields: [
|
|
30219
|
+
"capture.mental_health_status"
|
|
30220
|
+
],
|
|
30221
|
+
v3Domains: [
|
|
30222
|
+
"access_accommodations"
|
|
30223
|
+
]
|
|
30159
30224
|
},
|
|
30160
30225
|
{
|
|
30161
30226
|
code: "236-006-004-000-000-000-000",
|
|
@@ -30166,7 +30231,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30166
30231
|
parentKey: "health_accommodation",
|
|
30167
30232
|
childCodes: [],
|
|
30168
30233
|
childKeys: [],
|
|
30169
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3
|
|
30234
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.substance_use_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
|
|
30170
30235
|
retired: true,
|
|
30171
30236
|
status: "retired",
|
|
30172
30237
|
successors: [
|
|
@@ -30175,7 +30240,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30175
30240
|
successorCodes: [
|
|
30176
30241
|
"236-006-010-000-000-000-000"
|
|
30177
30242
|
],
|
|
30178
|
-
migrationRule: "row"
|
|
30243
|
+
migrationRule: "row",
|
|
30244
|
+
v3Fields: [
|
|
30245
|
+
"capture.substance_use_status"
|
|
30246
|
+
],
|
|
30247
|
+
v3Domains: [
|
|
30248
|
+
"access_accommodations"
|
|
30249
|
+
]
|
|
30179
30250
|
},
|
|
30180
30251
|
{
|
|
30181
30252
|
code: "236-006-005-000-000-000-000",
|
|
@@ -30186,7 +30257,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30186
30257
|
parentKey: "health_accommodation",
|
|
30187
30258
|
childCodes: [],
|
|
30188
30259
|
childKeys: [],
|
|
30189
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3
|
|
30260
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.chronic_health_severity`, `capture.long_term_conditions`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
|
|
30190
30261
|
retired: true,
|
|
30191
30262
|
status: "retired",
|
|
30192
30263
|
successors: [
|
|
@@ -30195,7 +30266,14 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30195
30266
|
successorCodes: [
|
|
30196
30267
|
"236-006-010-000-000-000-000"
|
|
30197
30268
|
],
|
|
30198
|
-
migrationRule: "row"
|
|
30269
|
+
migrationRule: "row",
|
|
30270
|
+
v3Fields: [
|
|
30271
|
+
"capture.chronic_health_severity",
|
|
30272
|
+
"capture.long_term_conditions"
|
|
30273
|
+
],
|
|
30274
|
+
v3Domains: [
|
|
30275
|
+
"access_accommodations"
|
|
30276
|
+
]
|
|
30199
30277
|
},
|
|
30200
30278
|
{
|
|
30201
30279
|
code: "236-006-006-000-000-000-000",
|
|
@@ -30206,7 +30284,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30206
30284
|
parentKey: "health_accommodation",
|
|
30207
30285
|
childCodes: [],
|
|
30208
30286
|
childKeys: [],
|
|
30209
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3
|
|
30287
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `health_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.hiv_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
|
|
30210
30288
|
retired: true,
|
|
30211
30289
|
status: "retired",
|
|
30212
30290
|
successors: [
|
|
@@ -30215,7 +30293,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30215
30293
|
successorCodes: [
|
|
30216
30294
|
"236-006-010-000-000-000-000"
|
|
30217
30295
|
],
|
|
30218
|
-
migrationRule: "row"
|
|
30296
|
+
migrationRule: "row",
|
|
30297
|
+
v3Fields: [
|
|
30298
|
+
"capture.hiv_status"
|
|
30299
|
+
],
|
|
30300
|
+
v3Domains: [
|
|
30301
|
+
"access_accommodations"
|
|
30302
|
+
]
|
|
30219
30303
|
},
|
|
30220
30304
|
{
|
|
30221
30305
|
code: "236-006-007-000-000-000-000",
|
|
@@ -30383,7 +30467,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30383
30467
|
parentKey: "immigration_legal_status",
|
|
30384
30468
|
childCodes: [],
|
|
30385
30469
|
childKeys: [],
|
|
30386
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3
|
|
30470
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `immigration_status` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): it RETAINS NOTHING, no v3 field was homed on it (`v3FieldsNote`), until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
|
|
30387
30471
|
retired: true,
|
|
30388
30472
|
status: "retired",
|
|
30389
30473
|
successors: [
|
|
@@ -30392,7 +30476,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30392
30476
|
successorCodes: [
|
|
30393
30477
|
"236-007-001-000-000-000-000"
|
|
30394
30478
|
],
|
|
30395
|
-
migrationRule: "row"
|
|
30479
|
+
migrationRule: "row",
|
|
30480
|
+
v3Fields: [],
|
|
30481
|
+
v3Domains: [],
|
|
30482
|
+
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."
|
|
30396
30483
|
},
|
|
30397
30484
|
{
|
|
30398
30485
|
code: "236-007-003-000-000-000-000",
|
|
@@ -30403,7 +30490,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30403
30490
|
parentKey: "immigration_legal_status",
|
|
30404
30491
|
childCodes: [],
|
|
30405
30492
|
childKeys: [],
|
|
30406
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3
|
|
30493
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.legal_action_type`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
|
|
30407
30494
|
retired: true,
|
|
30408
30495
|
status: "retired",
|
|
30409
30496
|
successors: [
|
|
@@ -30412,7 +30499,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30412
30499
|
successorCodes: [
|
|
30413
30500
|
"236-007-006-000-000-000-000"
|
|
30414
30501
|
],
|
|
30415
|
-
migrationRule: "row"
|
|
30502
|
+
migrationRule: "row",
|
|
30503
|
+
v3Fields: [
|
|
30504
|
+
"capture.legal_action_type"
|
|
30505
|
+
],
|
|
30506
|
+
v3Domains: [
|
|
30507
|
+
"immigration_legal_status"
|
|
30508
|
+
]
|
|
30416
30509
|
},
|
|
30417
30510
|
{
|
|
30418
30511
|
code: "236-007-004-000-000-000-000",
|
|
@@ -30423,7 +30516,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30423
30516
|
parentKey: "immigration_legal_status",
|
|
30424
30517
|
childCodes: [],
|
|
30425
30518
|
childKeys: [],
|
|
30426
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3
|
|
30519
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): it RETAINS NOTHING, no v3 field was homed on it (`v3FieldsNote`), until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
|
|
30427
30520
|
retired: true,
|
|
30428
30521
|
status: "retired",
|
|
30429
30522
|
successors: [
|
|
@@ -30432,7 +30525,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30432
30525
|
successorCodes: [
|
|
30433
30526
|
"236-007-006-000-000-000-000"
|
|
30434
30527
|
],
|
|
30435
|
-
migrationRule: "row"
|
|
30528
|
+
migrationRule: "row",
|
|
30529
|
+
v3Fields: [],
|
|
30530
|
+
v3Domains: [],
|
|
30531
|
+
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."
|
|
30436
30532
|
},
|
|
30437
30533
|
{
|
|
30438
30534
|
code: "236-007-005-000-000-000-000",
|
|
@@ -30443,7 +30539,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30443
30539
|
parentKey: "immigration_legal_status",
|
|
30444
30540
|
childCodes: [],
|
|
30445
30541
|
childKeys: [],
|
|
30446
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3
|
|
30542
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 POLICY or preset naming it reads as `immigration_applications` (`migrations` rule `row`, `policyReading: successor`, with a dated version row); a signed RELEASE or share naming it keeps its v3 grain (`releaseReading: retain`, Crysta's ruling of 2026-10-09): exactly its `v3Fields` (`capture.le_report_status`), read-only, never widened or narrowed, until the survivor re-signs on v4. It resolves here so a reader can tell retired from unknown.",
|
|
30447
30543
|
retired: true,
|
|
30448
30544
|
status: "retired",
|
|
30449
30545
|
successors: [
|
|
@@ -30452,7 +30548,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
30452
30548
|
successorCodes: [
|
|
30453
30549
|
"236-007-006-000-000-000-000"
|
|
30454
30550
|
],
|
|
30455
|
-
migrationRule: "row"
|
|
30551
|
+
migrationRule: "row",
|
|
30552
|
+
v3Fields: [
|
|
30553
|
+
"capture.le_report_status"
|
|
30554
|
+
],
|
|
30555
|
+
v3Domains: [
|
|
30556
|
+
"immigration_legal_status"
|
|
30557
|
+
]
|
|
30456
30558
|
},
|
|
30457
30559
|
{
|
|
30458
30560
|
code: "236-007-006-000-000-000-000",
|
|
@@ -32940,13 +33042,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
32940
33042
|
]
|
|
32941
33043
|
};
|
|
32942
33044
|
|
|
32943
|
-
// src/cvcs/roiScope.v1.
|
|
32944
|
-
var
|
|
33045
|
+
// src/cvcs/roiScope.v1.4.0.json
|
|
33046
|
+
var roiScope_v1_4_0_default = {
|
|
32945
33047
|
domain: "roi_scope",
|
|
32946
33048
|
name: "ROI Scope",
|
|
32947
|
-
version: "1.
|
|
32948
|
-
_status: 'DRAFT \u2014 TEMPORARY: net-new value-CVC not yet in Notion; provisional 900+ numbering. 0.8.13: COMPLETED against the canonical 27-item source. 0.8.12 shipped 15 of the canonical 27; the missing 12 are added here. Nothing PAVE shipped was invented \u2014 this was purely a gap. Canonical source: `HTI_SHARE_SCOPE_GROUPS` in HTI-LEADS-PAVE-Thread-prototype.html @ HEAD a596eb9 (7 groups x items = 27): identifying (5) + risk (4) + contact (3) + notes (3) + health_accommodation (6) + immigration_legal_status (5) + system (1). The GROUP axis (identifying / risk / contact / notes / health_accommodation / immigration_legal_status / system) is a separate presentation concern and is deliberately NOT modelled as hierarchy rows here \u2014 this CVC is the flat item vocabulary that an ROI authorizes. PENDING canonical Notion authoring + steward ratification. VERSION 1.2.0 supersedes 1.1.0 (co-bwc): `screen_notes` (983-012) and `background` (983-014) are RETIRED TOMBSTONES, matching CVC-236 `core_information_scope` v1.1.0 (retired 2026-10-05, Narrative notes, signed Spec v2 rule 5). Each keeps its published code (never reused), is `selectable: false` + `retired: true`, and includes nothing: a stored ROI that names one resolves to "retired", not "unknown". Not additive, hence the version (ADR-CVC-0.8.13 Addendum 2026-10-05; see `_supersedes`). This flat vocabulary is LEGACY: new units (e.g. `session_summary`, 236-005-004) are minted in CVC-236 only and are not mirrored here. VERSION 1.3.0 supersedes 1.2.0: `ida_full`, `ida_consid`, `disability_subtypes`, `mental_health_status`, `substance_use_status`, `chronic_health_status`, `hiv_status`, `uscis_alien_number`, `federal_protection_applications`, `tvap_enrollment`, `le_report_status` are RETIRED TOMBSTONES too, matching CVC-236 `core_information_scope`
|
|
32949
|
-
_source: "htilabstech/prototype@a596eb9 HTI-LEADS-PAVE-Thread-prototype.html HTI_SHARE_SCOPE_GROUPS; v1.2.0 retirements: htilabstech/prototype/data/cvcs/core_information_scope.yaml @ 9ef79748 retired_units (L467); v1.3.0 retirements: platform-common-models coreInformationScope.v2.
|
|
33049
|
+
version: "1.4.0",
|
|
33050
|
+
_status: 'DRAFT \u2014 TEMPORARY: net-new value-CVC not yet in Notion; provisional 900+ numbering. 0.8.13: COMPLETED against the canonical 27-item source. 0.8.12 shipped 15 of the canonical 27; the missing 12 are added here. Nothing PAVE shipped was invented \u2014 this was purely a gap. Canonical source: `HTI_SHARE_SCOPE_GROUPS` in HTI-LEADS-PAVE-Thread-prototype.html @ HEAD a596eb9 (7 groups x items = 27): identifying (5) + risk (4) + contact (3) + notes (3) + health_accommodation (6) + immigration_legal_status (5) + system (1). The GROUP axis (identifying / risk / contact / notes / health_accommodation / immigration_legal_status / system) is a separate presentation concern and is deliberately NOT modelled as hierarchy rows here \u2014 this CVC is the flat item vocabulary that an ROI authorizes. PENDING canonical Notion authoring + steward ratification. VERSION 1.2.0 supersedes 1.1.0 (co-bwc): `screen_notes` (983-012) and `background` (983-014) are RETIRED TOMBSTONES, matching CVC-236 `core_information_scope` v1.1.0 (retired 2026-10-05, Narrative notes, signed Spec v2 rule 5). Each keeps its published code (never reused), is `selectable: false` + `retired: true`, and includes nothing: a stored ROI that names one resolves to "retired", not "unknown". Not additive, hence the version (ADR-CVC-0.8.13 Addendum 2026-10-05; see `_supersedes`). This flat vocabulary is LEGACY: new units (e.g. `session_summary`, 236-005-004) are minted in CVC-236 only and are not mirrored here. VERSION 1.3.0 supersedes 1.2.0: `ida_full`, `ida_consid`, `disability_subtypes`, `mental_health_status`, `substance_use_status`, `chronic_health_status`, `hiv_status`, `uscis_alien_number`, `federal_protection_applications`, `tvap_enrollment`, `le_report_status` are RETIRED TOMBSTONES too, matching CVC-236 `core_information_scope` (the v4 tree: instrument-era retirements 2026-10-08, Health & accommodation and Immigration & legal status simplified 2026-10-09). Each keeps its code, is `selectable: false` + `retired: true`, and reads through its CVC-236 twin\'s `migrations` line (see `_supersedes`). VERSION 1.4.0 amends 1.3.0 (MINOR: readings only, no key, code or title changed) to follow CVC-236 v2.1.0: a stored ROI is a SIGNED RELEASE, so the 9 twins on a retained line (`disability_subtypes`, `mental_health_status`, `substance_use_status`, `chronic_health_status`, `hiv_status`, `uscis_alien_number`, `federal_protection_applications`, `tvap_enrollment`, `le_report_status`) keep their twin\'s v3 grain (`v3Fields`, read-only) until the survivor re-signs on v4, and a policy or preset naming the same code takes the successor with a dated version row (Crysta, 2026-10-09; CVC-236 `migrations.ruling`).',
|
|
33051
|
+
_source: "htilabstech/prototype@a596eb9 HTI-LEADS-PAVE-Thread-prototype.html HTI_SHARE_SCOPE_GROUPS; v1.2.0 retirements: htilabstech/prototype/data/cvcs/core_information_scope.yaml @ 9ef79748 retired_units (L467); v1.3.0 retirements and v1.4.0 readings: platform-common-models coreInformationScope.v2.1.0.json (CVC-236 v4, prototype core_information_scope.v4.draft.yaml @ e86dd89c)",
|
|
32950
33052
|
_supersedes: {
|
|
32951
33053
|
version: "1.2.0",
|
|
32952
33054
|
keyMap: {
|
|
@@ -32984,18 +33086,18 @@ var roiScope_v1_3_0_default = {
|
|
|
32984
33086
|
},
|
|
32985
33087
|
retiredCodes: [],
|
|
32986
33088
|
notes: {
|
|
32987
|
-
summary: "Every v1.2.0 key is still an entry
|
|
32988
|
-
ida_full: "v1.2.0 `ida_full` was a selectable item. CVC-236
|
|
32989
|
-
ida_consid: "v1.2.0 `ida_consid` was a selectable item. CVC-236
|
|
32990
|
-
disability_subtypes: "v1.2.0 `disability_subtypes` was a selectable item. CVC-236
|
|
32991
|
-
mental_health_status: "v1.2.0 `mental_health_status` was a selectable item. CVC-236
|
|
32992
|
-
substance_use_status: "v1.2.0 `substance_use_status` was a selectable item. CVC-236
|
|
32993
|
-
chronic_health_status: "v1.2.0 `chronic_health_status` was a selectable item. CVC-236
|
|
32994
|
-
hiv_status: "v1.2.0 `hiv_status` was a selectable item. CVC-236
|
|
32995
|
-
uscis_alien_number: "v1.2.0 `uscis_alien_number` was a selectable item. CVC-236
|
|
32996
|
-
federal_protection_applications: "v1.2.0 `federal_protection_applications` was a selectable item. CVC-236
|
|
32997
|
-
tvap_enrollment: "v1.2.0 `tvap_enrollment` was a selectable item. CVC-236
|
|
32998
|
-
le_report_status: "v1.2.0 `le_report_status` was a selectable item. CVC-236
|
|
33089
|
+
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.",
|
|
33090
|
+
ida_full: "v1.2.0 `ida_full` was a selectable item. CVC-236 retired the same key on 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30). It stays at 983-008 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `full_ida`, `summary_ida` (rule `retired before v4`, `informational`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
|
|
33091
|
+
ida_consid: "v1.2.0 `ida_consid` was a selectable item. CVC-236 retired the same key on 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30). It stays at 983-009 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `summary_ida` (rule `retired before v4`, `informational`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
|
|
33092
|
+
disability_subtypes: "v1.2.0 `disability_subtypes` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-018 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.has_disability`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`).",
|
|
33093
|
+
mental_health_status: "v1.2.0 `mental_health_status` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-019 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.mental_health_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`).",
|
|
33094
|
+
substance_use_status: "v1.2.0 `substance_use_status` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-020 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.substance_use_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`).",
|
|
33095
|
+
chronic_health_status: "v1.2.0 `chronic_health_status` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-021 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.chronic_health_severity`, `capture.long_term_conditions`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`).",
|
|
33096
|
+
hiv_status: "v1.2.0 `hiv_status` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-022 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.hiv_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`).",
|
|
33097
|
+
uscis_alien_number: "v1.2.0 `uscis_alien_number` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-024 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps the twin's v3 grain, which homed NO field (`v3Fields` is empty; the twin's `v3FieldsNote`): it RETAINS NOTHING, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_status` with a dated version row (`policyReading: successor`).",
|
|
33098
|
+
federal_protection_applications: "v1.2.0 `federal_protection_applications` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-025 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.legal_action_type`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`).",
|
|
33099
|
+
tvap_enrollment: "v1.2.0 `tvap_enrollment` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-026 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps the twin's v3 grain, which homed NO field (`v3Fields` is empty; the twin's `v3FieldsNote`): it RETAINS NOTHING, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`).",
|
|
33100
|
+
le_report_status: "v1.2.0 `le_report_status` was a selectable item. CVC-236 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-027 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.le_report_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`)."
|
|
32999
33101
|
}
|
|
33000
33102
|
},
|
|
33001
33103
|
levels: {
|
|
@@ -33113,7 +33215,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33113
33215
|
selectable: false,
|
|
33114
33216
|
parentCode: null,
|
|
33115
33217
|
childCodes: [],
|
|
33116
|
-
definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.
|
|
33218
|
+
definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.1.0 twin. Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `full_ida`, `summary_ida` (rule `retired before v4`, `informational`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition). It resolves here so a reader can tell retired from unknown.",
|
|
33117
33219
|
retired: true
|
|
33118
33220
|
},
|
|
33119
33221
|
{
|
|
@@ -33123,7 +33225,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33123
33225
|
selectable: false,
|
|
33124
33226
|
parentCode: null,
|
|
33125
33227
|
childCodes: [],
|
|
33126
|
-
definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.
|
|
33228
|
+
definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.1.0 twin. Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `summary_ida` (rule `retired before v4`, `informational`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition). It resolves here so a reader can tell retired from unknown.",
|
|
33127
33229
|
retired: true
|
|
33128
33230
|
},
|
|
33129
33231
|
{
|
|
@@ -33207,7 +33309,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33207
33309
|
selectable: false,
|
|
33208
33310
|
parentCode: null,
|
|
33209
33311
|
childCodes: [],
|
|
33210
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
33312
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.has_disability`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
|
|
33211
33313
|
retired: true
|
|
33212
33314
|
},
|
|
33213
33315
|
{
|
|
@@ -33217,7 +33319,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33217
33319
|
selectable: false,
|
|
33218
33320
|
parentCode: null,
|
|
33219
33321
|
childCodes: [],
|
|
33220
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
33322
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.mental_health_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
|
|
33221
33323
|
retired: true
|
|
33222
33324
|
},
|
|
33223
33325
|
{
|
|
@@ -33227,7 +33329,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33227
33329
|
selectable: false,
|
|
33228
33330
|
parentCode: null,
|
|
33229
33331
|
childCodes: [],
|
|
33230
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
33332
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.substance_use_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
|
|
33231
33333
|
retired: true
|
|
33232
33334
|
},
|
|
33233
33335
|
{
|
|
@@ -33237,7 +33339,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33237
33339
|
selectable: false,
|
|
33238
33340
|
parentCode: null,
|
|
33239
33341
|
childCodes: [],
|
|
33240
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
33342
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.chronic_health_severity`, `capture.long_term_conditions`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
|
|
33241
33343
|
retired: true
|
|
33242
33344
|
},
|
|
33243
33345
|
{
|
|
@@ -33247,7 +33349,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33247
33349
|
selectable: false,
|
|
33248
33350
|
parentCode: null,
|
|
33249
33351
|
childCodes: [],
|
|
33250
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
33352
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `health_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.hiv_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `health_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
|
|
33251
33353
|
retired: true
|
|
33252
33354
|
},
|
|
33253
33355
|
{
|
|
@@ -33266,7 +33368,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33266
33368
|
selectable: false,
|
|
33267
33369
|
parentCode: null,
|
|
33268
33370
|
childCodes: [],
|
|
33269
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
33371
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_status` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps the twin's v3 grain, which homed NO field (`v3Fields` is empty; the twin's `v3FieldsNote`): it RETAINS NOTHING, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_status` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
|
|
33270
33372
|
retired: true
|
|
33271
33373
|
},
|
|
33272
33374
|
{
|
|
@@ -33276,7 +33378,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33276
33378
|
selectable: false,
|
|
33277
33379
|
parentCode: null,
|
|
33278
33380
|
childCodes: [],
|
|
33279
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
33381
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.legal_action_type`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
|
|
33280
33382
|
retired: true
|
|
33281
33383
|
},
|
|
33282
33384
|
{
|
|
@@ -33286,7 +33388,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33286
33388
|
selectable: false,
|
|
33287
33389
|
parentCode: null,
|
|
33288
33390
|
childCodes: [],
|
|
33289
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
33391
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps the twin's v3 grain, which homed NO field (`v3Fields` is empty; the twin's `v3FieldsNote`): it RETAINS NOTHING, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
|
|
33290
33392
|
retired: true
|
|
33291
33393
|
},
|
|
33292
33394
|
{
|
|
@@ -33296,7 +33398,7 @@ var roiScope_v1_3_0_default = {
|
|
|
33296
33398
|
selectable: false,
|
|
33297
33399
|
parentCode: null,
|
|
33298
33400
|
childCodes: [],
|
|
33299
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
33401
|
+
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.1.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.1.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.1.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`, `releaseReading: retain`). An ROI is a SIGNED RELEASE, so (Crysta's ruling of 2026-10-09; canon SIGNED-GRAIN @ e86dd89c) it keeps exactly the twin's `v3Fields` (`capture.le_report_status`), read-only, never widened or narrowed, until the survivor re-signs on v4; a policy or preset naming the same code takes `immigration_applications` with a dated version row (`policyReading: successor`). It resolves here so a reader can tell retired from unknown.",
|
|
33300
33402
|
retired: true
|
|
33301
33403
|
}
|
|
33302
33404
|
]
|