Zefram wrote:
Ed Murphy wrote:
(c) Each ID number SHOULD be as small as possible. A player
may, with Agoran consent, make an entity's ID number chaotic.
Also need "an ID number is orderly by default". Possibly also explicate
that "orderly" and "chaotic" are antonymous. You could also upgrade the
SHOULD to a MUST, qualified with a clause regarding purported allocations
later found to be erroneous. I'd like the officer who uses a 17-digit
number to be subject to punishment.
I'm thinking "SHALL, unless e reasonably believes that assigning a
smaller number might be invalid".
Agoran consent might be too slow. Other items will arrive that have to
receive ID numbers, and until the chaoticity goes through they'll have
to receive very high ID numbers.
Agoran consent can be done in four days, enough to beat an ASAP
requirement.
but Eris's 17-digit monstrosities
I think e has something more ambitious in mind. I didn't grasp the
relevance of "computable numbers" when we're explicitly limiting this
to natural numbers. But perhaps e plans to use Graham's number, or a
length-17 chained arrow expression (using Conway's notation).
Fortunately, these could be reported using the same language that was
used to assign them in the first place. Successors could even be
reported as E1+1, E1+2, etc., provided that they're far enough apart
to avoid collisions.
