Reading the record
What each section of the output is for.
The logging design pack has four parts, each answering a different question about the system you described.
The readiness call
Whether the described use puts you in Art. 26(6) logging territory, stated plainly with the article cited.
The events list
What to capture, per the rules the tool ships — the events that make a decision reconstructable, not everything the system happens to emit.
The retention and control gaps
What is missing today: an unset retention period, an unreadable log, an unrecorded review. The gap list is the useful part.
The record
The exportable pack: system facts, events, gaps, and date. Re-run it when the system changes; a logging design is a dated artefact.
Decision-support drafting only — not legal advice. Confirm the duty set against the current consolidated text of Regulation (EU) 2024/1689.