2026-08-03

Why the commit history is the real proof

The most uncomfortable part of a fixed-price project is rarely the delivery itself — it’s the proof. “We work to OWASP” is a statement of intent. What’s usually missing is a form that doesn’t have to be claimed, only shown.

A chain of linked blocks recedes into the distance, the newest receives a seal stamp on the anvil — every step leaves a verifiable record

A chat transcript proves nothing

The obvious output of an AI-assisted system is a conversation log: prompt, answer, maybe a code block to copy. That’s not verifiable after the fact — whoever reads the transcript sees what the model said, not what actually ended up in the project. With Anvil Coder, the result isn’t a transcript; it’s a Git repository with real history.

What a commit actually proves

Every TaskSlice leaves its own commit, every phase its own state. That’s not just about tidiness: a commit carries a timestamp, a diff, and — because guardrails apply at every single work step, not as an afterthought check — the invariants that step was built under. What’s in there is verifiable: by a human, by a pipeline, by an auditor. Nobody has to take anyone’s word that a rule was followed; it’s visible in the diff whether it was.

Custom rules count too

An agency rarely brings only the built-in invariants — usually its own as well: a particular layering, a naming scheme, a banned library. Those can be stored as a guardrail of their own and get injected in the same prompt as the built-in ones, with one distinction that matters for proof: as plain prose, a custom rule works inside the prompt but not in an additional, machine-checked validation. Anyone who wants that too has to store it as a machine-readable rule, not just a sentence.

Proof isn’t a blank check

A verified history shows the conditions a step was built under — it says nothing about whether the requirement itself was right, or whether the underlying cut of the problem holds up. That stays a human decision, before and after every run. The real difference is elsewhere: when a client asks how a specific part came to be, there’s an answer that can be looked up, instead of one that has to be believed.