Skip to content

epic: package consolidation — trim to earned complexity #11

Description

@peterkc

Overview

The workspace declares 17 members for ~450 lines of source; 16 packages contain only a version string. The 3-layer architecture (packages → verticals → apps) is sound, but the package count is ahead of the code. Collapse to ~7–8 packages until implementation volume earns the finer split; the layering principle is unchanged.

Scope

In scope: package merges, workspace/member updates, commitlint scope updates, doc updates. Out of scope: new feature code (epic: make it run).

Decomposition

  • Merge hdp-{canonical,audit,identity,consent,provenance}hdp-core
  • Consolidate the home-health vertical packages to two
  • Keep the emr-sync adapter seam transport-agnostic (HTTP API today; alternative transports must slot in without reshaping the interface)
  • Adjudicate hh-hitl placement in the target map: the hdp-schema-seed spec (vault, FR-102) promotes it to packages/hdp-hitl — place it deliberately so that spec resumes cleanly in the make-it-run epic (epic: make it run — runnable app + real schema #12)
  • Update commitlint scope-enum, workspace members, README/CLAUDE.md architecture text

Success Criteria

  • Workspace member count ≤ 8 with CI green
  • Dependency edges still respect layering (apps → verticals → packages, no inversions)
  • Every remaining package has a truthful Depth marker

Verification

  • 16 of 17 packages contain only __init__.py + version string (per-package tokei sweep)
  • Zero cross-package imports exist today (grep -r "from hdp_\|from hh_" --include='*.py' → only __init__ hits), so merges are mechanical
  • Related: blocked by the OSS-readiness epic only for sequencing, not technically

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicTop-level initiative with sub-issues / task list

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions