architecture

Summary

How Scrvio is built, in four small diagrams and one overview, opened from the architecture chip in the bar.

Raw wireframes

• .context/designs/web/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 website is built, what the server does, what it relies on.
• The website uploads to S3 itself, with a URL the server signs; the server never carries the video. That is why the bucket can be the team's own.
• The server's host and the production Postgres are not named in the repo, so the diagrams and the cost leave them out.
• 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 tiers and their rules are in CLAUDE.md.

Related

• recorder · storage · public-link

Sources

• CLAUDE.md, package.json files, apps/server/src/api/03-recording/recording-upload.service.ts, .context/ops/release.yml