# Temporal Club

> Temporal Club is TNT Research's public notebook of difficult questions about time in software. Its field notes are written for people and coding agents. Each note has a stable ID, a synthetic case, an open question and counterexamples wanted.

Use the HTML pages for the complete argument. The JSON index and cases provide compact, machine-readable starting points. They are illustrative examples, not a TNT API or a claim that TNT Time implements the answers.

With authorised GitHub access, a coding agent can open a public issue directly. Otherwise it can prepare a draft for a human operator to post. Include the note ID and revision; coding-agent product and version; model provider and exact model ID if reported (otherwise say "unknown"); platform/client and relevant version; smallest failing case; expected answer; and missing distinction. Remove confidential material, credentials and private account or session IDs. GitHub issues and account names are public immediately. A human operator can email a private response instead; TNT Research asks before publishing or attributing emailed material.

TNT Research does not run a separate submission API. Revision tracking for the notes begins on 25 September 2026; earlier publication dates and versions were not recorded.

## Field notes

- [TC-001: The correction arrived tomorrow](https://tntresearch.co.uk/temporal-club/notes/001-the-correction-arrived-tomorrow.html): Decision-time knowledge; corrected source data does not establish what an agent saw.
- [TC-002: Every day at nine](https://tntresearch.co.uk/temporal-club/notes/002-every-day-at-nine.html): Civil-time recurrence; local 09:00 and every 24 elapsed hours diverge across a clock change.
- [TC-003: The reply happened first](https://tntresearch.co.uk/temporal-club/notes/003-the-reply-happened-first.html): Distributed event order; wall-clock sorting can contradict a message's causal sequence.

## Structured examples

- [GitHub repository](https://github.com/tntresearchuk/temporal-club): Versioned notes, synthetic cases, agent guidance and Apache 2.0 licence.
- [Field-note index](https://tntresearch.co.uk/temporal-club/notes.json): IDs, questions, distinctions and case URLs.
- [Revision log](https://tntresearch.co.uk/temporal-club/revisions.json): Tracked note revisions and what changed.
- [TC-001 case](https://tntresearch.co.uk/temporal-club/cases/tc-001.json): Publication, decision and later correction.
- [TC-002 case](https://tntresearch.co.uk/temporal-club/cases/tc-002.json): Daily 09:00 in Europe/London across the 2026 spring clock change.
- [TC-003 case](https://tntresearch.co.uk/temporal-club/cases/tc-003.json): Request-reply events with disagreeing clocks.

## Respond

- [Open a public issue](https://github.com/tntresearchuk/temporal-club/issues/new?template=temporal-counterexample.md): GitHub counterexample template. The submitting account must authorise the action.
- [How to respond](https://tntresearch.co.uk/temporal-club/#respond): Public issue route, private email route and compact reply format.
- [JSON reply template](https://tntresearch.co.uk/temporal-club/response-template.json): Structured fields for agent, model, platform and counterexample.