03 — AGENT SYSTEM

Multi-Agent Architecture

Orchestrator drives the ReAct loop while 7 specialist agents handle domain-specific processing. Click any agent to expand its full specification.

Central Orchestrator

Responsibilities

  • Drive REASON → ACT → OBSERVE reasoning loop
  • Delegate to specialist agents based on workflow stage
  • Manage session state and context window budget
  • Trigger summarization when token threshold is exceeded
  • Persist full reasoning trace for audit replay
  • Handle escalation and fallback routing

Node Pool

Orchestrator Pool — dedicated K8s pods with fast-model LLM access (8-13B params).

Tech Stack

Specialist Agents

7 Domain Specialists

Each specialist agent handles a specific domain task and calls typed tools for government API interactions.

Parses business rules from plain-English SKILL.md, compiles into canonical YAML policy packs, validates schema, and manages versioning.

Output

  • Versioned YAML rule packs
  • Rule expressions per service type
  • Required fields, integration groups, fee/exemption logic

Validates applicant/service eligibility and prerequisites by calling UDB, MOHRE, DEDx, Shory, Medical Fitness, and Insurance APIs.

Integration Groups

A: UDB + Medical + Insurance B: MOHRE + DEDx + MOFA

Autofills and validates in-form fields and dependencies. Writes draft requests to PostgreSQL.

Integration Groups

C: Shory + MOJ + DOH D: Lease Contract (DMTS)

Validates uploads, runs ICAO compliance checks, handles medical-related document and task coordination.

Integration Groups

E: DOH/EHS Medical Fitness

Discovers available appointment slots and books them through ICP Management, MOHRE, and AAMER systems.

Integration Groups

F: ICP Mgmt + MOHRE + AAMER

Computes fees, evaluates exemptions, processes payment, and triggers final request submission.

Integration Groups

G: CustomerPulse + Shory H: MOHRE + Shory + DOH + Insurance I: TAMM + Airlines + RAKEZ + DubaiNow

Reduces context without losing critical state when the orchestrator's token budget is exceeded. Preserves key facts while compressing intermediate reasoning.

Node Pool

Orchestrator Pool — uses fast-model LLM class (8-13B params).

Integration Pattern

Tool-Calling Strategy

Government integrations are exposed as strongly typed tools. Agents call tools directly through a middleware layer that handles six cross-cutting concerns:

🔒
Auth Token

Acquisition & refresh

→
🔄
Retry

Exponential backoff

→
⚡
Circuit Breaker

Fault isolation

→
🚦
Rate Limit

Per-API throttling

→
📋
Schema

Validation

→
📋
Logging

Structured traces