Case studies
Members are encouraged to carry one case study through the year, starting whenever they join. These are the worked examples so far.
California water rate data
California's water rates are public but scattered across hundreds of utility sites and PDFs. Machines can now read any rate sheet; finding the current one is the hard part. So the work focused on discoverability (a registry of each utility's rate page and an llms.txt pattern) rather than a new data standard.
Strategy report · Seven precedents · Five cases in data coordination
Construction bids from PDF solicitations
Every public bid arrives as a PDF with its own pay items, caps, and requirements. The pipeline keeps a fixed spine in code (intake, schemas, audit rules, gates) and leaves each job's judgment to agents. Forecasts are scored against published bid results, so the estimate improves with every letting.
Protocol Institute brand kit
A written brand spec that agents build pages from. It kept producing the same bugs until the kit gained shared components and automated checks. Brand kit
Your case study
Pick an organization you can see into: your own, a client's, or one whose records are public. Pick a data operation in it that AI is changing, or should change, and carry it for about a year from whenever you join, sharing progress in a session's show-and-tell.
- Choose. One paragraph on the organization and where the work gets stuck.
- Brief. One page on the context, the bottleneck, and how the work is done today.
- Intervene. Decide what becomes code, what is left to agents, and what stays with people, and what you will measure.
- Evidence. Run it, measure it, and note what surprised you.
- Publish. An open write-up, which feeds into the group's thesis.
Sample template
If a structure helps, the worked examples answer these questions. Find your own way if another shape fits your case better.
- Context: the organization and what the data is for.
- Bottleneck: where the work is actually stuck.
- Before: how data was found, checked, and trusted.
- Intervention: what became code, what went to agents, what stayed with people.
- Evidence: what you measured, and where the model was wrong.
- What transfers: what another domain could reuse.
To start, copy the sample template into case-studies/your-name/, or post your case in #protocols-for-business. You can keep a client anonymous.