Verify & Bake

The Verify and Bake pages

Verify — prove a produced file is authentic

Drop any file this tool produced (Word redline or Excel copy) on the Verify page (/verify). Everything is recomputed from the uploaded bytes — no database, no lookup; the file proves itself:

• Integrity — every part of the file is re-hashed and checked against the manifest embedded at generation time (pleodox/integrity.json).
  • ok: unaltered since generation.
  • failed: something was modified after generation (the failing parts are named).
  • missing: not a file this tool produced (or the manifest was stripped).
• Origin — when your server is configured with a signing secret, the manifest carries an HMAC only servers holding that secret can produce.
  • ok: produced by this server (or one sharing its secret).
  • failed: the manifest is self-consistent but not ours — a look-alike.
  • unsigned / not-configured: no signature to check (the server doesn't sign, or the file predates signing) — integrity still stands on its own.
• Certificate data — the embedded change-set and filing-metadata records and the file's own SHA-256, so you can see what the comparison claimed and tie the file to its inputs.

Use it when a stored redline resurfaces in an audit, a dispute, or an objection exchange: one drop answers "is this the real, unmodified artifact?"

Bake — flatten an existing tracked-changes document

The Bake page (/bake) takes a single .docx that already contains tracked changes (from Word, from this tool, from anywhere) and flattens the marks into fixed colors: insertions underlined, deletions struck through, in the two colors you pick. Use it when the recipient shouldn't (or can't) interact with revisions — e-mail attachments, PDF conversion, printing.

• Change report (optional): prepends a "Tracked-changes report" page listing every change with its original Word author — the only place that attribution survives once the marks are baked away. The report lines are clickable and the page carries the color key.
• Verify (on by default): checks that the baked text contains every inserted and deleted character of the original marks — nothing lost in the flattening.
• The result carries the same proof stack as a comparison output (embedded change-set, integrity manifest) and can be checked on the Verify page.