Every shop has a guy like this: the one who just knows that a particular edge tear is almost always the trim punch clearance being off. Nobody wrote that down anywhere. It's not in a manual. It's in his head, and it took him fifteen years to learn it the hard way.
When he retires, that knowledge doesn't get handed off. It just leaves. The next person re-discovers the same fix, the same slow way, usually after a bad week.
TatteredNote exists to capture that kind of knowledge the way it actually gets shared on a floor — symptom first, ranked by what's worked, not organized like a document library nobody opens.
I'm building it self-hosted on purpose. Shops that don't want another cloud subscription, and manufacturers who legally can't put controlled technical data in one, both need the same thing: software that runs on hardware they already control.
Core architecture decisions finalized: self-hosted deployment, append-only event model, fuzzy tag governance, solution ranking.
Database schema, models, and integrity constraints implemented and documented.
Symptom-first search, tagging, incident and solution tracking, roles and access control.
Looking for a small number of design-partner sites — small shop and controlled-data manufacturer — to validate the MVP against real use.
A polished demo is easy to fake and easy to distrust. An honest account of what's built and what isn't is more useful to anyone actually deciding whether to run this in their shop — or their controlled-data environment.
We'd rather talk to you now than sell you something finished later.
Get in touch