Architecture

app.abhyas.design owns all design source. app.abhyas.context owns documentation and consumes a verified compiled design artifact, never a source copy.

app.abhyas.storage (the book, LaTeX)
        │  "Sync from the book" opens migration PRs
        ▼
app.abhyas.database.dev ──release──▶ app.abhyas.database.prd
        │ migrations                         │ migrations
        ▼                                    ▼
  Supabase dev                         Supabase prd
        ▲                                    ▲
        │ supabase-js (browser)              │ supabase-js (browser)
abhyas.dev.nishko.co                  abhyas.nishko.co
        ▲                                    ▲
app.abhyas.frontend.dev ──release──▶ app.abhyas.frontend.prd

Rules

1. The site depends only on the database. The outline, lessons and questions all live in Supabase. The website never reads the book repository.
2. The book reaches the database as migrations. database.dev turns book changes into reviewed migration pull requests.
3. Build once, deploy the same files. A merge to a .dev repository makes one numbered release. The .prd repository deploys that exact release; it never builds anything.
4. No server. The website is a static export on GitHub Pages. All logic runs in the browser and talks to Supabase directly with a publishable key. Supabase sign-in plus row-level security protect the data.
5. dev first. Changes merge into the .dev repositories and go live on dev. prd is deployed by hand, database before frontend.

Pieces