---
name: fractal-reports
description: "Compose Axon HTML summaries, scientific reports, and evidence briefs from source material. Use for report layout and linked evidence, not generic product pages or slide decks."
---

# Compose an evidence report

Read [core](../../../../core.md), [interface direction](../../../product-ui/references/interface.md), [typography](../../../product-ui/references/typography.md), [report composition](../../references/composition.md), [device palette](../../references/devices.md), and [component selection](../../../product-ui/references/components/selection.md); use bundle `summary-report`.

1. Identify the reader's task: sustained reading, comparing peers, following a sequence, interpreting distributions, or looking up one entity. Inventory source claims, figures, caveats, and resources.
2. Preserve each figure's scientific information. A summary table cannot replace a distribution/trend/uncertainty view that carries different evidence. Retain source imagery when underlying data is unavailable; disclose any supported approximation.
3. Choose the primary content device, then shape page width and surrounding material around it. Avoid a fixed masthead/KPI/sidebar shell. The device palette and archetypes are examples, not templates or factual input.
4. Keep related summary content together. Add a stat strip only when its values earn a separate overview. Use neutral flat surfaces, coherent section grids, restrained dividers, and shared alignment.
5. Add navigation or cross-linked interactions only when useful. A clickable-looking rail must actually navigate, reveal, or locate content. Preserve keyboard parity and keep essential information available without hover.
6. Keep wide content inside its own scroll region. Check actual overflow instead of relying only on clipping CSS.

Load [visualization](../../../data-visualization/skills/fractal-data-visualization/SKILL.md) for charts, [color](../../../product-ui/references/color.md) for UI/status colors, [icons](../../../product-ui/skills/fractal-icons/SKILL.md) for icons, and [motion](../../../product-ui/references/motion.md) for animated interactions. Chart palettes and scientific element colors remain separate from page-level accents.

Use `fractal-ui` when the target supports React; standalone HTML uses semantic elements and the same design rules without pretending React components are installed. Verify content fidelity, actual links, final rendering, responsive reading order, accessible interactions, and chart-specific checks.
