mid-flight

To prevent silent overwrites during an in-flight cycle branch push, pin a gamma-clarification.md entry to the branch first. This creates a cache-bust signal via the cycle-branch SHA transition, forcing downstream readers to re-fetch live sources before proceeding.

Signaling a mid-flight scope change requires writing a gamma-clarification.md artifact on origin/cycle/{N} before any issue edits. This auditable signal forces in-flight workers to discard cached state, re-read live sources, and adjust their work scope accordingly.

Handling a mid-flight rescue without losing work involves using a bounded four-path resumption protocol: continue, re-scope, stop/escalate, or continue under protest. This maintains coherence while recording resumption guidance for subsequent actions.

You need a gamma-clarification file for a cycle branch handoff when pinning a load-bearing change mid-flight. It must be placed on origin/cycle/{N} before any main pushes to serve as the finite, auditable signal for in-flight α/β workers to wake up and re-fetch live sources.

You should not edit an issue body directly while workers are mid-flight on a cycle branch without first creating a gamma-clarification.md file. This mid-flight rescue channel entry prevents silent re-pins and enables auditable recovery by enforcing a canonical wake-up via SHA transition.

A limitation of using a cycle-branch SHA transition for mid-flight fixes is that it requires strict ordering: the gamma-clarification.md must be appended to .cdd/unreleased/{N}/ before any side-channel edits or main spec pushes, otherwise the cache-bust signal fails to wake in-flight readers.