Skip to content

Change Validation

Change validation should make it obvious whether a package edit is safe, risky, or mis-scoped.

Validation Model

flowchart LR
    semantics["core semantic change"]
    lifecycle["lifecycle and schema proof"]
    downstream["downstream contract review"]
    verdict["safe, risky, or mis-scoped"]

    semantics --> lifecycle --> downstream --> verdict

This page should make core validation feel like contract defense. The package is safe to change only when a reviewer can tell whether durable meaning moved and whether proof widened far enough to match that movement.

Review Rules

  • check whether a change alters core meaning or only implementation detail
  • run lifecycle and schema proof whenever contract surfaces move
  • require downstream review when public core semantics change

First Proof Check

  • packages/bijux-proteomics-core/tests
  • src/bijux_proteomics/program_spec.py and targets.py
  • src/bijux_proteomics/lifecycle.py and validation.py

Design Pressure

Core validation weakens when implementation convenience outruns semantic proof. If lifecycle and downstream contract checks do not widen when meaning moves, the review is already underspecified.