Back to the shelf

067

Culture Handling

A standalone app to manage living culture stock: master cultures, working cultures, and every passage between them.

Spec Ready · 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

The logbooks are paper. Several of them track master cultures, working cultures, and every passage in between. No existing system covers living cultures. That gap started this.

I am planning a standalone app for a pharma microbiology lab. It will register the organism, log each passage, barcode the working stock, and keep the remaining count true. Before any code, I will walk the procedure on the lab floor. Floor truth first, then code.

The first proof is deliberately small: one organism, master to working, one passage, remaining count staying true. If that holds, the model holds. Spec ready since September twenty twenty-six. The build has not started. The name is still open. Follow along.

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

The logbooks are paper. In a pharma microbiology lab, culture maintenance lives across several of them. No existing system covers living cultures: the master stock, the working cultures prepared from it, the passage records between them, the count of what remains. I’m planning an app to close that gap.

Before any code, I’ll walk the procedure on the lab floor. That’s the rule I set for myself on this build: floor truth first, then code. The actual procedure matters more than what a spec says it should be. The scope is deliberately narrow, because narrow is the only way to get it right.

The app will register the organism, record the preparation of a working culture from master stock, log each passage, barcode the working stock, and keep the remaining count true. Other systems will only need to know which lot was used.

The first proof is small by design: one organism, master to working, one passage, remaining count stays true. If that holds, the model holds.

The spec is ready as of September 2026. The stack is settled: Next.js, TypeScript, Tailwind, Prisma, PostgreSQL, Vitest. The build hasn’t started. There’s no live version and no repo yet. The name is still open. Follow along if the build interests you.

The making

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

01 · The problem

Before it existed

What hurt

A microbiology lab keeps living culture stock in several paper logbooks. No system covers master stock, working cultures, each passage between them, or what remains.

Who uses it

  • Microbiology analysts
  • QC reviewers
  • QA

02 · The flow

5 steps, in the order they happen

  1. 01 / 05

    Register the organism

    You
    Adds the organism and its master stock
    It answers
    Intended: creates the record that owns the stock
  2. 02 / 05

    Prepare a working culture

    You
    Records a working culture made from the master
    It answers
    Intended: links it to its master and takes from the count
  3. 03 / 05

    Log a passage

    You
    Records each passage
    It answers
    Intended: chains the passage to its source
  4. 04 / 05

    Barcode the working stock

    You
    Prints a label for the working culture
    It answers
    Intended: identifies each tube from then on
  5. 05 / 05

    Read what remains

    You
    Opens the stock overview
    It answers
    Intended: shows a remaining count that stays true

03 · What was special

What it stands on

  1. Floor truth first

    The procedure is walked on the lab floor before any code. The real steps outrank the spec.

  2. A deliberate first proof

    One organism, master to working, one passage, remaining count true. If that holds, the model holds.

  3. Owns the stock

    Other systems only learn which lot was used. They never hold the culture.

The count of what is left stays true.

Making-Of

Living culture stock still lives in paper logbooks. The first proof is one organism and a count that stays true.

A Notion brainstorm and spec, written the same week

  1. The world before

    Culture maintenance ran across several paper logbooks. Existing systems covered prepared media and samples, not living cultures.

  2. One day

    2 September 2026. A brainstorm decided it is a separate app: living stock as master, working and passage, with one plant’s lab first.

  3. Because of that

    1. The scope was kept narrow on purpose, with a hard list of what it is not (3 September).
    2. The stack was settled: Next.js, TypeScript, Tailwind CSS, Prisma, PostgreSQL and Vitest (3 September).
    3. A rule was set: walk the procedure on the lab floor before any code.
    4. The first proof was fixed small: one organism, master to working to one passage, remaining count true.
  4. Until finally

    Not yet. The spec has been ready since 3 September 2026. There is no repository and no live version.

  5. Since then

    Open: which organism for the first proof, the walk of the procedure on the floor, and the name.

The evidence Process, hands, and artifacts

Process

  1. Brainstorm

    A separate app for living stock; one plant’s lab first

  2. Spec

    Register, prepare, passage, remaining true, barcode

  3. Scope

    Hard no list; other systems consume later, never hold the stock

  4. Stack

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

  5. First proof

    One organism, master to working, one passage

Hands

Akshansh

  • The scope, the hard no list and the floor-first rule

Agents

  • Claude CodeDrafted the hub, spec and coding guide in Notion