Public control evidence
This page is the public procurement surface for VaultAI. It separates what is live on the current Vercel deployment from the source-ready AWS/Azure controls that a bank deploys inside its own account.
Functional subsystem actions passed
Extreme vectors passed in quick verification
Parallel ledger and replay checks passed
Deployment truth table
vaultai.network is served by Vercel today
AWS ALB DNS cutover is intentionally not performed from this public evidence step because it changes production routing and must be executed only after buyer AWS credentials and registrar access are confirmed.
Sovereign Core APIs require authentication
Unauthenticated requests to protected status and health routes are expected to return 401 instead of exposing internal financial state.
Terraform and Packer assets are source-ready
The repository contains the AWS and Azure infrastructure definitions required for bank-owned deployment, BYOK, private networking, WAF, and hardened AMI handover.
/api/audit/pilot-evidence returns fresh signed JSON
The evidence route executes the banking crucible arithmetic, returns exact 18-decimal results, and signs the payload hash server-side for CTO verification.
Five enterprise pillars
These are deployable controls in the repository. A production AWS ALB binding is a DNS and AWS-account operation, so it should be executed against the buyer-owned cloud account during cutover.
Terraform defines region-scoped AWS and Azure deployments so a buyer can keep data, metadata, and operations inside their approved jurisdiction.
The deployment bundle includes self-contained Docker assets, offline compose files, and an air-gap runbook for bank-controlled environments.
AWS KMS and Secrets Manager are represented in Terraform with buyer-supplied key ownership guidance.
This public evidence center exposes the controls. Runtime APIs and the full Sovereign Core dashboard remain protected behind authentication.
The GitHub Actions deployment workflow includes security scanning, immutable container publishing, and provenance-oriented build steps.
Packer assets are present for encrypted Amazon Linux 2023 AMI creation with sanitization before buyer delivery.
The local chaos and migration suites exercise parallel ledger processing, deterministic replay, overload rejection, and signed evidence.
A bounded 100,000-event run validates independently sequenced currency cells, exact replay, idempotent retries, quorum-loss safety, and reserve-aware bank-run routing.
Application rate limits and infrastructure WAF rules are defined to reject overload traffic without losing ledger state.
Sovereign Core inventory
AST admission checks, deterministic execution tokens, and signed rejection handling.
Zero-float double-entry postings, integer micro-units, and rolling Merkle roots.
Legacy COBOL rule extraction with fail-closed parsing for malformed programs.
pacs.008 and pacs.009 header validation, repair, and compliance evidence.
Basel III LCR guardrails for capital routing and unsafe-trade aborts.
Solvency proof validation with forged-proof rejection.
Repeatable black-swan macro and liquidity stress simulations.
Post-quantum capability detection, rotation continuity, and fail-closed proofs.
Accreditation-gated fractionalization workflow for real-world assets.
Graph cycle detection for shell-company and laundering-loop patterns.
Contradictory directive detection and structured audit output.
Live dashboard console for transaction execution and evidence logs.
Verification evidence
These checks validate engineering behavior locally. True zero-downtime bank readiness still requires production-like infrastructure, multi-region failover drills, extended soak testing, and independent banking-control review.
Functional subsystem actions passed
Extreme vectors passed in quick verification
Parallel ledger and replay checks passed
Measured locally across 64 independently sequenced cells
Measured local kernel result; not a global network claim
USD, EUR, GBP, INR, JPY, AED, SGD, and CHF all reconciled
10,000 idempotent retry events produced no additional posting
Withdrawal requests modeled with protected reserves and durable queuing
333,334 peak TPS and 251 cells; not a physical load certification
npm run build passed with the post-build validation hook.
Login, balance lookup, transfer, overload, and graceful rejection flows passed.
/auditor now routes to this public enterprise evidence center.
To bind vaultai.network to AWS, the next controlled step is a Terraform apply in the target AWS account, ALB DNS extraction, registrar CNAME or A/ALIAS update, and a staged traffic verification.