為何 86% 的多智能體系統會失敗：修正 Planner-to-Worker 規格漂移

Originally published by **Asif Muhammad Iqbal (Founder & CEO at Logic42)* at https://logic42.ai/articles/multi-agent-specification-drift-mast-failure-taxonomy.*

Why 86% of Multi-Agent Systems Fail: Fixing Planner-to-Worker Spec Drift

Planner-to-worker specification drift is the primary structural failure mode in multi-agent AI systems, occurring when an orchestrator agent delegates tasks to specialized sub-agents using ambiguous natural-language histories instead of deterministic state contracts. As documented in UC Berkeley's Multi-Agent System Failure Taxonomy (MAST), production multi-agent workflows fail at rates between 41% and 86.7% because inter-agent handoffs corrupt task constraints, mask silent tool errors, and terminate prematurely without verification.

For the past eighteen months, enterprise AI teams assumed that splitting a complex workflow across five specialized agents (Planner, Researcher, Coder, Reviewer, and Executor) would automatically improve reliability. Demo videos looked effortless. If one prompt struggled, teams simply added another agent to supervise it.

In production, adding more conversational agents multiplied failure rates exponentially. When an upstream Researcher agent receives an empty array or a shifted API response from an external service, it doesn't halt. Instead, it summarizes a plausible assumption in natural prose and hands that prose to the Coder agent. By step four, the entire swarm is confidently executing against fabricated state. You can't build ISO/IEC 42001-compliant automation on a game of telephone, and it's why naive agent swarms collapse under real load.

Why do multi-agent LLM systems fail at such high rates in production?

Multi-agent LLM systems fail at rates up to 86.7% because unstructured natural-language handoffs allow minor specification omissions and silent tool failures to compound across agent boundaries. When Worker A returns an HTTP 200 OK payload containing semantically incomplete data, Worker B lacks a deterministic pre-condition contract to reject the handoff, causing downstream agents to hallucinate missing parameters and declare premature task completion.

Look at our production audit across 10,000 multi-step enterprise workflows mapped against the three core MAST failure categories:

Examine the third row carefully: enforcing syntactic JSON output (response_format) only raises end-to-end reliability to 51.4%. Why? Because a worker agent can emit 100% syntactically valid JSON where "customer_tier": "enterprise" is guessed from context rather than verified against a primary key.

We saw this firsthand in an automated cloud-provisioning pipeline. The Planner agent instructed the Network Worker to "deploy inside the staging VPC." The Network Worker queried AWS, hit a pagination limit, picked the first VPC ID returned, and passed a valid JSON object to the Terraform Worker. Nobody checked that the VPC tag matched env=staging. It modified production routing tables in twelve seconds.

The Three Handoff Bottlenecks in Multi-Agent Orchestration

Replacing human coordination with agent-to-agent chat introduces three systemic reliability bottlenecks.

1. Planner-to-Worker Specification Drift

When a Planner decomposes a user objective into subtasks, it frequently drops negative constraints like "do not modify records updated after October 1" or "exclude EU-resident PII." Because the Worker agent only receives its narrow subtask prompt plus a noisy chat transcript, it violates global invariants that were obvious in the root request.

2. Silent Tool Failure Masking (HTTP 200 Semantic Corruption)

Traditional APM monitors check whether a microservice returns HTTP 500. In agentic pipelines, an API tool often returns HTTP 200 OK with {"status": "partial_match", "records": []} or a deprecated schema field. Conversational worker agents are trained to be helpful: instead of raising a hard exception, they bridge the gap with parametric guesswork, poisoning every subsequent agent in the chain.

3. Premature Verification Bypass

When an Executor agent asks a Reviewer agent to "verify the output," both models share the same blind spots and lack independent deterministic ground truth. Without executable post-condition assertions (such as AST compilation, SQL row-count checksums, or OPA policy evaluation), peer agents rubber-stamp broken outputs.

Architectural Comparison: Conversational Swarms vs. Deterministic Contract Graphs

To achieve enterprise-grade reliability, you must replace free-form agent chat handoffs with a Finite State Machine (FSM) governed by executable pre-condition and post-condition contracts.

The Logic42 Architectural Fix: Immutable Root Invariants & Executable Handoff Gates

Under our Build-Transfer-Operate practice, we eliminate conversational handoffs entirely. Agents don't "talk" to each other; they read and write to an immutable, schema-validated State Ledger guarded by deterministic Python/Rust verification gates.

# Logic42 Sovereign Orchestrator: Deterministic Pre/Post-Condition Handoff Gate
from dataclasses import dataclass, field
from typing import Dict, Any, List, Callable

@dataclass(frozen=True)
class GlobalInvariants:
    tenant_id: str
    allowed_environment: str
    max_mutation_rows: int
    prohibited_fields: List[str] = field(default_factory=lambda: ["ssn", "passport_no"])

class ContractHandoffGate:
    def __init__(self, invariants: GlobalInvariants):
        self.invariants = invariants

    def validate_worker_handoff(
        self,
        worker_name: str,
        tool_http_status: int,
        payload: Dict[str, Any],
        post_conditions: List[Callable[[Dict[str, Any], GlobalInvariants], bool]]
    ) -> Dict[str, Any]:
        # 1. Reject non-200 or empty semantic payloads before next agent wakes up
        if tool_http_status != 200 or not payload.get("verified_records"):
            raise RuntimeError(
                f"[HANDOFF HALT] {worker_name} returned empty or unverified tool state. "
                "Blocking downstream agent invocation to prevent hallucinated recovery."
            )

        # 2. Enforce immutable root invariants across every worker boundary
        if payload.get("environment") != self.invariants.allowed_environment:
            raise PermissionError(
                f"[SPEC DRIFT BLOCKED] {worker_name} drifted to env={payload.get('environment')}; "
                f"root invariant requires env={self.invariants.allowed_environment}."
            )

        # 3. Execute deterministic code assertions (never LLM-as-a-Judge for state integrity)
        for check in post_conditions:
            if not check(payload, self.invariants):
                raise ValueError(f"[POST-CONDITION FAILED] {worker_name} output failed contract check: {check.__name__}")

        return payload

Three Rules for High-Reliability Multi-Agent Engineering

1. Pin Global Invariants Outside the Chat Context:
   Never rely on a Planner agent to copy security, tenancy, or environment constraints into sub-agent prompts. Store root invariants (tenant_id, environment, budget_ceiling, jurisdiction) in an immutable state object injected and verified by code at every node transition.

2. Enforce Fail-Fast Exceptions on Partial Tool Responses:
   Configure worker tool wrappers so that empty result sets, schema mismatches, or low-confidence retrieval scores raise hard runtime exceptions that halt the graph, forbidding the worker LLM from "helpfully" improvising missing data.

3. Replace LLM Reviewers with Deterministic Code Verifiers:
   Do not use a second LLM to check whether the first LLM followed formatting, math, or policy rules. Use deterministic verifiers like Pydantic strict validators, SQL EXPLAIN plans, static AST parsers, and Open Policy Agent (OPA) rules before committing any state transition.

If your multi-agent architecture passes unstructured markdown strings from one LLM to the next, specification drift will guarantee production failures at scale. We engineer deterministic state-machine orchestrators and ISO/IEC 42001 verification gates inside your environment so your autonomous workflows execute with mathematical predictability.

Run the Interactive ISO/IEC 42001:2023 AI Management System (AIMS) Readiness Diagnostic

Evaluating this architectural bottleneck in production? Benchmark your stack in 3.5 minutes with instant Stage 1 blocker detection and a downloadable boardroom PDF dossier:
👉 Launch the Diagnostic on Logic42 (https://logic42.ai/assessments/iso-42001)

Or model your 2026 frontier MoE HBM3e VRAM residency and 24-month bare-metal payback:
🧮 Sovereign MoE VRAM & GPU Repatriation Calculator (https://logic42.ai/assessments/gpu-tco)