The deck that was shown,
and the notes that came with it.

A deck is a dated document. The handler reads slides, speaker notes, embedded tables and the deck’s own issue date, so what was presented to a board or a site meeting can be cited rather than recalled.

LLX-HANDLER-PPT · R2 · 4 formats

pptpptxodpkey
What it reads · 01 Structure level, not string level

Three things a slide export loses.

01

Slide text and order

Titles, bullets and the order they were shown in — the argument as it was put, not as it is remembered.

02

Speaker notes

Notes are read with the slide they belong to. They often say what the slide deliberately did not.

03

Embedded tables and charts

Tabular data inside a slide is read as data, so a figure shown on screen can be traced.

What it settles · 02 Where the handler earns its place

The questions a deck usually decides.

01

What a meeting was told

A statement is cited to its slide and to the deck’s issue date, not to someone’s recollection.

Chronology
02

Which version was presented

Two revisions of one deck are compared slide by slide, including the notes.

Version diff
03

Whether a risk was disclosed

Every mention of a risk across all decks is retrieved with its slide and date.

Disclosure
Custody

Read in place, in the format it arrived in.

The file is never converted or re-saved. It is read where it lies, and the handler records a SHA-512 of the bytes it read — so a passage cited today can be replayed against the same file years from now.

See it on your own decks All file formats