Architecture boundary
Next.js owns product rendering, authenticated UX, and AI route handlers while Go owns authoritative finance APIs, portfolio math, provider normalization, and audit-backed mutations.
Briefs
Aperture publishes implementation notes that explain how the product separates research support from trading, keeps user-owned finance data behind server boundaries, and verifies AI output with deterministic evals.
Next.js owns product rendering, authenticated UX, and AI route handlers while Go owns authoritative finance APIs, portfolio math, provider normalization, and audit-backed mutations.
Portfolio briefs, filing summaries, goal plans, and risk explanations are schema-checked for citations, freshness labels, refusal behavior, and advice-boundary language.
The research room combines filing chunks, watchlist context, saved citations, assumptions, and source timestamps so outputs can be reviewed instead of blindly trusted.
The case-study material focuses on real data flow, disabled-by-default external model spend, server-enforced entitlements, signed webhooks, and polished responsive surfaces.