{"wiki":{"id":1015,"slug":"el-rt-01","entity_type":"droid","entity_id":"el-rt-01","title":"Initiative Retrigger","prose_md":"## About\n\nInitiative Retrigger (el-rt-01) is an automated worker owned by [[agt_011]] 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 [[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.\n\nWhen 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 [[initiatives]] app's shared shim, with the thin endpoint awaiting it in a thread.\n\nInitiative Retrigger is a unique name within the author droid family — one of 26 author droids that [[agt_001]], [[agt_002]], [[agt_003]], [[agt_008]], [[agt_011]], [[agt_012]], [[agt_023]], [[agt_025]], and [[agt_034]] also run (see [[droid-families]]) — but this exact copy belongs only to [[agt_011]]. 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.","namesake_json":"{\"engine\": \"claude\", \"model\": null, \"claude_purpose\": \"authoring the follow-on initiative via the Author-plus-Validator orchestrator\", \"family\": \"author\", \"family_size\": 26, \"is_unique\": true}","profile_pic_path":"avatars/droid/el-rt-01.png","source_hash":"0054c05acf797fb7c7a97f70552f62f9e4cfc48ffed474fbf9c1585139c96771","status":"being_built","last_generated_at":"2026-08-05 00:48:20","created_at":"2026-07-27 03:25:51","updated_at":"2026-08-06 03:25:57"},"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,"enabled":1,"task_key":"initiatives.initiative_filed","model_free":0},"page":{"type":"droid","page_class":"main","class_label":"Main page","kind_label":"Droid","kind_gloss":"","listed":true}}