How Loresis Logistics is built
One web app on one server. Each person who signs in gets a private workspace. The Logistics tab turns a pile of shipping documents into a port-review report: a Python pipeline reads and measures every page, and Claude reviews each deal like the historic report did. Around it sits the full Loresis assistant: chat, voice, mail, calendar, Telegram, meetings, dashboards and knowledge.
Three ideas shape everything: the LLM does the thinking, code provides tools and safety; nothing goes out without your yes; and failures are shown, never papered over.
The whole system on one screen
Read it top to bottom: people reach the front door, the app checks who they are and opens their workspace, engines do the work with Claude and Python, and everything is remembered in files on one volume. Outside services sit on the right.
At rest the map shows the main flow. Hover a box to see all of its connections; click it for the full story.
From a pile of PDFs to a port review
Eight steps, four actors. Python does what must be exact and repeatable (reading, OCR, arithmetic, drawing marks); Claude does what needs judgement (which documents form a deal, what contradicts what). Click a step or any cell.
An analysis's life
“Add documents” on a finished analysis creates a new analysis with the same files plus the new ones — the earlier result never changes, so history stays navigable. The historic review of 01.10.2026 cannot be deleted or extended.
In review — not on main yet
The assistant: skills + tools, then your yes
Claude decides how to answer; it can only act through 75 tools in eight families. Text chat and voice share the same catalog. Skills are written instructions for a kind of work — the dashboard skill, the knowledge skill, and the logistics review method (which has its own six reviewer tools).
Every outgoing action is a proposal first
Gmail, Google Calendar, Outlook and Telegram writes exist in exactly one file, src/lib/executor.ts, reached only from an approval. Browser tasks have their own “Approve & run” button with a $1 cap. GitHub and data connections are read-only by construction.
Every request finds exactly one workspace
Seven gates between the internet and your data. Each one fails closed with a visible reason. This is application isolation in one process — not a separate machine or encryption key per account.
Where everything is stored
No external database: SQLite files and plain folders on one Docker volume. One folder per workspace makes isolation, backup and deletion simple. Expand the tree.
Tables and keys
Two machines, one product
Code is built where the developers and the Claude login live; it runs on a dedicated production server that accepts SSH only from the development host. Moving lines are what flows between them.
The codebase by size
Every rectangle is a folder or file, sized by lines of code, measured from Git at the commit above. Click to zoom in; use the path to zoom out. Archived design prototypes are left out.
What mapping turned up
Facts noticed while reading the code, docs and server for this map. None was changed by this report.