vivome is not a RAG chatbot. It's technology that turns records into structure

In plain words

RAG (retrieval-augmented generation)

In plain terms — A technique where the AI searches for relevant documents and pastes them in as reference before writing an answer.

In vivome — vivome doesn't rely on it — instead of searching documents later, it structures your records the moment they're saved.

Ontology

In plain terms — A predefined map of concepts: what something is, what properties it has, and how it connects to other things.

In vivome — vivome's ontology is its 10-domain codebook: emotion, body, symptoms, intake, activity, and more.

Event code

In plain terms — A standard name tag attached to each piece of a record. Different wording, same meaning — same tag.

In vivome — “My head is throbbing” and “have a headache” land on the same headache code, so they aggregate together later.

In plain words

Rule-based engine

In plain terms — A program that finds expressions in a sentence using predefined language rules. Unlike AI, it never guesses, so the result is always the same.

In vivome — vivome's on-device engine that classifies and saves your record the instant you write it.

On-device

In plain terms — Processing happens inside your phone, not on a company server (the cloud).

In vivome — Tagging and 110+ insight computations run on the device by default — which is why they work offline.

LLM (large language model)

In plain terms — An AI model, like ChatGPT, that understands and generates sentences.

In vivome — In vivome it plays a supporting role only: enriching classification and phrasing results that were already computed.

F1 score · golden set

In plain terms — F1 is an accuracy score that checks both misses and false tags; a golden set is an answer key labeled by humans.

In vivome — vivome runs a continuous regression gate that blocks any code change scoring below F1 82% on the golden set.

In plain words

Zero-knowledge

In plain terms — Data is locked on your device and only you hold the key — so even the company running the server can't know the contents.

In vivome — vivome's sensitive-data vault works this way: the server keeps only unreadable ciphertext.

XChaCha20-Poly1305 · Argon2id · BIP39

In plain terms — Not homemade cryptography — three open standards long proven in secure messengers, password protection, and crypto wallets.

In vivome — They lock the vault (XChaCha20-Poly1305), derive the key from your password (Argon2id), and back the 12-word recovery kit (BIP39).

Fail-closed

In plain terms — A design whose default is locked until explicitly allowed — the opposite of ‘open first, opt out later.’

In vivome — External AI integration ships off, so before consent no cloud call happens at all.

In plain words

Hallucination

In plain terms — When AI confidently makes up facts that don't exist — dates and counts included.

In vivome — vivome computes dates and counts by aggregating records, not by the model — removing the path to invention itself.

Deterministic engine

In plain terms — A computation with no guessing: the same input always produces the same output.

In vivome — vivome's 110+ insight engines work this way; only one uses a language model.

In plain words

Anonymous-first onboarding

In plain terms — Letting you use the app's features right away, without creating an email or password. An account gets linked later, only when you need one.

In vivome — vivome lets you start recording the moment you open the app; you link an email later, if you ever want to view your data on another device.

Device secure storage (Keychain/Keystore)

In plain terms — A locked compartment your phone's operating system provides, which even the app itself can't casually read out. The same kind of storage password managers rely on.

In vivome — The zero-knowledge vault's decryption key lives here — it is never transmitted to the server.

Refuse-before-mutate design

In plain terms — A design where, on hitting something ambiguous or risky, the system stops instead of making its own call and pushing through.

In vivome — When two accounts' encryption keys conflict in a way that can't be safely auto-merged, the account link is refused outright.