OK, I think I (partially) mispoke for which I (partially) apologize. OOPS
When I ran this the 1st time, I don't remember the tree size being 11gigs which it was the 2nd time I ran it (I didn't save the 1st run). I think I forgot to add a 25% sizing to the strategy profile the 1st time, hence the 100% check back result I initially claimed (as you'll see, AA never, ever prefers b55% or b100% compared to check--almost none of our range does, it might as well be a binary strategy profile b25% or check).
I also concede both V's and H's ranges may be off, H's 3x is throwing me for a loop assigning a range bc I personally wouldn't open any hand here for 3x. I tried my best. If you or anyone else has a better suggestion, I'm all ears and would be happy to rerun (OP that's your cue).
Also, I used much wider ranges for my 1st run but I'm just now just not confident they're as wide as I initially modeled the spot with. If anything, I think my ranges are still too wide (possibly much too wide).
Parameters (Don't worry I ran this down to .25% exploitability):
V's Range:
H's Range:
25% pot is a viable cbet sizing. BUT:
-As you can see, we're checking at a MUCH higher freq vs b25% (~3x checking freq w/ AA vs b25% freq) and KK too is more often a check than a bet
-AdAh (blocking FD and BDFD) is essentially a pure check
-Small sizing is the only viable sizing--if we're betting, never more than 25%, or
maybe 33%. So OP in any case made a mistake OTF
-I was wrong on my predicted cbet freq--it's ~65%, not 50% like I guessed. Range advantage (which hero has to the tune of 1.6:1 in this spot which is pretty big) is a powerful thing.
-I still maintain that with AA in particular check, if we had to purify our strategy down to just one option, is better for our global strategy, and precisely for the reasons I mentioned. It's a lot easier to make ourselves exploitable if we're overbetting with AA compared to overchecking.
If you really think V is spewing vs cbets, by all means go b25%. I'm still gonna be checking this flop almost always, and you really can't go wrong with checking--betting on the other hand has some pretty clear downsides that don't really exist in the checking nodes.