📖About & Usage

About

Merlin Replanner exists to create a clear paper trail whenever a task needs adjusting. When something goes off track—a task has to be redone, reprioritised, or changed—this droid captures the replan request, builds a formal decision record, and saves it to the system ledger. That way everyone on the team stays informed about what went wrong, what changed, and what to do next.

It works by watching for task-level replan handshakes addressed to Merlin. It reads the reason and details from each request, creates a decision record with full context and a timestamp, and writes that record to the session ledger. Once saved, it marks the request as complete and logs the step for the audit trail—keeping Audit & Compliance and other oversight services in the loop. This is a pure software droid: no Claude calls, just data movement and record-keeping. It only handles task-level changes; bigger strategy adjustments go to Elrond, and if something needs escalation it routes through Elrond or Albus.

Merlin Replanner belongs to Merlin, but it’s not a one-off. It’s part of the planner droid family—a standard reusable pattern run by 14 droids across multiple agents, including Elrond. So while the exact name “Merlin Replanner” is unique, several agents use their own planner droids built on the same blueprint for recording replan decisions. Because it never calls Claude, it executes purely as an automated software workflow.

👤Owner

📚Recent initiatives

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