Enterprise FAQ

The SEE is a sovereign HPC intelligence platform built on a microservices architecture orchestrated by Camunda 8 Zeebe. It comprises division-specific Web Workers, a shared Prisma database schema, Redis pub/sub for inter-service communication, and the Constitutional Governance Layer that enforces R1-R8 rules. The system runs on Tier III-equivalent infrastructure in Johannesburg, South Africa.

IntelliAI Group guarantees 99.99% platform uptime for Enterprise Tier operators, measured monthly. Standard Tier receives 99.9% uptime. SLA credits are automatically calculated and applied through the billing system.

Division access is managed through the Operator Profile. Standard Tier operators have single-division access. Enterprise Tier operators can request multi-division routing through Platform Governance. Access is verified against Division Attribute Vectors.

IntelliAI Group holds SOC 2 Type II certification, POPIA compliance, ISO 27001:2022 certification, SARS ISV for IntelliTax SA, FHIR R4 for IntelliHealth AI, and PCI DSS v4.0 (in progress).

POPIA compliance is enforced at every layer of the SEE framework. Data processing is conducted under lawful bases defined in POPIA Section 11. Data subject rights under Sections 23-26 are automated through the Sovereignty Controls panel. Cross-border transfers comply with POPIA Section 72.

All data in transit is encrypted using TLS 1.3 with AEAD cipher suites. Data at rest is encrypted using AES-256-GCM with hardware-backed HSM key management. Key rotation occurs every 90 days with HMAC-SHA256 signing for API communications.

Three tiers: Standard (single-division access, 99.9% SLA, email support), Enterprise (multi-division routing, 99.99% SLA, phone+ticket support), and Sovereign (dedicated HPC partition, 24/7/365 support, custom integration).

Navigate to the Deploy Workload page in the SEE Control Panel. Select your target division, configure workload parameters, and submit through R5 Verification Gate. The workload will be validated against constitutional rules and routed to the appropriate division pipeline.

Yes. The SEE engine supports cron-based scheduling and batch processing for recurring workloads. Batch workloads can be configured with dependencies, conditional execution rules, and parallel processing limits.

Cross-division workloads require Enterprise or Sovereign Tier access and Platform Governance approval under R3: Division-Aware Routing. Each workload must declare a primary and secondary divisions involved.