Back to the shelf

070

Material threshold

A pharma plant kiosk that logs every material crossing a pass box, incubator, or chamber.

Spec Ready · Started September 2026 · PWA · 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

In a pharma plant, material moves all day through pass boxes, incubators, and chambers. Every one of those movements still ends up in a handwritten logbook.

I built Dwaar to log people at entry doors for the pharma company I work with. This is its sibling, built for material at the same thresholds.

Tap the item, sign, done. Direction comes from the door's state, never a manually picked mode. The ledger is append-only. Three to five seconds.

The specification was written in September twenty twenty-six. No code yet. The first proof is one pass box, a short kit list, and a live board of what is inside right now.

The threshold still witnesses. The thing is not a person.

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

Every material movement through a pharma plant still ends in a handwritten logbook. Pass boxes, incubators, chambers: all of it, on paper. That is the gap.

The incubator vendor would not expose open and close events. A dedicated kiosk was the only path.

Material Threshold is the working name. It is a kiosk web app for plant operations, quality assurance, and quality control teams at the pharma company I work with. Tap or scan the item, sign, done. Three to five seconds. Direction comes from the door’s state, never a mode you pick manually. The ledger is append-only. One shared device covers an area. Each door has its own local catalog.

This is the sibling of Dwaar, my kiosk that logs people at entry doors. Dwaar closed the people gap. This closes the material gap at the same thresholds. The threshold still witnesses, but the thing is not a person.

The first proof is deliberately small: one pass box, a short kit list, and a live board of what is inside the box right now. This is enough to test whether the loop holds under real plant conditions before it spreads.

The specification was written in September 2026. No code yet.

The making

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

01 · The problem

Before it existed

What hurt

Material moves all day through pass boxes, incubators, and chambers, and every movement still ends in a handwritten logbook. The incubator vendor would not expose its open and close events.

Who uses it

  • Plant operations
  • QA
  • QC

02 · The flow

5 steps, in the order they happen

  1. 01 / 05

    Pick the door

    You
    Selects the pass box on the shared tablet
    It answers
    Intended: scopes the kiosk to that door and its local catalog
  2. 02 / 05

    Tap or scan the item

    You
    Taps the item or scans it
    It answers
    Intended: finds it in that door’s short kit list
  3. 03 / 05

    Sign

    You
    Signs once on the glass
    It answers
    Intended: stamps the time and appends it to the ledger
  4. 04 / 05

    Direction follows

    You
    Does nothing more
    It answers
    Intended: works out in or out from the door’s state, never a mode
  5. 05 / 05

    Read what is inside

    You
    Glances at the live board
    It answers
    Intended: lists what is in the box right now

03 · What was special

What it stands on

  1. Direction is derived

    Never a mode to pick. The door’s state says in or out.

  2. Append-only ledger

    A correction is a new entry. Nothing is edited or deleted.

  3. Local to the door

    Each door keeps its own catalog. One shared device covers an area.

The threshold still witnesses. The thing is not a person.

Making-Of

Dwaar logs people at the door. This is its sibling, for the material that crosses the same thresholds.

A Notion brainstorm and spec, written the same week

  1. The world before

    Every material movement through pass boxes, incubators, and chambers ended up in a handwritten logbook.

  2. One day

    2 September 2026. A brainstorm named it a Dwaar sibling, not Dwaar: the same gesture with a different roster and a local catalog for each door.

  3. Because of that

    1. The vendor’s refusal to expose open and close events made a dedicated kiosk the only path.
    2. Three rules were set: direction is derived, the ledger is append-only, each door’s catalog is local.
    3. The first proof was fixed small: one pass box, a short kit list and a live what’s-inside board (3 September).
    4. The stack was settled: Next.js, TypeScript, Tailwind CSS, Prisma, PostgreSQL, Vitest and a PWA.
  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: pick the first pass box and list the things that actually cross it.

The evidence Process, hands, and artifacts

Process

  1. Brainstorm

    A Dwaar sibling for material, with a local catalog per door

  2. Spec

    Tap or scan, sign, append-only, three to five seconds

  3. Rules

    Direction derived, ledger append-only, catalog local to the door

  4. Stack

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

  5. First proof

    One pass box, a short kit list, a live board

Hands

Akshansh

  • The sibling idea, the three rules and the first-proof scope

Agents

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