Series

Field guide

For when a number is not yet evidence.

Statistics Field Guide

Start here when a dashboard, model score, trend line, or anomaly looks persuasive and you need to know what it can actually support. The guide turns statistical methods into concrete questions: what changed, what broke, what leaked, what will be new in use, and what decision the evidence is allowed to move.

Editorial on-rampThe Question Before the NumberMost statistical failures begin before the calculation.

• How to read diagnostics
• Foundations for unfamiliar data
• Time, cadence, and sampling pressure
• Model changing vectors, variance, states, regimes, and events
• Censoring, survival, and remaining-life decisions
• Data leakage before it becomes confidence
• Build and evaluate a model
• Why the model includes the evaluation protocol

Open the field guide

Full sequence available

For when bytes look more authoritative than they are.

Reading Machine Buses

Read this when a trace, capture, or register-looking payload starts to feel more certain than it is. The series walks from raw bus artifacts to bounded claims: fields, timing, authority, observer position, silence, and the line between evidence and operation.

Start with the boundaryA Bus Artifact Is Not the SystemSeparate observation, authority, inference, and claim before the bytes become a story.

• A Bus Artifact Is Not the System
• Classical CAN: Frames Without a Story
• DBC: Where Signals Get Their Authority
• UART: Timing Is Part of the Evidence
• Signals: evidence and diagnostics

Open the bus-reading series

9 of 9 live

For when source code stops explaining the program.

Application Binary Interface (ABI) Series

Read this when an ordinary-looking call crosses a language, platform, hook, tracer, or FFI boundary and starts behaving like a packet format. The series follows the hidden fields, register roles, stack contracts, unwind metadata, and hardening rules that make the source signature only the cover story.

Best first specimenThe Bugs That Make ABI Rules MemorableMalformed call packets make the boundary visible.

• Why the function signature is a lie
• The bug zoo
• Calls as a security surface
• Trace hidden result storage in the lab

Open the ABI series