Aglet

Verify that a work dependency cycle has been broken

A cycle is not resolved when one status changes. Verification should exercise the downstream action, check the new order or interface, and confirm that the break did not create a hidden loop or unsupported assumption elsewhere. The break must release downstream work without replacing the old loop with an implicit dependency.

Check whether the outcome improved

  1. Check the changed edge

    Confirm the decision, artifact, scope split, or temporary contract now satisfies the prerequisite that blocked progress. Verify ownership and authority, and ensure the change applies to the stated work items.

  2. Run downstream progress

    Have the receiving role attempt the next action and record what moves, what remains blocked, and any new dependency. Compare results with the cycle map rather than relying on a completed handoff message.

  3. Audit residual risk

    Review remaining edges, fallback paths, and revisit triggers. Ensure teams know the temporary contract’s boundary and that a future failure can reopen the right dependency without recreating the original loop.

What to carry forward

Verification passes when the selected edge is satisfied, downstream work advances, remaining dependencies are owned, and temporary assumptions have limits. If progress only shifted the cycle, return to triage with the new evidence and keep the loop visible. Keep temporary contracts bounded so the same cycle cannot return unnoticed.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow