engineering docs

Internal platform handbook

Ship every data contract with confidence.

A practical guide for building across the Aori monorepo: one API boundary, four physical databases, and a clear CRUD path for every client.

request-flow.ts

01client apiFetch()

02api validate + authenticate

03service ownership check

04database scoped write

05success ✓ contract shipped

04physical databases
01API boundary
100%server-side ownership
safe integrations

System map

Find the domain that owns your data.

Resource pages are grouped by database so the ownership model stays visible while you build.

Build path

From first request to production.

Short, opinionated references for the day-to-day engineering loop.

Non-negotiable

Validate at the API. Scope at the database.

Never trust a client-provided organization ID, never write directly from UI, and never hide a cross-database assumption.

Read security rules