AARIA

Abstract

AARIA is the orchestrator: one entry point for every multi-agent dispatch, pipeline, and cross-agent handoff in the system. Most agent frameworks route like a flat dispatcher, handing the job to whichever agent is free. AARIA plans first. Every request is broken into a plan, scored against a mechanism library that keeps evolving, and handed to the specialist that actually fits. It treats an agent as a real runtime object rather than a prompt template you wire up by hand: something you can address, compose, persist, and hold accountable. That is where the hard parts (memory, delegation, observability, audit) stop being rebuilt in every application and become the platform's job.

Provenance

Started as a dashboard for tracking whether any of this was working, became a system for running it, and ended up the thing everything else plugs into. Underneath: years of multi-org Salesforce architecture, Health Cloud patient-journey work, event-driven integration at scale, and a running tally of the scaling problems prompt-chaining never actually fixed.

Declassified

Two choices are odd enough to name. First, it will not act without planning. Even on a request that looks like a one-liner, the planner runs to catch the downstream it would otherwise miss, and there is a deliberately narrow lane for trivial read-only work so that discipline doesn't become theatre. Second, the mechanism library is evolutionary: mechanisms compete on measured outcomes and the losers get retired. The plumbing borrows from multi-org stitching, event-driven enterprise architecture, and partitioning big systems along domain lines. The mechanisms themselves, the scoring, and how patterns spread across the fleet stay off this page.

Also in FORGE

• SF TEAM A senior delivery team, expressed as agents.
• SYNARK The flight panel. What the factory is actually doing.
• JUDGE PANEL Removing myself as the bottleneck, without removing the audit.