Undersign
The Making Of

Built in the open,
prompt by prompt

Undersign — an on-device e-signature app — designed and built in one short night with an AI agent (Claude Code) under human direction. This is the timeline behind it, reconstructed from the build log.

Six phases. Sixteen minutes.

The 16-minute sprint

Phases 0 → 6 · 05:15 → 05:31 IST
05:1505:1905:2305:2705:31

Each phase committed and pushed on its own — six green check-ins in a quarter of an hour.

The timeline

human prompts in terracotta · build phases in teal
Human prompt Decision Build phase Rename Milestone Live bug Fix

What's it called

the naming arc is part of the record
Signet SreeSign Undersign

What's real, what's staged

the honest part

Real: the document engine (pdf.js render, pdf-lib flatten), signature capture, the audit trail, and SHA-256 tamper-evidence — all running with zero backend, nothing leaving the device.   Simulated / out of scope: cross-device delivery (no server, so signers role-switch in one browser), and regulated eIDAS/ESIGN certification or identity verification. Knowing exactly where the moat is — workflow, compliance, integrations — is the point.