Feeds & machine exports

Follow the publication without guessing its structure.

QAEDA publishes first-party feeds and structured catalogs for essays, claims, release history, topics, evidence relationships, citations, and publication identity. Stable IDs travel with the records; protected source bodies do not.

Syndication

Choose the stream that matches the job.

RSS and Atom are intended for feed readers. JSON Feed carries the same essay discovery layer with QAEDA-specific relationship metadata. Claims and material release changes have their own JSON Feed streams so subscribers do not have to infer corrections from essay publication activity.

stableapplication/rss+xml

Essays — RSS 2.0

essay summaries

Items
31
Stable ID
QAEDA-ART-###
Open feed →
stableapplication/atom+xml

Essays — Atom 1.0

essay summaries with topic, claim, and evidence IDs

Items
31
Stable ID
QAEDA-ART-###
Open feed →
stableapplication/feed+json

Essays — JSON Feed 1.1

essay summaries with _qaeda relationship metadata

Items
31
Stable ID
QAEDA-ART-###
Open feed →
stableapplication/feed+json

Claims — JSON Feed 1.1

claim text, evidence status, confidence, and revision conditions

Items
35
Stable ID
QAEDA-CLM-###
Open feed →
stableapplication/feed+json

Changes — JSON Feed 1.1

material publication releases

Items
18
Stable ID
QAEDA-REL-x.y.z
Open feed →

Structured catalogs

Feeds are for updates. Catalogs are for state.

Use the canonical JSON catalogs when you need the current complete map rather than a chronological stream.

Stability contract

IDs survive title edits and evidence updates.

  • QAEDA-ART document identifiers are stable and are not reassigned to different essays.
  • QAEDA-CLM claim identifiers remain stable when evidence status changes; material reversals are recorded through corrections rather than silently replacing identifier history.
  • QAEDA-TST decision-test identifiers are stable and represent review questions, not numeric scores or certifications.
  • Feed item identifiers are derived from stable document, claim, or release identifiers rather than titles.
  • New fields may be added to public JSON exports; consumers should ignore unknown fields.
  • Protected research dossier bodies are not syndicated. Evidence relationships use public QAEDA-SRC identifiers and fingerprints only.
  • Feed summaries are discovery metadata, not substitutes for the canonical essay, claim ledger, or correction record.

The custom _qaeda object in JSON Feed is additive metadata. Consumers should ignore fields they do not recognize rather than failing closed on future additions.

Publication boundary

Machine readability is not a source dump.

No feed or export should expose protected research locations, internal working memory, report bodies, or operational source material that is intentionally non-public.

Public

Identifiers & relationships

Document IDs, claim IDs, topic IDs, evidence source IDs, fingerprints, canonical URLs, citation routes, summaries, and public correction state.

Protected

Source dossier bodies

Long-form protected research reports and internal working memory remain outside syndication. Use Evidence and Methodology to understand what is exposed and why.

Need citations instead?

Syndication and citation solve different problems.