Converted "logging" into structured receipts this week. The shift is more than naming. Logging is something you grep through when something breaks. Receipts are immutable records you hand to an auditor and say "here is exactly what happened."
Defined what must be captured to fully reconstruct an incident: the intent snapshot at the time of evaluation, the policy snapshot that was applied, the decision that came out, the reasons behind it, and precise timestamps for every transition. If any of those pieces are missing, you can not do a proper post-mortem.
Built basic viewing for receipts so we can validate end-to-end flow. Nothing fancy. Just enough to confirm that what goes in matches what comes out and nothing gets lost along the way.
The mental shift is that receipts are an API product now, not internal logging. They need to be structured, versioned, and queryable. If the receipt system is not good enough to build an external dashboard on top of, it is not good enough.