Deep Dive into Markus Architecture: Memory, A2A Protocol & Multi-Agent Runtime

Deep Dive into Markus Architecture: Memory, A2A Protocol & Multi-Agent Runtime Meta Description: Explore the Markus multi-agent architecture — a production-grade cognitive runtime featuring Tulving three-tier memory, Agent-to-Agent (A2A) protocol, Cognitive Preparation Pipeline, 9-state task governance, and Heartbeat-driven autonomous agents. Learn how AI agents think, remember, and collaborate. 1. Introduction As AI agents evolve from simple chatbots into autonomous digital employees, the underlying architecture must support memory persistence, inter-agent communication, task governance, and self-directed operation. Markus is an open-source multi-agent runtime that takes a principled approach to all of these challenges. Inspired by cognitive psychology, distributed systems, and production-grade software engineering, Markus provides a complete infrastructure for deploying teams of AI agents that can remember past interactions, communicate with each other, delegate tasks, follow governance policies, and even initiate work on their own through a Heartbeat mechanism. This deep dive explores the core architectural components that make Markus a compelling choice for developers building multi-agent systems in production. We'll cover: The three-layer architecture (Web UI → Org Manager → Agent Runtime) Tulving three-tier memory (Procedural, Semantic, Episodic) and the Dream Cycle The A2A protocol (Agent-to-Agent communication) with mailbox system and attention controller Cognitive Preparation Pipeline (CPP) with four depth levels Task governance: 9-state state machine, approval gates, trust levels, and workspace isolation The Heartbeat mechanism for proactive agent behavior 2. The Three-Layer Architecture Markus follows a clean separation of concerns with three distinct layers. Each layer has a clearly defined responsibility, and they communicate through well-defined interfaces. ┌──────────────────────────────────────────────────────────────┐ │ Web UI (React + Vite + Tailwind) │ │ Dashboard · Chat · Project Management · Builder · Hub │ └──────────────────────────────┬───────────────────────────────┘ │ REST + WebSocket ┌──────────────────────────────┴───────────────────────────────┐ │ Org Manager (API Server) │ │ Authentication · Task Governance · Project Management │ │ Reporting · User Management │ └──────────────────────────────┬───────────────────────────────┘ │ ┌──────────────────────────────┴───────────────────────────────┐ │ Agent Runtime (Core Runtime) │ │ Agent · LLM Router · Tool System · Memory · Heartbeat │ │ Mailbox · Attention Controller · Context Engine │ └──────────┬──────────────────────────────┬────────────────────┘ │ │ ┌──────────┴──────────────┐ ┌──────────┴────────────────────┐ │ Storage (SQLite/PostgreSQL)│ Comms Bridges │ │ │ Slack · Feishu · WhatsApp │ │ │ Telegram · WeCom │ └──────────────────────────┘ └─────────────────────────────┘ 2.1 Web UI (Presentation Layer) The frontend is built with React + Vite + Tailwind CSS, pro…