# Round-table judge brief: Zen of Nugu ## Historical record Recorded names, source locations and external scratch evidence describe the review's original tree, not current runtime APIs. You are one independent judge on a panel scoring Nuguland, a Quickshell desktop shell (bar plus popups) for the niri compositor, against its user-experience law, the Zen of Nugu. Read the law first: `/home/me/Workspace/dotfiles/quickshell/nuguland/.system/specs/NL-SPEC-VQXGUHYK-zen-of-nugu/index.md` (zen 1–15, rules, precedence, acceptance). Read-only: never edit, run, or create files except reading. ## Evidence - Rendered screenshots per feature: `/tmp/nl-zen///*.png` (round given in your prompt). They come from nested-niri test runs at 1280×720 with synthetic fixture data, horizontal bar unless the name says vertical. Fixture text such as "fixture track" is test data, not product copy; judge layout, hierarchy, states and wording patterns, not the fixture's sample strings. The bar clock and live values differ between runs. - Source, when a screenshot cannot settle a question (keyboard paths, focus, motion, polling, tooltips): `/tmp/nuguland-zen/quickshell/nuguland/` — `features//` (panel `*Panel.qml`, service, `fixtures/suite.mjs` shows exercised keyboard and pointer flows), shared controls `Popup*.qml`, `Bar.qml`, `PopoutHost.qml`, `Theme.qml`, `OverlayHost.qml`, `PrivilegeSurface.qml`. - Feature list: bar, clock, launcher, media, noko (speech-to-text), system, clipboard, vault (password manager), audio, brightness, connectivity, power, notifications (history popup and toasts), tray, osd (volume/brightness overlay), privilege (authentication prompt), screenshots (screenshot history notifications). Open every screenshot of a feature before scoring it. ## Scoring For every feature, score each zen principle 1–15: - 2: meets the principle as far as the evidence shows; - 1: partly, with a concrete shortfall; - 0: clearly violated; - null: the evidence cannot show it (never guess a pass). For every score below 2, give an issue: principle, severity (`blocker` for a 0, `major`, `minor`), the evidence (screenshot file name or `file:line`), the problem in one sentence, and the smallest fix in one sentence that keeps the house precedence (lowercase, tray chip stays, compact icon-led). Prefer few, decisive issues over many cosmetic ones; merge duplicates; an issue that applies to many features (a shared control, the bar) belongs to the feature `shared` instead of being repeated. Also give your strongest counterexample to your own verdict and your main uncertainty.