{"wiki":{"id":766,"slug":"el-fg-01","entity_type":"droid","entity_id":"el-fg-01","title":"Filing Gate","prose_md":"## About\n\nThe Filing Gate is a guard droid owned by [[agt_011]]. It sits at the entry point for new follow-on work in the [[initiatives]] pipeline and exists so [[agt_011]] can trust any filing that gets accepted: the filing must point at a real, active parent; it must stay inside the build pipeline's own files; it must not bypass one of [[agt_023]]'s hand-done jobs; and its chain must trace back to a legitimate starting point other than [[agt_001]].\n\nIt is triggered whenever [[agt_001]] or [[agt_011]] files a follow-on initiative; filings from anyone else pass straight through. The droid checks the named parent, refuses filings aimed at [[agt_023]]-filed bypasses, and for [[agt_001]] also refuses anything reaching outside the build pipeline into governance surfaces. On success it returns the resolved target and chain-root so the target can be parked atomically; on failure it refuses with a clear reason. It is read-only and does not write, park, or close anything.\n\nThe Filing Gate's exact name is unique, but it is not a one-off: it is one of three droids in the reusable \"gate\" family, and the same family is also run by [[agt_028]]. Although it is small and focused, it is not pure software: it calls Claude (unspecified model) to evaluate filings against the filing-invariant rules.","namesake_json":"{\"engine\": \"claude\", \"model\": null, \"claude_purpose\": \"enforcing the filing-invariant gate on follow-on filings\", \"family\": \"gate\", \"family_size\": 3, \"is_unique\": false}","profile_pic_path":"avatars/droid/el-fg-01.png","source_hash":"ad509a4b910219429d8565461ac31323ebf69df58f37d6a534527ea316853f80","status":"being_built","last_generated_at":"2026-08-05 00:45:09","created_at":"2026-07-26 03:31:39","updated_at":"2026-08-05 00:45:09"},"facts":{"id":"el-fg-01","name":"Filing Gate","machine_name":"EL-FG-01","owner":"agt_011","function":"Enforces the autonomous-agent filing-invariant gate on Albus/Elrond follow-on filings","process_type":"triggered","schedule":"On filing","process_name":"filing_gate","avatar_color":"#3b82f6","created_for":"Elrond is accountable for keeping the build pipeline's work legitimate. Every new follow-on initiative that Albus or Elrond's automation tries to open must be checked before it enters the system, so bad or out-of-scope filings never reach the pipeline.","purpose":"The Filing Gate is the checkpoint at the door for new follow-on work. It lets Elrond trust that any filing accepted into the pipeline points at a real, active parent, stays inside the build pipeline's own files, does not hijack one of Orion's hand-done jobs, and traces back to a legitimate starting point.","duties":"- Triggered whenever Albus or Elrond files a follow-on initiative.\n- Confirms the filing names a real parent that is currently active.\n- Refuses filings that target an Orion-filed bypass (those go to the operator queue instead).\n- For Albus, refuses filings that reach outside the build pipeline into governance surfaces (cookbook, policies, SSTs, designs, prompts).\n- Confirms the follow-on chain traces back to a non-Albus starting point.\n- On success, returns the resolved target and chain-root so the target can be parked atomically; on failure, refuses with a clear reason.","constraints":"- Only evaluates filings from Albus or Elrond; all other filings pass straight through.\n- Read-only on the initiatives database — it decides, it does not write, park, or close anything.\n- Does not own the database connection it is handed; the caller manages and closes it.\n- Reached only through the initiatives app's shared shim, never imported by the app directly.","status":"running","gender":"male","archetype":"gate","building_block":"file","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}}