Work / AskCal / Wiki / Surfaces
architecture
Surfacedraftverified 2026-10-23
SURFACE.MOBILE.ARCHITECTURESummary
How AskCal is built, in four small diagrams and one overview, opened from the architecture chip in the bar.
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>.htmlis drawn from it by Archify
Why it is drawn this way
- One question per diagram: who uses it, how the app is built, the Cloud Function, what it relies on.
- 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 runarchify finalize architecture <name>.json <name>.html --quality showcaseinsidedesigns/architecture/. - The overview is architecture and cost only: the stack with versions and the monthly cost. Why each choice was made is in the product's own CLAUDE.md and scan-cost.
Related
Sources
- CLAUDE.md, README.md, package.json in every workspace, firebase.json, .context/wiki/entities/scan-cost.md