OrbitraSCOUT, the 30 September build

The sign-up is chained end to end in the 30 September build. The first companies are invited and checked by hand, so this is reached from an invitation; joining from the open web comes later.

A step of the sign-up, which is chained end to end in the 30 September build.

A step of the sign-up. Asking whether the person is the manager on the licence is the authority question the builders put into the same fortnight.

A step of the sign-up, which is chained end to end in the 30 September build.

A step of the sign-up. The documents it takes are what the vault holds, and the vault is in the build.

A step of the sign-up, which is chained end to end in the 30 September build.

A step of the sign-up, which is chained end to end in the 30 September build.

A step of the sign-up, which is chained end to end in the 30 September build.

A step of the sign-up, which is chained end to end in the 30 September build.

The branch the sign-up takes when the manager on the licence is somebody else.

The terms, inside the sign-up, which is chained end to end in the 30 September build.

The walk ends here. Nothing else stands between wanting in and the product.

The one screen a trader works from. It is in the build, and it is where the way in ends.

Where a follow-up goes, and where an approval happens. The list of past conversations down the left is the October part of this screen: every conversation is stored from day one, and browsing them comes later.

The conversation is where a follow-up goes and where an approval is given, so it is in the build with the box. The list of past conversations down the left is the October part of it: every conversation is stored from day one, and browsing them comes later.

The assistant prepares, a person approves, and nothing acts until they do. The limit is held by the backend, not by this screen.

The assistant prepares and a person approves, and the backend refuses to act without that approval. It is in the build.

Its first row is the person's name, and it opens Your Scout ID.

Part of the shell the builders already have running on every screen after sign-in.

The fifth row, the manager on the licence, is only shown when a staff member did the setup; the meter reads 1 of 5 only here, and the status line takes its own variant.

The desk's setup card, in the variant where a colleague rather than the manager did the setting up.

The same rows, the same component, in the platform's own corner panel. Day one it is in the flow of the desk; from the second visit it is docked, until every row is done.

The desk's setup card in the corner panel, which is where it sits from the second visit.

The corner panel closed to one line.

The desk after the verification call is booked from the setup card.

The setup card becomes the Verified card for one visit, every status chip on the screen reads Verified, and the status line takes the Verified first-visit variant.

The desk the day the company becomes Verified. The first companies are checked by hand, and this is what that check produces.

The status line's fourth variant is no status line: nothing left to report and nothing left to do.

The desk on an ordinary later visit.

The desk once the setup card is put away.

Needs you does not exist at zero: the pill goes from the top bar and the section goes from the desk. The setup card and the tracker still hold the screen.

The band of what needs you, with nothing in it.

The language menu. The full run-through before going live covers every language.

The desk once there is work on it.

The open canvas. Deliberately sparse, because the emptiness is the offer: it asks who you are, offers the first call, and leads to the console. The switch at the foot of it is what opens the desk fourteen days on, which is the last row of the October group.

The desk as a colleague sees it on the day they are brought in. Drawn as a state of the desk rather than as a screen of its own, so both readings of the desk are reviewed against one screen's grammar.

The step before anything irreversible. Both of the builders' own maps put it on the desk.

Everything open on this desk, in one list, ordered by how soon ignoring a line starts to cost. The desk's own band shows the first four of them and says how many it could not show; this is all of them, each with the line of detail the band has no room for. Both are drawn from one table, so the number above the band, the count in the top bar and this screen cannot disagree.

What needs you today, as a list. The desk's own band is the first few rows of it and its foot comes here, so the surface is already in the build.

A list of the company's live shipments, built from its own documents. Settlement, wallet and reconciliation are not here and are not coming here: they live in OrbitraOS.

The list of the company's trades is in the build.

The build plan describes a trade's detail twice as a row that opens rather than a page, so the page is retired and this is what it is. The record of what was approved on the trade, which the plan names, is on it.

A trade's detail is in the build. The build plan describes it twice as a row that opens rather than a page, so that is how it is drawn, and the page is retired.

The moment the company's own rules first reach a trade. Choosing what kind of trade this is decides the papers it will be expected to carry, and the list appears under the form before the trade exists.

Creating a trade is in the build, along with reading, changing and removing one.

A step of adding a trade: the form before the kind of trade is chosen, which is the answer the expected-document list hangs on.

A trade added on day one. Nothing is expected of it yet, and it takes the rules the moment they go live.

Adding a trade before the company has published its data rules. The build plan puts the rules engine and the trade object in the same three weeks, so a company will meet this order.

Every paper the company has added, each with a sealed copy that shows whether it has been altered.

The vault is in the build: documents stored, searchable, each with a sealed copy.

Searching is what the vault genuinely does on 30 September, and it was the one part of it with no drawing anywhere.

Searching the vault is what the backend genuinely serves on 30 September, and it was the one part of the vault with no drawing anywhere.

The details beside the document are the ones typed in when it was uploaded. Reading them off the page itself is later work.

The vault is in the build, with one correction on this screen. Reading text off a scanned page is not in it, so the details beside the document are the ones typed in when it was uploaded.

The sealed, tamper-evident copy of a document is named in the backend work for the build.

Dropping a document into the box on the desk is half of what that box is for.

One assistant, with its instructions and its track record, and the list of what it has prepared. That list is not the desk's Needs you band: the band is dates, this is work waiting on a decision, and in the backend they come from two different places.

One assistant is in the build, the document chaser, with its instructions and its track record, and the list of what it has prepared and is waiting on. In the backend that list and the desk's band of dates come from two different places, so they are two surfaces here.

The one assistant, in detail. A second assistant, a trade preparer, comes later.

The five categories of outside trade data: customs, trade documentation, logistics, compliance, and banking and foreign exchange. None is connected, and none is connected on 30 September either: the build runs on the company's own data.

Bringing the company's own data together is in the build. The five kinds of outside trade data are shown here as not connected, which is what running on the company's own data looks like on a screen.

Need 2: one source of truth for data, procedures and workflows.

The layer that holds the company's own rules and procedures is in the build, and it doubles as what the assistant reads.

The data rules page as the flow builds it: the three parts that come first on day one, the shipment types six weeks in. Replaces the fast track.

Pick the type, confirm the documents, save; then the way on to the data rules. Replaces the consignment list.

A state of the setup card, not a screen before the desk. On 30 September the person says which they are; nothing recommends a path to them, because the thing that would work that out comes later.

Choosing a path at activation is in the build, as a manual choice. Nothing recommends a path, because the thing that would work one out comes later.

Everything about the company in one place, and it absorbs the old post-login home: the Orbitra ID with the status component, the public page and its QR, and the "every time you have been checked" log are the real markup off that screen. The rail item reads Organisation. The three tiers the launch document names are on it.

The company and the people on it. Thin in the build, in the builders' own word.

Inviting a colleague. Thin in the build, in the builders' own word.

People messaging people, and explicitly not an artificial-intelligence feature in this version. Whether the condition is a second AUTHORIZED user or simply a second person is not settled, and it is the builders' to answer.

Chat between authorized users is in the build, switched on by a second authorized user, and it is people talking to people rather than an assistant.

The same screen once a second person holds authority, which is the one thing this surface is for and the one state it did not have.

The setting that would let an assistant act on its own exists in the build and is held shut by the backend. Letting it open comes later.

Settings reaches it as Account security.

Account. Thin in the build, in the builders' own word.

The public page a buyer can check is named in the builders' own map of the way in.

What Settings is now: approval rules, notifications, account security, language. The rail's Settings item and the menu's Settings row both point here.

Settings. Thin in the build, in the builders' own word.

The person's own identity, separate from the company's, and what they personally hold. One press from the top bar on every screen: the profile menu's first row opens it, and so does Settings. Its second state, screens/S7-your-profile.html?as=collab, is the same page for a collaborator: a thinner middle card and no door into the company's credentials, which is the difference between the two people the demonstration shows.

The person's own identity, the Scout ID, and what they personally hold. Built 14 September 2026; it was a placeholder, and this file's own note used to say the certificate that would sit here comes later.

No build document names a notifications screen. It is here as part of the thin settings that are in the build, and it is drawn thin.

Signing in again, the other half of a sign-up that is chained end to end.

No build document names it. It is part of signing in and is drawn thin.

The setup card's second row opens this.

No build document names booking a verification call inside the product. It is here because the setup card's second row opens it, and it is a question still open with Maher.

No build document names an error set. Every screen that ships has these states, and they are drawn once, here.

The company's identity, and the credentials that sit behind it: the trade licence, the Chamber of Commerce membership and the legal entity number, then the two papers taken at sign-up and the one still to come. Rebuilt 14 September 2026 and back as a destination, having been retired on 10 September when it was only a number and a share link. Its way in is Your Scout ID, and the Organisation page.

The company's identity and the credentials behind it: the trade licence, the Chamber of Commerce membership and the legal entity number. Rebuilt 14 September 2026 and a destination again; it was retired on 10 September, when it held only a number and a share link.

The same desk after a fortnight of being taught, for the colleague in finance. Four things it watches for him now, and two decisions he and the authorised user are on together.

The same desk a fortnight after it opens. The roadmap of 13 September puts the collaboration layer in the fortnight after 30 September, so it is shown and marked as October rather than claimed for the build.

Need 3: the internal knowledge base the two paths are built on top of.

Reading the company's own documents is in the build; a screen for browsing that knowledge is October work. The framework asks for the browser at launch, and that is not yet settled between the two.

Need 4. No rail item: it is reached from the setup card's own progress meter on the desk and from the profile menu.

The progress map is October work. The framework asks for it at launch, and that is not yet settled between the two.

The guided path is October work. The framework asks for it at launch, and says it can follow in the same sprint.

The "Build your own" control was taken out. An open store is a later step; the catalogue is closed.

The gallery of assistants and building your own are October work. At launch the catalogue is closed.

Reached from one trade. No build document names document generation at all, so this is drawn and marked, not promised.

No build document names document generation at all, and Maher has doubted the capability himself. It is drawn and marked, not promised.

Superseded. The call now opens as a sheet from the setup card and from the identity page.

Superseded. The sign-up takes the password at its seventh step.

Superseded by the setup card.

Superseded by the setup card.

Superseded. Getting the identity is now a row on the setup card.

A state of a superseded screen.

Retired. One more surface for nothing, once the setup card carries the actions.

A door of a superseded screen.

A door of a retired screen.

A state of a retired screen.

Superseded. The conversation takes the whole screen now, rather than sitting beside the desk.