News methodology v1.2.0

How news works

We separate where a report came from, who or what wrote it, what the evidence supports, and whether it remains published. A fast signal is not presented as a verified fact merely because it is popular.

Labels describe our evidence process, not a guarantee of accuracy or investment suitability. Market news can change quickly.

Production flow

From source to public record

  1. Collect

    Primary documents, publishers, contributors, and public social signals enter separate source lanes.

  2. Normalize

    Claims, symbols, timestamps, source identity, authorship, and canonical links become a versioned record.

  3. Evaluate

    Evidence advances, disputes, expires, or retracts a report through an auditable state transition.

  4. Publish

    Every visible story carries labels derived from its current evidence state and origin.

  5. Correct

    Material changes create revisions; corrections and retractions remain visible in the public record.

Reader labels

What the badges mean

Verified
Supported by an identified primary source, independent corroboration, or a documented reviewer decision.
Social signal
Originated as a public social post and has not been promoted to verified reporting by origin alone.
Unconfirmed
Potentially relevant information whose core claim has not met the verification standard.
Disputed
Credible evidence conflicts with a material part of the claim.
Corrected
The current story includes a material correction and preserves its revision history.
Retracted
The original claim is no longer published as news. A public tombstone remains until the applicable storage-retention period ends.
AI summary
Automation assisted with summarization. AI output does not independently verify a claim.

Lifecycle

Evidence changes status, not history

Unconfirmed

Published for a limited review window when the signal may be time-sensitive but is not yet verified.

Corroborating

Evidence collection is active and at least one supporting item exists, but the verification standard is not complete.

Verified

The core claim met the documented evidence standard.

Disputed

Credible evidence conflicts with a material part of the claim.

Expired

The verification window closed before the claim met the evidence standard; the report leaves the public feed.

Retracted

The claim is no longer published as news. A tombstone remains during its storage-retention period.

Removed

The content is suppressed immediately for safety, legal, or integrity reasons and enters the abuse-retention lifecycle.

Accountability

Corrections, retractions, and automation

Corrections

Material edits create a new revision, identify changed fields, name the decision maker, and preserve the earlier record.

Retractions

The story body is unpublished, a public tombstone remains, and downstream consumers can receive a retraction event.

AI use

Automation may classify, deduplicate, translate, or summarize. It cannot independently upgrade a claim to Verified.

Appeals

Contributors and sources can submit evidence for review. Restored reports create a new auditable decision instead of erasing the removal.

Storage lifecycle

What we retain and what we purge

Editorial status and storage status are separate. A story can be retracted immediately while its payload remains temporarily available for review, appeals, fraud analysis, or legal obligations.

Retracted reports

The public body is removed immediately. The full internal payload follows the standard retention window before purge.

Expired signals

Low-value unconfirmed reports use a shorter retention window so stale payloads do not accumulate indefinitely.

Fabrication and abuse

Fake or harmful misinformation is unpublished immediately. Its payload is later purged under the abuse policy after review and appeal needs are met.

Legal holds

An authorized hold pauses every automated and manual purge path until the hold is explicitly released.

Purged means article text, evidence payloads, and revision bodies leave primary storage. A small integrity record, content hash, and immutable purge event remain; backups expire on their own documented schedule.

Current system

What is live in the foundation

  • Versioned story, evidence, decision, revision, and correction records
  • Automatic expiry of overdue unconfirmed reports
  • Immediate unpublish and tombstone behavior for retracted content
  • Automated retention classes, legal holds, bounded purge batches, and immutable purge events
  • SEC EDGAR primary-source ingestion when an operator enables and configures it
  • Authenticated contributor reports with evidence, disclosures, review scoring, withdrawals, and appeals
  • Public APIs for stories, provenance, methodology, and corrections

Next controls

What is still being built

  • Deeper contributor identity verification and coordinated-manipulation controls
  • Independent-source corroboration scoring and conflict detection
  • Signed partner feeds and real-time correction webhooks
  • Public aggregate transparency metrics and appeal outcomes
  • Additional government, issuer, exchange, and emergency sources
How News Works | CandleScript.io