Back to the shelf

068

Ritu

A stability sample system that tells you which chamber, when it was pulled, and how many remain.

Building · Started September 2026 · System · Notion-First

That's the whole thing.

The site's sound is off. The narration still plays.

This reading didn't load. The transcript is below.

Read the transcript

Ritu means season in Hindi. I named it in September twenty twenty-six, for stability samples at a pharma company.

In a stability study, drug samples sit in controlled chambers for a long time and are pulled on a schedule for testing. Ritu holds the answers: which sample sits where, when it was pulled, which tests ran, how many remain.

I picture it as a house of controlled seasons. Each real chamber is a room, and nothing is invented. Open it and the headline tells you the day’s work: two pulls need you today.

The spec came first. Now the house is being built. Chambers, pulls, custody, and the remaining count already work end to end, on practice data. Next, quality control confirms the chamber lists, and then the first real study.

Narrated in my own cloned voice, generated with ElevenLabs v4.

Ritu means season in Hindi. I chose the name in September 2026.

It’s a system for stability samples at a pharma company. In a stability study, drug samples sit in controlled chambers for a long time, pulled out on a schedule for testing. Ritu holds the answers: which sample is in which chamber, when it was pulled, which tests ran, and how many remain. Sample custody and the pull calendar, in one place.

I imagined it as a house of controlled seasons. Each real chamber is a room. The house is drawn only from rooms that actually exist, for each unit. Nothing invented, nothing added. The season in the art is a quiet setting; it never implies chamber conditions. The headline tells you the day’s work: “Two pulls need you today.”

The north star I kept returning to was the cool shade of a courtyard at the hour of a pull, every sample exactly where you left it.

Ritu builds on the QR inventory foundation from a sibling app I made, but carries its own identity. The first proof it has to pass: one chamber type, one product family, where parking a sample, pulling it, and the remaining count are all true.

I started in September 2026, documentation first. The spec came first; the house is now being built – chambers, pulls, custody and the remaining count already work end to end.

The making

  • Next.js
  • TypeScript
  • Tailwind CSS
  • Prisma
  • PostgreSQL
  • Vitest

01 · The problem

Before it existed

What hurt

Stability samples sit in controlled chambers for months. Which vial is where, when its pull is due, and how many remain is tracked by hand.

Who uses it

  • QC analysts
  • QC coordinators
  • QA reviewers
  • Unit administrators
  • 27commits in thirteen days
  • 12browser test specs
  • 2units, each with its own chambers

02 · The flow

8 steps, in the order they happen

  1. 01 / 08

    Open the house

    You
    Opens the app
    It answers
    Draws the unit’s real chambers as rooms and says what needs doing today
    The house: six chamber doors at dusk, with a note that two pulls need attention today
  2. 02 / 08

    Walk to a room

    You
    Opens the chambers
    It answers
    Lists each room from the register, with its configured condition and vials resting
    Six rooms in Unit II, each with its configured condition and vial count
  3. 03 / 08

    Find the bin

    You
    Opens one chamber
    It answers
    Shows racks and bins, and lights the bin whose pull is due
    A chamber with its racks; one bin lit as due, one hatched as on hold
  4. 04 / 08

    Receive a transfer note

    You
    Starts a receipt for a note
    It answers
    Counts what arrived against what was stated before anything is parked
    One transfer note waiting to be counted, with stated and counted columns
  5. 05 / 08

    Pull on schedule

    You
    Scans the door, the bin and each vial
    It answers
    Steps through door, bin, vials, seal and hand-over; a hold blocks the seal
    A pull in five steps with a vial counter and a seal panel; the signer is blurred
  6. 06 / 08

    Seal the record

    You
    Signs with a password
    It answers
    Places a seal that names who, what and when, and releases the vials for hand-over
  7. 07 / 08

    Take the round on a phone

    You
    Opens today’s round
    It answers
    Lists the day’s pulls in order, overdue first, with the bin for each
    Phone view: four pulls in today’s round
  8. 08 / 08

    Read the record

    You
    Opens the custody record
    It answers
    Shows every movement; nothing is removed, and a correction is a new event

03 · What was special

What it stands on

  1. Rooms from the register

    Each unit’s house is generated from its own chamber register. No room is ever drawn that is not there.

  2. Nothing is erased

    Every movement stays on the record. A correction is a new entry, and one number is checked against the movements.

  3. Season is a setting, not data

    The art season is labelled as art, never as chamber conditions. Conditions shown are configured, not live.

A house drawn only from rooms that really exist.

Making-Of

A courtyard at the hour of a pull, with every sample where you left it.

The Notion build hub; the name was chosen on 19 September

  1. The world before

    Stability sample management in QC, across both units, ran entirely by hand.

  2. One day

    19 September 2026. The name Ritu, the palette, the type and the mark were approved in one review, and the first working slice was built the same day.

  3. Because of that

    1. The structure was decided: each unit’s house is drawn from its own chamber register (19 Sep).
    2. Receive, park, pull, seal and hand over ran end to end, with a phone companion (19 Sep).
    3. Exceptions got sealed decisions, labels printed from the browser, and setup changes waited for QA (19 Sep).
    4. A production build with per-unit bootstrap went in; the living court and its motion followed (20 to 22 Sep).
    5. Protocols, chambers and scan cards could be set up by click (30 Sep).
    6. A setup workbench and one vial ledger made every screen agree on the same number (1 Oct).
  4. Until finally

    A working build runs on a synthetic fixture. Chamber lists, conditions, and pull windows still wait for QC to confirm them.

  5. Since then

    Next is QC sign-off of the masters, then the first real study.

The evidence Process, hands, and artifacts

Process

  1. Direction

    Palette, type and mark approved; the house is generated from each unit’s chambers

  2. First slice

    Receive, park, pull, seal and hand over, with a phone companion

  3. Labels

    Print from the browser, with a record of every print

  4. Production

    Standalone build and per-unit bootstrap

  5. Court

    A living court and motion that answers the work

  6. Setup

    Protocols, chambers and scan cards by click

  7. Ledger

    One vial ledger that every screen reads

Hands

Akshansh

  • The name, the north star and every ruling on palette, type and mark
  • The structure: one house per unit, drawn from real rooms

Agents

  • Claude CodeCo-authored most of the commits
  • CursorCo-authored commits in the build