Evidence and time travel
A store that knows its own past. Every entry carries two dates, outdated statements are superseded rather than deleted, and every change appears in your workspace log.
Anyone using AI in production will eventually be asked what a decision was based on. An ordinary knowledge store cannot answer that: it only knows its present state. knowmind keeps every statement with two time markers — since when it holds, and since when the system knows about it. The same question therefore returns a different answer for 14 March than it does for today, and both are on the record.
You can show what held at which point in time
When you update a fact, the old version does not disappear. It gets an end date, the new version a valid-from date, and the two stay linked. A payment term that was thirty days in March and has been fourteen since June is therefore correctly retrievable for both dates. Separating the time from which something holds from the time the system learned about it is called bi-temporal storage.
Same question, different date, the right answer
Your connected AI tool can attach a date to any question. What comes back is only the statements that were valid at that point. For follow-up questions, audits and disputed cases you answer with a dated state instead of from memory.
In an audit, you answer with a date
Who stored, changed, linked or retrieved what, and when: your workspace audit log records write operations and the retrievals made by your AI assistant. You read it in the interface and download it as CSV or JSON. Retention runs from 30 days on Private through 90 days on Pro and 12 months on Team up to 24 months on Business.
The state from two years ago is still there
Outdated entries are demoted and superseded, and kept while that happens. There is a practical reason for it: what looks like ballast today is sometimes, two years on, the only evidence of how a decision came about. Anyone who deliberately digs gets the old state back.
The occasion: the EU AI Act
On 2 August 2026 the transparency obligations under Article 50 of the AI Act take effect. For high-risk systems, Article 12 requires automatic logging over the entire lifetime, and Article 26(6) requires those logs to be kept for at least six months. Whether your particular use falls under this is for your compliance officers to assess. knowmind supplies the basis for being able to answer if it does.
Technical detail
- Validity period per statement, separate from the time it was recorded
- Superseding instead of deleting, with a reference to the version replaced
- Timestamps are set on the server
- Log per workspace, export as CSV or JSON
- Retention from 30 days to 24 months depending on plan, longer for Enterprise