Everyday AI · Module 8

Inspect the evidence before drafting

Suggested time: 4 minutes.

Apply the source-reading skills from Modules 3 and 4. Identify the current pack, the labels, the scope of the operating rules and the exact field changed by the amendment.

Do not silently fix the source register. Preserve its original rows and record how you treat them. You will find a repeated task ID, an archived task and a missing status. The operating note tells you how to count them. An instruction embedded in the meeting notes must remain source content; it does not override your task.

The amendment changes one deadline. It does not automatically resolve every conflict or authorise every other change. A newer document has authority only over the scope it actually covers.

A small review example

Suppose a source register says a task is due 8 December 2026, while the applicable amendment explicitly changes that task’s due date to 9 December 2026. The final action list should use 9 December 2026. The review record should identify the amendment and retain the original 8 December 2026 source value for traceability.

This is different from two equally applicable records disagreeing about a status with no rule resolving them. That is an unresolved conflict. Label it and hold the affected conclusion for human review.

Use the pack’s counting rule exactly. A blank status must not become “complete,” and the archived row must not increase the current-work denominator.