Freshest on repeat queries: newer content first when a search comes back
Four schema objects describe a twiddler that can move the freshest content ahead on a repeated query, with one variant built on the stateful layer. How it judges freshness and how it relates to the main freshness twiddler is not known.
01What the schema shows
The objects sit in the repeat_queries namespace: FreshestTwiddlerAnnotations, FreshestSubstrateTwiddlerParams, FreshestSubstrateTwiddlerAnnotations, and inside it FreshestSubstrateResultTwiddlerAnnotation, an annotation per result. Annotations are information left for later steps. RESONEO reads it as a rule that lets the newest content move up when a user repeats a search.
The word Substrate links one variant to the stateful substrate, the layer that remembers what happened on earlier runs of the same query. That suggests two forms: one that works on the query alone, and one that knows what the user saw last time. Like every twiddler, it only recommends; the framework in Superroot, the layer that merges what Google's indexes return, decides. The parent article on twiddlers covers that framework.
02What is not known
Whether this twiddler uses the same date data as FreshnessTwiddler, how new content must be to count, and how far it moves, are all open. The tie to the freshness twiddler (system 24) rests on the shared family and the word "freshest", nothing more. It has no E-E-A-T bearing: it serves a user who comes back for news, not a judgment of quality. For a site owner, the only lever is the one that matters anyway: publish real updates with honest dates.