📖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.
- Confirms the filing names a real parent that is currently active.
- Refuses filings that target an Orion-filed bypass (those go to the operator queue instead).
- For Albus, refuses filings that reach outside the build pipeline into governance surfaces (cookbook, policies, SSTs, designs, prompts).
- Confirms the follow-on chain traces back to a non-Albus starting point.
- 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.
- Read-only on the initiatives database — it decides, it does not write, park, or close anything.
- Does not own the database connection it is handed; the caller manages and closes it.
- Reached only through the initiatives app's shared shim, never imported by the app directly.
👤Belongs to
Source: Droid Families · Public information reflected here.