Platform-specific files are stored in /$architecture and binaries in /$architecture/bin. Shell scripts are stored in /rc/bin. For the home directory, traditionally, this style is reversed so your shell scripts would be in $home/bin/rc.
The namespace for any process can be enumerated, so in my default shell, I can see which directories are currently bound (and how) on /bin:
tenshi% ns | grep 'bind' | grep '/bin'
bind /amd64/bin /bin
bind -a /rc/bin /bin
bind -b /usr/seh/bin/rc /bin
bind -b /usr/seh/bin/amd64 /bin
bind -a /sys/go/bin /bin
bind -a /usr/seh/go/bin /bin
tenshi%
[1] http://man.cat-v.org/9front/1/bindIt's like having fond memories of Hillary Clinton's inauguration speech.
I don't think “vapourware” means what you think it means.
To elaborate, the comparison with an alternative universe is silly, since there are actually papers that people can read and there is actually code that people can use. So saying that “it never happened” is wrong.
I'd say it's closer to the DMC DeLorean: short production run, works but has short comings, more of a meme than an actual commodity.
It's not vaporware though, they definitely delivered something that works. It's just that there wasn't a good reason to use it compared to other options.
Also, gobolinux tries to mimic this behavior as well. https://www.gobolinux.org/