Use the Knots workflow through kno when asked to drive a knot end to end, run a claimed knot to completion, or keep advancing a knot until it reaches a terminal state such as SHIPPED, or a passive waiting state such as BLOCKED or DEFERRED.
Use the Knots workflow through kno when asked to orchestrate an execution plan from start to finish, processing waves sequentially, steps within each wave sequentially, and launching knots within each step concurrently.
Use the Knots workflow through kno when asked to create a knot, work on a specific knot, claim or execute a knot, advance a knot to its next state, or recover or roll back a knot safely after blocked or failed work.
Use when the operator explicitly asks to handoff, reset, wrap up, recycle a session, get fresh context, or restart a coordination agent (mechanik, deacon, witness). Do not invoke from internal judgment that a handoff would be useful — propose it in conversation and let the operator decide.