skills/business-analysis/references/visual-output.md

# Faithful visual output

Derive the visual from the completed analysis. Preserve the thesis, causal mechanism, evidence distinctions, counterargument, and decision; do not introduce new conclusions in the visual.

Choose the representation that explains the system: a bottleneck cascade, value-chain map, flywheel, moat stack, comparison table, or multi-panel executive brief. Do not add a panel merely to meet a template count. Any score must retain its definition, basis, and uncertainty.

Use a white editorial background with teal `#0d7377`, light teal `#14a3a8`, dark `#1a1a2e`, gray `#6c757d`, and selective red `#c41e3a` or gold `#d4a017`. Keep text readable and the result usable on mobile. The existing Atlas has its own dark visual system; preserve that when exporting it.

The optional plugin asset `assets/business-analysis-template.html` is an earlier layout example, not analytical evidence. Copy or adapt only relevant structure; replace example copy, numbers, scores, citations, and placeholders. A new HTML artifact can also be authored directly. Keep source links near the claims they support and include attribution to The Business Engineer · Gennaro Cuofano.

Use a self-contained HTML file by default for a substantial analysis. Read it back, check embedded script syntax where applicable, and use the host environment's artifact delivery and persistence workflow. Use document, presentation, chart, or site capabilities when the user requests those formats. Do not create a site deployment merely to deliver an analysis file.