The 32-view interface atlas
A design artifact, not a feature ledger
Section titled “A design artifact, not a feature ledger”The atlas explores the product’s larger direction in an original branded browser interface. Its actions manipulate local simulations. It does not start an inference engine, transfer model bytes, execute a shell, install MCPs or publish a change.
The native 0.0.1 release implements Chat, Model Library, Load Lab, System and About. Similar names in the atlas can describe a larger future workflow and may retain architecture-specific research gates. Use native release evidence to determine what actually works.
Coverage
Section titled “Coverage”| Group | Atlas views |
|---|---|
| Workspace | Neural Space, Overview, Load Lab, Model Planner, Discover Models, Model Library, Model Detail, Downloads |
| Create | Chat, Project Workbench, Agent Workspace, Orchestrator, Agent Library, Pets & Bots, Canvas & Artifacts, Projects, Knowledge |
| Extend | MCP Servers, Tools, Skills, Modules & SDK |
| Operate | Run History, Benchmarks, Runtimes, Remote Machines, Local API, Providers, Diagnostics |
| System | RegesMode, Settings, Setup, About & Licenses |
That is 32 routes. Night, Daylight, Focus and Crimson are atlas design themes; the current native app exposes Night and Day. The marketing website is another distinct surface and does not become the native executable by sharing its brand.
Useful design interactions
Section titled “Useful design interactions”The atlas includes exact custom context such as 57,000, model-discovery sample filters and direct source links, simulated download plans, a large-model planner, API route examples, an in-memory multi-file workbench, orchestration controls and permission previews. Research catalogs preserve official/community/proposed provenance.
The Model Planner’s large artifacts and memory scenarios are not successful native load claims. A simulated terminal does not execute commands. A patch applied in the prototype’s virtual file tree does not modify a real repository.
Use it for implementation
Section titled “Use it for implementation”Open the interface preview to review navigation, states and layout. For each future screen, map visible controls to an actual host contract, capability gate, error state and test. Preserve original workflows while replacing simulation with measured behavior a feature at a time.
The atlas is valuable because it makes product decisions reviewable. Its design preview banner is equally valuable: it prevents a polished screen from being mistaken for working engine or ecosystem integration.