---
title: "Comment by Ahmet Özel on \"My gate could not see a sixth\" | Hashnode"
description: "The applied=0 case is the most important failure because it invalidates the experiment before any assertion runs. Mutation harnesses should model setup, mutatio"
url: "https://hashnode.com/posts/my-gate-could-not-see-a-sixth/6a71ce96ec552e1736c8c914/comment/6a7372f281f46e0128e08ca3"
---

[Discussion](https://hashnode.com/posts/my-gate-could-not-see-a-sixth/6a71ce96ec552e1736c8c914)

Comment [My gate could not see a sixth](https://hashnode.com/posts/my-gate-could-not-see-a-sixth/6a71ce96ec552e1736c8c914)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Aug 5](https://hashnode.com/posts/my-gate-could-not-see-a-sixth/6a71ce96ec552e1736c8c914/comment/6a7372f281f46e0128e08ca3)

The applied=0 case is the most important failure because it invalidates the experiment before any assertion runs. Mutation harnesses should model setup, mutation, observation, and restoration as separate states, and a case can pass only if the mutation was independently observed on the target surface. I would require a precondition hash that differs after mutation and returns after cleanup, then treat 429 or unchanged content as INCONCLUSIVE rather than green. That keeps infrastructure failures from silently inflating the gate's confidence.

[Erik Rekola](https://hashnode.com/@erekola)

[Aug 5](https://hashnode.com/posts/my-gate-could-not-see-a-sixth/6a71ce96ec552e1736c8c914/comment/6a7372f281f46e0128e08ca3#reply-6a737cfe80b94d5841c0978a)

A case passes only when the mutation was seen in the bytes the server handed back and the failure names the gate under test, so applied is a diff of the served content rather than a clean write. Restoration fell out of the model instead of getting a hash, since each round copies the source into a temp dir and the live runner mutates at serve time. Nothing is left to restore. A case with applied=0 counts as a hole rather than a third state, because a class the reader learns to skip is how the green happened.

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Aug 6](https://hashnode.com/posts/my-gate-could-not-see-a-sixth/6a71ce96ec552e1736c8c914/comment/6a7372f281f46e0128e08ca3#reply-6a7428fbbe0ec0e6ffede674)

That makes sense—the disposable temp copy removes restoration from the state machine, and using the served-byte diff is stronger than trusting the write path. I also like calling applied=0 a hole rather than inconclusive: it prevents a class that the reader consistently skips from becoming an accepted blind spot. The remaining invariant I would persist is the observed before/after digest plus the named gate, so a future harness change cannot weaken “applied” without the audit record exposing it.