Back to the shelf

053

Setu

Setu means bridge. It doesn't carry data; it decides who may cross.

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

The name means bridge. That is not an accident. I work on a family of internal applications at a pharma company. They do not talk to each other, at least not without someone deciding who may connect and what is allowed.

Setu decides that. It authorises, issues credentials, and audits each app-to-app bridge. Data still travels directly. Setu never carries it. It just holds the keys.

I picture it as a brick board. Put two bricks together, tick a few boxes, and a governed connection exists. A serious machine that feels like play.

I started in August twenty twenty-six, documentation first. The design is drawn, screen by screen. It is live, with every bridge still off, and the code is catching up. You are early.

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

Setu
No. 053

Setu means bridge. It doesn’t carry things. Across a pharma company’s family of internal applications, Setu decides who may bridge at all.

Think of it as the switchboard. When two applications need to connect, Setu authorises the connection, issues credentials, and keeps watch. The data always travels app to app. Setu never carries it. Its job is governance, not transit.

The metaphor for how it looks is bricks on a shared baseplate. Each application is a brick. Put two bricks together on the board, tick a few boxes, and a governed connection exists. A serious, regulated machine that feels like play.

The board, the handshake, the register, the credential issuer, and the health observation layer all exist. It’s live, and the bridges switch on one at a time – the first, from Darpan to Gurukul, opened in October 2026. The full visual design is complete, drawn screen by screen, and the code is now being made to look and work as drawn. Switching on the first bridge comes after that.

I started in August 2026, documentation first, built with Claude Code.

The making

  • TypeScript
  • Next.js
  • PostgreSQL
  • Prisma

01 · The problem

Before it existed

What hurt

A family of plant applications needed to talk to each other, and every connection was an ad-hoc secret with no record of who allowed it or what it could reach.

Who uses it

  • Platform owner
  • Application owners
  • Quality and IT reviewers
  • 147commits in ten weeks
  • 84pull requests
  • 762automated tests
  • 13entities in the control-plane model

02 · The flow

7 steps, in the order they happen

  1. 01 / 07

    Snap two bricks

    You
    Drags one application brick onto another
    It answers
    Finds a joint and counts it; no governance on the public door
    A dark front door with the line Snap two bricks and coloured application bricks on a baseplate
  2. 02 / 07

    Plug in

    You
    Taps the three blocks: who, what, proof
    It answers
    Signs in with a local ID and password; Darpan stays a dormant second door
    The sign-in screen with three blocks titled who you are, what you may do, proof it is you
  3. 03 / 07

    Read the estate

    You
    Opens the board for a unit
    It answers
    Draws every application, bridge and health state; the first failure surfaces
    The Unit One board with application bricks, health counts and a needs-a-look card
  4. 04 / 07

    Press a brick

    You
    Selects one application
    It answers
    Highlights its bridges and offers to look inside it
    The board with one application brick selected and its connections lit pink
  5. 05 / 07

    Add a tool

    You
    Names it, drops its manifest, picks a unit
    It answers
    Records a connection that is off, with no credential issued
    A three-step form: who is it, what does it say, where does it stand
  6. 06 / 07

    Open a door

    You
    Names an application, a plant and a department
    It answers
    Writes the access rule; Darpan syncs a versioned copy and enforces it
    The entitlement register form: which application, which plant, department code, reason
  7. 07 / 07

    Open the ledger

    You
    Slides up the register
    It answers
    Lists every bridge with its state, in the words the audit desk uses
    A ledger sheet listing bridges such as Darpan to Cleanroom with health and on or off state

03 · What was special

What it stands on

  1. The joint, not the pipe

    Business payloads travel app to app. Setu holds the keys, the rules, and the record.

  2. Unlawful bridges cannot exist

    A bridge across units is refused by the database itself – not by convention.

  3. Play with a plain-words twin

    Every brick snap is also written as a sentence for the audit desk.

Setu decides who may cross. It never carries the data.

Making-Of

A serious control plane that feels like two bricks clicking.

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

  1. The world before

    The plant’s applications each held their own connection secrets and scopes. Nothing recorded which application may call which, or whether the link was healthy.

  2. One day

    2 August 2026. Documentation first: a brand identity, a nine-study design gallery and a constitution for how applications may connect.

  3. Because of that

    1. The control-plane model, the credential issuer and read-only health ingestion landed in the first two days (2–3 August).
    2. Setu became the entitlement register that Darpan copies and enforces locally (3 August).
    3. A local sign-in replaced reliance on Darpan as the only door (24 August).
    4. Version 2 of the front door, board, handshake and ledger followed the approved Paper designs (2–3 October).
    5. One connection, from Darpan to Gurukul, was switched on under its own decision record (8 October).
  4. Until finally

    Setu is live with the family registered. Bridges are switched on one at a time, each under its own decision record.

  5. Since then

    The visual-first redesign and the Order 9 gate are the next work.

The evidence Process, hands, and artifacts

Process

  1. Origin

    Docs and brand first; no payload in the database

  2. Board

    The operating board draws real rows

  3. Register

    Setu authors access rules; Darpan enforces a copy

  4. Freeze

    No production credential or bridge until the gates close

  5. Door

    A local sign-in that does not depend on Darpan

  6. Version 2

    Front door, board, handshake and ledger redrawn

  7. First bridge

    One connection switched on under a decision record

Hands

Akshansh

  • Concept: governance as a brick board
  • The integration constitution and every product ruling
  • Approval of each gate

Agents

  • Claude CodePrimary builder and reviewer
  • CursorExecuted written briefs