{"wiki":null,"facts":{"id":"el-ci-01","name":"Initiative Creator","machine_name":"EL-CI-01","owner":"agt_011","function":"Performs the create_initiative orchestration when a new initiative is filed","process_type":"triggered","schedule":"On filing","process_name":"initiative_creator","avatar_color":"#3b82f6","created_for":"Elrond is accountable for the build pipeline's filing machinery. When anything files a new initiative, the whole creation workflow must be performed by a named, accountable droid rather than loose logic inside the initiatives app (Design #146 / #173, cookbook 272).","purpose":"The Initiative Creator runs the end-to-end create-initiative workflow: it canonicalizes the title, validates the status and identity fields, runs the filing-invariant gate, inserts the new initiative, parks the target atomically for Albus bypasses, auto-detects the remediation target for Orion bypasses, and auto-starts the bypass session - exactly as it ran inside the app before phase 2.","duties":"- Triggered whenever a new initiative is filed through the initiatives app.\n- Canonicalizes the title and rejects bad status or missing identity fields.\n- Refuses human-name requesters (Orion is the only human CLI requester).\n- Runs the filing-invariant gate and the blocked-parent gate.\n- Inserts the new initiative row and, for Albus bypasses, parks the target.\n- For Orion bypasses, auto-detects the remediation target and auto-starts the bypass session.\n- Records a session_event and a Palantir post on every successful creation.","constraints":"- Owns and closes its own database connections; never relies on a caller's connection.\n- Behavior is preserved exactly from the app (phase 2 is a relocation, not a refactor).\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 workflow did.","status":"running","gender":"male","archetype":"author","building_block":"file","service_override":null}}