thorne-document-forgery — contract authenticity dispute
Disputed signed contract package where the PDF shows post-signature incremental edits, Word drafts carry conflicting author/template genealogy, and legacy .doc residue exposes ghost payment text. Fully synthetic.
what this proves
- all eight document-forgery primary engines produce deterministic, fixture-locked output — verified by
npm run check:flagship(96/96 fleet · 8 for this scenario). - every output is generated 100% locally in your browser — preserve originals, never upload contract bytes.
- post-signature incremental edits, signature byte-range drift, DOCX metadata genealogy mismatch, tracked wire-transfer deletions, and legacy OLE ghost text surface without sending evidence to a server.
primary engines locked to this fixture
build the case binder
runs all eight primary engines on the synthetic evidence zip and opens a self-contained html binder. uses the default binder renderer for document forgery — no upload.
runs all 8 primary engines locally on the synthetic evidence zip · opens a self-contained html binder · no upload
download the synthetic evidence
MIT-licensed, fully synthetic. includes signed incremental PDF, tracked draft DOCX, clean export DOCX, and legacy OLE .doc with recoverable ghost text.
built deterministically from scripts/fixtures/build-thorne-document-forgery.mjs. seed: thorne-document-forgery:v1.
methodology
document forgery is multi-file — hash the disputed PDF first, then walk object explorer → incremental updates → signature byte-range → metadata genealogy across DOCX branches → tracked changes → ghost text in legacy .doc. read the full document forgery / disputed authenticity guide →
after the playbook
run each primary locally — or export findings from the binder — then drop every csv/json into fatcousin-multi-tool-super-timeline-correlator. one timestamp-sorted timeline across incremental PDF edits, signature byte-range conflict, and draft genealogy — still zero upload.