Architecture
Developer architecture
Section titled “Developer architecture”Implementation guides for engineers: wire formats, sync protocols, deployment constraints, and diagrams. Product decisions (why, v1 scope, UX principles) stay under Planning.
Topics
Section titled “Topics”| Document | What it covers |
|---|---|
| Database schema | Implemented tables, foreign keys, and Mermaid ER diagrams — including study plan templates, tracks, electives, and mentorship curriculum |
| Note CRDT sync | Automerge note bodies, GraphQL pull/push, server merge, offline client, deployment risks |
| Rich text format | JSON envelope for note bodies and study plan instructions; TipTap schema, markdown interchange |
Related planning docs
Section titled “Related planning docs”| Document | Use when |
|---|---|
| Study plans | Template resolution, step lifecycle, admin AI |
| Tracks | Hourglass curriculum, modules, electives, mentor assignment |
When adding a new implementation doc, link it here and from the relevant Planning page so product and engineering stay separated.