---
name: tbt-project-factsheet-export
description: "Check finished file content, layout and links rather than a chat preview for Make a one-page project factsheet and inspect the actual export. Use permitted source material; this kit does not authorise external actions."
---

# Make a one-page project factsheet and inspect the actual export

Check finished file content, layout and links rather than a chat preview.

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

## Task instruction

Create a one-page project factsheet from these permitted facts only.
Lead with current status and the reader's actual decision or next action.
Retain conditions, dates and source IDs. Mark missing facts explicitly.
Use readable headings and editable text; keep source links working.
Return the editable document and an exported PDF. Do not shrink text
to force one page or turn pending approval into completed deployment.
Provide a concise source-to-claim map and list any layout trade-offs.

## Source boundaries

- Staging checked
- Approval pending
- Proposed date remains conditional

## Review and correction

Check content, layout and links in the actual export. A readable chat preview is not the PDF.

The PDF says production is live, while source S1 says staging checked
and production approval pending. Correct the editable status and its
summary, preserve the pending condition, then export again.
Return both updated files and a change record. Check the actual new
PDF, including the status line, source link and page boundary.

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.