What problem does it solve? Legal teams review contract redlines in markdown, but opposing counsel expects a Word file with native tracked changes and proper reviewer attribution. Manually converting markdown edits into Word revision marks is error-prone and risks leaking internal notes or misattributing authorship. ## Core Features & Use Cases - Tracked-Changes Conversion: Maps markdown redline entries (strikethroughs, bold insertions, WHY/FALLBACK annotations) to Word-native <w:ins>, <w:del>, and <w:comment> OOXML revisions using python-docx plus direct XML manipulation. - External/Internal Modes: External mode strips work-product headers, severity markers, and escalation references before sending to opposing counsel; internal mode preserves them and adds an INTERNAL DRAFT footer. - Reviewer Attribution & Cover Memo: Embeds confirmed reviewer name and email in revision metadata and generates a plain-text cover memo summarizing key positions for the outbound email. - Use Case: After running a contract redline on an MSA in markdown, convert it into a reviewer-ready .docx attributed to your GC, with fallback positions shown as comments, ready to email to opposing counsel. ## Quick Start Convert my markdown redline at redlines/acme-msa.md into a tracked-changes Word document in external mode attributed to Jane Smith.
