AESOP Control Plane — Domain Architecture

Architecture

Control Plane — One Instance

AESOP Transformation OS

Domain-agnostic. Evaluates agents, tracks portfolios, generates operationalization plans. Does not render domain UIs.

Evaluate

Multi-agent scoring Bias & safety Hard veto rules Drift detection Regulatory mapping

Portfolio

Cross-domain dashboard Adoption metrics ROI tracking Status across all agents

Operationalize

RACI generation Adoption plans Maintenance plans Roadmap generation

Domain Registry

Legal Healthcare Finance HR Operations

filter portfolio · scope evals · route agents

↓

Execution Plane — Many Apps

Each domain function is its own focused app. Own UI. Own workflow. Thin integration back to AESOP for governance and portfolio tracking.

Built

Contract Review

Upload → classify → extract → score → flag. 5 specialized agents. Human-in-the-loop review workflow. Legal standards library.

→ AESOP: eval hooks + portfolio endpoint

Built

Employment Legal

Separation agreement generator (US/EMEA/Australia). Legal metrics agent for outside-counsel spend. Built inside a large corporate legal department.

→ AESOP: portfolio registration

Practice area classification. Urgency scoring. Conflict check triggers. Staffing recommendation. Routes to the right partner.

→ AESOP: eval on day 1 + portfolio

Roadmap

Due Diligence

Bulk document review. Clause-level comparison against target standards. Deltas only to reviewer.

→ AESOP: eval + portfolio

Roadmap

Regulatory Monitor

Monitors regulatory updates. Maps to active client matters. Surfaces affected engagements.

→ AESOP: eval + portfolio

Roadmap

Knowledge Mgmt + Reporting

Precedent search. Clause libraries that learn. Client-facing outcome reports as retention asset.

→ AESOP: portfolio

Integration Protocol — The Thin Contract

Each function app exposes three endpoints. AESOP polls them. That's it. No shared database. No UI embedding. Each side stays focused.

Health + Status

Is the agent running? What's its last evaluation score? Any drift detected? Uptime and error rate.

GET /api/aesop/health

Metrics + Outcomes

Adoption rate, throughput, time saved, cost impact, user satisfaction. Domain-specific KPIs in a standard schema.

GET /api/aesop/metrics

Evaluation Target

AESOP hits this endpoint to run evaluation suites against the agent. Returns agent config, instructions, and test surface.

POST /api/aesop/eval-target

What AESOP Never Does

01

Render domain UIs

AESOP doesn't show contract details, matter forms, or diligence checklists. Each function app owns its UX. AESOP shows scores, status, and trends — the governance view.

02

Execute domain workflows

AESOP doesn't process contracts or triage matters. It evaluates the agents that do. The execution plane handles execution. The control plane handles oversight.

03

Store domain data

Each function app owns its database. AESOP stores evaluation results, portfolio state, and operationalization plans — metadata about agents, not the agents' data.

04

Get bigger with each domain

Adding a Legal function or a Healthcare function adds one entry to the domain registry and one filter to the portfolio dashboard. That's the only AESOP UI change. The complexity lives in the function app, where it belongs.