Multi-agent architecture.
Eleven agent roles across research, portfolio, risk and execution, with an independent risk veto and a human approval gate. Companion to the full blueprint published at agentteam.co.uk.
This chapter states the architecture. The full blueprint — with proposal schema, kill-switch conditions, seven-stage deployment roadmap and the exact obligations of each role — is published as a companion piece at agentteam.co.uk/share-trading.html. Read the two together.
Section ISeparation of powers
The organisational design deliberately prevents one agent from researching, sizing, approving and executing its own idea. The research and control departments contribute to the same proposal, but the risk function retains an independent veto and the broker connection is isolated.
Why separation matters:
- Language models can produce persuasive explanations even when the underlying evidence is weak.
- Several agents may repeat the same assumption, so a majority vote is not a reliable safety mechanism.
- Risk limits must remain enforceable even when models, prompts or data feeds fail.
- Broker credentials should never be available to research agents.
- Every decision should be reproducible from stored inputs, calculations, policies and approvals.
Agents recommend. Code calculates. Risk controls veto. Humans authorise. The execution service trades.
Section IIThe eleven roles
| # | Role | Responsibility |
|---|---|---|
| 1 | Chief Investment Officer (CIO) | Coordinates the process, writes the formal trade proposal. Does not override hard risk controls. |
| 2 | Market data agent | Gatekeeper for prices, volume, corporate actions, filings. Attaches source and timestamp metadata; halts on stale data. |
| 3 | Fundamental analyst | Structured output on financials, valuation, competitive position, catalysts. |
| 4 | Technical / quantitative | Trend, momentum, volatility, liquidity, factor exposure, entry/exit levels. |
| 5 | News, sentiment & macro | Announcements, filings, sector news, macro. Distinguishes publication from event dates. |
| 6 | Red-team | Attempts to disprove every proposed trade. Looks for contradictory data and hidden assumptions. |
| 7 | Backtesting & validation | Out-of-sample, walk-forward, transaction-cost-aware; look-ahead and survivorship-bias controls. |
| 8 | Portfolio manager | Allocation, sector / geography / currency / factor concentration, correlation with existing holdings. |
| 9 | Independent risk engine | Absolute veto. Deterministic policies stored outside model prompts. Kill switches. |
| 10 | Restricted execution service | Broker connection. Signed, validated, schema-checked orders only. Least-privilege credentials. |
| 11 | Monitoring & audit | Tracks assumptions, exposure, reconciliation. Records model, prompt and policy versions. |
Section IIIThe controlled decision workflow
Every proposed order passes through the same auditable sequence. A failed or missing stage stops the process rather than being silently ignored.
- Define permitted universe.
- Validate and timestamp data.
- Run independent analyses.
- Red-team the thesis.
- Create formal trade proposal.
- Backtest and validate.
- Assess portfolio impact.
- Risk approval or veto.
- Human approval.
- Execute and reconcile.
- Monitor and audit.
Section IVFormal trade proposal
Agents exchange structured records. The following fields are mandatory so that risk, execution and audit services can validate the proposal automatically.
{
"instrument": {"symbol": "ABC", "exchange": "LSE", "ccy": "GBP"},
"action": "BUY",
"strategy_id": "MOMENTUM_01_V3",
"thesis": "...",
"evidence": ["...", "..."],
"catalyst": "...",
"holding_period": {"min_days": 5, "max_days": 20},
"entry_condition": "price <= 12.45 GBP",
"invalidation_condition": "close > 13.20 for 2 sessions",
"exit_plan": ["take_profit @ 13.80", "stop_loss @ 11.90", "time_stop 20 sessions"],
"proposed_allocation": {"capital": 5000, "max_loss": 250},
"portfolio_impact": {"sector_delta": "+1.2% cons_disc", "correlation": 0.34},
"residual_risks": ["..."],
"confidence": 0.62,
"data_timestamp": "2026-07-13T09:15:00Z",
"approvals": {"research": "R-2018", "validation": "V-0912", "risk": "RISK-18267", "human": "HUM-90411"}
}
Section VRead the full blueprint
Companion blueprint
The full architecture — including the kill-switch conditions, seven-stage deployment roadmap (research mode → historical simulation → paper trading → shadow mode → human-approved live → limited automation → broader automation) and metrics to track from day one — is published at: