silent a/b testing of astra ? or just unquantized 5.6gpt sol?

[u/QuirkyGarage1364]

anyone notice that during some times of the day, if you get lucky, your 5.6 sol keeps track of every variable and the substrates they belong to?

but sometimes once it accepts one variable, it will remove another depending on your methodology/derivation for your mechanisms

anyway when i have notation collision, or any other kind of collision normal 5.6 sol is incredibly annoying to get to prune and address those specific collisions to not accidentally silently delete whatever transformation you're engaging with

last couple of days, at random times, the model has been fucking amazing out of nowhere at avoiding this particular failure

ive gotten it for like 1-2 hours and then randomly before its turn, you'll get a connection issue, you'll have to refresh, and then it's back to operational friction

there is a clear difference in user experience. i'm not exactly sure what causes it, but my theory is luckiness in the form of the a/b test or just maybe it's unquantized sometimes

[u/PhysicalConsistency]

Definitely feels like it's shifting effort on the fly sometimes.