VA.2026.013 · Floor 0 · service · hall 05
“one door for many minds — knocked once, answered by whichever is awake.”
VA-AI is the lightweight gateway of the collection — the thinned essence of a larger framework, keeping only routing, auth, and honesty. Providers are declared as plain JSON: a default route, keyed routes by prefix, an automatic door. When one mind sleeps, the next in line answers; cooldowns keep the sleeping ones undisturbed. Keys rotate from the database, never from the source.
Privacy is not a flag here but a boundary: every outbound message passes tokenization first — phone numbers, addresses, and names become stable placeholders — and only placeholders ever leave the room. The reply is rehydrated on return, streams included, mappings held per request and never persisted. Time and place are injected as situational awareness, scrubbed from echo unless asked.
Composition is opt-in and layered: metadata, then standing instruction, then the persona — one system message assembled in that order, ordinary calls untouched for SDK compatibility. Registration locks behind a secret when set; projects belong to their owners; management bows only to signed tokens. The subject's words pass through here daily — redacted at the door, restored at the exit — because a gateway that remembers plaintext is a liability wearing infrastructure.
VA.2026.013
VA-AI
LLM Gateway · Multi-Provider Routing · PII Redaction · Elysia + Bun
Thin gateway skeleton on the shared convention — schema-first persistence, eight-file modules, registry-mounted routes.
Two mechanisms that never mix: signed session tokens for management, hashed project keys for chat — revocation and expiry included.
JSON-declared providers with sequential fallback and cooldowns — serverless-safe, no sticky state.
Secrets out of source, CORS locked, rate limits and headers on, error shapes disciplined — the PoC grows a lock.
Always-on tokenization with stream rehydration, plus opt-in prompt composition with situational time — privacy and voice, together.
Hard-capped per-request budget and tighter orchestrator limits after serverless timeouts; an unknown model name now degrades gracefully instead of failing the call, and provider filters were relaxed so every healthy route can rank.
Several upstream accounts per provider with automatic selection, broken routes removed, and a retired key provider deleted outright — 61 commits by the end of October.
concepts — kept & discarded
kept — thin JSON-routed gateway; framework weight stays out
rejected — plaintext logging and single-key auth for everything
held — billing and metering wait beyond the PoC
archive ref — VA.2026.013/CON
cross ref — timeline fig. 01
curator annotations
a gateway that grows features becomes the framework it fled — stay thin.
what leaves the room should never be enough to find anyone.
an open door is a configuration, not an accident — label it.
| materials | JSON provider routing · fallback + cooldown · database key rotation · rate limit + JWT hardening · PII tokenize + rehydrate · opt-in prompt compose | dimensions | auth modes — JWT · project key · open · redaction — always-on · compose — opt-in · deploy — serverless · interface — OpenAI-compatible + SSE |
|---|---|---|---|
| condition | PoC · serverless deploy · postgres-backed keys · multi-account upstream keys | acquired | 2026 |
| revision | Rev. A | archive location | DWG-013 · floor Floor 0 · service |
| internal reference | VA.2026.013/M | origin | thinned from a larger framework until only the gateway remained, 2026 |
failed experiments
shipped with a placeholder signing secret. now refused at boot unless replaced.
registration stayed public when no secret was set. now locked the moment one exists.
redaction ate the timezone before composition could use it. order fixed: redact first, then compose around it.
draft concepts
research notes
— routing as JSON beats routing as code — providers change weekly, deploys shouldn't.
— redact before composing, or the composer will lovingly echo what you meant to hide.
— two key kinds with one verifier is how sessions chat and chats manage — keep them apart.
The gateway routes, guards, and redacts — nothing else. Every feature proposed here must prove it cannot live one layer up.
No real name, number, or address ever crosses the provider boundary. What returns is restored; what left was never enough.
Standard interfaces and untouched ordinary calls mean existing clients arrive without rewriting. Novelty lives in opt-in layers.
within the collection
future vision
VA-AI stays thin on purpose. Metering and billing wait beyond the PoC while routing tables grow heavier — but the promise holds: one door, many minds, nothing real ever leaving the room unmasked.