By Sagar Shankaran, Founder of CallSphere
Blackboard architectures from 1980s AI are quietly back, repurposed for 2026 multi-agent systems. The pattern, the modern stack, and where it shines.
Key takeaways
The blackboard architecture — Hearsay-II in 1980 was the canonical implementation — has a simple idea: multiple specialist "knowledge sources" share a common workspace ("blackboard"), reading and writing partial solutions. A control component decides which knowledge source acts next based on the current state.
In 2026 this pattern is back. Multi-agent LLM systems use it under different names: shared scratchpads, agent state stores, coordination memory. The pattern is older than most AI engineers, and worth understanding because it solves problems modern designs keep rediscovering.
flowchart TB
KS1[Specialist Agent 1] --> BB[(Blackboard)]
KS2[Specialist Agent 2] --> BB
KS3[Specialist Agent 3] --> BB
BB --> KS1
BB --> KS2
BB --> KS3
Ctrl[Control / Scheduler] --> KS1
Ctrl --> KS2
Ctrl --> KS3
BB --> Ctrl
Three components:
A modern blackboard for an LLM multi-agent system is typically:
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
fact, hypothesis, plan, action) with timestamps and provenanceflowchart LR
Event[Incoming event] --> BB[(Blackboard:<br/>Postgres + NATS)]
BB -->|trigger| Ag1[Specialist Agent: Triage]
BB -->|trigger| Ag2[Specialist Agent: Lookup]
BB -->|trigger| Ag3[Specialist Agent: Action]
Ag1 --> BB
Ag2 --> BB
Ag3 --> BB
Three workload shapes where blackboard wins in 2026:
CallSphere's after-hours escalation system has a blackboard-shaped architecture. Email events, voicemail events, and SMS events all post structured records to a shared event store. Specialist agents (triage, voice-script generator, escalation-ladder builder, ack-monitor) react asynchronously. The "orchestrator" is a thin event-routing layer rather than a single planner — which is exactly the blackboard pattern.
Once you've shipped blackboard Architectures Revisited to a real workload, the design questions change. You stop asking 'can the agent do this?' and start asking 'can the agent do this within a 1.2s p95 and under $0.04 per session?' Once you frame blackboard architectures revisited that way, the design choices get easier: short tool descriptions, narrow argument types, and a hard cap on tool calls per turn beat any amount of prompt engineering.
Agentic AI in a real call center is a different beast than a single-LLM chatbot. Instead of one model answering one prompt, you orchestrate a small team: a router that decides intent, specialists that own a vertical (booking, intake, billing, escalation), and tools that read and write to the same Postgres your CRM trusts. Hand-offs are where most production bugs hide — when Agent A passes context to Agent B, anything that isn't explicit in the message gets lost, and the user feels it as the agent "forgetting." That's why the systems that hold up under load are the ones with typed tool schemas, deterministic state stored outside the conversation, and a hard ceiling on tool calls per session. The cost story is just as important: a multi-agent loop can quietly burn 10x the tokens of a single-LLM design if you let it think out loud at every step. The fix isn't a smarter model, it's smaller agents, shorter prompts, cached system messages, and evals that fail the build when p95 latency or per-session cost regresses. CallSphere runs this pattern across 6 verticals in production, and the rule has held every time: the agent you can debug in five minutes will out-survive the agent that's "smarter" on a benchmark.
Q: When does blackboard Architectures Revisited actually beat a single-LLM design?
A: Scaling comes from constraint, not capability. The deployments that hold up keep each agent narrow, cap tool calls per turn, cache the system prompt, and pin a smaller model for routing while reserving the larger model for synthesis. CallSphere's stack — 37 agents · 90+ tools · 115+ DB tables · 6 verticals live — is sized that way on purpose.
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
Q: How do you debug blackboard Architectures Revisited when an agent makes the wrong handoff?
A: Hard ceilings beat heuristics. A maximum step count, an idempotency key on every tool call, and a fallback to a deterministic script when confidence drops below a threshold are what keep the loop bounded. Evals that simulate noisy inputs catch the rest before they reach a real caller.
Q: What does blackboard Architectures Revisited look like inside a CallSphere deployment?
A: It's already in production. Today CallSphere runs this pattern in Real Estate and IT Helpdesk, alongside the other live verticals (Healthcare, Real Estate, Salon, Sales, After-Hours Escalation, IT Helpdesk). The same orchestrator code path serves voice and chat — the difference is the tool set the router exposes.
Want to see salon agents handle real traffic? Spin up a walkthrough at https://salon.callsphere.tech or grab 20 minutes on the calendar: https://calendly.com/sagar-callsphere/new-meeting.
Written by
Sagar Shankaran· Founder, CallSphere
Sagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
The 2026 desktop AI agent landscape — ServiceNow Project Arc, Anthropic Claude offerings, OpenAI agents, and Google Mariner. A buyer's map.
Five proven multi-agent architecture patterns built on A2A — orchestrator, peer mesh, hub-and-spoke, marketplace, and tiered specialist.
How to design a multi-agent system using MCP for tools and A2A for cross-vendor coordination, with a CallSphere voice agent as a participating node.
A2A is the open standard for agent-to-agent coordination. Here is how the Agent Card JSON works, how discovery happens, and what to publish.
A2A unlocks cross-vendor agent coordination, but most enterprise voice/chat workloads still ship faster on a single-vendor stack. Here is how to choose.
Every 100ms of latency costs you. So does every cent per minute. Here is the decision matrix we use across 6 verticals to pick where to spend and where to save on voice AI infrastructure.
© 2026 CallSphere LLC. All rights reserved.
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.
Try Live DemoBook a DemoCalculate Your ROI