Ashish Narayan

The operating system for a preventive wellness centre

Documents before code

Where wellness begins.

  1. Cover
    01Cover — Nirmalkaya, read as a systems problem: where the correctness lives.Full size ↗
  2. What this is
    02What this is — Scope, role, and the three rules the system enforces instead of asking staff to remember.Full size ↗
  3. The ontology is the schema
    03The ontology is the schema — Six entities defined in a July architecture document; five of them became Prisma models, and one became an enum.Full size ↗
  4. The Understanding gate
    04The Understanding gate — A patient-journey stage written in July becomes a server-side refusal in August.Full size ↗
  5. Three paths, one function
    05Three paths, one function — The reliability architecture that came out of the 14 August incident.Full size ↗
  6. The sweep is the load-bearing half
    06The sweep is the load-bearing half — The same shape repeats three times: a fast direct path, and a periodic sweep that catches what it missed.Full size ↗
  7. One chokepoint
    07One chokepoint — Middleware protects pages; server actions are POST endpoints that never pass through it.Full size ↗
  8. Stated limits
    08Stated limits — What this study could not verify, and what it deliberately did not look at.Full size ↗

Brand, product, engineering and operational documentation by me, with an AI collaborator writing most of the code under constraints I set. Written from the project's own build log and decision log. No metrics, testimonials or business results are claimed, because none are documented.

Back to the written studyAll case studiesSee it live ↗

B-SIDEOff the record
Documents before code — the document — Ashish Narayan