🗺️ Architecture diagram — Todo architecture and ERD #2

New issue

Open

opened 2026-09-28 07:55:32 +00:00 by SemianiakaVY · 0 comments

SemianiakaVY commented

2026-09-28 07:55:32 +00:00

Owner

Goal — draw the architecture of the Todo app and the ERD of its single table on My Diagrams (/diagrams).

Owner — Diagram Expert (w4c-diagram).

Deliverables

One saved diagram: Browser (/ task list) → Next.js route handlers (/api/todos, /api/todos/[id]) → SQLite file (data/todos.db), plus the CI workflow box.
An ERD of todos (id, title, done, createdAt) matching SPEC.md §4.
The e-commerce diagram shipped with the template (.w4c/diagrams/architecture.excalidraw.json) is superseded — redraw it for the Todo scope instead of leaving the storefront architecture in place.

Acceptance

The diagram reloads on /diagrams without loss; the ERD lists exactly the todos fields of SPEC.md §4 and nothing else; report the document name/ids.

Ref — docs/PLAN.md §3–§4, SPEC.md §3–§4, /diagrams.

**Goal** — draw the architecture of the Todo app and the ERD of its single table on My Diagrams (`/diagrams`). **Owner** — Diagram Expert (`w4c-diagram`). **Deliverables** - One saved diagram: Browser (`/` task list) → Next.js route handlers (`/api/todos`, `/api/todos/[id]`) → SQLite file (`data/todos.db`), plus the CI workflow box. - An ERD of `todos` (`id`, `title`, `done`, `createdAt`) matching `SPEC.md` §4. - The e-commerce diagram shipped with the template (`.w4c/diagrams/architecture.excalidraw.json`) is superseded — redraw it for the Todo scope instead of leaving the storefront architecture in place. **Acceptance** - The diagram reloads on `/diagrams` without loss; the ERD lists exactly the `todos` fields of `SPEC.md` §4 and nothing else; report the document name/ids. **Ref** — `docs/PLAN.md` §3–§4, `SPEC.md` §3–§4, `/diagrams`.