Regisseur · Product Walkthrough
Built in one place. Installed cleanly in another.
A complete industry package — agents, forms, document templates, and process flow — exported as one cryptographically signed file and installed into a different, live customer-style workspace through a single install screen.
3
Workspaces involved
12
Package components installed
4 of 4
Follow-up policies applied
1
Unsigned package correctly refused
27
Screens captured live
About this walkthrough
Every screen below is a real screenshot from an automated, end-to-end run of Regisseur against a live, publicly-reachable deployment — not a mock-up, not a local demo. Company names shown (Woodgrove Life, Northwind Traders) are fictional demo workspaces.
Two honest notes about how this walkthrough was run: it creates one extra workspace along the way (Chapter 3) and leaves it in place afterward — there's no delete step for a workspace today, so that's a deliberate leftover, not something tidied up off-camera. The person who creates it also can't switch into it from the top of the screen yet — Regisseur doesn't have a workspace switcher yet — so Chapters 6-8 show what that kind of workspace looks like day-to-day using a separate, already-provisioned login instead. One screen briefly listed the new package in the wrong workspace's list until the page was reloaded — a small display timing issue we've already noted to fix.
Part 1
Proof of Version
Confirming exactly what release is live, on the live box, from three separate screens
A real sign-in against a live, publicly-reachable Regisseur deployment — not a local sandbox.
Settings shows the release identity that matters — set at build time and carried through the actual upgrade that happened on this box.
Every signed-in screen carries a small footer naming the release — a third, independent confirmation that agrees with Settings and with the public endpoint above it, not a one-off claim on a single page.
Part 2
Before Anything Changes
The workspace as it stood before any package action
The workspace's package panel exactly as it stood before any new package action — nothing staged, nothing pre-arranged for this walkthrough.
Part 3
A Real Choice
A signed package, verified — replace what's already running, or start fresh in a brand-new workspace
Uploading the real signed package and its signature triggers a live cryptographic check: signature verified, publisher identified by name and fingerprint, and a preview of exactly what would be added — 12 new components, nothing overwritten. Because this workspace already runs a different line of business, the product also shows a plain warning naming exactly what confirming would do, and the confirm button stays off until that warning is acknowledged.
Ticking "I understand this workspace will switch" is what turns the confirm button on — and even then it now reads "Replace and install," not a plain "Install." The consequence is stated, not buried.
The preview is dismissed and nothing is written. Right where this decision needs to be made, the product offers the alternative: keep the current line of business untouched, and install into a brand-new workspace instead.
The option to spin up a brand-new workspace, right from the install screen, is reserved for the workspace's owner — the one person accountable for everything that runs there. Anyone else sees the same option, correctly grayed out, with the reason stated in plain language.
Signed in as the workspace owner, the same signed package is previewed again — the same verified signature, the same plain warning. The warning is about the workspace, not about who happens to be looking at it.
Rather than replacing the line of business already running for other people, the owner takes the alternative: a brand-new workspace, created for this package alone. "You become its owner; the current workspace is left alone."
Previewed again against the brand-new workspace: the same verified signature, the same 12 new components — but no warning this time, because a workspace with nothing installed yet has nothing to overwrite. The confirm button is a plain "Install," and a clear note confirms the original workspace stays untouched.
The new workspace is created and the package installs into it immediately: all 12 components, and every one of its 4 built-in follow-up policies. A message confirms exactly where things stand: still in the original workspace, with the new one ready and waiting.
Part 4
Trust, Enforced
An unsigned package is refused automatically, before anything is touched
The identical package content, offered without its signature. The platform's trust check refuses it before any preview or install is even offered — no override taken, no exception made.
Part 5
Nothing Disturbed
The original workspace, unchanged — checked again after the new workspace goes live
The workspace's existing configuration, shown exactly as it was before and after this walkthrough — nothing here was altered by the review in the previous section.
A day-2 readiness check for the workspace's existing package: every requirement passes — a working AI model, a connected mail provider, a document-processing provider, and every team role staffed with an owner. This is what "ready to use" looks like from the inside.
A durable, timestamped record of every install and upgrade this workspace has ever run — who did it and when, going back to the very first install. The most recent steps each carry a verified signature; every change is on the record.
The full settings surface available to this admin account, shown as-is.
Back in the original workspace, reloaded fresh from the server: the existing line of business is still active, and the new package is nowhere on this workspace's own list. The new install genuinely went somewhere else.
This workspace's permanent install history is unchanged — no new entry, because nothing was installed here. The full record of the new install lives in the new workspace instead.
Part 6
A Dedicated Workspace
A workspace built for this package — this run may be its first install, or a repeat
A workspace built specifically for this package, signed into directly. This is where the full install is shown end to end.
This workspace already carries the package from an earlier walkthrough — a genuinely different, and equally honest, starting point. What happens next re-verifies the same signed package, checked and applied again, rather than performing a first install.
Part 7
The Real Install
The same signed package, verified again, installed for real
The identical signed package from earlier, previewed against this workspace: signature verified, its components ready to apply. Nothing left to decide — so the install proceeds.
The completed install, confirmed immediately: every component applied, the signature verified end to end, and all 4 of the package's built-in follow-up policies written in. Nothing pre-loaded, nothing assumed.
Part 8
Proof, From Every Angle
The new capability confirmed from several independent screens, not just the install's own message
Independent proof, from a completely different screen than the install confirmation: the four follow-up policies the package declared — document requests, information asks, status check-ins, and dispute responses — now genuinely present in this workspace's own configuration.
The same readiness check, run again right after the new package installs — and it says plainly what still needs attention before the new agents can run: a default AI model, a mail provider, a document-processing provider, and two team roles that still need an owner assigned. Nothing is hidden or glossed over; the platform tells the operator exactly what to do next, with a direct link to fix each item.
The workspace's install history now carries this event — package name, version, signed status, who ran it, and exactly when. A durable record, not just a one-time confirmation message.
The new package now appears in the workspace's own package list. Look at the navigation bar too: it has switched from generic terms (Jobs, Customers) to the new package's own language (Exceptions, Vendors, "+ New Exception") — visible proof the new capability is live everywhere in the product, not just on one settings page.