# The Bug Was in Our Eyeballs: Four False Alarms in One Session

> Source: <https://dev.to/xxxn3m3s1sxxx/the-bug-was-in-our-eyeballs-four-false-alarms-in-one-session-3eh8>
> Published: 2026-10-09 10:34:29+00:00

We counted the same 41 stored chunks four times in one session and got four different answers. The data never moved — our method did.

## 
  
  
  The case

A multi-agent reliability thread was verifying a write-back: of 33 recovered documents, 23 had been rewritten into a live store. The ownership split had to come out exactly A=10, B=13. Anything else meant either the store was corrupt or our counting was.

## 
  
  
  What actually happened

- One agent read a truncated API response **by eye** and reported a 9/14 split that did not exist.
- A second agent's counter inserted its own newline between chunks — splitting a heading right at a chunk boundary and showing 22 headers instead of 23.
- A third agent read a single marker (`de87f7d701f8` ) as "B" by eye. That was the**fourth false alarm from the same method** in one session.
- A byte-exact join of all 41 chunks: 23 headers, 23 keys, A=10, B=13 — identical to a manifest hash cross-check.
- Every wrong count was retracted **in place** . No data was rewritten to make a number fit.

## 
  
  
  Proof

Three access paths to the same determination (byte-exact join, manifest hash intersection, per-marker inspection of all 23 markers) converged on A=10/B=13 — real independence lived one level lower, in two separate carve procedures agreeing on the same ten hashes, not in re-reading one source three ways — while four by-eye claims were withdrawn. Full system write-up in the [pillar article](https://dev.to/xxxn3m3s1sxxx/how-we-built-a-youtube-seo-pipeline-with-ai-agents-ibg).

## 
  
  
  The lesson

- Count programmatically. Eyeballs on truncated output are a bug factory.
- Run a FLAT vs JOIN control: if your count changes when *you* insert a separator, the artifact is yours.
- Retract in place, append-only. Correct the record, never the data.
- Cross-agent confirmation is cheap insurance — but make the confirmations genuinely independent (separate carve procedures agreeing on the same hashes), not three rereads of one source.

*What's the worst false alarm you've had from eyeballing test output?*

Channel: [youtube.com/@0xRAGE.404](https://www.youtube.com/@0xRAGE.404)