Skip to content

The work

What the ledger actually finds.

These are findings from my own repositories, with the real numbers, including the one that came back bad and stayed that way. Client work goes at the top of this page when there is a client happy to be named; until then I am not going to dress my own code up as somebody else’s.

01

Scrim

macOS file provider · Swift + Rust · 174 tracked items

The test suite had never run in the push gate.

What the audit found

The suite was reported passing for weeks. It was red, at seven failures, and no push had ever been blocked by it.

Why it was invisible

The gate ran through pnpm and Turborepo, which cannot reach a directory with no package.json. The Swift tree had none, so the task silently resolved to nothing and reported success. Three of the seven failures were the repo's own checks for controls that render and do nothing.

What changed

The suite went into the gate, the seven failures were fixed, and an audit of the previous status found the figure that had been reported for weeks had never been printed by any run.

Swift tests now gated
2,452
Failures at discovery
7
Rows merged but unreachable
4
Unreferenced-type ratchet
122 → 114
02

Offload

macOS daemon · Rust core · 530 test cases

Six guards were green and could not fire.

What the audit found

A suite at 526 of 530 passing, with six checks that were structurally incapable of failing on the defect they existed to catch.

Why it was invisible

One read its marker out of a fixture string rather than the system under test. One lost track of which mistake it had found. One guarded an upstream branch that is unreachable. One was blind to any list-shaped field. One compared a basename against an absolute path and had never once executed its body.

What changed

Each was rebuilt to name the mutation it catches. The armed figure and the mutation-naming figure are now published separately, because 526 armed and 309 naming their mutation are two different claims and reporting one number hides that.

Cases armed
526 / 526
Naming their mutation
309
Guards found unable to fire
6
Ledger rows, nothing unbuilt
633
03

Graft

Mockup-to-SwiftUI engine · 121 delivered items

The coverage ratchet was lowered, on purpose.

What the audit found

Eleven cases claimed a stronger class of evidence than the test underneath them actually earned. The headline coverage figure was therefore too high.

Why it was invisible

A case that asserts an element exists was recorded as proving the behaviour worked. Nobody had lied; the rung a case stands on had never been checked against what the case actually does.

What changed

The ratchet was moved down to the honest number with the arithmetic published beside it, so the figure can only go up from something true. A report that had looked better was replaced with one that was correct.

Cases armed
59 / 59
At a real effect rung
51 (86%)
Overclaiming cases found
11
Ledger rows, nothing broken
213
04

Sidetone

macOS audio utility · 100 triaged items

A reckoning that came back bad, and stayed published.

What the audit found

Sixty-two items measured and broken, two hundred and thirty-one never measured either way, against fifty-seven merged.

Why it was invisible

Work had been merged faster than it had been proved. The board and the repository disagreed, and the board was the optimistic one.

What changed

Nothing yet. This one is included because a page of only clean results is not evidence of a method, it is evidence of selective reporting. The ledger stands at these numbers until the work moves them.

Items merged
57
Measured and broken
62
Never measured
231
Planned, unstarted
34

The same three things, every time.

The green suite is the most expensive lie in the repo.

Three of the four findings above are a passing check that could not fail. A build going green is a claim about the checks, not about the code, and nothing in a normal workflow ever tests the checks.

The dangerous column is never the broken one.

Broken work is visible and gets fixed. Work nobody ever measured looks identical to work that passed, and it is where a rebuild runs aground halfway through.

A figure nobody can trace back to a run is decoration.

Two of these repositories had a headline number in their own status that no run had ever printed. Numbers get copied forward; the run that produced them does not.

Your repository has a version of this.

Every codebase does, mine included. The question is whether you find out now or the week something breaks in front of a customer.

Start an audit