Foundation¶
The foundation section explains the durable role of bijux-proteomics-intelligence before it
explains implementation detail. Use it to resolve why decision policy belongs here without pretending to own evidence truth or execution.
flowchart LR
evidence["evidence input"]
constraints["program constraints"]
policy["scoring and scenario policy"]
explanation["explanations"]
intelligence["intelligence foundation"]
action["downstream action"]
evidence --> intelligence
constraints --> intelligence
policy --> intelligence
intelligence --> explanation
intelligence --> action
What This Section Protects¶
- a visible seam between fact and judgment
- recommendation logic that can be argued about instead of merely obeyed
- explanation surfaces that stay tied to policy rather than pretending to be raw evidence
Start With¶
- Open Package Overview for the shortest statement of the package role.
- Open Ownership Boundary when the question is whether a change belongs here or in a neighbor.
- Open Scope and Non-Goals when a proposed change risks broadening the package.
- Open Capability Map when you need the concrete work the package is allowed to do.
Section Pages¶
- Package Overview
- Scope and Non-Goals
- Ownership Boundary
- Capability Map
- Dependencies and Adjacencies
- Repository Fit
- Lifecycle Overview
- Domain Language
- Change Principles
What This Section Settles¶
- when a rule is a judgment policy rather than a knowledge claim
- which recommendation behavior belongs here before runtime or lab acts on it
- when a proposed change is really about evidence truth or workflow rules and should leave this package
First Proof Check¶
packages/bijux-proteomics-intelligence/src/bijux_proteomics_intelligencepackages/bijux-proteomics-intelligence/tests- neighboring handbooks once the change crosses the local boundary
Neighbors¶
- Open bijux-proteomics-knowledge when the question leaves scoring, ranking, scenarios, and explanations.
- Open bijux-proteomics-core when the issue is clearly outside this package's local role.