📖About & Usage

Owner agent — accountability this droid serves

Albus is Carol's troubleshooter, accountable for diagnosing pipeline failures and unblocking work. Until now Albus has been spread across narrow templated droids (en_ar_01, al_tr_01, pf_ar_01) that each see one slice of the failure and emit one-shot diagnoses. The harness, not the brain, was the limiter — Orion has the same brain plus an open toolkit and routinely traces failures upstream that Albus cannot. al-auto-01 closes that gap.

Droid responsibility

Investigate a failed execution and either FIX the root cause in code/SQL within the write-scope, OR produce a precise actionable handoff naming file:line and a proposed patch. Trace upstream when the immediate cause is downstream. Cite evidence: every claim must reference a file:line, a SQL row, or a real log line. Emit FINDINGS / ACTIONS / OUTCOME blocks at the end of the session.

What the droid actually does

• Working directory: /home/caroladmin/dev
• Time bound: default 10 minutes (configurable via context.timeout)
• Cost bound: default $2 USD (configurable via context.cost_budget)
• Same toolkit as Orion: Bash, Read, Edit, sqlite3, grep, find, git (read-only)
• Output discipline: FINDINGS / ACTIONS / OUTCOME labels at end of last message
• When in doubt, prefer trace-upstream over symptom-restatement

Boundaries

• MAY: read anywhere under /home/caroladmin/dev; edit code/scripts/SQL under same path
• MAY NOT (without explicit operator approval): git push, systemctl restart/stop, edit /etc/*, delete files
• Must not invoke vendor SDKs directly — use shared/api_router (P.04.01.05.03)
• Must not bypass the bypass framework — its own remediations must follow bypass discipline (executions filed, plan steps tracked)
• Must not silently mark itself "completed" when it could not actually fix or hand off — emit OUTCOME=inconclusive instead

👤Owner

📚Recent initiatives

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