عربي
DAY 03 · EVIDENCE

Build a brief that can be challenged

A useful executive brief shows its sources, assumptions, gaps, and dissent. The goal is not polished authority; it is a reviewable input to human judgment.

SELF-PACEDSOURCE PACKREVIEWED 31 AUG 2026

Use an approved environment and an approved, redacted source pack. Do not paste confidential board papers, privileged legal material, employee records, customer data, credentials, unpublished financials, or vendor-confidential documents. Confirm rights, lawful basis, retention, and access before processing any real material.

Any production implementation additionally requires approved redacted inputs, rights and lawful basis, data minimization, least privilege, tenant separation, managed secrets, audit logs, representative, adversarial, and regression evaluations, proposal-only behavior, human approval, monitoring, a stop condition, an incident path, and tested rollback.

The EXEC brief contract

EEvidence: enumerate permitted sources, dates, owners, and what each source actually supports.
XeXclusions: state prohibited data, out-of-scope questions, and claims the source pack cannot answer.
EEvaluation: request counter-arguments, uncertainty, missing evidence, and an abstention path.
CControl: keep outputs as proposals with named reviewers, approval criteria, and rollback.

Separate the layers

Fact

A bounded claim linked to a permitted source and date. Reviewers should be able to open the source and locate support.

Inference

An interpretation explicitly tied to facts, assumptions, confidence, alternatives, and possible disconfirming evidence.

Proposal

A reversible option with dependencies, risks, owner, decision gate, measurement plan, stop condition, and no automatic execution.

Fact: the fictional dataset records a higher return count for one synthetic category in the latest period. Inference: fit guidance may be contributing, but channel mix is an alternative explanation. Proposal: run a controlled content test after analytics and merchandising owners validate the data. This wording avoids turning correlation into a causal claim.

Prompt for a reviewable draft

Decision question: [bounded question] Audience and decision owner: [roles] Permitted source pack: [source IDs, titles, dates] Prohibited material: personal data, secrets, privileged or unlicensed content, and anything outside this pack. Rules: 1. Use only the source pack. Attach a source ID to every factual claim. 2. If support is absent or conflicting, write “insufficient evidence.” 3. Separate FACTS, INFERENCES, and PROPOSALS. 4. For every inference, show assumptions, uncertainty, counter-evidence, and what would change the view. 5. For every proposal, include owner, dependencies, affected groups, risks, approval, reversible test, monitoring, stop condition, and rollback. 6. Do not make employment, legal, financial, customer-eligibility, pricing, or public-claim decisions. 7. End with a verification queue for named human reviewers.

Review before circulation

Instructions to sound certain or imitate a famous consultancy can suppress useful uncertainty and invite misleading authority. Specify evidence and decision requirements instead. A polished unsupported answer is a failed brief.

Completion gate

The brief is ready for review when

Prompt features change. Check current official guidance such as OpenAI prompt engineering and Anthropic prompt engineering, then validate the complete workflow with representative and adversarial evaluations.

← Day 2: EvaluateDay 4: Market intelligence →