Recap what was the status of discussion:
value is triggered by an event (maybe a different contract than the token contract, e.g. a contract that monitor's voting result)
an event is updated every block or almost every block (e.g. a contract that reports Ethereum price).
In the No.2 case, the re-fetch (tick) doesn't have to be more frequent than block production and since the ENGINE knows block production it doesn't have to require more frequently. In the 1) case, the attribute has 'origins' that links it to the ethereum event it triggers.
There is a 3rd condition that the value changes but there are no event, e.g. in compound the system emits no useful event at all, partly because the team wasn't looking to integrate anything. That's the place where a frequency might be needed, but in that meeting, we weren't too keen on that and subconsciously think it's the same of 2). Maybe we should have taken care of it with a special case 3 - in the coming TS meetings.