---
name: tbt-source-led-visual-explanation
description: "Keep numbers and relationships in code or editable text rather than asking pixels to invent them for Build a source-led visual explanation instead of a decorative infographic. Use permitted source material; this kit does not authorise external actions."
---

# Build a source-led visual explanation instead of a decorative infographic

Keep numbers and relationships in code or editable text rather than asking pixels to invent them.

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

## Task instruction

Explain [reader question] visually using only these supplied source facts.
First write the factual conclusion and its limits. Map each proposed
visual element, value and label to a source ID or explicit calculation.
Keep denominator, period, missing data and sample scope visible.
Do not invent causes, benchmarks, outcomes or company-wide conclusions.
Choose a native chart/diagram/layout where it preserves exact facts.
Provide a readable text/table explanation with the actual output.

## Source boundaries

- 24 reviewed requests
- 18 fields present
- 6 missing

## Review and correction

75% describes the 24 reviewed requests. It does not establish company readiness or why fields were missing.

The visual labels [claim] but source [ID] establishes only [bounded fact].
Correct the title, denominator and related graphic labels. Keep the
useful visual mechanism and exact source values. Preserve the scope
qualification and text/table fallback. Do not add a new unsupported
claim to make the infographic feel more conclusive.

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.