architecture

Summary

How DwarSeva is built, in four small diagrams and one overview, opened from the architecture chip in the bar. The mobile and the web set show the same pages.

Raw wireframes

• .context/designs/mobile/architecture/<overview|who-uses|how-it-works|backend|relies-on>.html — the screens in the mobile set
• .context/designs/web/architecture/<overview|who-uses|how-it-works|backend|relies-on>.html — the same screens in the web set
• .context/designs/architecture/<name>.json — each diagram's source; <name>.html is drawn from it by Archify

Why it is drawn this way

• One question per diagram: who uses it, how the mobile app is built, the server, what it relies on.
• In the mobile set these screens are not in the phone frame: a 390px frame is too narrow to read a diagram, so they fill the window under the bar.
• The diagrams are generated assets: edit the .json, then run archify finalize architecture <name>.json <name>.html --quality showcase inside designs/architecture/.
• The overview is architecture and cost only: the stack with versions and the monthly cost. The EC2 size and the Postgres host are not in the repo, so the cost leaves them open.

Related

• splash · admin-dashboard

Sources

• CLAUDE.md, .context/ops/setup.md, .github/workflows/cd.yml, package.json in every workspace