← HomeLayerItemComponentRoleNote
1Websites and web apps · items 1.1–1.4
Layer 1, web: sites and web apps| Item | Component | Role | Note |
|---|
| 1.1 | TypeScript | Language | One typed language from the browser to the edge. |
| 1.2 | Svelte | Interface | Interactive UI with a small runtime. |
| 1.3 | Astro | Sites | Static-first pages that load fast. |
| 1.4 | Tailwind CSS | Styling | A constrained, shared design vocabulary. |
2Mobilephones and tablets · items 2.1–2.3
Layer 2, mobile: phones and tablets| Item | Component | Role | Note |
|---|
| 2.1 | Swift | Language | Native code on Apple platforms. |
| 2.2 | SwiftUI | Interface | Declarative iPhone and iPad interfaces. |
| 2.3 | Cross-platform apps | Reach | One codebase where native is not required. |
3Cloud and datahosting, storage, analysis · items 3.1–3.4
Layer 3, cloud and data: hosting, storage, analysis| Item | Component | Role | Note |
|---|
| 3.1 | Cloudflare | Edge | Hosting, functions and DNS close to users. |
| 3.2 | Supabase | Backend | Auth, storage and Postgres, managed. |
| 3.3 | PostgreSQL | Database | The relational core. |
| 3.4 | BigQuery | Warehouse | Analytics over large event data. |
4Product practicehow we decide and ship · items 4.1–4.5
Layer 4, product practice: how we decide and ship| Item | Component | Role | Note |
|---|
| 4.1 | PostHog analytics | Measure | Decisions from behaviour, not guesses. |
| 4.2 | Agent orchestration | Build | Many agents in parallel, directed by one engineer. |
| 4.3 | Agent review and tests | Check | Agents review each other’s work; tests and checks gate every change. |
| 4.4 | Engineer approval | Decide | A person approves everything that ships. |
| 4.5 | Continuous deployment | Ship | Small changes, released as soon as they pass. |
Fig. 1 — The stack, exploded: four layers, sixteen parts.
The process behind layer 4, step by step →