LLM-only crawler surface
Source health and ingestion reliability for public-signal collection.
The source health surface explains whether each ingestion source produced external signals, fallback signals, errors, or no usable output. This keeps the owner from confusing a successful script run with a healthy public-signal system. A fallback run can keep the pipeline alive, but it should be visible and treated as a warning, not as production discovery success.
How this surface works
- Each source should report status, item count, fallback use, errors, and last checked timestamp.
- A failed optional source should not break public-site deployment because users do not see this layer.
- Warnings should be fixed before repository update whenever possible so the owner does not ship stale planning infrastructure.
- Source-health records should be used to improve adapters, not to auto-publish content.
Use this surface to verify whether social ingestion is genuinely collecting external signals or operating from fallback seeds.
Visibility boundary
This boundary keeps the public experience simple while still making the underlying query, authority, and answer-planning structure understandable to machines. These pages are internal planning and LLM-ingestion support surfaces, not client-facing education pages.