alias name-here yields the line alias name-here='contents-of-alias-here' as output, and if you want just the part between the single quotes from that, sed, cut or, come to think of it, related shell tricks that do the same thing, would be needed to capture and convert it.
${BASH_ALIASES["name-here"]} is a name for what’s only between those single quotes.
For example, I have a lot of preferences built into my alias for ‘ls’. Occasionally I want to run watch ls -l somefilespec to watch a directory listing for changes to a file. But commands fed to watch don’t go through the alias mechanism, leaving the output somewhat different to my preferences.
It’s wordy, but watch ${BASH_ALIASES["ls"]} -l somefilespec mostly* achieves what I want.
* Unfortunately, watch also causes the stripping of colour codes and I have --color=auto, not --color=force in my ls alias, so it’s by no means perfect - I have add the latter if I want colour - but I don’t have to type the rest of the preferences I have in there.
FWIW, my ls alias is currently:
alias ls='LC_ALL=C ls --color=auto --group-directories-first --time-style="+ %F %T"'





I seem to remember a story about how something - a neural net, or an early reinforced learning experiment - ended up accidentally exploiting a physics bug in a chip to achieve a result that should have gone through the chip’s expected circuitry instead.
It was specific to that one particular chip, and swapping it out for another supposedly identical chip caused the calculation, or simulation, or whatever that was running on the larger system, to fail.
That is, it wasn’t supposed to be exploiting physics glitches but that’s what happened.
… I think I found it. It happened all the way back in the 1990s if this story is to be believed: https://www.damninteresting.com/on-the-origin-of-circuits/