Ready.
In the Beta-0 release, the master services are not implemented, yet. You may read my ideas/plans about them, as they are (gradually) published, though.
. . FRM (37) ARZ (45) AFRMZ (64) Stand-Alone 0 $ (36) , (44) ? (63) Stand-Alone 1 % (37) - (45) @ (64) Relational 0 : (58) / (47) = (61) Relational 1 ` (96) \ (92) ~ (126)
The numbers are calculated on the ASCII table.
For the absolute codes/numbers, I took the ordinal numbers (counting order) in the alphabet, and added them.
The zero/one alternatives are the adjacent ones. The difference is whether the ASCII-table look-up is zero-offset, or one-offset. The usual representation is with zero-offset, and taking the decimal equivalent. Yet, because we had to calculate the names with one-offset, the counting-sequence interpretation is also credible. I did not prefer one over the other, and both interpretation has found a presence. This way, the 64th letter is '?' with zero-offset, it is '@' with one-offset. And, so on.
The relative numbers/codes are the distances between each pair, in the ASCII table. For example, for FRM, with a sum of 37, and the distance between ':' and '`' is 37. Likewise, for AFRMZ. These are managerial and somewhat political. The distance is from midpoint to midpoint of the letter boxes. The interactions are functional, and more readily separable. For the ARZ, the distance covers the boxes in full, and it is not so much relations-craving. It has its strength within, and its interactions are inclusive. That leads to its covering one less letter in letter count, but it covers its range fully.
A character code is like a personality. Reflects its given (FRM, ARZ, AFRMZ) (expected) nature.
Contrast that with the A, F, R, M, -, Z -starting words, which tell the action, or object requested at the moment.
The whole software is a matching/tension with/between personalities and behaviors/socialization (or, requested behaviors).
Some may be more fit/tuned to service particular request than others.
It may be taken as a CISC machine architecture, with its variety of flavors. The better designed software, fitting the architecture better, would run faster on a hardware implementation.