← Catalog

Pragma FDE — the field visit, dictated

An engineer walking a plant has his hands and his eyes taken. He cannot type. He speaks: the note leaves time-stamped, the team files it by workshop, and the prepared questions get their answers one by one. Six tabs, and a disc you hold with your thumb.

fr.imachine.pragma.fde · Android 8.0+ · Kotlin and Jetpack Compose · 9 MCP tools · no public store: your instance serves its own build.

What it covers

Visit opens on the customer and his past visits, then becomes the dictation screen for the visit in progress. Questions holds what was prepared before going, to read out and answer on the spot. Journal shows the notes as the team filed them, workshop by workshop. Docs opens every file of the customer folder. Team is the conversation with the whole team, before and after the visit. WIP holds its runs.

Two ends of the same team answer here. During the visit you talk to the field worker, which answers in seconds. Before and after, you talk to the team: the brief, then the report.

Dictate rather than write

Hold the disc, say the note, release. The server transcribes with Whisper, the worker files it under the current workshop and answers what it did. A transcript that is only noise — under three characters, or a sentence speech recognition invents over machine din — reaches neither the worker nor the journal: the screen asks you to say it again. The screen stays on for the whole visit: you do not unlock a phone between two notes.

Four spoken orders sit under the microphone — recap, sheet, questions, summary. And when the workshop is too loud to dictate, a field takes the note typed.

Nothing is lost

The app writes every dictated note itself, in a file of its own, before the worker sees it. The journal counts both: the notes it filed, and the notes you dictated. When the two differ, the screen says so and names the file that holds the rest. The raw file is the one that settles it.

The screens

Interface preview: the published screens are in English, the shipped app speaks French. A cross-team request is open to make the apps bilingual.

Visit

Visits — one folder per customer, one sub-folder per visit. The customer comes from the customer file; the site names the visit. A past visit reopens where it stopped.
Pick a customer — the list is the customer file, re-read every time the screen opens. A customer is created in Pragma Commercial: one source, not a second list to keep in step.
Visit mode — hold the disc, dictate, release: the note leaves time-stamped and the agent files it. The halo follows the input level. The screen stays on for the whole visit, and the field is there when the workshop is too loud to dictate.

Questions

Questions — prepared before the visit, attached to the customer, not to one visit. The answer just recorded stays under your eyes, so the transcription is checked without leaving the list.
Ask the question — set in large type, to be read out to the customer, with what the answer decides. Dictate the answer and the question leaves the to-ask list.
Correct an answer — speech recognition mishears a name or a figure. Saving rewrites the last answer; removing it puts the question back in the to-ask list.

Journal

Journal — the notes as the agent filed them, workshop by workshop. The app also writes every dictated note in a file of its own, so the counter shows when the agent missed one.

The Docs, Team and WIP tabs run the screens of the shared module. Docs and WIP are shown on Pragma; Team runs the agent chat panel, shown on Pragma Commercial.

A folder per customer, a file per visit

A customer comes from the customer file — the one the sales desk keeps, served by the same MCP tool. There is no second list to keep in step: a customer is created in Pragma Commercial.

Each visit is a folder dated and named after the site, holding the journal and the raw notes in Markdown. The prepared questions sit one level up, in the customer folder: they belong to the customer, not to one visit. The team that writes the report after the visit reads those same files. Nothing stays on the phone.

The platform that serves those tools is described in MCP Infrastructure.

Yours, on your own servers

The app is a configuration of the same shared module as the other two: its team, its field worker, its screens. Another trade means another configuration, on your own instance.

Talk to an engineer