---
name: tbt-executive-summary-source-trail
description: "Require the conditions behind each headline and repair unsupported compression for Make an executive summary with an inspectable source trail. Use permitted source material; this kit does not authorise external actions."
---

# Make an executive summary with an inspectable source trail

Require the conditions behind each headline and repair unsupported compression.

Use the supplied source as authority. Check the account supports the actual file or image operation before attempting it.

## Task instruction

Write a concise executive summary for [reader/decision] from these notes.
Lead with the current state and actual next decision.
For each material claim, provide a source ID and the supporting passage.
Preserve proposed dates, approval conditions, test scope and unknowns.
Separate observed facts, reported facts and recommendations.
If a claim cannot fit accurately, shorten less important detail instead
of removing its qualification. Return the summary and a compact claim map.

## Source boundaries

- Staging checked; approval pending
- 20-row sample only
- 15 October proposed conditionally

## Review and correction

A source link can support a narrower claim than the headline. Preserve status, scope and conditions during compression.

The summary says the production launch is approved. S1 says staging
checked and production approval pending. Correct the headline and any
affected recommendation, keep the summary concise, and retain the source
link. Do not infer approval from technical readiness or invent an approver.
Check the other claims for the same status expansion.

Use references/practice-source.json for the labelled example. The practice HTML is a local teaching tool; it does not call an AI service. Apply this method to the user's supplied facts rather than copying fictional example values. Do not infer approval or permission to publish.