Full Review

Filename convention: YYYY-MM-DD REGION Type.md (e.g. 2026-04-15 CA POS Check.md).

Pause template (use this, don't improvise)

After each phase, present output in this format. Keep it tight — the saved file is the artefact; the pause summary is only for decisions that need your input now.

✅ [Phase] saved to [path]

Top findings (max 3):
- [finding 1]
- [finding 2]
- [finding 3]

Before [next phase], any of these need correcting?
1. [specific question, max 4]
2. ...

Do NOT include a 10-bullet recap of the phase's content. If the user needs detail they will open the file.

Data freshness rules

• Always re-pull the Order Schedule xlsx at the start of the run. Never rely on a previous extract (even from today) — Greg updates POS MODEL daily, sometimes multiple times, and the 3PL tab updates separately.
• Always run Step 0a (Gmail reconcile) in the POS Check. A POS Check without a Gmail reconcile against the POS MODEL paste time is a guess.
• Flag manual overrides at the top of every phase output, with source of truth (user-confirmed / Gmail thread / Slack message).

Methodology discipline

• If you spot a methodology choice mid-draft (e.g. "this container uses 1.4x not 1.3x"), commit or skip — don't leave a dangling caveat. Either redo the affected math or don't raise it. Hedges are landmines for the reader.
• Manual overrides must cascade to every downstream calculation. Don't silently use sheet values after declaring an override.

Context Files (read once at start)

• Ops/Regions/$ARGUMENTS.md
• Ops/Context/Current Issues.md
• Ops/Context/Upcoming Orders.md
• Shared/Component Map.md
• Ops/Context/Deduction Benchmarks.md
• Ops/Context/Lead Times.md

Post-Review

After all three phases + pauses complete:

• Update Ops/Context/Current Issues.md with combined findings.
• Update Ops/Context/Upcoming Orders.md if container/order status changed.
• Note: "Full review done. Ready to check your Slack summary when you post it."