The demonstration
What you will see, screen by screen
One complete task on a fictional file: you open folders, you describe the deliverable, the agent proposes a plan, gets to work, and hands you a document to approve or throw away. Six moments, in the order they happen.
- On a fictional file, never on yours. The demonstration runs on an invented company. No real data is used, here or on a video call.
- Nothing is sped up or staged. What a demonstration shows is what the installed software does, exactly as it ships.
Step by step
Six moments
At each moment, the same question: what does the software decide, and what do you decide?
You open the folders for the task
You pick the folders the agent works on — a bar keeps them in view at the top of the screen. It sees nothing else. Folders you have put on the red list stay unreadable to it, and that list is enforced by the software, not by a house rule: how that works.
You describe the deliverable, in one sentence
“A summary of these documents for the insurer, in Word, two pages.” No form, no setting: a sentence. If the format or the recipient is missing and the answer depends on it, the agent asks before writing anything.
The agent submits its plan, and waits
The Plan button is on: before touching a single file, the agent sets out what it intends to do, step by step. You approve, you correct, or you stop there. This is where you see that delegating a task does not mean losing sight of it.
It works in the open
You see what it reads, what it looks for, what it writes, and its reasoning when the model produces any. Nothing happens in a black box. Meanwhile, the computer only talks to a handful of known destinations: the list, and how to check it yourself.
The document is handed to you, off to one side
A new document does not go into your folders: it waits alongside them, with four actions — preview, open, approve, delete. An automatic check has already run before you see it: does the file the agent announced exist, and is it in the format you asked for? That check approves nothing on your behalf; it sends the agent back when the answer is no.
You approve — and you can still go back
If you approve, the document is copied into your folders; if you refuse, it is deleted. A correction to a document that already exists applies straight away — that is what you expect of a correction — and the original is set aside first, in a recycle bin, with a button to undo. All the while, the register of processing activities fills in automatically: the file it produces, for a fictional practice.
Off screen
What a screen cannot show
Three things matter most to a practice, and none of them shows up on a screenshot. They can be checked — which is why each has its own page.
- Where the content goes. The computer contacts a closed list of destinations, and you can check it yourself with the Windows Resource Monitor: what leaves the computer, and where to.
- Who builds the compliance file. Register of processing activities, processing policy, per-run log: the application produces them as a dated document, and how the burden is shared is set out line by line.
- What holds when nobody is watching. The technical measures — processing in Switzerland, content never read by the publisher, edits to an existing document that stay reversible, web tools off by default — are named and detailed on the Security & confidentiality page.
The same thing, on your own work
A video demonstration starts from your own tasks — the ones that come round every week — and runs on fictional data, never on your files. Allow thirty minutes.
LEMIA is published in Geneva by Colin Thompson. The publisher delivers, installs and maintains the software; it carries out no work on your data and never reads its content.