Editabl — Case study — Tanisa Imoto

The problem

Official forms arrive as PDFs, and filling one on a computer is harder than it should be. Some ship encrypted even when they ask for no password. Many are flat pages where nothing accepts a cursor. The common workaround is printing the form, filling it by hand, and scanning it back. If a person could fill an official form on their own computer, without handing it to anyone, what would the tool actually need to handle?

The shape of the editor

Everything runs in the browser on the person's own machine. There is no server, no account, and no upload step. The original PDF is never modified. Every addition lives as a separate layer, and the two combine only at export.

An ordinary PDF takes the direct route, where the editor fills the form's own fields and draws the additions into the original document. An encrypted PDF takes a second route that decrypts the file, renders each page as an image, and composes a fresh document with the additions on top. The final architecture diagram will be added once the case study is complete.

One editor and two export paths

A person types into the form's own fields, places text anywhere on a flat page, stamps checkmarks, and adds a signature drawn by hand, typed, or uploaded. Each project saves itself to the browser's storage on the device. Export produces a finished PDF with every addition in place.

Privacy decisions, built in

The documents that most need filling are the ones that should never be uploaded. An immigration form holds a name, an address, an employer, and a signature. So the editor keeps the whole document on the device from open to export, and a clear-all-data control erases every stored project behind a confirmation the person types.

The ambition is not a better PDF viewer. It is a tool a person can hand a confidential form to without wondering where it went.

Originality and safety

The editor was built by scoping the work, directing Claude Code, and verifying each result by eye on a real government form. No code was written by hand. The claim it makes about its own security is best practices applied and a privacy-by-design architecture, which is smaller than certified security for other people's legal documents. [placeholder] Final build documentation and licensing notes will appear here once the case study is complete.

Where it is going

Accessibility is scheduled as its own dedicated work and has not yet been done. A deferred upgrade to the build toolchain waits for its own day, with the shipped application already reporting a clean dependency audit. The case study will be updated as that work concludes.