@htilabs/platform-common-models 0.20.0 → 0.21.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cvcs/index.cjs +222 -120
- package/dist/cvcs/index.cjs.map +1 -1
- package/dist/cvcs/index.d.cts +223 -117
- package/dist/cvcs/index.d.ts +223 -117
- package/dist/cvcs/index.js +222 -120
- package/dist/cvcs/index.js.map +1 -1
- package/dist/enums/index.cjs.map +1 -1
- package/dist/enums/index.d.cts +4 -4
- package/dist/enums/index.d.ts +4 -4
- package/dist/enums/index.js.map +1 -1
- package/dist/{index-I-DiX9eQ.d.ts → index-CDoqrfc1.d.ts} +1 -1
- package/dist/{index-CoVr1jIV.d.cts → index-Zu_mOJRn.d.cts} +1 -1
- package/dist/index.cjs +320 -137
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +3 -3
- package/dist/index.d.ts +3 -3
- package/dist/index.js +319 -137
- package/dist/index.js.map +1 -1
- package/dist/information-scope/index.cjs +98 -17
- package/dist/information-scope/index.cjs.map +1 -1
- package/dist/information-scope/index.d.cts +142 -13
- package/dist/information-scope/index.d.ts +142 -13
- package/dist/information-scope/index.js +97 -17
- package/dist/information-scope/index.js.map +1 -1
- package/dist/models/index.d.cts +2 -2
- package/dist/models/index.d.ts +2 -2
- package/dist/schemas/index.d.cts +25 -25
- package/dist/schemas/index.d.ts +25 -25
- package/dist/services/index.cjs +98 -17
- package/dist/services/index.cjs.map +1 -1
- package/dist/services/index.d.cts +1 -1
- package/dist/services/index.d.ts +1 -1
- package/dist/services/index.js +97 -17
- package/dist/services/index.js.map +1 -1
- package/package.json +1 -1
- package/src/__tests__/__snapshots__/cvc-sot.snap +2 -2
- package/src/__tests__/core-information-scope-invariant.test.ts +141 -15
- package/src/__tests__/cvc-sot-snapshot.test.ts +4 -3
- package/src/__tests__/cvc-structural.test.ts +2 -2
- package/src/__tests__/location-type-routing-invariant.test.ts +1 -1
- package/src/cvcs/{coreInformationScope.v2.0.0.json → coreInformationScope.v2.1.0.json} +190 -88
- package/src/cvcs/index.ts +2 -2
- package/src/cvcs/{roiScope.v1.3.0.json → roiScope.v1.4.0.json} +26 -26
- package/src/generated/cvc-enums.ts +4 -4
- package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v3_placements.projection.csv +12 -0
- package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v4.migrations.csv +27 -27
- package/src/services/__tests__/fixtures/infoscope-v4/information_scope_v4.rows.csv +1 -1
- package/src/services/__tests__/fixtures/infoscope-v4/loadInfoscopeV4Fixtures.ts +85 -14
- package/src/services/__tests__/informationScopeResolver.test.ts +336 -22
- package/src/services/informationScopeResolver.ts +226 -19
- package/src/services/informationScopeSot.ts +50 -8
- package/dist/{cvcEntry-BCj1OWqL.d.cts → cvcEntry-0BIB9sen.d.cts} +8 -8
- package/dist/{cvcEntry-BCj1OWqL.d.ts → cvcEntry-0BIB9sen.d.ts} +8 -8
package/dist/index.cjs
CHANGED
|
@@ -330,6 +330,7 @@ __export(src_exports, {
|
|
|
330
330
|
INCIDENT_PARTICIPATION_ROLE_LABELS: () => INCIDENT_PARTICIPATION_ROLE_LABELS,
|
|
331
331
|
INCIDENT_PARTICIPATION_ROLE_SUPERSEDED_BY: () => INCIDENT_PARTICIPATION_ROLE_SUPERSEDED_BY,
|
|
332
332
|
INCIDENT_PARTICIPATION_ROLE_VALUES: () => INCIDENT_PARTICIPATION_ROLE_VALUES,
|
|
333
|
+
INFORMATION_SCOPE_POLICY_VERSION_ROW_NOTE: () => INFORMATION_SCOPE_POLICY_VERSION_ROW_NOTE,
|
|
333
334
|
INFORMATION_SCOPE_READABLE_VERSIONS: () => INFORMATION_SCOPE_READABLE_VERSIONS,
|
|
334
335
|
INFORMATION_SCOPE_SYSTEM_INFO: () => INFORMATION_SCOPE_SYSTEM_INFO,
|
|
335
336
|
INFORMATION_SCOPE_VERSION: () => INFORMATION_SCOPE_VERSION,
|
|
@@ -554,7 +555,7 @@ __export(src_exports, {
|
|
|
554
555
|
coreDhStateSot: () => coreDhState_v1_0_0_default,
|
|
555
556
|
coreFunctionsSot: () => coreFunctions_v1_1_0_default,
|
|
556
557
|
coreIndicatorsSot: () => coreIndicators_v1_1_0_default,
|
|
557
|
-
coreInformationScopeSot: () =>
|
|
558
|
+
coreInformationScopeSot: () => coreInformationScope_v2_1_0_default,
|
|
558
559
|
coreReferralOutcomeSot: () => coreReferralOutcome_v1_0_0_default,
|
|
559
560
|
countriesSot: () => countries_v1_0_0_default,
|
|
560
561
|
createInformationScopeResolver: () => createInformationScopeResolver,
|
|
@@ -738,7 +739,7 @@ __export(src_exports, {
|
|
|
738
739
|
riskIdentificationMilestoneSot: () => riskIdentificationMilestone_v1_0_0_default,
|
|
739
740
|
riskSeverityBandSot: () => riskSeverityBand_v1_0_0_default,
|
|
740
741
|
roiMethodSot: () => roiMethod_v1_0_0_default,
|
|
741
|
-
roiScopeSot: () =>
|
|
742
|
+
roiScopeSot: () => roiScope_v1_4_0_default,
|
|
742
743
|
roiStatusSot: () => roiStatus_v1_0_0_default,
|
|
743
744
|
roleContextSot: () => roleContext_v1_0_0_default,
|
|
744
745
|
romanticRelationshipChangeTypeSot: () => romanticRelationshipChangeType_v1_0_0_default,
|
|
@@ -13622,6 +13623,12 @@ var RESTRICTION_PRECEDENCE = [
|
|
|
13622
13623
|
"subtract",
|
|
13623
13624
|
...SELECTION_PRECEDENCE
|
|
13624
13625
|
];
|
|
13626
|
+
var READING_SUBJECTS = /* @__PURE__ */ new Set([
|
|
13627
|
+
"release",
|
|
13628
|
+
"share",
|
|
13629
|
+
"policy"
|
|
13630
|
+
]);
|
|
13631
|
+
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.";
|
|
13625
13632
|
var asList = (list) => Array.isArray(list) ? list : [];
|
|
13626
13633
|
function createInformationScopeResolver(input) {
|
|
13627
13634
|
const rows = Object.freeze([...input.rows]);
|
|
@@ -13716,16 +13723,34 @@ function createInformationScopeResolver(input) {
|
|
|
13716
13723
|
);
|
|
13717
13724
|
}
|
|
13718
13725
|
}
|
|
13726
|
+
if (m.releaseReading !== void 0 && m.releaseReading !== "retain" && m.releaseReading !== "successor") {
|
|
13727
|
+
throw new Error(`information scope: "${m.from}" has releaseReading "${String(m.releaseReading)}"`);
|
|
13728
|
+
}
|
|
13729
|
+
if (m.policyReading !== void 0 && m.policyReading !== "successor") {
|
|
13730
|
+
throw new Error(`information scope: "${m.from}" has policyReading "${String(m.policyReading)}"`);
|
|
13731
|
+
}
|
|
13732
|
+
if (m.releaseReading === "retain" && (m.to.length !== 1 || !Array.isArray(m.v3Fields) || !Array.isArray(m.v3Domains))) {
|
|
13733
|
+
throw new Error(
|
|
13734
|
+
`information scope: retained line "${m.from}" needs one successor and its v3Fields / v3Domains`
|
|
13735
|
+
);
|
|
13736
|
+
}
|
|
13719
13737
|
const perCode = migrations.get(m.from) ?? /* @__PURE__ */ new Map();
|
|
13720
13738
|
const prior = perCode.get(m.rule);
|
|
13721
13739
|
if (prior && prior.to.join(" ") !== m.to.join(" ")) {
|
|
13722
13740
|
throw new Error(`information scope: two "${m.rule}" readings for "${m.from}"`);
|
|
13723
13741
|
}
|
|
13742
|
+
const retain = m.releaseReading === "retain" ? m : prior?.releaseReading === "retain" ? prior : null;
|
|
13724
13743
|
perCode.set(m.rule, {
|
|
13725
13744
|
from: m.from,
|
|
13726
13745
|
rule: m.rule,
|
|
13727
13746
|
to: Object.freeze([...m.to]),
|
|
13728
|
-
widens: m.widens === true || prior?.widens === true
|
|
13747
|
+
widens: m.widens === true || prior?.widens === true,
|
|
13748
|
+
...retain === null ? {} : {
|
|
13749
|
+
releaseReading: "retain",
|
|
13750
|
+
v3Fields: Object.freeze([...retain.v3Fields ?? []]),
|
|
13751
|
+
v3Domains: Object.freeze([...retain.v3Domains ?? []]),
|
|
13752
|
+
...retain.v3FieldsNote === void 0 ? {} : { v3FieldsNote: retain.v3FieldsNote }
|
|
13753
|
+
}
|
|
13729
13754
|
});
|
|
13730
13755
|
migrations.set(m.from, perCode);
|
|
13731
13756
|
}
|
|
@@ -13792,9 +13817,9 @@ function createInformationScopeResolver(input) {
|
|
|
13792
13817
|
for (const d of descendantsOf(childCode)) sel.delete(d);
|
|
13793
13818
|
return normalize(sel);
|
|
13794
13819
|
};
|
|
13795
|
-
const readOne = (from, scopeVersion, precedence) => {
|
|
13820
|
+
const readOne = (from, scopeVersion, precedence, keepsGrain) => {
|
|
13796
13821
|
if (scopeVersion === INFORMATION_SCOPE_VERSION && isLive(from)) {
|
|
13797
|
-
return { from, rule: "identity", reads: [from], widens: false };
|
|
13822
|
+
return { from, rule: "identity", reads: [from], widens: false, retained: false };
|
|
13798
13823
|
}
|
|
13799
13824
|
const lines = migrations.get(from);
|
|
13800
13825
|
if (lines) {
|
|
@@ -13803,21 +13828,39 @@ function createInformationScopeResolver(input) {
|
|
|
13803
13828
|
continue;
|
|
13804
13829
|
}
|
|
13805
13830
|
const line = lines.get(rule);
|
|
13806
|
-
if (line)
|
|
13831
|
+
if (!line) continue;
|
|
13832
|
+
if (keepsGrain && line.releaseReading === "retain") {
|
|
13833
|
+
return scopeVersion === 3 ? { from, rule, reads: [], widens: false, retained: true } : { from, rule, reads: [], widens: false, retained: false };
|
|
13834
|
+
}
|
|
13835
|
+
return { from, rule, reads: [...line.to], widens: line.widens === true, retained: false };
|
|
13807
13836
|
}
|
|
13808
13837
|
}
|
|
13809
|
-
return { from, rule: "unknown", reads: [], widens: false };
|
|
13838
|
+
return { from, rule: "unknown", reads: [], widens: false, retained: false };
|
|
13839
|
+
};
|
|
13840
|
+
const retainedOf = (c) => {
|
|
13841
|
+
const line = migrations.get(c.from)?.get(c.rule);
|
|
13842
|
+
return {
|
|
13843
|
+
code: c.from,
|
|
13844
|
+
v3Fields: [...line.v3Fields ?? []],
|
|
13845
|
+
v3Domains: [...line.v3Domains ?? []],
|
|
13846
|
+
successor: line.to[0],
|
|
13847
|
+
...line.v3FieldsNote === void 0 ? {} : { note: line.v3FieldsNote }
|
|
13848
|
+
};
|
|
13810
13849
|
};
|
|
13811
|
-
const read = (list, scopeVersion, precedence,
|
|
13850
|
+
const read = (list, scopeVersion, precedence, subject) => {
|
|
13851
|
+
const isRestriction = subject === null;
|
|
13852
|
+
const keepsGrain = subject === "release" || subject === "share";
|
|
13853
|
+
const isPolicyLike = subject === "policy" || isRestriction;
|
|
13812
13854
|
const stored = [...asList(list)];
|
|
13813
13855
|
const supported = typeof scopeVersion === "number" && INFORMATION_SCOPE_READABLE_VERSIONS.includes(scopeVersion);
|
|
13856
|
+
const versionRowRequired = isPolicyLike && supported && scopeVersion !== INFORMATION_SCOPE_VERSION;
|
|
13814
13857
|
const codes = [];
|
|
13815
13858
|
const seen = /* @__PURE__ */ new Set();
|
|
13816
13859
|
for (const from of stored) {
|
|
13817
13860
|
if (seen.has(from)) continue;
|
|
13818
13861
|
seen.add(from);
|
|
13819
13862
|
codes.push(
|
|
13820
|
-
supported ? readOne(from, scopeVersion, precedence) : { from, rule: "unknown", reads: [], widens: false }
|
|
13863
|
+
supported ? readOne(from, scopeVersion, precedence, keepsGrain) : { from, rule: "unknown", reads: [], widens: false, retained: false }
|
|
13821
13864
|
);
|
|
13822
13865
|
}
|
|
13823
13866
|
return {
|
|
@@ -13832,9 +13875,22 @@ function createInformationScopeResolver(input) {
|
|
|
13832
13875
|
codes,
|
|
13833
13876
|
retired: codes.filter((c) => RETIRED_RULES.has(c.rule)).map((c) => c.from),
|
|
13834
13877
|
unknown: codes.filter((c) => c.rule === "unknown").map((c) => c.from),
|
|
13835
|
-
widened: codes.filter((c) => c.widens).map((c) => c.from)
|
|
13878
|
+
widened: codes.filter((c) => c.widens).map((c) => c.from),
|
|
13879
|
+
subject,
|
|
13880
|
+
retained: codes.filter((c) => c.retained).map(retainedOf),
|
|
13881
|
+
versionRowRequired,
|
|
13882
|
+
note: versionRowRequired ? INFORMATION_SCOPE_POLICY_VERSION_ROW_NOTE : null
|
|
13836
13883
|
};
|
|
13837
13884
|
};
|
|
13885
|
+
const readSelection = (list, scopeVersion, options) => {
|
|
13886
|
+
const subject = options?.subject;
|
|
13887
|
+
if (subject === void 0 || !READING_SUBJECTS.has(subject)) {
|
|
13888
|
+
throw new TypeError(
|
|
13889
|
+
`information scope readSelection: options.subject must be "release", "share" or "policy" (got ${JSON.stringify(subject)}) \u2014 there is no default`
|
|
13890
|
+
);
|
|
13891
|
+
}
|
|
13892
|
+
return read(list, scopeVersion, SELECTION_PRECEDENCE, subject);
|
|
13893
|
+
};
|
|
13838
13894
|
const rowForSubject = (homeRow, kind) => {
|
|
13839
13895
|
const home = byCode.get(homeRow);
|
|
13840
13896
|
if (!home) throw new RangeError(`information scope rowForSubject: unknown home "${homeRow}"`);
|
|
@@ -13888,8 +13944,8 @@ function createInformationScopeResolver(input) {
|
|
|
13888
13944
|
expandSelectAll,
|
|
13889
13945
|
selectAll,
|
|
13890
13946
|
deselectChild,
|
|
13891
|
-
readSelection
|
|
13892
|
-
readRestriction: (list, scopeVersion) => read(list, scopeVersion, RESTRICTION_PRECEDENCE,
|
|
13947
|
+
readSelection,
|
|
13948
|
+
readRestriction: (list, scopeVersion) => read(list, scopeVersion, RESTRICTION_PRECEDENCE, null),
|
|
13893
13949
|
rowForSubject,
|
|
13894
13950
|
expandBranchPickToGrain,
|
|
13895
13951
|
clampToCeiling
|
|
@@ -13964,13 +14020,37 @@ function scopeRowsFromSot(sot) {
|
|
|
13964
14020
|
}
|
|
13965
14021
|
function scopeMigrationsFromSot(sot) {
|
|
13966
14022
|
const code = keyReader(sot);
|
|
13967
|
-
|
|
13968
|
-
|
|
13969
|
-
|
|
13970
|
-
|
|
13971
|
-
|
|
13972
|
-
|
|
13973
|
-
|
|
14023
|
+
const byKey = new Map(sot.entries.map((e) => [e.key, e]));
|
|
14024
|
+
return (sot.migrations?.table ?? []).map((l) => {
|
|
14025
|
+
const m = {
|
|
14026
|
+
from: code(l.from),
|
|
14027
|
+
to: l.to.map(code),
|
|
14028
|
+
rule: l.rule,
|
|
14029
|
+
...l.note === void 0 ? {} : { note: l.note },
|
|
14030
|
+
...l.widens === void 0 ? {} : { widens: l.widens },
|
|
14031
|
+
...l.informational === void 0 ? {} : { informational: l.informational },
|
|
14032
|
+
...l.policyReading === void 0 ? {} : { policyReading: l.policyReading }
|
|
14033
|
+
};
|
|
14034
|
+
if (l.releaseReading === void 0) return m;
|
|
14035
|
+
if (l.releaseReading !== "retain") {
|
|
14036
|
+
return {
|
|
14037
|
+
...m,
|
|
14038
|
+
releaseReading: l.releaseReading,
|
|
14039
|
+
...l.releaseReadingNote === void 0 ? {} : { releaseReadingNote: l.releaseReadingNote }
|
|
14040
|
+
};
|
|
14041
|
+
}
|
|
14042
|
+
const e = byKey.get(l.from);
|
|
14043
|
+
if (e?.v3Fields === void 0 || e.v3Domains === void 0) {
|
|
14044
|
+
fail(l.from, "v3Fields / v3Domains (its line is releaseReading retain)", e?.v3Fields);
|
|
14045
|
+
}
|
|
14046
|
+
return {
|
|
14047
|
+
...m,
|
|
14048
|
+
releaseReading: l.releaseReading,
|
|
14049
|
+
v3Fields: [...e.v3Fields],
|
|
14050
|
+
v3Domains: [...e.v3Domains],
|
|
14051
|
+
...e.v3FieldsNote === void 0 ? {} : { v3FieldsNote: e.v3FieldsNote }
|
|
14052
|
+
};
|
|
14053
|
+
});
|
|
13974
14054
|
}
|
|
13975
14055
|
|
|
13976
14056
|
// src/validation/cvc.ts
|
|
@@ -40738,14 +40818,14 @@ var needsAssessmentChangeType_v1_0_0_default = {
|
|
|
40738
40818
|
]
|
|
40739
40819
|
};
|
|
40740
40820
|
|
|
40741
|
-
// src/cvcs/coreInformationScope.v2.
|
|
40742
|
-
var
|
|
40821
|
+
// src/cvcs/coreInformationScope.v2.1.0.json
|
|
40822
|
+
var coreInformationScope_v2_1_0_default = {
|
|
40743
40823
|
domain: "core_information_scope",
|
|
40744
40824
|
name: "Core Information Scope",
|
|
40745
|
-
version: "2.
|
|
40825
|
+
version: "2.1.0",
|
|
40746
40826
|
scopeVersion: 4,
|
|
40747
|
-
_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.",
|
|
40748
|
-
_source: "htilabstech/prototype/core_information_scope.v4.draft.yaml @
|
|
40827
|
+
_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.",
|
|
40828
|
+
_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",
|
|
40749
40829
|
_supersedes: {
|
|
40750
40830
|
version: "1.1.0",
|
|
40751
40831
|
keyMap: {
|
|
@@ -40825,7 +40905,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
40825
40905
|
},
|
|
40826
40906
|
retiredCodes: [],
|
|
40827
40907
|
notes: {
|
|
40828
|
-
summary: "Every v1.1.0 key is still an entry in v2.
|
|
40908
|
+
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).",
|
|
40829
40909
|
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`).",
|
|
40830
40910
|
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`).",
|
|
40831
40911
|
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`).",
|
|
@@ -40839,21 +40919,21 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
40839
40919
|
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`).",
|
|
40840
40920
|
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`).",
|
|
40841
40921
|
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`).",
|
|
40842
|
-
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
|
|
40843
|
-
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
|
|
40844
|
-
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
|
|
40845
|
-
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
|
|
40846
|
-
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
|
|
40922
|
+
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`).",
|
|
40923
|
+
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`).",
|
|
40924
|
+
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`).",
|
|
40925
|
+
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`).",
|
|
40926
|
+
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`).",
|
|
40847
40927
|
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`).",
|
|
40848
40928
|
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`).",
|
|
40849
40929
|
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`).",
|
|
40850
|
-
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
|
|
40851
|
-
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
|
|
40852
|
-
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
|
|
40853
|
-
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
|
|
40930
|
+
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`).",
|
|
40931
|
+
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`).",
|
|
40932
|
+
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`).",
|
|
40933
|
+
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`).",
|
|
40854
40934
|
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.",
|
|
40855
40935
|
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.",
|
|
40856
|
-
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.
|
|
40936
|
+
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)."
|
|
40857
40937
|
}
|
|
40858
40938
|
},
|
|
40859
40939
|
levels: {
|
|
@@ -40871,11 +40951,26 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
40871
40951
|
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.",
|
|
40872
40952
|
rules: {
|
|
40873
40953
|
identity: "code unchanged; a v3 list naming it reads the same in v4",
|
|
40874
|
-
row: "the v3 code is retired; a stored list naming it reads as the listed v4 successor(s)",
|
|
40954
|
+
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)",
|
|
40875
40955
|
category: "a category-grain v3 selection (a purpose payload, a partner rule, a policy) reads as the listed v4 codes only \u2014 never widened",
|
|
40876
40956
|
subtract: "a v3 RESTRICTION (a policy that forbids a code) keeps restricting the listed v4 rows",
|
|
40877
|
-
"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)",
|
|
40878
|
-
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;
|
|
40957
|
+
"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)`",
|
|
40958
|
+
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`)",
|
|
40959
|
+
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",
|
|
40960
|
+
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)",
|
|
40961
|
+
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"
|
|
40962
|
+
},
|
|
40963
|
+
ruling: {
|
|
40964
|
+
date: "2026-10-09",
|
|
40965
|
+
by: "Crysta",
|
|
40966
|
+
source: "Slack DM thread, https://htilabs-us.slack.com/archives/D0811D2R6QN/p1791581735053759?thread_ts=1791580621.618429&cid=D0811D2R6QN (16:35 CDT)",
|
|
40967
|
+
text: [
|
|
40968
|
+
"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.",
|
|
40969
|
+
"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."
|
|
40970
|
+
],
|
|
40971
|
+
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",
|
|
40972
|
+
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`).",
|
|
40973
|
+
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`)."
|
|
40879
40974
|
},
|
|
40880
40975
|
table: [
|
|
40881
40976
|
{
|
|
@@ -41136,7 +41231,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
41136
41231
|
"236-007-001-000-000-000-000"
|
|
41137
41232
|
],
|
|
41138
41233
|
note: "code unchanged",
|
|
41139
|
-
widens: true
|
|
41234
|
+
widens: true,
|
|
41235
|
+
releaseReading: "successor",
|
|
41236
|
+
policyReading: "successor",
|
|
41237
|
+
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."
|
|
41140
41238
|
},
|
|
41141
41239
|
{
|
|
41142
41240
|
from: "screen_indicators",
|
|
@@ -41852,8 +41950,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
41852
41950
|
toCodes: [
|
|
41853
41951
|
"236-006-010-000-000-000-000"
|
|
41854
41952
|
],
|
|
41855
|
-
note: "
|
|
41856
|
-
widens: true
|
|
41953
|
+
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)",
|
|
41954
|
+
widens: true,
|
|
41955
|
+
releaseReading: "retain",
|
|
41956
|
+
policyReading: "successor"
|
|
41857
41957
|
},
|
|
41858
41958
|
{
|
|
41859
41959
|
from: "substance_use_status",
|
|
@@ -41865,8 +41965,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
41865
41965
|
toCodes: [
|
|
41866
41966
|
"236-006-010-000-000-000-000"
|
|
41867
41967
|
],
|
|
41868
|
-
note: "
|
|
41869
|
-
widens: true
|
|
41968
|
+
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)",
|
|
41969
|
+
widens: true,
|
|
41970
|
+
releaseReading: "retain",
|
|
41971
|
+
policyReading: "successor"
|
|
41870
41972
|
},
|
|
41871
41973
|
{
|
|
41872
41974
|
from: "chronic_health_status",
|
|
@@ -41878,8 +41980,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
41878
41980
|
toCodes: [
|
|
41879
41981
|
"236-006-010-000-000-000-000"
|
|
41880
41982
|
],
|
|
41881
|
-
note: "
|
|
41882
|
-
widens: true
|
|
41983
|
+
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)",
|
|
41984
|
+
widens: true,
|
|
41985
|
+
releaseReading: "retain",
|
|
41986
|
+
policyReading: "successor"
|
|
41883
41987
|
},
|
|
41884
41988
|
{
|
|
41885
41989
|
from: "disability_subtypes",
|
|
@@ -41891,8 +41995,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
41891
41995
|
toCodes: [
|
|
41892
41996
|
"236-006-010-000-000-000-000"
|
|
41893
41997
|
],
|
|
41894
|
-
note: "
|
|
41895
|
-
widens: true
|
|
41998
|
+
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)",
|
|
41999
|
+
widens: true,
|
|
42000
|
+
releaseReading: "retain",
|
|
42001
|
+
policyReading: "successor"
|
|
41896
42002
|
},
|
|
41897
42003
|
{
|
|
41898
42004
|
from: "hiv_status",
|
|
@@ -41904,8 +42010,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
41904
42010
|
toCodes: [
|
|
41905
42011
|
"236-006-010-000-000-000-000"
|
|
41906
42012
|
],
|
|
41907
|
-
note: "
|
|
41908
|
-
widens: true
|
|
42013
|
+
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)",
|
|
42014
|
+
widens: true,
|
|
42015
|
+
releaseReading: "retain",
|
|
42016
|
+
policyReading: "successor"
|
|
41909
42017
|
},
|
|
41910
42018
|
{
|
|
41911
42019
|
from: "uscis_alien_number",
|
|
@@ -41917,8 +42025,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
41917
42025
|
toCodes: [
|
|
41918
42026
|
"236-007-001-000-000-000-000"
|
|
41919
42027
|
],
|
|
41920
|
-
note: "
|
|
41921
|
-
widens: true
|
|
42028
|
+
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)",
|
|
42029
|
+
widens: true,
|
|
42030
|
+
releaseReading: "retain",
|
|
42031
|
+
policyReading: "successor"
|
|
41922
42032
|
},
|
|
41923
42033
|
{
|
|
41924
42034
|
from: "federal_protection_applications",
|
|
@@ -41930,8 +42040,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
41930
42040
|
toCodes: [
|
|
41931
42041
|
"236-007-006-000-000-000-000"
|
|
41932
42042
|
],
|
|
41933
|
-
note: "
|
|
41934
|
-
widens: true
|
|
42043
|
+
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)",
|
|
42044
|
+
widens: true,
|
|
42045
|
+
releaseReading: "retain",
|
|
42046
|
+
policyReading: "successor"
|
|
41935
42047
|
},
|
|
41936
42048
|
{
|
|
41937
42049
|
from: "tvap_enrollment",
|
|
@@ -41943,8 +42055,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
41943
42055
|
toCodes: [
|
|
41944
42056
|
"236-007-006-000-000-000-000"
|
|
41945
42057
|
],
|
|
41946
|
-
note: "
|
|
41947
|
-
widens: true
|
|
42058
|
+
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)",
|
|
42059
|
+
widens: true,
|
|
42060
|
+
releaseReading: "retain",
|
|
42061
|
+
policyReading: "successor"
|
|
41948
42062
|
},
|
|
41949
42063
|
{
|
|
41950
42064
|
from: "le_report_status",
|
|
@@ -41956,8 +42070,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
41956
42070
|
toCodes: [
|
|
41957
42071
|
"236-007-006-000-000-000-000"
|
|
41958
42072
|
],
|
|
41959
|
-
note: "
|
|
41960
|
-
widens: true
|
|
42073
|
+
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)",
|
|
42074
|
+
widens: true,
|
|
42075
|
+
releaseReading: "retain",
|
|
42076
|
+
policyReading: "successor"
|
|
41961
42077
|
},
|
|
41962
42078
|
{
|
|
41963
42079
|
from: "risk",
|
|
@@ -42010,8 +42126,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42010
42126
|
"236-013-002-006-000-000-000",
|
|
42011
42127
|
"236-013-001-006-000-000-000"
|
|
42012
42128
|
],
|
|
42013
|
-
note: "via v3: full_ida summary_ida",
|
|
42014
|
-
widens: false
|
|
42129
|
+
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",
|
|
42130
|
+
widens: false,
|
|
42131
|
+
informational: true
|
|
42015
42132
|
},
|
|
42016
42133
|
{
|
|
42017
42134
|
from: "ida_consid",
|
|
@@ -42023,8 +42140,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42023
42140
|
toCodes: [
|
|
42024
42141
|
"236-013-001-006-000-000-000"
|
|
42025
42142
|
],
|
|
42026
|
-
note: "via v3: summary_ida",
|
|
42027
|
-
widens: false
|
|
42143
|
+
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",
|
|
42144
|
+
widens: false,
|
|
42145
|
+
informational: true
|
|
42028
42146
|
},
|
|
42029
42147
|
{
|
|
42030
42148
|
from: "initial_screen",
|
|
@@ -42036,8 +42154,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42036
42154
|
toCodes: [
|
|
42037
42155
|
"236-013-001-001-000-000-000"
|
|
42038
42156
|
],
|
|
42039
|
-
note: "via v3: summary_initial_screen",
|
|
42040
|
-
widens: false
|
|
42157
|
+
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",
|
|
42158
|
+
widens: false,
|
|
42159
|
+
informational: true
|
|
42041
42160
|
},
|
|
42042
42161
|
{
|
|
42043
42162
|
from: "tra",
|
|
@@ -42049,8 +42168,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42049
42168
|
toCodes: [
|
|
42050
42169
|
"236-013-001-013-000-000-000"
|
|
42051
42170
|
],
|
|
42052
|
-
note: "via v3: summary_tra",
|
|
42053
|
-
widens: false
|
|
42171
|
+
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",
|
|
42172
|
+
widens: false,
|
|
42173
|
+
informational: true
|
|
42054
42174
|
},
|
|
42055
42175
|
{
|
|
42056
42176
|
from: "lap",
|
|
@@ -42062,8 +42182,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42062
42182
|
toCodes: [
|
|
42063
42183
|
"236-013-001-007-000-000-000"
|
|
42064
42184
|
],
|
|
42065
|
-
note: "via v3: summary_lap",
|
|
42066
|
-
widens: false
|
|
42185
|
+
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",
|
|
42186
|
+
widens: false,
|
|
42187
|
+
informational: true
|
|
42067
42188
|
},
|
|
42068
42189
|
{
|
|
42069
42190
|
from: "danger_assessment",
|
|
@@ -42075,8 +42196,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42075
42196
|
toCodes: [
|
|
42076
42197
|
"236-013-001-008-000-000-000"
|
|
42077
42198
|
],
|
|
42078
|
-
note: "via v3: summary_danger_assessment",
|
|
42079
|
-
widens: false
|
|
42199
|
+
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",
|
|
42200
|
+
widens: false,
|
|
42201
|
+
informational: true
|
|
42080
42202
|
},
|
|
42081
42203
|
{
|
|
42082
42204
|
from: "injury_and_strangulation",
|
|
@@ -42088,8 +42210,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42088
42210
|
toCodes: [
|
|
42089
42211
|
"236-013-001-010-000-000-000"
|
|
42090
42212
|
],
|
|
42091
|
-
note: "via v3: summary_injury_and_strangulation",
|
|
42092
|
-
widens: false
|
|
42213
|
+
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",
|
|
42214
|
+
widens: false,
|
|
42215
|
+
informational: true
|
|
42093
42216
|
},
|
|
42094
42217
|
{
|
|
42095
42218
|
from: "stalking_assessment",
|
|
@@ -42101,8 +42224,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42101
42224
|
toCodes: [
|
|
42102
42225
|
"236-013-001-009-000-000-000"
|
|
42103
42226
|
],
|
|
42104
|
-
note: "via v3: summary_stalking_assessment",
|
|
42105
|
-
widens: false
|
|
42227
|
+
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",
|
|
42228
|
+
widens: false,
|
|
42229
|
+
informational: true
|
|
42106
42230
|
},
|
|
42107
42231
|
{
|
|
42108
42232
|
from: "ae_intake",
|
|
@@ -42114,8 +42238,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42114
42238
|
toCodes: [
|
|
42115
42239
|
"236-013-001-005-000-000-000"
|
|
42116
42240
|
],
|
|
42117
|
-
note: "via v3: summary_ae_intake",
|
|
42118
|
-
widens: false
|
|
42241
|
+
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",
|
|
42242
|
+
widens: false,
|
|
42243
|
+
informational: true
|
|
42119
42244
|
},
|
|
42120
42245
|
{
|
|
42121
42246
|
from: "hope_scale",
|
|
@@ -42127,8 +42252,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42127
42252
|
toCodes: [
|
|
42128
42253
|
"236-013-001-011-000-000-000"
|
|
42129
42254
|
],
|
|
42130
|
-
note: "via v3: summary_hope_scale",
|
|
42131
|
-
widens: false
|
|
42255
|
+
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",
|
|
42256
|
+
widens: false,
|
|
42257
|
+
informational: true
|
|
42132
42258
|
},
|
|
42133
42259
|
{
|
|
42134
42260
|
from: "assessment_records",
|
|
@@ -42136,8 +42262,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42136
42262
|
rule: "retired before v4",
|
|
42137
42263
|
to: [],
|
|
42138
42264
|
toCodes: [],
|
|
42139
|
-
note: "retired with no successor row (R30); the lifecycle lines are not share content",
|
|
42140
|
-
widens: false
|
|
42265
|
+
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",
|
|
42266
|
+
widens: false,
|
|
42267
|
+
informational: true
|
|
42141
42268
|
},
|
|
42142
42269
|
{
|
|
42143
42270
|
from: "determinations",
|
|
@@ -42149,8 +42276,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42149
42276
|
toCodes: [
|
|
42150
42277
|
"236-013-001-014-000-000-000"
|
|
42151
42278
|
],
|
|
42152
|
-
note: "via v3: summary_findings",
|
|
42153
|
-
widens: false
|
|
42279
|
+
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",
|
|
42280
|
+
widens: false,
|
|
42281
|
+
informational: true
|
|
42154
42282
|
},
|
|
42155
42283
|
{
|
|
42156
42284
|
from: "mental_health_screen",
|
|
@@ -42162,8 +42290,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42162
42290
|
toCodes: [
|
|
42163
42291
|
"236-013-001-002-000-000-000"
|
|
42164
42292
|
],
|
|
42165
|
-
note: "via v3: summary_mental_health_screen",
|
|
42166
|
-
widens: false
|
|
42293
|
+
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",
|
|
42294
|
+
widens: false,
|
|
42295
|
+
informational: true
|
|
42167
42296
|
},
|
|
42168
42297
|
{
|
|
42169
42298
|
from: "trauma_and_coping_screen",
|
|
@@ -42175,8 +42304,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42175
42304
|
toCodes: [
|
|
42176
42305
|
"236-013-001-004-000-000-000"
|
|
42177
42306
|
],
|
|
42178
|
-
note: "via v3: summary_trauma_and_coping_screen",
|
|
42179
|
-
widens: false
|
|
42307
|
+
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",
|
|
42308
|
+
widens: false,
|
|
42309
|
+
informational: true
|
|
42180
42310
|
},
|
|
42181
42311
|
{
|
|
42182
42312
|
from: "behavioral_health_intake",
|
|
@@ -42188,8 +42318,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42188
42318
|
toCodes: [
|
|
42189
42319
|
"236-013-001-003-000-000-000"
|
|
42190
42320
|
],
|
|
42191
|
-
note: "via v3: summary_behavioral_health_intake",
|
|
42192
|
-
widens: false
|
|
42321
|
+
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",
|
|
42322
|
+
widens: false,
|
|
42323
|
+
informational: true
|
|
42193
42324
|
},
|
|
42194
42325
|
{
|
|
42195
42326
|
from: "screen_notes",
|
|
@@ -42197,8 +42328,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42197
42328
|
rule: "retired before v4",
|
|
42198
42329
|
to: [],
|
|
42199
42330
|
toCodes: [],
|
|
42200
|
-
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",
|
|
42201
|
-
widens: false
|
|
42331
|
+
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",
|
|
42332
|
+
widens: false,
|
|
42333
|
+
informational: true
|
|
42202
42334
|
},
|
|
42203
42335
|
{
|
|
42204
42336
|
from: "background",
|
|
@@ -42206,8 +42338,9 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
42206
42338
|
rule: "retired before v4",
|
|
42207
42339
|
to: [],
|
|
42208
42340
|
toCodes: [],
|
|
42209
|
-
note: "retired 2026-10-05 \u2014 nothing ever captured it (Crysta to Nate: Eliminate)",
|
|
42210
|
-
widens: false
|
|
42341
|
+
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",
|
|
42342
|
+
widens: false,
|
|
42343
|
+
informational: true
|
|
42211
42344
|
}
|
|
42212
42345
|
]
|
|
42213
42346
|
},
|
|
@@ -43322,7 +43455,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43322
43455
|
parentKey: "health_accommodation",
|
|
43323
43456
|
childCodes: [],
|
|
43324
43457
|
childKeys: [],
|
|
43325
|
-
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
|
|
43458
|
+
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.",
|
|
43326
43459
|
retired: true,
|
|
43327
43460
|
status: "retired",
|
|
43328
43461
|
successors: [
|
|
@@ -43331,7 +43464,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43331
43464
|
successorCodes: [
|
|
43332
43465
|
"236-006-010-000-000-000-000"
|
|
43333
43466
|
],
|
|
43334
|
-
migrationRule: "row"
|
|
43467
|
+
migrationRule: "row",
|
|
43468
|
+
v3Fields: [
|
|
43469
|
+
"capture.has_disability"
|
|
43470
|
+
],
|
|
43471
|
+
v3Domains: [
|
|
43472
|
+
"access_accommodations"
|
|
43473
|
+
]
|
|
43335
43474
|
},
|
|
43336
43475
|
{
|
|
43337
43476
|
code: "236-006-003-000-000-000-000",
|
|
@@ -43342,7 +43481,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43342
43481
|
parentKey: "health_accommodation",
|
|
43343
43482
|
childCodes: [],
|
|
43344
43483
|
childKeys: [],
|
|
43345
|
-
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
|
|
43484
|
+
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.",
|
|
43346
43485
|
retired: true,
|
|
43347
43486
|
status: "retired",
|
|
43348
43487
|
successors: [
|
|
@@ -43351,7 +43490,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43351
43490
|
successorCodes: [
|
|
43352
43491
|
"236-006-010-000-000-000-000"
|
|
43353
43492
|
],
|
|
43354
|
-
migrationRule: "row"
|
|
43493
|
+
migrationRule: "row",
|
|
43494
|
+
v3Fields: [
|
|
43495
|
+
"capture.mental_health_status"
|
|
43496
|
+
],
|
|
43497
|
+
v3Domains: [
|
|
43498
|
+
"access_accommodations"
|
|
43499
|
+
]
|
|
43355
43500
|
},
|
|
43356
43501
|
{
|
|
43357
43502
|
code: "236-006-004-000-000-000-000",
|
|
@@ -43362,7 +43507,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43362
43507
|
parentKey: "health_accommodation",
|
|
43363
43508
|
childCodes: [],
|
|
43364
43509
|
childKeys: [],
|
|
43365
|
-
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
|
|
43510
|
+
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.",
|
|
43366
43511
|
retired: true,
|
|
43367
43512
|
status: "retired",
|
|
43368
43513
|
successors: [
|
|
@@ -43371,7 +43516,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43371
43516
|
successorCodes: [
|
|
43372
43517
|
"236-006-010-000-000-000-000"
|
|
43373
43518
|
],
|
|
43374
|
-
migrationRule: "row"
|
|
43519
|
+
migrationRule: "row",
|
|
43520
|
+
v3Fields: [
|
|
43521
|
+
"capture.substance_use_status"
|
|
43522
|
+
],
|
|
43523
|
+
v3Domains: [
|
|
43524
|
+
"access_accommodations"
|
|
43525
|
+
]
|
|
43375
43526
|
},
|
|
43376
43527
|
{
|
|
43377
43528
|
code: "236-006-005-000-000-000-000",
|
|
@@ -43382,7 +43533,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43382
43533
|
parentKey: "health_accommodation",
|
|
43383
43534
|
childCodes: [],
|
|
43384
43535
|
childKeys: [],
|
|
43385
|
-
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
|
|
43536
|
+
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.",
|
|
43386
43537
|
retired: true,
|
|
43387
43538
|
status: "retired",
|
|
43388
43539
|
successors: [
|
|
@@ -43391,7 +43542,14 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43391
43542
|
successorCodes: [
|
|
43392
43543
|
"236-006-010-000-000-000-000"
|
|
43393
43544
|
],
|
|
43394
|
-
migrationRule: "row"
|
|
43545
|
+
migrationRule: "row",
|
|
43546
|
+
v3Fields: [
|
|
43547
|
+
"capture.chronic_health_severity",
|
|
43548
|
+
"capture.long_term_conditions"
|
|
43549
|
+
],
|
|
43550
|
+
v3Domains: [
|
|
43551
|
+
"access_accommodations"
|
|
43552
|
+
]
|
|
43395
43553
|
},
|
|
43396
43554
|
{
|
|
43397
43555
|
code: "236-006-006-000-000-000-000",
|
|
@@ -43402,7 +43560,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43402
43560
|
parentKey: "health_accommodation",
|
|
43403
43561
|
childCodes: [],
|
|
43404
43562
|
childKeys: [],
|
|
43405
|
-
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
|
|
43563
|
+
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.",
|
|
43406
43564
|
retired: true,
|
|
43407
43565
|
status: "retired",
|
|
43408
43566
|
successors: [
|
|
@@ -43411,7 +43569,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43411
43569
|
successorCodes: [
|
|
43412
43570
|
"236-006-010-000-000-000-000"
|
|
43413
43571
|
],
|
|
43414
|
-
migrationRule: "row"
|
|
43572
|
+
migrationRule: "row",
|
|
43573
|
+
v3Fields: [
|
|
43574
|
+
"capture.hiv_status"
|
|
43575
|
+
],
|
|
43576
|
+
v3Domains: [
|
|
43577
|
+
"access_accommodations"
|
|
43578
|
+
]
|
|
43415
43579
|
},
|
|
43416
43580
|
{
|
|
43417
43581
|
code: "236-006-007-000-000-000-000",
|
|
@@ -43579,7 +43743,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43579
43743
|
parentKey: "immigration_legal_status",
|
|
43580
43744
|
childCodes: [],
|
|
43581
43745
|
childKeys: [],
|
|
43582
|
-
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
|
|
43746
|
+
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.",
|
|
43583
43747
|
retired: true,
|
|
43584
43748
|
status: "retired",
|
|
43585
43749
|
successors: [
|
|
@@ -43588,7 +43752,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43588
43752
|
successorCodes: [
|
|
43589
43753
|
"236-007-001-000-000-000-000"
|
|
43590
43754
|
],
|
|
43591
|
-
migrationRule: "row"
|
|
43755
|
+
migrationRule: "row",
|
|
43756
|
+
v3Fields: [],
|
|
43757
|
+
v3Domains: [],
|
|
43758
|
+
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."
|
|
43592
43759
|
},
|
|
43593
43760
|
{
|
|
43594
43761
|
code: "236-007-003-000-000-000-000",
|
|
@@ -43599,7 +43766,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43599
43766
|
parentKey: "immigration_legal_status",
|
|
43600
43767
|
childCodes: [],
|
|
43601
43768
|
childKeys: [],
|
|
43602
|
-
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
|
|
43769
|
+
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.",
|
|
43603
43770
|
retired: true,
|
|
43604
43771
|
status: "retired",
|
|
43605
43772
|
successors: [
|
|
@@ -43608,7 +43775,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43608
43775
|
successorCodes: [
|
|
43609
43776
|
"236-007-006-000-000-000-000"
|
|
43610
43777
|
],
|
|
43611
|
-
migrationRule: "row"
|
|
43778
|
+
migrationRule: "row",
|
|
43779
|
+
v3Fields: [
|
|
43780
|
+
"capture.legal_action_type"
|
|
43781
|
+
],
|
|
43782
|
+
v3Domains: [
|
|
43783
|
+
"immigration_legal_status"
|
|
43784
|
+
]
|
|
43612
43785
|
},
|
|
43613
43786
|
{
|
|
43614
43787
|
code: "236-007-004-000-000-000-000",
|
|
@@ -43619,7 +43792,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43619
43792
|
parentKey: "immigration_legal_status",
|
|
43620
43793
|
childCodes: [],
|
|
43621
43794
|
childKeys: [],
|
|
43622
|
-
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
|
|
43795
|
+
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.",
|
|
43623
43796
|
retired: true,
|
|
43624
43797
|
status: "retired",
|
|
43625
43798
|
successors: [
|
|
@@ -43628,7 +43801,10 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43628
43801
|
successorCodes: [
|
|
43629
43802
|
"236-007-006-000-000-000-000"
|
|
43630
43803
|
],
|
|
43631
|
-
migrationRule: "row"
|
|
43804
|
+
migrationRule: "row",
|
|
43805
|
+
v3Fields: [],
|
|
43806
|
+
v3Domains: [],
|
|
43807
|
+
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."
|
|
43632
43808
|
},
|
|
43633
43809
|
{
|
|
43634
43810
|
code: "236-007-005-000-000-000-000",
|
|
@@ -43639,7 +43815,7 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43639
43815
|
parentKey: "immigration_legal_status",
|
|
43640
43816
|
childCodes: [],
|
|
43641
43817
|
childKeys: [],
|
|
43642
|
-
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
|
|
43818
|
+
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.",
|
|
43643
43819
|
retired: true,
|
|
43644
43820
|
status: "retired",
|
|
43645
43821
|
successors: [
|
|
@@ -43648,7 +43824,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
43648
43824
|
successorCodes: [
|
|
43649
43825
|
"236-007-006-000-000-000-000"
|
|
43650
43826
|
],
|
|
43651
|
-
migrationRule: "row"
|
|
43827
|
+
migrationRule: "row",
|
|
43828
|
+
v3Fields: [
|
|
43829
|
+
"capture.le_report_status"
|
|
43830
|
+
],
|
|
43831
|
+
v3Domains: [
|
|
43832
|
+
"immigration_legal_status"
|
|
43833
|
+
]
|
|
43652
43834
|
},
|
|
43653
43835
|
{
|
|
43654
43836
|
code: "236-007-006-000-000-000-000",
|
|
@@ -46136,13 +46318,13 @@ var coreInformationScope_v2_0_0_default = {
|
|
|
46136
46318
|
]
|
|
46137
46319
|
};
|
|
46138
46320
|
|
|
46139
|
-
// src/cvcs/roiScope.v1.
|
|
46140
|
-
var
|
|
46321
|
+
// src/cvcs/roiScope.v1.4.0.json
|
|
46322
|
+
var roiScope_v1_4_0_default = {
|
|
46141
46323
|
domain: "roi_scope",
|
|
46142
46324
|
name: "ROI Scope",
|
|
46143
|
-
version: "1.
|
|
46144
|
-
_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`
|
|
46145
|
-
_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.
|
|
46325
|
+
version: "1.4.0",
|
|
46326
|
+
_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`).',
|
|
46327
|
+
_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)",
|
|
46146
46328
|
_supersedes: {
|
|
46147
46329
|
version: "1.2.0",
|
|
46148
46330
|
keyMap: {
|
|
@@ -46180,18 +46362,18 @@ var roiScope_v1_3_0_default = {
|
|
|
46180
46362
|
},
|
|
46181
46363
|
retiredCodes: [],
|
|
46182
46364
|
notes: {
|
|
46183
|
-
summary: "Every v1.2.0 key is still an entry
|
|
46184
|
-
ida_full: "v1.2.0 `ida_full` was a selectable item. CVC-236
|
|
46185
|
-
ida_consid: "v1.2.0 `ida_consid` was a selectable item. CVC-236
|
|
46186
|
-
disability_subtypes: "v1.2.0 `disability_subtypes` was a selectable item. CVC-236
|
|
46187
|
-
mental_health_status: "v1.2.0 `mental_health_status` was a selectable item. CVC-236
|
|
46188
|
-
substance_use_status: "v1.2.0 `substance_use_status` was a selectable item. CVC-236
|
|
46189
|
-
chronic_health_status: "v1.2.0 `chronic_health_status` was a selectable item. CVC-236
|
|
46190
|
-
hiv_status: "v1.2.0 `hiv_status` was a selectable item. CVC-236
|
|
46191
|
-
uscis_alien_number: "v1.2.0 `uscis_alien_number` was a selectable item. CVC-236
|
|
46192
|
-
federal_protection_applications: "v1.2.0 `federal_protection_applications` was a selectable item. CVC-236
|
|
46193
|
-
tvap_enrollment: "v1.2.0 `tvap_enrollment` was a selectable item. CVC-236
|
|
46194
|
-
le_report_status: "v1.2.0 `le_report_status` was a selectable item. CVC-236
|
|
46365
|
+
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.",
|
|
46366
|
+
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).",
|
|
46367
|
+
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).",
|
|
46368
|
+
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`).",
|
|
46369
|
+
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`).",
|
|
46370
|
+
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`).",
|
|
46371
|
+
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`).",
|
|
46372
|
+
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`).",
|
|
46373
|
+
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`).",
|
|
46374
|
+
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`).",
|
|
46375
|
+
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`).",
|
|
46376
|
+
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`)."
|
|
46195
46377
|
}
|
|
46196
46378
|
},
|
|
46197
46379
|
levels: {
|
|
@@ -46309,7 +46491,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46309
46491
|
selectable: false,
|
|
46310
46492
|
parentCode: null,
|
|
46311
46493
|
childCodes: [],
|
|
46312
|
-
definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.
|
|
46494
|
+
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.",
|
|
46313
46495
|
retired: true
|
|
46314
46496
|
},
|
|
46315
46497
|
{
|
|
@@ -46319,7 +46501,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46319
46501
|
selectable: false,
|
|
46320
46502
|
parentCode: null,
|
|
46321
46503
|
childCodes: [],
|
|
46322
|
-
definition: "RETIRED 2026-10-08 (INFOSCOPE-RETIRE; signed Instruments spec v4, R30), matching its CVC-236 `core_information_scope` v2.
|
|
46504
|
+
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.",
|
|
46323
46505
|
retired: true
|
|
46324
46506
|
},
|
|
46325
46507
|
{
|
|
@@ -46403,7 +46585,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46403
46585
|
selectable: false,
|
|
46404
46586
|
parentCode: null,
|
|
46405
46587
|
childCodes: [],
|
|
46406
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
46588
|
+
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.",
|
|
46407
46589
|
retired: true
|
|
46408
46590
|
},
|
|
46409
46591
|
{
|
|
@@ -46413,7 +46595,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46413
46595
|
selectable: false,
|
|
46414
46596
|
parentCode: null,
|
|
46415
46597
|
childCodes: [],
|
|
46416
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
46598
|
+
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.",
|
|
46417
46599
|
retired: true
|
|
46418
46600
|
},
|
|
46419
46601
|
{
|
|
@@ -46423,7 +46605,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46423
46605
|
selectable: false,
|
|
46424
46606
|
parentCode: null,
|
|
46425
46607
|
childCodes: [],
|
|
46426
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
46608
|
+
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.",
|
|
46427
46609
|
retired: true
|
|
46428
46610
|
},
|
|
46429
46611
|
{
|
|
@@ -46433,7 +46615,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46433
46615
|
selectable: false,
|
|
46434
46616
|
parentCode: null,
|
|
46435
46617
|
childCodes: [],
|
|
46436
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
46618
|
+
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.",
|
|
46437
46619
|
retired: true
|
|
46438
46620
|
},
|
|
46439
46621
|
{
|
|
@@ -46443,7 +46625,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46443
46625
|
selectable: false,
|
|
46444
46626
|
parentCode: null,
|
|
46445
46627
|
childCodes: [],
|
|
46446
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
46628
|
+
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.",
|
|
46447
46629
|
retired: true
|
|
46448
46630
|
},
|
|
46449
46631
|
{
|
|
@@ -46462,7 +46644,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46462
46644
|
selectable: false,
|
|
46463
46645
|
parentCode: null,
|
|
46464
46646
|
childCodes: [],
|
|
46465
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
46647
|
+
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.",
|
|
46466
46648
|
retired: true
|
|
46467
46649
|
},
|
|
46468
46650
|
{
|
|
@@ -46472,7 +46654,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46472
46654
|
selectable: false,
|
|
46473
46655
|
parentCode: null,
|
|
46474
46656
|
childCodes: [],
|
|
46475
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
46657
|
+
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.",
|
|
46476
46658
|
retired: true
|
|
46477
46659
|
},
|
|
46478
46660
|
{
|
|
@@ -46482,7 +46664,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46482
46664
|
selectable: false,
|
|
46483
46665
|
parentCode: null,
|
|
46484
46666
|
childCodes: [],
|
|
46485
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
46667
|
+
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.",
|
|
46486
46668
|
retired: true
|
|
46487
46669
|
},
|
|
46488
46670
|
{
|
|
@@ -46492,7 +46674,7 @@ var roiScope_v1_3_0_default = {
|
|
|
46492
46674
|
selectable: false,
|
|
46493
46675
|
parentCode: null,
|
|
46494
46676
|
childCodes: [],
|
|
46495
|
-
definition: "RETIRED 2026-10-09 (INFOSCOPE v4 SIMPLIFY, Crysta; GDR \xA7 0.6.2 rule 6), matching its CVC-236 `core_information_scope` v2.
|
|
46677
|
+
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.",
|
|
46496
46678
|
retired: true
|
|
46497
46679
|
}
|
|
46498
46680
|
]
|
|
@@ -62725,6 +62907,7 @@ var CVC_197_VALUES = selectableCodes(
|
|
|
62725
62907
|
INCIDENT_PARTICIPATION_ROLE_LABELS,
|
|
62726
62908
|
INCIDENT_PARTICIPATION_ROLE_SUPERSEDED_BY,
|
|
62727
62909
|
INCIDENT_PARTICIPATION_ROLE_VALUES,
|
|
62910
|
+
INFORMATION_SCOPE_POLICY_VERSION_ROW_NOTE,
|
|
62728
62911
|
INFORMATION_SCOPE_READABLE_VERSIONS,
|
|
62729
62912
|
INFORMATION_SCOPE_SYSTEM_INFO,
|
|
62730
62913
|
INFORMATION_SCOPE_VERSION,
|