{"wiki":null,"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}}