That map was primarily chosen to preserve the generator counts of those Trojan-derived symbols that we had already agreed on, and

which we agreed on. In the end, the generator counts for primes greater than 23 were not relevant, nor was the generator count for prime 19. But they were chosen to have the smallest absolute values that gave errors smaller than (or not much larger than) those of the primes whose mappings were already determined by the agreed symbols.
You say it is sad that the 144-note MOS cannot be notated with monotonic accidentals and without accents. So why do you not argue for the use of

as the symbol for 131g?
I think we owe it to future readers to consider that option more thoroughly. So I just attempted to assign generator counts, and hence cents values, to the flags under such a scheme. It is possible to do so consistently, but it requires that

be assigned a large negative value of cents, namely -19.5 ¢. Negative values for upward-pointing flags are a bad idea. I will use <...> as brackets here to indicate that only the flags are being referenced, in cases where the symbol is not allowed in the notation.
This occurs because <

> =

-

= 45.1 - 19.5 = 25.5 ¢ and <

> =

- <

> = 6.0 - 25.5 = -19.5 ¢
Whereas, if we don't use

the values of <

> and <

> are underconstrained and can be given the more reasonable assignments of <

> = 0 ¢ and <

> = 6.0 ¢ (-89g), thereby also implying a reasonable value of <

> = 3.7 ¢ (144g).
Another reason not to use

or any other unaccented symbol for 131g is that once we agree that nothing is gained by not using

for -68g, we might as well also use

for -102g because although it is not required, it is useful in avoiding having both sharps and flats applied to D. Or to put it another way, to use no more than 13 pseudo-nominals Ab Eb ... C# G# in a chain of fifths. And once we have

= -102g and

= -233g introduced for other reasons, it seems better to combine them to give a symbol for 131g rather than introduce a new symbol.
Yes, it's a shame we don't get to the 144-MOS without accents, but we must not allow the notations for more complex scales/tunings to make the notations for simpler scales/tunings more complicated than they need to be.
רועיסיני wrote: ↑Sun May 28, 2023 4:09 am
... it seems much more intuitive when I'm writing text (and not sheet music) to have the accent to the right and not to the left of the accidental, much like writing an accidental to the right and not to the left of the note name. I corrected my previous post but maybe now when the accidentals are differentiated only by shape and not by place it's possible to make an exception for people like me that when writing text the accents can come after the accidental, but the accidental and the accents still have to come in monotonic order.
That's fine, since you have a good reason for doing it. I just thought you might have been following the old convention.
But there is also a school of thought that says that an accented symbol should be thought of as a single symbol that has only been broken into multiple characters to minimise the number of characters in the font, like diacritics on letters, like "é".
There is even a sense in which combinations like


and particularly


are like a single symbol whose geometrical beauty and rapid recognition is lost when rearranged as


and


. So nowadays I am inclined to write them in text in the same order as on the staff. i.e. staff


o text E



. It's tempting to go all the way and write



E.