Context freshness
Every context entry carries a timestamp. DelegateZero tracks how recently each entry was updated and uses this to weight signals appropriately - a policy written last month carries more signal than one written three years ago for the same situation.
Freshness thresholds vary by context type:
| Context type | Staleness threshold |
|---|---|
| Policy | 365 days |
| Precedent | 180 days |
| Playbook | 365 days |
| Template | 365 days |
| Source | 180 days |
| Entity | No threshold - kept current automatically |
| Memory | No threshold - weighted by recency naturally |
When a context entry exceeds its threshold, it is flagged as potentially stale. This flag appears in the audit log whenever a stale entry influenced a decision, including the entry's name and age. DelegateZero will reduce confidence when stale entries are primary inputs to a response.
Stale entries are not ignored or deleted automatically. Their general content may still be valid. The flag is informational - it tells you and DelegateZero to treat specific details with appropriate skepticism and prompts you to review and update.
You can see the last-updated date for any context entry in the dashboard. Updating an entry resets its freshness clock.
Sorry, we don't have any results for that search. If you need assistance, please contact us.