§ Platform / Workbench
Everything you own, one surface.
Open Scellis without a workflow and you land on Home: your work, your recent activity, what others shared with you, and you — collections, workspaces, plan, account. Not a dashboard bolted on, but the same canvas in another mode, with everything one click from where you left off.
A mode, not a dashboard
Home is a mode of the Studio canvas — a sibling of the workflow and of Model View, and where you land whenever no document is open. Its shelves are a complete map of what is yours: My Work holds workflows, models, datasets, and everything you built; Activity holds recents, run history, and drafts; Shared & Acquired holds what was given to you, what you installed, what you bought, and the pools you joined; Me holds your collections, workspaces, plan, and account. If it exists, it has a shelf.
The shelves stay honest at scale. Your device holds only the working set you actually use, so Home lists names, versions, and dates instantly and fetches a thing itself only when you open it — your shelves stay fast however much you own. Work you made on another device is never quietly missing from the list, and offline the surface shows what is local and says plainly that it is doing so.
A collection that pins versions, not links
| What Home holds | What it pins | What that gets you |
|---|---|---|
| Collections | the exact versions you chose | Hand one over and they see what you curated — not what moved since. |
| Drafts | the work in progress on this device | A tab crash costs seconds, not an afternoon — Home offers the draft back. |
| Run history | every run, across sessions and devices | Which settings made Tuesday's curve is a lookup, not a memory test. |
| Trash | what you deleted, for a while | Deleting is undoable by default; erasing published work is refused while anyone still depends on it. |
| Shared & acquired | what others gave, sold, or granted you | It sits on the same shelves as your own work, and it is pinned the same way. |
Everything on these shelves is pinned to an exact version — nothing you depend on can move underneath you.
A Repository is your shelf: a named, shareable collection that pins exact versions of whatever you put on it — workflows, models, datasets, blocks. Curation is its entire job. It is one of five grouping ideas Scellis keeps deliberately apart, so that none of them quietly becomes a folder that does everything badly: what each one is for.
Pinning is what makes a collection safe to hand over. Share one with a colleague, a class, or a reviewer, and they see precisely the versions you curated — not whatever moved underneath in the meantime. That is the difference between sending someone your work and sending them a link that will mean something else next month.
Nothing is lost by accident
The draft you are editing saves itself to the device as you type — deliberately kept apart from published versions, because work in progress and a committed result are different things. A tab crash costs seconds, not an afternoon; on reload, Home offers the draft back. Run history is just as durable and outlives the session: close the tab, keep the record.
Deleting is recoverable by default: what you delete moves to the trash and waits there, and restoring it is one action. Erasing published work is stricter than you are: while anyone's pinned dependency still points at a version — including the one your future self pinned — the erase is refused or turned into a tombstone. The platform will not let you break somebody else's build, and it will not let you break your own.
A notice exists because something happened
Every notice is made on the server by an event that actually took place: a document shared with you in a live session, an @mention, a long local training run finishing — or failing — a pooled or federated job completing, a purchase unlocking, a new version of something you depend on. A client cannot invent one. A notice references what it points at rather than embedding it, and it carries no personal detail beyond who acted.
Delivery follows your tab: live over the session while one is open, held and delivered next time you sync otherwise. You choose what reaches you, per kind — mute a category, allow system alerts on this device, or turn on an email digest, which is off until you ask for it and carries a one-click unsubscribe in every message. The same bell reports service health and the reload-to-update signal: an incident or a new engine is said out loud, while your local compute keeps running.
One feed is deliberately absent: nowhere in the product can you follow a person. You can watch a thing — a model, a dataset, a pack — and hear about its new versions and its discussion. The object of attention is always the work, never the person behind it.
The first session is a contract
A small engine with nothing in it would open onto a dead blank canvas, so the first session is specified like any other surface. The first-run gallery arrives with early access: Home greets a first visit with templates covering the workloads people actually come for — train, analyze, run statistics — with sample data that resolves immediately. The rule behind the gallery is mechanical: every template must run end to end, from data to a first number, with zero edits, and that is checked automatically against a stated time budget. A template that stops working is caught before release, not left as a stale card.
Tours are content, not hardcoded pop-ups: replay one from Help whenever you want it, and a pack can bring its own tour for its own field. None of this needs an account — working without signing in is real work, held on your device — and claiming it into an account later is a one-time move that fills your shelves with everything you already made. The quickstart walks the same first path in prose.
Every setting is also a command
| Panel | You control | Note |
|---|---|---|
| Preferences | theme · language · units · timezone · density · how exactly runs reproduce | Readable by the Copilot; every change still asks you first. |
| Sessions & API keys | list, revoke — one or all | Making a key, or widening one, is a human gesture — never handed to an agent. |
| Storage & pins | what the device holds · pins · clear the cache | Pinned work is never evicted by cleanup. |
| Backup & restore | export everything local, import it back | Arrives with early access. Credentials stay out of the bundle by construction — they never leave the device. |
| Billing & plan | your plan, what it includes, your invoices | Computation is never tier-gated — unlimited local compute on every plan. |
| Account & data | see · export · correct · erase | Your data rights as buttons, not support tickets. |
Every row here is also a command — reachable from the interface, from the Copilot, and from a script of your own.
Settings live on one surface, and every control on it is also a command on the same interface the product itself is built from: theme, language, units, timezone, density, how exactly your runs should reproduce by default, what the bell may tell you. The symmetry is not cosmetic — the Copilot can read your setup and change it only with your say-so, and what must stay a human gesture is named exactly: an agent can open the API-keys panel for you, but it can never mint a key or widen one.
The account pages treat your data as yours in the mechanical sense. A meter shows what is occupying the device, with pins that cleanup never touches; sessions and API keys are listed and revocable one by one or all at once. Backup and restore arrives with early access in exactly this shape: a device-local export of everything local — drafts, documents, models, settings — with a checked import at the other end, and credentials left out of that bundle by construction. Your data rights — see it, export it, correct it, erase it — are controls on this page, not letters to a support address.