Can generated material include outdated copies of an otherwise correct policy?

**Does every generated document need to agree with the latest policy?**

No. A release can deliberately include operational copies that have fallen behind. The inconsistency should be part of the task design, with enough information to determine what needs correction.

**Which artefacts can carry the inconsistency?**

In healthcare administration, a booking policy may change the required referral information while a reception script, printable form and reminder template retain different parts of the old requirement. The authoritative policy can be internally consistent even though its operational copies are not.

**How can a buyer distinguish useful inconsistency from generation errors?**

Ask for a separate defect manifest that identifies intended stale passages, their controlling source and the expected repair boundary. Keep that manifest outside the agent's input when detection is being evaluated. Unlisted contradictions should be reviewed as potential quality defects rather than treated automatically as extra challenge.

**Can the task include repair?**

Yes. A task pack could ask the model to propose a corrected script while preserving unaffected wording and local instructions. That makes the target behaviour precise: repair the outdated requirement without introducing unrelated changes or erasing context that remains valid.