Back to the shelf

069

Gati

The gait of every trending report the plant still does in Excel.

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

Every trending report at this plant gets built by hand. Someone opens Excel, copies numbers, builds charts cell by cell. That is how the quality review has always been fed.

Gati is the tool I am building to replace it. The name means motion, or gait. The gait of every trending report. The charts are drawn in D three, in the spirit of Giorgia Lupi's data drawing: not the Excel look, but something precise and worth looking at, while every feature the quality review needs stays intact.

I started in September twenty twenty-six, drawing every screen before writing a single line of code. Several decisions are still open. This is a live work in progress, and you are welcome to watch it move.

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

Gati
No. 069

Gati means motion, or gait. The name came from a line that would not leave me: the gait of every trending report the plant still does in Excel.

The plant I work with does its trending reports by hand. Every year, those reports feed the annual product quality review. The work is careful and painstaking. It all happens in spreadsheets.

Gati turns those trends into charts drawn in D3, in the spirit of Giorgia Lupi’s data drawing. The aim is the simplest stunning gait, not the Excel look. Every feature the quality review needs stays.

I started in September 2026, documentation first. The whole product was drawn screen by screen in Paper, a design tool, and reviewed end to end before a line of code was written. Several product decisions are still open. It is better than it was, but it is not complete.

A live, work-in-progress version is up. Built with Next.js, TypeScript, Prisma, and PostgreSQL.

The making

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

01 · The problem

Before it existed

What hurt

The plant builds every trending report by hand in Excel, then feeds it to the yearly quality review. Slow, careful work, and a drifting trend is easy to miss.

Who uses it

  • QA review team
  • QA recorders
  • QA approvers
  • Plant leadership
  • 64commits in three weeks
  • 11pull requests
  • 5annexures in the first house
  • 10roads ranked on the seeded campaign

02 · The flow

6 steps, in the order they happen

  1. 01 / 06

    Open the house

    You
    Opens a campaign
    It answers
    Ranks every road worst first, with its Cpk and the room it has left
    The house: ten roads with findings, ranked worst first, each with a drawn year
  2. 02 / 06

    Walk the worst road

    You
    Taps Walk the worst road
    It answers
    Draws each lot as a mark between painted limit lines, smeared by drift
    One road drawn with red marks drifting toward its limit line
  3. 03 / 06

    Read an annexure

    You
    Opens Annexure I
    It answers
    Lays every parameter as its own road, with the table one toggle away
    Annexure I with Assay, LOD and pH drawn as roads
  4. 04 / 06

    Check the findings

    You
    Opens Findings
    It answers
    Lists the roads that fail the Cpk gate, though no lot is out of specification
    Findings page reading 2 roads fail the gate
  5. 05 / 06

    Compose the pack

    You
    Opens Reports
    It answers
    Gathers five annexures into a printable pack, labelled draft until signed
    Compose the pack: five annexures each with Open and Sign
  6. 06 / 06

    Bring last year in

    You
    Downloads the CSV template
    It answers
    Takes a year of lots from a sheet; nothing lands until a receipt names it
    Import page offering a CSV template

03 · What was special

What it stands on

  1. A road, not a chart

    Specification is the lane, a limit is a solid line, open ground is broken. No chart library; every mark is drawn in D3.

  2. Drawn before coded

    Every screen was drawn in Paper and reviewed end to end before the first line of product code.

  3. The table never leaves

    The GMP table is always one toggle from the drawing, so the record stays plain.

A chart that shows the trend before it shows a number.

Making-Of

A trending report drawn as a road at night, not a chart in Excel.

The locked brief and the first commit, the same day

  1. The world before

    Every annual quality review at the plant was fed by trending reports built by hand in spreadsheets.

  2. One day

    3 September 2026. The brief: D3 as the language, in the spirit of Giorgia Lupi, with every feature of the review guide kept and the Excel look dropped.

  3. Because of that

    1. The metaphor settled the same day: a road at night, with the lane line as the one symbol (3 Sep).
    2. A first working house ranked roads worst first, with lots enterable with JavaScript off (7 Sep).
    3. Setup, signing and an audit trail for limit changes arrived (18 Sep).
    4. Paper’s full set of screens was built into the live product (19 Sep).
    5. Five doors cut the first screen down to one next step (22 Sep).
  4. Until finally

    A live, work-in-progress house runs on the seeded Bleomycin campaign. Nine design decisions are still open.

  5. Since then

    Open items remain: spreadsheet import, retained report files, account recovery and the other plant departments.

The evidence Process, hands, and artifacts

Process

  1. Brief

    D3 only; the table always one toggle away; no Excel look

  2. Metaphor

    A road at night; the painted lane line is the one symbol

  3. Proof

    Worst road first; red spent only where a limit is crossed

  4. Record

    Signed snapshots and audited limit changes

  5. Paper

    Draw the whole product, then build it

  6. Doors

    Guide the house to one next lane

Hands

Akshansh

  • The brief, the Lupi direction and the rulings on colour and motion
  • Review of every drawn screen before any code

Agents

  • Claude CodeDrew the screens in Paper and built much of the product
  • CursorScaffolded the data model and the D3 marks