Definition of Done

Done means the package is easier to trust after the change, not just that the diff merged.

For bijux-proteomics-intelligence, done means a changed recommendation path is easier to justify in reader language than it was before the edit.

Completion Model

flowchart TB
    change["change lands in policy, evaluator, or outcome path"]
    logic{"recommendation logic still explainable?"}
    proof{"tests and docs show why outcomes changed?"}
    downstream{"reports and consumers stay safe to interpret?"}
    done["change is done"]

    change --> logic
    logic -->|yes| proof
    logic -->|no| block1["not done"]
    proof -->|yes| downstream
    proof -->|no| block2["not done"]
    downstream -->|yes| done
    downstream -->|no| block3["not done"]

The important threshold is explanation, not just score movement. If the outcome changed and the page still cannot tell a reviewer why, the work is incomplete.

Review Rules

• the changed recommendation path is easier to justify than before
• tests and docs explain the outcome shift in reader language
• downstream consumers can still interpret outputs safely

First Proof Check

• packages/bijux-proteomics-intelligence/tests
• src/bijux_proteomics_intelligence/policies.py and evaluators.py
• src/bijux_proteomics_intelligence/report/ and outcomes.py

Design Pressure

The easy mistake is to accept a recommendation change because the numbers moved in the expected direction, even though the justification path became harder to inspect.