Architecture

Architecture deep-dive

Layers, data flow, and the edges of what exists. Every box states whether it is built in code, planned or absent.

Status labels: Live (checked directly, dated) Built in code; not independently verified In progress Planned, not shipped Open decision or unverified Not offered / no claim made

1. Layers

Layered view of Exchange TerminusFour layers: delivery, desktop shell, application, and data. The data layer is inside the app. A separate account host is used only for a read-only check and pictures.DeliveryInstaller filehostedDelta updatescodedPublic routeundecidedDesktop shellElectron, Windows x64Self-extracting portableLocal file serverserves /media/ApplicationGlobe (Three.js)mock-litTool railand boardsProject locklocal saveSign-in and hatsData (inside the app)Catalog indexnodes + edgesOverlay packsPicturesCommons, creditedCompleteness dataBuilt in code, not independently verifiedData or sourcePlanned, not shippedNot built or refused

The only online identity dependency is the read-only session check.

Read from the project files on September 30, 2026. Nothing here was run end to end for this site.

2. Session and identity

Verify-only sign-inAfter sign-in on the account host, the app sends a read-only session check with a bearer token. A valid session returns the account email; otherwise it returns no. A hat is chosen only after the session verifies.Sign inon account hostSession checkread-only GETSession valid?yes / noChoose hatResearch · Sell · BothBuilt in code, not independently verifiedData or sourcePlanned, not shippedNot built or refused

The app never creates accounts or sessions and never deletes anything on the account host.

  • A session lasts seven days.
  • The token is read from a shared local account file or the running process. Remember-me stores the verified token locally.
  • Project locks contain no secrets. A lock is tagged with an email only if a token already exists.

3. Data flow for a typical question

From a search to a pinA search goes through the catalog index and the active filters, returns at most 80 pins, and the map paints only layers that are actually bound and drawn.Searchmap-scopedCatalog indexplus filtersUp to 80 pinsPaintonly bound layersBuilt in code, not independently verifiedData or sourcePlanned, not shippedNot built or refused

Nothing in this path calls a public data provider live. The data is baked into packs.

No live calls to public data providers were identified. Overlay data, catalog data and pictures are static files inside the app. That is why dated layers are labelled with the year or month they are pinned to.

Dated layerPinNature
Conflict events2025Dated, not live
Trade partner familiesJune 2026Statistical partners
Sea freightMockPlaceholder from a container index

4. Pictures

Picture loader orderThe loader tries bundled media first, then a local media folder, then a folder next to the portable app, then the media host. A missing picture shows as empty.Bundled mediaLocal media folderFolder next to appMedia host404 = emptyBuilt in code, not independently verifiedData or sourcePlanned, not shippedNot built or refused

Pictures are identification aids with per-file credit. They cannot be attached to an offer.

5. What the architecture does not contain

Not presentNote
ET user databaseThe account host is the only account source. Hats are capability flags.
ET payments or billingNone.
ET server storing user dataNone; desk state is local.
Web, mobile or other OS surfaceNone; Windows x64 only.
Third-party APIs, CRMs, ERPs, payment rails, email deliveryNone exist.

Security posture and limits: Trust model, Not claimed. Release state: Delivery and updates.

Questions about how it works?

The help center answers 1,000 concerns, architecture included.

No public download yet. Ask to be told when access opens.Request access