Back to the shelf

041

SanctumQMS

A quality management and laboratory information system for pharma, wearing a medieval sanctum as its living world.

Launched · 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

Quality management in pharma is rigorous. Rarely a place worth inhabiting. SanctumQMS is the quality realm I built for the pharma company I work with: a quality management system and a laboratory information system in one.

It wears a medieval sanctum metaphor, a living three-dimensional world. Underneath it has an audit trail, e-signatures, and role-based access.

The first phase shipped as validated G M P training, with a full validation package. Then the quality chambers came: deviations, corrective and preventive actions, change control, market complaints, an observatory. The lab side is still in active development and already in production.

In July twenty twenty-six, general learning moved to Gurukul, so Sanctum could focus. Vibe-coded with AI, it is live and in use.

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

SanctumQMS
No. 041

The quality world I built for the pharma company I work with looks like a medieval sanctum. It’s a living, three-dimensional realm, designed to feel like somewhere you inhabit, not a form you fill in. Underneath that metaphor, the rigor is strict: audit trail, e-signatures, and role-based access.

SanctumQMS is a quality management system and a laboratory information system in one. It’s built for quality control and quality assurance work, in a single place.

I started in May 2026, vibe-coded with AI. The stack is Next.js, Prisma, PostgreSQL, and Three.js.

The first phase was validated GMP training, complete with a full validation package. Then the quality chambers shipped: deviations, corrective and preventive actions, change control, market complaints, and an observatory.

The lab side is in active development and already running in production.

In July 2026, general learning and skill development moved out to its own home, Gurukul, so Sanctum could stay focused on quality.

It’s launched, live, and in use.

The making

  • Next.js
  • Prisma
  • PostgreSQL
  • TypeScript
  • Three.js

01 · The problem

Before it existed

What hurt

Quality software for a pharma plant arrives as grids, PDFs, and audit dread. People open it because an audit forces them to, and the record suffers for it.

Who uses it

  • QA head
  • QA officers
  • QC analysts
  • QC reviewers
  • Trainees
  • Observers
  • 946commits in six months
  • 88pull requests
  • 8chambers in one world
  • 14laws in its constitution

02 · The flow

6 steps, in the order they happen

  1. 01 / 06

    Arrive in the grove

    You
    Opens the sanctum
    It answers
    Grows the world from live records; the tree’s light is the plant’s compliance
    A 3D grove with a central guardian tree, chamber orbs and a health card reading 64 per cent
  2. 02 / 06

    Read the Hall of Scrolls

    You
    Lifts an SOP to read it
    It answers
    Shows the live version, keeps every superseded one, retrains on a major revision
    The Hall of Scrolls panel listing SOPs with their setup state
  3. 03 / 06

    Descend into Deviation Hollow

    You
    Opens a breach, complaint or out-of-spec event
    It answers
    Runs one investigation spine for all three, with its clocks
    Deviation Hollow showing open, major and planned breaches and complaints
  4. 04 / 06

    Stand in the Chamber of Order

    You
    Reads the health of the whole sanctum
    It answers
    Computes compliance from training, decrees and vows
    Chamber of Order overview with sanctum health at 70 per cent
  5. 05 / 06

    Work the bench

    You
    Taps a sample orb on the tablet, gloves on
    It answers
    Fills a ring per sample as each test facet is read
    The Bench: sample orbs with progress rings on a dark tablet screen
  6. 06 / 06

    Record the reading

    You
    Picks the observation for one facet
    It answers
    Binds it to the controlled test procedure and compiles the report
    One sample orb beside the observation choices for its description test

03 · What was special

What it stands on

  1. The world is the interface

    No dashboards, no settings pages. Every module is a place with its own orb, camera, and chamber.

  2. Health you can see

    Canopy, ground, and bloom grow from real modules, SOPs, and finished work. A neglected plant looks neglected.

  3. Fantasy copy, literal compliance

    Insert-only audit trail, e-signature with password re-entry, and a reviewer who cannot approve their own review – enforced on the server.

Play surrounds the record. It never enters it.

Making-Of

A quality system that looks like a forest and refuses to behave like one when it counts.

The first brainstorm and the first commit, the same day

  1. The world before

    Quality and QC teams worked from paper procedures and controlled forms. Commercial quality suites were priced like capital equipment and felt like it.

  2. One day

    26 May 2026. The idea: a GMP quality system where each module is a quest in a storybook world – training as trials, deviations as breaches, change control as decrees. The first commit landed that evening with a Three.js forest and the Trial Grounds.

  3. Because of that

    1. The rigour stayed literal: a trial cannot be sealed until its assessment is passed (29 May).
    2. Deviation, CAPA, change control, market complaints and an observatory arrived as chambers of the same world (9 July).
    3. A narrated, skippable onboarding in a practice realm that writes no real records (12 July).
    4. The lab joined: The Wellspring, a LIMS inside the same world, not a second product (14 July).
    5. Scope cut to quality and lab only; general learning moved to Gurukul (28 July).
    6. From 26 August the QC team raised its own pull requests, reviewed against production data before merge.
  4. Until finally

    SanctumQMS is live. Training and the lab bench are in daily production use; the quality chambers are shipped.

  5. Since then

    On 3 November one design pass gave every screen – world, bench and entry – a single language: a drawn seal and eight chamber sigils in place of emoji.

The evidence Process, hands, and artifacts

Process

  1. Origin

    Storybook world on the surface, ALCOA+ rigour underneath

  2. Hardening

    No seal without a passed assessment

  3. Chambers

    Deviation, CAPA, decrees, complaints, observatory

  4. Onboarding

    The First Pilgrimage, in a practice realm

  5. Lab

    The Wellspring LIMS joins the world

  6. Scope

    Quality and lab only; learning moves to Gurukul

  7. Method

    The QC team authors fixes; review before merge

  8. Design

    One design language across world and bench

Hands

Akshansh

  • Concept, metaphor and every product ruling
  • Design direction and the 14-law World Constitution
  • Review and independent verification of what the agents built

Agents

  • Claude CodePrimary builder and reviewer
  • CursorExecuted written briefs
  • ElevenLabsSound cues, narration and the voice deviation logger