bijux-proteomics-core¶
bijux-proteomics-core owns durable program contracts in
bijux-proteomics. It is where workflows, lifecycle state, gates, and other
long-lived rules are defined before downstream packages score, execute, or act
on them. If foundation is the shared language, core is the constitutional
layer: it decides which states exist, which transitions are legal, and which
constraints the rest of the system is not allowed to improvise around.
flowchart LR
foundation["foundation<br/>shared payload meaning"]
core["core<br/>program contracts and lifecycle rules"]
knowledge["knowledge<br/>evidence state"]
intelligence["intelligence<br/>decision policy"]
runtime["runtime<br/>execution control"]
lab["lab<br/>assay loop"]
foundation --> core
core --> knowledge
core --> intelligence
core --> runtime
core --> lab
Why This Package Exists¶
- the system needs one place where workflow and gate semantics stay durable
- downstream packages should inherit program rules, not reinvent them
- lifecycle design should be inspectable before it turns into runtime behavior or policy code
What It Owns¶
- program models and lifecycle rules
- gate semantics and durable workflow constraints
- core contracts that downstream packages depend on
Start With¶
- Open Foundation for the package role and contract boundary.
- Open Interfaces when the issue is a public contract or package-facing surface.
- Open bijux-proteomics-intelligence when the concern becomes recommendation policy rather than durable program rules.
What It Refuses¶
- shared serialization primitives that belong in foundation
- evidence truth and confidence policy that belong in knowledge
- execution orchestration that belongs in runtime
First Proof Check¶
packages/bijux-proteomics-core/src/bijux_proteomicspackages/bijux-proteomics-core/tests- public contract artifacts when a core API surface changes