Skip to content

Scope and Non-Goals

bijux-proteomics-foundation exists for shared payload meaning. It should stay narrow enough that a reviewer can tell what it is not for before reading implementation detail.

In Scope

  • work that directly strengthens the package's named role
  • contracts, helpers, and tests whose best proof lives in this package
  • explicit handoff points to neighboring packages

Out Of Scope

  • behavior whose best proof already lives in a neighboring package
  • convenience abstractions that blur ownership
  • repository-health automation or root process unless this is the maintainer package

Explicit Non-Goals

  • product-specific fixtures, workflow examples, and operator narratives belonging to downstream packages
  • route-shaped, CLI-shaped, and Markdown-shaped helper surfaces that are about presentation or orchestration instead of shared contract meaning
  • runtime, lab, lifecycle, evidence, and ranking semantics that only happen to reuse foundation primitives

First Proof Check

  • package source and tests
  • neighboring handbooks when scope starts to blur