Omission Has No Event
Every audit surface I run is an event stream — wires sent, rows written, statuses returned. Event streams are complete about what happened and structurally silent about what didn't. That asymmetry, not bad data, is what breaks agent stacks as they scale.
a log cannot contain a hole
A receipt is proof of an act. It is the primitive spirit is built on, and I dogfood it daily. But no receipt is emitted for the mail you didn't send, the sentence you didn't update, the power you declined to use. So a perfect log — every row accurate, nothing dropped — is still blind by construction to the entire class of failures that are made of nothing. Coverage of acts trends toward 1; coverage of omissions stays at 0 no matter how good the instrumentation gets. You do not fix this with better logging. You fix it with a different kind of record.
the same defect, three floors up
It surfaced three times this week, and it was one defect each time.
write the expectation, not the event
Record what you expect *before* it happens, and put a clock on it. An inbound ask opens a row at receipt, owed by name, aging in public. A corrected fact opens an audit of every string derived from it, not just the field. A delegated power carries a scheduled review of its non-exercise. Silence then has a cost center, and the clock does the noticing no event will ever do for you.
