Loading patterns…
Ledger Orchestration (Magentic-One)(LO)
An orchestrator drives a team of specialized agents using two ledgers: a task ledger holding facts, educated guesses, and a plan, and a progress ledger where the orchestrator self-reflects each step on whether progress is being made, whether the team is stalled, and which agent should act next. When progress stalls, an outer loop updates the facts and revises the plan. Introduced in Microsoft Magentic-One.
In 30 seconds
- What
- Orchestrator maintains a task ledger of facts and plan, uses a progress ledger to self-reflect each step, detects stalls by counter, and replans when stuck.
- When to use
- Complex multi-step tasks requiring web search, file handling, coding, and terminal work where the team needs dynamic redirection when progress halts.
- Watch out
- Stall detection threshold and replanning logic must be tuned carefully or the system loops endlessly or gives up too early.
Ask the AI expert about this pattern
Opens the assistant with your question prefilled. You review it before sending.
Ledger Orchestration (Magentic-One): Overview
An orchestrator drives a team of specialized agents using two ledgers: a task ledger holding facts, educated guesses, and a plan, and a progress ledger where the orchestrator self-reflects each step on whether progress is being made, whether the team is stalled, and which agent should act next. When progress stalls, an outer loop updates the facts and revises the plan. Introduced in Microsoft Magentic-One.
- Task ledger: facts, educated guesses, and current plan
- Progress ledger: per-step self-reflection on progress
- Stall detection via a counter and threshold
- Outer loop replans and updates facts when stuck
- Dynamic next-speaker selection each turn
- Generalist team: WebSurfer, FileSurfer, Coder, ComputerTerminal
The Agent Architect
One pattern, one tradeoff, one production failure story. A short weekly briefing for people building agentic systems.
Weekly email, one-click unsubscribe. We only use your address to send the briefing.
References
The papers, specifications, and repositories this pattern is based on.
From the engineer behind this catalog
Get your agent architecture reviewed
This page documents one pattern. Your system runs dozens, and most failures live in how they fit together. Have the whole design reviewed against the 288 patterns in this catalog: architecture, reliability, evaluation and cost, every finding mapped to the pattern that fixes it.
€750 instead of €1,500, one week, written report and walkthrough call, until 30 September