← Back to the case study

For Technical & AI

System architecture

Entry points, shared services, durable state, and release boundaries.

Public reading guide · Source: docs/03-Architecture.md
A reviewed summary of the repository documentation and current implementation. Private operational details and phase-test records are omitted.

Entry and state

Next.js routes validate private workspace access. Web uploads go to private Supabase Storage through bounded capabilities; signed email webhooks create durable jobs. Supabase Postgres holds documents, results, conversations, approvals, jobs, outbox records, and QA reviews.

Interpretation and execution

Gemini interprets documents and email and supplies typed outputs. Deterministic application code validates schemas, scopes access, calculates dates, validates approval versions, and serializes ICS. The Calendar role's serialization does not require model reasoning.

Branches and gates

Email uses a LangGraph coordinator and its own bounded MCP interface. Document Q&A separately prepares a lazy index and retrieves page evidence. QA gates extraction/results and applicable email/calendar release, with bounded correction and durable quota pauses.

Explore the interactive architecture →