Edmund Documentation
/USER MANUAL

Reading answers & citations

How to read an Edmund answer: watch the agent search a real source, tell a document answer (with Source links) from a database answer (a table), follow a Source to the original, and rate the reply.

Everyone Last reviewed July 2026

Every Edmund answer is grounded in the knowledge attached to the project you’re in — its documents, PLC programs, maintenance journals and any connected database. Two things make an answer checkable: you can watch which source Edmund searches, and a document-based answer links each claim back to where it came from.

A document/PLC answer: a status row shows the agent searching, each claim carries a Source link, and thumbs at the end let you rate the reply.

Watch the agent work

Before the answer appears, a status row shows what Edmund is doing — for example Hledám v databázi (searching the database) or Hledám v denících (searching the journals). That row is your signal that Edmund is really searching a source, not answering from general knowledge. Open it to see the exact query it ran. For what each agent does, see How Edmund searches (agents).

Two kinds of answer

The other kind of answer — results from a database, shown as a table.

What an answer looks like depends on where it came from:

  1. From documents & journals — manuals, drawings, maintenance-journal records. You get a written answer, and each statement carries a Source link back to the exact record it came from.

  2. From a connected database — stock, parts, fault logs. You get a results table plus a short summary, pulled live from the database.

Tip

A database answer is a live lookup, so it shows the data itself rather than per-row source links. Document and journal answers are where you’ll see Source links to follow.

Follow a source

On a document or journal answer, open a Source link to jump to the original record and confirm the answer against it before you act.

Warning

For a safety step or a torque value, open the source and read it yourself — don’t work from the summary alone.

Only readable sources can be used: a document marked No text won’t appear in answers until it’s fixed — see Documents & PLC programs.

When Edmund doesn’t know

If the project’s knowledge doesn’t cover your question, Edmund says so instead of inventing an answer — a clear gap is more useful on the floor than a confident guess. Tell whoever looks after that machine’s knowledge so they can add the missing manual, drawing or record.

Rate the answer

At the end of every answer are thumbs up / thumbs down (Ohodnoťte odpověď). Rating takes a second and tells the team what’s working — where it goes is covered in Feedback loop. You can keep asking in the same chat to go deeper; Edmund often suggests the next step itself.