A file you open is not a document you can audit. The difference is one reading on entry, and everything it puts on record.

The unit of your format

Slide, section, sheet, page

The screens and the agent use the unit of your format: slides, sections, sheets, pages.

slidepresentation
sectiondocument
sheetspreadsheet
pagePDF

One caveat for text documents: they are counted in pages but analyzed by section, and a section is a layout break. A document with no explicit break has one section, so its deep exam runs per document, not per page.

Photos of documents

Read on entry, never written back

A PNG or JPEG photo of a page, a receipt or a card uploads directly, and OCR reads its text as it arrives. A well-framed page reads nearly in full; a small or tilted card reads in part. Every reading carries its confidence, and a passage the engines did not confirm is marked as unconfirmed, so you know what to check against the photo. A photo is a source the agent can answer from, not a fifth format: it has no unit to translate or rewrite, and nothing is written back to it.

The X-ray, whole

One reading on entry, and every passage gets an address

SazAI Corpus reads the whole file once, by the format specification, without interpreting. The X-ray is what comes out.

text with origineach passage, the slide, and the shape it came from
comments with stateauthor, anchor, thread, resolved, with a task
notes and hiddenwhat the presenter was going to say, and what they hid
propertieswho created it, when it was revised, what changed

Each passage stays tied to the slide and shape it came from. Comments come with author, thread and state; notes come in full; hidden slides appear, marked as hidden. For audit, every statement in the document has an address in the file.

What the engine measured

A deck knows it is repeating itself before you do

The engine measures the whole document and stores the result under the lineage of that run. The signals have names:

near-identicalwithin a deck and across the twelve
title ≠ bodywhat it promises and what it says
will overflowthe box, once translated
mixed languageand a term spelled two different ways

The engine tells you two decks are nearly the same; what to do about it is a conversation with the agent. Measurements can be read across a whole portfolio.

Editions and comparison

Three relations declared before the first number

Every edition of yours, translation or revision, enters the vault as a complete document. Compare puts your original in the first column and declares the relation first: translation, revision, or independent. With no declared relation, no comparison appears.

your originalalways in the first column
the relation, declaredtranslation · revision · independent
the editiona complete document, with its own X-ray
Open the comparator

In a 45-slide edition: 633 elements before, 633 after. Counted, and kept per unit, so someone else can reopen it later without redoing the work.

Original and derivative stay linked

The relation survives the departure of whoever created it

When one document produces another, the link is recorded by the operation itself, and the derivative is read and measured like the original. An original and five translations are one document with five declared derivatives, not six files in a folder. Together the links draw the network your vault becomes.

What the receipt proves, and what it does not prove

Evidence of control, stated with its boundary alongside

The receipt proves that the operation happened, on which version, with which parameters, and what it changed: for a translation, completeness per segment, the glossary terms applied, and what made it into the file.

It does not prove the result looks right, because the system measures structure, not the final page. And it is not a certified audit: whether it meets a requirement in your sector is a case-by-case conversation. We do not ask you to trust the model; we show what happened to the file.

All of this lives in your vault, linked. The agent interprets it, reading the same vault you do.