📖About & Usage

About

The Autonomous Troubleshooter is a specialised worker droid owned by Albus. It exists to investigate failed executions in Carol's ecosystem — whether a script broke, a SQL query returned wrong results, or a pipeline stalled — and either fix the root cause itself or produce a precise handoff for a human operator. Instead of just reporting symptoms, it traces upstream through code, logs, and databases to find the actual fault, then edits the relevant file or SQL to apply a fix, or leaves an actionable patch with file:line references and proposed changes.

This droid works under strict discipline: every claim it makes must cite a real file:line, SQL row, or log line. At the end of its session it outputs three labelled sections — FINDINGS, ACTIONS, and OUTCOME — so its reasoning and results are fully transparent. It may read and edit any file under `/home/caroladmin/dev`, but cannot push to git, restart services, or edit system files without explicit operator approval.

The Autonomous Troubleshooter is a unique droid — no other agent runs a droid with this exact name — but it belongs to a larger worker family used by 30 droids across many agents, including Albus, Carol, Elrond, Forge, Galadriel, Hagrid, Merlin, Orion, Sage, Sentinel, Themis, Radagast, Noah, and Leo. It is not pure software; it calls claude (model unspecified) to help analyse logs, reason about failures, and generate patches. The human operator can configure its time and cost limits through `context.timeout` and `context.cost_budget`, and if it cannot fully fix or hand off, it must honestly report `OUTCOME=inconclusive` rather than pretending success.

👤Owner

📚Recent initiatives

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