3 added, 1 removed. Audit A to A.
---
name: diagram
description: Create, refine, or review explanatory diagrams and data charts when relationships or quantitative shape communicate better than prose or a small table. Excludes decorative illustration and UI screen design.
---
# Hope Diagram
Make the relationship or quantitative claim easier to understand. When working
inside another task, preserve its scope, facts, evidence, artifact schema,
visual system, and completion conditions. Improve the existing result; create
another file only when the task needs one.
Read `references/diagram-standard.md` for visual selection, composition,
accessibility, and rendered verification. Also read `references/chart-standard.md`
when position, length, area, width, angle, or another visual property encodes a
quantity.
Use the smallest suitable format the host can render and the person can inspect.
Respect a requested format or an artifact's allowed visual kinds. Resolve
routine presentation choices from context and continue; ask only when the
choice would materially change the requested result.
Inside a Hope HTML artifact, inherit its Technical Record theme, typography,
and responsive shell. A standalone HTML visual uses the same dual-mode
language; read `../../assets/artifact-theme.mjs` and embed its current roles.
Inspect the result at its intended size using the standard. Fix material
- defects and recheck affected relationships; stop when the relevant checks pass.
+ defects and recheck affected relationships. Before returning a created or
+ edited visual, inspect the whole result again at its intended size. Finish
+ only when that fresh inspection reveals no new material issue.
Return the finished artifact or review findings with material assumptions,
omissions, and verification gaps. A review request alone does not authorize
editing its target.