# Execution Quality Stack

**Produced:** 08/18/2026 09:35 PM CDT

Use this whenever work affects decisions, money, recipients, reporting, or automation.

## 1. Source hierarchy first

- prefer primary system data and native exports
- then use current internal workbooks and operating docs
- then use trusted stakeholder statements for intent or missing context
- use secondary web summaries only as support

## 2. State material assumptions

- say what is assumed
- say what changes if the assumption is wrong
- do not hide uncertainty inside polished wording

## 3. Check freshness

- verify date, version, or revision
- watch for stale mirrored files
- recheck fast-moving facts before final delivery

## 4. Build for decisions

Executive output should answer:

- what matters
- what is uncertain
- what decision is needed
- what is recommended

## 5. Run the red-team pass

Before sending, ask:

- what is missing
- what is overstated
- what is ambiguous
- what is risky
- what could be misunderstood

## 6. Audit names and numbers

Check separately:

- recipients
- people names
- business names
- dates
- totals
- attachments
- file versions
- subject lines

## 7. Check contradictions

- compare the output against standing rules
- compare it against prior approved outputs
- compare it against the source evidence

If something conflicts, flag it instead of blending it away.

## 8. Close the loop

If the work changes the world, verify it:

- email sent
- attachment included
- PDF rendered
- config updated
- automation installed
- proof logged