@htilabs/platform-common-models 0.8.20 → 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.
@@ -149,6 +149,7 @@ __export(cvcs_exports, {
149
149
  relationshipTiesSot: () => relationshipTies_v1_0_0_default,
150
150
  returnedToAbuserStatusSot: () => returnedToAbuserStatus_v1_0_0_default,
151
151
  riskCategorySot: () => riskCategory_v1_0_0_default,
152
+ riskIdentificationMilestoneSot: () => riskIdentificationMilestone_v1_0_0_default,
152
153
  riskSeverityBandSot: () => riskSeverityBand_v1_0_0_default,
153
154
  roiMethodSot: () => roiMethod_v1_0_0_default,
154
155
  roiScopeSot: () => roiScope_v1_0_0_default,
@@ -31128,6 +31129,117 @@ var riskSeverityBand_v1_0_0_default = {
31128
31129
  ]
31129
31130
  };
31130
31131
 
31132
+ // src/cvcs/riskIdentificationMilestone.v1.0.0.json
31133
+ var riskIdentificationMilestone_v1_0_0_default = {
31134
+ domain: "risk_identification_milestone",
31135
+ name: "Core Risk Identification Milestone (CVC-267)",
31136
+ version: "1.0.0",
31137
+ _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`.",
31138
+ _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)",
31139
+ levels: {
31140
+ "0": "Unknown or Missing",
31141
+ "1": "Identification funnel rung"
31142
+ },
31143
+ entries: [
31144
+ {
31145
+ code: "267-000-000-000-000-000-000",
31146
+ key: "missingness_root",
31147
+ title: "Unknown, Redacted, or Missing",
31148
+ selectable: false,
31149
+ parentCode: null,
31150
+ childCodes: [
31151
+ "267-000-000-000-000-000-001",
31152
+ "267-000-000-000-000-000-002",
31153
+ "267-000-000-000-000-000-003"
31154
+ ],
31155
+ 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."
31156
+ },
31157
+ {
31158
+ code: "267-000-000-000-000-000-001",
31159
+ key: "unknown",
31160
+ title: "Unknown",
31161
+ selectable: true,
31162
+ parentCode: "267-000-000-000-000-000-000",
31163
+ childCodes: [],
31164
+ canonicalCode: "UNK",
31165
+ 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."
31166
+ },
31167
+ {
31168
+ code: "267-000-000-000-000-000-002",
31169
+ key: "anonymous",
31170
+ title: "Anonymous / declined to answer",
31171
+ selectable: true,
31172
+ parentCode: "267-000-000-000-000-000-000",
31173
+ childCodes: [],
31174
+ definition: "Value is intentionally withheld or redacted. Combines declined-to-answer and redacted/anonymous semantics under the workspace standard ANON sentinel."
31175
+ },
31176
+ {
31177
+ code: "267-000-000-000-000-000-003",
31178
+ key: "data_not_collected",
31179
+ title: "Data not collected",
31180
+ selectable: true,
31181
+ parentCode: "267-000-000-000-000-000-000",
31182
+ childCodes: [],
31183
+ definition: "No attempt was made to collect the value. System-only sentinel per GLOBAL_DESIGN_RULES."
31184
+ },
31185
+ {
31186
+ code: "267-001-000-000-000-000-000",
31187
+ key: "on_radar",
31188
+ title: "On radar",
31189
+ selectable: true,
31190
+ parentCode: null,
31191
+ childCodes: [],
31192
+ ordinal: 1,
31193
+ assertionDomain: "signal_identification",
31194
+ 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`."
31195
+ },
31196
+ {
31197
+ code: "267-002-000-000-000-000-000",
31198
+ key: "screened",
31199
+ title: "Screened",
31200
+ selectable: true,
31201
+ parentCode: null,
31202
+ childCodes: [],
31203
+ ordinal: 2,
31204
+ assertionDomain: "signal_identification",
31205
+ 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`."
31206
+ },
31207
+ {
31208
+ code: "267-003-000-000-000-000-000",
31209
+ key: "at_risk",
31210
+ title: "At risk",
31211
+ selectable: true,
31212
+ parentCode: null,
31213
+ childCodes: [],
31214
+ ordinal: 3,
31215
+ assertionDomain: "signal_identification",
31216
+ 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`."
31217
+ },
31218
+ {
31219
+ code: "267-004-000-000-000-000-000",
31220
+ key: "assessed",
31221
+ title: "Assessed",
31222
+ selectable: true,
31223
+ parentCode: null,
31224
+ childCodes: [],
31225
+ ordinal: 4,
31226
+ assertionDomain: "signal_identification",
31227
+ definition: "Rung 4. A full assessment was completed. Stored `assertion_domain`: `signal_identification`."
31228
+ },
31229
+ {
31230
+ code: "267-005-000-000-000-000-000",
31231
+ key: "determined",
31232
+ title: "Determined",
31233
+ selectable: true,
31234
+ parentCode: null,
31235
+ childCodes: [],
31236
+ ordinal: 5,
31237
+ assertionDomain: "investigative_legal",
31238
+ 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."
31239
+ }
31240
+ ]
31241
+ };
31242
+
31131
31243
  // src/cvcs/adminRoles.v1.0.0.json
31132
31244
  var adminRoles_v1_0_0_default = {
31133
31245
  domain: "admin_roles",
@@ -41576,12 +41688,11 @@ var assertionDomain_v1_1_0_default = {
41576
41688
  domain: "assertion_domain",
41577
41689
  name: "Assertion Domain (CVC-159)",
41578
41690
  version: "2.0.0",
41579
- _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 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.",
41691
+ _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.",
41580
41692
  _source: "htilabstech/prototype@a596eb9 Final CVCs/Assertion Contract/core - assertion_domain.md (CVC-159) + 17 core_assertion_domain_extensions_*.yaml",
41581
41693
  levels: {
41582
41694
  "0": "Unknown or Missing",
41583
- "1": "CAR assertion domain",
41584
- "2": "CAR assertion value (the vocabulary the domain's assertion_value_code resolves against)"
41695
+ "1": "CAR assertion domain"
41585
41696
  },
41586
41697
  entries: [
41587
41698
  {
@@ -42206,12 +42317,7 @@ var assertionDomain_v1_1_0_default = {
42206
42317
  title: "Signal / Identification",
42207
42318
  selectable: true,
42208
42319
  parentCode: null,
42209
- childCodes: [
42210
- "159-066-001-000-000-000-000",
42211
- "159-066-002-000-000-000-000",
42212
- "159-066-003-000-000-000-000",
42213
- "159-066-004-000-000-000-000"
42214
- ],
42320
+ childCodes: [],
42215
42321
  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."
42216
42322
  },
42217
42323
  {
@@ -42220,55 +42326,8 @@ var assertionDomain_v1_1_0_default = {
42220
42326
  title: "Investigative / Legal",
42221
42327
  selectable: true,
42222
42328
  parentCode: null,
42223
- childCodes: [
42224
- "159-067-001-000-000-000-000"
42225
- ],
42226
- 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."
42227
- },
42228
- {
42229
- code: "159-066-001-000-000-000-000",
42230
- key: "on_radar",
42231
- title: "On radar",
42232
- selectable: true,
42233
- parentCode: "159-066-000-000-000-000-000",
42234
- childCodes: [],
42235
- 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)."
42236
- },
42237
- {
42238
- code: "159-066-002-000-000-000-000",
42239
- key: "screened",
42240
- title: "Screened",
42241
- selectable: true,
42242
- parentCode: "159-066-000-000-000-000-000",
42243
- childCodes: [],
42244
- 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)."
42245
- },
42246
- {
42247
- code: "159-066-003-000-000-000-000",
42248
- key: "at_risk",
42249
- title: "At risk",
42250
- selectable: true,
42251
- parentCode: "159-066-000-000-000-000-000",
42252
- childCodes: [],
42253
- 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."
42254
- },
42255
- {
42256
- code: "159-066-004-000-000-000-000",
42257
- key: "assessed",
42258
- title: "Assessed",
42259
- selectable: true,
42260
- parentCode: "159-066-000-000-000-000-000",
42261
42329
  childCodes: [],
42262
- definition: "Rung 4. A full assessment was completed."
42263
- },
42264
- {
42265
- code: "159-067-001-000-000-000-000",
42266
- key: "determined",
42267
- title: "Determined",
42268
- selectable: true,
42269
- parentCode: "159-067-000-000-000-000-000",
42270
- childCodes: [],
42271
- 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."
42330
+ 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."
42272
42331
  }
42273
42332
  ]
42274
42333
  };
@@ -43552,6 +43611,7 @@ var criminalOrgCategory_v1_0_0_default = {
43552
43611
  relationshipTiesSot,
43553
43612
  returnedToAbuserStatusSot,
43554
43613
  riskCategorySot,
43614
+ riskIdentificationMilestoneSot,
43555
43615
  riskSeverityBandSot,
43556
43616
  roiMethodSot,
43557
43617
  roiScopeSot,