“24 of 40 participant slots are filled” helps an assistant draft this week’s recruitment update. If the team recruits more participants next week, reusing that sentence could produce an outdated update.
The problem begins before a model writes anything. The selected context itself may be wrong for the moment in which it is used.
Useful for this request
Recruitment total: 24 of 40
Review: Friday
Before the next update
Check when the total was recorded.
Check whether Friday is still the next
review.
The fictional example fixes these details so you can concentrate on access. A real workflow would also need to account for their age and source.
A review date is a different decision from deletion
A team might need to retain an old recruitment total as a historical record while preventing an assistant from treating it as the current total. Those are separate uses of the same information.
That distinction matters for Vivendur: deciding who can retrieve a record does not answer whether the record is still suitable for a new task. One design to examine is a review date that makes someone check the source before reusing time-sensitive context.