Phases follow reality

A delivery's phase says where the work really is. A skipped step is recorded on the delivery, not hidden and not enforced afterwards.

At Blume, we want the phase of a piece of work to answer one question truthfully: where is this, right now? A record that disagrees with the world is worse than a record that notes a skipped step.

What goes wrong when status enforces process

Status as a gate

On Friday a fix is urgent. You tell the agent to merge and deploy it. Nobody opened the review, so the tracking tool refuses to move the work past Test.

On Monday the board says Test while the fix has been in production for three days. Someone starts retesting it, and the one fact worth knowing, that it shipped without a review, is nowhere.

Status as fact

The phase moves to Release, with a note on that move: moved here without approval.

On Monday you open it, look at the evidence and approve the outcome after the fact, or send it back.

What to do

  • Move the status when the world moves: after a merge, a deploy or a rollback, even if the process was not followed.
  • Write down the skip in the same place: who moved it, from where, and what was passed over.
  • Keep approval separate from position. Approval is a fact about a revision. Phase is a fact about the work.

This is not permission to skip reviews. The normal path is still to ask and wait.

In Blume

  • Each delivery shows its phase and its route, and you can choose any phase from the phase badge.
  • When an agent reports a phase that passes over a step, Blume moves the delivery and records the skip.
  • Nothing moves a delivery back on its own after the outcome review. Gaps show as notes, such as “Not approved”. See reviews and release.