Documentation
Redlineo — user guide
Redlineo turns two versions of a document into a redline — a marked-up copy showing exactly what changed — and proves the result is correct and untampered. It runs on your own server; documents are processed in memory/temp files and deleted after the download, never stored.
| Guide | What it covers |
|---|---|
| Getting started | What the tool does, the three outputs, your first comparison. |
| The Compare page | Every control on the main page, step by step. |
| Understanding the outputs | Tracked vs. colored Word, the Excel review copy, the report page, "Changed content only". |
| Alfresco integration | Comparing document versions from Share, drafts vs. stored versions, saving results back. |
| The Classify page | Checking and sealing a single document: metadata extraction, assertions, scrub, integrity — content untouched. |
| Verify & Bake pages | Proving a produced file is authentic; flattening tracked changes into fixed colors. |
| REST API | Every endpoint, parameter and response header, with examples. |
The one idea behind everything
Every output this tool produces carries its own evidence — a runtime verification (✔ Verified), a SHA-256 certificate of exactly which inputs produced it, and a tamper-evident record inside the file. You never have to trust a redline; you can always check it.