Following up on @trevorsc 's point 4 and the Snapshot result. With the ARFC passed, the oversight question is still open for the first instance: the framework states no service provider is scoped or paid to monitor it, and the two-week listing review only works if someone is actually watching.
Separate from any paid mandate, a public read-only monitor for this Hub is straightforward on the same event-driven approach as the V4 cap-utilization monitor we raised in the cap-round thread (post #35 in [ARFC] Aave V4 Activation on Ethereum Mainnet). It would cover live utilization and add/draw cap status per Spoke, queued AccessManager operations during the 48h window with time remaining, and role-grant changes.
@SentoraHQ, would you want that kind of external signal for the Hub? @LlamaRisk / @AaveLabs, is it useful before the AIP, or is monitoring of curated instances deliberately left out of scope? If the AIP includes funded tooling for oversight of curated instances, we’re open to scoping that.