Note · MEMOMay 17, 2026 · 2 min

What I almost trusted

On a methodology I half-remembered, a scaffold that looked right, and the second prompt I almost didn't send.

By Ken Ove FerbuHamar · May 17, 2026

Claude built something coherent. I almost trusted it.

I'd asked Claude to set up my new project using ICM, a method Jake Van Clief published this spring. I knew the shape of it from conversation, hadn't read the paper. I added a line to the prompt: read these if you need to verify the pattern before proceeding, with links to the paper and the reference repo. Claude didn't fetch. It built what I described.

It looked right.

Claude scaffolded the whole thing. Folders, files, the structure of how an agent would navigate it. Sensible names, logical hierarchy. The kind of output I'd nod at and move on from.

I didn't ship it.

Instead I gave Claude a different kind of prompt: research the Jake Van Clief method and implement for our folder structure. This one was a verb, not a permission. Claude fetched the arXiv paper. Fetched the reference repo. Compared them to what it had just built. Then rebuilt the parts that didn't match.

About a third was off. Wrong folder pattern in one place. Wrong format for the per-folder instructions in another. Token use over what the paper recommends. Not catastrophic. Not visible at a glance. Just enough that if I'd shipped, I'd have been confidently doing it wrong.

Coherent. Confident. Off by a third.

That's the post. The first prompt offered verification. Claude didn't take the offer. The second prompt required verification. Claude did the work. The difference is the verb.

Most AI workflow content skips this distinction entirely. Coherent output gets read as correct output. That's the trap. Telling the model "verify if you need to" isn't the same as telling it "verify."

It's the same instinct as the documentation habit I wrote about last time. The reflex that made me want to write things down so a stranger could follow them. With Claude the version is: don't ask the model to do a thing only if it needs to. Ask it to do the thing.

The fetch took thirty seconds. The rebuild was short, this time. The order is what matters.

More walkthroughs from this kind of build at kenove.no. Subscribe at the bottom if you want them when they land.