Skip to content

Definition of Done

A change in bijux-canon-ingest is done only when prepared ingest behavior is implemented, explained, and defended together. Local success without package-level trust is not done.

What To Check

  • require code, docs, and proof to agree on the new behavior
  • treat unclear release or compatibility impact as unfinished work when callers are affected
  • reject “done” that depends on a reviewer inferring the missing proof story alone

First Proof Check

  • tests and package-local validation surfaces for executable evidence
  • caller-facing docs, limits, and risks for the trust story readers actually receive
  • release notes and change records when the work alters what others may safely assume

Bottom Line

If bijux-canon-ingest cannot explain why prepared ingest behavior should be trusted after a change, the quality work is still incomplete.