architecture

Summary

How Seedha Ghar is built, in four small diagrams and one overview, opened from the architecture chip in the bar. The same screens are in the mobile and the web set.

Raw wireframes

• .context/designs/mobile/architecture/<overview|who-uses|how-it-works|backend|relies-on>.html — the screens, phone set
• .context/designs/web/architecture/<same names>.html — the screens, 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 web app is built today, the planned backend, what it relies on.
• Today the web app runs on seed data in memory and the mobile app is a scaffold. The backend and the services are planned in architecture-overview and not locked (tech-stack is a draft); the diagrams say "planned" where nothing is built.
• In the phone 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, taken from the cost ceilings in non-functional.

Related

• architecture-overview · non-functional · tech-stack · wallet

Sources

• apps/web/package.json, apps/mobile/package.json, wiki/concepts/architecture-overview.md, wiki/concepts/non-functional.md