Freshness
Use a current evidence set for questions that change over time.
Bring current, source-linked evidence into a bounded decision instead of asking a model to improvise from stale context.
The evidence loop
A live context workflow should make the evidence visible before it shows the answer.
Use a current evidence set for questions that change over time.
Keep the source and retrieval timestamp next to the decision.
Ask a focused yes/no, choice or score question instead of generating an essay.
Collect relevant sources with URLs and retrieval time.
Put snippets and source metadata into structured state.
Keep the decision narrow enough to inspect and reproduce.
Explain which sources changed or supported the result.
Trust
Fresh evidence still needs source quality, conflict handling and an explicit fallback when the signal is weak.
Ask about current evidence
Fresh evidence still needs source quality, conflict handling and an explicit fallback when the signal is weak.
{
"state": {
"question": "Has the launch date moved?",
"sources": [
{ "url": "https://example.com/notice", "retrieved": "2026-09-29", "text": "Launch moved to October 12." }
]
},
"questions": {
"changed": { "type": "noul", "instructions": "Do the current sources support that the launch date moved?" },
"confidence": { "type": "score", "instructions": "How strong is the evidence?", "criteria": ["weak", "mixed", "strong"] }
}
}FAQ
No. The useful pattern is source collection followed by a bounded decision with visible evidence.
Keep the conflict in state, ask about it directly and route low-confidence results to review.
Store the source URLs, retrieval time, extracted text, request and response together.