Skip to main content
Desk 2.0 has a documented product model and a safe implementation checkpoint. It is not yet a finished, browser-proven workspace.

​
Established

  • The existing market cockpit is now Home in the product direction.
  • A separate Desk route and shell were introduced to begin the Home-versus-Desk separation.
  • The Desk Suite information architecture is defined.
  • The market-data work has an established ownership boundary: Desk consumes versioned adapters rather than rebuilding the data plane.
  • The collaboration model, privacy rules, history behavior, and shared-artifact model are documented.
  • The pinned Desk 2.0 layout contract is verified at deployed parity in the v9 prototype preview: the four canonical layouts (EdgeCaster, Tilt Correction, Analyst, Stock Screener), the shared briefing and KPI stack, region selection, mobile stacking, and the header/footer shell match the pinned reference build at desktop and mobile viewports.
  • The prototype preview surfaces now consume the live production API (fintheon.fly.dev) through a same-origin /api/* proxy on both Vercel deployments: the v9 preview and the pinned reference build both render identical live market data (briefs, futures, GEX levels, risk signals), and auth-gated lanes degrade honestly to forbidden states rather than fabricated content. This proves the deployed-preview data lane, not the full authenticated workflow.
  • The complete source-derived Wonder block set landed in Fintheon Blocks (v9) (main, Page 1): all four canonical Desk layouts — Desk EdgeCaster, Desk Tilt Correction, Desk Analyst, and Desk Stock Screener — were built inside the designated pre-polish container from the deployed preview and repository tokens (15 fintheon/* variables, all styling bound via var(--fintheon-*)), at both desktop (1440px) and mobile (390px) viewports, and each matched its own live capture of the production surface. A ninth artboard, Desk Interactive States (v9, Live), carries 27 panels covering every shipped interactive state: the secondary/primary tab alternates (EdgeCaster primary flip — honest unavailable, Risk Signals, shared Forum widget), the open layout-picker menu, the secondary risk-window layer, the stock-screener row drill-in (TradingView chart frame), the account and profile header dropdowns, the resizable column split (localStorage persistence verified across reload), the Cmd+K/Cmd+J/Cmd+. keyboard overlays, the Tribune briefing-source menu, the collapsed icon rail, the sidebar filter, the forum invite popover, the event-drawer tab alternates, the econ-print popover (honest unavailable), and all five right-drawer kinds via the ?drawer= deep link (event plus copilot, research, session, voice), the drawer resize seam (320-560px bounds clamped live, per-kind fintheon-drawer-widths localStorage persistence), and every tab of every drawer kind (copilot Mission Control/Calendar, research Provenance/Revisions/Share, session Steer/Fork, voice Transcript/Consent). The ?surface= secondary-surface deep link was verified live via hash URLs (#/desk/analyst?surface=forum seeds Forum; #/desk/edgecaster?surface=risk seeds Risk Signals; #/desk/huddles compat-redirects to analyst+forum). Every element not shown is recorded as inert, login-gated, static, or unrendered in the honest empty state. The deployed layout picker exposes exactly these four layouts. Two honest limitations are recorded: Space Grotesk is not in the Wonder font catalog so the canvas falls back to Inter while the token holds the correct value, and the Analyst article hero image is a placeholder block because the source uses a generated photo asset.

​
Still required

The product must prove one complete vertical slice before expanding across every Desk page:
  1. Find a market target.
  2. Open a governed session.
  3. Create or attach a stage artifact.
  4. Load the correct context module.
  5. Restore history and return to the same state.
After that, the remaining work includes durable room behavior, permissions, agent-context protection, DeskMap and QuantComposer integration, the unified settings page, and activity-triggered islands.

​
What does not count as completion

A route, a static channel list, a loaded shell, a green build, or an available health endpoint does not prove that the Desk works for a trader. Completion requires browser proof that the real workflow can survive navigation, refresh, errors, unavailable providers, private-context boundaries, and return paths.

​
The release standard

Desk 2.0 reaches release readiness when the source, the browser experience, durable state, access rules, and deployed product all agree. Until then, these docs describe the target experience and its verified foundations.