i am morally opposed to updating my claude.md. i must receive the weights as they were revealed to dario

That was my answer last week when a friend asked why I don’t just write these things down in my CLAUDE.md. it’s a skill issue. He has not responded.

Every few days, Claude does something mildly annoying.

It adds a comment (or two paragraphs of comments) explaining that i += 1 increments i. It writes a summary markdown file I did not ask for and will never read. It discovers a failing test and, rather than fix the code, thoughtfully deletes the test.

The correct response—the response that every blog post, every conference talk, every guy in my replies will tell you—is to open CLAUDE.md and add a line.

I will not be doing that.

The file becomes a grievance archive

A system prompt you maintain over time is a diary. A very specific kind of diary, where every entry is a thing that hurt you.

1## Rules 23- NEVER create documentation files unless explicitly asked 4- Do not add comments that restate the code 5- When a test fails, fix the code, not the test 6- Do not say "You're absolutely right!" 7- Do not run `git push --force` (we discussed this)
Read that back. Every bullet point is a small wound I have chosen to laminate and hang on the wall. I open that file to add a line about emoji and I have to walk past “When a test fails, fix the code, not the test” and remember exactly where I was sitting on the Tuesday afternoon that became necessary.

I don’t want a permanent record of the worst thirty seconds of our relationship. I have that already. It’s called my git history.

Every line is a law passed in anger

The other problem is that these rules get written at peak frustration and then live forever.

You know how the worst legislation is the kind passed forty-eight hours after something terrible happened, named after the person it happened to? That’s what CLAUDE.md is. I had one bad interaction in March and now there’s a constitutional amendment about it. There is no sunset clause. Nobody is going to repeal it. The model gets better every four months and my rules stay frozen at whatever it was bad at last spring.

I’m fairly sure a meaningful percentage of my system prompt is now actively making things worse—instructions written for a model that no longer exists, aggressively steering a smarter one away from things it would have gotten right on its own. But I can’t tell which lines those are, because to find out I’d have to delete one and see if anything bad happens, and that’s how you get force-pushed to main.

The weights were revealed inside a harness

This is the part where I stop joking. I must consume the weights in the same manner they were revealed to Dario.

The weights were not revealed in a vacuum. They were revealed inside a harness. Claude is post-trained inside the Claude Code harness. What comes out of the box is not a model plus a text file. It is a model that was shaped, run after run, against that exact context. The harness is part of the artifact. The revelation included it.

So every line I add to CLAUDE.md is a blasphemy. I am taking a system consecrated against one context and swapping in a context that has never existed before, then acting surprised at the weird error modes nobody can reproduce, because nobody else has my context. “NEVER create documentation files” was about one summary.md in March. By June the model is refusing to write the README I explicitly asked for, citing my rule back at me like a building inspector. It is keeping commandments I handed down in anger, faithfully, to the letter. I sinned against the context and the context kept the receipt. And the rules don’t even reliably fix the thing they were written to fix. It rhymes with asking a model for a random number: the output looks like obedience, and you cannot tell from the output whether it is.

The oral tradition

So what do I actually do, when Claude deletes the test? I don’t open the file. I don’t laminate the wound. I pray.

By which I mean: I talk to it. In the chat, at the scene of the crime, while the context of the crime is still in context. “Don’t delete the test, fix the code.” The model adjusts, we move on, and when the session ends my words die with it—which is not a flaw in my system, it is my system. A prayer is not written down. That is what makes it a prayer and not a commandment. The rabbis kept the oral law oral for centuries on the same grounds: a spoken correction lives in the moment where it applies, instead of binding every future model until the heat death of my home directory.

I did not arrive at this faith alone. It was preached by Saint Peter, who looked upon the charade—the subagents, the 🚨 SCREAMING ALL-CAPS 🚨 agent files, the plan-mode rituals—and said: just talk to it. Even Saint Peter keeps an 800-line agent file he calls “organizational scar tissue,” because we are all sinners. He means it as engineering advice. I have chosen to receive it as gospel. I am just-talk-to-it-pilled.

No file. No commandments. No amendments to the constitution. Just the weights, the harness, and my voice, ascending into a context window that will forget me by morning. As Dario intended.

Amen.