@htilabs/platform-common-models 0.8.19 → 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.
@@ -45643,11 +45643,12 @@ var activityType_v1_0_0 = {
45643
45643
  var domain$c = "assertion_domain";
45644
45644
  var name$c = "Assertion Domain (CVC-159)";
45645
45645
  var version$c = "2.0.0";
45646
- var _status$b = "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.";
45646
+ var _status$b = "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.";
45647
45647
  var _source$b = "htilabstech/prototype@a596eb9 Final CVCs/Assertion Contract/core - assertion_domain.md (CVC-159) + 17 core_assertion_domain_extensions_*.yaml";
45648
45648
  var levels$c = {
45649
45649
  "0": "Unknown or Missing",
45650
- "1": "CAR assertion domain"
45650
+ "1": "CAR assertion domain",
45651
+ "2": "CAR assertion value (the vocabulary the domain's assertion_value_code resolves against)"
45651
45652
  };
45652
45653
  var entries$c = [
45653
45654
  {
@@ -46332,6 +46333,81 @@ var entries$c = [
46332
46333
  childCodes: [
46333
46334
  ],
46334
46335
  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."
46336
+ },
46337
+ {
46338
+ code: "159-066-000-000-000-000-000",
46339
+ key: "signal_identification",
46340
+ title: "Signal / Identification",
46341
+ selectable: true,
46342
+ parentCode: null,
46343
+ childCodes: [
46344
+ "159-066-001-000-000-000-000",
46345
+ "159-066-002-000-000-000-000",
46346
+ "159-066-003-000-000-000-000",
46347
+ "159-066-004-000-000-000-000"
46348
+ ],
46349
+ 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."
46350
+ },
46351
+ {
46352
+ code: "159-067-000-000-000-000-000",
46353
+ key: "investigative_legal",
46354
+ title: "Investigative / Legal",
46355
+ selectable: true,
46356
+ parentCode: null,
46357
+ childCodes: [
46358
+ "159-067-001-000-000-000-000"
46359
+ ],
46360
+ 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."
46361
+ },
46362
+ {
46363
+ code: "159-066-001-000-000-000-000",
46364
+ key: "on_radar",
46365
+ title: "On radar",
46366
+ selectable: true,
46367
+ parentCode: "159-066-000-000-000-000-000",
46368
+ childCodes: [
46369
+ ],
46370
+ 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)."
46371
+ },
46372
+ {
46373
+ code: "159-066-002-000-000-000-000",
46374
+ key: "screened",
46375
+ title: "Screened",
46376
+ selectable: true,
46377
+ parentCode: "159-066-000-000-000-000-000",
46378
+ childCodes: [
46379
+ ],
46380
+ 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)."
46381
+ },
46382
+ {
46383
+ code: "159-066-003-000-000-000-000",
46384
+ key: "at_risk",
46385
+ title: "At risk",
46386
+ selectable: true,
46387
+ parentCode: "159-066-000-000-000-000-000",
46388
+ childCodes: [
46389
+ ],
46390
+ 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."
46391
+ },
46392
+ {
46393
+ code: "159-066-004-000-000-000-000",
46394
+ key: "assessed",
46395
+ title: "Assessed",
46396
+ selectable: true,
46397
+ parentCode: "159-066-000-000-000-000-000",
46398
+ childCodes: [
46399
+ ],
46400
+ definition: "Rung 4. A full assessment was completed."
46401
+ },
46402
+ {
46403
+ code: "159-067-001-000-000-000-000",
46404
+ key: "determined",
46405
+ title: "Determined",
46406
+ selectable: true,
46407
+ parentCode: "159-067-000-000-000-000-000",
46408
+ childCodes: [
46409
+ ],
46410
+ 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."
46335
46411
  }
46336
46412
  ];
46337
46413
  var assertionDomain_v1_1_0 = {
@@ -45643,11 +45643,12 @@ var activityType_v1_0_0 = {
45643
45643
  var domain$c = "assertion_domain";
45644
45644
  var name$c = "Assertion Domain (CVC-159)";
45645
45645
  var version$c = "2.0.0";
45646
- var _status$b = "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.";
45646
+ var _status$b = "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.";
45647
45647
  var _source$b = "htilabstech/prototype@a596eb9 Final CVCs/Assertion Contract/core - assertion_domain.md (CVC-159) + 17 core_assertion_domain_extensions_*.yaml";
45648
45648
  var levels$c = {
45649
45649
  "0": "Unknown or Missing",
45650
- "1": "CAR assertion domain"
45650
+ "1": "CAR assertion domain",
45651
+ "2": "CAR assertion value (the vocabulary the domain's assertion_value_code resolves against)"
45651
45652
  };
45652
45653
  var entries$c = [
45653
45654
  {
@@ -46332,6 +46333,81 @@ var entries$c = [
46332
46333
  childCodes: [
46333
46334
  ],
46334
46335
  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."
46336
+ },
46337
+ {
46338
+ code: "159-066-000-000-000-000-000",
46339
+ key: "signal_identification",
46340
+ title: "Signal / Identification",
46341
+ selectable: true,
46342
+ parentCode: null,
46343
+ childCodes: [
46344
+ "159-066-001-000-000-000-000",
46345
+ "159-066-002-000-000-000-000",
46346
+ "159-066-003-000-000-000-000",
46347
+ "159-066-004-000-000-000-000"
46348
+ ],
46349
+ 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."
46350
+ },
46351
+ {
46352
+ code: "159-067-000-000-000-000-000",
46353
+ key: "investigative_legal",
46354
+ title: "Investigative / Legal",
46355
+ selectable: true,
46356
+ parentCode: null,
46357
+ childCodes: [
46358
+ "159-067-001-000-000-000-000"
46359
+ ],
46360
+ 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."
46361
+ },
46362
+ {
46363
+ code: "159-066-001-000-000-000-000",
46364
+ key: "on_radar",
46365
+ title: "On radar",
46366
+ selectable: true,
46367
+ parentCode: "159-066-000-000-000-000-000",
46368
+ childCodes: [
46369
+ ],
46370
+ 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)."
46371
+ },
46372
+ {
46373
+ code: "159-066-002-000-000-000-000",
46374
+ key: "screened",
46375
+ title: "Screened",
46376
+ selectable: true,
46377
+ parentCode: "159-066-000-000-000-000-000",
46378
+ childCodes: [
46379
+ ],
46380
+ 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)."
46381
+ },
46382
+ {
46383
+ code: "159-066-003-000-000-000-000",
46384
+ key: "at_risk",
46385
+ title: "At risk",
46386
+ selectable: true,
46387
+ parentCode: "159-066-000-000-000-000-000",
46388
+ childCodes: [
46389
+ ],
46390
+ 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."
46391
+ },
46392
+ {
46393
+ code: "159-066-004-000-000-000-000",
46394
+ key: "assessed",
46395
+ title: "Assessed",
46396
+ selectable: true,
46397
+ parentCode: "159-066-000-000-000-000-000",
46398
+ childCodes: [
46399
+ ],
46400
+ definition: "Rung 4. A full assessment was completed."
46401
+ },
46402
+ {
46403
+ code: "159-067-001-000-000-000-000",
46404
+ key: "determined",
46405
+ title: "Determined",
46406
+ selectable: true,
46407
+ parentCode: "159-067-000-000-000-000-000",
46408
+ childCodes: [
46409
+ ],
46410
+ 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."
46335
46411
  }
46336
46412
  ];
46337
46413
  var assertionDomain_v1_1_0 = {
@@ -41373,11 +41373,12 @@ var assertionDomain_v1_1_0_default = {
41373
41373
  domain: "assertion_domain",
41374
41374
  name: "Assertion Domain (CVC-159)",
41375
41375
  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.",
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.",
41377
41377
  _source: "htilabstech/prototype@a596eb9 Final CVCs/Assertion Contract/core - assertion_domain.md (CVC-159) + 17 core_assertion_domain_extensions_*.yaml",
41378
41378
  levels: {
41379
41379
  "0": "Unknown or Missing",
41380
- "1": "CAR assertion domain"
41380
+ "1": "CAR assertion domain",
41381
+ "2": "CAR assertion value (the vocabulary the domain's assertion_value_code resolves against)"
41381
41382
  },
41382
41383
  entries: [
41383
41384
  {
@@ -41995,6 +41996,76 @@ var assertionDomain_v1_1_0_default = {
41995
41996
  parentCode: null,
41996
41997
  childCodes: [],
41997
41998
  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."
41999
+ },
42000
+ {
42001
+ code: "159-066-000-000-000-000-000",
42002
+ key: "signal_identification",
42003
+ title: "Signal / Identification",
42004
+ selectable: true,
42005
+ 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
+ ],
42012
+ 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
+ },
42014
+ {
42015
+ code: "159-067-000-000-000-000-000",
42016
+ key: "investigative_legal",
42017
+ title: "Investigative / Legal",
42018
+ selectable: true,
42019
+ 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
+ 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."
41998
42069
  }
41999
42070
  ]
42000
42071
  };