@htilabs/platform-common-models 0.20.0 → 0.21.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (53) hide show
  1. package/dist/cvcs/index.cjs +222 -120
  2. package/dist/cvcs/index.cjs.map +1 -1
  3. package/dist/cvcs/index.d.cts +223 -117
  4. package/dist/cvcs/index.d.ts +223 -117
  5. package/dist/cvcs/index.js +222 -120
  6. package/dist/cvcs/index.js.map +1 -1
  7. package/dist/enums/index.cjs.map +1 -1
  8. package/dist/enums/index.d.cts +4 -4
  9. package/dist/enums/index.d.ts +4 -4
  10. package/dist/enums/index.js.map +1 -1
  11. package/dist/{index-I-DiX9eQ.d.ts → index-CDoqrfc1.d.ts} +1 -1
  12. package/dist/{index-CoVr1jIV.d.cts → index-Zu_mOJRn.d.cts} +1 -1
  13. package/dist/index.cjs +320 -137
  14. package/dist/index.cjs.map +1 -1
  15. package/dist/index.d.cts +3 -3
  16. package/dist/index.d.ts +3 -3
  17. package/dist/index.js +319 -137
  18. package/dist/index.js.map +1 -1
  19. package/dist/information-scope/index.cjs +98 -17
  20. package/dist/information-scope/index.cjs.map +1 -1
  21. package/dist/information-scope/index.d.cts +142 -13
  22. package/dist/information-scope/index.d.ts +142 -13
  23. package/dist/information-scope/index.js +97 -17
  24. package/dist/information-scope/index.js.map +1 -1
  25. package/dist/models/index.d.cts +2 -2
  26. package/dist/models/index.d.ts +2 -2
  27. package/dist/schemas/index.d.cts +25 -25
  28. package/dist/schemas/index.d.ts +25 -25
  29. package/dist/services/index.cjs +98 -17
  30. package/dist/services/index.cjs.map +1 -1
  31. package/dist/services/index.d.cts +1 -1
  32. package/dist/services/index.d.ts +1 -1
  33. package/dist/services/index.js +97 -17
  34. package/dist/services/index.js.map +1 -1
  35. package/package.json +1 -1
  36. package/src/__tests__/__snapshots__/cvc-sot.snap +2 -2
  37. package/src/__tests__/core-information-scope-invariant.test.ts +141 -15
  38. package/src/__tests__/cvc-sot-snapshot.test.ts +4 -3
  39. package/src/__tests__/cvc-structural.test.ts +2 -2
  40. package/src/__tests__/location-type-routing-invariant.test.ts +1 -1
  41. package/src/cvcs/{coreInformationScope.v2.0.0.json → coreInformationScope.v2.1.0.json} +190 -88
  42. package/src/cvcs/index.ts +2 -2
  43. package/src/cvcs/{roiScope.v1.3.0.json → roiScope.v1.4.0.json} +26 -26
  44. package/src/generated/cvc-enums.ts +4 -4
  45. package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v3_placements.projection.csv +12 -0
  46. package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v4.migrations.csv +27 -27
  47. package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v4.rows.csv +1 -1
  48. package/src/services/__tests__/fixtures/infoscope-v4/loadInfoscopeV4Fixtures.ts +85 -14
  49. package/src/services/__tests__/informationScopeResolver.test.ts +336 -22
  50. package/src/services/informationScopeResolver.ts +226 -19
  51. package/src/services/informationScopeSot.ts +50 -8
  52. package/dist/{cvcEntry-BCj1OWqL.d.cts → cvcEntry-0BIB9sen.d.cts} +8 -8
  53. package/dist/{cvcEntry-BCj1OWqL.d.ts → cvcEntry-0BIB9sen.d.ts} +8 -8
package/dist/index.js CHANGED
@@ -12819,6 +12819,12 @@ var RESTRICTION_PRECEDENCE = [
12819
12819
  "subtract",
12820
12820
  ...SELECTION_PRECEDENCE
12821
12821
  ];
12822
+ var READING_SUBJECTS = /* @__PURE__ */ new Set([
12823
+ "release",
12824
+ "share",
12825
+ "policy"
12826
+ ]);
12827
+ var INFORMATION_SCOPE_POLICY_VERSION_ROW_NOTE = "Handoff \xA7 3: a policy is migrated with a new version row on the record, dated, so a Member Admin sees a change in history, not a silent rewrite. Write that row before acting on this reading; the stored list itself is never rewritten.";
12822
12828
  var asList = (list) => Array.isArray(list) ? list : [];
12823
12829
  function createInformationScopeResolver(input) {
12824
12830
  const rows = Object.freeze([...input.rows]);
@@ -12913,16 +12919,34 @@ function createInformationScopeResolver(input) {
12913
12919
  );
12914
12920
  }
12915
12921
  }
12922
+ if (m.releaseReading !== void 0 && m.releaseReading !== "retain" && m.releaseReading !== "successor") {
12923
+ throw new Error(`information scope: "${m.from}" has releaseReading "${String(m.releaseReading)}"`);
12924
+ }
12925
+ if (m.policyReading !== void 0 && m.policyReading !== "successor") {
12926
+ throw new Error(`information scope: "${m.from}" has policyReading "${String(m.policyReading)}"`);
12927
+ }
12928
+ if (m.releaseReading === "retain" && (m.to.length !== 1 || !Array.isArray(m.v3Fields) || !Array.isArray(m.v3Domains))) {
12929
+ throw new Error(
12930
+ `information scope: retained line "${m.from}" needs one successor and its v3Fields / v3Domains`
12931
+ );
12932
+ }
12916
12933
  const perCode = migrations.get(m.from) ?? /* @__PURE__ */ new Map();
12917
12934
  const prior = perCode.get(m.rule);
12918
12935
  if (prior && prior.to.join(" ") !== m.to.join(" ")) {
12919
12936
  throw new Error(`information scope: two "${m.rule}" readings for "${m.from}"`);
12920
12937
  }
12938
+ const retain = m.releaseReading === "retain" ? m : prior?.releaseReading === "retain" ? prior : null;
12921
12939
  perCode.set(m.rule, {
12922
12940
  from: m.from,
12923
12941
  rule: m.rule,
12924
12942
  to: Object.freeze([...m.to]),
12925
- widens: m.widens === true || prior?.widens === true
12943
+ widens: m.widens === true || prior?.widens === true,
12944
+ ...retain === null ? {} : {
12945
+ releaseReading: "retain",
12946
+ v3Fields: Object.freeze([...retain.v3Fields ?? []]),
12947
+ v3Domains: Object.freeze([...retain.v3Domains ?? []]),
12948
+ ...retain.v3FieldsNote === void 0 ? {} : { v3FieldsNote: retain.v3FieldsNote }
12949
+ }
12926
12950
  });
12927
12951
  migrations.set(m.from, perCode);
12928
12952
  }
@@ -12989,9 +13013,9 @@ function createInformationScopeResolver(input) {
12989
13013
  for (const d of descendantsOf(childCode)) sel.delete(d);
12990
13014
  return normalize(sel);
12991
13015
  };
12992
- const readOne = (from, scopeVersion, precedence) => {
13016
+ const readOne = (from, scopeVersion, precedence, keepsGrain) => {
12993
13017
  if (scopeVersion === INFORMATION_SCOPE_VERSION && isLive(from)) {
12994
- return { from, rule: "identity", reads: [from], widens: false };
13018
+ return { from, rule: "identity", reads: [from], widens: false, retained: false };
12995
13019
  }
12996
13020
  const lines = migrations.get(from);
12997
13021
  if (lines) {
@@ -13000,21 +13024,39 @@ function createInformationScopeResolver(input) {
13000
13024
  continue;
13001
13025
  }
13002
13026
  const line = lines.get(rule);
13003
- if (line) return { from, rule, reads: [...line.to], widens: line.widens === true };
13027
+ if (!line) continue;
13028
+ if (keepsGrain && line.releaseReading === "retain") {
13029
+ return scopeVersion === 3 ? { from, rule, reads: [], widens: false, retained: true } : { from, rule, reads: [], widens: false, retained: false };
13030
+ }
13031
+ return { from, rule, reads: [...line.to], widens: line.widens === true, retained: false };
13004
13032
  }
13005
13033
  }
13006
- return { from, rule: "unknown", reads: [], widens: false };
13034
+ return { from, rule: "unknown", reads: [], widens: false, retained: false };
13035
+ };
13036
+ const retainedOf = (c) => {
13037
+ const line = migrations.get(c.from)?.get(c.rule);
13038
+ return {
13039
+ code: c.from,
13040
+ v3Fields: [...line.v3Fields ?? []],
13041
+ v3Domains: [...line.v3Domains ?? []],
13042
+ successor: line.to[0],
13043
+ ...line.v3FieldsNote === void 0 ? {} : { note: line.v3FieldsNote }
13044
+ };
13007
13045
  };
13008
- const read = (list, scopeVersion, precedence, isRestriction) => {
13046
+ const read = (list, scopeVersion, precedence, subject) => {
13047
+ const isRestriction = subject === null;
13048
+ const keepsGrain = subject === "release" || subject === "share";
13049
+ const isPolicyLike = subject === "policy" || isRestriction;
13009
13050
  const stored = [...asList(list)];
13010
13051
  const supported = typeof scopeVersion === "number" && INFORMATION_SCOPE_READABLE_VERSIONS.includes(scopeVersion);
13052
+ const versionRowRequired = isPolicyLike && supported && scopeVersion !== INFORMATION_SCOPE_VERSION;
13011
13053
  const codes = [];
13012
13054
  const seen = /* @__PURE__ */ new Set();
13013
13055
  for (const from of stored) {
13014
13056
  if (seen.has(from)) continue;
13015
13057
  seen.add(from);
13016
13058
  codes.push(
13017
- supported ? readOne(from, scopeVersion, precedence) : { from, rule: "unknown", reads: [], widens: false }
13059
+ supported ? readOne(from, scopeVersion, precedence, keepsGrain) : { from, rule: "unknown", reads: [], widens: false, retained: false }
13018
13060
  );
13019
13061
  }
13020
13062
  return {
@@ -13029,9 +13071,22 @@ function createInformationScopeResolver(input) {
13029
13071
  codes,
13030
13072
  retired: codes.filter((c) => RETIRED_RULES.has(c.rule)).map((c) => c.from),
13031
13073
  unknown: codes.filter((c) => c.rule === "unknown").map((c) => c.from),
13032
- widened: codes.filter((c) => c.widens).map((c) => c.from)
13074
+ widened: codes.filter((c) => c.widens).map((c) => c.from),
13075
+ subject,
13076
+ retained: codes.filter((c) => c.retained).map(retainedOf),
13077
+ versionRowRequired,
13078
+ note: versionRowRequired ? INFORMATION_SCOPE_POLICY_VERSION_ROW_NOTE : null
13033
13079
  };
13034
13080
  };
13081
+ const readSelection = (list, scopeVersion, options) => {
13082
+ const subject = options?.subject;
13083
+ if (subject === void 0 || !READING_SUBJECTS.has(subject)) {
13084
+ throw new TypeError(
13085
+ `information scope readSelection: options.subject must be "release", "share" or "policy" (got ${JSON.stringify(subject)}) \u2014 there is no default`
13086
+ );
13087
+ }
13088
+ return read(list, scopeVersion, SELECTION_PRECEDENCE, subject);
13089
+ };
13035
13090
  const rowForSubject = (homeRow, kind) => {
13036
13091
  const home = byCode.get(homeRow);
13037
13092
  if (!home) throw new RangeError(`information scope rowForSubject: unknown home "${homeRow}"`);
@@ -13085,8 +13140,8 @@ function createInformationScopeResolver(input) {
13085
13140
  expandSelectAll,
13086
13141
  selectAll,
13087
13142
  deselectChild,
13088
- readSelection: (list, scopeVersion) => read(list, scopeVersion, SELECTION_PRECEDENCE, false),
13089
- readRestriction: (list, scopeVersion) => read(list, scopeVersion, RESTRICTION_PRECEDENCE, true),
13143
+ readSelection,
13144
+ readRestriction: (list, scopeVersion) => read(list, scopeVersion, RESTRICTION_PRECEDENCE, null),
13090
13145
  rowForSubject,
13091
13146
  expandBranchPickToGrain,
13092
13147
  clampToCeiling
@@ -13161,13 +13216,37 @@ function scopeRowsFromSot(sot) {
13161
13216
  }
13162
13217
  function scopeMigrationsFromSot(sot) {
13163
13218
  const code = keyReader(sot);
13164
- return (sot.migrations?.table ?? []).map((l) => ({
13165
- from: code(l.from),
13166
- to: l.to.map(code),
13167
- rule: l.rule,
13168
- ...l.note === void 0 ? {} : { note: l.note },
13169
- ...l.widens === void 0 ? {} : { widens: l.widens }
13170
- }));
13219
+ const byKey = new Map(sot.entries.map((e) => [e.key, e]));
13220
+ return (sot.migrations?.table ?? []).map((l) => {
13221
+ const m = {
13222
+ from: code(l.from),
13223
+ to: l.to.map(code),
13224
+ rule: l.rule,
13225
+ ...l.note === void 0 ? {} : { note: l.note },
13226
+ ...l.widens === void 0 ? {} : { widens: l.widens },
13227
+ ...l.informational === void 0 ? {} : { informational: l.informational },
13228
+ ...l.policyReading === void 0 ? {} : { policyReading: l.policyReading }
13229
+ };
13230
+ if (l.releaseReading === void 0) return m;
13231
+ if (l.releaseReading !== "retain") {
13232
+ return {
13233
+ ...m,
13234
+ releaseReading: l.releaseReading,
13235
+ ...l.releaseReadingNote === void 0 ? {} : { releaseReadingNote: l.releaseReadingNote }
13236
+ };
13237
+ }
13238
+ const e = byKey.get(l.from);
13239
+ if (e?.v3Fields === void 0 || e.v3Domains === void 0) {
13240
+ fail(l.from, "v3Fields / v3Domains (its line is releaseReading retain)", e?.v3Fields);
13241
+ }
13242
+ return {
13243
+ ...m,
13244
+ releaseReading: l.releaseReading,
13245
+ v3Fields: [...e.v3Fields],
13246
+ v3Domains: [...e.v3Domains],
13247
+ ...e.v3FieldsNote === void 0 ? {} : { v3FieldsNote: e.v3FieldsNote }
13248
+ };
13249
+ });
13171
13250
  }
13172
13251
 
13173
13252
  // src/validation/cvc.ts
@@ -39935,14 +40014,14 @@ var needsAssessmentChangeType_v1_0_0_default = {
39935
40014
  ]
39936
40015
  };
39937
40016
 
39938
- // src/cvcs/coreInformationScope.v2.0.0.json
39939
- var coreInformationScope_v2_0_0_default = {
40017
+ // src/cvcs/coreInformationScope.v2.1.0.json
40018
+ var coreInformationScope_v2_1_0_default = {
39940
40019
  domain: "core_information_scope",
39941
40020
  name: "Core Information Scope",
39942
- version: "2.0.0",
40021
+ version: "2.1.0",
39943
40022
  scopeVersion: 4,
39944
- _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.",
39945
- _source: "htilabstech/prototype/core_information_scope.v4.draft.yaml @ 615ed0b9 (CVC-236 v4, based on v3, proposed 2026-10-08); structural cross-check against htilabstech/prototype/docs/share-roi/information_scope_v4.rows.csv and docs/share-roi/information_scope_v4.migrations.csv @ 615ed0b9; 1 duplicate migration line(s) emitted once: immigration_status; v2-era readings via canon's v2 -> v3 table, htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc",
40023
+ _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.",
40024
+ _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",
39946
40025
  _supersedes: {
39947
40026
  version: "1.1.0",
39948
40027
  keyMap: {
@@ -40022,7 +40101,7 @@ var coreInformationScope_v2_0_0_default = {
40022
40101
  },
40023
40102
  retiredCodes: [],
40024
40103
  notes: {
40025
- summary: "Every v1.1.0 key is still an entry in v2.0.0, at its v1.1.0 code, so `keyMap` is the identity and `retiredCodes` is empty: no code was withdrawn. BREAKING because 25 more published units are now RETIRED tombstones (each with its canon `successors`, notes below), the twelve published categories became selectable (v4 rule 6: select-all at any level) and six of them (identifying, risk, contact, services, health_accommodation, immigration_legal_status) gained `primary_client` as their parent, 2 categories read narrower, `appRelevance` became `apps` ({pave, thread, leads}), and every live row now carries the full v4 column set (rowType \xB7 depth \xB7 kindBranch \xB7 platformFloor \xB7 status \xB7 replacesV3). Relabelled by canon (code unchanged): `screen_indicators`, `victimization`, `health_accommodation`, `immigration_legal_status`. Added: 73 rows (status `new` in canon, plus the v3 instruments rows this package had not exported).",
40104
+ 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).",
40026
40105
  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`).",
40027
40106
  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`).",
40028
40107
  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`).",
@@ -40036,21 +40115,21 @@ var coreInformationScope_v2_0_0_default = {
40036
40115
  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`).",
40037
40116
  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`).",
40038
40117
  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`).",
40039
- disability_subtypes: "v1.1.0 `disability_subtypes` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-002 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `disability_subtypes` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `hiv_status`, `mental_health_status`, `substance_use_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
40040
- mental_health_status: "v1.1.0 `mental_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-003 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `mental_health_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `hiv_status`, `substance_use_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
40041
- substance_use_status: "v1.1.0 `substance_use_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-004 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `substance_use_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `hiv_status`, `mental_health_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
40042
- chronic_health_status: "v1.1.0 `chronic_health_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-005 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `chronic_health_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `disability_subtypes`, `hiv_status`, `mental_health_status`, `substance_use_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
40043
- hiv_status: "v1.1.0 `hiv_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). It stays at 236-006-006 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `hiv_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `health_status` also carries what `chronic_health_status`, `disability_subtypes`, `mental_health_status`, `substance_use_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
40118
+ 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`).",
40119
+ 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`).",
40120
+ 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`).",
40121
+ 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`).",
40122
+ 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`).",
40044
40123
  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`).",
40045
40124
  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`).",
40046
40125
  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`).",
40047
- uscis_alien_number: "v1.1.0 `uscis_alien_number` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. It stays at 236-007-002 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `immigration_status` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `uscis_alien_number` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_status` also carries what `immigration_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
40048
- federal_protection_applications: "v1.1.0 `federal_protection_applications` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-003 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `federal_protection_applications` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `le_report_status`, `tvap_enrollment` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
40049
- tvap_enrollment: "v1.1.0 `tvap_enrollment` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-004 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `tvap_enrollment` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `federal_protection_applications`, `le_report_status` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
40050
- le_report_status: "v1.1.0 `le_report_status` was a selectable unit. Retired 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6): Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). It stays at 236-007-005 as a tombstone (`selectable: false`, `retired: true`); a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). A v1.1.0 list is unstamped and v2-era (`migrations.unstamped`). A stored list naming `le_report_status` ALONE now reads WIDER (`migrations` line `row`, `widens: true`): `immigration_applications` also carries what `federal_protection_applications`, `tvap_enrollment` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta.",
40126
+ 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`).",
40127
+ 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`).",
40128
+ 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`).",
40129
+ 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`).",
40051
40130
  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.",
40052
40131
  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.",
40053
- immigration_status: "v1.1.0 `immigration_status` keeps 236-007-001 and its key, but canon now homes `uscis_alien_number` on it (`replacesV3`). A stored list naming `immigration_status` ALONE now reads WIDER (`migrations` line `identity`, `widens: true`): `immigration_status` also carries what `uscis_alien_number` carried. Canon declares this non-narrowing only for `hiv_status` (yaml migrations.rows); consent widening, OPEN, owner Crysta."
40132
+ 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)."
40054
40133
  }
40055
40134
  },
40056
40135
  levels: {
@@ -40068,11 +40147,26 @@ var coreInformationScope_v2_0_0_default = {
40068
40147
  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.",
40069
40148
  rules: {
40070
40149
  identity: "code unchanged; a v3 list naming it reads the same in v4",
40071
- row: "the v3 code is retired; a stored list naming it reads as the listed v4 successor(s)",
40150
+ 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)",
40072
40151
  category: "a category-grain v3 selection (a purpose payload, a partner rule, a policy) reads as the listed v4 codes only \u2014 never widened",
40073
40152
  subtract: "a v3 RESTRICTION (a policy that forbids a code) keeps restricting the listed v4 rows",
40074
- "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)",
40075
- widens: "true on an identity or row line whose v4 target is also another v3 code's target: a stored list naming the `from` code ALONE reads WIDER than it did in v3. Canon's mapping is kept; the flag lets a reader gate it (consent widening, OPEN, owner Crysta)"
40153
+ "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)`",
40154
+ 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`)",
40155
+ 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",
40156
+ 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)",
40157
+ 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"
40158
+ },
40159
+ ruling: {
40160
+ date: "2026-10-09",
40161
+ by: "Crysta",
40162
+ source: "Slack DM thread, https://htilabs-us.slack.com/archives/D0811D2R6QN/p1791581735053759?thread_ts=1791580621.618429&cid=D0811D2R6QN (16:35 CDT)",
40163
+ text: [
40164
+ "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.",
40165
+ "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."
40166
+ ],
40167
+ 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",
40168
+ 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`).",
40169
+ 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`)."
40076
40170
  },
40077
40171
  table: [
40078
40172
  {
@@ -40333,7 +40427,10 @@ var coreInformationScope_v2_0_0_default = {
40333
40427
  "236-007-001-000-000-000-000"
40334
40428
  ],
40335
40429
  note: "code unchanged",
40336
- widens: true
40430
+ widens: true,
40431
+ releaseReading: "successor",
40432
+ policyReading: "successor",
40433
+ 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."
40337
40434
  },
40338
40435
  {
40339
40436
  from: "screen_indicators",
@@ -41049,8 +41146,10 @@ var coreInformationScope_v2_0_0_default = {
41049
41146
  toCodes: [
41050
41147
  "236-006-010-000-000-000-000"
41051
41148
  ],
41052
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
41053
- widens: true
41149
+ 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)",
41150
+ widens: true,
41151
+ releaseReading: "retain",
41152
+ policyReading: "successor"
41054
41153
  },
41055
41154
  {
41056
41155
  from: "substance_use_status",
@@ -41062,8 +41161,10 @@ var coreInformationScope_v2_0_0_default = {
41062
41161
  toCodes: [
41063
41162
  "236-006-010-000-000-000-000"
41064
41163
  ],
41065
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
41066
- widens: true
41164
+ 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)",
41165
+ widens: true,
41166
+ releaseReading: "retain",
41167
+ policyReading: "successor"
41067
41168
  },
41068
41169
  {
41069
41170
  from: "chronic_health_status",
@@ -41075,8 +41176,10 @@ var coreInformationScope_v2_0_0_default = {
41075
41176
  toCodes: [
41076
41177
  "236-006-010-000-000-000-000"
41077
41178
  ],
41078
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
41079
- widens: true
41179
+ 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)",
41180
+ widens: true,
41181
+ releaseReading: "retain",
41182
+ policyReading: "successor"
41080
41183
  },
41081
41184
  {
41082
41185
  from: "disability_subtypes",
@@ -41088,8 +41191,10 @@ var coreInformationScope_v2_0_0_default = {
41088
41191
  toCodes: [
41089
41192
  "236-006-010-000-000-000-000"
41090
41193
  ],
41091
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
41092
- widens: true
41194
+ 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)",
41195
+ widens: true,
41196
+ releaseReading: "retain",
41197
+ policyReading: "successor"
41093
41198
  },
41094
41199
  {
41095
41200
  from: "hiv_status",
@@ -41101,8 +41206,10 @@ var coreInformationScope_v2_0_0_default = {
41101
41206
  toCodes: [
41102
41207
  "236-006-010-000-000-000-000"
41103
41208
  ],
41104
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
41105
- widens: true
41209
+ 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)",
41210
+ widens: true,
41211
+ releaseReading: "retain",
41212
+ policyReading: "successor"
41106
41213
  },
41107
41214
  {
41108
41215
  from: "uscis_alien_number",
@@ -41114,8 +41221,10 @@ var coreInformationScope_v2_0_0_default = {
41114
41221
  toCodes: [
41115
41222
  "236-007-001-000-000-000-000"
41116
41223
  ],
41117
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
41118
- widens: true
41224
+ 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)",
41225
+ widens: true,
41226
+ releaseReading: "retain",
41227
+ policyReading: "successor"
41119
41228
  },
41120
41229
  {
41121
41230
  from: "federal_protection_applications",
@@ -41127,8 +41236,10 @@ var coreInformationScope_v2_0_0_default = {
41127
41236
  toCodes: [
41128
41237
  "236-007-006-000-000-000-000"
41129
41238
  ],
41130
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
41131
- widens: true
41239
+ 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)",
41240
+ widens: true,
41241
+ releaseReading: "retain",
41242
+ policyReading: "successor"
41132
41243
  },
41133
41244
  {
41134
41245
  from: "tvap_enrollment",
@@ -41140,8 +41251,10 @@ var coreInformationScope_v2_0_0_default = {
41140
41251
  toCodes: [
41141
41252
  "236-007-006-000-000-000-000"
41142
41253
  ],
41143
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
41144
- widens: true
41254
+ 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)",
41255
+ widens: true,
41256
+ releaseReading: "retain",
41257
+ policyReading: "successor"
41145
41258
  },
41146
41259
  {
41147
41260
  from: "le_report_status",
@@ -41153,8 +41266,10 @@ var coreInformationScope_v2_0_0_default = {
41153
41266
  toCodes: [
41154
41267
  "236-007-006-000-000-000-000"
41155
41268
  ],
41156
- note: "retired in v4; a stored selection naming it reads as the successor(s)",
41157
- widens: true
41269
+ 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)",
41270
+ widens: true,
41271
+ releaseReading: "retain",
41272
+ policyReading: "successor"
41158
41273
  },
41159
41274
  {
41160
41275
  from: "risk",
@@ -41207,8 +41322,9 @@ var coreInformationScope_v2_0_0_default = {
41207
41322
  "236-013-002-006-000-000-000",
41208
41323
  "236-013-001-006-000-000-000"
41209
41324
  ],
41210
- note: "via v3: full_ida summary_ida",
41211
- widens: false
41325
+ 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",
41326
+ widens: false,
41327
+ informational: true
41212
41328
  },
41213
41329
  {
41214
41330
  from: "ida_consid",
@@ -41220,8 +41336,9 @@ var coreInformationScope_v2_0_0_default = {
41220
41336
  toCodes: [
41221
41337
  "236-013-001-006-000-000-000"
41222
41338
  ],
41223
- note: "via v3: summary_ida",
41224
- widens: false
41339
+ 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",
41340
+ widens: false,
41341
+ informational: true
41225
41342
  },
41226
41343
  {
41227
41344
  from: "initial_screen",
@@ -41233,8 +41350,9 @@ var coreInformationScope_v2_0_0_default = {
41233
41350
  toCodes: [
41234
41351
  "236-013-001-001-000-000-000"
41235
41352
  ],
41236
- note: "via v3: summary_initial_screen",
41237
- widens: false
41353
+ 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",
41354
+ widens: false,
41355
+ informational: true
41238
41356
  },
41239
41357
  {
41240
41358
  from: "tra",
@@ -41246,8 +41364,9 @@ var coreInformationScope_v2_0_0_default = {
41246
41364
  toCodes: [
41247
41365
  "236-013-001-013-000-000-000"
41248
41366
  ],
41249
- note: "via v3: summary_tra",
41250
- widens: false
41367
+ 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",
41368
+ widens: false,
41369
+ informational: true
41251
41370
  },
41252
41371
  {
41253
41372
  from: "lap",
@@ -41259,8 +41378,9 @@ var coreInformationScope_v2_0_0_default = {
41259
41378
  toCodes: [
41260
41379
  "236-013-001-007-000-000-000"
41261
41380
  ],
41262
- note: "via v3: summary_lap",
41263
- widens: false
41381
+ 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",
41382
+ widens: false,
41383
+ informational: true
41264
41384
  },
41265
41385
  {
41266
41386
  from: "danger_assessment",
@@ -41272,8 +41392,9 @@ var coreInformationScope_v2_0_0_default = {
41272
41392
  toCodes: [
41273
41393
  "236-013-001-008-000-000-000"
41274
41394
  ],
41275
- note: "via v3: summary_danger_assessment",
41276
- widens: false
41395
+ 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",
41396
+ widens: false,
41397
+ informational: true
41277
41398
  },
41278
41399
  {
41279
41400
  from: "injury_and_strangulation",
@@ -41285,8 +41406,9 @@ var coreInformationScope_v2_0_0_default = {
41285
41406
  toCodes: [
41286
41407
  "236-013-001-010-000-000-000"
41287
41408
  ],
41288
- note: "via v3: summary_injury_and_strangulation",
41289
- widens: false
41409
+ 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",
41410
+ widens: false,
41411
+ informational: true
41290
41412
  },
41291
41413
  {
41292
41414
  from: "stalking_assessment",
@@ -41298,8 +41420,9 @@ var coreInformationScope_v2_0_0_default = {
41298
41420
  toCodes: [
41299
41421
  "236-013-001-009-000-000-000"
41300
41422
  ],
41301
- note: "via v3: summary_stalking_assessment",
41302
- widens: false
41423
+ 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",
41424
+ widens: false,
41425
+ informational: true
41303
41426
  },
41304
41427
  {
41305
41428
  from: "ae_intake",
@@ -41311,8 +41434,9 @@ var coreInformationScope_v2_0_0_default = {
41311
41434
  toCodes: [
41312
41435
  "236-013-001-005-000-000-000"
41313
41436
  ],
41314
- note: "via v3: summary_ae_intake",
41315
- widens: false
41437
+ 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",
41438
+ widens: false,
41439
+ informational: true
41316
41440
  },
41317
41441
  {
41318
41442
  from: "hope_scale",
@@ -41324,8 +41448,9 @@ var coreInformationScope_v2_0_0_default = {
41324
41448
  toCodes: [
41325
41449
  "236-013-001-011-000-000-000"
41326
41450
  ],
41327
- note: "via v3: summary_hope_scale",
41328
- widens: false
41451
+ 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",
41452
+ widens: false,
41453
+ informational: true
41329
41454
  },
41330
41455
  {
41331
41456
  from: "assessment_records",
@@ -41333,8 +41458,9 @@ var coreInformationScope_v2_0_0_default = {
41333
41458
  rule: "retired before v4",
41334
41459
  to: [],
41335
41460
  toCodes: [],
41336
- note: "retired with no successor row (R30); the lifecycle lines are not share content",
41337
- widens: false
41461
+ 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",
41462
+ widens: false,
41463
+ informational: true
41338
41464
  },
41339
41465
  {
41340
41466
  from: "determinations",
@@ -41346,8 +41472,9 @@ var coreInformationScope_v2_0_0_default = {
41346
41472
  toCodes: [
41347
41473
  "236-013-001-014-000-000-000"
41348
41474
  ],
41349
- note: "via v3: summary_findings",
41350
- widens: false
41475
+ 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",
41476
+ widens: false,
41477
+ informational: true
41351
41478
  },
41352
41479
  {
41353
41480
  from: "mental_health_screen",
@@ -41359,8 +41486,9 @@ var coreInformationScope_v2_0_0_default = {
41359
41486
  toCodes: [
41360
41487
  "236-013-001-002-000-000-000"
41361
41488
  ],
41362
- note: "via v3: summary_mental_health_screen",
41363
- widens: false
41489
+ 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",
41490
+ widens: false,
41491
+ informational: true
41364
41492
  },
41365
41493
  {
41366
41494
  from: "trauma_and_coping_screen",
@@ -41372,8 +41500,9 @@ var coreInformationScope_v2_0_0_default = {
41372
41500
  toCodes: [
41373
41501
  "236-013-001-004-000-000-000"
41374
41502
  ],
41375
- note: "via v3: summary_trauma_and_coping_screen",
41376
- widens: false
41503
+ 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",
41504
+ widens: false,
41505
+ informational: true
41377
41506
  },
41378
41507
  {
41379
41508
  from: "behavioral_health_intake",
@@ -41385,8 +41514,9 @@ var coreInformationScope_v2_0_0_default = {
41385
41514
  toCodes: [
41386
41515
  "236-013-001-003-000-000-000"
41387
41516
  ],
41388
- note: "via v3: summary_behavioral_health_intake",
41389
- widens: false
41517
+ 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",
41518
+ widens: false,
41519
+ informational: true
41390
41520
  },
41391
41521
  {
41392
41522
  from: "screen_notes",
@@ -41394,8 +41524,9 @@ var coreInformationScope_v2_0_0_default = {
41394
41524
  rule: "retired before v4",
41395
41525
  to: [],
41396
41526
  toCodes: [],
41397
- 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",
41398
- widens: false
41527
+ 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",
41528
+ widens: false,
41529
+ informational: true
41399
41530
  },
41400
41531
  {
41401
41532
  from: "background",
@@ -41403,8 +41534,9 @@ var coreInformationScope_v2_0_0_default = {
41403
41534
  rule: "retired before v4",
41404
41535
  to: [],
41405
41536
  toCodes: [],
41406
- note: "retired 2026-10-05 \u2014 nothing ever captured it (Crysta to Nate: Eliminate)",
41407
- widens: false
41537
+ 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",
41538
+ widens: false,
41539
+ informational: true
41408
41540
  }
41409
41541
  ]
41410
41542
  },
@@ -42519,7 +42651,7 @@ var coreInformationScope_v2_0_0_default = {
42519
42651
  parentKey: "health_accommodation",
42520
42652
  childCodes: [],
42521
42653
  childKeys: [],
42522
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
42654
+ 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.",
42523
42655
  retired: true,
42524
42656
  status: "retired",
42525
42657
  successors: [
@@ -42528,7 +42660,13 @@ var coreInformationScope_v2_0_0_default = {
42528
42660
  successorCodes: [
42529
42661
  "236-006-010-000-000-000-000"
42530
42662
  ],
42531
- migrationRule: "row"
42663
+ migrationRule: "row",
42664
+ v3Fields: [
42665
+ "capture.has_disability"
42666
+ ],
42667
+ v3Domains: [
42668
+ "access_accommodations"
42669
+ ]
42532
42670
  },
42533
42671
  {
42534
42672
  code: "236-006-003-000-000-000-000",
@@ -42539,7 +42677,7 @@ var coreInformationScope_v2_0_0_default = {
42539
42677
  parentKey: "health_accommodation",
42540
42678
  childCodes: [],
42541
42679
  childKeys: [],
42542
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
42680
+ 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.",
42543
42681
  retired: true,
42544
42682
  status: "retired",
42545
42683
  successors: [
@@ -42548,7 +42686,13 @@ var coreInformationScope_v2_0_0_default = {
42548
42686
  successorCodes: [
42549
42687
  "236-006-010-000-000-000-000"
42550
42688
  ],
42551
- migrationRule: "row"
42689
+ migrationRule: "row",
42690
+ v3Fields: [
42691
+ "capture.mental_health_status"
42692
+ ],
42693
+ v3Domains: [
42694
+ "access_accommodations"
42695
+ ]
42552
42696
  },
42553
42697
  {
42554
42698
  code: "236-006-004-000-000-000-000",
@@ -42559,7 +42703,7 @@ var coreInformationScope_v2_0_0_default = {
42559
42703
  parentKey: "health_accommodation",
42560
42704
  childCodes: [],
42561
42705
  childKeys: [],
42562
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
42706
+ 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.",
42563
42707
  retired: true,
42564
42708
  status: "retired",
42565
42709
  successors: [
@@ -42568,7 +42712,13 @@ var coreInformationScope_v2_0_0_default = {
42568
42712
  successorCodes: [
42569
42713
  "236-006-010-000-000-000-000"
42570
42714
  ],
42571
- migrationRule: "row"
42715
+ migrationRule: "row",
42716
+ v3Fields: [
42717
+ "capture.substance_use_status"
42718
+ ],
42719
+ v3Domains: [
42720
+ "access_accommodations"
42721
+ ]
42572
42722
  },
42573
42723
  {
42574
42724
  code: "236-006-005-000-000-000-000",
@@ -42579,7 +42729,7 @@ var coreInformationScope_v2_0_0_default = {
42579
42729
  parentKey: "health_accommodation",
42580
42730
  childCodes: [],
42581
42731
  childKeys: [],
42582
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
42732
+ 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.",
42583
42733
  retired: true,
42584
42734
  status: "retired",
42585
42735
  successors: [
@@ -42588,7 +42738,14 @@ var coreInformationScope_v2_0_0_default = {
42588
42738
  successorCodes: [
42589
42739
  "236-006-010-000-000-000-000"
42590
42740
  ],
42591
- migrationRule: "row"
42741
+ migrationRule: "row",
42742
+ v3Fields: [
42743
+ "capture.chronic_health_severity",
42744
+ "capture.long_term_conditions"
42745
+ ],
42746
+ v3Domains: [
42747
+ "access_accommodations"
42748
+ ]
42592
42749
  },
42593
42750
  {
42594
42751
  code: "236-006-006-000-000-000-000",
@@ -42599,7 +42756,7 @@ var coreInformationScope_v2_0_0_default = {
42599
42756
  parentKey: "health_accommodation",
42600
42757
  childCodes: [],
42601
42758
  childKeys: [],
42602
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `health_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
42759
+ 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.",
42603
42760
  retired: true,
42604
42761
  status: "retired",
42605
42762
  successors: [
@@ -42608,7 +42765,13 @@ var coreInformationScope_v2_0_0_default = {
42608
42765
  successorCodes: [
42609
42766
  "236-006-010-000-000-000-000"
42610
42767
  ],
42611
- migrationRule: "row"
42768
+ migrationRule: "row",
42769
+ v3Fields: [
42770
+ "capture.hiv_status"
42771
+ ],
42772
+ v3Domains: [
42773
+ "access_accommodations"
42774
+ ]
42612
42775
  },
42613
42776
  {
42614
42777
  code: "236-006-007-000-000-000-000",
@@ -42776,7 +42939,7 @@ var coreInformationScope_v2_0_0_default = {
42776
42939
  parentKey: "immigration_legal_status",
42777
42940
  childCodes: [],
42778
42941
  childKeys: [],
42779
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `immigration_status` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
42942
+ 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.",
42780
42943
  retired: true,
42781
42944
  status: "retired",
42782
42945
  successors: [
@@ -42785,7 +42948,10 @@ var coreInformationScope_v2_0_0_default = {
42785
42948
  successorCodes: [
42786
42949
  "236-007-001-000-000-000-000"
42787
42950
  ],
42788
- migrationRule: "row"
42951
+ migrationRule: "row",
42952
+ v3Fields: [],
42953
+ v3Domains: [],
42954
+ 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."
42789
42955
  },
42790
42956
  {
42791
42957
  code: "236-007-003-000-000-000-000",
@@ -42796,7 +42962,7 @@ var coreInformationScope_v2_0_0_default = {
42796
42962
  parentKey: "immigration_legal_status",
42797
42963
  childCodes: [],
42798
42964
  childKeys: [],
42799
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
42965
+ 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.",
42800
42966
  retired: true,
42801
42967
  status: "retired",
42802
42968
  successors: [
@@ -42805,7 +42971,13 @@ var coreInformationScope_v2_0_0_default = {
42805
42971
  successorCodes: [
42806
42972
  "236-007-006-000-000-000-000"
42807
42973
  ],
42808
- migrationRule: "row"
42974
+ migrationRule: "row",
42975
+ v3Fields: [
42976
+ "capture.legal_action_type"
42977
+ ],
42978
+ v3Domains: [
42979
+ "immigration_legal_status"
42980
+ ]
42809
42981
  },
42810
42982
  {
42811
42983
  code: "236-007-004-000-000-000-000",
@@ -42816,7 +42988,7 @@ var coreInformationScope_v2_0_0_default = {
42816
42988
  parentKey: "immigration_legal_status",
42817
42989
  childCodes: [],
42818
42990
  childKeys: [],
42819
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
42991
+ 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.",
42820
42992
  retired: true,
42821
42993
  status: "retired",
42822
42994
  successors: [
@@ -42825,7 +42997,10 @@ var coreInformationScope_v2_0_0_default = {
42825
42997
  successorCodes: [
42826
42998
  "236-007-006-000-000-000-000"
42827
42999
  ],
42828
- migrationRule: "row"
43000
+ migrationRule: "row",
43001
+ v3Fields: [],
43002
+ v3Domains: [],
43003
+ 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."
42829
43004
  },
42830
43005
  {
42831
43006
  code: "236-007-005-000-000-000-000",
@@ -42836,7 +43011,7 @@ var coreInformationScope_v2_0_0_default = {
42836
43011
  parentKey: "immigration_legal_status",
42837
43012
  childCodes: [],
42838
43013
  childKeys: [],
42839
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in share policy, internal viewing settings or a release; a scopeVersion-3 list naming it reads as `immigration_applications` (selection reading, `migrations` rule `row`). It resolves here so a reader can tell retired from unknown.",
43014
+ 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.",
42840
43015
  retired: true,
42841
43016
  status: "retired",
42842
43017
  successors: [
@@ -42845,7 +43020,13 @@ var coreInformationScope_v2_0_0_default = {
42845
43020
  successorCodes: [
42846
43021
  "236-007-006-000-000-000-000"
42847
43022
  ],
42848
- migrationRule: "row"
43023
+ migrationRule: "row",
43024
+ v3Fields: [
43025
+ "capture.le_report_status"
43026
+ ],
43027
+ v3Domains: [
43028
+ "immigration_legal_status"
43029
+ ]
42849
43030
  },
42850
43031
  {
42851
43032
  code: "236-007-006-000-000-000-000",
@@ -45333,13 +45514,13 @@ var coreInformationScope_v2_0_0_default = {
45333
45514
  ]
45334
45515
  };
45335
45516
 
45336
- // src/cvcs/roiScope.v1.3.0.json
45337
- var roiScope_v1_3_0_default = {
45517
+ // src/cvcs/roiScope.v1.4.0.json
45518
+ var roiScope_v1_4_0_default = {
45338
45519
  domain: "roi_scope",
45339
45520
  name: "ROI Scope",
45340
- version: "1.3.0",
45341
- _status: 'DRAFT \u2014 TEMPORARY: net-new value-CVC not yet in Notion; provisional 900+ numbering. 0.8.13: COMPLETED against the canonical 27-item source. 0.8.12 shipped 15 of the canonical 27; the missing 12 are added here. Nothing PAVE shipped was invented \u2014 this was purely a gap. Canonical source: `HTI_SHARE_SCOPE_GROUPS` in HTI-LEADS-PAVE-Thread-prototype.html @ HEAD a596eb9 (7 groups x items = 27): identifying (5) + risk (4) + contact (3) + notes (3) + health_accommodation (6) + immigration_legal_status (5) + system (1). The GROUP axis (identifying / risk / contact / notes / health_accommodation / immigration_legal_status / system) is a separate presentation concern and is deliberately NOT modelled as hierarchy rows here \u2014 this CVC is the flat item vocabulary that an ROI authorizes. PENDING canonical Notion authoring + steward ratification. VERSION 1.2.0 supersedes 1.1.0 (co-bwc): `screen_notes` (983-012) and `background` (983-014) are RETIRED TOMBSTONES, matching CVC-236 `core_information_scope` v1.1.0 (retired 2026-10-05, Narrative notes, signed Spec v2 rule 5). Each keeps its published code (never reused), is `selectable: false` + `retired: true`, and includes nothing: a stored ROI that names one resolves to "retired", not "unknown". Not additive, hence the version (ADR-CVC-0.8.13 Addendum 2026-10-05; see `_supersedes`). This flat vocabulary is LEGACY: new units (e.g. `session_summary`, 236-005-004) are minted in CVC-236 only and are not mirrored here. VERSION 1.3.0 supersedes 1.2.0: `ida_full`, `ida_consid`, `disability_subtypes`, `mental_health_status`, `substance_use_status`, `chronic_health_status`, `hiv_status`, `uscis_alien_number`, `federal_protection_applications`, `tvap_enrollment`, `le_report_status` are RETIRED TOMBSTONES too, matching CVC-236 `core_information_scope` v2.0.0 (the v4 tree: instrument-era retirements 2026-10-08, Health & accommodation and Immigration & legal status simplified 2026-10-09). Each keeps its code, is `selectable: false` + `retired: true`, and reads as its CVC-236 twin\'s `successors` (see `_supersedes`).',
45342
- _source: "htilabstech/prototype@a596eb9 HTI-LEADS-PAVE-Thread-prototype.html HTI_SHARE_SCOPE_GROUPS; v1.2.0 retirements: htilabstech/prototype/data/cvcs/core_information_scope.yaml @ 9ef79748 retired_units (L467); v1.3.0 retirements: platform-common-models coreInformationScope.v2.0.0.json (CVC-236 v4, prototype core_information_scope.v4.draft.yaml @ 615ed0b9)",
45521
+ version: "1.4.0",
45522
+ _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`).',
45523
+ _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)",
45343
45524
  _supersedes: {
45344
45525
  version: "1.2.0",
45345
45526
  keyMap: {
@@ -45377,18 +45558,18 @@ var roiScope_v1_3_0_default = {
45377
45558
  },
45378
45559
  retiredCodes: [],
45379
45560
  notes: {
45380
- summary: "Every v1.2.0 key is still an entry in v1.3.0, at its v1.2.0 code, so `keyMap` is the identity and `retiredCodes` is empty: no code was withdrawn. Non-additive because 11 more published items are now RETIRED tombstones (notes below), matching CVC-236 `core_information_scope` v2.0.0 (the v4 tree), which retired the same keys; nothing was added. Unlike the v1.2.0 pair, these tombstones are NOT empty: a stored roi_scope list is unstamped and v2-era, so it reads through canon's v2 -> v3 table first and then through the CVC-236 v2.0.0 `migrations` table (its twin's `successors`), and keeps a v4 reading. Keeps the co-bwc rule: one answer to \"is this offerable\" across both vocabularies.",
45381
- ida_full: "v1.2.0 `ida_full` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30). It stays at 983-008 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `full_ida`, `summary_ida` (rule `retired before v4`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
45382
- ida_consid: "v1.2.0 `ida_consid` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30). It stays at 983-009 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `summary_ida` (rule `retired before v4`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition).",
45383
- disability_subtypes: "v1.2.0 `disability_subtypes` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-018 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`).",
45384
- mental_health_status: "v1.2.0 `mental_health_status` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-019 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`).",
45385
- substance_use_status: "v1.2.0 `substance_use_status` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-020 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`).",
45386
- chronic_health_status: "v1.2.0 `chronic_health_status` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-021 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`).",
45387
- hiv_status: "v1.2.0 `hiv_status` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-022 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`).",
45388
- uscis_alien_number: "v1.2.0 `uscis_alien_number` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-024 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_status` (rule `row`).",
45389
- federal_protection_applications: "v1.2.0 `federal_protection_applications` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-025 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`).",
45390
- tvap_enrollment: "v1.2.0 `tvap_enrollment` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-026 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`).",
45391
- le_report_status: "v1.2.0 `le_report_status` was a selectable item. CVC-236 v2.0.0 retired the same key on 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6). It stays at 983-027 as a tombstone (`selectable: false`, `retired: true`); a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`)."
45561
+ 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.",
45562
+ 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).",
45563
+ 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).",
45564
+ 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`).",
45565
+ 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`).",
45566
+ 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`).",
45567
+ 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`).",
45568
+ 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`).",
45569
+ 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`).",
45570
+ 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`).",
45571
+ 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`).",
45572
+ 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`)."
45392
45573
  }
45393
45574
  },
45394
45575
  levels: {
@@ -45506,7 +45687,7 @@ var roiScope_v1_3_0_default = {
45506
45687
  selectable: false,
45507
45688
  parentCode: null,
45508
45689
  childCodes: [],
45509
- definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.0.0 twin. Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `full_ida`, `summary_ida` (rule `retired before v4`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition). It resolves here so a reader can tell retired from unknown.",
45690
+ 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.",
45510
45691
  retired: true
45511
45692
  },
45512
45693
  {
@@ -45516,7 +45697,7 @@ var roiScope_v1_3_0_default = {
45516
45697
  selectable: false,
45517
45698
  parentCode: null,
45518
45699
  childCodes: [],
45519
- definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.0.0 twin. Superseded by the Screens & assessments category (`instruments`): one Summary & outcome row and one Full row per instrument. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `summary_ida` (rule `retired before v4`) \u2014 canon's flattened reading, which the conjunctive v2 -> v3 rows can narrow (see the twin's definition). It resolves here so a reader can tell retired from unknown.",
45700
+ 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.",
45520
45701
  retired: true
45521
45702
  },
45522
45703
  {
@@ -45600,7 +45781,7 @@ var roiScope_v1_3_0_default = {
45600
45781
  selectable: false,
45601
45782
  parentCode: null,
45602
45783
  childCodes: [],
45603
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
45784
+ 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.",
45604
45785
  retired: true
45605
45786
  },
45606
45787
  {
@@ -45610,7 +45791,7 @@ var roiScope_v1_3_0_default = {
45610
45791
  selectable: false,
45611
45792
  parentCode: null,
45612
45793
  childCodes: [],
45613
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
45794
+ 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.",
45614
45795
  retired: true
45615
45796
  },
45616
45797
  {
@@ -45620,7 +45801,7 @@ var roiScope_v1_3_0_default = {
45620
45801
  selectable: false,
45621
45802
  parentCode: null,
45622
45803
  childCodes: [],
45623
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
45804
+ 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.",
45624
45805
  retired: true
45625
45806
  },
45626
45807
  {
@@ -45630,7 +45811,7 @@ var roiScope_v1_3_0_default = {
45630
45811
  selectable: false,
45631
45812
  parentCode: null,
45632
45813
  childCodes: [],
45633
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
45814
+ 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.",
45634
45815
  retired: true
45635
45816
  },
45636
45817
  {
@@ -45640,7 +45821,7 @@ var roiScope_v1_3_0_default = {
45640
45821
  selectable: false,
45641
45822
  parentCode: null,
45642
45823
  childCodes: [],
45643
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Health & accommodation collapses to two sub-categories; every health fact rides Health status (`health_status`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `health_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
45824
+ 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.",
45644
45825
  retired: true
45645
45826
  },
45646
45827
  {
@@ -45659,7 +45840,7 @@ var roiScope_v1_3_0_default = {
45659
45840
  selectable: false,
45660
45841
  parentCode: null,
45661
45842
  childCodes: [],
45662
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Immigration & legal status collapses to two sub-categories; the A-number rides Immigration status. No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_status` (rule `row`). It resolves here so a reader can tell retired from unknown.",
45843
+ 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.",
45663
45844
  retired: true
45664
45845
  },
45665
45846
  {
@@ -45669,7 +45850,7 @@ var roiScope_v1_3_0_default = {
45669
45850
  selectable: false,
45670
45851
  parentCode: null,
45671
45852
  childCodes: [],
45672
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`). It resolves here so a reader can tell retired from unknown.",
45853
+ 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.",
45673
45854
  retired: true
45674
45855
  },
45675
45856
  {
@@ -45679,7 +45860,7 @@ var roiScope_v1_3_0_default = {
45679
45860
  selectable: false,
45680
45861
  parentCode: null,
45681
45862
  childCodes: [],
45682
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`). It resolves here so a reader can tell retired from unknown.",
45863
+ 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.",
45683
45864
  retired: true
45684
45865
  },
45685
45866
  {
@@ -45689,7 +45870,7 @@ var roiScope_v1_3_0_default = {
45689
45870
  selectable: false,
45690
45871
  parentCode: null,
45691
45872
  childCodes: [],
45692
- definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.0.0 twin. Immigration & legal status collapses to two sub-categories; what is in flight rides Applications, enrollments & law enforcement engagement (`immigration_applications`). No longer offered in an ROI; a stored roi_scope list is unstamped and v2-era (CVC-236 v2.0.0 `migrations.unstamped`): it reads through canon's v2 -> v3 table (htilabstech/prototype/data/cvcs/core_information_scope.yaml L539-565 @ 00179edc) first, then through CVC-236 v2.0.0's `migrations`, where its twin's line names `immigration_applications` (rule `row`). It resolves here so a reader can tell retired from unknown.",
45873
+ 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.",
45693
45874
  retired: true
45694
45875
  }
45695
45876
  ]
@@ -61921,6 +62102,7 @@ export {
61921
62102
  INCIDENT_PARTICIPATION_ROLE_LABELS,
61922
62103
  INCIDENT_PARTICIPATION_ROLE_SUPERSEDED_BY,
61923
62104
  INCIDENT_PARTICIPATION_ROLE_VALUES,
62105
+ INFORMATION_SCOPE_POLICY_VERSION_ROW_NOTE,
61924
62106
  INFORMATION_SCOPE_READABLE_VERSIONS,
61925
62107
  INFORMATION_SCOPE_SYSTEM_INFO,
61926
62108
  INFORMATION_SCOPE_VERSION,
@@ -62145,7 +62327,7 @@ export {
62145
62327
  coreDhState_v1_0_0_default as coreDhStateSot,
62146
62328
  coreFunctions_v1_1_0_default as coreFunctionsSot,
62147
62329
  coreIndicators_v1_1_0_default as coreIndicatorsSot,
62148
- coreInformationScope_v2_0_0_default as coreInformationScopeSot,
62330
+ coreInformationScope_v2_1_0_default as coreInformationScopeSot,
62149
62331
  coreReferralOutcome_v1_0_0_default as coreReferralOutcomeSot,
62150
62332
  countries_v1_0_0_default as countriesSot,
62151
62333
  createInformationScopeResolver,
@@ -62329,7 +62511,7 @@ export {
62329
62511
  riskIdentificationMilestone_v1_0_0_default as riskIdentificationMilestoneSot,
62330
62512
  riskSeverityBand_v1_0_0_default as riskSeverityBandSot,
62331
62513
  roiMethod_v1_0_0_default as roiMethodSot,
62332
- roiScope_v1_3_0_default as roiScopeSot,
62514
+ roiScope_v1_4_0_default as roiScopeSot,
62333
62515
  roiStatus_v1_0_0_default as roiStatusSot,
62334
62516
  roleContext_v1_0_0_default as roleContextSot,
62335
62517
  romanticRelationshipChangeType_v1_0_0_default as romanticRelationshipChangeTypeSot,