ork-glyph

# Ork Glyph Render immediately from the user's topic. With no topic, use the current conversation. Choose the form yourself without setup questions, task creation, or subagents. The inline rendering itself needs no external tools. Encode information in structure. State the verdict in one prose line, then draw one render in a monospace code block. Follow it with two or three short observations when the diagram reveals something worth explaining. ## Choose the form | Data shape | Render | |---|---| | Inventory, audit, budget | Header meter, sections, rows, totals, caveats | | Status, progress, health | Status box and bar meters | | Options, trade-offs | Comparison table | | Steps, pipeline, handoffs | Flow with arrows | | Containment, layers | Nested boxes or tree | | Ranking, scores, counts | Table and bars | | Change over time | Sparkline or milestone track | ## Rendering contract - One render per reply, at most about 50 lines. In a terminal, keep each line within 76 display cells. In chat, web transcripts, and other non-TTY surfaces, use at most 72 cells and one narrow table or a vertical list, never side-by-side boards. Default to the non-TTY layout when the surface is uncertain. - Use one box style per render: `┌─┐│└─┘` normally, `╭─╮│╰─╯` for soft status cards, or `+-|` for ASCII-only surfaces. Keep nesting to three levels. Use arrows `→`, `↓`, or `->` and meters `▓▓▓░░` with the numeric value beside them. - Pair every status icon with a word: ✅ done, ❌ fa...