Every changing fact needs a trail.

Official documentation and endpoint pages are preferred for current specifications and prices. Official announcements establish what a provider said at a point in time, but performance statements remain provider-reported until independently reproduced.

Reliable secondary sources can add context or corroboration. Community posts and project submissions are leads, not publication authority.

• Official documentation and billing surfaces
• Official announcements and repositories
• Recorded first-party observations with a stated method
• Reliable independent reporting
• Community reports and submissions as unverified leads

Not disclosed means no reliable public evidence was found for the field. Stale means a previously verified record crossed its review boundary. Neither state is represented as zero, false, or an implied negative.

A project status records the last observation under a named method. An HTTP response alone does not prove that a generative stream is live.

When first-party pages disagree, the ledger retains both claims with their scope and observation time. We do not average the values or quietly select the more convenient statement.

For pricing, an effective endpoint or billing surface takes priority only when its identity, unit, currency, and timing can be matched. Otherwise the value remains announced, historical, or unavailable to the calculator.

Promotions and live status receive short review windows. Stable model identity and historical release records can use longer intervals. Crossing a conservative review deadline blocks a dynamic price from new calculations until it is checked again.

Automated checks may flag a likely change or broken link, but they do not autonomously publish a new price or declare a project discontinued.