# How changelogs.info works

## What this is

An archive of how the AI ecosystem changes. We watch releases from coding harnesses,
model providers and protocol specs; preserve the original source permanently; and
publish a normalised account of what changed, how much it matters, and what it affects.

The website is one interface. The product is the Git-backed, Markdown-canonical archive
underneath — which is why every page has a `.md` twin and a JSON form.

## The pipeline

1. **Collect** — per-entity detectors (GitHub releases, in-repo CHANGELOG.md, npm).
   New material lands in `data/raw/` and is never edited again. Raw is sacred.
2. **Eventify** — an LLM turns raw into a structured event: title, summary, categories,
   significance, breaking flag, confidence. It may not state a fact absent from the
   source, and may not reproduce vendor text verbatim.
3. **Review** — confidence below 0.75 flags `needs_review` and waits for a human.
   27 events are in that queue now, and say so on their own pages.
4. **Derive** — index, search, graph, site, API, CLI and MCP server are all regenerated
   from the event files. Delete them all and they rebuild identically.

## Significance

| | |
|---|---|
| 5 | Ecosystem-shifting — new frontier model, protocol-level change, major launch |
| 4 | Changes decisions — breaking change in a widely used tool, pricing, big capability |
| 3 | Worth knowing — notable feature, new model support |
| 2 | Routine — fixes, minor features |
| 1 | Noise — patch bumps, docs |

Significance is per-audience by nature. The number is a default, not a verdict.

## Rules we hold ourselves to

- **Provenance or it doesn't ship.** No event without a source URL; the schema rejects
  it at write time.
- **We don't mirror.** Vendor notes stay on the vendor's site. You get our synthesis
  and a prominent link.
- **Facts and opinion never blend.** Community reactions live in a separate module.
- **History is append-only.** Corrections are new events pointing at old ones —
  including when the mistake is ours.
- **Absence is disclosed.** Coverage starts at each entity's first tracked release.

## What this is not, yet

The community layer is **empty** — the curated creator list that feeds it is not
written, so every event says so rather than faking it. Five of six verticals are **not
publishing**: manifests exist, golden evaluation sets have not passed. No paid tier,
no alerts, no webhooks.

Tracking 11 entities and 393 events.

## For agents

Append `.md` to any URL, or send `Accept: text/markdown`. Start at https://changelogs.info/llms.txt,
or use the skill and MCP server at https://changelogs.info/agents. Don't scrape the HTML.

---
Source: https://github.com/cyperx84/changelogsdotinfo