@htilabs/platform-common-models 0.8.18 → 0.8.20

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@htilabs/platform-common-models",
3
- "version": "0.8.18",
3
+ "version": "0.8.20",
4
4
  "description": "Shared constants, types, and models for HTI Labs applications",
5
5
  "type": "module",
6
6
  "main": "./dist/index.cjs",
@@ -147,8 +147,8 @@
147
147
  "hash": "29fb041c4d1b40260e4a448a0501eb580d29606479628a6807a833b52212f3c3"
148
148
  },
149
149
  "person_relationships": {
150
- "count": 89,
151
- "hash": "f901a60ec1f275e2f003d1f1f2f94f2a3ae07d7badee227d650c28c00a1510bb"
150
+ "count": 94,
151
+ "hash": "15b9d1989b897723881cdb489026fab9c42eb9fe0b809f349ec027e42ca7b154"
152
152
  },
153
153
  "employment_status": {
154
154
  "count": 29,
@@ -500,7 +500,7 @@
500
500
  },
501
501
  "relationship_concern": {
502
502
  "count": 11,
503
- "hash": "03e18352e1ffb13a4e9b63e1f4043923f1da7e0153649db6940d0bb2653917d8"
503
+ "hash": "48e882447e87dd4342afc4c9b56aff3925f10177e7ea214dca5d5f66c09e5668"
504
504
  },
505
505
  "recency_band": {
506
506
  "count": 12,
@@ -511,8 +511,8 @@
511
511
  "hash": "995a3170efe8219c0bfe0a174abb2389c86bf94423a70a5ce2b2feb3d9e6b3fa"
512
512
  },
513
513
  "assertion_domain": {
514
- "count": 68,
515
- "hash": "6076e65b804f6e7d3b8385fecfb5114b710ecf672ca13d1e97e5fe0e412b1041"
514
+ "count": 75,
515
+ "hash": "26dc08a4a8da031715b1a0528d578aa65ef231f395c209e7db2f711d4995ad08"
516
516
  },
517
517
  "activity_type": {
518
518
  "count": 14,
@@ -670,6 +670,10 @@
670
670
  "count": 254,
671
671
  "hash": "21525c56d5bac7f218bcb9a5dc048eea4b9132cfaf4a6a7439ebbf7dd34ebcde"
672
672
  },
673
+ "determination_helper_categories": {
674
+ "count": 57,
675
+ "hash": "9e296ba8ae3a187171eb8facfd13a5e6824daa0ed7f963e41e31672104aa16c0"
676
+ },
673
677
  "trafficking_relevant_role": {
674
678
  "count": 8,
675
679
  "hash": "1a4ea2992cc501179adafd192d7a2f1733ffe48c1ba26e1e61a3c757b2d62b32"
@@ -302,7 +302,40 @@ const INDEX_ABSENT: Record<string, { cvc: number; reason: string }> = {
302
302
  hmis_project_type: { cvc: 225, reason: "no CVC_INDEX row" },
303
303
  funder: { cvc: 226, reason: "no CVC_INDEX row" },
304
304
  da_incident_severity: { cvc: 228, reason: "no CVC_INDEX row" },
305
- relationship_concern: { cvc: 231, reason: "no CVC_INDEX row" },
305
+ // relationship_concern (231) LEFT this list in the 2026-08-29 renumber — the
306
+ // OTHER way a domain retires from INDEX_ABSENT, and the one that matters.
307
+ // Jevon ratified CVC-231 to the Determination Helper categories on
308
+ // 2026-08-28. This domain had only ever held 231 as a provisional mint taken
309
+ // out of the canonical block, which is exactly why it lived here instead of
310
+ // in CANONICAL_BINDING. Left at 231 it would have become a SQUAT the moment
311
+ // the next cvcIndex pin refresh published the DH row — and per GATE C a squat
312
+ // does not merely mislabel the squatter, it makes the slot look OCCUPIED and
313
+ // hides the absence of the domain that owns it. It is renumbered to the
314
+ // provisional block at CVC-991 (see relationshipConcern.v1.0.0.json
315
+ // `_status.renumber` / `_status.numberChoice`), so `isProvisional()` now
316
+ // exempts it and no entry here is needed. The Determination Helper categories
317
+ // that own 231 are authored directly below — the gap the vacated squat had
318
+ // been hiding, closed in the same branch that vacated it.
319
+ //
320
+ // CVC-231's rightful owner, authored 2026-08-30. This is the SECOND half of the
321
+ // renumber above and the whole point of GATE C: vacating the squat exposed an
322
+ // unauthored canonical vocabulary, and the exposure is only worth anything if
323
+ // the vocabulary then gets authored. `CVC_INDEX.md` @ 622410b has no row for it
324
+ // (grep confirms: the only `determination`-prefixed rows are CVC-138
325
+ // `core - determination_level` and CVC-233 `core-DH_state`), so this is the
326
+ // `core_information_scope` disposition — numbered from the domain's own
327
+ // canonical self-declaration plus a codebook-owner ruling, index-absent until
328
+ // the extractor catches up — and NOT the CVC-181 one, which had a reserved pin
329
+ // row to bind against. NO PIN EDIT: `cvcIndex.pin.json` is machine-derived and
330
+ // `src/__sot__/README.md` forbids hand-editing it; the row arrives on its own
331
+ // refresh cycle and this domain is promoted into CANONICAL_BINDING then.
332
+ determination_helper_categories: {
333
+ cvc: 231,
334
+ reason:
335
+ "no CVC_INDEX row; number self-declared by the canonical " +
336
+ "data/cvcs/core_determination_helper_categories.yaml and ratified to this " +
337
+ "vocabulary by Jevon on 2026-08-28",
338
+ },
306
339
  };
307
340
 
308
341
  /**
@@ -338,11 +338,17 @@ const SOT_SPECS: readonly SotSpec[] = [
338
338
  // L0 missingness (anonymous, data_not_collected; Notion codebook explicitly
339
339
  // omits `unknown` at L0 — the L2 `relationship_unknown` code carries that
340
340
  // semantic instead; no PNA) + 8 L1 topics + 35 L2 canonical relationship
341
- // types + 40 L3 directional role labels + 3 L3 pet-branch roles = 89.
341
+ // types + 40 L3 directional role labels + 3 L3 pet-branch roles = 89,
342
+ // + 3 L2 LOCAL EXTENSIONS (`parental_figure_dependent`,
343
+ // `intimate_romantic_partner`, `intimate_partner_prior`) + 2 L3 directional
344
+ // roles under `parental_figure_dependent` = 94. All 5 are flagged
345
+ // `localExtension: true`; the canonical picker (prototype@622410b
346
+ // REL_CATEGORIES) offers them and the Notion-side export does not yet carry
347
+ // them. See the file's `_status.localExtension`.
342
348
  {
343
349
  file: "personRelationships.v1.0.0.json",
344
350
  domain: "person_relationships",
345
- expectedCount: 89,
351
+ expectedCount: 94,
346
352
  },
347
353
  // CVC-179 — employment_status: 1 missingness_root + 5 HMIS missingness
348
354
  // (unknown, anonymous, data_not_collected, client_doesnt_know,
@@ -574,9 +580,13 @@ const SOT_SPECS: readonly SotSpec[] = [
574
580
  // `none` = negative determination, canonical per Crysta directive 2026-05-27)
575
581
  // + 1 missingness root + 3 canonical missingness children = 8.
576
582
  { file: "htType.v1.0.0.json", domain: "ht_type", expectedCount: 8 },
577
- // PROVISIONAL CVC-231 relationship_concern — 7 TRA relationship-concern
583
+ // PROVISIONAL CVC-991 relationship_concern — 7 TRA relationship-concern
578
584
  // codes + 1 missingness root + 3 canonical missingness children = 11.
579
585
  // CVC number is PROVISIONAL pending codebook-session ratification.
586
+ // RENUMBERED 231 -> 991 on 2026-08-29: CVC-231 was ratified to the
587
+ // Determination Helper categories (Jevon, 2026-08-28), so the provisional
588
+ // mint this domain held out of the canonical block vacates to the 900-block.
589
+ // Count is unchanged — the renumber is a pure segment-1 prefix substitution.
580
590
  { file: "relationshipConcern.v1.0.0.json", domain: "relationship_concern", expectedCount: 11 },
581
591
  // CVC-137 recency_band — the CANONICAL 8-band key system adopted in 0.8.13
582
592
  // (w3m, m3_6, m6_12, y1p, y1_3, y3_10, y10p, ylt3 — the lowercase
@@ -594,7 +604,10 @@ const SOT_SPECS: readonly SotSpec[] = [
594
604
  // root + 3 canonical missingness children = 16. CVC number is PROVISIONAL
595
605
  // pending ratification.
596
606
  { file: "housingSubsidyTypes.v1.0.0.json", domain: "housing_subsidy_types", expectedCount: 16 },
597
- { file: "assertionDomain.v1.1.0.json", domain: "assertion_domain", expectedCount: 68 },
607
+ // 68 -> 75: the 2026-08-29 signal-identification ratification adds two Level-1
608
+ // domains (signal_identification 159-066, investigative_legal 159-067) plus the
609
+ // five identification-funnel rungs as their Level-2 value rows.
610
+ { file: "assertionDomain.v1.1.0.json", domain: "assertion_domain", expectedCount: 75 },
598
611
  { file: "activityType.v1.0.0.json", domain: "activity_type", expectedCount: 14 },
599
612
  { file: "provenanceSourceId.v1.0.0.json", domain: "provenance_source_id", expectedCount: 13 },
600
613
  { file: "radiusBucket.v1.0.0.json", domain: "radius_bucket", expectedCount: 9 },
@@ -661,6 +674,18 @@ const SOT_SPECS: readonly SotSpec[] = [
661
674
  // 1 authored `non_us_unspecified` local extension = 254. The +1 over CVC-182
662
675
  // is that local extension, and nothing else.
663
676
  { file: "countries.v1.0.0.json", domain: "countries", expectedCount: 254 },
677
+ // CVC-231 — the Determination Helper category taxonomy: 53 canonical rows
678
+ // across the four sections (§ I Subject and Scope 5 · § II Activity 20 ·
679
+ // § III Means 24 · § IV Status 4) + 1 missingness root + 3 workspace-standard
680
+ // missingness children (this codebook carries none of its own) = 57. ALL 53 are
681
+ // selectable, including the 10 non-leaf rows — the canonical
682
+ // feeds_dh_subdomain_crossref addresses parent rows directly, so a
683
+ // category/leaf split would orphan those references.
684
+ {
685
+ file: "determinationHelperCategories.v1.0.0.json",
686
+ domain: "determination_helper_categories",
687
+ expectedCount: 57,
688
+ },
664
689
  // CVC-235 — 4 L1 trafficking-relevant roles + 1 missingness root + 3 canonical
665
690
  // missingness children = 8.
666
691
  {
@@ -208,6 +208,12 @@ const SOT_FILES: readonly SotFile[] = [
208
208
  { file: "citizenship.v1.0.0.json", expectedDomain: "citizenship" },
209
209
  // CVC-181 — the country list CVC-182 shares. Authored 2026-08-26.
210
210
  { file: "countries.v1.0.0.json", expectedDomain: "countries" },
211
+ // CVC-231 — the Determination Helper category taxonomy. Authored 2026-08-30,
212
+ // on the number Jevon ratified to it on 2026-08-28.
213
+ {
214
+ file: "determinationHelperCategories.v1.0.0.json",
215
+ expectedDomain: "determination_helper_categories",
216
+ },
211
217
  { file: "traffickingRelevantRole.v1.0.0.json", expectedDomain: "trafficking_relevant_role" },
212
218
  // ─── Domains the hand-maintained list previously OMITTED (found by the
213
219
  // CVC drift gate, which scans the directory instead of a list). ───
@@ -2,11 +2,12 @@
2
2
  "domain": "assertion_domain",
3
3
  "name": "Assertion Domain (CVC-159)",
4
4
  "version": "2.0.0",
5
- "_status": "CANONICAL — RENUMBERED 0.8.13 from provisional CVC-964 to canonical CVC-159. Live prototype HEAD a596eb9: `Final CVCs` -> `core - assertion_domain` = CVC-159 (vocab_status 'Ready for dev', Verification 'Verified'), corroborated by 17 `data/cvcs/core_assertion_domain_extensions_*.yaml` files that all declare `cvc: core - assertion_domain`. CVC-159 was freed by deleting the 100%-unbound hand-coded `CVC_159_RELATIONSHIP_TIES` family from `src/constants/ic.ts`; `relationship_ties` keeps its canonical CVC-158. Consumers persist KEYS, not wire codes, so the renumber is compile-clean (regenerate `cvcKeys.ts`). WITHDRAWN in 0.8.13 (all three have ZERO occurrences at prototype HEAD): `romantic_relationship` (964-066) — upstream the romantic-partner lifecycle routes to `household_relationships`, see `data/cvcs/core_romantic_relationship_change_type.yaml`; `household_tenure` (964-045); `household_composition` (964-067). All three fold into `household_relationships` (554 occurrences at HEAD). NOTE: `romantic_partner` is a relationship-type VALUE code (1,575 occurrences), never an assertion domain — it is correctly not modelled here. `child_profile` (159-065) is KEPT: 353 occurrences at HEAD. Segment-2 ordinals are preserved across the renumber (gaps at 045/066/067 are intentional; no data migration exists, but stable ordinals keep the diff reviewable). The 37 domains PAVE ships that are absent from the Final CVC-159 export all have substantial upstream occurrence counts and are retained as proposed CVC-159 extensions.",
5
+ "_status": "CANONICAL — RENUMBERED 0.8.13 from provisional CVC-964 to canonical CVC-159. Live prototype HEAD a596eb9: `Final CVCs` -> `core - assertion_domain` = CVC-159 (vocab_status 'Ready for dev', Verification 'Verified'), corroborated by 17 `data/cvcs/core_assertion_domain_extensions_*.yaml` files that all declare `cvc: core - assertion_domain`. CVC-159 was freed by deleting the 100%-unbound hand-coded `CVC_159_RELATIONSHIP_TIES` family from `src/constants/ic.ts`; `relationship_ties` keeps its canonical CVC-158. Consumers persist KEYS, not wire codes, so the renumber is compile-clean (regenerate `cvcKeys.ts`). WITHDRAWN in 0.8.13 (all three have ZERO occurrences at prototype HEAD): `romantic_relationship` (964-066) — upstream the romantic-partner lifecycle routes to `household_relationships`, see `data/cvcs/core_romantic_relationship_change_type.yaml`; `household_tenure` (964-045); `household_composition` (964-067). All three fold into `household_relationships` (554 occurrences at HEAD). NOTE: `romantic_partner` is a relationship-type VALUE code (1,575 occurrences), never an assertion domain — it is correctly not modelled here. `child_profile` (159-065) is KEPT: 353 occurrences at HEAD. Segment-2 ordinals are preserved across the renumber (gaps at 045/066/067 are intentional; no data migration exists, but stable ordinals keep the diff reviewable). The 37 domains PAVE ships that are absent from the Final CVC-159 export all have substantial upstream occurrence counts and are retained as proposed CVC-159 extensions. | 0.8.20: ADDED `signal_identification` (159-066) and `investigative_legal` (159-067) -- retroactive homing of the Track-1 identification-rung emitter live since 2026-08-23; both ratified in the CVC-159 codebook 2026-08-29 (prototype PR #519, hti-features PR #34). Ordinals 066/067 were free: the 0.8.13 withdrawals that reserved those slots were under the OLD CVC-964 numbering and the 159 equivalents were never issued -- verified zero references to 159-066/159-067 anywhere in the repo or the published dist before assigning. The 045 gap remains reserved. The four `signal_identification` rungs and the one `investigative_legal` rung are carried as LEVEL-2 rows under their Level-1 domain, matching how Notion authored them (CVC-159 post-ratification: 26 L1 / 17 L2 / 2 L0 / 2 unleveled) -- they are the value set `assertion_value_code` resolves against for the `identification_rung_reached` CAR, NOT domains of their own. There is no CVC-267 row in CVC_INDEX.md; modelling them as a separate vocabulary was rejected by GATE C. The milestone-symmetry `NO_IDENTIFICATION` row is deliberately EXCLUDED (ruling 2026-08-29, OR2): reaching no rung is the ABSENCE of rows, and a 'none' assertion would re-assert a derived status. CVC-159's OTHER Level-2 rows (incl. `risk_band_crossing` under `risk_signal`) remain unmodelled here -- a follow-up port, not a regression.",
6
6
  "_source": "htilabstech/prototype@a596eb9 Final CVCs/Assertion Contract/core - assertion_domain.md (CVC-159) + 17 core_assertion_domain_extensions_*.yaml",
7
7
  "levels": {
8
8
  "0": "Unknown or Missing",
9
- "1": "CAR assertion domain"
9
+ "1": "CAR assertion domain",
10
+ "2": "CAR assertion value (the vocabulary the domain's assertion_value_code resolves against)"
10
11
  },
11
12
  "entries": [
12
13
  {
@@ -624,6 +625,76 @@
624
625
  "parentCode": null,
625
626
  "childCodes": [],
626
627
  "definition": "assertion_domain partition for CARs on a Child profile subject-record entity (Add Child / Edit Child; core_child_change_type verbs). DRAFT-TEMPORARY direct import from prototype, pending Notion ratification."
628
+ },
629
+ {
630
+ "code": "159-066-000-000-000-000-000",
631
+ "key": "signal_identification",
632
+ "title": "Signal / Identification",
633
+ "selectable": true,
634
+ "parentCode": null,
635
+ "childCodes": [
636
+ "159-066-001-000-000-000-000",
637
+ "159-066-002-000-000-000-000",
638
+ "159-066-003-000-000-000-000",
639
+ "159-066-004-000-000-000-000"
640
+ ],
641
+ "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."
642
+ },
643
+ {
644
+ "code": "159-067-000-000-000-000-000",
645
+ "key": "investigative_legal",
646
+ "title": "Investigative / Legal",
647
+ "selectable": true,
648
+ "parentCode": null,
649
+ "childCodes": [
650
+ "159-067-001-000-000-000-000"
651
+ ],
652
+ "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."
653
+ },
654
+ {
655
+ "code": "159-066-001-000-000-000-000",
656
+ "key": "on_radar",
657
+ "title": "On radar",
658
+ "selectable": true,
659
+ "parentCode": "159-066-000-000-000-000-000",
660
+ "childCodes": [],
661
+ "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)."
662
+ },
663
+ {
664
+ "code": "159-066-002-000-000-000-000",
665
+ "key": "screened",
666
+ "title": "Screened",
667
+ "selectable": true,
668
+ "parentCode": "159-066-000-000-000-000-000",
669
+ "childCodes": [],
670
+ "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)."
671
+ },
672
+ {
673
+ "code": "159-066-003-000-000-000-000",
674
+ "key": "at_risk",
675
+ "title": "At risk",
676
+ "selectable": true,
677
+ "parentCode": "159-066-000-000-000-000-000",
678
+ "childCodes": [],
679
+ "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."
680
+ },
681
+ {
682
+ "code": "159-066-004-000-000-000-000",
683
+ "key": "assessed",
684
+ "title": "Assessed",
685
+ "selectable": true,
686
+ "parentCode": "159-066-000-000-000-000-000",
687
+ "childCodes": [],
688
+ "definition": "Rung 4. A full assessment was completed."
689
+ },
690
+ {
691
+ "code": "159-067-001-000-000-000-000",
692
+ "key": "determined",
693
+ "title": "Determined",
694
+ "selectable": true,
695
+ "parentCode": "159-067-000-000-000-000-000",
696
+ "childCodes": [],
697
+ "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."
627
698
  }
628
699
  ]
629
700
  }