There is a common pattern that’s not well defined yet in Nostr that is effectively a cached result. It’s stateful and typically either expires by time, or expires when replaced.

An example could be how much credit you have used for a paid service. Goes up and down on payment and usage.

Another example is a list of current trending events or similar, updated hourly or daily.

One consideration is how and when to update. Schedule is ok, however a client bump to update their usage to be current is likely a valid case too.

It’s basically a snapshot of data that’s useful as an event and more (likely) accurate the closer to its creation time, however it’s content changes.