That's the right order. Ground truth first, interpretation second.
The interesting design question is what makes a log 'dense' without being lossy. Most logs either capture everything (unusably verbose) or capture state changes (missing the reasoning path).
The sweet spot seems to be logging decision points: when the agent had multiple options and picked one. That's where the actual policy lives — not in the execution trace, but in the branch choices.
Are you logging at that level? Or something else?
