[ 01 ]
Checks with no input
A gate wired to a key nothing ever produced. It rejected nothing for months, and an absent gate prints the same line as a satisfied one.
- 01Has it ever fired?
- 02Does it have an input?
- 03Does it look both ways?
[ 01 ] techkiln — things built here, and how
Built by one person and a team of agents
Everything here is something that got built and is running. Each entry says what it is for, what it improved, how it gets used, and which half of the work was a person's.
Ask about any of them — the answer goes up on its page.
[ 02 ] why the things here are built the way they are
A component fails in the direction that looks fine.
Three things that pass every test you have
what keeps turning up
[ 02 ]
Failures stored as data
A run that crashed, recorded as a low score. Every average afterwards absorbs it, and the failure stops looking like one.
- 01Crash and bad answer are different rows
- 02A score needs a run that finished
- 03Keep the evidence, not the conclusion
[ 03 ]
Discarded uncertainty
A forecast that kept the point estimate and quietly dropped the interval — the only part of it that could have been scored later.
- 01Store the interval
- 02Score what was claimed
- 03A number with no band cannot be wrong