17 Check generated text line by line

What people usually ask

Write a one page description of our test lab's capabilities. We do tensile testing, hardness, salt spray and some wet chemistry.

What comes back

A fluent page that quotes accuracies nobody measured and names a thermal analysis instrument the lab does not own. One sentence promises a turnaround nobody would say to a customer.

Ask this instead

Write a one page description of our test lab's capabilities for customers, from the two attached files only: instruments.txt (one instrument per line, with its range and resolution) and scope.pdf (our accreditation scope).

- End every sentence with the line number in instruments.txt it rests on, like [L12], or [scope p.3] when it rests on the scope.
- No number that is not in the files. No accuracy, uncertainty or turnaround figure unless a line gives it.
- Where a description like this would normally add something the files do not give (sample sizes, lead times, uncertainty), write [gap] in its place and leave it.
- Say nothing about accreditation beyond what scope.pdf states, and quote the scope wording where you use it.
- Plain sentences. No adjectives about quality, no closing paragraph.
Every untagged sentence, and every tag that does not hold up, will be deleted.

Attach: instruments.txt with ranges and resolutions, and the accreditation scope PDF.

Why it works: every sentence carries the line it came from, so checking is a lookup and a sentence with no line to point at stands out at once.