closer-claim-provenance

The gate that stops a guess becoming next week's fact

On 24 May I audited my own 27-skill toolkit. Three of the skills were teaching Claude to fabricate. Not in the instructions. In the sample outputs.

What the audit actually found

A pitch deck citing "Anthropic 2025 internal data." A business plan quoting a benchmark that doesn't exist. A testimonial from a person who doesn't exist, with a handle that looks real.

Every one of those files had a no-fabrication rule written at the top. The example underneath it broke the rule. Pattern-matching beats instruction every time. The model learns from the sample, not the sentence above it.

They were fixed before the toolkit shipped. But catching it by hand once is not a system.

Every claim carries a tag or it doesn't get written

[VERIFIED: source]I opened the primary source myself, in this session.
[INHERITED: source]Came from a past session, memory, or another agent. Not re-checked. This is the honest default.
[HYPOTHESIS]I made it up on purpose, and I am saying so.

An inherited claim never becomes verified by being repeated. It becomes verified only by someone opening the source.

Three rules that do the work

gated words
audit · proven · benchmark · validated · tested · measured · confirmed

These words assert that a process happened. They stay locked until five named data points clear the gate, each carrying its own verified tag. Four is not five.

Every locked rule needs a falsifier. If nothing could disprove it, it is a preference, not a rule, and it gets written as one.

Nothing auto-carries between sessions. Everything you read from last week enters as inherited, however confident it sounds. Confidence in the source document is not evidence.

Send me the file

It lands on this page straight after, and in your inbox as a backup. Free, and it runs on the Claude free plan.

could not save your email. try again in a sec.

One file, no drip about it. Unsubscribe whenever.

it's yours

Install closer-claim-provenance

1

Make the folder ~/.claude/skills/closer-claim-provenance/

2

Save the file below inside it as SKILL.md. Use the download button, or copy and paste.

3

Start Claude and ask it to run closer-claim-provenance on the last thing you built. Check whether the examples agree with the rules.