AI Agent Architecture - Quick Reference & Summary
Executive Summary
Axiom Genesis AI Agent Architecture is a meta-level automation system where AI agents autonomously design, configure, and deploy complete enterprise solutions based on natural language requirements.
Key Innovation
Instead of users manually configuring entities, workflows, forms, and reports, AI agents do this automatically by leveraging the Axiom Genesis RAD platform as their execution engine.
System at a Glance
USER: "I need an invoicing system with email reading, data extraction,
approval workflow, and reporting"
↓ (Natural Language Processing)
AI AGENTS:
└─ Communication Agent (understands user intent)
└─ Orchestrator Agent (plans execution)
└─ Knowledge Agent (gathers industry best practices)
└─ Entity Architect Agent (designs data structures)
└─ Workflow Designer Agent (creates automation)
└─ Form Designer Agent (builds UI)
└─ Report Builder Agent (creates dashboards)
└─ Security Agent (configures permissions)
└─ Integration Agent (sets up connections)
↓ (Configuration Generation)
CONFIGURATIONS CREATED:
• 5 Entities (Invoice, Vendor, Approval, etc.)
• 1 Workflow (8-step processing pipeline)
• 3 Forms (Data entry, Approval, Reporting)
• 2 Reports (Dashboards & KPIs)
• 4 Security Roles
• 2 Data Connections
↓ (Automatic Deployment)
AXIOM GENESIS PLATFORM:
✅ Entities deployed
✅ Workflows ready
✅ Forms available
✅ Reports accessible
✅ Security configured
↓ (Ready to Use)
USER: Solution deployed in ~5 minutes instead of 2-3 days!
Core Components
1. Agent Types (9 Total)
| Agent | Purpose | Output |
|---|---|---|
| Communication | User interface & dialog | Formatted responses, conversation history |
| Orchestrator | Master coordinator | Execution plan, task routing, state aggregation |
| Knowledge | Context & research | Best practices, templates, standards |
| Entity Architect | Data structure design | Entity configs with fields, relationships, indexes |
| Workflow Designer | Process automation | Workflow definitions with nodes and connections |
| Form Designer | UI creation | Form layouts, fields, sections, validations |
| Report Builder | Analytics & dashboards | Reports, KPIs, charts, visualizations |
| Security Manager | Access control | Roles, permissions, field-level security |
| Integration Manager | External connections | Connection configs for email, DBs, APIs |
2. Execution Model
Queue-Based & Event-Driven
Task Queue → Worker Process → Event Emission → State Update → User Push Notification
↓ ↓ ↓
Task stored Agent executes Progress updates Real-time feedback
with priority in parallel to Communication via WebSocket
where possible Agent
3. State Management (3 Layers)
| Layer | Storage | TTL | Purpose |
|---|---|---|---|
| Conversation | Redis | 24h | Chat history & context |
| Task | Database | 30d | Agent execution tracking |
| Project | Database | Permanent | Full solution blueprint |
4. Learning Loop
Requirements → Planning → Execution → Validation → Deployment → User Feedback
↓ ↓ ↓ ↓ ↓ ↓
Parse Decompose Agents Check Deploy Collect
intent into tasks execute output to platform improvements
& orch. validity
Data Flow Example: Invoice Processing System
Phase 1: Planning (0-1 minutes)
User Input:
"Create an invoice processing system that reads emails, extracts data,
validates it, and stores in database with approval workflow"
↓ Communication Agent Parses ↓
{
"intent": "build_solution",
"domain": "accounting",
"requirements": {
"inputs": ["email"],
"processing": ["extraction", "validation"],
"storage": ["database"],
"approval": ["workflow"]
}
}
↓ Orchestrator Plans ↓
Execution Plan:
Phase 1 (Parallel):
- KnowledgeAgent: Research invoice standards
- EntityArchitectAgent: Design Invoice, Vendor, Approval entities
Phase 2 (Parallel):
- WorkflowDesignerAgent: Create processing workflow
- FormDesignerAgent: Create entry forms
- ReportBuilderAgent: Create dashboards
Phase 3 (Sequential):
- SecurityAgent: Define roles & permissions
- IntegrationAgent: Configure email connection
- OrchestratorAgent: Deploy all configs
Phase 2: Execution (1-4 minutes)
Agents execute in parallel (where possible):
Knowledge Agent:
✅ Researches invoice standards (ISO 20022)
✅ Gathers tax compliance requirements
✅ Finds email extraction best practices
Entity Architect Agent:
✅ Designs Invoice entity
- Fields: invoice_number, vendor_id, amount, status, etc.
- Relationships: Invoice → Vendor, Invoice → Approval
- Indexes: (invoice_number), (status), (created_date)
- Permissions: Finance Admin > Manager > Viewer
✅ Designs Vendor entity
...
Workflow Designer Agent:
✅ Creates invoice_processing workflow
- Email input node
- Data extraction node (AI-powered)
- Validation node
- Database write node
- Approval routing node
- Notification node
Form Designer Agent:
✅ Creates invoice_entry form
✅ Creates approval_dashboard form
✅ Creates vendor_management form
Report Builder Agent:
✅ Creates invoice_status dashboard
✅ Creates vendor_payment_summary report
Phase 3: Deployment (4-5 minutes)
All configurations deployed to Axiom Genesis:
Entities:
INSERT INTO app_object_registries (Invoice, Vendor, Approval...)
INSERT INTO app_object_profiles (field configs...)
Workflows:
INSERT INTO workflow_definitions (invoice_processing...)
Forms:
INSERT INTO form_configs (invoice_entry, approval_dashboard...)
Reports:
INSERT INTO report_configs (dashboard, summary...)
Permissions:
INSERT INTO roles (finance_admin, finance_manager, finance_viewer)
INSERT INTO permissions (role_entity_action mappings)
Connections:
INSERT INTO connection_configs (email_connection...)
✅ System Ready!
Phase 4: User Feedback (5+ minutes)
System Presents:
"✅ Your invoice processing system is ready!
📊 What was created:
• 4 Entities (Invoice, Vendor, Approval, Report)
• 1 Workflow (8-step processing)
• 3 Forms
• 2 Reports
• 4 Security roles
• 1 Email connection
Next Steps:
[View System] [Deploy Live] [Modify] [Export Config]"
User Can:
• Review and refine any components
• Modify field names or workflow steps
• Ask AI for additional features
• Deploy immediately to production
Technical Architecture
Technology Stack
AI/LLM:
- OpenAI GPT-4 (primary)
- Anthropic Claude (backup)
- Google Vertex AI (option)
- Local LLMs (fallback)
Execution:
- Bull (job queue) or RabbitMQ
- Redis (state, caching, pub/sub)
- Node.js (agent runtime)
Storage:
- MSSQL (config database)
- PostgreSQL (state+project storage)
- MongoDB (optional document storage)
- Redis (conversation cache)
Real-Time:
- Socket.IO (WebSocket communication)
- EventEmitter (internal events)
Monitoring:
- Winston (logging)
- DataDog (monitoring)
- ELK (log aggregation)
System Architecture Diagram
┌─────────────────────────────────────────────┐
│ USER INTERFACE LAYER │
│ (Chat UI, Progress Dashboard, Reviews) │
└────────────────┬────────────────────────────┘
│
┌────────────────▼────────────────────────────┐
│ COMMUNICATION AGENT │
│ (Intent Parsing, Response Formatting) │
└────────────────┬────────────────────────────┘
│
┌────────▼──────────┐
│ Message Queue │
│ (Bull/RabbitMQ) │
└────────┬──────────┘
│
┌────────────┼────────────┐
│ │ │