When the volume of code is no longer the evidence of human impact, what we can still measure is the provenance of judgment — the decisions, the predictions, and the moments where a person steered the work. handprint.sh is an open protocol for recording that provenance, kept private by default and made auditable on your terms. It exists to define what it means to build, as a human, in the company of machines.
handprint watches the seam between you and the tools you already work with — chat, terminal, IDE, team channels — and quietly flags the moments where your judgment shaped the outcome. The session below is a real-time replay from an auth-service-v2 redesign.
Detection runs on a lightweight model on your machine. Your work never leaves your laptop until you choose to seal a record — and even then, every entry stays private until you explicitly mark it public. Every sealed entry is a structured intent record per the handprint protocol v0.1, with cryptographic provenance baked in.
handprint listens for five shapes of human judgment in the work you’re already doing. The structure of each entry — type, intent, risk, horizon — is inferred from the context, and you confirm with a keystroke when something feels worth keeping.
each handprint is timestamped before the outcome. each resolution is appended, never edited. over months and years a pattern emerges — how this person decides, where their judgment is sharpest, and how honestly they learn when they were wrong.
the centerpiece is the calibration score — computed, never claimed. when this engineer says “i think we should do x,” how much should you trust that?
Installation is a single command and each tool integration is opt-in. Your handprints live on your machine by default; syncing to handprint.sh is opt-in too, and entries you keep private remain encrypted at rest — only the records you explicitly mark public become searchable.