Files
DeepSeek-Reasonix/desktop/README.md
T
yhh 394da0a313 refactor: the kernel's packages live in the layer they belong to
internal/ was 141 packages side by side, so nothing but a reader's memory
said which were foundations and which assembled the rest. Each now sits in a
layer directory, and the directory is the declaration:

  base      L0  foundation with no domain in it
  contract  L1  types and interfaces the layers above agree on
  model, tools, safety, ext, state, platform
            L2  subsystems, peers of one another
  runtime   L3  the turn engine
  session   L4  the controller
  assembly  L5  the composition root
  frontend  L6  cli, serve, acp and the host adapters

Only paths change: package names, code and behaviour do not. Imports,
repolint and coverage baselines, sensitive paths, CI package lists and docs
follow the new paths; release notes keep the paths they were written with,
and sample paths inside tests and fixtures keep theirs.

repolint gains layer-order: a package may import its own layer and those
below it, read from where it lives. The 47 imports that point upward today
are recorded as that rule's opening debt (-allow-widen, a new rule's first
baseline) and can only go down. Most of it is config, which still reaches
into eight subsystems and is the next thing to take apart; the rest is
event, history and a few tools reaching into runtime for types that belong
in contract.
2026-09-23 18:28:21 -07:00

4.4 KiB

Reasonix Studio

A desktop window around the Reasonix Go kernel. The window hosts a React SPA, and every request the SPA makes reaches the kernel's own HTTP server (internal/frontend/serve) over loopback, so Studio, reasonix serve and the remote UI all answer the same routes.

┌──────────────────────────────────────────────────────────────┐
│  renderer (React + TS, Vite)  —  desktop/frontend-next        │
│    fetch("/…") · EventSource("/events")                       │
└───────────────▲────────────────────────────┬─────────────────┘
                │ HTTP + SSE over 127.0.0.1  │
┌───────────────┴────────────────────────────▼─────────────────┐
│  desktop/electron  main process                               │
│    windows, menus, dialogs, tray, the platform opener         │
│    owns OS capability and no business state                   │
└───────────────▲────────────────────────────┬─────────────────┘
                │ spawns, holds the lease    │
┌───────────────┴────────────────────────────▼─────────────────┐
│  cmd/reasonix-studio-host  (main module, CGO-free)            │
│    internal/assembly/boot.Build → internal/session/control.Controller          │
│    (same assembly the CLI uses: providers, tools, gate, …)    │
└───────────────────────────────────────────────────────────────┘

The renderer never learns which shell it is in: anything a page cannot do it asks HostPort (frontend-next/src/port/host.ts) for, and the main process answers over IPC that carries OS capability only. The boundaries this runs on are written down in docs/STUDIO_SHELL_BOUNDARIES.md.

Layout

Path What it is
electron/ the shell: main process, preload bridge, packaging
frontend-next/ the SPA it serves
internal/platform/update/ manifest, download, verify, apply — shared by the shell and the helper
cmd/update-helper/ the elevated half of an update (dpkg on Linux, versioned install on Windows)
cmd/studio-manifest/, cmd/sign/ release-side tools
internal/winuninstall/ taking a previous Windows install over

The host binary itself lives in the main module at cmd/reasonix-studio-host, because the updater it carries has to stay in the kernel's language.

Why a nested module

desktop/ is its own Go module (module reasonix/desktop, replace reasonix => ../). The parent module's go build / vet / test ./... skip this directory while the import path stays under reasonix/, so it can still import the reasonix/internal/* kernel. The module is CGO-free, so no platform carries build dependencies of its own.

Prerequisites

  • Go (matches the parent module).
  • Node 24+ and pnpm 10 (npm install -g pnpm@10).

Running it

make studio          # build the SPA + kernel and launch the Electron shell

One launch path on every platform. The dev build is already an .app, so macOS treats it as a real GUI app and native panels — "Add a folder…" — open normally.

For frontend iteration, run the kernel and point Vite at it:

go run ./cmd/reasonix serve                       # from the repository root
cd desktop/frontend-next && pnpm install && pnpm dev   # :5273, proxies API paths

Building and testing

make studio-test                                  # go test ./... for this module
cd frontend-next && pnpm typecheck && pnpm test && pnpm build

Packaging runs through electron-builder; release-studio.yml drives it on all three platforms. Linux ships a .deb because that is what makes Studio self-updating there. See docs/STUDIO_RELEASE.md.