Reader stack
Next.js App Router, Tailwind 4, TypeScript, and Supabase SSR are in place.
Reader platform foundation
The Almanack of Half-Second Decisions
A field manual for freedom, leverage, and sukoon
The product surface is still intentionally narrow: a premium reading shell, structured chapter delivery, existing-reader magic-link access, and a backend boundary that keeps paid content out of bulk payloads.
Foundation status
Content delivery is the first real product boundary.
Content model
Chapters stay in Supabase as structured JSON blocks, served one chapter at a time.
Access rules
Introduction and Chapter 1 remain public. Paid chapters require an authenticated reader record.
Included now
- Branded App Router shell
- Supabase browser, server, and admin clients
- Chapter content delivery endpoint with navigation metadata
- Reader routes, magic-link login, and session restore for existing buyers
Delivery contract
Each chapter ships as structured data, never as a full-book dump.
Public
Introduction and Chapter 1 remain available without login for preview and SEO.
Paid
Chapters 2 through 44 require an authenticated reader with active or comp access tied to the Supabase auth user id.
Response shape
The API returns one chapter, adjacent navigation metadata, and progress restore without exposing the full book payload.
Next up
Razorpay checkout is now wired into the unlock flow. Existing readers still authenticate and resume by magic link.