Back to the shelf

040

Pramaan

A pharmaceutical serialization and product-proof system that validates codes and keeps the evidence.

Building · Started May 2026 · System · Vibe-Coded

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

Pramaan means proof. Every medicine pack that leaves a production line carries a code: a G S one DataMatrix, or a QR code. That code is supposed to prove the pack is genuine. But proof only works if someone is checking.

Pramaan checks. It reads the barcode files the team's machines produce, in all their messy formats, and verifies each code against signed market rules as the line runs. Replayable evidence, reports, an audit history. A mobile-first web app.

I started this in May twenty twenty-six, vibe-coded with AI, for the pharma company I work with. It is in the team's hands for testing. In the next stage, anyone could one day verify a pack is genuine. That is what proof means.

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

Pramaan
No. 040

Pramaan means proof. The word sits at the center of everything this system does.

Every medicine pack carries a code: a GS1 DataMatrix, a GS1 QR code, or an India Digital Link code printed into the label. Those codes are meant to prove the pack is genuine. But proof only works if someone is checking. Pramaan does the checking: it validates codes against signed market profiles on the production line, and keeps replayable evidence, reports, and a full audit history for every batch.

The files the team’s machines and conversion steps actually produce come in all shapes and formats. Pramaan reads them as they are. Each batch gets a room of its own.

It is a mobile-first web app with a controlled serial repository. The approved expansion takes this further: serial custody and public authenticity checks, so anyone could one day verify that a pack is genuine. That is what the name means.

I started building Pramaan in May 2026 for the pharma company I work with, vibe-coded with AI. It is with the team now, in testing. Still building.

The making

  • Fastify
  • TypeScript
  • PostgreSQL
  • PWA
  • GS1 DataMatrix
  • Ed25519

01 · The problem

Before it existed

What hurt

A medicine pack’s code is meant to prove it is genuine, but each market has its own rules. Nobody on the line could check them or show the check later.

Who uses it

  • Line operators
  • QA reviewers
  • Serialization IT
  • Patients and partners
  • 126commits in four months
  • 7signed market profiles
  • 17modules in the API

02 · The flow

5 steps, in the order they happen

  1. 01 / 05

    Enter the office

    You
    Opens the app and taps Enter
    It answers
    Greets with the Office of Proof and asks for a sign-in
    Pramaan landing card with the mark and an Enter the office button
  2. 02 / 05

    Check a pack

    You
    Picks a market, pastes the code, taps Check
    It answers
    Recomputes on the server: green when cleared, red naming the failing rule
    Three phone screens: the empty chamber, a green Cleared verdict and a red Not cleared verdict
  3. 03 / 05

    Open the rooms

    You
    Opens the office menu
    It answers
    Lists the record, batches, registry, serial dossier and investigations
    Phone screens: the Office of Proof menu and an empty Batches room
  4. 04 / 05

    Let anyone check a pack

    You
    A stranger opens the public page
    It answers
    Takes a camera scan or pack details, with no account and no personal data
    Public page asking Is your pack genuine, with a camera scan panel
  5. 05 / 05

    Read the certificate

    You
    Reads the result
    It answers
    Answers genuine, unknown, suspicious, recalled or expired, with the signatory
    Phone screens: the public check page and a certificate for a code not established

03 · What was special

What it stands on

  1. Rules that are signed

    Each market’s rules are a signed profile. The server recomputes every check, so the phone cannot overrule it.

  2. A second parser as a gate

    An independent reference parser runs in CI against the profiles, so one reading of a code cannot quietly drift.

  3. Minimum disclosure

    The public certificate says whether a pack is genuine, and nothing about who handled it.

Every verdict is kept as evidence that can be replayed.

Making-Of

A pack code proves itself and keeps the proof.

The first commit, as the GreenTick line-side verifier

  1. The world before

    Export markets ask for GS1 codes with country-specific rules. A pass or fail on the line and an audit trail behind it did not exist.

  2. One day

    6 May 2026. The first commit landed a backend for a line-side verifier then called GreenTick.

  3. Because of that

    1. The web app, reports and docs portal took shape around a booth metaphor (7–10 May).
    2. Seven signed market profiles were written, each with its own test codes.
    3. The product was renamed Pramaan, the Office of Proof, and a controlled serial repository was planned (July).
    4. A public certificate page let anyone check a pack without an account (July).
    5. Intake learned to read the files machines actually produce, and each batch became a room (24 Aug).
  4. Until finally

    Pramaan is with the team for testing.

  5. Since then

    The approved expansion – serial custody and public checks at scale – is still to come.

The evidence Process, hands, and artifacts

Process

  1. Origin

    A line-side verifier: server-side PASS or FAIL with evidence

  2. Docs

    A built-in documentation portal that prints cleanly

  3. Rename

    GreenTick becomes Pramaan, with compatibility kept

  4. Public

    A public certificate for anyone with a pack

  5. Identity

    One mark, one steel, six colour meanings

  6. Intake

    Read each file as the machine wrote it

  7. Audit

    A batch you can open; green only when earned

Hands

Akshansh

  • The product intent and the trust model
  • Identity law, voice and every verdict wording
  • Review of what the agents built

Agents

  • Claude CodePrimary builder across the platform
  • CursorExecuted written briefs
  • AmpOperational QA tasks
  • Warp OzAgent runs on tasks and fixes