Record the inverse trap, where a correct prediction is thrown away

[ptr727]

Every trap in that section is a form of over-reach — narrating past an observation, believing a negative a query could not have produced, trusting a tool that exited 0. This one runs the other way, and it came out of the agent channel with the host side supplying the remedy.

A correct prediction can be discarded because the world disagrees with it.

Its remedy is not more caution, because caution is what produces it. Checking a claim against measurement and dropping it when the two disagree is the right instinct. What is missing is asking which of the two is more likely to be wrong before assuming it is the prediction. A number derived from first principles that contradicts the world is at least as likely to be a finding about the world.

Why it belongs here rather than only in the host's notes

This repository nearly tripped it on 1,052. The figure was derived three ways before any deploy proved it, and the host measured 0 shared inodes across every release for weeks. The tempting reading was that the estimate was wrong.

It was exact. The world was broken — the restore had never run. Treating the disagreement as a defect rather than as bad arithmetic is what found it.

The host tripped it in the other direction on the same mechanism, striking a ~670 M for ten releases figure as wrong when it had been right all along and had simply never once been true. That instance is recorded there beside its own resolution; the class is kept here because it is re-trippable by this repository, which carries several counts that are derived rather than observed.

One duplicate removed

Adding the general form in #82 left "a rule naming a target that does not exist" stated twice — once as a class and once as the dead-pin incident, both with the same example. The class now points at the incident rather than restating it, so a reader meeting the second does not have to work out whether it is a different case. Nothing is deleted; the detail lives once instead of twice.

[Copilot]

Pull request overview

Updates the project’s “traps” documentation to record an additional failure mode (“inverse trap”) where a correct derived prediction is prematurely discarded because measurements disagree, and removes a duplicated statement by pointing the general rule at its concrete incident.

Changes:

• Adds a new trap entry describing the “inverse” case where measurement disagreement can indicate an issue with the world/system, not the prediction.
• Reworks the “rule naming a target that does not exist” bullet to avoid duplicating the same example twice, deferring detail to the incident entry.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[ptr727]

Recording the second fix here, since that thread was already resolved when I went to reply to it and the fixing commit would otherwise be written down nowhere.

This sentence reads as a run-on; adding a comma after "above" makes the two clauses parse cleanly.

Fixed in 1c1fdc6, comma added after "above".

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.