An explainability-first, human-supervised enterprise AI architecture — designed for regulated industries, from the business requirements layer through to production infrastructure. Six design phases. Four intelligent modules. One coherent system.
Four things had to be true simultaneously for an autonomous seller to be architecturally viable: the regulatory framework had to be clear enough to design against, the tooling had to be mature enough to build production systems with, and the data infrastructure had to be fast enough to act on in real time.
In 2024–25, all four converged. The Autonomous Seller is a response to that convergence — a complete architectural design that takes each of the four enabling factors below and expresses it as a concrete engineering decision.
These aren't best-practice guidelines. In the EU AI Act and FDA regulatory environment, they are architectural constraints. Every component of the AS must satisfy all four.
Each layer has a single responsibility and a clean interface to the layer above and below it. XAI outputs and HITL checkpoints flow upward from the MLOps layer to the Experience layer. Governance and audit constraints flow downward from policy into the Infrastructure layer. Nothing bypasses a layer. Nothing is ad-hoc.
This is a concept overview. The full technical design — GCP reference architecture, Terraform IaC, ADK agent topology, and Vertex AI pipeline specs — is developed in Phase 2 (TOGAF D) and Phase 6 of the design process.
The four-layer model is deliberately borrowed from classic enterprise architecture thinking — but updated for the agentic era. Layer 1 is what users see and interact with, including the HITL approval surfaces. Layer 2 is where agent intelligence lives: the orchestration swarm, the event bus, and the A2A protocol. Layer 3 is where ML lives: the models, the XAI pipeline, the feature store, and drift detection. Layer 4 is where trust is enforced: zero-trust networking, encrypted storage, IAM, immutable audit logs, and the IaC that makes all of it reproducible and auditable.
The insight is that in a regulated enterprise, trust cannot be a property of the application — it must be a property of the infrastructure. If the infrastructure doesn't enforce it, any application can violate it. Layer 4 makes compliance physically un-bypassable.
Each regulation below imposes specific architectural constraints — not just documentation requirements. The design satisfies them structurally, not through post-hoc reporting.