@htilabs/platform-common-models 0.14.0 → 0.17.0

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.
Files changed (39) hide show
  1. package/dist/{cvcEntry-0BIB9sen.d.cts → cvcEntry-ctHTp2df.d.cts} +36 -36
  2. package/dist/{cvcEntry-0BIB9sen.d.ts → cvcEntry-ctHTp2df.d.ts} +36 -36
  3. package/dist/cvcs/index.cjs +184 -40
  4. package/dist/cvcs/index.cjs.map +1 -1
  5. package/dist/cvcs/index.d.cts +191 -41
  6. package/dist/cvcs/index.d.ts +191 -41
  7. package/dist/cvcs/index.js +184 -40
  8. package/dist/cvcs/index.js.map +1 -1
  9. package/dist/enums/index.cjs +3 -1
  10. package/dist/enums/index.cjs.map +1 -1
  11. package/dist/enums/index.d.cts +8 -6
  12. package/dist/enums/index.d.ts +8 -6
  13. package/dist/enums/index.js +3 -1
  14. package/dist/enums/index.js.map +1 -1
  15. package/dist/{index-CDoqrfc1.d.ts → index-4DiJrn7y.d.ts} +1 -1
  16. package/dist/{index-Zu_mOJRn.d.cts → index-qreOzXYS.d.cts} +1 -1
  17. package/dist/index.cjs +187 -41
  18. package/dist/index.cjs.map +1 -1
  19. package/dist/index.d.cts +2 -2
  20. package/dist/index.d.ts +2 -2
  21. package/dist/index.js +187 -41
  22. package/dist/index.js.map +1 -1
  23. package/dist/models/index.d.cts +2 -2
  24. package/dist/models/index.d.ts +2 -2
  25. package/dist/schemas/index.d.cts +11 -11
  26. package/dist/schemas/index.d.ts +11 -11
  27. package/package.json +27 -26
  28. package/src/__tests__/__snapshots__/cvc-sot.snap +5 -5
  29. package/src/__tests__/core-functions-canon.test.ts +53 -0
  30. package/src/__tests__/core-information-scope-invariant.test.ts +298 -19
  31. package/src/__tests__/cvc-sot-snapshot.test.ts +19 -12
  32. package/src/__tests__/cvc-status-parser.test.ts +1 -1
  33. package/src/__tests__/cvc-structural.test.ts +3 -3
  34. package/src/__tests__/location-type-routing-invariant.test.ts +1 -1
  35. package/src/cvcs/{coreFunctions.v1.0.0.json → coreFunctions.v1.1.0.json} +11 -2
  36. package/src/cvcs/{coreInformationScope.v1.0.0.json → coreInformationScope.v1.1.0.json} +113 -22
  37. package/src/cvcs/index.ts +3 -3
  38. package/src/cvcs/{roiScope.v1.0.0.json → roiScope.v1.2.0.json} +51 -7
  39. package/src/generated/cvc-enums.ts +8 -6
@@ -1,13 +1,97 @@
1
1
  {
2
2
  "domain": "core_information_scope",
3
3
  "name": "Core Information Scope",
4
- "version": "1.0.0",
5
- "_status": "DRAFT: canonical number 236, self-declared by the source YAML (`cvc_id: CVC-236`); CVC_INDEX.md carries no row for it yet, so the drift gate classifies it INDEX_ABSENT. Sourced from canonical CVC-236 `core_information_scope` v2 (authored 2026-08-13, restructured 2026-08-14): 12 categories / 56 units. TWO GRAINS, deliberately modelled as hierarchy: L1 categories are the POLICY grain and are NOT selectable; L2 units are the AUTHORIZATION grain and are what an ROI or a share actually authorizes. This is the axis the sibling `roi_scope` domain deliberately omits — `roi_scope` is the flat item vocabulary, and its 27 substantive keys are a strict SUBSET of the 56 units here, with no renames and no collisions. That subset relationship is what makes adopting this domain additive: every stored ROI keeps its exact recorded meaning. `safe_locations` is CANON since CVC236-AUDIT R1 (Crysta, 2026-09-08): id and label ratified and minted in the Notion codebook; the former PROVISIONAL marker is retired. PENDING canonical Notion authoring + steward ratification.",
6
- "_source": "htilabstech/prototype/data/cvcs/core_information_scope.yaml @ 55088d44 (CVC-236 v2, restructured 2026-08-14, amended 2026-10-01; read from 46a60114; structural columns cross-checked against htilabstech/prototype/Final CVCs/System Roles, Permissions, & Account Management (IC-66)/core-information_scope — codebook.csv @ 55088d44)",
4
+ "version": "1.1.0",
5
+ "_status": "DRAFT: canonical number 236, self-declared by the source YAML (`cvc_id: CVC-236`); CVC_INDEX.md carries no row for it yet, so the drift gate classifies it INDEX_ABSENT. Sourced from canonical CVC-236 `core_information_scope` v2 (authored 2026-08-13, restructured 2026-08-14): 12 categories / 55 live units + 2 retired tombstones. TWO GRAINS, deliberately modelled as hierarchy: L1 categories are the POLICY grain and are NOT selectable; L2 units are the AUTHORIZATION grain and are what an ROI or a share actually authorizes. This is the axis the sibling `roi_scope` domain deliberately omits — `roi_scope` is the flat item vocabulary, and every one of its 27 substantive keys resolves here, spelled identically, with no renames and no collisions. That is what makes adopting this domain a migration rather than a re-consent: a stored ROI never WIDENS. RETIRED TOMBSTONES: `screen_notes` (236-005-001, retired 2026-10-05, Narrative notes, signed Spec v2 rule 5); `background` (236-005-003, retired 2026-10-05, Narrative notes, signed Spec v2 rule 5). Each keeps its published code (never reused), is `selectable: false` + `retired: true`, and includes nothing: a stored ROI or share that names one resolves to \"retired\", not \"unknown\". Unit codes follow the generator's frozen ledger, not canon's display order: a new unit APPENDS inside its category. VERSION 1.1.0 supersedes 1.0.0 because the change is not additive (see `_supersedes`); neither version was seeded in platform-prod or platform-dev when it was minted (checked 2026-10-06), so the bump is the convention (ADR-CVC-0.8.13 Addendum 2026-10-05), not a guard-driven fix. `safe_locations` is CANON since CVC236-AUDIT R1 (Crysta, 2026-09-08): id and label ratified and minted in the Notion codebook; the former PROVISIONAL marker is retired. The Notion codebook is AHEAD of the yaml mirror on `instruments` (31 rows, acknowledged via --allow-codebook-ahead and not exported here), pending its own absorb lane. PENDING canonical Notion authoring + steward ratification.",
6
+ "_source": "htilabstech/prototype/data/cvcs/core_information_scope.yaml @ 9ef79748 (CVC-236 v2, restructured 2026-08-14, amended 2026-10-01; read from origin/main; structural columns cross-checked against htilabstech/prototype/Final CVCs/System Roles, Permissions, & Account Management (IC-66)/core-information_scope — codebook.csv @ 9ef79748; 2 retired codebook rows matched to the yaml's retired_units; 31 codebook-ahead rows under instruments acknowledged, not exported)",
7
+ "_supersedes": {
8
+ "version": "1.0.0",
9
+ "keyMap": {
10
+ "missingness_root": "missingness_root",
11
+ "unknown": "unknown",
12
+ "anonymous": "anonymous",
13
+ "data_not_collected": "data_not_collected",
14
+ "identifying": "identifying",
15
+ "names": "names",
16
+ "dob": "dob",
17
+ "addresses": "addresses",
18
+ "additional_ids": "additional_ids",
19
+ "demographics": "demographics",
20
+ "risk": "risk",
21
+ "screen_indicators": "screen_indicators",
22
+ "victimization": "victimization",
23
+ "ida_full": "ida_full",
24
+ "ida_consid": "ida_consid",
25
+ "initial_screen": "initial_screen",
26
+ "tra": "tra",
27
+ "lap": "lap",
28
+ "danger_assessment": "danger_assessment",
29
+ "injury_and_strangulation": "injury_and_strangulation",
30
+ "stalking_assessment": "stalking_assessment",
31
+ "ae_intake": "ae_intake",
32
+ "hope_scale": "hope_scale",
33
+ "assessment_records": "assessment_records",
34
+ "determinations": "determinations",
35
+ "offender_facilitator": "offender_facilitator",
36
+ "system_involvement": "system_involvement",
37
+ "derived_risk_signals": "derived_risk_signals",
38
+ "contact": "contact",
39
+ "contact_info": "contact_info",
40
+ "safe_locations": "safe_locations",
41
+ "priorities_safety": "priorities_safety",
42
+ "encounter_location": "encounter_location",
43
+ "services": "services",
44
+ "contact_history": "contact_history",
45
+ "service_history": "service_history",
46
+ "plans_goals": "plans_goals",
47
+ "notes": "notes",
48
+ "screen_notes": "screen_notes",
49
+ "case_notes": "case_notes",
50
+ "background": "background",
51
+ "health_accommodation": "health_accommodation",
52
+ "accommodation_needs": "accommodation_needs",
53
+ "disability_subtypes": "disability_subtypes",
54
+ "mental_health_status": "mental_health_status",
55
+ "substance_use_status": "substance_use_status",
56
+ "chronic_health_status": "chronic_health_status",
57
+ "hiv_status": "hiv_status",
58
+ "mental_health_screen": "mental_health_screen",
59
+ "trauma_and_coping_screen": "trauma_and_coping_screen",
60
+ "behavioral_health_intake": "behavioral_health_intake",
61
+ "immigration_legal_status": "immigration_legal_status",
62
+ "immigration_status": "immigration_status",
63
+ "uscis_alien_number": "uscis_alien_number",
64
+ "federal_protection_applications": "federal_protection_applications",
65
+ "tvap_enrollment": "tvap_enrollment",
66
+ "le_report_status": "le_report_status",
67
+ "system": "system",
68
+ "system_info": "system_info",
69
+ "network_associations": "network_associations",
70
+ "network_membership": "network_membership",
71
+ "persona_links": "persona_links",
72
+ "commercial_activity": "commercial_activity",
73
+ "ad_content": "ad_content",
74
+ "commercial_patterns": "commercial_patterns",
75
+ "investigative_work_product": "investigative_work_product",
76
+ "case_determinations": "case_determinations",
77
+ "case_lifecycle": "case_lifecycle",
78
+ "case_attachments": "case_attachments",
79
+ "object_identifiers": "object_identifiers",
80
+ "phone_identifiers": "phone_identifiers",
81
+ "object_identity_attributes": "object_identity_attributes"
82
+ },
83
+ "retiredCodes": [],
84
+ "notes": {
85
+ "summary": "Every v1.0.0 key is still an entry in v1.1.0, at its v1.0.0 code, so `keyMap` is the identity and `retiredCodes` is empty: no code was withdrawn. Non-additive because 2 published unit(s) are now RETIRED tombstones and 1 unit(s) read narrower (notes below). Added: `session_summary` (236-005-004).",
86
+ "screen_notes": "v1.0.0 `screen_notes` was a selectable unit. Retired 2026-10-05 (Narrative notes, signed Spec v2 rule 5): The Initial Screen's notes box is an instrument note and belongs to the Initial Screen. It stays at 236-005-001 as a tombstone (`selectable: false`, `retired: true`) with NO successor key, and includes nothing — a stored ROI or share that names it narrows, never widens. Canon records that only demo data named it (Crysta 2026-10-04); the demo presets were rewritten by hand.",
87
+ "background": "v1.0.0 `background` was a selectable unit. Retired 2026-10-05 (Narrative notes, signed Spec v2 rule 5): Nothing ever captured it. It stays at 236-005-003 as a tombstone (`selectable: false`, `retired: true`) with NO successor key, and includes nothing — a stored ROI or share that names it narrows, never widens. Canon records that only demo data named it (Crysta 2026-10-04); the demo presets were rewritten by hand.",
88
+ "case_notes": "v1.0.0 `case_notes` ('Detailed case notes') keeps 236-005-002 but reads NARROWER under its new label 'Session & case notes' (renamed + narrowed 2026-10-02, Crysta; signed 2026-10-05, Narrative notes Spec v2 rule 5): every note whose home is a session of the case or the case itself, OTHER THAN the session summary, with its files. The session summary (the typed summary and each note marked 'Include in session summary') now rides the new `session_summary` unit (236-005-004), and a note written inside an instrument, in the Determination notes box, or in a notes box on another record belongs to that record. A stored ROI or share that authorized `case_notes` therefore no longer includes the session summary; whether it should also gain `session_summary` is a consent question for the consumer, not a mapping."
89
+ }
90
+ },
7
91
  "levels": {
8
92
  "0": "Unknown or Missing",
9
93
  "1": "Category (policy grain, not selectable)",
10
- "2": "Information unit (authorization grain, selectable)"
94
+ "2": "Information unit (authorization grain; selectable unless retired)"
11
95
  },
12
96
  "entries": [
13
97
  {
@@ -423,10 +507,11 @@
423
507
  "selectable": true,
424
508
  "parentCode": "236-002-000-000-000-000-000",
425
509
  "childCodes": [],
426
- "definition": "Offender + facilitator records. Category `risk`. Carries TRA perpetrator records (ruled 2026-08-14): content wins — third-party identity never rides a subject-instrument disclosure silently.",
510
+ "definition": "Offender + facilitator records. Category `risk`. Carries TRA perpetrator records (ruled 2026-08-14): content wins — third-party identity never rides a subject-instrument disclosure silently. | THREAD ADDED 2026-10-01 (OFFENDER-SYSTEM-UNITS-THREAD, Crysta R1 — Nate Luginbill's Question set 2 item 4): app_relevance follows where the unit's content is captured, and Thread captures perpetrator records (identity · description · vehicle · violence history in PAVE 2.0's Thread; in the prototype a relevant person with the offender role-in-case + the Priorities Q1 source of the danger). The 2026-08-14 rule was never Thread-exempt — Thread had no box, so perpetrator identity rode under the victim's `names`; with the box it rides HERE and comes out of names (R2). The offender PROFILE never rides under system_involvement because a protection order names them (R3).",
427
511
  "levelFloor": 3,
428
512
  "appRelevance": [
429
513
  "PAVE",
514
+ "Thread",
430
515
  "LEADS"
431
516
  ],
432
517
  "shareableDefault": true,
@@ -439,10 +524,11 @@
439
524
  "selectable": true,
440
525
  "parentCode": "236-002-000-000-000-000-000",
441
526
  "childCodes": [],
442
- "definition": "System involvement. Category `risk`.",
527
+ "definition": "System involvement. Category `risk`. THREAD ADDED 2026-10-01 (OFFENDER-SYSTEM-UNITS-THREAD, Crysta R1): Thread captures protection orders and system-involvement answers in PAVE 2.0; the [PAVE] flag was the record as of 2026-08-14. R3 (protection orders — canon holds, no split): a protection order is ONE record under this unit, whole — the survivor's legal protection (petitioner · court · status · expiry · violations) with the respondent's name as it appears on the order, a court document; an offender profile may REFERENCE the order (the ADR's 'offender-bundle extension' is a presentation), but the order is delivered only when this unit is granted — a reference carries no content, the referenced record rides its own unit (the 2026-10-01 safety-plan reference rule).",
443
528
  "levelFloor": 3,
444
529
  "appRelevance": [
445
- "PAVE"
530
+ "PAVE",
531
+ "Thread"
446
532
  ],
447
533
  "shareableDefault": true,
448
534
  "specialDataType": "survivor_confidential"
@@ -575,7 +661,7 @@
575
661
  "selectable": true,
576
662
  "parentCode": "236-004-000-000-000-000-000",
577
663
  "childCodes": [],
578
- "definition": "Contact history with this agency. Category `services`. Honest-empty (§ 5.4): no canonical UDD field carries the interaction register yet.",
664
+ "definition": "Contact history with this agency. Category `services`. DELIVERS since 2026-10-01 (CONTACT-HISTORY-REGISTER, Crysta R1–R3 — Nate Luginbill's Question set 2 item 3; honest-empty from 2026-08-14 to that date): the register of this agency's own contacts with the person — one row per session, date · channel (CVC-47) · kind of sitting (CVC-217) · the agency/program as recorded, plus a count line — computed from the SENDING agency's session records at send time by the one as-delivered builder, never stored (UDD person.contact_history, derived · accumulating_log · IC-76; source fields capture.session_started_at · capture.service_delivery_channel [its session-record store `contact_method`] · capture.session_template). The fact of contact, not content: no notes, answers, outcomes or services — service_history carries the service instances (the Thread session-as-service row is the same session's other view). Which sessions: closed plus the sending one; drafts from other days, discarded sessions, inbound-share reviews (origin claimed_share), other agencies' sessions (knowing is not telling) and LEADS sessions never ride. No domain_map row — sessions are no-CAR facts; the coverage gate reads the crosswalk derived_units entry (field + store + builder marker). Presets: Thread risk_only_handoff (carried it throughout) · ROI full_collab gains it 2026-10-01 (derivation for veto). Smoke FLOW-381.",
579
665
  "levelFloor": 3,
580
666
  "appRelevance": [
581
667
  "PAVE",
@@ -625,9 +711,10 @@
625
711
  "childCodes": [
626
712
  "236-005-001-000-000-000-000",
627
713
  "236-005-002-000-000-000-000",
628
- "236-005-003-000-000-000-000"
714
+ "236-005-003-000-000-000-000",
715
+ "236-005-004-000-000-000-000"
629
716
  ],
630
- "definition": "Narrative notes — policy-grain category. Units under it are the authorization grain. LEADS flag dropped 2026-08-14 (all units PAVE/Thread — was an empty shell for LEADS-only agencies).",
717
+ "definition": "Narrative notes — policy-grain category. Units under it are the authorization grain. LEADS flag dropped 2026-08-14 (all units PAVE/Thread — was an empty shell for LEADS-only agencies). | NARRATIVE-NOTES 2026-10-05 (signed Spec v2, rule 5 — Crysta: 'Narrative notes - I've signed off on this spec.'): two sub-categories, Session summary and Session & case notes. It holds only the notes whose home is a session of the case or the case itself; a note written inside an instrument, in the Determination notes box, or in a notes box on another record belongs to that record.",
631
718
  "levelFloor": 3,
632
719
  "appRelevance": [
633
720
  "PAVE",
@@ -640,26 +727,20 @@
640
727
  "code": "236-005-001-000-000-000-000",
641
728
  "key": "screen_notes",
642
729
  "title": "Screen notes",
643
- "selectable": true,
730
+ "selectable": false,
644
731
  "parentCode": "236-005-000-000-000-000-000",
645
732
  "childCodes": [],
646
- "definition": "Screen notes. Category `notes`.",
647
- "levelFloor": 3,
648
- "appRelevance": [
649
- "PAVE",
650
- "Thread"
651
- ],
652
- "shareableDefault": true,
653
- "specialDataType": "survivor_confidential"
733
+ "definition": "RETIRED 2026-10-05 (Narrative notes, signed Spec v2 rule 5). The Initial Screen's notes box is an instrument note and belongs to the Initial Screen. No longer offered in share policy, internal viewing settings or a release; a stored code resolves here so a reader can tell retired from unknown, and includes nothing.",
734
+ "retired": true
654
735
  },
655
736
  {
656
737
  "code": "236-005-002-000-000-000-000",
657
738
  "key": "case_notes",
658
- "title": "Detailed case notes",
739
+ "title": "Session & case notes",
659
740
  "selectable": true,
660
741
  "parentCode": "236-005-000-000-000-000-000",
661
742
  "childCodes": [],
662
- "definition": "Detailed case notes. Category `notes`.",
743
+ "definition": "Session & case notes. Category `notes`. RENAMED + NARROWED 2026-10-02 (Crysta; was 'Detailed case notes'; the code is unchanged). Every note whose home is a session of the case or the case itself, other than the session summary, with its files. Read from the notes store, one row per note, through the note's own visibility; the session_note / log_entry claims keep their viewing rows in domain_map and are never share content.",
663
744
  "levelFloor": 3,
664
745
  "appRelevance": [
665
746
  "PAVE",
@@ -672,10 +753,20 @@
672
753
  "code": "236-005-003-000-000-000-000",
673
754
  "key": "background",
674
755
  "title": "Background information",
756
+ "selectable": false,
757
+ "parentCode": "236-005-000-000-000-000-000",
758
+ "childCodes": [],
759
+ "definition": "RETIRED 2026-10-05 (Narrative notes, signed Spec v2 rule 5). Nothing ever captured it. No longer offered in share policy, internal viewing settings or a release; a stored code resolves here so a reader can tell retired from unknown, and includes nothing.",
760
+ "retired": true
761
+ },
762
+ {
763
+ "code": "236-005-004-000-000-000-000",
764
+ "key": "session_summary",
765
+ "title": "Session summary",
675
766
  "selectable": true,
676
767
  "parentCode": "236-005-000-000-000-000-000",
677
768
  "childCodes": [],
678
- "definition": "Background information. Category `notes`.",
769
+ "definition": "Session summary. Category `notes`. MINTED 2026-10-02 (Crysta: two sub-categories — 'Agree'); in the apps since 2026-10-05 (NARRATIVE-NOTES). Includes the typed session summary (one note marked as the summary — it has no visibility of its own and freezes when the session is submitted) and each note whose home is that session and that the advocate marked 'Include in session summary'. A marked note from another home shows in the on-screen summary and is included in a share only with its own home, never here.",
679
770
  "levelFloor": 3,
680
771
  "appRelevance": [
681
772
  "PAVE",
package/src/cvcs/index.ts CHANGED
@@ -162,10 +162,10 @@ import immigrationLegalStatusChangeTypeSot from "./immigrationLegalStatusChangeT
162
162
  import programEnrollmentChangeTypeSot from "./programEnrollmentChangeType.v1.0.0.json" with { type: "json" };
163
163
  import romanticRelationshipChangeTypeSot from "./romanticRelationshipChangeType.v1.0.0.json" with { type: "json" };
164
164
  import riskCategorySot from "./riskCategory.v1.0.0.json" with { type: "json" };
165
- import coreFunctionsSot from "./coreFunctions.v1.0.0.json" with { type: "json" };
165
+ import coreFunctionsSot from "./coreFunctions.v1.1.0.json" with { type: "json" };
166
166
  import needsAssessmentChangeTypeSot from "./needsAssessmentChangeType.v1.0.0.json" with { type: "json" };
167
- import coreInformationScopeSot from "./coreInformationScope.v1.0.0.json" with { type: "json" };
168
- import roiScopeSot from "./roiScope.v1.0.0.json" with { type: "json" };
167
+ import coreInformationScopeSot from "./coreInformationScope.v1.1.0.json" with { type: "json" };
168
+ import roiScopeSot from "./roiScope.v1.2.0.json" with { type: "json" };
169
169
  import roiStatusSot from "./roiStatus.v1.0.0.json" with { type: "json" };
170
170
  import coreReferralOutcomeSot from "./coreReferralOutcome.v1.0.0.json" with { type: "json" };
171
171
  import coreIndicatorsSot from "./coreIndicators.v1.1.0.json" with { type: "json" };
@@ -1,9 +1,51 @@
1
1
  {
2
2
  "domain": "roi_scope",
3
3
  "name": "ROI Scope",
4
- "version": "1.1.0",
5
- "_status": "DRAFT — TEMPORARY: net-new value-CVC not yet in Notion; provisional 900+ numbering. 0.8.13: COMPLETED against the canonical 27-item source. 0.8.12 shipped 15 of the canonical 27; the missing 12 are added here. Nothing PAVE shipped was invented — this was purely a gap. Canonical source: `HTI_SHARE_SCOPE_GROUPS` in HTI-LEADS-PAVE-Thread-prototype.html @ HEAD a596eb9 (7 groups x items = 27): identifying (5) + risk (4) + contact (3) + notes (3) + health_accommodation (6) + immigration_legal_status (5) + system (1). The GROUP axis (identifying / risk / contact / notes / health_accommodation / immigration_legal_status / system) is a separate presentation concern and is deliberately NOT modelled as hierarchy rows here — this CVC is the flat item vocabulary that an ROI authorizes. PENDING canonical Notion authoring + steward ratification.",
6
- "_source": "htilabstech/prototype@a596eb9 HTI-LEADS-PAVE-Thread-prototype.html HTI_SHARE_SCOPE_GROUPS",
4
+ "version": "1.2.0",
5
+ "_status": "DRAFT — TEMPORARY: net-new value-CVC not yet in Notion; provisional 900+ numbering. 0.8.13: COMPLETED against the canonical 27-item source. 0.8.12 shipped 15 of the canonical 27; the missing 12 are added here. Nothing PAVE shipped was invented — this was purely a gap. Canonical source: `HTI_SHARE_SCOPE_GROUPS` in HTI-LEADS-PAVE-Thread-prototype.html @ HEAD a596eb9 (7 groups x items = 27): identifying (5) + risk (4) + contact (3) + notes (3) + health_accommodation (6) + immigration_legal_status (5) + system (1). The GROUP axis (identifying / risk / contact / notes / health_accommodation / immigration_legal_status / system) is a separate presentation concern and is deliberately NOT modelled as hierarchy rows here — this CVC is the flat item vocabulary that an ROI authorizes. PENDING canonical Notion authoring + steward ratification. VERSION 1.2.0 supersedes 1.1.0 (co-bwc): `screen_notes` (983-012) and `background` (983-014) are RETIRED TOMBSTONES, matching CVC-236 `core_information_scope` v1.1.0 (retired 2026-10-05, Narrative notes, signed Spec v2 rule 5). Each keeps its published code (never reused), is `selectable: false` + `retired: true`, and includes nothing: a stored ROI that names one resolves to \"retired\", not \"unknown\". Not additive, hence the version (ADR-CVC-0.8.13 Addendum 2026-10-05; see `_supersedes`). This flat vocabulary is LEGACY: new units (e.g. `session_summary`, 236-005-004) are minted in CVC-236 only and are not mirrored here.",
6
+ "_source": "htilabstech/prototype@a596eb9 HTI-LEADS-PAVE-Thread-prototype.html HTI_SHARE_SCOPE_GROUPS; v1.2.0 retirements: htilabstech/prototype/data/cvcs/core_information_scope.yaml @ 9ef79748 retired_units (L467)",
7
+ "_supersedes": {
8
+ "version": "1.1.0",
9
+ "keyMap": {
10
+ "missingness_root": "missingness_root",
11
+ "unknown": "unknown",
12
+ "anonymous": "anonymous",
13
+ "data_not_collected": "data_not_collected",
14
+ "names": "names",
15
+ "dob": "dob",
16
+ "addresses": "addresses",
17
+ "additional_ids": "additional_ids",
18
+ "demographics": "demographics",
19
+ "screen_indicators": "screen_indicators",
20
+ "victimization": "victimization",
21
+ "ida_full": "ida_full",
22
+ "ida_consid": "ida_consid",
23
+ "contact_info": "contact_info",
24
+ "service_history": "service_history",
25
+ "screen_notes": "screen_notes",
26
+ "case_notes": "case_notes",
27
+ "background": "background",
28
+ "system_info": "system_info",
29
+ "contact_history": "contact_history",
30
+ "accommodation_needs": "accommodation_needs",
31
+ "disability_subtypes": "disability_subtypes",
32
+ "mental_health_status": "mental_health_status",
33
+ "substance_use_status": "substance_use_status",
34
+ "chronic_health_status": "chronic_health_status",
35
+ "hiv_status": "hiv_status",
36
+ "immigration_status": "immigration_status",
37
+ "uscis_alien_number": "uscis_alien_number",
38
+ "federal_protection_applications": "federal_protection_applications",
39
+ "tvap_enrollment": "tvap_enrollment",
40
+ "le_report_status": "le_report_status"
41
+ },
42
+ "retiredCodes": [],
43
+ "notes": {
44
+ "summary": "Every v1.1.0 key is still an entry in v1.2.0, at its v1.1.0 code, so `keyMap` is the identity and `retiredCodes` is empty: no code was withdrawn. Non-additive because 2 published items are now RETIRED tombstones (notes below), matching CVC-236 `core_information_scope` v1.1.0, which retired the same two keys; nothing was added. Before this version the package gave two answers to \"is screen_notes offerable\" (co-bwc). The file was named `roiScope.v1.0.0.json` while declaring version 1.1.0 (the 0.8.13 completion); the published version superseded here is the declared 1.1.0.",
45
+ "screen_notes": "v1.1.0 `screen_notes` was a selectable item. Retired 2026-10-05 (Narrative notes, signed Spec v2 rule 5): The Initial Screen's notes box is an instrument note and belongs to the Initial Screen. It stays at 983-012 as a tombstone (`selectable: false`, `retired: true`) with NO successor key, and includes nothing — a stored ROI that names it narrows, never widens. CVC-236 v1.1.0 retired the same key (canon `data/cvcs/core_information_scope.yaml` `retired_units` L467 @ prototype 9ef79748); canon records that only demo data named it (Crysta 2026-10-04).",
46
+ "background": "v1.1.0 `background` was a selectable item. Retired 2026-10-05 (Narrative notes, signed Spec v2 rule 5): Nothing ever captured it. It stays at 983-014 as a tombstone (`selectable: false`, `retired: true`) with NO successor key, and includes nothing — a stored ROI that names it narrows, never widens. CVC-236 v1.1.0 retired the same key (canon `data/cvcs/core_information_scope.yaml` `retired_units` L467 @ prototype 9ef79748); canon records that only demo data named it (Crysta 2026-10-04)."
47
+ }
48
+ },
7
49
  "levels": {
8
50
  "0": "Unknown or Missing",
9
51
  "1": "ROI scope item"
@@ -152,10 +194,11 @@
152
194
  "code": "983-012-000-000-000-000-000",
153
195
  "key": "screen_notes",
154
196
  "title": "Screen notes",
155
- "selectable": true,
197
+ "selectable": false,
156
198
  "parentCode": null,
157
199
  "childCodes": [],
158
- "definition": "Narrative notes captured during screening. Narrative-notes scope group."
200
+ "definition": "RETIRED 2026-10-05 (Narrative notes, signed Spec v2 rule 5), matching its CVC-236 `core_information_scope` v1.1.0 twin. The Initial Screen's notes box is an instrument note and belongs to the Initial Screen. No longer offered in an ROI; a stored code resolves here so a reader can tell retired from unknown, and includes nothing.",
201
+ "retired": true
159
202
  },
160
203
  {
161
204
  "code": "983-013-000-000-000-000-000",
@@ -170,10 +213,11 @@
170
213
  "code": "983-014-000-000-000-000-000",
171
214
  "key": "background",
172
215
  "title": "Background information",
173
- "selectable": true,
216
+ "selectable": false,
174
217
  "parentCode": null,
175
218
  "childCodes": [],
176
- "definition": "Background/narrative context about the subject. Narrative-notes scope group."
219
+ "definition": "RETIRED 2026-10-05 (Narrative notes, signed Spec v2 rule 5), matching its CVC-236 `core_information_scope` v1.1.0 twin. Nothing ever captured it. No longer offered in an ROI; a stored code resolves here so a reader can tell retired from unknown, and includes nothing.",
220
+ "retired": true
177
221
  },
178
222
  {
179
223
  "code": "983-015-000-000-000-000-000",
@@ -3986,9 +3986,9 @@ export const RiskCategoryKeys = {
3986
3986
  export type RiskCategoryKey = keyof typeof RiskCategoryKeys;
3987
3987
 
3988
3988
  /**
3989
- * Key → positional code map for the `core_functions` CVC domain (CANONICAL Notion CVC-133 `core - functions`, verified v1.0 — the Canonical Authorization Model function registry: 77 functions the roles → functions → gates/tiers graph is built over. NOT provisional numbering. Per-entry lifecycle Status (v1 / future / not-started), Platform Relevance, user/admin relevance and Category are carried in each entry's definition, since the CVC entry schema has no fields for them).
3989
+ * Key → positional code map for the `core_functions` CVC domain (CANONICAL Notion CVC-133 `core - functions`, verified v1.0 — the Canonical Authorization Model function registry: 78 functions (the verified 77 + `note_open_departed_author`, 133-078, appended 2026-10-05) the roles → functions → gates/tiers graph is built over. NOT provisional numbering. Per-entry lifecycle Status (v1 / future / not-started), Platform Relevance, user/admin relevance and Category are carried in each entry's definition, since the CVC entry schema has no fields for them).
3990
3990
  *
3991
- * Domain: `core_functions` · Version: 1.0.0 · Entries: 81
3991
+ * Domain: `core_functions` · Version: 1.1.0 · Entries: 82
3992
3992
  */
3993
3993
  export const CoreFunctionsKeys = {
3994
3994
  missingness_root: "133-000-000-000-000-000-000",
@@ -4072,6 +4072,7 @@ export const CoreFunctionsKeys = {
4072
4072
  training_content_upload: "133-075-000-000-000-000-000",
4073
4073
  training_gate_manage: "133-076-000-000-000-000-000",
4074
4074
  usr_manage: "133-077-000-000-000-000-000",
4075
+ note_open_departed_author: "133-078-000-000-000-000-000",
4075
4076
  } as const;
4076
4077
 
4077
4078
  export type CoreFunctionsKey = keyof typeof CoreFunctionsKeys;
@@ -4100,9 +4101,9 @@ export const NeedsAssessmentChangeTypeKeys = {
4100
4101
  export type NeedsAssessmentChangeTypeKey = keyof typeof NeedsAssessmentChangeTypeKeys;
4101
4102
 
4102
4103
  /**
4103
- * Key → positional code map for the `core_information_scope` CVC domain (DRAFT-TEMPORARY; canonical CVC-236, 12 policy-grain CATEGORIES + 56 authorization-grain UNITS. Categories are level 1 and NOT selectable; units are level 2 and are what an ROI or a share authorizes. Distinct from the sibling `roi_scope` domain, which is the FLAT item vocabulary and deliberately omits the category axis — roi_scope's 27 substantive keys are a strict SUBSET of these 56 units, with no renames, so adoption is additive and no stored ROI changes meaning).
4104
+ * Key → positional code map for the `core_information_scope` CVC domain (DRAFT-TEMPORARY; canonical CVC-236, 12 policy-grain CATEGORIES + 55 authorization-grain UNITS + 2 RETIRED tombstones. Categories are level 1 and NOT selectable; units are level 2 and are what an ROI or a share authorizes. Tombstones (`screen_notes`, `background`; retired 2026-10-05) keep their codes so a stored value resolves, but are `selectable: false` + `retired: true` and include nothing — offer only selectable children. Distinct from the sibling `roi_scope` domain, which is the FLAT item vocabulary and deliberately omits the category axis — every one of roi_scope's 27 substantive keys resolves here with no renames (25 live units, 2 tombstones), so a stored ROI never widens).
4104
4105
  *
4105
- * Domain: `core_information_scope` · Version: 1.0.0 · Entries: 72
4106
+ * Domain: `core_information_scope` · Version: 1.1.0 · Entries: 73
4106
4107
  */
4107
4108
  export const CoreInformationScopeKeys = {
4108
4109
  missingness_root: "236-000-000-000-000-000-000",
@@ -4146,6 +4147,7 @@ export const CoreInformationScopeKeys = {
4146
4147
  screen_notes: "236-005-001-000-000-000-000",
4147
4148
  case_notes: "236-005-002-000-000-000-000",
4148
4149
  background: "236-005-003-000-000-000-000",
4150
+ session_summary: "236-005-004-000-000-000-000",
4149
4151
  health_accommodation: "236-006-000-000-000-000-000",
4150
4152
  accommodation_needs: "236-006-001-000-000-000-000",
4151
4153
  disability_subtypes: "236-006-002-000-000-000-000",
@@ -4182,9 +4184,9 @@ export const CoreInformationScopeKeys = {
4182
4184
  export type CoreInformationScopeKey = keyof typeof CoreInformationScopeKeys;
4183
4185
 
4184
4186
  /**
4185
- * Key → positional code map for the `roi_scope` CVC domain (DRAFT-TEMPORARY; the 15 ROI scope ITEMS an ROI authorizes for sharing, sourced from PAVE `@pave/domain` ROI_SCOPE_KEYS. The item axis only — named bundles over these items are ROI_SCOPE_PRESET_NAMES. The prototype's 27-item HTI_SHARE_SCOPE_GROUPS superset holds +12 health-accommodation / immigration-legal items that are the documented extension set).
4187
+ * Key → positional code map for the `roi_scope` CVC domain (DRAFT-TEMPORARY; LEGACY flat item vocabulary, superseded for new work by `core_information_scope` (CVC-236). 27 ROI scope ITEMS: 25 live + 2 RETIRED tombstones (`screen_notes`, `background`; retired 2026-10-05, matching CVC-236 v1.1.0) that keep their codes so a stored value resolves, but are `selectable: false` + `retired: true` and include nothing — never offer them. The item axis only — named bundles over these items are ROI_SCOPE_PRESET_NAMES).
4186
4188
  *
4187
- * Domain: `roi_scope` · Version: 1.1.0 · Entries: 31
4189
+ * Domain: `roi_scope` · Version: 1.2.0 · Entries: 31
4188
4190
  */
4189
4191
  export const RoiScopeKeys = {
4190
4192
  missingness_root: "983-000-000-000-000-000-000",