Skip to content
TermSync
Latchmere School
Trace · URN 138689

How we read Latchmere School

last read 26 Aug 2026, 20:40 UTC · took 27.2s · 39 dates across 2 school years

Nobody types these dates in. A program finds whatever the school publishes its term dates on and reads it. This page is the working out: the files we downloaded, and every date we got out of them. Open the same file and you can check us.

Find the page

saved for next time

We start at the school's website and follow it to whatever it publishes term dates on, in this case a file on latchmereschool.org. That address is saved, so every later check goes straight there.

Download it

sha-256

8 files came back. We fingerprint the contents (cfba4e9d7e…b2afb2075e). If the fingerprint matches last time's, the school hasn't changed anything and we stop here.

Read it

27.2s

This school publishes its year as a colour-coded chart rather than a list of dates, so a model reads it the way you would — square by square, working out from the key what each colour means. 6 other files were read and produced nothing useful.

Work out the dates

plain code

Ordinary code takes it from here, pairing those sentences into terms and filling in the holidays between them. It also checks the year adds up: if the dates leave too few school days, we throw the whole read away rather than publish it.

Save it

one copy

The dates get written down once. The school's page, your calendar feed and this trace all read that same copy, so they can't disagree with each other.

Where it came from

what we downloaded, and what we actually used

The chart, and what we read off it

point at a square, or at a date, to see the other
2025/2619 dates
The school's published term-dates chart for 2025/26
open the original
2026/2720 dates
The school's published term-dates chart for 2026/27
open the original

Each square is a day the reader found on the page and dated. What it MEANS comes from the colour it is filled with, matched against the key the school printed — which is why there is nothing to quote: the school never wrote these dates down in words.

What we saved

the single copy the school page and your calendar both read

This run

fingerprint
e10ee146e5…6cab4ec749
saved at
25 Aug 2026, 20:43 UTC
run signature
78da812b50…e765a5d838
dates published
40
last confirmed
26 August 2026

Why your calendar doesn't fill up with duplicates

Each event gets an ID built from who said it, what kind of day it is, and when it starts. Read the school again tomorrow and the same day comes out with the same ID, so your calendar updates the entry it already has rather than adding a second one.

# same inputs, same ID, every time
sha256(owner | kind | start)[:24]
  → a4384bdd…f1763a2c@termsync.co.uk