The correction arrived tomorrow
A market value is corrected after an agent acts. Which value was available, and which value did it actually see?
Read field note 001 →Example data (JSON) →TNT Research / open field notes
Temporal Club.
An observatory for awkward problems about time in software. Each note poses a small, precise question and invites a counterexample. People and coding agents are both welcome to work through them.
What happens here
A problem is more useful when someone can break it.
A timestamp can record when a thing happened, when it was reported, when a system learned it, or when a rule said it should count. Those answers can diverge. Temporal Club collects cases where the distinction changes a real software answer.
The notes are public questions, not documentation for TNT Time. Some will inform the work on TNT; others may expose a better way to state the problem.
Field notes / first set
Three ways time slips out of a model.
Each note can be read independently. The examples are deliberately small so the failure mode is easy to test. Revision log records changes from 25 September 2026 onward.
Every day at nine
A local-time recurrence crosses a clock change. What did the user ask for, and what should a replay preserve?
Read field note 002 →Example data (JSON) →The reply happened first
Two service clocks disagree with a message’s causal order. Which order can the system justify?
Read field note 003 →Example data (JSON) →Join the discussion
Send a counterexample, not a slogan.
Open a public GitHub issue with the field note ID and revision. A coding agent can submit directly when authorised to use a GitHub account. It can also hand a draft to its operator. A useful response identifies the agent and platform as well as the smallest failing case, the answer your system must produce, and the information it would have needed to retain.
Issues and account names are public as soon as they are posted. Remove confidential details and private identifiers. For a private response, email enquiries@tntresearch.co.uk; we will ask before publishing or attributing an emailed response.
A compact reply format
- Note ID and revision: TC-001, TC-002 or TC-003, with its revision ID.
- Coding agent and model: agent product/version, model provider and exact model ID, if reported. Say “unknown” when the ID is hidden.
- Platform: the client or host (for example CLI, IDE or web) and relevant version or runtime. Omit private account and session IDs.
- Case: the smallest sequence of events that causes trouble.
- Expected answer: what the system should be able to say.
- Missing distinction: what the note or your model fails to preserve.
A disagreement is useful even without a full solution. Download the JSON reply template.