Your resume can be faked in an afternoon. Your work can't.

Anyone can now ask an AI to write a polished, backdated account of their career in an afternoon. A glowing summary of projects you led, skills you mastered, impact you drove: generated in minutes, nearly indistinguishable from the real thing, and almost impossible to verify after the fact.

That should worry anyone who relies on resumes, LinkedIn profiles, or portfolios to signal what they've actually done. Every one of them is a self-reported claim. They always have been. We just used to treat the effort of writing them as a weak proxy for truth. AI removed that proxy.

Polishing the claim doesn't fix the problem

Most advice for standing out right now is about being more visible: post more, network more, build a personal brand. That isn't bad advice. It just solves discoverability, not credibility. It makes claims louder, not truer.

In a world where anyone can generate a convincing story about their past, louder claims just mean better-produced fiction competes with honest work on equal footing.

What if your work wrote itself down as it happened?

I've been designing, and am now building (for myself first) a different answer: a work journal that doesn't rely on you remembering to write anything down, and can't be quietly rewritten later.

The core idea is simple. Instead of a document you write once and polish forever, it's a log that captures itself passively from things you're already doing: commits, calendar events, the real trail of a working life. Periodically, weekly or monthly, you review what it captured, approve it, and it becomes part of a permanent, dated record.

The part that matters most: once an entry is approved, it's immutable. Not "hard to edit." Actually append-only, enforced at the core of how the tool works, with optional cryptographic timestamping so the record's integrity can be verified by anyone, even years later, even if I disappear as the person maintaining it. That's what turns it from another journal into something closer to proof of existence at a point in time.

The shape of it

A few design decisions I think matter:

• Local-first. Your data lives on your machine by default. Nothing is required to leave it.
• Passive, not another app to open. It runs quietly in the background and nudges you, rather than waiting for you to remember it exists.
• Open source. The whole point is trust, so there's nothing about how it works that isn't inspectable.
• Immutable by design. Entries can be corrected by appending, never edited or deleted.
• Optional, not mandatory sharing. The log is yours. What you choose to show a future employer, or no one at all, is up to you.

Where this stands

I'm building a personal version first, pulling from my own GitHub and calendar into a monthly rollup, and I'm going to actually live with it for six months before deciding whether it's worth being more than that. No grand claims yet. I just think the underlying problem is real and getting worse, and I'd rather find out if this is a genuine answer to it than assume it is.

If this resonates, or if you think it's solving the wrong problem, I'd like to hear it.