HOW IT WORKS · ONE EXAMPLE

What happens to the document you add?

Follow one shop policy from a file on your computer to the text your assistant uses. The example below explains the process; it does not run a live MESA query.

01

You add a text file.

Save the policy as policy.txt, then add it with mesa add. MESA keeps the text and a reference to this source.

mesa add policy.txt --source file://policy.txt
policy.txtVersion 1
“Returns are accepted within 14 days. Keep your receipt.”
02

MESA prepares the text for search.

It divides the document into smaller passages, keeps their source and processes the work in the background. Adding a file starts this work; search it once processing is complete.

MESA Core
  1. Source filepolicy.txt · v1
  2. Stored textReturns: 14 days. Keep the receipt.
  3. Source linkEvery passage points back to this file.
03

Your application asks a question.

MESA searches the data this application is allowed to read. It returns the relevant text, document and version. Your application’s model uses that text to write the answer.

mesa search "returns"
How long do I have to return it?
TEXT FOUND BY MESA
“Returns are accepted within 14 days.”
Sourcepolicy.txt · v1

IF THE DOCUMENT CHANGES

The new version becomes the current source.

Suppose the shop changes its return policy. Once the new document version is processed, current searches use the new information instead of the superseded version.

Old version · history14 dayspolicy.txt · v1
New version · current30 dayspolicy.txt · v2

To update or delete a source in your application, follow the document lifecycle API. Document API →

What does the first installation give you?

Word search works without a model. To find similar meanings, configure a model provider. For model-based relationships, also enable extraction explicitly. MESA returns source material; it does not write the final answer.