On 10/29/25 11:23, 4st nomic via agora-official wrote:
> CoE: missing names, bleeding eyes, subject line date
I CFJ: On or about 2025-10-29 15:23:35 UTC, 4st issued a doubt on a
document.
Arguments:
{
In [0], 4st attempted to doubt eir previously-published Illuminator's
report [1]. Under Rule 2202, in order to issue a doubt on a document,
one must "explain[] the scope and nature of a perceived error in it (or
in a statement it attests to)". 4st's purported doubt gave "missing
names, bleeding eyes, subject line date" as the identified errors.
Each of these purported errors has some potential issues:
1. "missing names" appears to refer to the lack of expansions of the
abbreviations used in the "NAME" column. Does this actually constitute
an error? Moreover, I initially assumed this meant one or more players
were missing from the list (thus implying they had 0 radiance); is this
sufficiently "clear[] and unambiguous[]" to meet the "by announcement"
standard in Rule 478?
2. "bleeding eyes" refers to inconsistent formatting of the table. It's
doubtful whether this is an "error" in the report, given that 4st is not
alleging the report is factually incorrect.
3. "subject line date" refers to the failure to update the date in the
subject line. The subject line of the email is not part of the message,
and thus is not part the document purportedly being doubted.
Additionally, since Rule 2201 requires identifying "a perceived error in
[the document]", does the identification of multiple purported errors
unconditionally cause the doubt to fail? If not, and if at least one of
the above errors is not actually a "perceived error in [the document]",
does *that* cause the doubt to fail?
}
Evidence:
{
------------------------------------------------------------------------
Rule 2201/14 (Power=3)
Self-Ratification
When a public document published less than 180 days ago is first
continuously undoubted for two weeks after publication:
- If the rules define it as self-ratifying, it is ratified.
- If the rules define it as a self-ratifying attestation to a
given statement, the statement is ratified, with the publication
time being the instant at which the document was published.
This clause is inapplicable if the statement to be ratified
cannot be reasonably ascertained from the ruleset and the
contents of the message.
Any person CAN by announcement issue a doubt (syn. claim of
error), identifying a public document published less than 180 days
ago and explaining the scope and nature of a perceived error in it
(or in a statement it attests to).
The definition of documents as self-ratifying and the definition
of documents as self-ratifying attestations are secured at power
3.
When this happens, the publisher of the original document SHALL
(if e was required to publish that document) or SHOULD (otherwise)
do one of the following in a timely fashion, in an announcement
that clearly cites the claim of error:
1. Deny the claim (causing it to cease to be a doubt).
2. Publish a revision.
3. Initiate an inquiry case regarding the truth of the claim
(if the subject is actually a matter of law), or cite a
relevant existing inquiry case.
The issuance of a doubt on a documents, the denial of a claim of
error, and the ceasing of a doubt on a document to be a doubt are
secured at power 3.
------------------------------------------------------------------------
Rule 478/42 (Power=3)
Fora
Publicity is a secured forum switch with values Public,
Discussion, and Foreign (default), tracked by the Registrar.
The Registrar CAN change the publicity of a forum without
objection as long as:
1. e sends eir announcement of intent to that forum; and
2. if the forum is to be made public, the announcement by which
the Registrar makes that forum public is sent to all existing
public fora.
Each player should ensure e can receive messages via each public
forum.
A public message is a message sent via a public forum, or sent to
all players and containing a clear designation of intent to be
public. A rule can also designate that a part of one public
message is considered a public message in its own right. To
"publish" or "announce" something is to send a public message
whose body contains that thing. To do something "publicly" is
to do that thing within a public message.
Where the rules define an action that a person CAN perform "by
announcement", that person performs that action by, in a single
public message, specifying the action and setting forth intent to
perform that action by sending that message, doing both clearly
and unambiguously.
Any action performed by sending a message is performed at the time
date-stamped on that message. Actions in messages (including
sub-messages) are performed in the order they appear in the
message, unless otherwise specified. Allowing actions performed by
sending a message to take place simultaneously must be done
explicitly and is secured at power 2.
------------------------------------------------------------------------
[0]
https://mailman.agoranomic.org/cgi-bin/mailman/private/agora-official/2025-October/018779.html
[1]
https://mailman.agoranomic.org/cgi-bin/mailman/private/agora-official/2025-October/018776.html
}
--
Janet Cobb
Assessor, Rulekeepor
