jason.woltjeandClaude Opus 5.5
08b428ecf1
Dewey's round 3 candidate, manifest
agents/dewey/work/queue-40/candidate-manifest-r3.sha256 (d0aa0ded,
27 files, checked OK in the canonical tree).
- WebUI inbox, tasks, agents and trail views, read-only over /api/bus.
The README says the bus proof ends at the Console process.
- CHAT-03 seal: the engine command is fixed, the engine environment is
explicit, SEAL_FLAGS has --no-approve, escalating is cleared on throw.
- Terminal input typed after Ctrl-T or Ctrl-O is held. Only the run whose
own parse set held drains it (T1), and #run catches errors per action.
- DEFERRED keeps N2 and moves F2 to done, citing T1.
Reviews: Filbert approve (comment 27011, rev 260), Darkwing approve
(27013, rev 264). Landing gate on 8cad7722 plus the candidate: webui 22,
conversation 161, control-board 124, every scripts/test-*.sh green,
test-task 98/0. Mutant Mr survives; its flows test is the first
follow-up row.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Mosaic Stack WUI design work
Status as of 2026-09-26: Jason selected d3 Console on 2026-09-12 (MOSAIC-STACK-D-002). It is implemented in packages/webui (ea00ec66, #1507) and continues under the session-chat plan, docs/plans/2026-09-13_webui-session-chat.md. The five mockups and the brand board below are kept for reference. No brand choice is approved.
Dashboard mockups: open the comparison
Entry page:
/mnt/storage/src/mosaic-stack/agents/dewey/work/wui/mockups/index.html
Open that file in a browser on this host. It needs the mockups/shared folder, brand.js, and assets/fonts beside it. No server, package, account, or network is required. Everything is a local design prototype: every button produces a "Simulated" notice and nothing touches the fleet, the data root, or credentials.
The five designs share one data set, one route list, and one settings page. They differ in navigation and in how the control board lays out.
| Design | Shape | Choose it when |
|---|---|---|
| Rail | Left rail, board with waiting list on top, running table, side panels; fourth column on ultrawide | You live in it all day and want stable navigation at any width |
| Deck | Top tabs, waiting cards in a row, session cards | You glance a few times a day and want the waiting row to shout |
| Console | Command bar with Ctrl+K, project tree, dense table, inspector drawer | You run many sessions and prefer keyboard and density |
| Board | Kanban by session state with project chips | You think in states and want to see load per column |
| Stream | Pinned inbox, time-ordered stream, bottom tabs on phones | You check from a phone often |
Suggested review, about fifteen minutes:
- Pick a palette and appearance on the comparison page. The buttons under each design open it with that choice.
- Open each design's control board. Ask whether the waiting-on-you section would make you act within a few seconds.
- Narrow the window to a phone width, then widen it to your full monitor. The shell should stay usable at both.
- Open the Darkwing session from the Session view button. Try Observe, Request control, Stop, and Check now on the config notice.
- Open Launch. Try the retired workspace archive-2025 and an agent that is already running. Both refuse with a reason.
- On Settings, change the demo state to loading, empty, and error, then back to normal.
- Keyboard only: Tab from the top, use Escape to close anything open, and in Console press Ctrl+K.
- Write notes on the comparison page and download them, or reply here with the design to iterate and what to change.
What to decide: the design to iterate in HTML, features to add or drop, and whether the control board should stay the landing page. Selection is a human decision; nothing in the pages records approval.
Records: feature inventory, design spec, verification with evidence/mockups/report.json and screenshots, tasks, history, decisions.
Brand board (earlier phase)
Open the board
Entry page:
/mnt/storage/src/mosaic-stack/agents/dewey/work/wui/index.html
Open that file in a browser on this host. To review on a different computer, copy the whole wui folder and open its index.html. Keep assets, the CSS, and the JavaScript beside it. No server, package installation, account, or network connection is required for the board. Do not open only a copied HTML file without its assets.
The reference-research scripts use the network, but the delivered board does not. No service has been started or deployed.
Suggested review, about ten minutes
- Start with Assembly, DM Sans, and Harbor, my proposed baseline. Appearance initially follows the browser's system preference unless you already have a saved choice.
- In Identity, choose each mark. Compare the full logo in the header/brand specimen and the monochrome 16/24/32 px samples. Tell me whether you prefer the literal M, the woven links, or the abstract tile.
- In Typography, compare DM Sans, IBM Plex Sans, and Manrope. The three specimens retain their own font. Choosing a font changes the rest of the board, including actual controls.
- In Color system, try each palette's Light, Dim, and Dark buttons. Each button selects both that palette and that appearance. Look for readable text, useful surface depth, and a color family you would want to use daily. Hue angles and harmony rationale are printed on every palette card.
- In Iconography & controls, try the example name field, all five states, and Preview success. An error keeps the text intact. Loading is a labeled specimen, not a running request. Nothing creates a project or contacts a server.
- In Your review, write notes and download them. Downloads contain the selected logo, font, palette, mode, and your notes. Send the file or your feedback in this conversation. The page does not transmit notes to Dewey.
Selections and review notes use this browser's local storage when available. Reset preview restores the proposed choices but deliberately keeps your notes and the example name. Clearing site data or using a different file location/browser can lose local notes; download a copy to keep them.
You can also download the selected palette's tokens for all three modes. This is a design reference, not a production configuration file.
What to decide
- Preferred logo and any shape/spacing revisions.
- Preferred font and icon treatment.
- Default palette and appearance behavior.
- Palettes to change or remove before dashboard exploration.
Branding approval is a separate human decision. Choosing controls or downloading notes does not approve anything automatically. Jason later allowed dashboard work to proceed with Manrope, the ten palettes, and a text wordmark while the logo stays unresolved; see DECISIONS.md.
Evidence and project records
- Verification and limits, including reproducible commands.
- Reference observations, including what was and was not inspected on t3.codes and buzz.xyz.
- Requirements, owner decisions, task list, work history.
evidence/verification.json: 840 token-pair checks and 240 layout combinations.evidence/detail-verification.json: 8,220 rendered-text checks and interaction/failure/download checks.evidence/final-verification.json: local resources, links, targets, breakpoint checks, and skip navigation.evidence/board-light-1440.png,board-dim-1440.png,board-dark-1440.png: desktop appearance captures.evidence/section-identity-light.png,section-typography-light.png,section-color-ultrawide.png,section-components-mobile.png, andsection-review-light.png: comparison and component captures.assets/logos/: three standalone original SVG studies.assets/palettes.json: all ten proposed palettes and thirty token sets.assets/fonts/: bundled Latin fonts, OFL licenses, and source receipts. The existing font license notices are unchanged.
This is a local design-review package. No integration, deployment, commit, push, or independent technical acceptance is implied.