How it works
Methodology
How infinitenews collects, structures, checks, and updates developing stories.
01 / Story model
Coverage is organized by developing story.
A story board can remain active across days, weeks, or months. Its current state summarizes where the published record stands; its ledger preserves the individual developments underneath. Calendar dates help orient the record, but they do not replace the story.
02 / Chronology
Events stay in time order.
Entries are displayed by when the recorded event occurred. Filters can narrow what is already on the page, but they do not reorder it. Featured placement is an explicit publication choice, not a personalized or engagement-based recommendation.
03 / Confidence
Support and source identity are different questions.
- Confirmed
- The published entry has corroborating support.
- Official
- The claim is attributed to a named official or primary source. Official attribution does not itself mean independent corroboration.
- Reported
- The entry rests on a named outlet's published account.
- Unverified
- The available support remains insufficient or unresolved.
04 / Sources
Every entry links to its sources.
Each ledger entry displays its named sources as direct links. When a source publication time is available, it appears beside that link. Source count is not a substitute for source quality, and source identity is not collapsed into the confidence label.
05 / Freshness
“Active” does not automatically mean “live.”
Story status, latest-entry time, and last-checked time are shown separately. An active board that has not been checked in more than 24 hours carries a visible freshness warning. Ended and archived boards retain their final coverage dates.
06 / Scheduled automation
Automated research runs on a fixed schedule.
The research system looks for material developments on a fixed schedule. Accepted entries must pass source, URL, timestamp, timezone, and duplicate checks before entering the published record.
When the evidence changes, an automated synthesis may refresh the current-status paragraph and up to three watchpoints. Each statement links to the entries that support it. If the synthesis cannot be validated, the previous cited briefing remains in place. Reader searches never trigger this process.
07 / Corrections
Corrections stay attached to the published record.
Source-verified timestamp or factual corrections update the affected ledger entry without changing its stable URL. Material methodology changes are documented here rather than silently changing what labels mean.
08 / Reader contract
The same chronological record is available to every reader.
The current state and newest ledger entries are rendered in the page and remain readable without JavaScript. No reader login is required. Search and filters do not personalize or reorder the record. JavaScript is reserved for optional conveniences such as theme selection.
The global RSS feed and per-story RSS feeds publish the same dated entries for feed readers without personalizing or reordering coverage.
Event time is shown both where it happened and in U.S. Mountain Time, so a distributed sequence can be compared without losing local context.