Caveat first, because most posts like this bury it and I'd rather lead with the part that's actually honest. What I'm building can prove a process happened. It cannot prove a human did the thinking. If you automate the steps, or paste an LLM's answer through them, the record still fills up. So this is not "proof of human." It's proof of process. If that distinction doesn't matter to you, you can close the tab now and we're still friends.
Here's the thing that's been bugging me for months.
A year ago, if someone handed you a tight decision memo — three options weighed, one picked, the reasons written down — the artifact itself was evidence. Producing it cost judgment and time, so having it meant someone spent both. That link is gone. Anyone can generate a plausible version of that memo, or a clean PR description, or a crisp design doc, in about nine seconds. The output stopped being proof of anything.
So what's actually scarce now? Not the answer. The trail to it. What you decided, what you rejected, when, and what happened after reality pushed back on the call. That part AI can't hand you, because it doesn't have your context, your constraints, or your consequences. The decision-to-outcome loop is yours. The problem is almost nobody records it, so it evaporates. You end up with the polished final thing and no memory of the reasoning that got you there.
Why this got urgent
We're drowning in plausible output, and we're starting not to trust any of it. Reviewers can't tell what a person reasoned through from what got autocompleted. The main response so far has been detectors, which are a losing arms race — every detector gets beaten, and worse, they flag careful human writing as fake. I think the more honest move isn't to detect the fake. It's to let the real work keep a receipt.
What I'm building
Working name Glovrex. The short version: you record decisions as you make them. What you chose, the options you killed, the reason. Then it links each decision to what actually happened later — the outcome, not just the intention. The record is tamper-evident, so you can't quietly backdate a call to look smart after the fact, and neither can anyone reading it.
What comes out the other end is a portable log. "On this date I decided X over Y and Z, for these reasons, and here's how it aged." A receipt for your own judgment. It's useful to you, because your past self is a stranger and this is how you audit whether your reasoning was any good or you just got lucky. And it's useful to show other people, because a track record beats the polished final artifact that everyone has learned to distrust. The version of this I already trust most is boring: a GitHub profile full of other people's merged PRs. Nobody can generate that one for you.
That's the visible value. I'm going to stay quiet on how it decides what to keep and surface. That's the part I'm still building and the part that's mine.
The honest limit
Back to the caveat, because it's load-bearing. Provenance proves the process ran: these steps, at these times, in this order, unaltered since. It does not prove the quality or the humanity of the thinking inside. Recording a decision doesn't make it a good decision. And a determined faker can perform the whole ritual with a bot.
What tamper-evidence actually buys you is narrower and more real: the record can't be silently rewritten later. The timeline is honest even when the thinking wasn't. That's a much smaller claim than "verified human work," and I'd rather ship the smaller true claim than the bigger false one. If I ever start selling this as proof a human did the cognitive labor, call me on it.
One more thing worth saying plainly. This sits on top of LLMs, not against them. I use them all day. The point isn't "AI bad." It's that when generation is free, the generated thing carries less information, and the trail around it carries more. Glovrex is a layer for the trail.
Where this is
Pre-launch. No signup wall to shove at you, nothing "revolutionary," no metrics I haven't earned. I'm writing this partly to think out loud and partly to find the people who already feel the problem — engineers, researchers, anyone whose real value is their judgment over time, watching that judgment get harder to prove as the output around it turns to noise.
If that's you, here's the disagreement I actually want: where does "proof of process" stop being useful and start being theater? That's the question I don't have fully answered yet, and it's the one that decides whether this is worth building.
Top comments (0)