Operations

bijux-proteomics-foundation operations is the discipline of changing shared meaning without breaking the family. A maintainer here is not mostly operating a service. They are stewarding compatibility: every schema tweak, serialization decision, and migration rule can ripple through every other package.

flowchart LR
    change["schema or migration change"]
    meaning["check meaning drift"]
    canon["rebuild canonical artifacts"]
    migrate["prove migration continuity"]
    downstream["check downstream package assumptions"]
    release["publish only when shared proof holds"]

    change --> meaning --> canon --> migrate --> downstream --> release

What Operations Means Here

• protecting long-lived records matters more than local implementation convenience
• release confidence comes from compatibility proof, not from file count
• downstream breakage often begins as subtle meaning drift rather than obvious runtime failure

Start With

• open Common Workflows when you need the expected path from change to compatibility proof
• open Release and Versioning before treating any schema or migration edit as publishable
• open Failure Recovery when persisted records or cross-package fixtures have already drifted
• open Observability and Diagnostics when you need to prove whether the break is semantic, versioned, or serialization-specific

Operational Reading Paths

• Local Development and Installation and Setup for working safely with canonical fixtures and migrations
• Deployment Boundaries and Security and Safety for understanding what must remain conservative because other packages depend on it
• Performance and Scaling only when artifact volume or migration throughput becomes operationally significant, not as the default concern

First Proof Check

• src/bijux_proteomics_foundation/schema.py and migrations.py
• src/bijux_proteomics_foundation/serialization.py
• packages/bijux-proteomics-foundation/tests