Knowledge Base
We do not delete history because something failed
Failed, deprecated and superseded work stays documented, so anyone can understand what happened and why.
Internal documentation
The full Knowledge Base lives with the platform source. This page describes how it works.
The core rule
Every meaningful change records ten things
01
What we did
02
Why we did it
03
Where it lives
04
Commands or configuration used
05
Expected result
06
Actual result
07
How to verify it
08
How to recover or reverse it
09
Current status
10
What replaces it if superseded
Chapters
Architecture
The canonical ownership chain, security model and business boundaries.
GitHub & Codespaces
The canonical repository and the development environment.
Supabase
The canonical database project, migrations and recovery rules.
Vercel
Hosting, environments and deployment records.
UI & design system
Design tokens, components, page map and reuse decisions.
Integrations
Every connected system, with verification and failure modes.
Deprecated work
Failed, deprecated and superseded work, kept rather than deleted.