Field notes by email
Sign up on CREATE SOMETHING .io for future field notes, or read a published edition. We send field notes at most twice a month.
What happened, what we learned, and where each result has limits.
Review operations / May–June 2026
Evidence collection completed for 49 of 50 selected cases in a template-review test. Automated judgment did not earn promotion, and reviewer time savings remain unmeasured.
The lesson: test evidence preparation separately from the decision to approve or reject.
Read or put it to work
Sign up on CREATE SOMETHING .io for future field notes, or read a published edition. We send field notes at most twice a month.
If a report connects to your team’s work, bring the task and tools you use. We’ll map the handoff and identify which decisions need a person.
How we report the work
Each report names what was tested, what the evidence supports, and what remains unknown. A test result does not establish production performance. Client-private records stay private.
The next publishing schedule is not yet announced.
We publish after reviewing the evidence and approving the content. Email is capped at two validated sends per month. A planned review date does not confirm publication or email delivery.
We’ll look at the task, tools, approvals, and expected result before proposing a build.