HTML Artifacts

Emit a single self-contained .html file when markdown can't carry the content. Default everywhere else stays markdown.

When YES

Use HTML for outputs where structure or interactivity is load-bearing:

Comparisons with ≥3 axes (options × criteria × tradeoffs) that benefit from sortable / filterable tables.
Complex plans that need navigation, a decision surface, or a clickable map. Simple linear plans stay markdown.
Code reviews with annotated diffs, module maps, or call/data-flow graphs.
Visual explanations where a timeline, process flow, architecture/system map, ERD-style relationship view, concept map, or infographic makes relationships clearer than prose.
Long-work status snapshots with exact counts, validation matrices, decision logs, and "what's next" surfaces. See references/status-snapshot.md.
Throwaway tools (interactive editors) — drag-drop, sliders, live filters — where the user manipulates inputs and exports a decision. See references/interactive-editor.md.
SVG-flow explainers where ASCII or markdown lists lose the spatial relationship.

Stay in markdown for: