@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.
@@ -30925,6 +30925,117 @@ var riskSeverityBand_v1_0_0_default = {
30925
30925
  ]
30926
30926
  };
30927
30927
 
30928
+ // src/cvcs/riskIdentificationMilestone.v1.0.0.json
30929
+ var riskIdentificationMilestone_v1_0_0_default = {
30930
+ domain: "risk_identification_milestone",
30931
+ name: "Core Risk Identification Milestone (CVC-267)",
30932
+ version: "1.0.0",
30933
+ _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`.",
30934
+ _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)",
30935
+ levels: {
30936
+ "0": "Unknown or Missing",
30937
+ "1": "Identification funnel rung"
30938
+ },
30939
+ entries: [
30940
+ {
30941
+ code: "267-000-000-000-000-000-000",
30942
+ key: "missingness_root",
30943
+ title: "Unknown, Redacted, or Missing",
30944
+ selectable: false,
30945
+ parentCode: null,
30946
+ childCodes: [
30947
+ "267-000-000-000-000-000-001",
30948
+ "267-000-000-000-000-000-002",
30949
+ "267-000-000-000-000-000-003"
30950
+ ],
30951
+ 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."
30952
+ },
30953
+ {
30954
+ code: "267-000-000-000-000-000-001",
30955
+ key: "unknown",
30956
+ title: "Unknown",
30957
+ selectable: true,
30958
+ parentCode: "267-000-000-000-000-000-000",
30959
+ childCodes: [],
30960
+ canonicalCode: "UNK",
30961
+ 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."
30962
+ },
30963
+ {
30964
+ code: "267-000-000-000-000-000-002",
30965
+ key: "anonymous",
30966
+ title: "Anonymous / declined to answer",
30967
+ selectable: true,
30968
+ parentCode: "267-000-000-000-000-000-000",
30969
+ childCodes: [],
30970
+ definition: "Value is intentionally withheld or redacted. Combines declined-to-answer and redacted/anonymous semantics under the workspace standard ANON sentinel."
30971
+ },
30972
+ {
30973
+ code: "267-000-000-000-000-000-003",
30974
+ key: "data_not_collected",
30975
+ title: "Data not collected",
30976
+ selectable: true,
30977
+ parentCode: "267-000-000-000-000-000-000",
30978
+ childCodes: [],
30979
+ definition: "No attempt was made to collect the value. System-only sentinel per GLOBAL_DESIGN_RULES."
30980
+ },
30981
+ {
30982
+ code: "267-001-000-000-000-000-000",
30983
+ key: "on_radar",
30984
+ title: "On radar",
30985
+ selectable: true,
30986
+ parentCode: null,
30987
+ childCodes: [],
30988
+ ordinal: 1,
30989
+ assertionDomain: "signal_identification",
30990
+ 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`."
30991
+ },
30992
+ {
30993
+ code: "267-002-000-000-000-000-000",
30994
+ key: "screened",
30995
+ title: "Screened",
30996
+ selectable: true,
30997
+ parentCode: null,
30998
+ childCodes: [],
30999
+ ordinal: 2,
31000
+ assertionDomain: "signal_identification",
31001
+ 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`."
31002
+ },
31003
+ {
31004
+ code: "267-003-000-000-000-000-000",
31005
+ key: "at_risk",
31006
+ title: "At risk",
31007
+ selectable: true,
31008
+ parentCode: null,
31009
+ childCodes: [],
31010
+ ordinal: 3,
31011
+ assertionDomain: "signal_identification",
31012
+ 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`."
31013
+ },
31014
+ {
31015
+ code: "267-004-000-000-000-000-000",
31016
+ key: "assessed",
31017
+ title: "Assessed",
31018
+ selectable: true,
31019
+ parentCode: null,
31020
+ childCodes: [],
31021
+ ordinal: 4,
31022
+ assertionDomain: "signal_identification",
31023
+ definition: "Rung 4. A full assessment was completed. Stored `assertion_domain`: `signal_identification`."
31024
+ },
31025
+ {
31026
+ code: "267-005-000-000-000-000-000",
31027
+ key: "determined",
31028
+ title: "Determined",
31029
+ selectable: true,
31030
+ parentCode: null,
31031
+ childCodes: [],
31032
+ ordinal: 5,
31033
+ assertionDomain: "investigative_legal",
31034
+ 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."
31035
+ }
31036
+ ]
31037
+ };
31038
+
30928
31039
  // src/cvcs/adminRoles.v1.0.0.json
30929
31040
  var adminRoles_v1_0_0_default = {
30930
31041
  domain: "admin_roles",
@@ -41373,12 +41484,11 @@ var assertionDomain_v1_1_0_default = {
41373
41484
  domain: "assertion_domain",
41374
41485
  name: "Assertion Domain (CVC-159)",
41375
41486
  version: "2.0.0",
41376
- _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.",
41487
+ _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.",
41377
41488
  _source: "htilabstech/prototype@a596eb9 Final CVCs/Assertion Contract/core - assertion_domain.md (CVC-159) + 17 core_assertion_domain_extensions_*.yaml",
41378
41489
  levels: {
41379
41490
  "0": "Unknown or Missing",
41380
- "1": "CAR assertion domain",
41381
- "2": "CAR assertion value (the vocabulary the domain's assertion_value_code resolves against)"
41491
+ "1": "CAR assertion domain"
41382
41492
  },
41383
41493
  entries: [
41384
41494
  {
@@ -42003,12 +42113,7 @@ var assertionDomain_v1_1_0_default = {
42003
42113
  title: "Signal / Identification",
42004
42114
  selectable: true,
42005
42115
  parentCode: null,
42006
- childCodes: [
42007
- "159-066-001-000-000-000-000",
42008
- "159-066-002-000-000-000-000",
42009
- "159-066-003-000-000-000-000",
42010
- "159-066-004-000-000-000-000"
42011
- ],
42116
+ childCodes: [],
42012
42117
  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."
42013
42118
  },
42014
42119
  {
@@ -42017,55 +42122,8 @@ var assertionDomain_v1_1_0_default = {
42017
42122
  title: "Investigative / Legal",
42018
42123
  selectable: true,
42019
42124
  parentCode: null,
42020
- childCodes: [
42021
- "159-067-001-000-000-000-000"
42022
- ],
42023
- 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."
42024
- },
42025
- {
42026
- code: "159-066-001-000-000-000-000",
42027
- key: "on_radar",
42028
- title: "On radar",
42029
- selectable: true,
42030
- parentCode: "159-066-000-000-000-000-000",
42031
- childCodes: [],
42032
- 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)."
42033
- },
42034
- {
42035
- code: "159-066-002-000-000-000-000",
42036
- key: "screened",
42037
- title: "Screened",
42038
- selectable: true,
42039
- parentCode: "159-066-000-000-000-000-000",
42040
- childCodes: [],
42041
- 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)."
42042
- },
42043
- {
42044
- code: "159-066-003-000-000-000-000",
42045
- key: "at_risk",
42046
- title: "At risk",
42047
- selectable: true,
42048
- parentCode: "159-066-000-000-000-000-000",
42049
- childCodes: [],
42050
- 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."
42051
- },
42052
- {
42053
- code: "159-066-004-000-000-000-000",
42054
- key: "assessed",
42055
- title: "Assessed",
42056
- selectable: true,
42057
- parentCode: "159-066-000-000-000-000-000",
42058
42125
  childCodes: [],
42059
- definition: "Rung 4. A full assessment was completed."
42060
- },
42061
- {
42062
- code: "159-067-001-000-000-000-000",
42063
- key: "determined",
42064
- title: "Determined",
42065
- selectable: true,
42066
- parentCode: "159-067-000-000-000-000-000",
42067
- childCodes: [],
42068
- 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."
42126
+ 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."
42069
42127
  }
42070
42128
  ]
42071
42129
  };
@@ -43348,6 +43406,7 @@ export {
43348
43406
  relationshipTies_v1_0_0_default as relationshipTiesSot,
43349
43407
  returnedToAbuserStatus_v1_0_0_default as returnedToAbuserStatusSot,
43350
43408
  riskCategory_v1_0_0_default as riskCategorySot,
43409
+ riskIdentificationMilestone_v1_0_0_default as riskIdentificationMilestoneSot,
43351
43410
  riskSeverityBand_v1_0_0_default as riskSeverityBandSot,
43352
43411
  roiMethod_v1_0_0_default as roiMethodSot,
43353
43412
  roiScope_v1_0_0_default as roiScopeSot,