Parakh

Parakh means the assay. The act of testing a thing to establish its quality. A parakhi is an assayer who rubs gold against a touchstone and reads the streak.

That image felt right for what I was building: a validation lifecycle system for every instrument, machine, facility and utility at the pharma company I work with. Each asset is qualified the first time, then re-proved on a cycle, for as long as it lives. Its state of qualification has to be provable at any instant.

The whole lifecycle was manual before this. A large Excel calendar. Hand-typed Word protocols and summary reports.

I kept returning to the idea that every asset is a timepiece. Its qualification is stored energy. A validation winds it. When it runs down, the movement stops.

Parakh is built on an append-only qualification ledger. Due dates, the calendar, overdue detection and the annual plan are all derived from it. Two rules hold the whole thing together: nothing that can be computed is ever typed, and no date is ever invented. Protocols are executed on a tablet. The summary report writes itself from locked data.

I started in July 2026, documentation first. Parakh is feature-complete and live, and still being built. The team who will use it is now validating it, and their feedback shapes what comes next. Follow along if that matters to you.