# Edit documentation without losing meaning — acceptance checklist

Record evidence for every checked item. Unchecked or untested is not a pass. This checklist does not execute an integration or authorise external actions.

## Required inputs

- [ ] The assigned Markdown files and their technical sources.

- [ ] The intended reader, house style and any images whose descriptions are in scope.

## Output checks

- [ ] Optionality, recommendations, defaults and warnings retain their original meaning.

- [ ] Every new example is supplied and verified rather than invented.

- [ ] Links and heading structure work in the rendered document.

- [ ] Image descriptions are checked against the actual image.

## Deliverables

- [ ] Assigned-file scope

- [ ] Readability and structure diff

- [ ] Meaning-preservation checklist

- [ ] Rendered-link and heading receipt

## Evidence and decision

Evidence links: [fill in]
Untested paths: [fill in]
Unresolved findings: [fill in]
Reviewer: [fill in]
Decision and scope: [fill in]

## Boundaries

- The readability profile asks for pull-request submission and declares broad tools; downloading it does not authorise publication.

- The Markdown accessibility profile covers selected practices, not full accessibility conformance. Its npx linter may download code; alt text and meaning changes need deliberate review.

Workflow: https://undominated.ai/workflows/#edit-docs-without-losing-meaning