@htilabs/platform-common-models 0.8.19 → 0.8.21
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 +132 -1
- package/dist/cvcs/index.cjs.map +1 -1
- package/dist/cvcs/index.d.cts +1936 -1791
- package/dist/cvcs/index.d.ts +1936 -1791
- package/dist/cvcs/index.js +131 -1
- package/dist/cvcs/index.js.map +1 -1
- package/dist/index.cjs +148 -2
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +22 -3
- package/dist/index.d.ts +22 -3
- package/dist/index.js +146 -2
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
- package/src/__tests__/__snapshots__/cvc-sot.snap +2 -2
- package/src/__tests__/cvc-drift-gate.test.ts +13 -0
- package/src/__tests__/cvc-sot-snapshot.test.ts +9 -1
- package/src/cvcs/assertionDomain.v1.1.0.json +19 -1
- package/src/cvcs/index.ts +2 -0
- package/src/cvcs/riskIdentificationMilestone.v1.0.0.json +109 -0
- package/src/generated/cvc-enums.ts +22 -1
package/package.json
CHANGED
|
@@ -511,8 +511,8 @@
|
|
|
511
511
|
"hash": "995a3170efe8219c0bfe0a174abb2389c86bf94423a70a5ce2b2feb3d9e6b3fa"
|
|
512
512
|
},
|
|
513
513
|
"assertion_domain": {
|
|
514
|
-
"count":
|
|
515
|
-
"hash": "
|
|
514
|
+
"count": 70,
|
|
515
|
+
"hash": "6b10f093870817757f4dcb45a513b347f0491ae3ca08c518e3c88df52cd48fdb"
|
|
516
516
|
},
|
|
517
517
|
"activity_type": {
|
|
518
518
|
"count": 14,
|
|
@@ -264,6 +264,19 @@ const INDEX_ABSENT: Record<string, { cvc: number; reason: string }> = {
|
|
|
264
264
|
// but CVC_INDEX.md carries no row. Not a squat (nothing else claims these
|
|
265
265
|
// numbers) — but each needs a Notion index row to become verifiable.
|
|
266
266
|
service_categories: { cvc: 22, reason: "no CVC_INDEX row" },
|
|
267
|
+
// Ratified in the live Notion CVC-159 codebook 2026-08-29 (Crysta knock-out
|
|
268
|
+
// walk) and mirrored to `data/cvcs/core_assertion_domain_extensions_
|
|
269
|
+
// signal_identification.yaml` (prototype PR #519), but CVC_INDEX.md carries no
|
|
270
|
+
// row: the 2026-08-29 targeted live refresh updated CVC-159's own rows without
|
|
271
|
+
// re-running extract_final_cvcs.py, so no `Final CVCs/` export exists for this
|
|
272
|
+
// slice yet. The number is the domain's own self-declaration (CVC-267) and
|
|
273
|
+
// nothing else claims it. NOT parked at 900+ on purpose — same reasoning as
|
|
274
|
+
// core_information_scope: that block is for vocabularies with no canonical
|
|
275
|
+
// number, and parking a numbered domain there would leave 267 looking free.
|
|
276
|
+
risk_identification_milestone: {
|
|
277
|
+
cvc: 267,
|
|
278
|
+
reason: "no CVC_INDEX row — authored live in Notion 2026-08-29, extractor not re-run",
|
|
279
|
+
},
|
|
267
280
|
// Authored directly in the live Notion inline DB (2026-08-13, restructured
|
|
268
281
|
// 2026-08-14), so no `Final CVCs/` export exists yet and extract_final_cvcs.py
|
|
269
282
|
// emits no row. The number is the domain's own self-declaration —
|
|
@@ -604,7 +604,15 @@ const SOT_SPECS: readonly SotSpec[] = [
|
|
|
604
604
|
// root + 3 canonical missingness children = 16. CVC number is PROVISIONAL
|
|
605
605
|
// pending ratification.
|
|
606
606
|
{ file: "housingSubsidyTypes.v1.0.0.json", domain: "housing_subsidy_types", expectedCount: 16 },
|
|
607
|
-
|
|
607
|
+
// 68 -> 75: the 2026-08-29 signal-identification ratification adds two Level-1
|
|
608
|
+
// domains (signal_identification 159-066, investigative_legal 159-067) plus the
|
|
609
|
+
// five identification-funnel rungs as their Level-2 value rows.
|
|
610
|
+
// 75 -> 70: the five identification-funnel rungs move OUT of CVC-159 into
|
|
611
|
+
// their own vocabulary (riskIdentificationMilestone, CVC-267). CVC-159 keeps
|
|
612
|
+
// the two new Level-1 DOMAINS only — AssertionDomainKeys is the set of
|
|
613
|
+
// domains, and a value folded into it makes `on_radar` demand a domain
|
|
614
|
+
// classification in every downstream totality gate.
|
|
615
|
+
{ file: "assertionDomain.v1.1.0.json", domain: "assertion_domain", expectedCount: 70 },
|
|
608
616
|
{ file: "activityType.v1.0.0.json", domain: "activity_type", expectedCount: 14 },
|
|
609
617
|
{ file: "provenanceSourceId.v1.0.0.json", domain: "provenance_source_id", expectedCount: 13 },
|
|
610
618
|
{ file: "radiusBucket.v1.0.0.json", domain: "radius_bucket", expectedCount: 9 },
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"domain": "assertion_domain",
|
|
3
3
|
"name": "Assertion Domain (CVC-159)",
|
|
4
4
|
"version": "2.0.0",
|
|
5
|
-
"_status": "CANONICAL — RENUMBERED 0.8.13 from provisional CVC-964 to canonical CVC-159. Live prototype HEAD a596eb9: `Final CVCs` -> `core - assertion_domain` = CVC-159 (vocab_status 'Ready for dev', Verification 'Verified'), corroborated by 17 `data/cvcs/core_assertion_domain_extensions_*.yaml` files that all declare `cvc: core - assertion_domain`. CVC-159 was freed by deleting the 100%-unbound hand-coded `CVC_159_RELATIONSHIP_TIES` family from `src/constants/ic.ts`; `relationship_ties` keeps its canonical CVC-158. Consumers persist KEYS, not wire codes, so the renumber is compile-clean (regenerate `cvcKeys.ts`). WITHDRAWN in 0.8.13 (all three have ZERO occurrences at prototype HEAD): `romantic_relationship` (964-066) — upstream the romantic-partner lifecycle routes to `household_relationships`, see `data/cvcs/core_romantic_relationship_change_type.yaml`; `household_tenure` (964-045); `household_composition` (964-067). All three fold into `household_relationships` (554 occurrences at HEAD). NOTE: `romantic_partner` is a relationship-type VALUE code (1,575 occurrences), never an assertion domain — it is correctly not modelled here. `child_profile` (159-065) is KEPT: 353 occurrences at HEAD. Segment-2 ordinals are preserved across the renumber (gaps at 045/066/067 are intentional; no data migration exists, but stable ordinals keep the diff reviewable). The 37 domains PAVE ships that are absent from the Final CVC-159 export all have substantial upstream occurrence counts and are retained as proposed CVC-159 extensions.",
|
|
5
|
+
"_status": "CANONICAL — RENUMBERED 0.8.13 from provisional CVC-964 to canonical CVC-159. Live prototype HEAD a596eb9: `Final CVCs` -> `core - assertion_domain` = CVC-159 (vocab_status 'Ready for dev', Verification 'Verified'), corroborated by 17 `data/cvcs/core_assertion_domain_extensions_*.yaml` files that all declare `cvc: core - assertion_domain`. CVC-159 was freed by deleting the 100%-unbound hand-coded `CVC_159_RELATIONSHIP_TIES` family from `src/constants/ic.ts`; `relationship_ties` keeps its canonical CVC-158. Consumers persist KEYS, not wire codes, so the renumber is compile-clean (regenerate `cvcKeys.ts`). WITHDRAWN in 0.8.13 (all three have ZERO occurrences at prototype HEAD): `romantic_relationship` (964-066) — upstream the romantic-partner lifecycle routes to `household_relationships`, see `data/cvcs/core_romantic_relationship_change_type.yaml`; `household_tenure` (964-045); `household_composition` (964-067). All three fold into `household_relationships` (554 occurrences at HEAD). NOTE: `romantic_partner` is a relationship-type VALUE code (1,575 occurrences), never an assertion domain — it is correctly not modelled here. `child_profile` (159-065) is KEPT: 353 occurrences at HEAD. Segment-2 ordinals are preserved across the renumber (gaps at 045/066/067 are intentional; no data migration exists, but stable ordinals keep the diff reviewable). The 37 domains PAVE ships that are absent from the Final CVC-159 export all have substantial upstream occurrence counts and are retained as proposed CVC-159 extensions. | 0.8.20: ADDED `signal_identification` (159-066) and `investigative_legal` (159-067) -- retroactive homing of the Track-1 identification-rung emitter live since 2026-08-23; both ratified in the CVC-159 codebook 2026-08-29 (prototype PR #519, hti-features PR #34). Ordinals 066/067 were free: the 0.8.13 withdrawals that reserved those slots were under the OLD CVC-964 numbering and the 159 equivalents were never issued -- verified zero references to 159-066/159-067 anywhere in the repo or the published dist before assigning. The 045 gap remains reserved. The rung VALUE set those two domains carry lives in its own vocabulary (`riskIdentificationMilestone`, CVC-267) rather than as Level-2 rows here: `AssertionDomainKeys` is consumed as THE SET OF DOMAINS, and folding values into it breaks that contract for every consumer -- PAVE's `Record<AssertionDomain, DomainValueVocabulary>` totality gate would demand a domain classification for `on_radar`. CVC-159 stays Level-1 only.",
|
|
6
6
|
"_source": "htilabstech/prototype@a596eb9 Final CVCs/Assertion Contract/core - assertion_domain.md (CVC-159) + 17 core_assertion_domain_extensions_*.yaml",
|
|
7
7
|
"levels": {
|
|
8
8
|
"0": "Unknown or Missing",
|
|
@@ -624,6 +624,24 @@
|
|
|
624
624
|
"parentCode": null,
|
|
625
625
|
"childCodes": [],
|
|
626
626
|
"definition": "assertion_domain partition for CARs on a Child profile subject-record entity (Add Child / Edit Child; core_child_change_type verbs). DRAFT-TEMPORARY direct import from prototype, pending Notion ratification."
|
|
627
|
+
},
|
|
628
|
+
{
|
|
629
|
+
"code": "159-066-000-000-000-000-000",
|
|
630
|
+
"key": "signal_identification",
|
|
631
|
+
"title": "Signal / Identification",
|
|
632
|
+
"selectable": true,
|
|
633
|
+
"parentCode": null,
|
|
634
|
+
"childCodes": [],
|
|
635
|
+
"definition": "The identification-funnel pipeline domain: a subject's position on the reach ladder (on_radar -> screened -> at_risk -> assessed), asserted by the `identification_rung_reached` CAR whose `assertion_value_code` is the rung (CVC-267). Ratified 2026-08-29 as retroactive codebook homing of a live emitter that has minted rung CARs since 2026-08-23 (Crysta ruling, milestone-residue R1). A rung CAR asserts that a subject REACHED a rung; it never restates a determination -- it joins the derived milestone row via `pm_ref`, and the derived row remains the derived row (a milestone row never IS the CAR). Distinct from `identification_status` (CVC-241), the identity-CONFIDENCE axis; per the 2026-06-30 naming directive that axis is named `identity_status` and 'identification ladder' is a retired synonym for it -- display copy for THIS domain says 'identification funnel' or 'pipeline rungs', never bare 'identification ladder'. The `determined` rung is filed under BOTH this domain and `investigative_legal` (ruling 2026-08-29); its STORED domain stays `investigative_legal` as built."
|
|
636
|
+
},
|
|
637
|
+
{
|
|
638
|
+
"code": "159-067-000-000-000-000-000",
|
|
639
|
+
"key": "investigative_legal",
|
|
640
|
+
"title": "Investigative / Legal",
|
|
641
|
+
"selectable": true,
|
|
642
|
+
"parentCode": null,
|
|
643
|
+
"childCodes": [],
|
|
644
|
+
"definition": "The investigation-and-legal-process domain. Carries `TRAFFICKING_STATUS` (CVC-267) and is the STORED `assertion_domain` of the `determined` rung of the identification funnel -- the rung measures reaching a conclusion in a safe setting, not which conclusion, so a no-indication determination still counts. Ratified 2026-08-29 alongside `signal_identification`: it is live in the same emitter and was equally unhomed. Filed-under-both (ruling 2026-08-29): data relevant to multiple milestone topics is documented under every topic it is relevant for, while CVC-159's one-assertion-one-domain rule keeps the STORED domain single -- nothing re-mints."
|
|
627
645
|
}
|
|
628
646
|
]
|
|
629
647
|
}
|
package/src/cvcs/index.ts
CHANGED
|
@@ -165,6 +165,7 @@ import coreReferralOutcomeSot from "./coreReferralOutcome.v1.0.0.json" with { ty
|
|
|
165
165
|
import coreIndicatorsSot from "./coreIndicators.v1.0.0.json" with { type: "json" };
|
|
166
166
|
import coreDhStateSot from "./coreDhState.v1.0.0.json" with { type: "json" };
|
|
167
167
|
import riskSeverityBandSot from "./riskSeverityBand.v1.0.0.json" with { type: "json" };
|
|
168
|
+
import riskIdentificationMilestoneSot from "./riskIdentificationMilestone.v1.0.0.json" with { type: "json" };
|
|
168
169
|
import adminRolesSot from "./adminRoles.v1.0.0.json" with { type: "json" };
|
|
169
170
|
import userRolesSot from "./userRoles.v1.0.0.json" with { type: "json" };
|
|
170
171
|
import hmisCurrentLivingSituationSot from "./hmisCurrentLivingSituation.v1.0.0.json" with { type: "json" };
|
|
@@ -360,6 +361,7 @@ export {
|
|
|
360
361
|
coreIndicatorsSot,
|
|
361
362
|
coreDhStateSot,
|
|
362
363
|
riskSeverityBandSot,
|
|
364
|
+
riskIdentificationMilestoneSot,
|
|
363
365
|
adminRolesSot,
|
|
364
366
|
userRolesSot,
|
|
365
367
|
hmisCurrentLivingSituationSot,
|
|
@@ -0,0 +1,109 @@
|
|
|
1
|
+
{
|
|
2
|
+
"domain": "risk_identification_milestone",
|
|
3
|
+
"name": "Core Risk Identification Milestone (CVC-267)",
|
|
4
|
+
"version": "1.0.0",
|
|
5
|
+
"_status": "CANONICAL -- ratified 2026-08-29 (Crysta knock-out walk). The identification-FUNNEL rung value set: the vocabulary `assertion_value_code` resolves against when `assertion_domain` is `signal_identification` (CVC-159 159-066) or, for `determined`, `investigative_legal` (159-067). Homes the `identification_rung_reached` CAR (Crysta-named 2026-08-23) minted once per subject per rung first reached, deterministic id `ast-t1r-<sid>-<rung>`, retroactively over the derived corpus. The rung CAR is a sibling EVENT record joined to the derived milestone row via `pm_ref`: the derived row remains derived and re-derives, and a milestone row never IS the CAR (spine 5.5). The 2026-05-11 no-CAR ruling STAYS IN FORCE for Track-3 rollups -- this is a carve-out for rung events, not a new default. Modelled as its OWN vocabulary rather than as Level-2 rows inside CVC-159: `AssertionDomainKeys` is consumed as the set of DOMAINS, and folding values into it breaks that contract downstream. Naming guard (Crysta 2026-06-30): identification FUNNEL / pipeline rungs -- never 'identification ladder', a retired synonym for the identity-CONFIDENCE axis `identity_status`.",
|
|
6
|
+
"_source": "htilabstech/prototype Final CVCs core - risk_identification_milestone (CVC-267) + data/cvcs/core_assertion_domain_extensions_signal_identification.yaml (PR #519); Notion 'Signal / identification question' (2026-08-29)",
|
|
7
|
+
"levels": {
|
|
8
|
+
"0": "Unknown or Missing",
|
|
9
|
+
"1": "Identification funnel rung"
|
|
10
|
+
},
|
|
11
|
+
"entries": [
|
|
12
|
+
{
|
|
13
|
+
"code": "267-000-000-000-000-000-000",
|
|
14
|
+
"key": "missingness_root",
|
|
15
|
+
"title": "Unknown, Redacted, or Missing",
|
|
16
|
+
"selectable": false,
|
|
17
|
+
"parentCode": null,
|
|
18
|
+
"childCodes": [
|
|
19
|
+
"267-000-000-000-000-000-001",
|
|
20
|
+
"267-000-000-000-000-000-002",
|
|
21
|
+
"267-000-000-000-000-000-003"
|
|
22
|
+
],
|
|
23
|
+
"definition": "Root group for values indicating absent, withheld, or uncollected data. Variant: 3-value (unknown, anonymous, data_not_collected) under the workspace standard ANON semantic."
|
|
24
|
+
},
|
|
25
|
+
{
|
|
26
|
+
"code": "267-000-000-000-000-000-001",
|
|
27
|
+
"key": "unknown",
|
|
28
|
+
"title": "Unknown",
|
|
29
|
+
"selectable": true,
|
|
30
|
+
"parentCode": "267-000-000-000-000-000-000",
|
|
31
|
+
"childCodes": [],
|
|
32
|
+
"canonicalCode": "UNK",
|
|
33
|
+
"definition": "Unknown or cannot be determined from the available information. NOT a safe default. Distinct from having reached NO rung: a subject who has reached no rung has NO rows at all. The milestone-symmetry `NO_IDENTIFICATION` row is deliberately NOT part of this value set (ruling 2026-08-29, OR2) -- absence of rung CARs IS the no-state, and minting a 'none' assertion would re-assert a derived status."
|
|
34
|
+
},
|
|
35
|
+
{
|
|
36
|
+
"code": "267-000-000-000-000-000-002",
|
|
37
|
+
"key": "anonymous",
|
|
38
|
+
"title": "Anonymous / declined to answer",
|
|
39
|
+
"selectable": true,
|
|
40
|
+
"parentCode": "267-000-000-000-000-000-000",
|
|
41
|
+
"childCodes": [],
|
|
42
|
+
"definition": "Value is intentionally withheld or redacted. Combines declined-to-answer and redacted/anonymous semantics under the workspace standard ANON sentinel."
|
|
43
|
+
},
|
|
44
|
+
{
|
|
45
|
+
"code": "267-000-000-000-000-000-003",
|
|
46
|
+
"key": "data_not_collected",
|
|
47
|
+
"title": "Data not collected",
|
|
48
|
+
"selectable": true,
|
|
49
|
+
"parentCode": "267-000-000-000-000-000-000",
|
|
50
|
+
"childCodes": [],
|
|
51
|
+
"definition": "No attempt was made to collect the value. System-only sentinel per GLOBAL_DESIGN_RULES."
|
|
52
|
+
},
|
|
53
|
+
{
|
|
54
|
+
"code": "267-001-000-000-000-000-000",
|
|
55
|
+
"key": "on_radar",
|
|
56
|
+
"title": "On radar",
|
|
57
|
+
"selectable": true,
|
|
58
|
+
"parentCode": null,
|
|
59
|
+
"childCodes": [],
|
|
60
|
+
"ordinal": 1,
|
|
61
|
+
"assertionDomain": "signal_identification",
|
|
62
|
+
"definition": "Rung 1. The subject is known to the system at all. EVERY new person record counts, with the origin kind carried on the derived milestone row (ruling 2026-08-20, confirmed x3). Stored `assertion_domain`: `signal_identification`."
|
|
63
|
+
},
|
|
64
|
+
{
|
|
65
|
+
"code": "267-002-000-000-000-000-000",
|
|
66
|
+
"key": "screened",
|
|
67
|
+
"title": "Screened",
|
|
68
|
+
"selectable": true,
|
|
69
|
+
"parentCode": null,
|
|
70
|
+
"childCodes": [],
|
|
71
|
+
"ordinal": 2,
|
|
72
|
+
"assertionDomain": "signal_identification",
|
|
73
|
+
"definition": "Rung 2. A screening instrument was administered. A CLEAN screening still counts -- the rung measures REACH, not result; results are row data (ruling 2026-08-20, confirmed x3). Stored `assertion_domain`: `signal_identification`."
|
|
74
|
+
},
|
|
75
|
+
{
|
|
76
|
+
"code": "267-003-000-000-000-000-000",
|
|
77
|
+
"key": "at_risk",
|
|
78
|
+
"title": "At risk",
|
|
79
|
+
"selectable": true,
|
|
80
|
+
"parentCode": null,
|
|
81
|
+
"childCodes": [],
|
|
82
|
+
"ordinal": 3,
|
|
83
|
+
"assertionDomain": "signal_identification",
|
|
84
|
+
"definition": "Rung 3. Satisfiable by EITHER an upward risk-band crossing OR a screening `recommended_followup` -- both count, and `satisfied_by` is carried on every row so analysis can separate the sources (ruling 2026-08-20 R1). Stored `assertion_domain`: `signal_identification`."
|
|
85
|
+
},
|
|
86
|
+
{
|
|
87
|
+
"code": "267-004-000-000-000-000-000",
|
|
88
|
+
"key": "assessed",
|
|
89
|
+
"title": "Assessed",
|
|
90
|
+
"selectable": true,
|
|
91
|
+
"parentCode": null,
|
|
92
|
+
"childCodes": [],
|
|
93
|
+
"ordinal": 4,
|
|
94
|
+
"assertionDomain": "signal_identification",
|
|
95
|
+
"definition": "Rung 4. A full assessment was completed. Stored `assertion_domain`: `signal_identification`."
|
|
96
|
+
},
|
|
97
|
+
{
|
|
98
|
+
"code": "267-005-000-000-000-000-000",
|
|
99
|
+
"key": "determined",
|
|
100
|
+
"title": "Determined",
|
|
101
|
+
"selectable": true,
|
|
102
|
+
"parentCode": null,
|
|
103
|
+
"childCodes": [],
|
|
104
|
+
"ordinal": 5,
|
|
105
|
+
"assertionDomain": "investigative_legal",
|
|
106
|
+
"definition": "Rung 5. A determination was reached in a safe setting. A NO-INDICATION determination still counts -- the rung measures reaching a conclusion, not which conclusion (ruling 2026-08-20, confirmed x3). STORED `assertion_domain` is `investigative_legal` (159-067) because CVC-267 TRAFFICKING_STATUS carries that domain; DOCUMENTED under `signal_identification` too (filed-under-both ruling 2026-08-29) without changing what is stored. Cross-population caveat: most determinations on file predate the screening rail, so a subject can legitimately show `determined` with no `screened` above it -- correct, not a broken chain."
|
|
107
|
+
}
|
|
108
|
+
]
|
|
109
|
+
}
|
|
@@ -3556,7 +3556,7 @@ export type HousingSubsidyTypesKey = keyof typeof HousingSubsidyTypesKeys;
|
|
|
3556
3556
|
/**
|
|
3557
3557
|
* Key → positional code map for the `assertion_domain` CVC domain (CAR assertion domain; PROVISIONAL, pending Notion ratification).
|
|
3558
3558
|
*
|
|
3559
|
-
* Domain: `assertion_domain` · Version: 2.0.0 · Entries:
|
|
3559
|
+
* Domain: `assertion_domain` · Version: 2.0.0 · Entries: 70
|
|
3560
3560
|
*/
|
|
3561
3561
|
export const AssertionDomainKeys = {
|
|
3562
3562
|
missingness_root: "159-000-000-000-000-000-000",
|
|
@@ -3627,6 +3627,8 @@ export const AssertionDomainKeys = {
|
|
|
3627
3627
|
facilitator_subrole: "159-063-000-000-000-000-000",
|
|
3628
3628
|
facilitator_entity_type: "159-064-000-000-000-000-000",
|
|
3629
3629
|
child_profile: "159-065-000-000-000-000-000",
|
|
3630
|
+
signal_identification: "159-066-000-000-000-000-000",
|
|
3631
|
+
investigative_legal: "159-067-000-000-000-000-000",
|
|
3630
3632
|
} as const;
|
|
3631
3633
|
|
|
3632
3634
|
export type AssertionDomainKey = keyof typeof AssertionDomainKeys;
|
|
@@ -4464,6 +4466,25 @@ export const CoreIndicatorKeys = {
|
|
|
4464
4466
|
|
|
4465
4467
|
export type CoreIndicatorKey = keyof typeof CoreIndicatorKeys;
|
|
4466
4468
|
|
|
4469
|
+
/**
|
|
4470
|
+
* Key → positional code map for the `risk_identification_milestone` CVC domain (CVC-267, ratified 2026-08-29). The identification-FUNNEL rung value set — the vocabulary `assertion_value_code` resolves against for the `identification_rung_reached` CAR. Four rungs store `assertion_domain` `signal_identification` (CVC-159 159-066); `determined` stores `investigative_legal` (159-067) and is documented under both (filed-under-both ruling 2026-08-29). Each entry carries its stored `assertionDomain` so a consumer can route a rung without a second table. Deliberately its OWN vocabulary, not Level-2 rows inside CVC-159: `AssertionDomainKeys` is the set of DOMAINS, and folding values in would make `on_radar` demand a domain classification downstream. The milestone-symmetry no-state row is absent: reaching no rung is the ABSENCE of rows.
|
|
4471
|
+
*
|
|
4472
|
+
* Domain: `risk_identification_milestone` · Version: 1.0.0 · Entries: 9
|
|
4473
|
+
*/
|
|
4474
|
+
export const RiskIdentificationMilestoneKeys = {
|
|
4475
|
+
missingness_root: "267-000-000-000-000-000-000",
|
|
4476
|
+
unknown: "267-000-000-000-000-000-001",
|
|
4477
|
+
anonymous: "267-000-000-000-000-000-002",
|
|
4478
|
+
data_not_collected: "267-000-000-000-000-000-003",
|
|
4479
|
+
on_radar: "267-001-000-000-000-000-000",
|
|
4480
|
+
screened: "267-002-000-000-000-000-000",
|
|
4481
|
+
at_risk: "267-003-000-000-000-000-000",
|
|
4482
|
+
assessed: "267-004-000-000-000-000-000",
|
|
4483
|
+
determined: "267-005-000-000-000-000-000",
|
|
4484
|
+
} as const;
|
|
4485
|
+
|
|
4486
|
+
export type RiskIdentificationMilestoneKey = keyof typeof RiskIdentificationMilestoneKeys;
|
|
4487
|
+
|
|
4467
4488
|
/**
|
|
4468
4489
|
* Key → positional code map for the `risk_severity_band` CVC domain (CVC-238, VERIFIED). Replaces the withdrawn provisional `risk_band` (981). Carries the load-bearing `lowerBand` thresholds 0/20/40/60/80 that the milestone band-crossing trigger reads.
|
|
4469
4490
|
*
|