Stack Demo App
A local-only architecture spike: a simple ticket board using App Router, Server Actions, and SQLite persistence.
Captured locally
Ticket board screenshot from the spike app
Why this exists
A minimal stack reference turned into a working board
This experiment was built as a small proof of structure: keep routing in the App Router, push domain logic into a feature folder, and use a file-backed SQLite database so the demo survives server restarts.
It is intentionally local-only. The point is to show the architecture and interaction pattern, not to treat a tiny spike like a hosted product.
What it demonstrates
1. Create a ticket with a validated Server Action.
2. Persist it into a local SQLite file.
3. Read grouped board data through a query and service layer.
4. Move cards between columns without adding deployment complexity.
What I learned
A small demo gets more credible once it persists real state. Even a lightweight SQLite file changes the exercise from static UI to something closer to an application slice.
Keeping the scope narrow also matters. This is more useful in the portfolio as a concise architecture example than it would be as another half-finished hosted app.