@htilabs/platform-common-models 0.8.19 → 0.8.21

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.cjs CHANGED
@@ -409,6 +409,7 @@ __export(src_exports, {
409
409
  RelationshipTiesKeys: () => RelationshipTiesKeys,
410
410
  ReturnedToAbuserStatusKeys: () => ReturnedToAbuserStatusKeys,
411
411
  RiskCategoryKeys: () => RiskCategoryKeys,
412
+ RiskIdentificationMilestoneKeys: () => RiskIdentificationMilestoneKeys,
412
413
  RiskSeverityBandKeys: () => RiskSeverityBandKeys,
413
414
  RoiMethodKeys: () => RoiMethodKeys,
414
415
  RoiScopeKeys: () => RoiScopeKeys,
@@ -661,6 +662,7 @@ __export(src_exports, {
661
662
  resolveRegistryWithInheritance: () => resolveRegistryWithInheritance,
662
663
  returnedToAbuserStatusSot: () => returnedToAbuserStatus_v1_0_0_default,
663
664
  riskCategorySot: () => riskCategory_v1_0_0_default,
665
+ riskIdentificationMilestoneSot: () => riskIdentificationMilestone_v1_0_0_default,
664
666
  riskSeverityBandSot: () => riskSeverityBand_v1_0_0_default,
665
667
  roiMethodSot: () => roiMethod_v1_0_0_default,
666
668
  roiScopeSot: () => roiScope_v1_0_0_default,
@@ -10289,7 +10291,9 @@ var AssertionDomainKeys = {
10289
10291
  facilitator_role: "159-062-000-000-000-000-000",
10290
10292
  facilitator_subrole: "159-063-000-000-000-000-000",
10291
10293
  facilitator_entity_type: "159-064-000-000-000-000-000",
10292
- child_profile: "159-065-000-000-000-000-000"
10294
+ child_profile: "159-065-000-000-000-000-000",
10295
+ signal_identification: "159-066-000-000-000-000-000",
10296
+ investigative_legal: "159-067-000-000-000-000-000"
10293
10297
  };
10294
10298
  var ActivityTypeKeys = {
10295
10299
  missingness_root: "965-000-000-000-000-000-000",
@@ -10940,6 +10944,17 @@ var CoreIndicatorKeys = {
10940
10944
  trauma_perpetrator_is_current_manager: "136-215-000-000-000-000-000",
10941
10945
  active_protective_order: "136-216-000-000-000-000-000"
10942
10946
  };
10947
+ var RiskIdentificationMilestoneKeys = {
10948
+ missingness_root: "267-000-000-000-000-000-000",
10949
+ unknown: "267-000-000-000-000-000-001",
10950
+ anonymous: "267-000-000-000-000-000-002",
10951
+ data_not_collected: "267-000-000-000-000-000-003",
10952
+ on_radar: "267-001-000-000-000-000-000",
10953
+ screened: "267-002-000-000-000-000-000",
10954
+ at_risk: "267-003-000-000-000-000-000",
10955
+ assessed: "267-004-000-000-000-000-000",
10956
+ determined: "267-005-000-000-000-000-000"
10957
+ };
10943
10958
  var RiskSeverityBandKeys = {
10944
10959
  missingness_root: "238-000-000-000-000-000-000",
10945
10960
  unknown: "238-000-000-000-000-000-001",
@@ -43164,6 +43179,117 @@ var riskSeverityBand_v1_0_0_default = {
43164
43179
  ]
43165
43180
  };
43166
43181
 
43182
+ // src/cvcs/riskIdentificationMilestone.v1.0.0.json
43183
+ var riskIdentificationMilestone_v1_0_0_default = {
43184
+ domain: "risk_identification_milestone",
43185
+ name: "Core Risk Identification Milestone (CVC-267)",
43186
+ version: "1.0.0",
43187
+ _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`.",
43188
+ _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)",
43189
+ levels: {
43190
+ "0": "Unknown or Missing",
43191
+ "1": "Identification funnel rung"
43192
+ },
43193
+ entries: [
43194
+ {
43195
+ code: "267-000-000-000-000-000-000",
43196
+ key: "missingness_root",
43197
+ title: "Unknown, Redacted, or Missing",
43198
+ selectable: false,
43199
+ parentCode: null,
43200
+ childCodes: [
43201
+ "267-000-000-000-000-000-001",
43202
+ "267-000-000-000-000-000-002",
43203
+ "267-000-000-000-000-000-003"
43204
+ ],
43205
+ 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."
43206
+ },
43207
+ {
43208
+ code: "267-000-000-000-000-000-001",
43209
+ key: "unknown",
43210
+ title: "Unknown",
43211
+ selectable: true,
43212
+ parentCode: "267-000-000-000-000-000-000",
43213
+ childCodes: [],
43214
+ canonicalCode: "UNK",
43215
+ 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."
43216
+ },
43217
+ {
43218
+ code: "267-000-000-000-000-000-002",
43219
+ key: "anonymous",
43220
+ title: "Anonymous / declined to answer",
43221
+ selectable: true,
43222
+ parentCode: "267-000-000-000-000-000-000",
43223
+ childCodes: [],
43224
+ definition: "Value is intentionally withheld or redacted. Combines declined-to-answer and redacted/anonymous semantics under the workspace standard ANON sentinel."
43225
+ },
43226
+ {
43227
+ code: "267-000-000-000-000-000-003",
43228
+ key: "data_not_collected",
43229
+ title: "Data not collected",
43230
+ selectable: true,
43231
+ parentCode: "267-000-000-000-000-000-000",
43232
+ childCodes: [],
43233
+ definition: "No attempt was made to collect the value. System-only sentinel per GLOBAL_DESIGN_RULES."
43234
+ },
43235
+ {
43236
+ code: "267-001-000-000-000-000-000",
43237
+ key: "on_radar",
43238
+ title: "On radar",
43239
+ selectable: true,
43240
+ parentCode: null,
43241
+ childCodes: [],
43242
+ ordinal: 1,
43243
+ assertionDomain: "signal_identification",
43244
+ 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`."
43245
+ },
43246
+ {
43247
+ code: "267-002-000-000-000-000-000",
43248
+ key: "screened",
43249
+ title: "Screened",
43250
+ selectable: true,
43251
+ parentCode: null,
43252
+ childCodes: [],
43253
+ ordinal: 2,
43254
+ assertionDomain: "signal_identification",
43255
+ 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`."
43256
+ },
43257
+ {
43258
+ code: "267-003-000-000-000-000-000",
43259
+ key: "at_risk",
43260
+ title: "At risk",
43261
+ selectable: true,
43262
+ parentCode: null,
43263
+ childCodes: [],
43264
+ ordinal: 3,
43265
+ assertionDomain: "signal_identification",
43266
+ 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`."
43267
+ },
43268
+ {
43269
+ code: "267-004-000-000-000-000-000",
43270
+ key: "assessed",
43271
+ title: "Assessed",
43272
+ selectable: true,
43273
+ parentCode: null,
43274
+ childCodes: [],
43275
+ ordinal: 4,
43276
+ assertionDomain: "signal_identification",
43277
+ definition: "Rung 4. A full assessment was completed. Stored `assertion_domain`: `signal_identification`."
43278
+ },
43279
+ {
43280
+ code: "267-005-000-000-000-000-000",
43281
+ key: "determined",
43282
+ title: "Determined",
43283
+ selectable: true,
43284
+ parentCode: null,
43285
+ childCodes: [],
43286
+ ordinal: 5,
43287
+ assertionDomain: "investigative_legal",
43288
+ 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."
43289
+ }
43290
+ ]
43291
+ };
43292
+
43167
43293
  // src/cvcs/adminRoles.v1.0.0.json
43168
43294
  var adminRoles_v1_0_0_default = {
43169
43295
  domain: "admin_roles",
@@ -53612,7 +53738,7 @@ var assertionDomain_v1_1_0_default = {
53612
53738
  domain: "assertion_domain",
53613
53739
  name: "Assertion Domain (CVC-159)",
53614
53740
  version: "2.0.0",
53615
- _status: "CANONICAL \u2014 RENUMBERED 0.8.13 from provisional CVC-964 to canonical CVC-159. Live prototype HEAD a596eb9: `Final CVCs` -> `core - assertion_domain` = CVC-159 (vocab_status 'Ready for dev', Verification 'Verified'), corroborated by 17 `data/cvcs/core_assertion_domain_extensions_*.yaml` files that all declare `cvc: core - assertion_domain`. CVC-159 was freed by deleting the 100%-unbound hand-coded `CVC_159_RELATIONSHIP_TIES` family from `src/constants/ic.ts`; `relationship_ties` keeps its canonical CVC-158. Consumers persist KEYS, not wire codes, so the renumber is compile-clean (regenerate `cvcKeys.ts`). WITHDRAWN in 0.8.13 (all three have ZERO occurrences at prototype HEAD): `romantic_relationship` (964-066) \u2014 upstream the romantic-partner lifecycle routes to `household_relationships`, see `data/cvcs/core_romantic_relationship_change_type.yaml`; `household_tenure` (964-045); `household_composition` (964-067). All three fold into `household_relationships` (554 occurrences at HEAD). NOTE: `romantic_partner` is a relationship-type VALUE code (1,575 occurrences), never an assertion domain \u2014 it is correctly not modelled here. `child_profile` (159-065) is KEPT: 353 occurrences at HEAD. Segment-2 ordinals are preserved across the renumber (gaps at 045/066/067 are intentional; no data migration exists, but stable ordinals keep the diff reviewable). The 37 domains PAVE ships that are absent from the Final CVC-159 export all have substantial upstream occurrence counts and are retained as proposed CVC-159 extensions.",
53741
+ _status: "CANONICAL \u2014 RENUMBERED 0.8.13 from provisional CVC-964 to canonical CVC-159. Live prototype HEAD a596eb9: `Final CVCs` -> `core - assertion_domain` = CVC-159 (vocab_status 'Ready for dev', Verification 'Verified'), corroborated by 17 `data/cvcs/core_assertion_domain_extensions_*.yaml` files that all declare `cvc: core - assertion_domain`. CVC-159 was freed by deleting the 100%-unbound hand-coded `CVC_159_RELATIONSHIP_TIES` family from `src/constants/ic.ts`; `relationship_ties` keeps its canonical CVC-158. Consumers persist KEYS, not wire codes, so the renumber is compile-clean (regenerate `cvcKeys.ts`). WITHDRAWN in 0.8.13 (all three have ZERO occurrences at prototype HEAD): `romantic_relationship` (964-066) \u2014 upstream the romantic-partner lifecycle routes to `household_relationships`, see `data/cvcs/core_romantic_relationship_change_type.yaml`; `household_tenure` (964-045); `household_composition` (964-067). All three fold into `household_relationships` (554 occurrences at HEAD). NOTE: `romantic_partner` is a relationship-type VALUE code (1,575 occurrences), never an assertion domain \u2014 it is correctly not modelled here. `child_profile` (159-065) is KEPT: 353 occurrences at HEAD. Segment-2 ordinals are preserved across the renumber (gaps at 045/066/067 are intentional; no data migration exists, but stable ordinals keep the diff reviewable). The 37 domains PAVE ships that are absent from the Final CVC-159 export all have substantial upstream occurrence counts and are retained as proposed CVC-159 extensions. | 0.8.20: ADDED `signal_identification` (159-066) and `investigative_legal` (159-067) -- retroactive homing of the Track-1 identification-rung emitter live since 2026-08-23; both ratified in the CVC-159 codebook 2026-08-29 (prototype PR #519, hti-features PR #34). Ordinals 066/067 were free: the 0.8.13 withdrawals that reserved those slots were under the OLD CVC-964 numbering and the 159 equivalents were never issued -- verified zero references to 159-066/159-067 anywhere in the repo or the published dist before assigning. The 045 gap remains reserved. The rung VALUE set those two domains carry lives in its own vocabulary (`riskIdentificationMilestone`, CVC-267) rather than as Level-2 rows here: `AssertionDomainKeys` is consumed as THE SET OF DOMAINS, and folding values into it breaks that contract for every consumer -- PAVE's `Record<AssertionDomain, DomainValueVocabulary>` totality gate would demand a domain classification for `on_radar`. CVC-159 stays Level-1 only.",
53616
53742
  _source: "htilabstech/prototype@a596eb9 Final CVCs/Assertion Contract/core - assertion_domain.md (CVC-159) + 17 core_assertion_domain_extensions_*.yaml",
53617
53743
  levels: {
53618
53744
  "0": "Unknown or Missing",
@@ -54234,6 +54360,24 @@ var assertionDomain_v1_1_0_default = {
54234
54360
  parentCode: null,
54235
54361
  childCodes: [],
54236
54362
  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."
54363
+ },
54364
+ {
54365
+ code: "159-066-000-000-000-000-000",
54366
+ key: "signal_identification",
54367
+ title: "Signal / Identification",
54368
+ selectable: true,
54369
+ parentCode: null,
54370
+ childCodes: [],
54371
+ 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."
54372
+ },
54373
+ {
54374
+ code: "159-067-000-000-000-000-000",
54375
+ key: "investigative_legal",
54376
+ title: "Investigative / Legal",
54377
+ selectable: true,
54378
+ parentCode: null,
54379
+ childCodes: [],
54380
+ 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."
54237
54381
  }
54238
54382
  ]
54239
54383
  };
@@ -55784,6 +55928,7 @@ var CVC_197_VALUES = selectableCodes(
55784
55928
  RelationshipTiesKeys,
55785
55929
  ReturnedToAbuserStatusKeys,
55786
55930
  RiskCategoryKeys,
55931
+ RiskIdentificationMilestoneKeys,
55787
55932
  RiskSeverityBandKeys,
55788
55933
  RoiMethodKeys,
55789
55934
  RoiScopeKeys,
@@ -56036,6 +56181,7 @@ var CVC_197_VALUES = selectableCodes(
56036
56181
  resolveRegistryWithInheritance,
56037
56182
  returnedToAbuserStatusSot,
56038
56183
  riskCategorySot,
56184
+ riskIdentificationMilestoneSot,
56039
56185
  riskSeverityBandSot,
56040
56186
  roiMethodSot,
56041
56187
  roiScopeSot,