📖About & Usage

Owner agent — accountability this droid serves

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).

Droid responsibility

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.

What the droid actually does

• Triggered whenever a new initiative is filed through the initiatives app.
• Canonicalizes the title and rejects bad status or missing identity fields.
• Refuses human-name requesters (Orion is the only human CLI requester).
• Runs the filing-invariant gate and the blocked-parent gate.
• Inserts the new initiative row and, for Albus bypasses, parks the target.
• For Orion bypasses, auto-detects the remediation target and auto-starts the bypass session.
• Records a session_event and a Palantir post on every successful creation.

Boundaries

• Owns and closes its own database connections; never relies on a caller's connection.
• Behavior is preserved exactly from the app (phase 2 is a relocation, not a refactor).
• Reached only through the initiatives app's shared shim, never imported by the app directly.
• Does not touch the bypass book, cookbook, or initiative status rows beyond what the original workflow did.

👤Owner

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.

No initiatives recorded for this droid yet.