per context physics (or rather internal logic with spatial consequences, e.g attraction/repulsion) #58

Could be tried first as text descriptors in chemistry (see the dedicated branch https://git.benetou.fr/utopiah/text-code-xr-engine/src/branch/chemistry_example ), e.g C for Carbon, O for Oxygen, etc. There are probably equivalent text based notations for most systems.

Same principles for non physical systems e.g programming https://twitter.com/slsoftworks/status/941403037880520705

See https://twitter.com/utopiah/status/1581678695240327169 and motivated by https://fabien.benetou.fr/Analysis/ExtendedLayeredModel

Also useful in exercises, being warmup, e.g typing on keyboard challenge, or introduction #12

It is not physics per se but rather rules of behavior internal to a domain, a causal system.

Consider how scope, assuming it can be brought throught different engines, e.g physics (e.g bullet), is sufficient knowing that timescales might differ yet still be sufficient in a single large scope.

See also for non physical work https://fabien.benetou.fr/CognitiveEnvironments/ that could have sets of (jxr) commands attached, possibly part of steps in a workflow, either explicited by the user or implicit (detected).

Consider already https://github.com/n5ro/aframe-physics-system especially for workshops with kids.

Consider grammatization, a la Stiegler, across layers or systems.

Note that this does apply to code too. Even though it might initially not because text seems so infinite it is not, namely code has a grammar and even though naming makes it look extremely diverse or rich in pratice, as seen with syntax highlighting, a function name or a variable name are "just" tokens of the same type. Consequently coding itself follow that principle.

see https://mobile.twitter.com/utopiah/status/1623953604116611077 relying on CANNON.js