Mathematical specifications sounds sensible if actually viable, unsure whether it needs at least logic operators too, beyond my understanding. Taking year long adjusted and altered current Core codebase as dogma or fixed reference seems questionable to me in light that Segwit and Taproot seem to have introduced either unforeseen or initially obscured behaviors namely with arbitrary data storage in transaction or script fields. As for individual saviors, I had the impression that somewhat happened with the Segwit activation, and with no UASF pressure the 2x version, if I remember the name correctly, or something else might have activated, especially with that miner and exchange operator meeting or meetings which too constituted an attempt for few actors to run the show.

Another thought, according to my memory and cursory research the US, EU states and other sizable jurisdictions have criminalized possessing files for 3D printing firearms, and they can get smaller than 256kb used as a frequent limit in BIP 110. So does this criminal data store issue have any sensible way out, other than recognizing criminalizing speech as absurdity?

1) The RDTS limit is 256 _bytes_, not kilobytes. 2) Those are unjust laws, and people should fight them. 3) That being said, 3D files still don't belong on Bitcoin, and fear of unjust prosecution would likely still be fatal to Bitcoin in this way.