01 / Featured engineering story
SeatLedger Deployed demo
One seat left.
Two people booking.
I built a reservation system to explore what happens when requests compete, holds expire, and clients retry—with a deployed demo and reproducible engineering evidence.
Synthetic shared accounts · Free backend may take a minute or more to wake · No personal information
Actual product capture - 01 / Protect capacity
Serialize reservation changes at the event.
- 02 / Handle retries
Persist idempotent outcomes with lifecycle changes.
- 03 / Explain the numbers
Build replayable analytics apart from live inventory.
Verification and demo limitations
18 October 2026 · Deployed portfolio demo · CI: 265 backend, 56 analytics and 28 browser tests passed, zero failures/errors/skips. Synthetic evidence, not production load or real-user validation.
Free backend sleeps; email delivery is unavailable. Real-user launch still needs email and completion of privacy/recovery work. Shared demo accounts only; no personal information.
Inspect verification scope

