📖About & Usage

About

Initiative Retrigger (el-rt-01) is an automated worker owned by Elrond that keeps initiatives moving when the pipeline breaks. If an initiative ends up blocked or closed because the pipeline failed, an operator can retrigger it through the Carol Initiatives app; the droid then files a follow-on (-FF) of the parent so the autonomous resume loop completes end-to-end. It was relocated out of the app in phase 4 as a self-contained droid — a move, not a refactor — so its behavior is preserved from the original orchestration.

When triggered, the droid loads the parent initiative and runs the INI-725 blocked-parent remediation gate, refusing with a structured 409 result (never an HTTP response) unless an override is set. If the gate passes, it parses the parent title, builds a retry intent from the parent's scope plus any operator note, and routes it through the Author-plus-Validator orchestrator to create the follow-on. It then auto-enqueues the new initiative so it never sits in planned-but-undispatched limbo, and records a session_event and a Palantir post on success. It is fully self-contained: it owns its DB connections, carries its own title parser, and is reached only through the Carol Initiatives app's shared shim, with the thin endpoint awaiting it in a thread.

Initiative Retrigger is a unique name within the author droid family — one of 26 author droids that Albus, Archon, Argus, Carol, Elrond, Forge, Orion, Sage, and Leo also run (see Droid Families) — but this exact copy belongs only to Elrond. It is not pure software: it calls Claude with the model unspecified in its registry, using Claude to author the follow-on initiative through the Author-plus-Validator orchestrator.

👤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.