FAQ
Questions, answered directly.
What institutions ask before they engage — platform, validation, security, and access — answered in one place, without a funnel. For precise numerics, the model-risk dossier, or independent validation reports, reach the founder directly via contact.
Platform Overview · 01 / 04
What is Scientific Analytics Alliance?
Scientific Analytics Alliance (SAA) builds the Sovereign Risk Infrastructure — an integrated, institutional-grade ecosystem of seven production modules covering portfolio risk analytics, physical-financial digital twins, narrative intelligence, equity & cross-asset research, digital-assets rating, a 22-agent AI decision council (ARIN), and a control-plane orchestrator (KOKON). The platform is designed for global banks, insurers, asset managers, regulators, and sovereign-level institutions that require deterministic, auditable risk math at sub-millisecond latency. NVIDIA Inception Program member.
What is the “Sovereign Risk Infrastructure”?
The Sovereign Risk Infrastructure is SAA’s positioning name for an end-to-end risk platform that eliminates the trade-off between speed and auditability. At its core: the proprietary ARIN22 deterministic kernel for sub-millisecond VaR / CVaR revaluation; the 22-agent ARIN council for cross-domain verdict consensus under NeMo Guardrails; and the KOKON control plane for HMAC-signed audit trail and human-in-the-loop oversight. Six product modules feed analytical data into the council; KOKON orchestrates and serves as the seventh callable operator endpoint.
What are the seven production modules?
(1) ARIN — central 22-agent decision council and RAG-backed Hydra Ontology (~1.7M nodes, ~11.76M relationships, ~3.44M RAG chunks). (2) Global Risk Intelligence — physical-financial digital twins via the PARS Protocol with 5 autonomous agents. (3) News Analytics — 12 narrative-intelligence agents with Impact Graph. (4) Risk Analyzer — multi-method VaR / CVaR engine, primary client of ARIN22. (5) Investment Analytics — 6-axis equity & cross-asset research. (6) Digital Assets Analytics — 6-category AA-D weighted rating model. (7) KOKON — control plane, governance, and agent calibration.
Who are typical institutional users?
Global systemically important banks (G‑SIBs), regional banks, insurance companies (especially Munich Re-class reinsurers), asset managers, infrastructure funds, REITs, sovereign wealth funds, family offices, hedge funds, and government / regulatory agencies requiring Fed/OCC/FDIC SR 26‑2-grade model risk practice, Basel III backtesting, and EU AI Act / DORA-aligned governance. Public access is provided for analytical demonstration; production execution is gated by an integration NDA and KYC/AML on the counterparty.
Validation & Methodology · 02 / 04
How is the ARIN22 deterministic kernel validated?
ARIN22 has been validated against an external Monte Carlo reference under three independent campaigns: (a) the production 1,008-job campaign (28 scenarios × 4 horizons × 3 samplers × 3 tiers, 0 failures, two-regime Fed/OCC/FDIC SR 26‑2 quality gating); (b) the 44-job good-class holdout pack (no-harm verification on bulk regime — avg 0.0366% / p95 0.1338% / 5,696× speedup, 100% PASS); and (c) an EVT overlay layer for sub-bp tail-risk accuracy. Full methodology and per-scenario results: see the ARIN22 demo and methodology.
How is ARIN22 different from Monte Carlo?
Monte Carlo is stochastic — different runs produce different verdicts because they sample the random distribution. ARIN22 is deterministic — given identical inputs it always returns the identical answer, because it is a closed-form mathematical solution rather than a sampling procedure. This makes the kernel reproducible by definition (same input → byte-identical output) and removes the source of variance that breaks Fed/OCC/FDIC SR 26‑2 reproducibility audits. Speedup vs MC is regime-dependent: ~5,700× on bulk / good-class, up to ~3M× on stress / chokepoint-tail. ARIN22 is complementary to Monte Carlo, not a replacement — both engines run in production and are reconciled per verdict.
Do we need NVIDIA GPUs to run ARIN22?
No. ARIN22 deterministic risk-core validates identically on commodity ARM CPU at the kernel-call layer — sub-10 µs split runtime, tens of thousands of times faster than Monte Carlo equivalent, with better than 0.05% deviation at the 99.9th percentile vs Monte Carlo gold-standard. Validated on a synthetic Tier-1 sovereign-heavy bank book with high-correlation sanctioned-state exposure (per OFAC / UN sanctions lists). The 8×H100 NVIDIA Innovation Lab stack is layered on top for batch throughput at Enterprise Wave scale (8.8 B paths per backend · 8,800 cases per backend · 0 execution failures). Kernel correctness is CPU-bound; GPU is for production scale-up. No GPU lock-in. Every result is stamped with hardware fingerprint and run SHA for replay across environments. Detailed benchmark numbers (precise µs, speedup×, q999%, hardware fingerprint, run SHA) are released to bank model-risk under NDA only.
What does “US-registered” mean for ARIN22?
The name ARIN22 is a US-registered name for the deterministic risk-core. The name is public and may appear in UI, marketing, decks and customer-facing material. The kernel implementation (method derivation, per-module specialization, internal algorithm class) is a protected trade secret of Scientific Analytics Alliance Inc., with provisional patent filings in preparation covering: the deterministic 99.9 tail kernel · the decision-evidence cryptographic spine · the multi-stage release validator · the hash-chained backtest harness. Three-tier disclosure governs precise numerics: TIER 1 (public, this site) carries general phrasings only (sub-10 µs, tens of thousands×, < 0.05% q99.9); TIER 2 (under NDA) carries precise numbers, hardware fingerprint and run SHA; TIER 3 (under signed engagement) carries method derivation and per-module specialization.
How does SAA prevent LLM hallucination?
Three independent layers: (a) NVIDIA NeMo Guardrails enforces factuality, safety, and compliance constraints on every LLM output (NVIDIA-vendor stack, not a homebrew prompt-filter). (b) The 5-LLM sovereignty fallback chain (vLLM local H100 → NVIDIA NIM → GPT‑5 → DeepSeek R1 → Ollama) ensures vendor-independence. (c) The proprietary 7-rule math-to-narrative audit engine blocks specific failure modes — Cascade Amplification, SPOF Fabrication, Regime Fabrication, Severity Escalation, Downplay-in-Critical, Polarity Inversion, Cascade-Through-Zero — before any verdict is committed.
Are verdicts reproducible? What is in the audit trail?
Yes. Every verdict carries per-verdict provenance (input hash, agent assignments, LLM provider used, NeMo Guardrails clearance, ARIN22 kernel call ID, MC reference run ID, NeMo audit log) under HMAC-signed append-only storage in the KOKON control plane. The platform enforces 5 Decision-Integrity Invariants: data immutability, append-only verdicts, no backflow, single exit, data freshness. Designed to satisfy Fed/OCC/FDIC SR 26‑2 forensic reproducibility and EU AI Act Article 12 record-keeping requirements.
Security & Compliance · 03 / 04
What compliance frameworks does SAA cover?
The platform is architected for institutional compliance across: SOC 2 Type II, GDPR / UK GDPR, ISO 27001, NIST CSF 2.0, DORA (EU 2022/2554), EU AI Act, PCI DSS, FedRAMP, Fed/OCC/FDIC SR 26‑2 model risk management, and Basel III for backtesting. Specific certifications and audit reports are released to qualified counterparties under standard NDA. See security overview.
How is data hosted — on-prem, private cloud, or public?
Three deployment patterns are supported: (a) public cloud for the demonstration / evaluation tier (SAA-hosted on hardened infrastructure with TLS, structured logging, and HMAC audit trail); (b) private cloud for institutional production (customer-owned VPC, BYOK encryption, isolated tenancy); (c) on-premises for sovereign deployments (full-stack delivery including ARIN22 kernel, KOKON control plane, and the 22-agent ARIN council). Hardware reference: NVIDIA H100 (80 GiB) DGX-class node, 8×H100 + 208 vCPUs + 1.83 TiB RAM.
Is the platform Fed/OCC/FDIC SR 26‑2 / model-risk-management compliant?
The platform is architected for Fed/OCC/FDIC SR 26‑2 conformance: (a) every model output is reproducible and audit-traceable; (b) validation is performed under explicit two-regime quality gating (bulk vs chokepoint-tail) per Fed/OCC/FDIC SR 26‑2 regime-conditional practice; (c) independence-of-validation is preserved by the multi-LLM fallback chain (no single-vendor lock-in); (d) ongoing monitoring is enforced via the KOKON control plane and the 5 Decision-Integrity Invariants. Customers retain ultimate compliance responsibility — SAA provides the model-risk infrastructure, not the regulatory submission.
Are agent decisions traceable to specific human review?
Yes. Human-in-the-loop (HITL) escalation is enforced by KOKON for any verdict that hits one of the configurable triggers: confidence threshold breach, novel-scenario flag, regulator-tagged entity, override request, or compliance-officer review. Every escalation produces a signed reviewer attestation that becomes part of the verdict provenance. Designed for institutional governance committees, internal audit, and regulator-facing forensic review.
Access, Integration & Pricing · 04 / 04
How do I get access?
Demonstration access (read-only analytical views of ARIN22, the 22-agent council, and the seven production modules) is available via the contact page. Production access — write operations, custom integrations, on-prem delivery — is gated by a standard institutional NDA, KYC/AML on the counterparty, and a scope-of-work agreement.
What integration interfaces are available?
REST (versioned, typed, JWT-authenticated), WebSocket (real-time signal stream + verdict push), Webhook (configurable event delivery), Bulk export (Excel / PDF / JSON / CSV), and chat / messaging (Telegram digests). All endpoints share a unified HMAC-signed audit trail. Endpoint paths, auth scopes, rate limits, and configuration parameters are released under standard integration NDA — not disclosed publicly.
What languages are supported?
Production interfaces ship in English and Russian (EN / RU). Additional languages are added on a per-customer basis under the integration scope-of-work. The 22-agent ARIN council operates in English internally; multi-language output is generated under NeMo Guardrails for factuality preservation across translations.
What is the pricing model?
Pricing is customised by deployment pattern, module mix, integration scope, latency SLA, and counterparty profile. The standard institutional structure is a per-seat / per-module annual licence with a separate kernel-call commit for ARIN22 production traffic and an on-prem delivery fee where applicable. Demonstration access is free under fair-use limits. Contact sales for a structured quote.
