This is a sibling of illustrious-visual-reference.pages.dev. Nothing there was changed. Here is what I took from it, what I altered, and one working prototype to judge before beta.2: the fused Workroom instrument, fed by a journal instead of a tension slider, in the fonts and tokens the app actually ships.
Liquid Spine shell + Resonant Spine waveguide + harmonic-blob vessels in the glass skin. Nine scenario buttons drive a fixture journal through a FrequencyState reducer. EN/ES. Goals grid, org strip with gates, decision packet with reply-with-edit and a shadow dry-run send.
open → press the scenarios in order Side by sideYour original render on the left, the prototype on the right, same viewport. Switch the left side between 011, 015, 012 and 014.
open compare EvidenceAll seventeen renders measured frame by frame, calm against drift, with the signal model and a live six-input playground.
open assessment Yours · untouchedThe seventeen originals, the style bank and the four new render choices, exactly as you published them.
open the hubThe hub is a good reference site. Its thesis line is the product thesis. The things below are the places where the reference and the shipping app would drift apart if nobody said so now.
| Hub element | Verdict | Why, and what the prototype does instead |
|---|---|---|
| Thesis: workflow health is frequency; drift is violent oscillation; recovery is governed damping, never a snap | keep, verbatim | This is the product sentence. It is the first line of the tester guide's "reading the instrument" page. |
| Two collections (sketches, liquid engines) | keep | The split is right: information architecture on one side, physics on the other. The prototype is the point where they meet. |
| Style bank: six skins on number keys | adapt to two | A product has one skin and one light theme. Obsidian Atelier is the app's dark theme; Consulting Ivory is its light theme (the app already ships pearl and cloud tokens). Phosphor, Blueprint, Ember and Mono Ink are moods for marketing pages and the operator shell, not the harness. Six skins in the product would mean six times the visual QA on every screen. |
| IBM Plex Mono for telemetry, loaded from Google Fonts | align with the app | The app bundles JetBrains Mono, Inter and Fraunces under the OFL and runs with a self-only content policy; nothing loads from Google at runtime. This site and the prototype use the same bundled files, so what you see here is what the installer draws. |
| "A global tension 0..1 drives every visual property" | replace with the reducer | True of the mockups, and the reason they cannot ship: one number cannot tell a storm from a rejected handoff. The prototype derives everything from six measured signals per stage and shows the harmonic that carries each cause. The hub's physics section stays; its four laws are the four envelopes the reducer uses. |
| Flagship 011 with the ILLUSTRIOUS_STATE contract | keep the contract, swap the vessels | The state object and the tick are exactly how the app will feed the renderer (snapshot-changed over IPC). The particle vessels measured almost no visible change at node size, so the prototype draws the harmonic blob inside the same glass sphere. |
| 016 Constellation Web | leave | Same failure as the orbit renders: legible at five agents, spaghetti at nine, and the Fable roster has a Chief, four PMs, four gates and twenty-two profiles. Its one good idea, pulses travelling the edges, is already the waveguide packet. |
| 017 VU Meter Deck | take one idea | Peak hold is a real instrument idea: the bar shows now, the tick shows the worst of the last minute. The prototype's org-strip severity bars now carry a peak-hold tick. The full deck is not needed. |
| 018 Ink & Scroll | move to exports | Not a screen, a document skin. The wax seal is the right stamp for SEALED receipts and the exported audit packet, alongside the Ledger Brief (006) broadsheet. |
| 019 Radar Sweep | leave | The sweep is the damping sweep the waveguide already has; smeared blips are the illegibility problem again. |
| Renders carry real customer and project names | fix before anything is copied | The product CI fails a build that contains either customer's name. The prototype uses a labelled sample business and generic goals. |
| 011 and 010 sketch: inspector card visible on load · 009: one asset 404s | fix on the hub | Cosmetic on the hub, blocking under the app's content policy. Listed in the assessment with the fixes. |
Harmonic blob inside the glass sphere (prototype) instead of the particle-in-vessel liquid (011). My recommendation: yes.
In tune below 0.30, drifting to 0.60, out of tune above. The chip follows the worst stage, not the average, so one storm in one stage is visible from across the room. Recommendation: yes.
Chief, four PMs and the four gates as vessels, roster profiles behind a click. Or PMs only, gates as pills. Recommendation: gates as vessels; they are the identities that hold work.
Obsidian Atelier dark, Consulting Ivory light, nothing else in the product. Recommendation: yes; keep the other four for marketing pages.
Promote none to a full render; take peak hold from 017 and the wax seal from 018 as components. Recommendation: as stated.