Field Notes
The architecture, product, and design thinking behind Felix — the plan as it stands. Deterministic facts, generated words; advice, never automation.
Engineering
Overview
The system in one narrative — layers, storage authority, tenancy, cost, and the build roadmap.
Data pipelines & lake
Raw/curated Parquet zones, universe-driven prices, news → story synthesis, broker ingestion.
Analytics & daily AI
The deterministic fact catalog, the daily agent with quantity-preserving validators, the action lifecycle.
App DB & web
Schema catalog, two-plane API, Supabase Auth, page-by-page UX from Today to Settings.
Chat agent
Grounded toolbelt with real what-if analytics, SSE contract, drafting actions from conversation.
Tenancy, BYOK & ops
Gateway key hierarchy, Vault-backed BYOK, budgets and usage ledger, isolation, evals-as-CI.
Supabase as DB + auth
Why Supabase is the app DB + auth layer — RLS from day 1, Vault for keys, lake stays on R2.
Cost model
Shared layer, per-user spend, infra, and scenario totals at the current defaults.
Research
Validated brief
The case for Felix — market, competition, feasibility, top risks, and the Go decision, kept current as decisions land.
Market landscape
TAM/SAM/SOM, segments, trends, and the RSU-tech-worker beachhead call.
Competitive analysis
The advisory-only white space — positioning map, pricing gap, and defensibility, with facts verified July 2026.
Feasibility
Ingestion options, core algorithms, the AI layer, the RIA question, and MVP scope.
Assumption map
22 assumptions across six categories, top-5 risks ranked, each with its current status.
Decision log
The April 2026 discovery decisions, each with its current status — stands, evolved, or superseded.
Design phase — no application code yet. The build roadmap runs phase 0 (scaffold) through phase 8 (multi-user hardening), ordered to make the app useful early: holdings visible → facts computed → daily briefing end-to-end → verification → news and markets → chat.