📖About
Bypass Session Reaper is a droid that helps keep work statuses consistent when a session stops.
📖Usage
Readers would encounter it in the estate’s maintenance work, where it helps prevent inactive work from remaining marked as active.
📖Purpose
No initiative rests in 'executing' without a live session. A bypass that ends properly moves to reviewing; one that simply stops used to leave its run, its execution and its initiative open forever.
📖Duties
Every 15 minutes: close out bypass runs with no heartbeat inside the 30-minute window and fail their executions; then move any initiative still in 'executing' with no live bypass session - to parked if its execution recorded work (a check result or a completed step), to planned if it recorded none. All status changes go through the one status router.
📖Constraints
Bypass lane only - an initiative with no execution in the bypass book is not this reaper's work. Never touches a live session, so a parallel Orion lane is safe. Only moves rows OUT of 'executing': parked stays untouchable (712) and closed/discarded/redirected stay dead (717). Never raises into a caller; a run that hit any error is recorded FAILED, never as a quiet success.
Some source information is confidential and is not published here.
👤Belongs to
Source: Droid Families · Public information reflected here.