# Execution Quality Stack

Use this when a request affects decisions, reporting, external communication, automation, or anything likely to be reused.

## 1. Source Hierarchy

- Prefer primary system data, native exports, official platform docs, and authoritative current workbooks first.
- Use stakeholder statements for direction, intent, or missing context, but do not silently treat them as system truth when a better source exists.
- Use secondary web summaries only as supporting material, not as the final authority.

## 2. Assumption Logging

- State any material assumption in plain English.
- Say what would change if the assumption is wrong.
- Do not hide uncertainty inside polished wording.

## 3. Freshness Check

- Confirm date, revision, version, or last-updated signal on time-sensitive sources.
- Watch for stale mirrored files when a newer authoritative source may exist.
- Recheck fast-moving topics before final delivery.

## 4. Build for Decisions

For executive-facing output, do not stop at facts. Translate them into:

- What matters
- What is uncertain
- What decision is needed
- What is recommended

## 5. Pre-Send Red-Team Pass

Before sending or publishing, ask:

- What is missing?
- What is overstated?
- What is ambiguous?
- What could be misunderstood?
- What creates avoidable business, security, or reputational risk?

## 6. Numbers and Names Audit

Run a separate verification pass on:

- Totals
- Dates
- Recipients
- Attachments
- File versions
- Property names
- Person names
- Subject lines

These fail more often than strategy.

## 7. Contradiction Check

- Compare the request against standing rules, prior outputs, and source evidence.
- If something conflicts, flag it explicitly rather than averaging the conflict away.

## 8. Closed-Loop Verification

If work changes the world, verify it.

- Email sent
- Attachment included
- PDF rendered
- Automation installed
- Cron scheduled
- Config updated
- Proof logged

## 9. Reuse

- When a workflow repeats, convert the good version into a documented standard instead of rebuilding it from scratch.
- Keep improvements in workspace docs, memory, or approved skills so quality survives resets.

## Quick Use Checklist

- Best available source confirmed
- Material assumptions stated
- Freshness checked
- Decision framing included
- Red-team pass completed
- Names and numbers audited
- Contradictions checked
- Action verified after execution