Storage
WDBX
Episodic substrate: durable records, vector retrieval, causal history, and structural provenance.
Platform
Inspect the system behind the offering.
Explore trace, control, evaluation, and runtime capabilities alongside the layers underneath them.
The trace and private runtime capabilities are partial; the control plane is in development and the evaluation mesh is planned. Read each status before choosing an integration.
Inspect the source behind this pageStack
Bottom to top.
Compute
ABI
Deterministic persona routing, template completion, and source-defined tools.
Application
Abbey
Assistant source: persona profiles, capability ledger, and local CLI.
Product
Quesar
Experimental local website builder: browser client, paired operator-owned service, and separately configured model provider.
This checkout
Independent gates. One repository.
quesar.cloud is the current site and contains the local service clients, sidecars, and native shell. Each needs its own verification; a green web gate does not prove device behavior.
| Path | Purpose | Status |
|---|---|---|
| src/ | The one app: TanStack Start site, console, admin, workspace, demos, Quasar screens, and cinematic showcase | Current |
| migrations/ | Postgres schema (Neon, or in-memory PGLite without DATABASE_URL): auth, notes, audits, connectors, rate limits | Current |
| sidecars/quasar-service/ | Local AI site-builder service (Bun, port 4700) that the /quasar screens drive; run it yourself, never hosted | Experimental |
| sidecars/python-worker/ | Optional local document extraction and embeddings worker, reached by URL, never spawned | Experimental |
| native/ | Capacitor shell source that loads the deployed site, with an Android project and a CloudKit availability plugin | Partial |
| notes/ | Merge spec, plan and gap matrix, plus the pre-merge MLAI records under notes/mlai/ (docs/ holds the built static site) | Current |
Personas vs products
Two color axes. Do not mix them.
Product accents: WDBX cyan, ABI violet, Abbey emerald. Persona colors: Abbey emerald, Aviva violet, Abi cyan. The ABI product is violet; the Abi persona is cyan.
Abbey
Empathic polymath
High-EQ tutor and partner. Scaffolds, names uncertainty, and keeps the human in the loop.
Aviva
Unfiltered expert
Direct, concise, unhedged. Fewer tokens by design. Facts without preamble.
Abi
Adaptive moderator
Routes and blends. Classifies intent, applies policy, and reports what the ledger can prove.
Configuration
What the active crate actually sets.
Sourced from the Rust substrate. Not a scoreboard.
- Engine
- Layered HNSW
- Concurrency
- MVCC
- M
- 16
- efConstruction
- 40
- efSearch
- 32
- Metric
- Cosine
- Addressing
- Content-addressed
- Sharding
- Not established
Related
Gama is not Quesar.
Gama
A modular declarative Swift UI framework with TUI, Apple, WebAssembly, and embed backends. It lives at Gama. It is not a Quesar product, not an Abbey runtime, and not evidence of a shipped spatial engine.
Trust boundary
Configured console Chat: three boundaries.
The server-side console Chat path checks identity, provider configuration, and audit storage within one request. Broader runtime control-plane work has separate status and acceptance requirements.
Account-scoped access
Protected console functions use Better Auth sessions and scope per-user records by user id. Admin access requires an allowlisted email and a linked Google or Apple account. Public inquiry and configuration functions have separate controls.
One server-side model interface
Website model requests use a server-side interface configured for xAI or Cloudflare AI Gateway to Gemini. Console Chat checks provider availability and a per-user rate limit; the request builder does not automatically add account email. Provider and deployment acceptance require separate evidence.
Records you control
Conversation audits and workspace refresh tokens are sealed with AES-256-GCM under APP_ENCRYPTION_KEY, bound to their owner and purpose. Console Chat requires current audit consent and stores its sealed exchange before returning a reply. Contact inquiry fields are stored separately and are not covered by this application-level sealing.
One request
Five checks for console Chat.
In the configured server console Chat path, authenticate, consent, generate, encrypt, and store the audit before returning the reply. These checks are implemented in source. The static preview has no server chat, and live deployment acceptance requires separate evidence.
Inspect the security model- 01
Authenticate
CurrentThe protected console Chat function requires a Better Auth session and uses that user's id. This requirement does not apply to every public server function.
- 02
Consent
CurrentConsole Chat requires acceptance of the current audit policy before its provider request. Other website features have their own data and permission boundaries.
- 03
Generate
CurrentConsole Chat requires a configured provider and checks a per-user rate limit before generation. The server request does not automatically include account email.
- 04
Encrypt
CurrentConsole Chat refuses without a valid audit-encryption key. Its prompt and reply are sealed with AES-256-GCM, bound to the audit owner.
- 05
Commit
CurrentConsole Chat stores the sealed audit before returning a successful reply. If audit storage fails, the generated reply is withheld.
Product boundary
An experimental local builder.
The Quasar browser client pairs with an operator-owned service that scaffolds Next.js projects and uses a configured provider for generation. Live provider generation remains unverified. ABI, WDBX, and Abbey have separate source and integration boundaries.
What it is
Quesar's available source surface is the experimental Quasar website builder: a browser client paired to a separately running operator-owned service. Generation uses a configured provider; live provider acceptance remains unverified.
Separate acceptance boundaries
Builder source does not establish a trained Quesar foundation model, a hosted Abbey product session, compliance certification, or a performance result. The configured website console is a separate model-request path.
Docs