architecture

Summary

How Pattaya is planned to be built, in four small diagrams and one overview, opened from the architecture chip in the bar. Nothing here is built yet.

Raw wireframes

• .context/designs/mobile/architecture/<overview|who-uses|how-it-works|backend|relies-on>.html — the screens
• .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 app is built, what the server does, what it relies on.
• The stack is the Phase 3 preview in FEAT-0003. It is not settled: T003 in tasks.md decides between it and the Firebase and UniWind scaffold every Expo app gets. Redraw these when it is.
• The server diagram exists because the journal is decrypted on the server for the weekly report, and every decryption is logged (journal-encryption).
• 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. Why each choice was made belongs in a decision page once T003 is done.

Related

• data-model · journal-encryption · household-as-billing-unit

Sources

• .context/features/0003-mvp-build.md, wiki/entities/data-model.md, wiki/concepts/journal-encryption.md