Deployment Boundaries

Deployment boundaries for bijux-canon-agent should protect the idea that the package is publishable and operable as its own unit. Deployment assumptions that quietly require the whole repository weaken that claim.

What To Check

• start from package metadata and declared entrypoints rather than from monorepo convenience
• separate what the package must ship from what maintainers happen to have nearby locally
• treat implicit repository coupling as an operational smell until it is justified explicitly

First Proof Check

• pyproject.toml, README.md, and boundary-facing entrypoints for checked-in operating truth
• tests and runnable workflows for executable confirmation that the runbook still works
• release notes and version metadata when the work changes caller expectations

Bottom Line

If bijux-canon-agent cannot be operated repeatably under change, the operational documentation is still incomplete.