Skip to contentSkip to Content
DocsArchitectureOverview
Architecture

System architecture

How the Advizr platform is built, starting with the DOE framework that separates AI judgment from deterministic code. We’re rebuilding this section page by page with real commands, schemas, and diagrams pulled from the live systems — what’s published here is verified, not aspirational, and sections reappear in the sidebar as they’re completed.

Start here

The DOE framework→

Directives, Orchestration, Execution — the three-layer architecture behind every Advizr build.

Infrastructure→

Repositories, hosting, and the tech stack behind every property.

Knowledge base→

The three-tier knowledge system and the 13 MCP tools agents use.

DOE at a glance

The entire system is built on three layers. Directives define the goal. Orchestration (AI) routes work and handles errors. Execution (Python) runs deterministic code with no probabilistic AI.

DirectivesSOPs define goalsOrchestrationAI routes & decidesExecutionDeterministic code

Why it works: 90% accuracy per step compounds to 59% over five steps — so complexity is pushed into deterministic code.

DOE Architecture - three layers separating directives, orchestration, and execution
The three layers of Advizr's DOE architecture

What’s coming

Deployment pipeline, database topology, the automation pipeline, and the engineering practices — each rebuilt from the live systems before it returns to the sidebar.

Last updated on
GlossaryDOE Framework