Time Travel

Your company, on any day

Pick a date and the graph rebuilds as it stood. Every fact keeps its full history, so what was true, who approved it, and what your agents knew when they acted is one click away.

Pick a date

The fact base rebuilds as it was

One fact, one year. Drag the date and watch the version that was live, who approved it, what it replaced, and who read it on the way.

The record

A fact is only trustworthy if you can see behind it

A source of truth that forgets is a rumor with a login. In NOAN the history of a fact is part of the fact: its versions, its approvers, its dates. That record is what makes a single fact base safe to run a company, and a fleet of agents, on.

01

Every write is a version

A fact is never overwritten. Each change creates a new version and the old one stays, with who approved it and the day it became true. Nothing is thrown away.

02

Restorable, in the app and over the API

Open a fact's history in NOAN and bring any version back. Over the API, every fact's versions are one GET away, so an agent can read the record too.

03

The whole company, on a date

Time Travel runs across the Company Graph: facts, contacts, notes, assets and the connections between them, as they stood on the day you pick.

04

Held for review

A workspace can require approval on fact changes. A write from a person or an agent waits for a human before it becomes ground truth.

Running agents

What the agent knew when it acted

An agent is only accountable if you can reconstruct its inputs. On NOAN every agent reads the facts before it acts and writes back to the board after, so a decision carries two records: what was done, and what was true at the time. Time Travel puts them side by side.

Ground before generating

An agent on NOAN reads the facts live before it writes a word, so every output is built from what was true at that moment, not from a prompt pasted in months ago.

Write back after

It claims the task, leaves a note, moves the card. The board holds what was done and the facts hold what was known. Together they are the audit trail.

Question any decision

If an agent made a call three weeks ago, pick that date. You see exactly what it knew and whether the facts it read were right, without guessing from a log line.

A sample. The people are made up; the grammar is the app's. Reads in teal, writes in amber, and the answer comes from the record rather than from anyone's memory.

The safety net

Agents can write. Nothing is lost

A write over the API replaces the whole fact, and an agent can get that wrong. The history is the reason that is recoverable: open the fact, pick the version that was right, bring it back. The mistake stays on the record too, with who made it and when.

A fact's versions, over the API
GET /v1/facts/{factId}/versions

  v4  2026-08-20  approved by Neal    annual option added
  v3  2026-06-12  approved by Neal    price raised
  v2  2026-03-03  approved by Neal    seats raised to 5
  v1  2026-01-14  approved by Neal    first written

A sample, in prose rather than JSON. Every version, every approver, every date, readable by a person in the app or by an agent over the API.

In the app

Three steps to any day

01

Open the Company Graph

From the brain icon in the Intelligence widget on your Activity page.

02

Pick a date

The graph rebuilds as it stood that day: every fact, contact, note and asset, and the connections between them.

03

Read the record

Open any fact for its versions, who approved each one, and when. Bring an earlier version back if you need to.

Start a record worth keeping

The history of every fact comes with the fact base, alongside the API, MCP, and unlimited keys. Write down one truth today and you can travel back to it next year.