breachlisted

# Quick Page Fast, single-page HTML artifacts for daily dev communication. ## Output Boundary breach owns HTML and deterministic discussion-digest rendering only. - Native document, presentation, or spreadsheet requested → use the requested OpenAI Template or native artifact capability. - HTML page, HTML slide-like page, or discussion digest requested → use breach. - Another workflow may define content and evidence first, then call breach only for HTML presentation. ## Core Rule Speed first, polish follows. A good-enough page in 30 seconds beats a perfect page in 5 minutes. Choose one mode: - **General page** — use html-effectiveness for layout and DESIGN.md sources for visual tokens. - **Discussion digest** — use the bundled schema, renderer, and template. Do not run the generic layout/style selection because this mode is deterministic. ## Optional Chart Renderer In General page mode, `lieflat-charts` may render a chart module inside the page. Breach still owns page integration and chart placement; `paperwork` owns the surrounding narrative. Use it only when all are true: - the input contains real quantitative data or an honest relationship graph; - a chart carries an independent conclusion better than prose, cards, or a table; - the visual encoding does not require invented scores, weights, or benchmarks; - the artifact's use is compatible with the renderer's license. Keep this route small: normally 1–3 charts, each with a distinct conclusion. Do not chart