Cinecourier
Cinecourier

Methods

Every article contains one data table. Software builds it, not the model that writes the article: the model can only comment on the table. Each table is stored with a fingerprint (SHA-256) of its data, and every figure read from a source has a recorded origin: a quote verified word for word against a saved primary source, or the address of a public API with the time it was read. Columns such as week dates or differences are calculated from those figures. The method of each table is printed next to it in the article.

These tables aggregate and compare public data. They are not tests: we have not run the models or tools ourselves, and the tables do not measure quality.

Comparison table

Compares the model in the story with up to four recent models in our tracker, on attributes such as maximum clip length, maximum resolution, frame rate, native audio, price, access (API, app or open weights), licence and release date. Only figures quoted in primary sources and verified word for word are used, so a cell stays empty when no verified figure is on file. The tracker grows with every story we read; nothing in it comes from memory or from unverified sources.

Spec tracker

A variant of the comparison table focused on published specifications and limits. The same rules apply: each cell comes from a quote verified in a primary source, with the date it was read, and a cell stays empty when the figure is not published.

Repository metrics

Stars, forks, open issues, licence and date of the last push of the code repositories cited in the story, read from the public GitHub REST API at the time shown with the table. These figures change every day: the table is a snapshot, not a ranking of quality.

Paper trend

Weekly counts of new arXiv papers matching a query set for this publication, for the last eight complete weeks, Monday to Sunday, read from the public arXiv API (metadata under CC0). The last column is the difference from the previous week, with a plus sign when the count rose. The arXiv API selects papers by submission date in GMT, so a paper submitted close to midnight can fall in the neighbouring week. A rise or fall in the count does not show its cause.

Timeline

Release dates taken only from quotes verified in primary sources stored by our pipeline, in date order. It is used only when at least five such dates are on file.

Prices and specifications

Prices and specifications of the tool in the story and of its direct competitors, read from their official pricing and documentation pages. The competitors come from a fixed list per category, not from the story. Each cell keeps the page address and the line it was read from; a cell stays empty when the page does not state the figure. Units can differ between vendors (dollars, credits): the table shows them as published.

Release history

Dated entries the project published in its own release notes, news list or changelog, newest first, with the page they were read from. The text of each entry is the project's own wording: it says what the project announced and when, not whether it works as described.

Published results

A results table published by the project on its own page (benchmarks, hardware needs, timings), copied cell for cell with the page address. These are the project's own figures, not an independent test.