Deployment Boundaries

Deployment boundaries matter because a package can be publishable without being the right place to run a service.

Operating Rules

• this package is primarily a published knowledge layer rather than a standalone deployed service
• deployment boundaries here are artifact and repository compatibility boundaries
• service concerns belong in runtime or application layers that transport the knowledge state

First Proof Check

• src/bijux_proteomics_knowledge/claims.py and evidence.py
• src/bijux_proteomics_knowledge/confidence/segments.py and review.py
• packages/bijux-proteomics-knowledge/tests