Evidence and knowledge assets
Keep knowledge current and traceable so workflow decisions remain grounded and auditable.
Knowledge assets
- Register websites, documents, and connected sources as managed assets
- Track asset ownership and workflow usage
- Apply source-specific freshness and retention policy
Ingestion pipelines
- Handle website sync, uploads, connector sync, and feed ingestion
- Monitor pipeline health and last successful sync state
- Preserve ingestion lineage for troubleshooting and audits
Freshness policy
- Set sync cadence and stale thresholds
- Review diffs before policy-critical updates
- Alert on freshness drift and source failures
Evidence quality controls
- Require citations for selected workflows and intents
- Route low-evidence responses to review or escalation
- Track retrieval diagnostics and missing-source patterns
- Tie response outcomes to source freshness and ingestion health
FAQ
FAQ
What content sources does Threada support?
Websites, uploaded documents, API connectors, and feed-based sources. Each is registered as a managed knowledge asset with its own freshness and retention policy.
How does freshness policy work?
You set sync cadence and stale thresholds per source. Threada alerts on freshness drift and failed syncs so evidence stays current.
Can we require citations in responses?
Yes. Citation requirements can be applied per workflow and intent. Low-evidence responses are routed to review or escalation automatically.