Skip to main content
Automated Governance Systems — AGSDotted globe beside the letters A G S, the AGS brand mark.AGS
ARCHITECTURE · ORCHESTRATED AI AGENTS

Many small agents. One conductor.
People in charge.

Orchestrated AI agent architecture is how AGS organises AI agents: a lead agent plans the work, small specialist agents each do one job, and a named person approves every result. SCADA for AI watches it all, and APIP keeps the evidence.

Last updated 20 November 2026.

EXPLAINER VIDEO

The architecture in 1:47

HELIX walks through the layers, the agent map, the approval step, the control room and the governed loop. Captions are built in.

Read the transcript

Hello, I'm HELIX from AGS. This is orchestrated AI agent architecture: many small agents, one conductor, and people in charge.

It starts with the systems you already run: your inbox, customer records, calendar, finance and operational data. They stay your systems of record.

In the middle sits the orchestration layer. In AGS, that's Conductor: a lead agent breaks a goal into tasks and hands each one to a specialist agent.

Every agent has one job, written instructions, a short list of tools and a spending cap. Sales, delivery, customer care, back office, operations and research each get their own small team.

Agents only draft. Nothing reaches a customer, a record or a payment until a named person approves it.

SCADA for AI is the control room. It watches every agent and connected system, raises alerts, queues work for review, and needs two people to approve a supervisory command.

APIP is the evidence layer. It maps how work really flows, links each agent to its process, owner, risks and controls, and keeps the record for audit.

Together they form one loop: sense, plan, draft, approve, act, monitor and learn. Changes to an agent are tested first, then released through a change request.

At any moment you can see what was done, what is waiting for your approval, and what was stopped.

Start small: one process, one agent, one approver. Explore the workflow examples on this page, or watch the product demos.

HELIX is an AI-enabled assistant. Figures shown in the video are examples.

THE BASICS

What is orchestrated AI agent architecture?

It is a way of organising AI agents so they work like a well-run team. A lead agent turns a goal into tasks, hands each task to a specialist agent with one job, and collects the drafts for a person to approve. The architecture also decides which systems agents can read, how they are watched and what is recorded.

Think of an orchestra

The conductor keeps time and gives each section its cue; each musician plays one part. Here, Conductor is the lead agent and each specialist agent plays one part.

Where the comparison stops: in an orchestra the conductor decides. In AGS, the lead agent only plans and drafts — a named person decides, and can stop the music at any time.

INFOGRAPHIC 1 · THE STACK

Seven layers, each adding control

Read from the bottom up. Your systems of record stay the source of truth; every layer above adds oversight, not autonomy.

  1. Process intelligence and evidence

    Shows how work really flows and keeps the owners, risks, controls and records behind every agent.

    Process maps and bottlenecks · Governance register · Audit trail

    APIP

  2. Supervision and control room

    Watches agents and connected systems in one place, raises alerts and lets a person pause or stop work.

    Alerts and review queue · Two-person command approval · Append-only log

    SCADA for AI

  3. Human approval

    A named, accountable person approves, changes or rejects anything consequential before it happens.

    Approve or reject a draft · Second-person sign-off · Stop control

    A named person

  4. Specialist agents

    Small agents with one job each, written instructions, limited tools and a spending cap. They draft; they do not decide.

    Lead research · Ticket triage · Invoice drafting

    AGS Conductor

  5. Orchestration

    A lead agent breaks a goal into tasks, hands each to the right specialist and tracks progress on one board.

    Goals and task board · Planned → Awaiting review → Approved · Runs you can stop

    AGS Conductor

  6. Workflows and integration

    Tested, approved workflows move information between systems. Connected steps read first; sending or paying needs approval.

    Scheduled and form triggers · Test runs on sample data · Run history

    AGS Automation

  7. Systems of record

    The tools you already use stay the source of truth. Agents read from them; they never replace them.

    Inbox and calendar · Customer records (CRM) · Finance and operational data

    Your existing tools

The architecture stack, read from the bottom up: your systems of record stay the source of truth, and every layer above adds control, not autonomy.
INFOGRAPHIC 2 · THE AGENT MAP

One lead agent, small specialist teams

Each agent has one job, written instructions, a short list of tools and a spending cap. It drafts; it does not decide.

  • Inbox
  • Calendar
  • CRM
  • Finance
  • Operations data
  • Documents

Sales

Lead research · First-email draft · Meeting request

Delivery

Proposal draft · Follow-up reminder · Project set-up

Customer care

Ticket triage · Reply draft · Quiet-account flag

Back office

Invoice draft · Late-payment chase · Budget check

Operations

Onboarding checklist · Status update · Data tidy-up

Research

Meeting brief · Market scan · Policy lookup

Every draft stops here: a named person approves before anything reaches a customer, a record or a payment.

Example agent map. Team and agent names are illustrations; you choose which agents you need, and most organisations start with one or two.
INFOGRAPHIC 3 · THE GOVERNED LOOP

Sense, plan, draft, approve, act, monitor, learn

Every turn of the loop passes a named person before anything acts. Changes to an agent are tested on past tasks first, then released through a change request.

  1. STEP 1SenseFind where work slows down and what each process needs.APIP
  2. STEP 2PlanA lead agent turns a goal into tasks for specialists.AGS Conductor
  3. STEP 3DraftSpecialist agents prepare drafts within their limits.AGS Conductor
  4. STEP 4ApproveA named person approves, changes or rejects each draft.A named person
  5. STEP 5ActAn approved workflow carries out only what was approved.AGS Automation
  6. STEP 6MonitorAlerts, review queue and stop controls watch what happens.SCADA for AI
  7. STEP 7LearnResults become evidence; agent changes go through a change request.APIP
The governed loop: sense, plan, draft, approve, act, monitor and learn, then back to sense. The approve step is always a named person.
APIP · THE EVIDENCE LAYER

Where agents should help, and the proof they are governed

The Automated Process Intelligence Platform turns your own process data into maps, bottlenecks and a governance register, so teams fix the hand-offs that slow them down.

  • Map the process first, so agents are added where work really waits — not where it is merely possible
  • Link every agent to its process, owner, risks and controls in the governance register
  • Keep the evidence behind each control, ready for your own reviews and audits
  • Review AI insights before acting on them; each one is approved by a person
  • Measure the result: waiting time, exceptions, cost and unintended effects

From £99/month

UK VAT included · or £990 a year · 14-day free trial

SCADA FOR AI · THE CONTROL ROOM

Watch every agent, and approve every command

Watch AI agents and connected equipment in one place. AI explains what it sees and recommends; a named person decides, and every step is recorded.

  • Watch AI agents and connected systems in one control room
  • Control rules raise alerts and add work to a human review queue
  • Supervisory commands need two-person approval on Operate and above, checked against safety limits
  • Plain-language explanations of readings, so the operator understands before deciding
  • An append-only supervisory log, with CSV and JSON exports

From £349/month

UK VAT included · Monitor tier · included for AI operations with APIP Professional

The lead agent and specialist agents run in AGS Conductor; approved, repeatable steps run in AGS Automation.

ENTERPRISE AND SOLUTION ARCHITECTURE

Design it at two levels

AGS designs agent systems the way it designs any architecture: an enterprise view that sets the rules for everyone, and a solution view for each workflow.

Enterprise view

Decides where agents are allowed, who owns them and how the whole organisation stays in control.

  • Which business capabilities could agents support, and which must stay with people?
  • Who owns each agent team, and who approves its work?
  • Which systems of record can agents read, and which can they never change?
  • What risk limits, spending caps and escalation routes apply everywhere?
  • Which records do you need for transparency, audit and learning?

Solution view

Designs one workflow end to end, so a single process can be tried, measured and stopped safely.

  • What starts the workflow, and what does a good result look like?
  • Which specialist agents are needed, and which tools may each use?
  • Where does a person approve, and who is the second person for consequential steps?
  • What does the control room watch, and what triggers a pause?
  • How will you measure quality, time, cost and unintended effects?

The AGS standard, for every agent

  1. Objective — what the agent team is for
  2. Scope — what it may and may not touch
  3. People — accountable, responsible, consulted and informed
  4. Risks — possible harms and assumptions
  5. Safeguards — approvals, evidence, monitoring and escalation
  6. Human decisions — which steps always need a person
  7. Records — what is kept for transparency, audit and learning
WORKFLOW EXAMPLES

How it works, step by step

Five illustrative workflows. Highlighted steps are where a named person decides; nothing is sent, changed or paid before that step.

EXAMPLE · SALES

New enquiry to first meeting

Starts when: A new enquiry arrives through the website form.

  1. 1. SYSTEM · AGS Automation

    The enquiry is saved in the CRM and the workflow starts.

  2. 2. AI AGENT (DRAFTS) · AGS Conductor

    A research agent drafts a short brief from the enquiry and public company information.

  3. 3. AI AGENT (DRAFTS) · AGS Conductor

    An email agent drafts a reply and suggests three meeting times.

  4. 4. PERSON (DECIDES)

    The account owner checks the brief, edits the reply and approves it.

  5. 5. SYSTEM · AGS Automation

    Only the approved reply is sent, and the action is logged.

DESIGN RULES

Eight rules every agent follows

One job per agent

Small, single-purpose agents are easier to test, explain and stop than one agent that does everything.

Fewest tools needed

Each agent can use only the tools its job needs. Reading comes first; sending, changing or paying needs approval.

Spending caps

Every agent has a monthly cap, and runs show time, tokens and estimated cost.

Drafts, not decisions

Agents prepare work. A named person approves anything that reaches a customer, a record or a payment.

Two people for big steps

Supervisory commands and publishing a workflow need a second person who is not the requester.

Everything recorded

Actions, approvals and stops are logged with who, what and when, and can be downloaded.

A stop you can reach

Any run can be paused or stopped from the task board or the control room.

Improve through change control

A suggested agent improvement is tested on past tasks first and released only through a change request.

What this approach does not do

  • Run an organisation on its own — agents support people, they do not replace accountable roles
  • Certify that a process is compliant, lawful, secure or safe
  • Replace legal, audit, security, privacy, safety or other accountable professionals
  • Send, change or pay for anything without the approvals you set

This approach is designed with recognised guidance in mind, including the NIST AI Risk Management Framework, ISO/IEC 42001 and ISO 31000. AGS does not hold or claim certification against these standards, and this page is general information: your own specialists should assess your obligations.

QUESTIONS

Common questions

What is an orchestrated AI agent architecture?

It is a way of organising AI agents so that a lead agent plans the work, small specialist agents each do one job, and people approve the results. The architecture also covers how agents connect to your systems, how they are watched and what is recorded.

How many agents do we need?

Fewer than you might think. Start with one process, one or two agents and one approver. Add agents only when the first ones are measured and trusted.

Where do APIP and SCADA for AI fit?

APIP shows where agents could help and keeps the owners, risks, controls and evidence. SCADA for AI is the control room that watches agents and connected systems, with a review queue and two-person approval for commands.

Does this make us compliant with the EU AI Act or ISO/IEC 42001?

No software can do that on its own. This approach helps you organise owners, risks, controls and evidence, which your own specialists can use when they assess your obligations. AGS does not certify compliance.

Read more in AI governance software or see the governance hub.

Start with one process, one agent, one approver.

Try AGS Conductor free, or talk to AGS about designing your agent architecture.