@htilabs/platform-common-models 0.8.20 → 0.8.22
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/constants/index.cjs +5 -1
- package/dist/constants/index.cjs.map +1 -1
- package/dist/constants/index.d.cts +1 -1
- package/dist/constants/index.d.ts +1 -1
- package/dist/constants/index.js +5 -1
- package/dist/constants/index.js.map +1 -1
- package/dist/cvcs/index.cjs +128 -58
- package/dist/cvcs/index.cjs.map +1 -1
- package/dist/cvcs/index.d.cts +1929 -1849
- package/dist/cvcs/index.d.ts +1929 -1849
- package/dist/cvcs/index.js +127 -58
- package/dist/cvcs/index.js.map +1 -1
- package/dist/{index-C0J3f169.d.ts → index-4DiJrn7y.d.ts} +1 -1
- package/dist/{index-EPjPjR0z.d.cts → index-qreOzXYS.d.cts} +1 -1
- package/dist/index.cjs +149 -66
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +25 -12
- package/dist/index.d.ts +25 -12
- package/dist/index.js +147 -66
- package/dist/index.js.map +1 -1
- package/dist/models/index.d.cts +2 -2
- package/dist/models/index.d.ts +2 -2
- package/dist/{platform-auth-CvQkzOy1.d.cts → platform-auth-91Hcl8F8.d.cts} +3 -2
- package/dist/{platform-auth-CvQkzOy1.d.ts → platform-auth-91Hcl8F8.d.ts} +3 -2
- package/dist/schemas/index.cjs +5 -1
- package/dist/schemas/index.cjs.map +1 -1
- package/dist/schemas/index.d.cts +25 -25
- package/dist/schemas/index.d.ts +25 -25
- package/dist/schemas/index.js +5 -1
- package/dist/schemas/index.js.map +1 -1
- package/dist/types/index.d.cts +2 -2
- package/dist/types/index.d.ts +2 -2
- package/package.json +1 -1
- package/src/__tests__/__snapshots__/cvc-sot.snap +4 -4
- package/src/__tests__/cvc-drift-gate.test.ts +17 -4
- package/src/__tests__/cvc-sot-snapshot.test.ts +8 -3
- package/src/constants/ic.ts +4 -0
- package/src/cvcs/assertionDomain.v1.1.0.json +4 -57
- package/src/cvcs/incidentParticipationRoles.v1.0.0.json +11 -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 -7
- package/dist/{cvcEntry-DaDrEuTa.d.cts → cvcEntry-ctHTp2df.d.cts} +8 -8
- package/dist/{cvcEntry-DaDrEuTa.d.ts → cvcEntry-ctHTp2df.d.ts} +8 -8
package/dist/index.js
CHANGED
|
@@ -1370,6 +1370,7 @@ var INCIDENT_PARTICIPATION_ROLE = {
|
|
|
1370
1370
|
DATA_ENTRY: "data_entry",
|
|
1371
1371
|
OTHER_INCIDENT_RESPONDER: "other_incident_responder",
|
|
1372
1372
|
RESPONDING_OFFICER: "responding_officer",
|
|
1373
|
+
LEGAL_PROFESSIONAL: "legal_professional",
|
|
1373
1374
|
UNKNOWN: "unknown",
|
|
1374
1375
|
ANONYMOUS: "anonymous",
|
|
1375
1376
|
DATA_NOT_COLLECTED: "data_not_collected"
|
|
@@ -1386,6 +1387,7 @@ var INCIDENT_PARTICIPATION_ROLE_VALUES = [
|
|
|
1386
1387
|
INCIDENT_PARTICIPATION_ROLE.DATA_ENTRY,
|
|
1387
1388
|
INCIDENT_PARTICIPATION_ROLE.OTHER_INCIDENT_RESPONDER,
|
|
1388
1389
|
INCIDENT_PARTICIPATION_ROLE.RESPONDING_OFFICER,
|
|
1390
|
+
INCIDENT_PARTICIPATION_ROLE.LEGAL_PROFESSIONAL,
|
|
1389
1391
|
INCIDENT_PARTICIPATION_ROLE.UNKNOWN,
|
|
1390
1392
|
INCIDENT_PARTICIPATION_ROLE.ANONYMOUS,
|
|
1391
1393
|
INCIDENT_PARTICIPATION_ROLE.DATA_NOT_COLLECTED
|
|
@@ -1402,6 +1404,7 @@ var INCIDENT_PARTICIPATION_ROLE_LABELS = {
|
|
|
1402
1404
|
[INCIDENT_PARTICIPATION_ROLE.DATA_ENTRY]: "Data Entry / Editor",
|
|
1403
1405
|
[INCIDENT_PARTICIPATION_ROLE.OTHER_INCIDENT_RESPONDER]: "VSP or Other Incident Responder",
|
|
1404
1406
|
[INCIDENT_PARTICIPATION_ROLE.RESPONDING_OFFICER]: "LE Responding Officer",
|
|
1407
|
+
[INCIDENT_PARTICIPATION_ROLE.LEGAL_PROFESSIONAL]: "Legal Professional",
|
|
1405
1408
|
[INCIDENT_PARTICIPATION_ROLE.UNKNOWN]: "Unknown",
|
|
1406
1409
|
[INCIDENT_PARTICIPATION_ROLE.ANONYMOUS]: "Anonymous",
|
|
1407
1410
|
[INCIDENT_PARTICIPATION_ROLE.DATA_NOT_COLLECTED]: "Not Collected"
|
|
@@ -1419,7 +1422,8 @@ var PARTICIPATION_ROLE_CATEGORIES = {
|
|
|
1419
1422
|
],
|
|
1420
1423
|
SYSTEM_PROFESSIONAL: [
|
|
1421
1424
|
INCIDENT_PARTICIPATION_ROLE.SERVICE_PROVIDER_STAFF,
|
|
1422
|
-
INCIDENT_PARTICIPATION_ROLE.MEDICAL_PROVIDER_STAFF
|
|
1425
|
+
INCIDENT_PARTICIPATION_ROLE.MEDICAL_PROVIDER_STAFF,
|
|
1426
|
+
INCIDENT_PARTICIPATION_ROLE.LEGAL_PROFESSIONAL
|
|
1423
1427
|
]
|
|
1424
1428
|
};
|
|
1425
1429
|
var CALLER_IS_VICTIM_ROLES = [
|
|
@@ -7189,7 +7193,8 @@ var IncidentParticipationRoleKeys = {
|
|
|
7189
7193
|
medical_provider_staff: "069-004-002-000-000-000-000",
|
|
7190
7194
|
data_entry: "069-004-003-000-000-000-000",
|
|
7191
7195
|
other_incident_responder: "069-004-004-000-000-000-000",
|
|
7192
|
-
responding_officer: "069-004-005-000-000-000-000"
|
|
7196
|
+
responding_officer: "069-004-005-000-000-000-000",
|
|
7197
|
+
legal_professional: "069-004-006-000-000-000-000"
|
|
7193
7198
|
};
|
|
7194
7199
|
var IncidentInvolvementRoleKeys = {
|
|
7195
7200
|
missingness_root: "130-000-000-000-000-000-000",
|
|
@@ -9570,12 +9575,7 @@ var AssertionDomainKeys = {
|
|
|
9570
9575
|
facilitator_entity_type: "159-064-000-000-000-000-000",
|
|
9571
9576
|
child_profile: "159-065-000-000-000-000-000",
|
|
9572
9577
|
signal_identification: "159-066-000-000-000-000-000",
|
|
9573
|
-
|
|
9574
|
-
screened: "159-066-002-000-000-000-000",
|
|
9575
|
-
at_risk: "159-066-003-000-000-000-000",
|
|
9576
|
-
assessed: "159-066-004-000-000-000-000",
|
|
9577
|
-
investigative_legal: "159-067-000-000-000-000-000",
|
|
9578
|
-
determined: "159-067-001-000-000-000-000"
|
|
9578
|
+
investigative_legal: "159-067-000-000-000-000-000"
|
|
9579
9579
|
};
|
|
9580
9580
|
var ActivityTypeKeys = {
|
|
9581
9581
|
missingness_root: "965-000-000-000-000-000-000",
|
|
@@ -10226,6 +10226,17 @@ var CoreIndicatorKeys = {
|
|
|
10226
10226
|
trauma_perpetrator_is_current_manager: "136-215-000-000-000-000-000",
|
|
10227
10227
|
active_protective_order: "136-216-000-000-000-000-000"
|
|
10228
10228
|
};
|
|
10229
|
+
var RiskIdentificationMilestoneKeys = {
|
|
10230
|
+
missingness_root: "267-000-000-000-000-000-000",
|
|
10231
|
+
unknown: "267-000-000-000-000-000-001",
|
|
10232
|
+
anonymous: "267-000-000-000-000-000-002",
|
|
10233
|
+
data_not_collected: "267-000-000-000-000-000-003",
|
|
10234
|
+
on_radar: "267-001-000-000-000-000-000",
|
|
10235
|
+
screened: "267-002-000-000-000-000-000",
|
|
10236
|
+
at_risk: "267-003-000-000-000-000-000",
|
|
10237
|
+
assessed: "267-004-000-000-000-000-000",
|
|
10238
|
+
determined: "267-005-000-000-000-000-000"
|
|
10239
|
+
};
|
|
10229
10240
|
var RiskSeverityBandKeys = {
|
|
10230
10241
|
missingness_root: "238-000-000-000-000-000-000",
|
|
10231
10242
|
unknown: "238-000-000-000-000-000-001",
|
|
@@ -14023,7 +14034,8 @@ var incidentParticipationRoles_v1_0_0_default = {
|
|
|
14023
14034
|
"069-004-002-000-000-000-000",
|
|
14024
14035
|
"069-004-003-000-000-000-000",
|
|
14025
14036
|
"069-004-004-000-000-000-000",
|
|
14026
|
-
"069-004-005-000-000-000-000"
|
|
14037
|
+
"069-004-005-000-000-000-000",
|
|
14038
|
+
"069-004-006-000-000-000-000"
|
|
14027
14039
|
],
|
|
14028
14040
|
definition: "Group of participation roles identifying system-side professionals involved in the incident."
|
|
14029
14041
|
},
|
|
@@ -14071,6 +14083,15 @@ var incidentParticipationRoles_v1_0_0_default = {
|
|
|
14071
14083
|
parentCode: "069-004-000-000-000-000-000",
|
|
14072
14084
|
childCodes: [],
|
|
14073
14085
|
definition: "A participant acting as a law-enforcement responding officer on the incident (patrol officer, detective, or equivalent sworn personnel)."
|
|
14086
|
+
},
|
|
14087
|
+
{
|
|
14088
|
+
code: "069-004-006-000-000-000-000",
|
|
14089
|
+
key: "legal_professional",
|
|
14090
|
+
title: "Legal professional",
|
|
14091
|
+
selectable: true,
|
|
14092
|
+
parentCode: "069-004-000-000-000-000-000",
|
|
14093
|
+
childCodes: [],
|
|
14094
|
+
definition: "An attorney or other legal professional (e.g., legal advocate, paralegal) acting in a legal capacity in relation to the incident."
|
|
14074
14095
|
}
|
|
14075
14096
|
]
|
|
14076
14097
|
};
|
|
@@ -42450,6 +42471,117 @@ var riskSeverityBand_v1_0_0_default = {
|
|
|
42450
42471
|
]
|
|
42451
42472
|
};
|
|
42452
42473
|
|
|
42474
|
+
// src/cvcs/riskIdentificationMilestone.v1.0.0.json
|
|
42475
|
+
var riskIdentificationMilestone_v1_0_0_default = {
|
|
42476
|
+
domain: "risk_identification_milestone",
|
|
42477
|
+
name: "Core Risk Identification Milestone (CVC-267)",
|
|
42478
|
+
version: "1.0.0",
|
|
42479
|
+
_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`.",
|
|
42480
|
+
_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)",
|
|
42481
|
+
levels: {
|
|
42482
|
+
"0": "Unknown or Missing",
|
|
42483
|
+
"1": "Identification funnel rung"
|
|
42484
|
+
},
|
|
42485
|
+
entries: [
|
|
42486
|
+
{
|
|
42487
|
+
code: "267-000-000-000-000-000-000",
|
|
42488
|
+
key: "missingness_root",
|
|
42489
|
+
title: "Unknown, Redacted, or Missing",
|
|
42490
|
+
selectable: false,
|
|
42491
|
+
parentCode: null,
|
|
42492
|
+
childCodes: [
|
|
42493
|
+
"267-000-000-000-000-000-001",
|
|
42494
|
+
"267-000-000-000-000-000-002",
|
|
42495
|
+
"267-000-000-000-000-000-003"
|
|
42496
|
+
],
|
|
42497
|
+
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."
|
|
42498
|
+
},
|
|
42499
|
+
{
|
|
42500
|
+
code: "267-000-000-000-000-000-001",
|
|
42501
|
+
key: "unknown",
|
|
42502
|
+
title: "Unknown",
|
|
42503
|
+
selectable: true,
|
|
42504
|
+
parentCode: "267-000-000-000-000-000-000",
|
|
42505
|
+
childCodes: [],
|
|
42506
|
+
canonicalCode: "UNK",
|
|
42507
|
+
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."
|
|
42508
|
+
},
|
|
42509
|
+
{
|
|
42510
|
+
code: "267-000-000-000-000-000-002",
|
|
42511
|
+
key: "anonymous",
|
|
42512
|
+
title: "Anonymous / declined to answer",
|
|
42513
|
+
selectable: true,
|
|
42514
|
+
parentCode: "267-000-000-000-000-000-000",
|
|
42515
|
+
childCodes: [],
|
|
42516
|
+
definition: "Value is intentionally withheld or redacted. Combines declined-to-answer and redacted/anonymous semantics under the workspace standard ANON sentinel."
|
|
42517
|
+
},
|
|
42518
|
+
{
|
|
42519
|
+
code: "267-000-000-000-000-000-003",
|
|
42520
|
+
key: "data_not_collected",
|
|
42521
|
+
title: "Data not collected",
|
|
42522
|
+
selectable: true,
|
|
42523
|
+
parentCode: "267-000-000-000-000-000-000",
|
|
42524
|
+
childCodes: [],
|
|
42525
|
+
definition: "No attempt was made to collect the value. System-only sentinel per GLOBAL_DESIGN_RULES."
|
|
42526
|
+
},
|
|
42527
|
+
{
|
|
42528
|
+
code: "267-001-000-000-000-000-000",
|
|
42529
|
+
key: "on_radar",
|
|
42530
|
+
title: "On radar",
|
|
42531
|
+
selectable: true,
|
|
42532
|
+
parentCode: null,
|
|
42533
|
+
childCodes: [],
|
|
42534
|
+
ordinal: 1,
|
|
42535
|
+
assertionDomain: "signal_identification",
|
|
42536
|
+
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`."
|
|
42537
|
+
},
|
|
42538
|
+
{
|
|
42539
|
+
code: "267-002-000-000-000-000-000",
|
|
42540
|
+
key: "screened",
|
|
42541
|
+
title: "Screened",
|
|
42542
|
+
selectable: true,
|
|
42543
|
+
parentCode: null,
|
|
42544
|
+
childCodes: [],
|
|
42545
|
+
ordinal: 2,
|
|
42546
|
+
assertionDomain: "signal_identification",
|
|
42547
|
+
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`."
|
|
42548
|
+
},
|
|
42549
|
+
{
|
|
42550
|
+
code: "267-003-000-000-000-000-000",
|
|
42551
|
+
key: "at_risk",
|
|
42552
|
+
title: "At risk",
|
|
42553
|
+
selectable: true,
|
|
42554
|
+
parentCode: null,
|
|
42555
|
+
childCodes: [],
|
|
42556
|
+
ordinal: 3,
|
|
42557
|
+
assertionDomain: "signal_identification",
|
|
42558
|
+
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`."
|
|
42559
|
+
},
|
|
42560
|
+
{
|
|
42561
|
+
code: "267-004-000-000-000-000-000",
|
|
42562
|
+
key: "assessed",
|
|
42563
|
+
title: "Assessed",
|
|
42564
|
+
selectable: true,
|
|
42565
|
+
parentCode: null,
|
|
42566
|
+
childCodes: [],
|
|
42567
|
+
ordinal: 4,
|
|
42568
|
+
assertionDomain: "signal_identification",
|
|
42569
|
+
definition: "Rung 4. A full assessment was completed. Stored `assertion_domain`: `signal_identification`."
|
|
42570
|
+
},
|
|
42571
|
+
{
|
|
42572
|
+
code: "267-005-000-000-000-000-000",
|
|
42573
|
+
key: "determined",
|
|
42574
|
+
title: "Determined",
|
|
42575
|
+
selectable: true,
|
|
42576
|
+
parentCode: null,
|
|
42577
|
+
childCodes: [],
|
|
42578
|
+
ordinal: 5,
|
|
42579
|
+
assertionDomain: "investigative_legal",
|
|
42580
|
+
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."
|
|
42581
|
+
}
|
|
42582
|
+
]
|
|
42583
|
+
};
|
|
42584
|
+
|
|
42453
42585
|
// src/cvcs/adminRoles.v1.0.0.json
|
|
42454
42586
|
var adminRoles_v1_0_0_default = {
|
|
42455
42587
|
domain: "admin_roles",
|
|
@@ -52898,12 +53030,11 @@ var assertionDomain_v1_1_0_default = {
|
|
|
52898
53030
|
domain: "assertion_domain",
|
|
52899
53031
|
name: "Assertion Domain (CVC-159)",
|
|
52900
53032
|
version: "2.0.0",
|
|
52901
|
-
_status: "CANONICAL \u2014 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) \u2014 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 \u2014 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
|
|
53033
|
+
_status: "CANONICAL \u2014 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) \u2014 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 \u2014 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.",
|
|
52902
53034
|
_source: "htilabstech/prototype@a596eb9 Final CVCs/Assertion Contract/core - assertion_domain.md (CVC-159) + 17 core_assertion_domain_extensions_*.yaml",
|
|
52903
53035
|
levels: {
|
|
52904
53036
|
"0": "Unknown or Missing",
|
|
52905
|
-
"1": "CAR assertion domain"
|
|
52906
|
-
"2": "CAR assertion value (the vocabulary the domain's assertion_value_code resolves against)"
|
|
53037
|
+
"1": "CAR assertion domain"
|
|
52907
53038
|
},
|
|
52908
53039
|
entries: [
|
|
52909
53040
|
{
|
|
@@ -53528,12 +53659,7 @@ var assertionDomain_v1_1_0_default = {
|
|
|
53528
53659
|
title: "Signal / Identification",
|
|
53529
53660
|
selectable: true,
|
|
53530
53661
|
parentCode: null,
|
|
53531
|
-
childCodes: [
|
|
53532
|
-
"159-066-001-000-000-000-000",
|
|
53533
|
-
"159-066-002-000-000-000-000",
|
|
53534
|
-
"159-066-003-000-000-000-000",
|
|
53535
|
-
"159-066-004-000-000-000-000"
|
|
53536
|
-
],
|
|
53662
|
+
childCodes: [],
|
|
53537
53663
|
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."
|
|
53538
53664
|
},
|
|
53539
53665
|
{
|
|
@@ -53542,55 +53668,8 @@ var assertionDomain_v1_1_0_default = {
|
|
|
53542
53668
|
title: "Investigative / Legal",
|
|
53543
53669
|
selectable: true,
|
|
53544
53670
|
parentCode: null,
|
|
53545
|
-
childCodes: [
|
|
53546
|
-
"159-067-001-000-000-000-000"
|
|
53547
|
-
],
|
|
53548
|
-
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."
|
|
53549
|
-
},
|
|
53550
|
-
{
|
|
53551
|
-
code: "159-066-001-000-000-000-000",
|
|
53552
|
-
key: "on_radar",
|
|
53553
|
-
title: "On radar",
|
|
53554
|
-
selectable: true,
|
|
53555
|
-
parentCode: "159-066-000-000-000-000-000",
|
|
53556
|
-
childCodes: [],
|
|
53557
|
-
definition: "Rung 1 of the identification funnel. The subject is known to the system at all. EVERY new person record counts as on_radar, with the origin kind carried on the derived milestone row (ruling 2026-08-20, confirmed x3)."
|
|
53558
|
-
},
|
|
53559
|
-
{
|
|
53560
|
-
code: "159-066-002-000-000-000-000",
|
|
53561
|
-
key: "screened",
|
|
53562
|
-
title: "Screened",
|
|
53563
|
-
selectable: true,
|
|
53564
|
-
parentCode: "159-066-000-000-000-000-000",
|
|
53565
|
-
childCodes: [],
|
|
53566
|
-
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)."
|
|
53567
|
-
},
|
|
53568
|
-
{
|
|
53569
|
-
code: "159-066-003-000-000-000-000",
|
|
53570
|
-
key: "at_risk",
|
|
53571
|
-
title: "At risk",
|
|
53572
|
-
selectable: true,
|
|
53573
|
-
parentCode: "159-066-000-000-000-000-000",
|
|
53574
|
-
childCodes: [],
|
|
53575
|
-
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). The band-crossing CAR alone anchors this rung."
|
|
53576
|
-
},
|
|
53577
|
-
{
|
|
53578
|
-
code: "159-066-004-000-000-000-000",
|
|
53579
|
-
key: "assessed",
|
|
53580
|
-
title: "Assessed",
|
|
53581
|
-
selectable: true,
|
|
53582
|
-
parentCode: "159-066-000-000-000-000-000",
|
|
53583
53671
|
childCodes: [],
|
|
53584
|
-
definition: "
|
|
53585
|
-
},
|
|
53586
|
-
{
|
|
53587
|
-
code: "159-067-001-000-000-000-000",
|
|
53588
|
-
key: "determined",
|
|
53589
|
-
title: "Determined",
|
|
53590
|
-
selectable: true,
|
|
53591
|
-
parentCode: "159-067-000-000-000-000-000",
|
|
53592
|
-
childCodes: [],
|
|
53593
|
-
definition: "Rung 5 of the identification funnel, stored under `investigative_legal` because CVC-267 TRAFFICKING_STATUS carries that domain. DOCUMENTED under `signal_identification` as well (filed-under-both ruling 2026-08-29) without changing what is stored -- CVC-159's one-assertion-one-domain rule keeps the stored domain single. A NO-INDICATION determination still counts: the rung measures reaching a conclusion in a safe setting, not which conclusion (ruling 2026-08-20, confirmed x3). 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."
|
|
53672
|
+
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."
|
|
53594
53673
|
}
|
|
53595
53674
|
]
|
|
53596
53675
|
};
|
|
@@ -55140,6 +55219,7 @@ export {
|
|
|
55140
55219
|
RelationshipTiesKeys,
|
|
55141
55220
|
ReturnedToAbuserStatusKeys,
|
|
55142
55221
|
RiskCategoryKeys,
|
|
55222
|
+
RiskIdentificationMilestoneKeys,
|
|
55143
55223
|
RiskSeverityBandKeys,
|
|
55144
55224
|
RoiMethodKeys,
|
|
55145
55225
|
RoiScopeKeys,
|
|
@@ -55392,6 +55472,7 @@ export {
|
|
|
55392
55472
|
resolveRegistryWithInheritance,
|
|
55393
55473
|
returnedToAbuserStatus_v1_0_0_default as returnedToAbuserStatusSot,
|
|
55394
55474
|
riskCategory_v1_0_0_default as riskCategorySot,
|
|
55475
|
+
riskIdentificationMilestone_v1_0_0_default as riskIdentificationMilestoneSot,
|
|
55395
55476
|
riskSeverityBand_v1_0_0_default as riskSeverityBandSot,
|
|
55396
55477
|
roiMethod_v1_0_0_default as roiMethodSot,
|
|
55397
55478
|
roiScope_v1_0_0_default as roiScopeSot,
|