The weekly newsletter

Subscribe for a weekly newsletter: what I'm learning building handprint, early findings from the network, and what's shipping next.

It's patronage, not a paywall. handprint stays open source and free either way. Subscribing keeps it independent and puts you on the list.

Open source

The protocol, the CLI, and the glyph engine are all open. A star helps.

  • handprint Public

    Decision provenance protocol so humans own human data

    TypeScript
  • ridge-field Public

    Deterministic friction-ridge (fingerprint) synthesis from configurable shapes + orientation fields. Rust core, based on Düring et al. (2019).

    Rust
  • Deterministic synthetic-fingerprint synthesis in TypeScript. Anisotropic particle relaxation (Düring et al. 2019). Zero deps. Powers handprint.sh.

    TypeScript

Where this is going

Three things I'm building toward. The direction matters more than the dates.

  • Cheaper marks, same judgment Extraction should cost next to nothing. Prompt caching, atomic marks, and local-first passes let handprint read more of your work for less, without watering down what it actually captures.
  • Ambient, still yours Less ceremony, fewer commands. handprint should sit quietly alongside your work and surface decisions as they happen, while you keep full control and clear guardrails over what it can touch.
  • Ambient without leaking The more ambient it gets, the easier it is to catch something you never meant to share. So the human stays in the loop: extraction runs locally, secrets are scrubbed before anything is signed, and nothing is published until you push it.

Shape the roadmap

These are the open questions I care about most right now. If you have a view on any of them, I want to hear it.

  • How should handprints interoperate across tools and hubs, so this never becomes another silo?
  • What would make this trustworthy enough to run on your real work?
  • How should it get distributed and actually reach the people who'd use it?
  • What do data owners need to benefit from their own data: viewing it, sharing it, connecting, and socializing around it?
  • What does a healthy people-system around this data even look like?

If any of this is your thing, get in touch. cam@handprint.sh