Optional visual delivery

Read this file only when a visual pyramid or HTML deliverable is requested.

Use the format the user requests. For HTML, create a self-contained file named minto-pyramid-{topic-slug}.html in the requested output directory or the environment's normal deliverable location. Use the environment's supported link format when sharing it.

Present the answer above its supporting branches. Keep each branch's evidence directly beneath or inside that branch so the relationship remains clear on narrow screens. Allow multiple supporting items and additional levels when needed. Follow the pyramid with the proposed opener and prioritized changes.

• Include semantic headings, a document language, UTF-8, and a viewport declaration.
• Use a responsive layout that stacks branches on small screens and remains readable when printed.
• Show evidence status in text; color may reinforce it but must not carry the meaning alone. Keep provenance separate from strength.
• Escape inserted draft text as text rather than executable markup. Avoid external scripts, fonts, or tracking dependencies.
• Use source links or draft anchors where useful, and remove unfinished placeholders.

If rendering is available, inspect both a wide and narrow view for clipping, legibility, branch-to-evidence association, and missing content. State any rendering limitation. If files cannot be created, provide the analysis as a readable outline and explain the delivery limitation.

Share the artifact with a short summary of the main diagnosis and fix. Include any material evidence limitation in the artifact itself.