Signal scope
Thetitle, url, and published_at fields point to the full source, but the decomposition (central statement, arguments, and claims) reflects only the extracted segment. So when a podcast signal’s statement reads narrowly, that is expected: treat the decomposition as authoritative for what the signal covers, and the source metadata as a pointer to where it came from.
What gets ingested
Gildea ingests from a curated set of 500+ sources across these formats:| Format | Examples |
|---|---|
| Essays | Blog posts, newsletters, long-form analysis |
| News articles | Industry reporting, first-party announcements |
| Podcasts | Transcribed and decomposed |
| Research papers | Academic and industry research |
| Social media | Expert discourse and announcements |
| Earnings calls | Quarterly calls from the companies that anchor the AI value chain |
| Press releases | Product launches, partnerships, policy announcements |
Two types of signals
Every signal is classified bycontent_type into one of two kinds:
Event signals (content_type: "event")
Key events sourced from global reporting and first-party announcements.
| Role | Description |
|---|---|
synopsis | The central factual recap of what happened, as individual verified sentences |
claim | Specific factual assertions extracted from the source |
Expert analysis signals (content_type: "analysis")
Expert analysis from leading researchers, operators, investors, and analysts who explain what the events mean.
| Role | Description |
|---|---|
thesis | The author’s central argued position, as individual verified sentences |
argument | Supporting reasoning lines; group by argument_id to reconstruct each as a paragraph |
claim | Specific verifiable facts extracted from the article |
The unit model
Signal detail is a flat list of verified units, the fundamental atom of Gildea’s data model. Every unit shares one shape, whether it comes back from signal detail or from search:role is the single axis that says what a unit is:
role | Appears in | Meaning |
|---|---|---|
thesis | analysis | a sentence of the author’s central argued position |
synopsis | events | a sentence of the central factual recap |
argument | analysis | a supporting-argument sentence (carries argument_id) |
claim | both | an atomic verifiable fact |
thesis (or synopsis) units in order for the central statement; group argument units by argument_id, in order, to rebuild each argument as a paragraph. Units come back grouped by role (thesis/synopsis → arguments → claims) in document order. List position is the order; there is no separate index field.
Every unit:
- Has passed verification: only verified units are served (see Verification).
- Carries its cited
evidencesnippets by default. - May carry
verification: { "human_reviewed": true }when a human reviewer signed off (omitted otherwise). - Is retrievable through semantic search (see Search).
Decomposition structure
Expert analysis signals
Event signals
Signal card vs. signal detail
The list endpoint returns lightweight signal cards: identity, classification, a depth signal (verified_unit_count), and the central statement served whole: a thesis field on analysis signals, a synopsis field on event signals.
The detail endpoint returns the full flat units[]: every verified unit with its evidence (included by default). Concatenating the thesis/synopsis units reproduces the card’s statement, so the two never disagree. Pull cards from the list endpoint for discovery; fetch detail when you need the verified atoms.