Evidence and knowledge asset
Keep knowledge current and traceable so workflow decision go still stand on evidence and you fit audit am.
Knowledge asset
- Register website, document and connected source as managed asset
- Track who own each asset and which workflow dey use am
- Apply freshness and retention policy wey fit each source
Ingestion pipeline
- Handle website sync, upload, connector sync and feed ingestion
- Monitor pipeline health and di last sync wey succeed
- Keep ingestion lineage for troubleshooting and audit
Policy for freshness
- Set sync cadence and threshold for when content don stale
- Review di diff before update wey policy dey critical for
- Alert when freshness dey drift abi source fail
Control for evidence quality
- Require citation for di workflow and intent wey you pick
- Route response wey no get enough evidence go review abi escalation
- Track retrieval diagnostic and pattern of source wey dey miss
- Tie response outcome to source freshness and ingestion health
FAQ
FAQ
Which content source Threada dey support?
Website, document wey dem upload, API connector, and source wey base on feed. Dem dey register each one as managed knowledge asset wey get im own freshness and retention policy.
How freshness policy take dey work?
You go set sync cadence and stale threshold for each source. Threada go alert you when freshness dey drift abi sync fail, so evidence go stay current.
We fit require citation inside response?
Yes. Dem fit apply citation requirement for each workflow and intent. Response wey no get enough evidence dey route go review abi escalation by itself.