@htilabs/platform-common-models 0.12.0 → 0.12.2
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/config/index.cjs +0 -81
- package/dist/config/index.cjs.map +1 -1
- package/dist/config/index.d.cts +4 -79
- package/dist/config/index.d.ts +4 -79
- package/dist/config/index.js +1 -79
- package/dist/config/index.js.map +1 -1
- package/dist/constants/index.cjs +18 -2
- 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 +18 -2
- package/dist/constants/index.js.map +1 -1
- package/dist/cvc-Cp4uWnAa.d.cts +298 -0
- package/dist/cvc-Cp4uWnAa.d.ts +298 -0
- package/dist/{cvcEntry-BCj1OWqL.d.cts → cvcEntry-ctHTp2df.d.cts} +44 -44
- package/dist/{cvcEntry-BCj1OWqL.d.ts → cvcEntry-ctHTp2df.d.ts} +44 -44
- package/dist/cvcs/index.cjs +8065 -1384
- package/dist/cvcs/index.cjs.map +1 -1
- package/dist/cvcs/index.d.cts +15287 -8079
- package/dist/cvcs/index.d.ts +15287 -8079
- package/dist/cvcs/index.js +8052 -1384
- package/dist/cvcs/index.js.map +1 -1
- package/dist/enums/index.cjs +4573 -0
- package/dist/enums/index.cjs.map +1 -0
- package/dist/enums/index.d.cts +5277 -0
- package/dist/enums/index.d.ts +5277 -0
- package/dist/enums/index.js +4369 -0
- package/dist/enums/index.js.map +1 -0
- package/dist/{index-I-DiX9eQ.d.ts → index-4DiJrn7y.d.ts} +1 -1
- package/dist/{index-CoVr1jIV.d.cts → index-qreOzXYS.d.cts} +1 -1
- package/dist/index.cjs +8616 -1389
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +7 -4700
- package/dist/index.d.ts +7 -4700
- package/dist/index.js +8590 -1389
- 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/mongo/index.cjs +0 -1
- package/dist/mongo/index.cjs.map +1 -1
- package/dist/mongo/index.js +1 -2
- package/dist/mongo/index.js.map +1 -1
- package/dist/{platform-auth-v53r3BhN.d.cts → platform-auth-Dv5fu0Fh.d.cts} +5 -4
- package/dist/{platform-auth-v53r3BhN.d.ts → platform-auth-Dv5fu0Fh.d.ts} +5 -4
- package/dist/schemas/index.cjs +5 -1
- package/dist/schemas/index.cjs.map +1 -1
- package/dist/schemas/index.d.cts +35 -35
- package/dist/schemas/index.d.ts +35 -35
- 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/dist/validation/index.cjs +58 -0
- package/dist/validation/index.cjs.map +1 -1
- package/dist/validation/index.d.cts +82 -283
- package/dist/validation/index.d.ts +82 -283
- package/dist/validation/index.js +57 -0
- package/dist/validation/index.js.map +1 -1
- package/package.json +32 -22
- package/src/__sot__/README.md +36 -1
- package/src/__sot__/coreIndicatorFields.ts +331 -0
- package/src/__sot__/coreIndicators.pin.json +1936 -2
- package/src/__sot__/cvcIndex.pin.json +8 -4
- package/src/__tests__/__snapshots__/cvc-sot.snap +45 -13
- package/src/__tests__/core-information-scope-invariant.test.ts +134 -0
- package/src/__tests__/cvc-136-scoring-invariant.test.ts +8 -3
- package/src/__tests__/cvc-181-182-country-parity.test.ts +163 -0
- package/src/__tests__/cvc-drift-gate.test.ts +463 -12
- package/src/__tests__/cvc-sot-snapshot.test.ts +81 -11
- package/src/__tests__/cvc-status-parser.test.ts +150 -0
- package/src/__tests__/cvc-structural.test.ts +16 -0
- package/src/__tests__/runtime-contract-validator.test.ts +1 -325
- package/src/__tests__/share-response-reason-invariant.test.ts +167 -0
- package/src/config/index.ts +4 -189
- package/src/constants/ic.ts +120 -3
- package/src/cvcs/assertionDomain.v1.1.0.json +19 -1
- package/src/cvcs/assertionStatus.v1.0.0.json +80 -0
- package/src/cvcs/carCorrectionReason.v1.0.0.json +89 -0
- package/src/cvcs/caseShareState.v1.0.0.json +62 -0
- package/src/cvcs/coreIndicators.v1.0.0.json +83 -5
- package/src/cvcs/coreInformationScope.v1.0.0.json +1165 -0
- package/src/cvcs/countries.v1.0.0.json +3077 -0
- package/src/cvcs/createdBySystem.v1.0.0.json +89 -0
- package/src/cvcs/criminalOrgCategory.v1.0.0.json +116 -0
- package/src/cvcs/determinationHelperCategories.v1.0.0.json +1166 -0
- package/src/cvcs/incidentParticipationRoles.v1.0.0.json +11 -1
- package/src/cvcs/index.ts +36 -0
- package/src/cvcs/minorAdultStatus.v1.0.0.json +80 -0
- package/src/cvcs/personRelationships.v1.0.0.json +67 -2
- package/src/cvcs/referralOrigin.v1.0.0.json +26 -0
- package/src/cvcs/relationshipConcern.v1.0.0.json +28 -19
- package/src/cvcs/riskIdentificationMilestone.v1.0.0.json +109 -0
- package/src/cvcs/sessionTemplate.v1.0.0.json +22 -0
- package/src/cvcs/sharePurpose.v1.0.0.json +80 -12
- package/src/cvcs/shareResponseReason.v1.0.0.json +220 -0
- package/src/cvcs/subjectType.v1.0.0.json +80 -0
- package/src/generated/cvc-enums.ts +628 -20
- package/src/validation/cvcStatus.ts +209 -0
- package/src/validation/index.ts +1 -0
|
@@ -149,7 +149,8 @@
|
|
|
149
149
|
"069-004-002-000-000-000-000",
|
|
150
150
|
"069-004-003-000-000-000-000",
|
|
151
151
|
"069-004-004-000-000-000-000",
|
|
152
|
-
"069-004-005-000-000-000-000"
|
|
152
|
+
"069-004-005-000-000-000-000",
|
|
153
|
+
"069-004-006-000-000-000-000"
|
|
153
154
|
],
|
|
154
155
|
"definition": "Group of participation roles identifying system-side professionals involved in the incident."
|
|
155
156
|
},
|
|
@@ -197,6 +198,15 @@
|
|
|
197
198
|
"parentCode": "069-004-000-000-000-000-000",
|
|
198
199
|
"childCodes": [],
|
|
199
200
|
"definition": "A participant acting as a law-enforcement responding officer on the incident (patrol officer, detective, or equivalent sworn personnel)."
|
|
201
|
+
},
|
|
202
|
+
{
|
|
203
|
+
"code": "069-004-006-000-000-000-000",
|
|
204
|
+
"key": "legal_professional",
|
|
205
|
+
"title": "Legal professional",
|
|
206
|
+
"selectable": true,
|
|
207
|
+
"parentCode": "069-004-000-000-000-000-000",
|
|
208
|
+
"childCodes": [],
|
|
209
|
+
"definition": "An attorney or other legal professional (e.g., legal advocate, paralegal) acting in a legal capacity in relation to the incident."
|
|
200
210
|
}
|
|
201
211
|
]
|
|
202
212
|
}
|
package/src/cvcs/index.ts
CHANGED
|
@@ -44,6 +44,11 @@ import contactSafetyStatusSot from "./contactSafetyStatus.v1.0.0.json" with { ty
|
|
|
44
44
|
import highestEducationLevelCompletedSot from "./highestEducationLevelCompleted.v1.0.0.json" with { type: "json" };
|
|
45
45
|
import preferredContactMethodSot from "./preferredContactMethod.v1.0.0.json" with { type: "json" };
|
|
46
46
|
import sharePurposeSot from "./sharePurpose.v1.0.0.json" with { type: "json" };
|
|
47
|
+
import referralOriginSot from "./referralOrigin.v1.0.0.json" with { type: "json" };
|
|
48
|
+
import caseShareStateSot from "./caseShareState.v1.0.0.json" with { type: "json" };
|
|
49
|
+
// CVC-306 — structured reasons for responding to an inbound case share. Generated
|
|
50
|
+
// from prototype canon by scripts/gen-share-response-reason.py; re-run, don't hand-edit.
|
|
51
|
+
import shareResponseReasonSot from "./shareResponseReason.v1.0.0.json" with { type: "json" };
|
|
47
52
|
import facilitatorEntityTypeSot from "./facilitatorEntityType.v1.0.0.json" with { type: "json" };
|
|
48
53
|
import facilitatorSubroleSot from "./facilitatorSubrole.v1.0.0.json" with { type: "json" };
|
|
49
54
|
import maritalStatusLegalSot from "./maritalStatusLegal.v1.0.0.json" with { type: "json" };
|
|
@@ -156,12 +161,14 @@ import romanticRelationshipChangeTypeSot from "./romanticRelationshipChangeType.
|
|
|
156
161
|
import riskCategorySot from "./riskCategory.v1.0.0.json" with { type: "json" };
|
|
157
162
|
import coreFunctionsSot from "./coreFunctions.v1.0.0.json" with { type: "json" };
|
|
158
163
|
import needsAssessmentChangeTypeSot from "./needsAssessmentChangeType.v1.0.0.json" with { type: "json" };
|
|
164
|
+
import coreInformationScopeSot from "./coreInformationScope.v1.0.0.json" with { type: "json" };
|
|
159
165
|
import roiScopeSot from "./roiScope.v1.0.0.json" with { type: "json" };
|
|
160
166
|
import roiStatusSot from "./roiStatus.v1.0.0.json" with { type: "json" };
|
|
161
167
|
import coreReferralOutcomeSot from "./coreReferralOutcome.v1.0.0.json" with { type: "json" };
|
|
162
168
|
import coreIndicatorsSot from "./coreIndicators.v1.0.0.json" with { type: "json" };
|
|
163
169
|
import coreDhStateSot from "./coreDhState.v1.0.0.json" with { type: "json" };
|
|
164
170
|
import riskSeverityBandSot from "./riskSeverityBand.v1.0.0.json" with { type: "json" };
|
|
171
|
+
import riskIdentificationMilestoneSot from "./riskIdentificationMilestone.v1.0.0.json" with { type: "json" };
|
|
165
172
|
import adminRolesSot from "./adminRoles.v1.0.0.json" with { type: "json" };
|
|
166
173
|
import userRolesSot from "./userRoles.v1.0.0.json" with { type: "json" };
|
|
167
174
|
import hmisCurrentLivingSituationSot from "./hmisCurrentLivingSituation.v1.0.0.json" with { type: "json" };
|
|
@@ -177,6 +184,8 @@ import sessionTemplateSot from "./sessionTemplate.v1.0.0.json" with { type: "jso
|
|
|
177
184
|
import serviceDeliveryChannelSot from "./serviceDeliveryChannel.v1.0.0.json" with { type: "json" };
|
|
178
185
|
import whyNotsSot from "./whyNots.v1.0.0.json" with { type: "json" };
|
|
179
186
|
import citizenshipSot from "./citizenship.v1.0.0.json" with { type: "json" };
|
|
187
|
+
import countriesSot from "./countries.v1.0.0.json" with { type: "json" };
|
|
188
|
+
import determinationHelperCategoriesSot from "./determinationHelperCategories.v1.0.0.json" with { type: "json" };
|
|
180
189
|
import traffickingRelevantRoleSot from "./traffickingRelevantRole.v1.0.0.json" with { type: "json" };
|
|
181
190
|
// Domains that were never exported from this barrel (found by the CVC drift gate).
|
|
182
191
|
import activityTypeSot from "./activityType.v1.0.0.json" with { type: "json" };
|
|
@@ -187,6 +196,13 @@ import radiusBucketSot from "./radiusBucket.v1.0.0.json" with { type: "json" };
|
|
|
187
196
|
import roiMethodSot from "./roiMethod.v1.0.0.json" with { type: "json" };
|
|
188
197
|
import sessionNoteVisibilitySot from "./sessionNoteVisibility.v1.0.0.json" with { type: "json" };
|
|
189
198
|
import suggestionSourceSot from "./suggestionSource.v1.0.0.json" with { type: "json" };
|
|
199
|
+
// GDR §10.1 CAR-contract vocabularies (provisional 900-block; PAVE @pave/domain
|
|
200
|
+
// verbatim; bead pv-pgdr-cvc-source-gdr-10-1-bulk-publish).
|
|
201
|
+
import assertionStatusSot from "./assertionStatus.v1.0.0.json" with { type: "json" };
|
|
202
|
+
import carCorrectionReasonSot from "./carCorrectionReason.v1.0.0.json" with { type: "json" };
|
|
203
|
+
import createdBySystemSot from "./createdBySystem.v1.0.0.json" with { type: "json" };
|
|
204
|
+
import subjectTypeSot from "./subjectType.v1.0.0.json" with { type: "json" };
|
|
205
|
+
import minorAdultStatusSot from "./minorAdultStatus.v1.0.0.json" with { type: "json" };
|
|
190
206
|
// Trunk-only domain (CVC-67) authored on `kl-develop` and never seen by the
|
|
191
207
|
// canonical 0.8.13 line. It shipped as an orphan JSON — the file existed but
|
|
192
208
|
// was never wired into this barrel, so nothing could import it. Wired in here
|
|
@@ -194,6 +210,13 @@ import suggestionSourceSot from "./suggestionSource.v1.0.0.json" with { type: "j
|
|
|
194
210
|
// across the merged tree. Coexists with the `CVC_67_HMIS_SEX` constants in
|
|
195
211
|
// `../constants/ic.ts`; the JSON is the SOT, the constants are the legacy view.
|
|
196
212
|
import hmisSexSot from "./hmisSex.v1.0.0.json" with { type: "json" };
|
|
213
|
+
// Domain authored in PR #142 (0.8.15) alongside the codegen manifest entry in
|
|
214
|
+
// scripts/codegen-cvc-enums.ts, but never wired into this barrel — the SOT
|
|
215
|
+
// JSON shipped and `src/generated/cvc-enums.ts` regenerated correctly (it
|
|
216
|
+
// reads `src/cvcs/*.json` directly), but this file does not, so the export
|
|
217
|
+
// never reached the compiled `dist/cvcs/`. Wired in here so downstream
|
|
218
|
+
// consumers that derive their key maps from `./cvcs` (e.g. PAVE) can see it.
|
|
219
|
+
import criminalOrgCategorySot from "./criminalOrgCategory.v1.0.0.json" with { type: "json" };
|
|
197
220
|
|
|
198
221
|
export {
|
|
199
222
|
serviceCategoriesSot,
|
|
@@ -221,6 +244,9 @@ export {
|
|
|
221
244
|
highestEducationLevelCompletedSot,
|
|
222
245
|
preferredContactMethodSot,
|
|
223
246
|
sharePurposeSot,
|
|
247
|
+
referralOriginSot,
|
|
248
|
+
caseShareStateSot,
|
|
249
|
+
shareResponseReasonSot,
|
|
224
250
|
facilitatorEntityTypeSot,
|
|
225
251
|
facilitatorSubroleSot,
|
|
226
252
|
maritalStatusLegalSot,
|
|
@@ -333,12 +359,14 @@ export {
|
|
|
333
359
|
riskCategorySot,
|
|
334
360
|
coreFunctionsSot,
|
|
335
361
|
needsAssessmentChangeTypeSot,
|
|
362
|
+
coreInformationScopeSot,
|
|
336
363
|
roiScopeSot,
|
|
337
364
|
roiStatusSot,
|
|
338
365
|
coreReferralOutcomeSot,
|
|
339
366
|
coreIndicatorsSot,
|
|
340
367
|
coreDhStateSot,
|
|
341
368
|
riskSeverityBandSot,
|
|
369
|
+
riskIdentificationMilestoneSot,
|
|
342
370
|
adminRolesSot,
|
|
343
371
|
userRolesSot,
|
|
344
372
|
hmisCurrentLivingSituationSot,
|
|
@@ -354,6 +382,8 @@ export {
|
|
|
354
382
|
serviceDeliveryChannelSot,
|
|
355
383
|
whyNotsSot,
|
|
356
384
|
citizenshipSot,
|
|
385
|
+
countriesSot,
|
|
386
|
+
determinationHelperCategoriesSot,
|
|
357
387
|
traffickingRelevantRoleSot,
|
|
358
388
|
activityTypeSot,
|
|
359
389
|
assertionDomainSot,
|
|
@@ -363,5 +393,11 @@ export {
|
|
|
363
393
|
roiMethodSot,
|
|
364
394
|
sessionNoteVisibilitySot,
|
|
365
395
|
suggestionSourceSot,
|
|
396
|
+
assertionStatusSot,
|
|
397
|
+
carCorrectionReasonSot,
|
|
398
|
+
createdBySystemSot,
|
|
399
|
+
subjectTypeSot,
|
|
400
|
+
minorAdultStatusSot,
|
|
366
401
|
hmisSexSot,
|
|
402
|
+
criminalOrgCategorySot,
|
|
367
403
|
};
|
|
@@ -0,0 +1,80 @@
|
|
|
1
|
+
{
|
|
2
|
+
"domain": "minor_adult_status",
|
|
3
|
+
"name": "Minor / Adult Status (age band at event)",
|
|
4
|
+
"version": "1.0.0",
|
|
5
|
+
"_status": "PROVISIONAL — GDR §10.1 confirmed-CVC name is `core - minor_adult_status`, and the canonical index DOES number this concept (Final CVCs/CVC_INDEX.md @ a596eb9: CVC-61 `minor_adult_status`) — but the CVC-61 Notion codebook has 0 entries anywhere, and ADR-CVC-0.8.13-canonical-alignment §Deliberately-NOT-authored (NARRATIVE_ONLY) deliberately declined to author at 61 to avoid manufacturing canonical drift. This vocabulary therefore parks in the provisional 900-block; RENUMBER 988 → 61 when the CVC-61 Notion codebook gains substantive entries (and reconcile membership at that point). Substantive values sourced verbatim from the PAVE @pave/domain `AGE_BANDS_AT_EVENT` enum (D10 GDR §10.1 bulk publish, bead pv-pgdr-cvc-source-gdr-10-1-bulk-publish): PAVE's `minor` / `adult` / `indeterminate` stay substantive; PAVE's fourth member `unknown` maps to the canonical missingness `unknown` sentinel (same realignment shape as the ROLE_CONTEXTS 0.7.0 bind), so every PAVE member remains expressible. Distinct from the numeric IC constant MINOR_ADULT_STATUS in constants/ic.ts (IC layer, 1/2/99) — that is a different encoding layer, not a parallel CVC.",
|
|
6
|
+
"_source": "pave-2.0/packages/domain/src/enums.ts AGE_BANDS_AT_EVENT",
|
|
7
|
+
"levels": {
|
|
8
|
+
"0": "Unknown or Missing",
|
|
9
|
+
"1": "Minor / adult status at event"
|
|
10
|
+
},
|
|
11
|
+
"entries": [
|
|
12
|
+
{
|
|
13
|
+
"code": "988-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
|
+
"988-000-000-000-000-000-001",
|
|
20
|
+
"988-000-000-000-000-000-002",
|
|
21
|
+
"988-000-000-000-000-000-003"
|
|
22
|
+
],
|
|
23
|
+
"definition": "Root group for values indicating absent, withheld, or uncollected data."
|
|
24
|
+
},
|
|
25
|
+
{
|
|
26
|
+
"code": "988-000-000-000-000-000-001",
|
|
27
|
+
"key": "unknown",
|
|
28
|
+
"title": "Unknown",
|
|
29
|
+
"selectable": true,
|
|
30
|
+
"parentCode": "988-000-000-000-000-000-000",
|
|
31
|
+
"childCodes": [],
|
|
32
|
+
"definition": "The age band is unknown — not assessed or not recorded (missingness sentinel). Carries PAVE's `unknown` member of AGE_BANDS_AT_EVENT."
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"code": "988-000-000-000-000-000-002",
|
|
36
|
+
"key": "anonymous",
|
|
37
|
+
"title": "Anonymous / declined to answer",
|
|
38
|
+
"selectable": true,
|
|
39
|
+
"parentCode": "988-000-000-000-000-000-000",
|
|
40
|
+
"childCodes": [],
|
|
41
|
+
"definition": "Value is intentionally withheld, declined, or redacted."
|
|
42
|
+
},
|
|
43
|
+
{
|
|
44
|
+
"code": "988-000-000-000-000-000-003",
|
|
45
|
+
"key": "data_not_collected",
|
|
46
|
+
"title": "Data not collected",
|
|
47
|
+
"selectable": true,
|
|
48
|
+
"parentCode": "988-000-000-000-000-000-000",
|
|
49
|
+
"childCodes": [],
|
|
50
|
+
"definition": "No attempt was made to collect the value."
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"code": "988-001-000-000-000-000-000",
|
|
54
|
+
"key": "minor",
|
|
55
|
+
"title": "Minor (under 18)",
|
|
56
|
+
"selectable": true,
|
|
57
|
+
"parentCode": null,
|
|
58
|
+
"childCodes": [],
|
|
59
|
+
"definition": "The subject was under 18 when the asserted event occurred."
|
|
60
|
+
},
|
|
61
|
+
{
|
|
62
|
+
"code": "988-002-000-000-000-000-000",
|
|
63
|
+
"key": "adult",
|
|
64
|
+
"title": "Adult (18+)",
|
|
65
|
+
"selectable": true,
|
|
66
|
+
"parentCode": null,
|
|
67
|
+
"childCodes": [],
|
|
68
|
+
"definition": "The subject was 18 or older when the asserted event occurred."
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"code": "988-003-000-000-000-000-000",
|
|
72
|
+
"key": "indeterminate",
|
|
73
|
+
"title": "Indeterminate",
|
|
74
|
+
"selectable": true,
|
|
75
|
+
"parentCode": null,
|
|
76
|
+
"childCodes": [],
|
|
77
|
+
"definition": "The age band cannot be determined from the available evidence — a positive determination of indeterminacy (e.g. conflicting or insufficient evidence), distinct from the `unknown` missingness sentinel (not assessed / not recorded)."
|
|
78
|
+
}
|
|
79
|
+
]
|
|
80
|
+
}
|
|
@@ -2,6 +2,15 @@
|
|
|
2
2
|
"domain": "person_relationships",
|
|
3
3
|
"name": "Core Person Relationships",
|
|
4
4
|
"version": "1.0.0",
|
|
5
|
+
"_status": {
|
|
6
|
+
"vocabStatus": "canonical",
|
|
7
|
+
"authoredBy": "CVC-126 imported from the Notion codebook (`Final CVCs/Linking & Relationships (IC-13)/core person relationship CVC`, CVC_INDEX.md row `core person relationship CVC` = 126). Engineer-direct, 2026-08-29 (ships in the next release): APPENDS 3 relationship types + 2 directional roles the canonical prototype's relationship picker offers and the Notion-side export does not yet carry. Envelope `version` is deliberately UNCHANGED at 1.0.0: this is a purely additive append with every prior positional code stable, which is the CVC-136 0.8.17 append precedent (`coreIndicators.v1.0.0.json`, +1 code, version held). The renumber precedent (`housingSubsidyTypes`, 233 -> 194) is the one that bumps, because every code there moved.",
|
|
8
|
+
"evidence": "prototype@622410b `HTI-LEADS-PAVE-Thread-prototype.html` L121814-121993 (`REL_CATEGORIES`). At that pin the picker enumerates 33 relationship types across 7 categories; this codebook carried 30. The 3-type delta is exactly `parental_figure_dependent` (Familial / Kin), `intimate_romantic_partner` and `intimate_partner_prior` (Intimate / Partner).",
|
|
9
|
+
"localExtension": "`parental_figure_dependent` (126-001-007) with its 2 directional roles, `intimate_romantic_partner` (126-002-003) and `intimate_partner_prior` (126-002-004) are AUTHORED, not carried — all 5 are flagged `localExtension: true` so reporting can separate them. The canonical HTML flags the two Intimate entries itself: its inline comments at L121850-121885 say each `is not yet in the Notion-side 'core - person relationships' codebook export at 'Final CVCs/Linking & Relationships (IC-13)/'` and name the Crysta-led canonicalization as a queued follow-up (tracker row `RWT-NEW-intimate-partner-prior-canonicalize`). `parental_figure_dependent` carries no such inline note but is absent from this codebook for the same reason and is treated identically. PENDING canonical Notion authoring + steward ratification of titles/definitions. Structural precedent: CVC-47 serviceDeliveryChannel's `group_inperson` / `group_remote` (047-006 / 047-007) and CVC-181 countries' `non_us_unspecified` (181-250) — flagged, codebook-absent leaves appended after the enumerated set. Upstream must adopt or reject all three.",
|
|
10
|
+
"ordinals": "APPENDED, never interleaved. Segment-3 ordinals inside a topic are otherwise alphabetical by key, so alphabetical insertion would have put `parental_figure_dependent` at 126-001-005 and reshuffled `parent_child` / `sibling`. New types are appended at the end of their topic (126-001-007 after `sibling`; 126-002-003 / 126-002-004 after `spouse_partner`) so every previously issued positional code stays stable — the same rule CVC-136 states for its appends. Consumers persist KEYS, not wire codes, so the appends are additive in both directions.",
|
|
11
|
+
"roleStructure": "Unchanged by this append: an ASYMMETRIC type carries 2 level-3 directional role children ordered alphabetically by key (`guardian_dependent` -> `dependent_of` / `guardian_of`); a SYMMETRIC type carries none (`sibling`, `spouse_partner`, `dating_relationship`, ...). `parental_figure_dependent` is asymmetric and so mirrors `guardian_dependent` exactly; `intimate_romantic_partner` and `intimate_partner_prior` are symmetric in the canonical picker (`symmetric: true`) and so carry no role children."
|
|
12
|
+
},
|
|
13
|
+
"_source": "htilabstech/prototype@622410b HTI-LEADS-PAVE-Thread-prototype.html L121814-121993 (`REL_CATEGORIES`) — reference for the 3 appended types only; the 30 pre-existing types remain sourced from the Notion codebook",
|
|
5
14
|
"levels": {
|
|
6
15
|
"0": "Unknown or Missing",
|
|
7
16
|
"1": "Topic",
|
|
@@ -51,7 +60,8 @@
|
|
|
51
60
|
"126-001-003-000-000-000-000",
|
|
52
61
|
"126-001-004-000-000-000-000",
|
|
53
62
|
"126-001-005-000-000-000-000",
|
|
54
|
-
"126-001-006-000-000-000-000"
|
|
63
|
+
"126-001-006-000-000-000-000",
|
|
64
|
+
"126-001-007-000-000-000-000"
|
|
55
65
|
],
|
|
56
66
|
"definition": "Relationships between two people who are related through family or kinship, including immediate and extended family."
|
|
57
67
|
},
|
|
@@ -172,6 +182,39 @@
|
|
|
172
182
|
"childCodes": [],
|
|
173
183
|
"definition": "A relationship between two people who share a sibling relationship."
|
|
174
184
|
},
|
|
185
|
+
{
|
|
186
|
+
"code": "126-001-007-000-000-000-000",
|
|
187
|
+
"key": "parental_figure_dependent",
|
|
188
|
+
"title": "Parental figure / Dependent",
|
|
189
|
+
"selectable": true,
|
|
190
|
+
"parentCode": "126-001-000-000-000-000-000",
|
|
191
|
+
"childCodes": [
|
|
192
|
+
"126-001-007-001-000-000-000",
|
|
193
|
+
"126-001-007-002-000-000-000"
|
|
194
|
+
],
|
|
195
|
+
"definition": "LOCAL EXTENSION (not in canonical CVC-126). A relationship where one person functions as a parental figure to the other: adult-child caretaking is clear, but the biological, adoptive, step, or legal-guardianship basis is unknown or not asserted. DISTINCT from `parent_child` (the parental basis IS known or asserted) and from `guardian_dependent` (legal or functional guardianship is the key fact) — this leaf carries the positive fact that a parental caretaking role exists WITHOUT claiming which basis produces it, which neither of those two can express. Asymmetric: the two directional roles are carried as level-3 children, mirroring `guardian_dependent`.",
|
|
196
|
+
"localExtension": true
|
|
197
|
+
},
|
|
198
|
+
{
|
|
199
|
+
"code": "126-001-007-001-000-000-000",
|
|
200
|
+
"key": "dependent_of_parental_figure",
|
|
201
|
+
"title": "Dependent",
|
|
202
|
+
"selectable": true,
|
|
203
|
+
"parentCode": "126-001-007-000-000-000-000",
|
|
204
|
+
"childCodes": [],
|
|
205
|
+
"definition": "LOCAL EXTENSION (not in canonical CVC-126). Use when the related person is the dependent of the anchor person's parental figure — i.e. the anchor person acts as the parental figure on this link. Distinct key from `dependent_of` (126-001-002-001), which is the guardianship-based role.",
|
|
206
|
+
"localExtension": true
|
|
207
|
+
},
|
|
208
|
+
{
|
|
209
|
+
"code": "126-001-007-002-000-000-000",
|
|
210
|
+
"key": "parental_figure_of",
|
|
211
|
+
"title": "Parental figure",
|
|
212
|
+
"selectable": true,
|
|
213
|
+
"parentCode": "126-001-007-000-000-000-000",
|
|
214
|
+
"childCodes": [],
|
|
215
|
+
"definition": "LOCAL EXTENSION (not in canonical CVC-126). Use when the related person is the parental figure of the anchor person.",
|
|
216
|
+
"localExtension": true
|
|
217
|
+
},
|
|
175
218
|
{
|
|
176
219
|
"code": "126-002-000-000-000-000-000",
|
|
177
220
|
"key": "romantic_partner",
|
|
@@ -180,7 +223,9 @@
|
|
|
180
223
|
"parentCode": null,
|
|
181
224
|
"childCodes": [
|
|
182
225
|
"126-002-001-000-000-000-000",
|
|
183
|
-
"126-002-002-000-000-000-000"
|
|
226
|
+
"126-002-002-000-000-000-000",
|
|
227
|
+
"126-002-003-000-000-000-000",
|
|
228
|
+
"126-002-004-000-000-000-000"
|
|
184
229
|
],
|
|
185
230
|
"definition": "Relationship between two people who are or were in a romantic or intimate partnership."
|
|
186
231
|
},
|
|
@@ -202,6 +247,26 @@
|
|
|
202
247
|
"childCodes": [],
|
|
203
248
|
"definition": "Intimate partner relationship, including spouse, domestic partner, or romantic partner. Legal status and current/former status are modeled elsewhere (e.g., marital_status_legal, relationship_status_current, time_scope)."
|
|
204
249
|
},
|
|
250
|
+
{
|
|
251
|
+
"code": "126-002-003-000-000-000-000",
|
|
252
|
+
"key": "intimate_romantic_partner",
|
|
253
|
+
"title": "Intimate / Romantic Partner",
|
|
254
|
+
"selectable": true,
|
|
255
|
+
"parentCode": "126-002-000-000-000-000-000",
|
|
256
|
+
"childCodes": [],
|
|
257
|
+
"definition": "LOCAL EXTENSION (not in canonical CVC-126). Generic romantic-partner type that stays shape-stable across both marital postures: the legally-married vs. dating distinction is captured on the relationship ROW (`is_current_spouse`, `attributes.ties[] = LEGALLY_MARRIED`) rather than by the relationship type, so a partnership does not have to change type when its legal posture changes. The Households & Relationships \"Romantic Partner\" tile hard-locks to this code. Symmetric — an intimate partnership is mutual — so no directional role children. Prefer `spouse_partner` or `dating_relationship` when the asserted fact IS the marital or dating posture itself. Added upstream 2026-05-05 (H&R Phase 2, TILE_RULES extension).",
|
|
258
|
+
"localExtension": true
|
|
259
|
+
},
|
|
260
|
+
{
|
|
261
|
+
"code": "126-002-004-000-000-000-000",
|
|
262
|
+
"key": "intimate_partner_prior",
|
|
263
|
+
"title": "Former intimate partner",
|
|
264
|
+
"selectable": true,
|
|
265
|
+
"parentCode": "126-002-000-000-000-000-000",
|
|
266
|
+
"childCodes": [],
|
|
267
|
+
"definition": "LOCAL EXTENSION (not in canonical CVC-126). Use when an intimate partnership has ENDED. The \"prior\" semantic stays canonically derivable from the relationship row (`relationship_is_active: false` + `relationship_end`); this leaf exists so the picker and the label resolver recognise the code as an Intimate-category type and render \"Former intimate partner\" instead of falling back to the raw code. For active partnerships use `spouse_partner`, `dating_relationship`, or `intimate_romantic_partner` with the appropriate active/end attributes. Symmetric, so no directional role children. Added upstream 2026-05-26 (RWT-NEW-hector-audit-atomic-fixes Fix B); upstream tracker row `RWT-NEW-intimate-partner-prior-canonicalize` proposes either renaming to `spouse_partner` + scope=prior or promoting this code into the codebook.",
|
|
268
|
+
"localExtension": true
|
|
269
|
+
},
|
|
205
270
|
{
|
|
206
271
|
"code": "126-003-000-000-000-000-000",
|
|
207
272
|
"key": "care_household",
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
{
|
|
2
|
+
"domain": "referral_origin",
|
|
3
|
+
"name": "Core Referral Origin",
|
|
4
|
+
"version": "1.0.0",
|
|
5
|
+
"levels": { "1": "Origin" },
|
|
6
|
+
"entries": [
|
|
7
|
+
{
|
|
8
|
+
"code": "909-001-000-000-000-000-000",
|
|
9
|
+
"key": "internal",
|
|
10
|
+
"title": "Internal",
|
|
11
|
+
"selectable": true,
|
|
12
|
+
"parentCode": null,
|
|
13
|
+
"childCodes": [],
|
|
14
|
+
"definition": "A referral whose sending and receiving parties sit within the same agency or account boundary, so completing it involves no disclosure of client information across an organizational boundary."
|
|
15
|
+
},
|
|
16
|
+
{
|
|
17
|
+
"code": "909-002-000-000-000-000-000",
|
|
18
|
+
"key": "external",
|
|
19
|
+
"title": "External",
|
|
20
|
+
"selectable": true,
|
|
21
|
+
"parentCode": null,
|
|
22
|
+
"childCodes": [],
|
|
23
|
+
"definition": "A referral whose receiving party is a different agency, making acceptance a cross-agency disclosure of client information. Where an implementation cannot positively determine the origin, it must treat the referral as external, so that the stronger disclosure controls apply by default rather than the weaker ones."
|
|
24
|
+
}
|
|
25
|
+
]
|
|
26
|
+
}
|
|
@@ -1,54 +1,63 @@
|
|
|
1
1
|
{
|
|
2
2
|
"domain": "relationship_concern",
|
|
3
|
-
"name": "Core Relationship Concern (PROVISIONAL CVC-
|
|
4
|
-
"version": "1.
|
|
3
|
+
"name": "Core Relationship Concern (PROVISIONAL CVC-991 — pending codebook ratification)",
|
|
4
|
+
"version": "1.1.0",
|
|
5
|
+
"_status": {
|
|
6
|
+
"vocabStatus": "provisional-pending-notion-ratification",
|
|
7
|
+
"authoredBy": "platform-common 0.8.1 (`feature/cvc-author-missing-domains`), originally minted at provisional CVC-231. RENUMBERED 231 -> 991 engineer-direct on 2026-08-29 (ships in the next release).",
|
|
8
|
+
"renumber": "RENUMBERED FROM PROVISIONAL 231 ON CVC-231'S RATIFICATION TO THE DETERMINATION HELPER CATEGORIES, 2026-08-28 (Jevon). 231 was never this vocabulary's number — it was a provisional mint taken from the CANONICAL block (<900) at a time when `CVC_INDEX.md` carried no row for it, which is why this domain sat in the drift gate's `INDEX_ABSENT` list rather than in `CANONICAL_BINDING`. With 231 now ratified to the Determination Helper categories, holding it here would be a SQUAT in the exact sense GATE C describes: a wrong number does not merely mislabel the squatter, it makes the slot look occupied and thereby hides the absence of the domain that owns it (`housing_subsidy_types` on CVC-233 is the precedent that cost us `core-DH_state` entirely). Vacating 231 now, BEFORE the next `cvcIndex` pin refresh publishes the DH row, keeps that failure mode from ever arming. This domain has no canonical number of its own, so it moves to the provisional 900-block — the sanctioned escape hatch — rather than to another canonical number.",
|
|
9
|
+
"numberChoice": "991 = the next number above the highest provisional in use (990 `criminal_org_category`). The 900-block gaps below it are NOT free-for-reuse: 930 is claimed by the open `codebook-bridge/proposals/evidence_tier.v1.0.0.json`, and 964 / 981 are VACATED numbers (`assertion_domain` renumbered 964 -> canonical 159; `risk_band` withdrawn at 981 in favour of canonical CVC-238) which the house has deliberately left as historical gaps rather than recycled — the same stable-ordinal discipline `assertionDomain._status` states for its segment-2 gaps. 991 itself was briefly held by `core_information_scope` on the `feat/cvc-236-information-scope` branch and released within that same PR (f9a71b3, \"number core_information_scope at its canonical 236, not provisional 991\"); it never shipped in any release, so it is clean. Verified collision-free against every `src/cvcs/*.json`, `codebook-bridge/proposals/*.json`, and `cvcIndex.pin.json` (which carries no row for 231, 990, 991 or 992).",
|
|
10
|
+
"consumerImpact": "NONE at the type level. Consumers persist KEYS, not wire codes: PAVE binds this domain as `RELATIONSHIP_CONCERNS_KEYS = keysExceptRoot(RelationshipConcernKeys)` and every downstream `z.enum(...)` / Mongoose enum is over those keys. A repo-wide grep of pave-2.0 finds ZERO occurrences of a `\"231-...\"` positional code; the numeral appears only in prose comments and ADR text. Only the generated map VALUES change (`231-*` -> `991-*`) — the key identifiers and TypeScript types are unchanged. Regenerate `src/generated/cvc-enums.ts` (`npm run codegen:cvc`). No production data exists.",
|
|
11
|
+
"ordinals": "Segment-2 ordinals are preserved verbatim across the renumber (001..007 substantive, 000-000-001/002/003 missingness), so the diff is a pure prefix substitution and stays reviewable.",
|
|
12
|
+
"upstreamReconciliation": "Two things. (1) Notion must author this vocabulary and assign it a canonical number, at which point it renumbers out of the 900-block the way `assertion_domain` (964 -> 159) and `core_information_scope` (991 -> 236) did. (2) The Determination Helper categories now own CVC-231 and are NOT authored in platform-common at all — the same gap-behind-a-squat this renumber exists to expose. Authoring them at 231 is a separate item."
|
|
13
|
+
},
|
|
5
14
|
"levels": {
|
|
6
15
|
"0": "Unknown or Missing",
|
|
7
16
|
"1": "Relationship concern"
|
|
8
17
|
},
|
|
9
18
|
"entries": [
|
|
10
19
|
{
|
|
11
|
-
"code": "
|
|
20
|
+
"code": "991-000-000-000-000-000-000",
|
|
12
21
|
"key": "missingness_root",
|
|
13
22
|
"title": "Unknown, Redacted, or Missing",
|
|
14
23
|
"selectable": false,
|
|
15
24
|
"parentCode": null,
|
|
16
25
|
"childCodes": [
|
|
17
|
-
"
|
|
18
|
-
"
|
|
19
|
-
"
|
|
26
|
+
"991-000-000-000-000-000-001",
|
|
27
|
+
"991-000-000-000-000-000-002",
|
|
28
|
+
"991-000-000-000-000-000-003"
|
|
20
29
|
],
|
|
21
30
|
"definition": "Root group for values indicating absent, withheld, or uncollected data."
|
|
22
31
|
},
|
|
23
32
|
{
|
|
24
|
-
"code": "
|
|
33
|
+
"code": "991-000-000-000-000-000-001",
|
|
25
34
|
"key": "unknown",
|
|
26
35
|
"title": "Unknown",
|
|
27
36
|
"selectable": true,
|
|
28
|
-
"parentCode": "
|
|
37
|
+
"parentCode": "991-000-000-000-000-000-000",
|
|
29
38
|
"childCodes": [],
|
|
30
39
|
"definition": "The relationship concern is unknown or cannot be determined from the available information."
|
|
31
40
|
},
|
|
32
41
|
{
|
|
33
|
-
"code": "
|
|
42
|
+
"code": "991-000-000-000-000-000-002",
|
|
34
43
|
"key": "anonymous",
|
|
35
44
|
"title": "Anonymous / declined to answer",
|
|
36
45
|
"selectable": true,
|
|
37
|
-
"parentCode": "
|
|
46
|
+
"parentCode": "991-000-000-000-000-000-000",
|
|
38
47
|
"childCodes": [],
|
|
39
48
|
"definition": "The relationship concern may be withheld by preference or due to redaction; identity is anonymous or redacted."
|
|
40
49
|
},
|
|
41
50
|
{
|
|
42
|
-
"code": "
|
|
51
|
+
"code": "991-000-000-000-000-000-003",
|
|
43
52
|
"key": "data_not_collected",
|
|
44
53
|
"title": "Data not collected",
|
|
45
54
|
"selectable": true,
|
|
46
|
-
"parentCode": "
|
|
55
|
+
"parentCode": "991-000-000-000-000-000-000",
|
|
47
56
|
"childCodes": [],
|
|
48
57
|
"definition": "No attempt was made to collect the relationship concern."
|
|
49
58
|
},
|
|
50
59
|
{
|
|
51
|
-
"code": "
|
|
60
|
+
"code": "991-001-000-000-000-000-000",
|
|
52
61
|
"key": "appears_controlling",
|
|
53
62
|
"title": "Appears controlling",
|
|
54
63
|
"selectable": true,
|
|
@@ -57,7 +66,7 @@
|
|
|
57
66
|
"definition": "Employer, intimate partner, or family member who appears controlling in relation to the subject."
|
|
58
67
|
},
|
|
59
68
|
{
|
|
60
|
-
"code": "
|
|
69
|
+
"code": "991-002-000-000-000-000-000",
|
|
61
70
|
"key": "is_much_older",
|
|
62
71
|
"title": "Is much older (age-disparate)",
|
|
63
72
|
"selectable": true,
|
|
@@ -66,7 +75,7 @@
|
|
|
66
75
|
"definition": "Significant age disparity in the relationship — a vulnerability signal, especially for youth."
|
|
67
76
|
},
|
|
68
77
|
{
|
|
69
|
-
"code": "
|
|
78
|
+
"code": "991-003-000-000-000-000-000",
|
|
70
79
|
"key": "physically_abusive",
|
|
71
80
|
"title": "Physically abusive",
|
|
72
81
|
"selectable": true,
|
|
@@ -75,7 +84,7 @@
|
|
|
75
84
|
"definition": "Reports of physical harm or abuse from this person toward the subject."
|
|
76
85
|
},
|
|
77
86
|
{
|
|
78
|
-
"code": "
|
|
87
|
+
"code": "991-004-000-000-000-000-000",
|
|
79
88
|
"key": "emotionally_abusive",
|
|
80
89
|
"title": "Emotionally abusive / threatening",
|
|
81
90
|
"selectable": true,
|
|
@@ -84,7 +93,7 @@
|
|
|
84
93
|
"definition": "Emotional abuse, threats, or intimidation by this person toward the subject."
|
|
85
94
|
},
|
|
86
95
|
{
|
|
87
|
-
"code": "
|
|
96
|
+
"code": "991-005-000-000-000-000-000",
|
|
88
97
|
"key": "has_legal_involvement",
|
|
89
98
|
"title": "Has relevant legal involvement",
|
|
90
99
|
"selectable": true,
|
|
@@ -93,7 +102,7 @@
|
|
|
93
102
|
"definition": "This person has a legal case, protective order, or criminal history relevant to the subject's situation."
|
|
94
103
|
},
|
|
95
104
|
{
|
|
96
|
-
"code": "
|
|
105
|
+
"code": "991-006-000-000-000-000-000",
|
|
97
106
|
"key": "is_known_trafficker_or_suspect",
|
|
98
107
|
"title": "Is known or suspected trafficker",
|
|
99
108
|
"selectable": true,
|
|
@@ -102,7 +111,7 @@
|
|
|
102
111
|
"definition": "This person is suspected or confirmed as a trafficker in relation to the subject. Complements (does not replace) role assignment via Add-Person."
|
|
103
112
|
},
|
|
104
113
|
{
|
|
105
|
-
"code": "
|
|
114
|
+
"code": "991-007-000-000-000-000-000",
|
|
106
115
|
"key": "other_concern",
|
|
107
116
|
"title": "Other concern",
|
|
108
117
|
"selectable": true,
|
|
@@ -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
|
+
}
|
|
@@ -256,6 +256,28 @@
|
|
|
256
256
|
"childCodes": [],
|
|
257
257
|
"definition": "Catch-all session template for non-field, non-hotline interactions conducted virtually (video or other virtual meeting formats) when no more specific template applies.",
|
|
258
258
|
"canonicalCode": "CST-UNK-OTHER_VIRTUAL"
|
|
259
|
+
},
|
|
260
|
+
{
|
|
261
|
+
"code": "217-020-000-000-000-000-000",
|
|
262
|
+
"key": "cst_pave_inbound_share",
|
|
263
|
+
"title": "Inbound Share",
|
|
264
|
+
"selectable": true,
|
|
265
|
+
"parentCode": null,
|
|
266
|
+
"childCodes": [],
|
|
267
|
+
"definition": "Review a case another agency shared with your team — claim, set up the record, decide field by field.",
|
|
268
|
+
"canonicalCode": "CST-PAVE-INBOUND_SHARE",
|
|
269
|
+
"application": "PAVE"
|
|
270
|
+
},
|
|
271
|
+
{
|
|
272
|
+
"code": "217-021-000-000-000-000-000",
|
|
273
|
+
"key": "cst_thread_inbound_share",
|
|
274
|
+
"title": "Inbound Share",
|
|
275
|
+
"selectable": true,
|
|
276
|
+
"parentCode": null,
|
|
277
|
+
"childCodes": [],
|
|
278
|
+
"definition": "Review a case another agency shared with your team — claim, set up the record, decide field by field.",
|
|
279
|
+
"canonicalCode": "CST-THREAD-INBOUND_SHARE",
|
|
280
|
+
"application": "Thread"
|
|
259
281
|
}
|
|
260
282
|
]
|
|
261
283
|
}
|