{"wiki":{"id":1888,"slug":"mr-s1","entity_type":"droid","entity_id":"mr-s1","title":"Merlin Replanner","prose_md":"## About\n\nMerlin 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.\n\nIt works by watching for task-level replan handshakes addressed to [[agt_020]]. 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]] 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 [[agt_011]], and if something needs escalation it routes through [[agt_011]] or [[agt_001]].\n\nMerlin Replanner belongs to [[agt_020]], 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 [[agt_011]]. 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.","namesake_json":"{\"engine\": \"software\", \"model\": null, \"claude_purpose\": null, \"family\": \"planner\", \"family_size\": 14, \"is_unique\": false}","profile_pic_path":"","source_hash":"19cab93c9fb5db74eb7f1788f5cd8d421e3ae8d6dfd2c24e10ed352839e4b1d6","status":"active","last_generated_at":"2026-07-30 03:38:01","created_at":"2026-07-30 03:37:53","updated_at":"2026-07-30 03:38:01"},"facts":{"id":"mr-s1","name":"Merlin Replanner","machine_name":"MR-S1","owner":"agt_020","function":"Consumes task-level replan_requested handshakes and records Merlin task-level replan decisions in the session ledger","process_type":"triggered","schedule":"On demand","process_name":"Merlin Replanner","avatar_color":"#0ea5e9","created_for":"Merlin runs the day-to-day execution. When something goes wrong with a task mid-execution, Merlin decides what to do next without rethinking the whole strategy. This droid handles the replan piece—it captures signals that a task needs adjusting and records Merlin's decision so the team can move forward.","purpose":"MR-S1 creates a paper trail for task adjustments. When a task needs to be redone or changed, the droid captures the request, builds a clear decision record, and saves it to the system ledger. This keeps everyone on the team informed about what went wrong, what changed, and what to do next.","duties":"- Looks for replan requests sent to Merlin\n- Reads the reason and details from each request\n- Creates a decision record with all the context\n- Saves the decision to the system ledger with a timestamp\n- Marks the request as complete\n- Logs the activity for the audit trail","constraints":"- Only handles task-level changes; bigger strategy changes go to Elrond\n- Records decisions; doesn't make them\n- Does not escalate directly to leadership—routes through Elrond or Albus\n- Only processes requests addressed to Merlin; skips other agents' requests","status":"running","gender":"female","archetype":"planner","building_block":"replan","service_override":null,"enabled":1,"task_key":"initiatives.blanket_planner","model_free":0},"page":{"type":"droid","page_class":"main","class_label":"Main page","kind_label":"Droid","kind_gloss":"","listed":true}}