Two-Plane AI Architecture

Control Plane / Reasoning Plane

The organization owns the rules. The model performs the work.

Evilware Labs separates governance from reasoning. The control plane evaluates identity, clearance, policy, and data classification before the reasoning plane is allowed to act.

REQUESTCAPTURED
IDENTITYVERIFIED
CLEARANCEEVALUATED
POLICYAPPLIED
MODELSELECTED
AUDITWRITTEN
CONTROL PLANE
Authentication, policy evaluation, model routing, escalation, redaction, and audit handling.
REASONING PLANE
Privately hosted or customer-approved models execute approved work under routed context.
DATA PLANE
RAG sources, document stores, vector indexes, knowledge bases, ticket systems, and approved operational datasets.
AUDIT PLANE
Immutable request records, policy decisions, response metadata, source references, and operational review logs.

Design assumptions.

The architecture is built around enterprise reality: policy changes, clearance differences, tenant boundaries, and audit requirements.

A1

Models are replaceable

The durable value is not a single model. It is the governance, routing, logging, and deployment structure around the model.

A2

Policy lives outside the weights

Organizational rules should be declared, reviewed, versioned, and audited instead of being buried in opaque behavioral tuning.

A3

Every action has lineage

High-trust AI requires a clear record of who asked, what was requested, what rule applied, and what system responded.