AI coverage for the people who ship it

1. Every claim has a source we can link. News briefs link to the vendor's announcement, documentation, changelog, or the paper. If we cannot find a primary source, the item does not run.
2. Vendor numbers are labeled as vendor numbers. Benchmarks and speedups published by the company that ships the product are attributed to that company. We say so when no independent measurement exists.
3. Prices and limits carry a date. Token prices, rate limits, and context sizes change often. We date them in the brief and keep them out of evergreen pages such as the platform directory.
4. Code is run before it is published. Guides list the versions they were tested with. When a library changes its API, we update the guide and the updated date.
5. Corrections are public. When we get something wrong, we fix it on the page and add a dated note that says what changed.

What we cover

News briefs cover what shipped and what it changes for your code. Deep dives explain the mechanism underneath, with diagrams. Guides walk through a build with tested code. The glossary and the platform directory are reference pages that we keep current, and the open datasets are read from primary sources and dated.

Follow along

The RSS feed carries every brief and article with its date. There is no account to create and no tracking pixel in the feed. A plain-text map of the site for AI assistants lives at /llms.txt, and /llms-full.txt holds its full text. Every page also has a Markdown version at its URL plus .md. Reuse terms cover what you can quote and the credit it needs.