Scope & Method

Topics are the stable containers for ongoing topics. Events capture the key developments inside a topic. Reports provide the reporting evidence behind those developments. Sources show which outlets are participating in the tracked topic.

These units are related, but they are not interchangeable. The product uses them to help readers move from a broad topic view into the specific reporting that supports it.

News Track shows reporting from the outlets and reports that have been ingested into the current tracked dataset. It does not claim to represent every newsroom, every topic angle, or the full universe of available reporting.

Visible material should be read as a tracked subset with clear provenance, not as a guarantee of exhaustive global completeness.

Tracked content may be added, regrouped, or revised as new reporting arrives and as topic structure becomes clearer. That means a topic page can change over time even when the underlying topic remains the same.

Temporary delays, shorter timelines, or sparse source lists can happen when ingestion is still catching up, when source reporting is thin, or when content is being reprocessed.

The interface is designed to help readers understand change over time. Timelines make sequence visible, takeaways compress the current state of the topic, and source views keep outlet differences visible instead of flattening them.

Search also reflects this structure by prioritizing topics first and then showing events and reports as supporting context.

News Track keeps sources, sequence, and product limits visible at the same time. That makes it easier to understand what is known, which reporting supports it, and where the tracked dataset is still thin.

The goal is not to imply that the topic is complete. The goal is to make the currently tracked material legible enough that missing context stays visible instead of hidden.

Some topic pages may have short timelines, some source pages may show limited reporting, and some searches may not surface the topic you expect. That usually means the tracked dataset is still sparse, the topic is not clearly organized yet, or the available reporting is still limited.

These gaps should be interpreted as product limits that are still being worked on, not as proof that nothing happened or that the tracked topic is already complete.

If you see a missing topic, incorrect grouping, wrong source attribution, or missing relevant reporting, use the feedback center to prepare a correction or feedback report.

The most useful reports include the topic name or page URL, the specific issue, the relevant source link, and what you expected to see instead.