Most technical writing tells you how to do something, and rarely says why this particular boundary, what it protects, or under what conditions it should be revisited.Boundary Notes is an attempt at that second half.
Most of what I build sits close to hard constraints: real-time speech on CPU alone, observable event pipelines, and a balance between latency and false triggers reached through policy rather than one magic threshold. Writing the trade-offs down is how I avoid forgetting why they were made.