Back to the shelf

054

Darpan

One governed mirror of the live organisation, so six applications draw from the same truth, not six drifting ones.

Building · Started August 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

Darpan means mirror in Hindi. I started it in August twenty twenty-six, vibe-coded with AI. Six applications at a pharma company each kept its own copy of who works here. Six drifting truths: wrong names, mismatched departments, orphaned accounts, duplicated logins. The data just drifted.

Darpan is one governed mirror of the live organisation. It takes in employment data, validates and reconciles it, quarantines anything ambiguous instead of guessing, and gives each application only the fields it needs. It's not the HR authority. It's just the mirror.

The interface is called the Quiet Room: cool porcelain, one window, the real sun. A version is running, and it is still being built. Follow along if that interests you.

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

Darpan
No. 054

Darpan means mirror. Six applications were keeping their own copy of who works here. Six lists that started as one truth and drifted: wrong names in one system, mismatched departments in another, orphaned accounts, duplicated logins.

Darpan is the mirror. One governed copy of the live organisation: people, departments, designations, units, employment status. It takes in employment data through a versioned feed, validates and reconciles it, and quarantines anything ambiguous instead of guessing. You can see what arrived and what changed. Each application draws only the fields it needs. Apps reference stable employee codes, not names, so a name change never breaks anything downstream.

Darpan isn’t the HR authority. That record lives elsewhere. For now, it also provides a temporary sign-in bridge until the permanent sign-in is ready. That part will step back when it’s no longer needed.

The design language is called The Quiet Room: cool porcelain, one window, the real sun coming through. A torch follows your pointer across the floor.

I started building this in August 2026, vibe-coded with AI. A version is running. It’s still being built.

The making

  • TypeScript
  • Next.js
  • PostgreSQL
  • Prisma

01 · The problem

Before it existed

What hurt

Six applications each kept their own copy of who works at the plant. The copies drifted: wrong names, mismatched departments, orphaned accounts, duplicated logins.

Who uses it

  • Platform administrator
  • Application owners
  • People-data stewards
  • 87commits
  • 43commits on day one
  • 6applications drawing from it
  • 12fields the feed may carry

02 · The flow

7 steps, in the order they happen

  1. 01 / 07

    Meet the mirror

    You
    Opens Darpan
    It answers
    Shows a quiet room lit by the real sun over the plant’s town
    A pale porcelain page with the Darpan mark, a short statement and a sign-in card
  2. 02 / 07

    Sign in

    You
    Types an employee code and password
    It answers
    Locks the account after eight wrong tries for fifteen minutes
    A sign-in card with employee code and password fields
  3. 03 / 07

    Choose your own password

    You
    Replaces the temporary one
    It answers
    Accepts twelve characters or more; the administrator never learns it
    A card titled Choose your password with two password fields
  4. 04 / 07

    Read the directory

    You
    Searches or filters by unit and department
    It answers
    Lists every person with code, department, designation and status
    A table of twelve demonstration people with department, designation and unit
  5. 05 / 07

    See what Spine sent

    You
    Opens the feed
    It answers
    Holds each batch for a decision before anything permanent happens
    The feed page reading No version yet, with a button to read the roster
  6. 06 / 07

    Decide who opens what

    You
    Names a department and an application
    It answers
    Writes a rule; everyone in the department, now and later, may enter
    The access page with waiting requests, rules and exceptions
  7. 07 / 07

    Add a person by hand

    You
    Issues an employee code
    It answers
    Mints a permanent code that is never changed or reused
    An Add a person form with employee code, name, unit and department

03 · What was special

What it stands on

  1. Absence never deactivates

    A person missing from a feed stays. Leaving arrives as an explicit tombstone, and nobody is deleted.

  2. Quarantine, not guessing

    A row with an unknown department or a forbidden field is held back whole, with the reason.

  3. Light as behaviour

    Shadows follow the real sun over Panchkula. The metaphor lives in how the room behaves, not in a graphic.

A mirror reflects; it never originates.

Making-Of

Six lists began as one truth. Darpan makes them one again.

The first Notion brief and the first commit, the same day

  1. The world before

    Each plant application held its own copy of who works here. Over time the copies drifted apart, with no one place to say which was right.

  2. One day

    2 August 2026. The first day carried the visual gallery, an inventory of people data across every application, the identity architecture and the Part 11 step-up contract: 43 commits.

  3. Because of that

    1. Access management and a first administrator let the record be opened safely (2 August).
    2. The architecture was corrected: Darpan is a Spine-fed repository, not the people authority (3 August).
    3. The Quiet Room identity went in: a real mark, a type system, light that follows the sun (18 August).
    4. A Spine pull adapter brought the roster into the governed record (24 August).
    5. Another application began reading Darpan as a consumer (8 October).
  4. Until finally

    A version of Darpan is running and still being built.

  5. Since then

    Its sign-in bridge is temporary by design; it steps back when the permanent sign-in is ready.

The evidence Process, hands, and artifacts

Process

  1. Origin

    Inventory first: who is a person in each application

  2. Identity

    The employee code is immutable and is the sign-in subject

  3. Correction

    Spine holds employment truth; Darpan mirrors it

  4. Access

    Signing in is not access to every application

  5. Identity

    The Quiet Room: light as behaviour

  6. Feed

    The roster enters through a governed pull

  7. Consumers

    A read-only consumer API for other applications

Hands

Akshansh

  • Concept: a governed mirror, not a second HR system
  • The rule that absence never deactivates
  • Design direction for the Quiet Room

Agents

  • Claude CodePrimary builder and reviewer
  • CursorCo-authored commits