Track AI model releases as reviewed events, not as an endlessly refreshed news list. Preserve the provider, version identity, event type, official source and event date separately from the time your workflow discovered it. Search can find a candidate page; the official page and a review determine whether it belongs in the timeline.
Separate release, alias change and documentation update
| Record | Meaning |
|---|---|
| Official event date | The date stated for the reviewed event |
| Observed time | When your collector saw it |
| Version or alias | The identifier whose behavior or availability changed |
| Event type | Release, deprecation, alias change or documented API change |
| Source passage | The text that supports that specific event |
| Review state | Whether the source and interpretation have been checked |
Start with provider sources such as the OpenAI API changelog and Gemini API release notes. A page’s update date can reflect an edit rather than a model release. If the event date is missing, retain an observation with an unknown date rather than guess from a search snippet.
Deduplicate by event identity, not collection time
The runnable Python ledger uses an approved source host, provider, version, event type and source URL as the identity. It stores a separate content digest so a corrected observation becomes an update instead of a second release. The demonstration is explicitly fictional and cannot be used as a current model announcement.
import hashlib
import json
from datetime import datetime, timezone, date
from urllib.parse import urlparse
def reconcile_events(previous, observations, allowed_hosts):
current = dict(previous)
changes = []
for event in observations:
url = event["official_url"]
if urlparse(url).scheme != "https" or urlparse(url).hostname not in allowed_hosts:
raise ValueError("Event needs an approved official source")
official_date = event.get("official_event_date")
if official_date is not None:
date.fromisoformat(official_date)
identity = "|".join([event["provider"], event["version"], event["event_type"], url])
key = hashlib.sha256(identity.encode()).hexdigest()
substance = {k: event.get(k) for k in
["provider", "version", "event_type", "official_url",
"official_event_date", "summary", "reviewed"]}
digest = hashlib.sha256(json.dumps(substance, sort_keys=True).encode()).hexdigest()
old = current.get(key)
change = "new" if not old else "unchanged" if old["content_hash"] == digest else "updated"
current[key] = {**substance, "content_hash": digest,
"observed_at": datetime.now(timezone.utc).isoformat(),
"usable_for_timeline": bool(event.get("reviewed") is True and official_date)}
changes.append({"event_id": key, "change": change})
return {"events": current, "changes": changes}
if __name__ == "__main__":
fixture = {"provider": "Example provider", "version": "example-v2",
"event_type": "release", "official_url": "https://example.test/changelog#v2",
"official_event_date": None, "summary": "Synthetic fixture, not a real release",
"reviewed": False}
print(json.dumps(reconcile_events({}, [fixture], {"example.test"}), indent=2))
Check the state transitions with a replay
- The first reviewed event produces new; the same content collected again produces unchanged.
- A changed summary or event date produces updated while preserving the event identity.
- A missing official date cannot become a dated timeline entry.
- A source outside the approved host list is rejected before it is added.
The ledger assumes that an upstream reviewer or controlled extractor has already identified the source passage. It does not infer the event from arbitrary HTML, and a reviewed flag is an application assertion rather than proof. Keep the reference snapshot and reviewer decision beside the stored event.
Keep source discovery and event review separate
Use the news-monitoring workflow to discover candidates and the model-update source workflow for provider evidence. A SERP query can expand discovery; Reader extraction can preserve source text. Neither operation makes a headline an official release or assigns a missing date.