Skip to main content

Asking it to remember

Plain words are enough.

— Remember: called Olympus Moscow, delivery slips by two weeks, spoke to Ivanov, he runs logistics there.

The assistant writes down two things:

  • the event — your account, in your words, dated today
  • the facts — "Ivanov works at Olympus Moscow", "Ivanov runs logistics", "delivery has slipped by two weeks"

The event stays as it is forever. The facts are what is later found by meaning and linked into the graph.

Worth saying out loud​

Dates. "He has been there since 2019" beats "he works there": with no date the fact gets today, and a question about 2020 will not find it.

Who is who. "Ivanov is logistics at Olympus" turns a person into an entity of their own rather than a word inside a sentence. Only then does "who do I go through" reach them.

How it ended. "We stopped working with them in March" closes the old facts by a date. Otherwise they stay true as of today.

Worth writing down​

Anything you will come back to with a question:

  • agreements and their terms
  • who works where, who reports to whom, who knows whom
  • why something was decided that way — especially a decision not to
  • findings that are expensive to get again: registration details, codes, restrictions

Not worth writing down​

  • a retelling of what is already in a file or an email — write down where it lives instead
  • the momentary: "currently checking the build"
  • passwords and keys; if one lands in a note, ask for the whole event to be deleted — it goes with every fact drawn from it

Files​

Links can be attached to an event and to a single fact:

— Attach the scan of the certificate to that note: link

mnemos stores the link, not the file. The scan stays where you put it.

Checking what landed​

— Show me what you wrote down about Olympus.

The assistant lists the facts standing on that company. If something is wrong — corrections.