package substance¶
This report makes package-boundary substance explicit. The five real product packages must carry enough owned logic to justify their boundaries, the shared kernel must stay narrow and reusable, the compatibility bridge must stay wrapper-only, and the maintainer package must remain a real repository-health surface instead of a token directory.
Boundary Roles¶
- canonical products: 5
- shared kernels: 1
- compatibility bridges: 1
- maintainer support packages: 1
Current Package Counts¶
agentic-proteins: role=compatibility_bridge, owned_logic=0, wrappers=112, thin=0, ready=yesbijux-proteomics-core: role=canonical_product, owned_logic=128, wrappers=0, thin=21, ready=yesbijux-proteomics-dev: role=maintainer_support, owned_logic=142, wrappers=0, thin=27, ready=nobijux-proteomics-foundation: role=shared_kernel, owned_logic=24, wrappers=0, thin=1, ready=yesbijux-proteomics-intelligence: role=canonical_product, owned_logic=25, wrappers=0, thin=1, ready=yesbijux-proteomics-knowledge: role=canonical_product, owned_logic=44, wrappers=0, thin=13, ready=yesbijux-proteomics-lab: role=canonical_product, owned_logic=27, wrappers=0, thin=10, ready=yesbijux-proteomics-runtime: role=canonical_product, owned_logic=139, wrappers=0, thin=26, ready=yes
Release Rule¶
- the five real product packages must keep enough owned logic to justify separate release identities
- the shared kernel must stay narrow, reusable, and free of presentation or workflow ownership drift
- the compatibility bridge is allowed to be thin only because it is explicitly a wrapper-only bridge
- package-boundary thinness is release-blocking when it hides unresolved SSOT ownership
- current package substance issues: 0
First Proof Check¶
docs/08-bijux-proteomics-maintain/bijux-proteomics-dev/package-substance.csvdocs/08-bijux-proteomics-maintain/bijux-proteomics-dev/package-substance.mdpackages/bijux-proteomics-dev/tests/quality/architecture/test_package_substance.py