Decisions
The reasoning, not just the result
2026
- CAN-103postmortem
A draft gate that looked like an environment check and was not one
Draft library articles were invisible on the preview channel — the one deployment where a draft is actually useful — and visible only under `next dev`.
- SEC-113decision
Shipping the method to the browser IS the privacy guarantee
The payload washer runs client-side, so its entire rule set — every pattern, the word lists, the policy matrix — is delivered to every visitor. Can the quality of those rules be treated as proprietary?
- UX-109decision
A true argument on the wrong axis: cost is not readiness
A tool that makes zero network calls costs nothing to serve. Is that sufficient grounds to promote it to the production surface?
- WASH-107bdecision
Provider and facility identity is kept, permanently — and saying so is the control
The payload washer replaces patient identity with synthetic equivalents. Should it do the same to practitioners, organizations and facilities?
- WASH-110decision
Most of a compliance method is the wrong amount to implement
One geography mode keeps the first three digits of a US postal code. The published de-identification method it resembles additionally requires that the small number of low-population three-digit prefixes be zeroed. The list is static, short and cheap to implement. Should it be?