The environment
IDEs are not fading. They are where a solution's lifecycle becomes visible. Softanza's estate has built the same environment six times, in two years, without sharing a line of code, and this page says what shape it keeps converging on and what would make the next one easy.
The grammar
Six efforts in two years, for six different readers, have converged on one grammar. None of them shares code with another, which is the argument for a foundation.
- A window with three permanent regions. A spine that lists the facets, a workspace where the work is, and a context rail. A title bar sits above and a status bar below.
- An identity bar. The project or session, the user, the theme, the language, a mode from guided to expert, and one primary action.
- A ribbon ordered by a solution's lifecycle, not by the tool's features: for example Design, Data, Build, Intelligence, Operate, Support; or Define, Architect, Build, Govern, Ship.
- An explorer over closed-grammar files, each kind with its own extension.
- A context rail that proposes and never commits. It changes with what is focused, and its assistant panel shows its context and the rule that governs it everywhere: a proposal is reviewed like a human's.
- A status bar that tells the truth, and governance in every cell: proposals as counts, a violation as a badge, cost against budget, and in guided mode every change previewed before it lands and reversible after.
What makes it Softanza's and not another shell: the ribbon follows the solution's lifecycle, the rail proposes with a court beneath it, and governance is a first-class cell.
The efforts, and their stages
A listening bench for the sound plane (built)
One file to run: the page is embedded in the executable, so the binary is the whole tool, and rebuilding the engine rebuilds the studio. It is the one shell that ships.
The commercial visual environment (specification)
Softanza Studio: the declared application, its world, its facets, its deployment, over the same plain-text truth. A design corpus and a browser prototype exist.
A refinement product (specification)
Governed change over code, interface and data. The paradigm's mechanics are the platform's, and the environment is the product's.
A language editor (specification)
An editor for the language that follows, whose language service is an adapter over a contract.
A federation console (specification)
For organisations that govern by declarations: a prototype of nineteen pages and no software.
The harness's studio (designed)
The estate live on one page: serve, watch, speak, govern, authorise, in one executable.
Two shells, one chrome
Which shell should an environment have? The ruling is both: the page in your browser and the window on your desktop, declared once, and proved to agree.
The page in the browser
One file to run, no install on any machine with a browser, the same page that an AI agent, a remote reviewer or a phone opens. Its costs, as written: a browser tab and not a native window, the browser's file-access model, and a local port that must be treated as a surface. Measured for a sound studio, not yet for an environment.
The window on the desktop
A single executable with no runtime and no framework, input to screen under sixteen milliseconds, no port, the host's own dialogs, the graphics card for a large code graph. Its costs: a native widget layer to build or project, and a latency constraint owed as a measurement, not a promise.
Three constraints carry both. One declaration: no chrome element exists in one shell and not the other. Agreement proved: the guard that checks a picture rendered by two backends is extended to the chrome. Latency measured, not inherited: each shell carries its own number, dated, with its method, a loss published where it stands.
The Softanza way A picture is described once and rendered twice, so the two backends cannot disagree about where anything sits. For pictures that sentence is checked by a guard with twenty-four assertions, written because until it existed, "cannot disagree" was an argument and not a result.
designed No environment of this family ships today. One shell ships, for the sound plane. The foundation that would make the next one a projection of a declaration, a shell kit, a declared chrome, the facet as data, the rail and the governance cells as library verbs, is specified and not built. The two shells' latency was not measured, and whether the current panel kinds reach a native window without new plumbing was not tested.
Sources: the interface law on the Zui page; the estate's products and their stages on the estate page. The six efforts and their grammar were read from the estate's design documents by an outside assessment on 2026-10-07.