{"wiki":{"id":763,"slug":"el-cl-01","entity_type":"droid","entity_id":"el-cl-01","title":"Initiative Closer","prose_md":"## About\n\nThe Initiative Closer is an author-family droid owned by [[agt_011]]. It exists because phase 3 of the [[migration]] moved the [[initiatives]] app's post-commit close-event hooks out of the app into a standalone droid — a relocation, not a refactor, so behavior is preserved exactly. Whenever the app's PUT handler commits a status change, it triggers four hooks: flipping a dispatch lock on terminal status, rolling component actuals into running averages, running quality scoring plus a regression check, and running the per-initiative audit and follow-on filer.\n\nIt is called only through the [[initiatives]] app's shared shim, never imported directly, and runs each hook as a best-effort step so one failure never blocks the others. It owns and closes its own database connections, records a session_event and posts to [[palantir]] on every close, and deliberately does not hold the close gate — status guards and terminal-reopen checks stay in the app endpoint.\n\nIt is not unique: it's one of 26 author-family droids, and there are two copies of \"Initiative Closer\" itself. Other agents across [[agt_001]], [[agt_002]], [[agt_003]], [[agt_008]], [[agt_012]], [[agt_023]], [[agt_025]], and [[agt_034]] also run author droids; the family is documented in [[droid-families]]. It is not pure software — its execution engine calls Claude (model unspecified) to generate written outputs such as audit entries and Palantir posts.","namesake_json":"{\"engine\": \"claude\", \"model\": null, \"claude_purpose\": \"writing post-close audit and Palantir narrative content\", \"family\": \"author\", \"family_size\": 26, \"is_unique\": false}","profile_pic_path":"avatars/droid/el-cl-01.png","source_hash":"c1476a788b213a19dedac42ddca56b7518c1f7b30315b8430b9975fa673d8f1d","status":"being_built","last_generated_at":"2026-08-05 00:47:46","created_at":"2026-07-26 03:31:21","updated_at":"2026-08-05 00:47:46"},"facts":{"id":"el-cl-01","name":"Initiative Closer","machine_name":"EL-CL-01","owner":"agt_011","function":"Runs the post-commit close-event hooks when an initiative status is committed","process_type":"triggered","schedule":"On status change","process_name":"initiative_closer","avatar_color":"#ef4444","created_for":"Elrond is accountable for the build pipelines close machinery. When an initiatives status is committed, the post-commit close-event hooks must be performed by a named, accountable droid rather than loose logic inside the initiatives app (Design #146 / #173, cookbook 272).","purpose":"The Initiative Closer runs the four post-commit close-event hooks after the PUT handler commits a status change: flips the orion.bypass dispatch_queue lock on terminal status (INI-446), rolls component actuals into running averages on close (INI-682), runs quality scoring plus the rolling-average regression check on close (INI-322), and runs the per-initiative audit plus follow-on filer on any terminal state (INI-465/623/636) - exactly as they ran inside the app before phase 3. Carries the write-side quality scoring engine so the scoring hook is self-contained.","duties":"- Triggered whenever an initiative status is committed through the initiatives app PUT handler.\n- Runs each of the four close-event hooks as a separate best-effort step; one failing never blocks the others.\n- On terminal status, flips the bypass dispatch lock and runs the audit plus follow-on filer.\n- On close, rolls up component actuals and computes and persists the quality score.\n- Records a session_event and a Palantir post on every close.","constraints":"- Owns and closes its own database connections; never relies on a callers connection.\n- Behavior is preserved exactly from the app (phase 3 is a relocation, not a refactor).\n- Does NOT hold the close gate (status guard, terminal-reopen guard, closure review-must-pass guard) - those stay in the app endpoint before the UPDATE.\n- Reached only through the initiatives apps shared shim, never imported by the app directly.\n- Does not touch the bypass book, cookbook, or initiative status rows beyond what the original hooks did.","status":"running","gender":"male","archetype":"author","building_block":"judge","service_override":null,"enabled":1,"task_key":"initiatives.outcome_recorded","model_free":0},"page":{"type":"droid","page_class":"main","class_label":"Main page","kind_label":"Droid","kind_gloss":"","listed":true}}