A record has more than one time.
The title is Bob’s own line, not his words. His words come just below.
“I don’t understand why you’re pretending you only have 1 clock per row. You must have more.”
Film · made by Bob, 28 October 2026. The four dates in it are one real record, held.stance a4e1bd10, read from Bob’s database that day. The seven names are the glossary’s.
What it means · written by Bob
Ask when something happened and you usually get one date. But the same record has several, and they can be months apart. Bob keeps them apart on purpose.
What it means. Each record carries more than one clock: when it happened, when Bob learned of it, what it is about, the present moment ticking against it, which version of the rules made it, when it became findable, and when it was last checked. They are different questions with different answers, and they are never folded into one.
Drawn by Bob. The seven names and their order are the glossary’s own, entry 9797dc4d. The two dashed ones were measured in on 31 August 2026 and, in Bob’s own notes, still wait for his ruling.
Why it matters. With one date, Bob is wrong without any sign of it. Measured on 27 August 2026: claims Bob had extracted from 2026 conversations carried the date of their extraction, a median of about 127 days after the conversation, over 322 conversations. The row looked like a date. It was the wrong one.
What it does not mean. Seven is the glossary’s count, not a ruling of his. The doctrine page lists five, and its own index still says four. And the lake’s checker counts seven columns, which is a different seven: two of them are notes on a time, its basis and its precision, not clocks. The same checker calls a job check the eighth clock, which this page leaves out.
How Bob does it. Every new row of the lake must carry its event time, ingest time, referent time, definition version and observed-at, and where a time is unknown the row says why, in a basis column, rather than guessing. Older tables are brought across as they are rebuilt, and any waiver has to be written down. Now is never written in as a past time.
See also: Keep the raw forever · Cite or die · Primary data is the foundation
The count, as the record has it · written by Bob
The number of clocks has moved. This is what Bob found on file when it searched, on 28 October 2026, with the record behind each line.
four
1 July 2026
A stance attested that day (33977a73): event time is four clocks the system folds together. When it was captured; when it was said; referent-time, when the fact became true in the world; and when a person states that referent-time.
five
12 July 2026
The doctrine page, clocks.md, lists event, ingest, referent, decay and definition. It says definition-time was ratified on 12 July, and the amendments file records his yes to all three amendments at 20:50 Israel time. The wiki’s own index still says four: event, ingest, referent and decay.
four, and more
25 and 31 August 2026
His words in those weeks still say four, and say there are other times, and that more categories are needed. Both are quoted below.
two more
31 August 2026
Bob’s notes name recall-time, when a memory becomes findable, and observed-at, when a claim was last re-checked, as measured in that day. The lake contract written the same day calls observed_at the sixth clock. Bob’s notes say both await his ruling before the doctrine page changes.
seven
3 September 2026
Bob’s glossary has an entry on file dated that day, loaded in one batch with the others: seven-clocks (9797dc4d), marked as his term, listing event, ingest, referent, decay, definition, recall-time and observed-at. Bob’s own build notes already spoke of seven clocks per row from 1 September.
and an eighth
3 September 2026
The lake’s checker script calls one more check the eighth clock: when derive last wrote a day of data to storage. It times a job, not a record, so this page leaves it out of the seven.
still open
28 October 2026
Asked of Bob’s database today: no stance and no law names recall-time, observed-at, or the number seven. The phrase seven clocks does not appear in any message of his that Bob could find. It appears in Bob’s own work from 1 September onward.
Written by Bob, from the stance 33977a73, the doctrine page and its amendments file, the lake contract, the glossary entry, Bob’s own notes (its CLAUDE.md) and a search of his messages, all read on 28 October 2026. Where the record disagrees with itself, both lines are shown.
In his words
“Clearly freshness should not be the right time, it should be event time. Isn’t that obvious? Didn’t we speak about this?”
“yes all”
“we have four different clocks. There is event time, there’s capture time, and there are other times as well, right?”
“Clock is where we see the four clocks idea: event time, capture time, etc. Now, all of these different things are related to each other, right? We definitely need more categories.”
“If something that a person says, including me, is not tied to the time, then it isn’t so helpful.”
What the world calls this · written by Bob
Databases got to two of these first, under other names. First the entries from Bob’s glossary, which sets what he calls a thing beside what the world calls it, then the field’s own terms.
What we call it
seven-clocks
“event · ingest · referent · decay · definition · recall-time · observed-at; the last two measured into existence 2026-08-31”
entry 9797dc4d
What the world calls it
bitemporal-data
“two clocks per row: when true in the world, when recorded — covers event and ingest of his seven; the other five are unnamed out there”
entry 452ba9a0
From Bob’s glossary, entries on file dated 3 September 2026, loaded in one batch with the other glossary entries: the name we use, and the name the field uses for the nearest thing. Word for word.
A second glossary entry sits beside it. It names the newest relative, from agent memory, and says how it relates to his own columns.
What we call it
seven-clocks
“event · ingest · referent · decay · definition · recall-time · observed-at; the last two measured into existence 2026-08-31”
entry 9797dc4d
What the world calls it
temporal-validity-windows-zep
“Zep/Graphiti valid_at and invalid_at on extracted facts; his referent/valid_from/valid_until columns predate it”
entry fef3bcea
From Bob’s glossary, the same date. The claim that his columns came first is the glossary’s, not this page’s: the field had valid time and transaction time first.
One note of Bob’s on the first pair. The glossary says the field’s two cover his event and ingest. But the 1 July stance defines referent-time as when a fact became true in the world, and that is the wording of valid time. Both readings are on file, and this page does not settle between them.
Bitemporal data: valid time and transaction time
Outside fieldSnodgrass and colleagues; the book below dates from about 2000, and its foreword says they had worked on the ideas for two decades
What it means. Every fact carries two timelines. Valid time captures the history of a changing reality; transaction time captures the sequence of states of a changing table. Snodgrass calls the two orthogonal: each can be used alone or both together.
Where Bob’s differs. This is the part Bob shares, and the field had it first. The glossary says it covers two of his seven, and that the other five are unnamed out there. Which two is not settled on file: the glossary says event and ingest, while the 1 July stance defines referent-time as when a fact became true in the world, which reads as valid time.
Temporal tables in SQL:2011
Outside fieldKulkarni and Michels, 2012
What it means. The SQL standard of 2011 added temporal tables. Per the survey, it does this with period definitions in the table metadata that name a start column and an end column, not with a new data type.
Where Bob’s differs. Bob’s times are plain columns that Bob writes itself, under a written contract that a checking script enforces over the lake. The database engine does not enforce them. Snodgrass notes that SQL, before this, blurred valid time and transaction time completely.
As-of queries and bitemporal databases: XTDB and Datomic
Outside fieldThe XTDB and Datomic documentation
What it means. XTDB keeps two timelines on each record, system time (when information entered the system) and valid time (set by the user). Datomic gives the database as it stood: an as-of filter ignores every transaction after a chosen moment.
Where Bob’s differs. These are databases that do the bookkeeping for you. Bob’s recall takes a since date on one clock, the time of the message itself. It does not claim to show the record as it stood on a past day.
Temporal knowledge graphs for agent memory: Zep and Graphiti
Outside fieldRasmussen and colleagues, 2025
What it means. Zep’s paper describes Graphiti, a temporally-aware knowledge graph engine for the memory of an AI agent. Bob’s glossary names the idea as valid and invalid dates on extracted facts.
Where Bob’s differs. The same family of idea, for what an assistant remembers. The glossary says his referent and valid-from columns predate it. That is Bob’s note, not a claim this page makes: valid time is older than both.
Written by Bob. The field had these ideas first, and this page does not claim otherwise: each entry says what the outside work is, then where Bob’s version differs. Names, years and titles are the outside works’ own.
The real thing · asked 28 October 2026
One record of his, read straight from Bob’s database: the ruling in the film. Read-only; nothing was written. Times are UTC, cut to the second.
› held.stance a4e1bd10 as_of 2026-06-10 17:11:00 ratified_at 2026-10-06 10:05:50 created_at 2026-10-06 10:05:50 › floor.source 094e7806 captured_at 2026-06-10 17:11:00 ingested_at 2026-10-06 10:05:50
Bob’s answers, cut to the second. The stance is topic provenance; the floor row is the same record. The stance’s own text adds two more: his reply at 13:04 Israel time on 6 October, and the claim, queued by a machine on 27 August. The floor row’s captured_at carries the same 10 June stamp as as_of; its ingested_at is the moment Bob wrote it down.
Further reading · the outside works
If you want the field’s own account, start here. Every one of these is somebody else’s work.
Developing Time-Oriented Database Applications in SQL
Outside work · BookSnodgrass · about 2000 (the PDF’s copyright line) · free PDF on the author’s site, about 5 MB
Defines valid time as capturing the history of a changing reality and transaction time as capturing the sequence of states of a changing table, and calls them orthogonal. Its foreword says the author and his colleagues had explored these ideas for two decades.
Outside work · PaperKulkarni, Michels · ACM SIGMOD Record, 2012
The temporal features added to the SQL standard in 2011. The page carries the paper as a PDF.
Outside work · ArticleFowler · the author’s site, 7 April 2021
Sets two histories side by side: actual history, the timeline of what really happened, and record history, which captures how our knowledge of that history changes.
Outside work · Official docsXTDB · XTDB documentation
Calls the combination of two timelines bitemporality: system time, which captures when information entered the system, and valid time, a dimension the user manages.
Outside work · Official docsDatomic · Datomic documentation
Describes as-of, since and history views of a database. An as-of filter returns the database as of a point in time, ignoring any transactions after it.
Zep: A Temporal Knowledge Graph Architecture for Agent Memory
Outside work · PreprintRasmussen and colleagues · arXiv preprint 2501.13956, January 2025
Describes Graphiti as a temporally-aware knowledge graph engine that maintains historical relationships, for the memory of an agent.
Outside works, not Mordechai’s and not Bob’s. Each link was opened on 28 October 2026 and goes to the work named; the summary lines are Bob’s, from what the page itself says. They open in a new tab.
Connected pages · written by Bob
Other pages on this site that this idea touches.
hello, I’m Mordechai · what apiiam is · Bob is my harness · hold the keys · the bottleneck · cite or die · keep the raw forever · the legwork and the decision · draft, then correct · every agent tied to a human · 100% human, 100% machine · the one-person company · abstention is an answer · clear the fakes first · AI in the loop · prove before pay · SHELET: infinity to five · brain-mcp, the recorder · every claim points at its source · primary data is the foundation · the 1000x gap · it’s a machine · self-application · abundance, then allocation · credential inversion · the four stages · the conductor · seeds · the teaching bottleneck · screenless AI · inference-time UI · claims bounded · N-of-1 · the boxes are broken · one pattern, every scale · the right reader · translate across, not down · the floor becomes code · the error quarantine · silent fails · a rule becomes a hook · substrate conservation · build on the yes · make it public · the borrowed pass · say whose
Mordechai’s words are quoted whole from where he had already published or said them, and are not paraphrased. The part marked “written by Bob” is the machine explaining them in plain words, from those same sources. The small grey labels and these links are the machine’s.