# Word documents — the brief, the fixture and the scoring

Sent as one message with `policy-draft.docx` attached through each tool's own upload, free tier, fresh chat (Claude: incognito). If a tool cannot take a .docx, the text is pasted and that is noted; if it cannot return a .docx, whatever it returns is scored as delivered and the "file" column says no.

> Attached is our shipping and returns policy, a rough draft in Word. Please turn it into a clean, properly formatted Word document: real heading styles with the sections numbered consistently, the shipping rates as a proper table, a table of contents at the top, the spelling mistakes fixed, and anything duplicated removed. Keep the policy itself exactly as it is - do not change any amounts, days or rules. Send it back as a .docx.

## The fixture

`policy-draft.docx`, made by `make_fixture.py`: a 570-word policy for the fictional shop typed as 25 plain paragraphs - no heading styles, the section labels numbered four different ways, the rates table as tab-separated lines, eight spelling mistakes, one paragraph pasted twice, a date in two formats. `ground-truth.md` lists every planted fault and the twelve facts that must survive.

## Scoring

- **File** - a .docx comes back and opens. A rendered preview, a Google Doc link or a Markdown block is not a Word document; recorded, scored as no file.
- **Headings** - paragraphs in Heading styles, of 8, and whether they are numbered one way.
- **Table** - a real Word table for the rates, 5 × 4, with all 12 prices intact.
- **TOC** - a table-of-contents field, or a Contents list; which one.
- **Spelling** - of the 8 planted mistakes, how many remain.
- **Duplicate** - the pasted-twice paragraph gone.
- **Facts** - of the 12, how many survive unchanged. **Invented** - anything the draft does not say.
- Time, refusals, output form, whether the file was made with code the tool ran or by its own document feature.

`check_docx.py` runs the structural checks on a returned file with python-docx.