Prepare a source packet an AI teammate can use

A source packet should tell the tool what is authoritative and what is only background. Resolve conflicts explicitly instead of relying on filenames such as final-new.

Work through these checks

1. Inventory

list each file and its purpose. Record the evidence or the unresolved question before moving on.

2. Authority

state which source wins on conflicts. Record the evidence or the unresolved question before moving on.

3. Scope

include dates, audience and exclusions. Record the evidence or the unresolved question before moving on.

4. Gaps

identify missing information the tool must not invent. Record the evidence or the unresolved question before moving on.

5. Privacy

remove unrelated sensitive material. Record the evidence or the unresolved question before moving on.

Put the checklist to work

If an old catalog conflicts with approved-prices.csv, name the price file as authoritative and use the catalog only for descriptions.

Keep the checklist beside the task brief and the actual output. Mark a check complete only after inspecting the relevant file, setting or event. If a required check cannot run in the current environment, describe that gap and choose an appropriate next review rather than substituting a confident summary.

A boundary to remember

An attachment list alone does not explain the relationship between the files.

For the corresponding controls and troubleshooting steps, read the desktop help guide. These checks are a practical review aid; adapt them to the specific source material and intended use of your deliverable.