Sources and provenance
Trend Finder collects configured, reviewed public-source metadata. A source name in documentation is not proof that it ran in the current local result.
Three source layers
Section titled “Three source layers”| Layer | Meaning |
|---|---|
| Built-in direct adapter | Reviewed code that uses a public API or feed without a paid Actor |
| Reviewed source declaration | Metadata, role, quality tier, caps, and compliance decision; not a run |
| Configured source | A reviewed source selected locally and allowed to run when readiness passes |
Built-in direct adapters
Section titled “Built-in direct adapters”The current direct set covers:
- arXiv paper metadata
- GitHub repository search metadata
- reviewed RSS and Atom feeds
- Hacker News keyword story metadata
- Hugging Face model metadata
- Google News result metadata
- Dev.to article metadata
When a direct adapter succeeds, a matching paid fallback is skipped before it can run. A direct adapter that is disabled, empty, rate-limited, timed out, or offline does not make the fallback valid automatically; the fallback still needs reviewed configuration and readiness.
Reviewed configured coverage
Section titled “Reviewed configured coverage”Reviewed declarations also cover public discussion, launch, creator-video, paper, model, repository, news, and feed roles from sources such as Reddit, Product Hunt, YouTube, Hugging Face, GitHub, arXiv, and Google News.
Quality tiers cap how much evidence a source can contribute. The tier is a trust and collection signal, not a guarantee that every source item is true.
Health and provenance
Section titled “Health and provenance”| State | Meaning |
|---|---|
| Active | Current evidence was contributed |
| Degraded | Partial evidence or bounded warnings were returned |
| Offline | No current evidence was contributed |
| Blocked | A credential, compliance, configuration, or policy gate prevented the run |
| Fixture | Reviewed example evidence is active |
The browser distinguishes the current data state, analysis state, and source state. Deterministic fallback analysis can operate on evidence without claiming that a live AI analyst ran.
Compliance rules
Section titled “Compliance rules”- New sources need a source-specific review before collection.
- Collection is bounded to reviewed public metadata and approved fields.
- Source roles, caps, retention, attribution, deletion, rate, and spend rules remain source-specific.
- Unknown or placeholder source configurations are rejected.
- Public evidence links remain the verification path for the operator.
- Private caches and source diagnostics are not public documentation or demo data.
For score interpretation, continue with Scoring and history.