@htilabs/platform-common-models 0.8.24 → 0.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (91) hide show
  1. package/dist/config/index.cjs +81 -0
  2. package/dist/config/index.cjs.map +1 -1
  3. package/dist/config/index.d.cts +79 -4
  4. package/dist/config/index.d.ts +79 -4
  5. package/dist/config/index.js +79 -1
  6. package/dist/config/index.js.map +1 -1
  7. package/dist/constants/index.cjs +2 -18
  8. package/dist/constants/index.cjs.map +1 -1
  9. package/dist/constants/index.d.cts +1 -1
  10. package/dist/constants/index.d.ts +1 -1
  11. package/dist/constants/index.js +2 -18
  12. package/dist/constants/index.js.map +1 -1
  13. package/dist/{cvcEntry-ctHTp2df.d.cts → cvcEntry-BCj1OWqL.d.cts} +44 -44
  14. package/dist/{cvcEntry-ctHTp2df.d.ts → cvcEntry-BCj1OWqL.d.ts} +44 -44
  15. package/dist/cvcs/index.cjs +217 -6674
  16. package/dist/cvcs/index.cjs.map +1 -1
  17. package/dist/cvcs/index.d.cts +8057 -15024
  18. package/dist/cvcs/index.d.ts +8057 -15024
  19. package/dist/cvcs/index.js +217 -6662
  20. package/dist/cvcs/index.js.map +1 -1
  21. package/dist/{index-qreOzXYS.d.cts → index-CoVr1jIV.d.cts} +1 -1
  22. package/dist/{index-4DiJrn7y.d.ts → index-I-DiX9eQ.d.ts} +1 -1
  23. package/dist/index.cjs +230 -7217
  24. package/dist/index.cjs.map +1 -1
  25. package/dist/index.d.cts +26 -588
  26. package/dist/index.d.ts +26 -588
  27. package/dist/index.js +230 -7193
  28. package/dist/index.js.map +1 -1
  29. package/dist/models/index.d.cts +2 -2
  30. package/dist/models/index.d.ts +2 -2
  31. package/dist/mongo/index.cjs +1 -0
  32. package/dist/mongo/index.cjs.map +1 -1
  33. package/dist/mongo/index.js +2 -1
  34. package/dist/mongo/index.js.map +1 -1
  35. package/dist/{platform-auth-91Hcl8F8.d.cts → platform-auth-v53r3BhN.d.cts} +3 -4
  36. package/dist/{platform-auth-91Hcl8F8.d.ts → platform-auth-v53r3BhN.d.ts} +3 -4
  37. package/dist/schemas/index.cjs +1 -5
  38. package/dist/schemas/index.cjs.map +1 -1
  39. package/dist/schemas/index.d.cts +35 -35
  40. package/dist/schemas/index.d.ts +35 -35
  41. package/dist/schemas/index.js +1 -5
  42. package/dist/schemas/index.js.map +1 -1
  43. package/dist/types/index.d.cts +2 -2
  44. package/dist/types/index.d.ts +2 -2
  45. package/dist/validation/index.cjs +0 -58
  46. package/dist/validation/index.cjs.map +1 -1
  47. package/dist/validation/index.d.cts +283 -82
  48. package/dist/validation/index.d.ts +283 -82
  49. package/dist/validation/index.js +0 -57
  50. package/dist/validation/index.js.map +1 -1
  51. package/package.json +22 -26
  52. package/src/__sot__/README.md +1 -36
  53. package/src/__sot__/coreIndicators.pin.json +2 -1936
  54. package/src/__sot__/cvcIndex.pin.json +4 -8
  55. package/src/__tests__/__snapshots__/cvc-sot.snap +13 -41
  56. package/src/__tests__/cvc-136-scoring-invariant.test.ts +3 -8
  57. package/src/__tests__/cvc-drift-gate.test.ts +12 -445
  58. package/src/__tests__/cvc-sot-snapshot.test.ts +11 -73
  59. package/src/__tests__/cvc-structural.test.ts +0 -14
  60. package/src/__tests__/runtime-contract-validator.test.ts +325 -1
  61. package/src/config/index.ts +189 -4
  62. package/src/constants/ic.ts +3 -120
  63. package/src/cvcs/assertionDomain.v1.1.0.json +1 -19
  64. package/src/cvcs/coreIndicators.v1.0.0.json +5 -83
  65. package/src/cvcs/incidentParticipationRoles.v1.0.0.json +1 -11
  66. package/src/cvcs/index.ts +0 -32
  67. package/src/cvcs/personRelationships.v1.0.0.json +2 -67
  68. package/src/cvcs/relationshipConcern.v1.0.0.json +19 -28
  69. package/src/cvcs/sessionTemplate.v1.0.0.json +0 -22
  70. package/src/cvcs/sharePurpose.v1.0.0.json +12 -80
  71. package/src/generated/cvc-enums.ts +20 -606
  72. package/src/validation/index.ts +0 -1
  73. package/dist/cvc-C7qdsXYK.d.cts +0 -298
  74. package/dist/cvc-C7qdsXYK.d.ts +0 -298
  75. package/src/__sot__/coreIndicatorFields.ts +0 -331
  76. package/src/__tests__/core-information-scope-invariant.test.ts +0 -134
  77. package/src/__tests__/cvc-181-182-country-parity.test.ts +0 -163
  78. package/src/__tests__/cvc-status-parser.test.ts +0 -150
  79. package/src/cvcs/assertionStatus.v1.0.0.json +0 -80
  80. package/src/cvcs/carCorrectionReason.v1.0.0.json +0 -89
  81. package/src/cvcs/caseShareState.v1.0.0.json +0 -62
  82. package/src/cvcs/coreInformationScope.v1.0.0.json +0 -1165
  83. package/src/cvcs/countries.v1.0.0.json +0 -3077
  84. package/src/cvcs/createdBySystem.v1.0.0.json +0 -89
  85. package/src/cvcs/criminalOrgCategory.v1.0.0.json +0 -116
  86. package/src/cvcs/determinationHelperCategories.v1.0.0.json +0 -1166
  87. package/src/cvcs/minorAdultStatus.v1.0.0.json +0 -80
  88. package/src/cvcs/referralOrigin.v1.0.0.json +0 -26
  89. package/src/cvcs/riskIdentificationMilestone.v1.0.0.json +0 -109
  90. package/src/cvcs/subjectType.v1.0.0.json +0 -80
  91. package/src/validation/cvcStatus.ts +0 -209
@@ -149,8 +149,7 @@
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",
153
- "069-004-006-000-000-000-000"
152
+ "069-004-005-000-000-000-000"
154
153
  ],
155
154
  "definition": "Group of participation roles identifying system-side professionals involved in the incident."
156
155
  },
@@ -198,15 +197,6 @@
198
197
  "parentCode": "069-004-000-000-000-000-000",
199
198
  "childCodes": [],
200
199
  "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."
210
200
  }
211
201
  ]
212
202
  }
package/src/cvcs/index.ts CHANGED
@@ -44,8 +44,6 @@ 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
47
  import facilitatorEntityTypeSot from "./facilitatorEntityType.v1.0.0.json" with { type: "json" };
50
48
  import facilitatorSubroleSot from "./facilitatorSubrole.v1.0.0.json" with { type: "json" };
51
49
  import maritalStatusLegalSot from "./maritalStatusLegal.v1.0.0.json" with { type: "json" };
@@ -158,14 +156,12 @@ import romanticRelationshipChangeTypeSot from "./romanticRelationshipChangeType.
158
156
  import riskCategorySot from "./riskCategory.v1.0.0.json" with { type: "json" };
159
157
  import coreFunctionsSot from "./coreFunctions.v1.0.0.json" with { type: "json" };
160
158
  import needsAssessmentChangeTypeSot from "./needsAssessmentChangeType.v1.0.0.json" with { type: "json" };
161
- import coreInformationScopeSot from "./coreInformationScope.v1.0.0.json" with { type: "json" };
162
159
  import roiScopeSot from "./roiScope.v1.0.0.json" with { type: "json" };
163
160
  import roiStatusSot from "./roiStatus.v1.0.0.json" with { type: "json" };
164
161
  import coreReferralOutcomeSot from "./coreReferralOutcome.v1.0.0.json" with { type: "json" };
165
162
  import coreIndicatorsSot from "./coreIndicators.v1.0.0.json" with { type: "json" };
166
163
  import coreDhStateSot from "./coreDhState.v1.0.0.json" with { type: "json" };
167
164
  import riskSeverityBandSot from "./riskSeverityBand.v1.0.0.json" with { type: "json" };
168
- import riskIdentificationMilestoneSot from "./riskIdentificationMilestone.v1.0.0.json" with { type: "json" };
169
165
  import adminRolesSot from "./adminRoles.v1.0.0.json" with { type: "json" };
170
166
  import userRolesSot from "./userRoles.v1.0.0.json" with { type: "json" };
171
167
  import hmisCurrentLivingSituationSot from "./hmisCurrentLivingSituation.v1.0.0.json" with { type: "json" };
@@ -181,8 +177,6 @@ import sessionTemplateSot from "./sessionTemplate.v1.0.0.json" with { type: "jso
181
177
  import serviceDeliveryChannelSot from "./serviceDeliveryChannel.v1.0.0.json" with { type: "json" };
182
178
  import whyNotsSot from "./whyNots.v1.0.0.json" with { type: "json" };
183
179
  import citizenshipSot from "./citizenship.v1.0.0.json" with { type: "json" };
184
- import countriesSot from "./countries.v1.0.0.json" with { type: "json" };
185
- import determinationHelperCategoriesSot from "./determinationHelperCategories.v1.0.0.json" with { type: "json" };
186
180
  import traffickingRelevantRoleSot from "./traffickingRelevantRole.v1.0.0.json" with { type: "json" };
187
181
  // Domains that were never exported from this barrel (found by the CVC drift gate).
188
182
  import activityTypeSot from "./activityType.v1.0.0.json" with { type: "json" };
@@ -193,13 +187,6 @@ import radiusBucketSot from "./radiusBucket.v1.0.0.json" with { type: "json" };
193
187
  import roiMethodSot from "./roiMethod.v1.0.0.json" with { type: "json" };
194
188
  import sessionNoteVisibilitySot from "./sessionNoteVisibility.v1.0.0.json" with { type: "json" };
195
189
  import suggestionSourceSot from "./suggestionSource.v1.0.0.json" with { type: "json" };
196
- // GDR §10.1 CAR-contract vocabularies (provisional 900-block; PAVE @pave/domain
197
- // verbatim; bead pv-pgdr-cvc-source-gdr-10-1-bulk-publish).
198
- import assertionStatusSot from "./assertionStatus.v1.0.0.json" with { type: "json" };
199
- import carCorrectionReasonSot from "./carCorrectionReason.v1.0.0.json" with { type: "json" };
200
- import createdBySystemSot from "./createdBySystem.v1.0.0.json" with { type: "json" };
201
- import subjectTypeSot from "./subjectType.v1.0.0.json" with { type: "json" };
202
- import minorAdultStatusSot from "./minorAdultStatus.v1.0.0.json" with { type: "json" };
203
190
  // Trunk-only domain (CVC-67) authored on `kl-develop` and never seen by the
204
191
  // canonical 0.8.13 line. It shipped as an orphan JSON — the file existed but
205
192
  // was never wired into this barrel, so nothing could import it. Wired in here
@@ -207,13 +194,6 @@ import minorAdultStatusSot from "./minorAdultStatus.v1.0.0.json" with { type: "j
207
194
  // across the merged tree. Coexists with the `CVC_67_HMIS_SEX` constants in
208
195
  // `../constants/ic.ts`; the JSON is the SOT, the constants are the legacy view.
209
196
  import hmisSexSot from "./hmisSex.v1.0.0.json" with { type: "json" };
210
- // Domain authored in PR #142 (0.8.15) alongside the codegen manifest entry in
211
- // scripts/codegen-cvc-enums.ts, but never wired into this barrel — the SOT
212
- // JSON shipped and `src/generated/cvc-enums.ts` regenerated correctly (it
213
- // reads `src/cvcs/*.json` directly), but this file does not, so the export
214
- // never reached the compiled `dist/cvcs/`. Wired in here so downstream
215
- // consumers that derive their key maps from `./cvcs` (e.g. PAVE) can see it.
216
- import criminalOrgCategorySot from "./criminalOrgCategory.v1.0.0.json" with { type: "json" };
217
197
 
218
198
  export {
219
199
  serviceCategoriesSot,
@@ -241,8 +221,6 @@ export {
241
221
  highestEducationLevelCompletedSot,
242
222
  preferredContactMethodSot,
243
223
  sharePurposeSot,
244
- referralOriginSot,
245
- caseShareStateSot,
246
224
  facilitatorEntityTypeSot,
247
225
  facilitatorSubroleSot,
248
226
  maritalStatusLegalSot,
@@ -355,14 +333,12 @@ export {
355
333
  riskCategorySot,
356
334
  coreFunctionsSot,
357
335
  needsAssessmentChangeTypeSot,
358
- coreInformationScopeSot,
359
336
  roiScopeSot,
360
337
  roiStatusSot,
361
338
  coreReferralOutcomeSot,
362
339
  coreIndicatorsSot,
363
340
  coreDhStateSot,
364
341
  riskSeverityBandSot,
365
- riskIdentificationMilestoneSot,
366
342
  adminRolesSot,
367
343
  userRolesSot,
368
344
  hmisCurrentLivingSituationSot,
@@ -378,8 +354,6 @@ export {
378
354
  serviceDeliveryChannelSot,
379
355
  whyNotsSot,
380
356
  citizenshipSot,
381
- countriesSot,
382
- determinationHelperCategoriesSot,
383
357
  traffickingRelevantRoleSot,
384
358
  activityTypeSot,
385
359
  assertionDomainSot,
@@ -389,11 +363,5 @@ export {
389
363
  roiMethodSot,
390
364
  sessionNoteVisibilitySot,
391
365
  suggestionSourceSot,
392
- assertionStatusSot,
393
- carCorrectionReasonSot,
394
- createdBySystemSot,
395
- subjectTypeSot,
396
- minorAdultStatusSot,
397
366
  hmisSexSot,
398
- criminalOrgCategorySot,
399
367
  };
@@ -2,15 +2,6 @@
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",
14
5
  "levels": {
15
6
  "0": "Unknown or Missing",
16
7
  "1": "Topic",
@@ -60,8 +51,7 @@
60
51
  "126-001-003-000-000-000-000",
61
52
  "126-001-004-000-000-000-000",
62
53
  "126-001-005-000-000-000-000",
63
- "126-001-006-000-000-000-000",
64
- "126-001-007-000-000-000-000"
54
+ "126-001-006-000-000-000-000"
65
55
  ],
66
56
  "definition": "Relationships between two people who are related through family or kinship, including immediate and extended family."
67
57
  },
@@ -182,39 +172,6 @@
182
172
  "childCodes": [],
183
173
  "definition": "A relationship between two people who share a sibling relationship."
184
174
  },
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
- },
218
175
  {
219
176
  "code": "126-002-000-000-000-000-000",
220
177
  "key": "romantic_partner",
@@ -223,9 +180,7 @@
223
180
  "parentCode": null,
224
181
  "childCodes": [
225
182
  "126-002-001-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"
183
+ "126-002-002-000-000-000-000"
229
184
  ],
230
185
  "definition": "Relationship between two people who are or were in a romantic or intimate partnership."
231
186
  },
@@ -247,26 +202,6 @@
247
202
  "childCodes": [],
248
203
  "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)."
249
204
  },
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
- },
270
205
  {
271
206
  "code": "126-003-000-000-000-000-000",
272
207
  "key": "care_household",
@@ -1,63 +1,54 @@
1
1
  {
2
2
  "domain": "relationship_concern",
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
- },
3
+ "name": "Core Relationship Concern (PROVISIONAL CVC-231 — pending codebook ratification)",
4
+ "version": "1.0.0",
14
5
  "levels": {
15
6
  "0": "Unknown or Missing",
16
7
  "1": "Relationship concern"
17
8
  },
18
9
  "entries": [
19
10
  {
20
- "code": "991-000-000-000-000-000-000",
11
+ "code": "231-000-000-000-000-000-000",
21
12
  "key": "missingness_root",
22
13
  "title": "Unknown, Redacted, or Missing",
23
14
  "selectable": false,
24
15
  "parentCode": null,
25
16
  "childCodes": [
26
- "991-000-000-000-000-000-001",
27
- "991-000-000-000-000-000-002",
28
- "991-000-000-000-000-000-003"
17
+ "231-000-000-000-000-000-001",
18
+ "231-000-000-000-000-000-002",
19
+ "231-000-000-000-000-000-003"
29
20
  ],
30
21
  "definition": "Root group for values indicating absent, withheld, or uncollected data."
31
22
  },
32
23
  {
33
- "code": "991-000-000-000-000-000-001",
24
+ "code": "231-000-000-000-000-000-001",
34
25
  "key": "unknown",
35
26
  "title": "Unknown",
36
27
  "selectable": true,
37
- "parentCode": "991-000-000-000-000-000-000",
28
+ "parentCode": "231-000-000-000-000-000-000",
38
29
  "childCodes": [],
39
30
  "definition": "The relationship concern is unknown or cannot be determined from the available information."
40
31
  },
41
32
  {
42
- "code": "991-000-000-000-000-000-002",
33
+ "code": "231-000-000-000-000-000-002",
43
34
  "key": "anonymous",
44
35
  "title": "Anonymous / declined to answer",
45
36
  "selectable": true,
46
- "parentCode": "991-000-000-000-000-000-000",
37
+ "parentCode": "231-000-000-000-000-000-000",
47
38
  "childCodes": [],
48
39
  "definition": "The relationship concern may be withheld by preference or due to redaction; identity is anonymous or redacted."
49
40
  },
50
41
  {
51
- "code": "991-000-000-000-000-000-003",
42
+ "code": "231-000-000-000-000-000-003",
52
43
  "key": "data_not_collected",
53
44
  "title": "Data not collected",
54
45
  "selectable": true,
55
- "parentCode": "991-000-000-000-000-000-000",
46
+ "parentCode": "231-000-000-000-000-000-000",
56
47
  "childCodes": [],
57
48
  "definition": "No attempt was made to collect the relationship concern."
58
49
  },
59
50
  {
60
- "code": "991-001-000-000-000-000-000",
51
+ "code": "231-001-000-000-000-000-000",
61
52
  "key": "appears_controlling",
62
53
  "title": "Appears controlling",
63
54
  "selectable": true,
@@ -66,7 +57,7 @@
66
57
  "definition": "Employer, intimate partner, or family member who appears controlling in relation to the subject."
67
58
  },
68
59
  {
69
- "code": "991-002-000-000-000-000-000",
60
+ "code": "231-002-000-000-000-000-000",
70
61
  "key": "is_much_older",
71
62
  "title": "Is much older (age-disparate)",
72
63
  "selectable": true,
@@ -75,7 +66,7 @@
75
66
  "definition": "Significant age disparity in the relationship — a vulnerability signal, especially for youth."
76
67
  },
77
68
  {
78
- "code": "991-003-000-000-000-000-000",
69
+ "code": "231-003-000-000-000-000-000",
79
70
  "key": "physically_abusive",
80
71
  "title": "Physically abusive",
81
72
  "selectable": true,
@@ -84,7 +75,7 @@
84
75
  "definition": "Reports of physical harm or abuse from this person toward the subject."
85
76
  },
86
77
  {
87
- "code": "991-004-000-000-000-000-000",
78
+ "code": "231-004-000-000-000-000-000",
88
79
  "key": "emotionally_abusive",
89
80
  "title": "Emotionally abusive / threatening",
90
81
  "selectable": true,
@@ -93,7 +84,7 @@
93
84
  "definition": "Emotional abuse, threats, or intimidation by this person toward the subject."
94
85
  },
95
86
  {
96
- "code": "991-005-000-000-000-000-000",
87
+ "code": "231-005-000-000-000-000-000",
97
88
  "key": "has_legal_involvement",
98
89
  "title": "Has relevant legal involvement",
99
90
  "selectable": true,
@@ -102,7 +93,7 @@
102
93
  "definition": "This person has a legal case, protective order, or criminal history relevant to the subject's situation."
103
94
  },
104
95
  {
105
- "code": "991-006-000-000-000-000-000",
96
+ "code": "231-006-000-000-000-000-000",
106
97
  "key": "is_known_trafficker_or_suspect",
107
98
  "title": "Is known or suspected trafficker",
108
99
  "selectable": true,
@@ -111,7 +102,7 @@
111
102
  "definition": "This person is suspected or confirmed as a trafficker in relation to the subject. Complements (does not replace) role assignment via Add-Person."
112
103
  },
113
104
  {
114
- "code": "991-007-000-000-000-000-000",
105
+ "code": "231-007-000-000-000-000-000",
115
106
  "key": "other_concern",
116
107
  "title": "Other concern",
117
108
  "selectable": true,
@@ -256,28 +256,6 @@
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"
281
259
  }
282
260
  ]
283
261
  }
@@ -1,9 +1,7 @@
1
1
  {
2
2
  "domain": "share_purpose",
3
3
  "name": "Core Share Purpose",
4
- "version": "1.1.0",
5
- "_status": "Synced verbatim from canonical CVC-84 (renamed `core-sharing_purpose` 2026-08-19). 8 core rows from `core_share_purpose.yaml` + 4 LEADS-wing rows from `core_share_purpose_extensions_leads.yaml`, which the prototype's `build_sharing_purpose_catalog.py` joins into the 12-row catalog. The wing rows were RATIFIED 2026-07-03 and live-synced 2026-08-19 (no longer proposal-only). 0.8.16 shipped the core 8 only, and shipped them WITHOUT the decision attributes — which is how a consumer came to map `deconfliction` and `automatic_account_share` onto each other's legacy policy rows. `setBy`, `wing`, `appScope` and `needToKnowArm` are now carried as data so that mapping is derivable rather than inferred from titles. Codes 084-001..008 are FROZEN at their published key assignment; the wing rows take 084-009..012, so nothing already stored changes meaning.",
6
- "_source": "htilabstech/prototype data/cvcs/core_share_purpose.yaml + core_share_purpose_extensions_leads.yaml",
4
+ "version": "1.0.0",
7
5
  "levels": {
8
6
  "1": "Purpose"
9
7
  },
@@ -15,9 +13,7 @@
15
13
  "selectable": true,
16
14
  "parentCode": null,
17
15
  "childCodes": [],
18
- "definition": "A one time point in time share used to refer limited, specific segments of information to another party for a narrow purpose.",
19
- "setBy": "manual",
20
- "wing": "core"
16
+ "definition": "Sharing client information to connect the client to a service, program, or provider outside the originating agency so that the receiving party can engage or enroll them."
21
17
  },
22
18
  {
23
19
  "code": "084-002-000-000-000-000-000",
@@ -26,9 +22,7 @@
26
22
  "selectable": true,
27
23
  "parentCode": null,
28
24
  "childCodes": [],
29
- "definition": "An ongoing but time limited sharing purpose to support repeated communication needed to complete a specific service or action approved by the victim or mandated by law.",
30
- "setBy": "manual",
31
- "wing": "core"
25
+ "definition": "Sharing information among agencies or providers actively co-working a client's case so each collaborator can coordinate services, avoid duplication, and advance shared case goals."
32
26
  },
33
27
  {
34
28
  "code": "084-003-000-000-000-000-000",
@@ -37,32 +31,25 @@
37
31
  "selectable": true,
38
32
  "parentCode": null,
39
33
  "childCodes": [],
40
- "definition": "A sharing purpose for detecting overlap between two parties' case records (deconfliction) so agencies, teams, or investigators can identify parallel work and coordinate safely when appropriate.",
41
- "setBy": "automatic",
42
- "wing": "core",
43
- "appScope": "leads_only"
34
+ "definition": "Sharing the minimum information required to determine whether multiple parties are engaged with the same client or incident, in order to prevent conflicting actions or duplicate outreach."
44
35
  },
45
36
  {
46
37
  "code": "084-004-000-000-000-000-000",
47
38
  "key": "mandatory_reporting",
48
- "title": "Mandatory report",
39
+ "title": "Mandatory reporting",
49
40
  "selectable": true,
50
41
  "parentCode": null,
51
42
  "childCodes": [],
52
- "definition": "A sharing purpose indicating information must be shared to meet a legal or regulatory mandated reporting duty.",
53
- "setBy": "manual",
54
- "wing": "core"
43
+ "definition": "Sharing information to satisfy a legal duty to report suspected abuse, neglect, or similar statutorily defined harms to an authorized receiving body (e.g., child or adult protective services)."
55
44
  },
56
45
  {
57
46
  "code": "084-005-000-000-000-000-000",
58
47
  "key": "authority_reporting",
59
- "title": "Authority report",
48
+ "title": "Authority reporting",
60
49
  "selectable": true,
61
50
  "parentCode": null,
62
51
  "childCodes": [],
63
- "definition": "A sharing purpose used to notify a designated authority for accountability, compliance, intelligence, or administrative purposes when the sender is not acting under a mandated reporter duty.",
64
- "setBy": "manual",
65
- "wing": "core"
52
+ "definition": "Sharing information with a governing authority, regulator, or funder to satisfy a non-mandatory-reporter disclosure obligation such as grant reporting, oversight notifications, or jurisdictional alerts."
66
53
  },
67
54
  {
68
55
  "code": "084-006-000-000-000-000-000",
@@ -71,20 +58,16 @@
71
58
  "selectable": true,
72
59
  "parentCode": null,
73
60
  "childCodes": [],
74
- "definition": "An agency-admin configured, default sharing mode that automatically makes a limited, standardized subset of case information viewable across the agency account without requiring case-by-case sharing decisions by end users.",
75
- "setBy": "automatic",
76
- "wing": "core"
61
+ "definition": "Sharing that occurs automatically because the receiving party is configured as a standing member of the client's account, team, or care circle and receives information without a case-by-case release decision."
77
62
  },
78
63
  {
79
64
  "code": "084-007-000-000-000-000-000",
80
65
  "key": "discretionary_share",
81
- "title": "Discretionary share (FYI)",
66
+ "title": "Discretionary share",
82
67
  "selectable": true,
83
68
  "parentCode": null,
84
69
  "childCodes": [],
85
- "definition": "A sharing purpose for situational awareness or FYI sharing when there is no explicit requested action, no legal duty, and no structured collaboration.",
86
- "setBy": "manual",
87
- "wing": "core"
70
+ "definition": "Ad-hoc sharing initiated at the sharer's discretion for a specific purpose that does not fit another defined category; the sharer is responsible for recording the reason and scope on the share."
88
71
  },
89
72
  {
90
73
  "code": "084-008-000-000-000-000-000",
@@ -93,58 +76,7 @@
93
76
  "selectable": true,
94
77
  "parentCode": null,
95
78
  "childCodes": [],
96
- "definition": null,
97
- "setBy": "automatic",
98
- "wing": "core",
99
- "incompleteInSource": true
100
- },
101
- {
102
- "code": "084-009-000-000-000-000-000",
103
- "key": "investigation_support",
104
- "title": "Investigation support",
105
- "selectable": true,
106
- "parentCode": null,
107
- "childCodes": [],
108
- "definition": "Case or investigative intelligence (identifies people or organizations) disseminated to a LEADS recipient working on some aspect of the inquiry.",
109
- "setBy": "manual",
110
- "wing": "leads",
111
- "needToKnowArm": "assist_support_investigation"
112
- },
113
- {
114
- "code": "084-010-000-000-000-000-000",
115
- "key": "threat_prevention",
116
- "title": "Threat prevention",
117
- "selectable": true,
118
- "parentCode": null,
119
- "childCodes": [],
120
- "definition": "A sharing purpose for dissemination that is pertinent and necessary to prevent or mitigate a threat.",
121
- "setBy": "manual",
122
- "wing": "leads",
123
- "needToKnowArm": "prevent_mitigate_threat"
124
- },
125
- {
126
- "code": "084-011-000-000-000-000-000",
127
- "key": "awareness_product",
128
- "title": "Situational awareness (intelligence product)",
129
- "selectable": true,
130
- "parentCode": null,
131
- "childCodes": [],
132
- "definition": "A sharing purpose for a de-identified intelligence product — indicators, methodologies, or pattern trends with no identified individuals or organizations.",
133
- "setBy": "manual",
134
- "wing": "leads",
135
- "needToKnowArm": "assumed_for_le"
136
- },
137
- {
138
- "code": "084-012-000-000-000-000-000",
139
- "key": "prosecution_support",
140
- "title": "Prosecution support",
141
- "selectable": true,
142
- "parentCode": null,
143
- "childCodes": [],
144
- "definition": "A sharing purpose for material headed toward charging, court filing, or discovery; routes the act to the evidence/discovery export register rather than the dissemination share path.",
145
- "setBy": "manual",
146
- "wing": "leads",
147
- "needToKnowArm": "assist_support_investigation"
79
+ "definition": "Sharing information in response to a formal request for records (for example a subpoena, court order, ROI-backed request, or FOIA-style inquiry) where the request itself establishes the sharing purpose."
148
80
  }
149
81
  ]
150
82
  }