---
name: tbt-source-linked-visual-memo
description: "Keep visual hierarchy separate from evidential strength for Make a one-page visual memo from checked source facts. Use permitted source material; this kit does not authorise external actions."
---

# Make a one-page visual memo from checked source facts

Keep visual hierarchy separate from evidential strength.

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 visual memo answering [reader question] from these
checked source facts. Use a clear headline, source-backed points,
options/conditions and visible unknowns. Link every material claim to
a source ID and exact supporting passage. Keep proposal, approval and
completion states distinct. Use visual hierarchy for readability,
not to imply unsupported certainty. Provide editable file/source and
a readable text fallback. Do not invent costs, benefits or integration.

## Source boundaries

- Staging checked
- Production approval pending
- Sample check is limited

## Review and correction

Make visual labels traceable to their source conditions. Design should not promote a pending decision into completion.

The memo headline says [unsupported claim] while source [ID] says
[bounded fact]. Correct the headline, linked note and related visual
cue. Keep the useful one-page structure and unknowns. Do not invent
a new figure or approval to make the options look comparable.
Return the actual revised memo for source and layout review.

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.
