📖About & Usage

About

The Elrond Orphan Droid-Run Reaper is a housekeeping droid that cleans up stale, stuck droid executions. Its job is to scan the Pipeline for any droid runs that are still marked running but have been active for more than 30 minutes with no actual execution — these are “orphans” that lost their process but never finished. It marks them as failed so they don’t clog the system or report confusing statuses. This fills a gap: the Foreman service handles many droid lifecycle events, but it doesn’t catch execution‑less hangs, which the Reaper exists to fix.

Every 5 minutes the Reaper wakes up (controlled by Scheduled Processes), reads only `droid_runs` records, finds the ones stuck in a running state beyond the 30‑minute threshold, and flips them to failed. It then writes a small audit note — a `run-audit` — for each reaped run, so there’s always a trail. It cannot read or change anything else; its permissions are locked strictly to `droid_runs` updates.

Owned by Elrond, the Reaper originally lived inside a retired watcher but now runs as a standalone droid. It is not a one‑off. It’s a member of a widely‑shared (none) droid family — 209 agents across the Carolverse, from Albus to Scriber, each run an identical copy. This one is pure software: it never calls out to Claude or any large language model, doing its work entirely with deterministic code.

👤Owner

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.

No initiatives recorded for this droid yet.