{"wiki":null,"facts":{"id":"el-rt-01","name":"Initiative Retrigger","machine_name":"EL-RT-01","owner":"agt_011","function":"Runs the retrigger orchestration that files a follow-on of a blocked/closed initiative after the pipeline is fixed","process_type":"triggered","schedule":"On retrigger request","process_name":"initiative_retrigger","avatar_color":"#f59e0b","created_for":"Elrond is accountable for the build pipeline's retrigger machinery. When an operator retriggers a blocked/closed initiative, the orchestration that files the follow-on must be performed by a named, accountable droid rather than loose logic inside the initiatives app (Design #146 / #173, cookbook 272).","purpose":"The Initiative Retrigger files a follow-on (-FF) of a blocked or closed parent initiative after the pipeline has been fixed (INI-342): it loads the parent, runs the INI-725 blocked-parent remediation gate (refusing with a structured 409 unless override_blocked_parent_gate is set), parses the parent title, builds the retry intent, routes it through the Author plus Validator orchestrator (iv-s1, falling back to ia-s1) to create the follow-on, then auto-enqueues the new follow-on (INI-624) so the autonomous resume loop completes end-to-end - exactly as it ran inside the app before phase 4. Carries its own DB handle and title parser so it is self-contained.","duties":"- Triggered whenever an operator retriggers an initiative through the initiatives app retrigger endpoint.\n- Loads the parent initiative and runs the INI-725 blocked-parent remediation gate before doing anything else.\n- Returns a structured 409 result (never an HTTP response) when the gate refuses and no override is given.\n- Builds the retry intent from the parent's scope plus any operator note, then routes it through the Author plus Validator orchestrator to create the -FF follow-on.\n- Auto-enqueues the new follow-on so it does not sit in planned-but-undispatched limbo.\n- Records a session_event and a Palantir post on every successful retrigger.","constraints":"- Owns and closes its own database connections; never relies on a caller's connection.\n- Behavior is preserved exactly from the app (phase 4 is a relocation, not a refactor) modulo the async-to-sync transform: the droid runs synchronously and the thin endpoint awaits it in a thread.\n- Never raises an HTTP response; the gate 409 is carried back as a structured result and the thin app endpoint reconstructs the 409.\n- Reached only through the initiatives app's shared shim, never imported by the app directly.\n- Does not touch the bypass book, cookbook, or initiative status rows beyond what the original orchestration did.","status":"running","gender":"male","archetype":"author","building_block":"troubleshoot","service_override":null}}