Ask what you knew, and promised, on any past date.
Nexus stamps every claim with two clocks, when it was true in the world and when Nexus learned it. Ask a question as-of any date and get back what was actually true then, cited, plus which of those facts have since been superseded and the note that changed them.
Run Nexus- 1
Describe the task
Nexus stores your knowledge bi-temporally: every fact it extracts carries a valid time (when the claim became true in the world) and a system time (when Nexus first read it). When a later note contradicts an earlier one, Nexus doesn’t overwrite history, it marks the old claim invalid from that date and links the new one. That means you can ask a plain-English question as-of any point in the past and get the answer that was actually true then, not the answer that is true now.
The tighter you frame the window, the sharper the recall. Tell Nexus which date to answer as-of, whether you mean what was true then or what you knew then, and how you want each claim cited, and it holds that framing across every note in the graph, so a promise made in Q1 and quietly reversed in Q3 shows up as exactly that.
Using the graph, answer as of March 31: what had we promised investors, and who owned each commitment? For every claim: - Show whether it was still valid on that date or already superseded - Separate what was true then from what we only learned afterwards (system time) - Cite the source note and date each promise came from Then show me which of those promises are no longer valid today, and the note that changed them.
- 2
Give Nexus context
In a Nexus workspace, point the run at the notes, board updates and investor memos that hold your commitments, and Nexus stamps each extracted claim with its valid time and system time as it reads. No manual dating, the date in the note (or its modification time) becomes the valid time.
Give Nexus a cutoff or reference date when you query and it filters the graph to the claims that were valid then. State whether you mean valid time (what was true in the world) or system time (what you had actually recorded by then), the two answers can differ, and Nexus keeps them straight.
Required contextA source location, a drive, vault or folder of notes, updates and memos to indexA reference date or window to answer as-of, so Nexus knows which slice of history to readOptional contextA glossary of internal codenames, so a commitment referenced three ways resolves to one claimA Connected-mode team vault, so the whole leadership team queries the same dated historyA note on whether you mean valid time or system time, so ambiguous “what did we know” questions resolve the way you intendinvestor-updates folderboard-memos folderinternal-glossary.md - 3
What Nexus creates
Nexus reads every note, stamps each claim with valid and system time, and marks a claim invalid the moment a later note contradicts it. You get a graph you can query as-of any date: ask what was promised on March 31 and Nexus returns the commitments that were valid then, each cited to its source note, plus a separate list of the ones that have since been superseded and the note that changed them.
From Nexus: Indexed 612 notes and updates into one bi-temporal graph, queryable as-of any date.
2Clocks tracked (valid + system time)18Claims superseded since Q1100%Answers cited to source notesPromises valid as of Mar 314 commitmentsCommitment Owner Valid from Source Ship self-serve by Q3 Renata Voss Jan 18 series-a-update.md Hold headcount at 40 Marcus Lin Feb 02 board-memo-feb.md EU data residency live Priya Anand Mar 09 security-review.md Superseded since that date2 reversedClaim Valid until Superseded by Date Hold headcount at 40 May 20 Approved 6 new hires board-memo-may.md Self-serve by Q3 Jun 11 Slipped to Q4 after security review q2-retro.md "The headcount promise was valid on Mar 31 but a May board memo reversed it, so it reads as valid-then, invalid-now. Want me to trace every commitment that changed between Q1 and today, each cited to the note that moved it?"
- 4
Follow-up prompts
Diff two dates to see what changed
Nexus can answer the same question as-of two dates and show only the delta, the claims that became valid, were reversed, or shifted owners in between, each cited to the note that moved it. It is the fastest way to prep a “what changed since last quarter” review.
Compare the graph as of Mar 31 and today. List every investor commitment that was added, reversed, or reassigned in between, and cite the source note and date for each change.
Ask what you knew versus what was true
Because Nexus tracks both clocks, you can ask the harder question, on a given date, what had you actually recorded, even if the fact had been true for weeks. Useful when you need to show what was knowable at decision time, not with hindsight.
As of April 15, what did we know about the security-review delay, by system time, not what turned out to be true later? Cite the note and the date we recorded each fact.
Re-index when new updates land
When new memos or updates land, re-point Nexus at the source and it folds them into the existing graph on your next run, stamping the new claims and invalidating any they contradict. There is no proactive sync, you re-run the index whenever you want the history current.
Re-index the investor-updates folder and fold in any new memos. Show me which prior commitments are now superseded, each cited to the note that changed them and the date it took effect.
- 5
Tips and troubleshooting
Name the date, and which clock you mean
Valid time and system time answer different questions. “What was true on March 31” reads valid time; “what had we recorded by March 31” reads system time. State which one and Nexus never conflates the world with your notes about it.
Dates come from your notes, so date them
Nexus uses the date inside a note, or its modification time, as the valid time. An undated memo anchors to its file timestamp, which can misplace a claim on the timeline. A dated line at the top of each note keeps the history honest.
Contradictions are a feature, not an error
When two notes disagree, Nexus keeps both and marks the older one invalid from the contradiction date, rather than picking a winner. If an answer looks surprising, ask for the superseding note, the reversal is usually the thing you wanted to catch.
Ready to try it yourself?
Point Nexus at your notes and updates, name a date, and ask what was true, and what you had promised, exactly as the graph stood then, every claim cited to the note it came from.
Run Nexus