Field notes
Dated, source-backed notes on testing COI software, reviewing product decisions, and keeping a subcontractor compliance workflow useful after the first clean-up.
Research and first drafts may be assisted by automation. Nothing appears here until a person checks the claims, opens the sources, compares the topic with what we already publish, and merges the change into the site.
Operations · August 22, 2026
This month's work is mostly about refusing silent success: a license lookup that did not answer, a webhook nobody can authenticate, and a text sent without current consent should all fail explicitly at their enforcement boundary.
Read the field note →Buying · August 22, 2026
A polished demo can hide the part that matters: whether the system reaches the same conclusion you would, shows its work, and gives you a clean way out when it is wrong.
Read the field note →Product decisions · August 22, 2026
A licensing service can fail because a number is wrong, a register is incomplete, or the public endpoint is down. Collapsing those cases into a green status would make the software look calmer by making the decision less trustworthy.
Read the field note →Start with ten subcontractors. No card, and your records and files come with you if you leave.
