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. Planned maintenance windows are communicated 72 hours in advance via the telemetry dashboard and communications channel.

Primary data center: Johannesburg, South Africa (Sovereign HPC Cluster). Secondary/DR: Cape Town, South Africa. All data processing and storage occurs within South African borders, ensuring full POPIA compliance and data sovereignty. No primary workloads are processed outside the Republic of South Africa.

Yes. Enterprise and Sovereign Tier operators can deploy workloads in hybrid configurations that bridge the SEE engine with on-premise systems via the ERP Strategy Pattern adapter interface. Supported integrations include SAP, Sage, QuickBooks, Xero, and custom REST/gRPC endpoints. Cross-premise workloads are subject to R5 Verification Gate auditing.

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. Division-specific encryption keys are managed through the Sovereign Key Management Service, with key rotation occurring every 90 days. HMAC-SHA256 signing ensures end-to-end integrity for all API communications.

Continuous automated auditing is performed by the R5 Verification Gate, which monitors every operation against constitutional rules and compliance requirements. External SOC 2 audits occur annually with a 12-month observation period. POPIA compliance audits are conducted bi-annually. All audit trails are immutable and retained under R6: No Forgetting.

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. The Data Sovereignty Officer monitors compliance under R8: Constitutional Adherence.

Invoicing is automated monthly based on metered usage tracked through the telemetry dashboard. Payment methods include EFT, credit card (Visa/Mastercard), and SADC-region wire transfers. Enterprise and Sovereign Tier operators can request Net-30 or Net-60 terms. All invoices are available in the Payments section of the SEE Control Panel.

Workloads are metered by compute units consumed, measured as SEE Operations (SEEOps). Each workload's compute consumption is calculated based on CPU time, memory allocation, storage I/O, and VGate processing cycles. Usage dashboards in the telemetry console provide real-time metering data. Monthly allocations reset on the billing cycle date.

Yes. Tier changes take effect at the next billing cycle. Upgrades are processed immediately with prorated billing for the remainder of the current cycle. Downgrades require verification through Platform Governance to ensure compliance with the target tier's operational constraints. Tier changes are logged under R4: Temporal Binding.

The Telemetry Dashboard provides real-time monitoring of all active workloads, including execution status, compute consumption, estimated completion time, and VGate verification state. The My Workloads section provides a detailed list view with filtering by division, status, and date range. Webhook notifications can be configured for status changes.

Workload failures are captured by the SEE's automatic retry mechanism, which implements exponential backoff with configurable max retry count (default: 3). After exhausting retries, the workload is flagged for manual operator review under R5. Failed workloads are logged with full diagnostic telemetry under R6: No Forgetting for post-mortem analysis.

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. Scheduling is managed through the Workloads section of the SEE Control Panel, with all schedules audited under R4: Temporal Binding

Cross-division workloads require Enterprise or Sovereign Tier access and explicit Platform Governance approval under R3: Division-Aware Routing. Each workload must declare a primary division and any secondary divisions involved. The SEE engine enforces strict data isolation between divisions while allowing controlled data flow through the Governance integration layer.

Division role changes are processed through the Operator Profile settings. The request undergoes R5 Verification Gate review and requires approval from both the current and target division leads. Role changes are timestamped under R4: Temporal Binding, and all historical role data is retained under R6: No Forgetting for audit purposes.