Definition of Done

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

For bijux-proteomics-lab, done means an operator can still reconstruct what was planned, what happened, and what was promoted from the durable record.

Completion Model

flowchart TB
    change["change lands in planning, outcomes, or lab records"]
    story{"operator story still reconstructable?"}
    proof{"tests and docs defend the changed lab path?"}
    downstream{"upstream and downstream payload meaning still aligned?"}
    done["change is done"]

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

The real threshold is not just correctness at runtime. It is whether the promoted lab record still tells a coherent story to the next operator and the next system boundary.

Review Rules

• operators can still explain what happened from the durable record
• tests and docs defend the changed lab surface clearly
• upstream and downstream consumers still align on the payload meaning

First Proof Check

• packages/bijux-proteomics-lab/tests
• src/bijux_proteomics_lab/planning.py and outcomes.py
• src/bijux_proteomics_lab/repositories.py and serialization.py

Design Pressure

The easy mistake is to treat successful execution as enough while letting planning intent, outcome meaning, or promotion history become harder to audit.