Stateless Gateway for Institutional Inference
Part 11 is vision: it describes how the Sovereign architecture Pocket Portfolio already ships in consumer form maps onto institutional connectivity (VPC, managed browser, private gateways). It is not a press release for a named bank deal or a dated GA SKU — those land when contracts and pipes are signed — but it is written from the premise that Pocket Portfolio is engineered to a bank-grade bar on the axes that matter for customer and market data.
Bank-grade is architecture, not capex
Sovereignty — user-anchored truth, bounded context across the wire, stateless inference for the portfolio payload — is compliance-shaped by construction. That is a stronger default than bolting a chatbot onto a central ledger and hoping log pipelines stay narrow.
Large institutions can outspend almost anyone on perimeter and headcount; capex is not the same as minimized blast radius. When sensitive narrative is copied everywhere “for AI,” the attack surface and subpoena surface grow with it — and headline breaches at major financial firms are a standing reminder that big budgets do not automatically mean small custody.
Pocket Portfolio’s bet is the opposite direction: fewer durable copies of the financial story on the vendor side, clearer boundaries between telemetry and prompt bodies, and inference that behaves like a pure function over bounded context. That is bank-serious engineering without pretending that marble lobbies equal sound data design.
The question institutions lead with
Security and data teams still ask where customer and market data lands after the question is asked. Indefinite central storage of rich portfolio context is the failure mode they are trying to avoid — and it is the failure mode Sovereignty refuses by default.
The consumer product already embodies that shape:
- Aggregation at the edge — the
buildPortfolioContext pattern: structured context is assembled where the user’s data already lives, not dumped wholesale into a vendor database for inference.
- Stateless HTTP inference —
/api/ai/chat takes bounded context for the request and does not treat that payload as ledger rows to retain.
- Telemetry without prompt archives — operational signals (for example
toolUsage-style metadata) are separable from full prompt bodies.
A B2B deployment extends the same contract inside the bank’s VPC or a managed browser environment: a gateway sends only bounded context plus the user’s question, receives a streamed answer, and does not widen retention to “everything we ever saw in prompts.”
What paperwork and pipes still add
Even when the technical bar is already institution-grade, enterprise adoption still runs through:
- Legal and privacy — DPAs, subprocessors, liability, data-processing terms.
- Network controls — private connectivity, mutual TLS, access boundaries the bank expects.
- Model and vendor governance — which models, which regions, audit trails the institution owns.
- Model risk and validation — internal sign-off processes that calendars, not architecture alone, govern.
That is velocity and procurement, not a verdict that the product philosophy is “consumer-only.” The claim here is: Sovereign design already meets a bank-grade security and data-handling posture; what remains is contracting, connectivity, and their governance calendar — not an excuse to centralize first and minimize later.
Part 11 of Sovereign Engineering.
Read the full Sovereign Intelligence book or try the app.