How Sentra keeps company memory current
Every fact in Sentra keeps the source it came from and the time it happened. Newer evidence wins over older evidence, corrections are kept as dated facts, and edits people make are never overwritten by a later sync.
In short
- Each fact is linked to one source record, such as a meeting, an email thread, a Slack conversation or a CRM record, with the time the event happened and the time Sentra stored it.
- When a source changes, Sentra rebuilds the facts from that source, so an edited document or an updated ticket does not leave old facts behind.
- Facts a person edited or deleted survive every later sync and are never brought back.
- When sources disagree, Sentra answers from the newer one and says that the older one disagrees.
Why search tools serve stale answers
Enterprise search indexes documents. When a decision changes in a meeting or a Slack thread, the old document still ranks, and nothing tells the reader it is out of date. Companies that tried search for this told us the same thing: it could not retire stale content, and re-indexing to fix it was costly.
Sentra stores facts instead of documents. A fact is a short statement, such as who owns an account or when a launch moved, tied to the record it came from and the moment it happened. That makes time a property of every answer, not something the reader has to guess.
What every fact carries
Each fact is linked to a source record that holds the source type, the source's own ID and the event time. For a meeting, the event time is when the recording started. For an email or message, it is when it was sent. Sentra also records when it stored the fact.
- The source, so every answer can cite where it came from
- The time the event happened, so answers list the newest facts first
- The entity it is about, such as a person, account, project or deal
- Whether a person has edited or deleted it
What happens when a source changes
When Sentra processes a source again, for example an edited document or a ticket with new comments, it replaces the facts from that source with a fresh set. Facts never pile up from old versions of the same record.
The exception is anything a person changed by hand. A fact someone edited keeps their edit, and a fact someone deleted stays deleted, however many times the source is processed again.
How corrections work
People correct Sentra in chat, in plain language. Sentra finds the entity the correction is about, shows a confirmation card with exactly what it will record, and writes it only after the person confirms.
A correction is stored as a new dated fact, for example that as of 4 November a named person says the launch is now in December. The earlier fact is not erased, so the history of what changed and who changed it stays visible. If the person correcting is not the owner of the item, Sentra records it as a proposal pending the owner's confirmation rather than as a decision.
When sources disagree
When an older and a newer source conflict, Sentra answers from the newer one and notes the discrepancy, and it flags facts that are more than 30 days old when they carry the answer. Summaries built on top of facts, such as the live view of a project, are regenerated as facts change and are marked stale or superseded rather than left to drift.
Frequently asked questions
Does Sentra delete old facts when something changes?
Sentra rebuilds the facts from a source when that source changes, so old versions of the same record do not linger. Corrections made in chat are kept as new dated facts alongside the earlier ones, so the history of what changed stays visible.
Can a later sync overwrite a correction someone made?
No. A fact a person edited keeps the edit, and a fact a person deleted is never brought back by a later sync.
How does Sentra decide between two sources that disagree?
It prefers the newer evidence and says that an older source disagrees, citing both, so the reader can see the conflict rather than receive a silent guess.
How is this different from re-indexing a search tool?
A search index returns documents ranked by relevance, whatever their age. Sentra returns facts with their source and date, newest first, and rebuilds them when the source changes, so out-of-date knowledge is not served as current.