POM terminal UI
Surface hierarchy
- status line: stage, progress, gate/blocker, Hive, approval, retry
- HUD widget: persistent contract, evidence, blockers, active work
- working message: exact current semantic phase
- custom cards: validation, Hive, milestones, important events
- tool renderers: compact call, partial update, pass/fail result, expanded evidence
/pomoverlay: run, Hive, validate, evidence, vault, export, themes, settings- thinking lane: optional stage/execution annotation beneath visible thinking
Density
- cinematic: three-line HUD, stage track, richer cards and coordination cues
- rich: two-line evidence HUD and detailed cards
- compact: one-line HUD and terse cards
- minimal: status plus critical cards; no persistent widget
Motion
- off: static semantic symbols
- subtle: two-frame work pulse
- full: four-frame activity cue and stronger live coordination feedback
Law
Use OMP theme tokens and visual-width utilities. Never emit raw ANSI control sequences. Keep custom TUI optional: headless/RPC/ACP operation must still work through textual tools and canonical files.