-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathcurrent_FLR.txt
4355 lines (3527 loc) · 183 KB
/
current_FLR.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
THE FULL LOGICAL RULESET
Most Recent Ruleset Change Recorded:
Adoption of Proposal 7786, 29 August 2015
Last Ruleset Ratification:
Short Logical Ruleset of 7 Apr 2014, ratified on 1 May 2014
Highest Rule ID number ever assigned:
Rule 2454
Online documents:
http://faculty.washington.edu/kerim/nomic/rkeep/current_flr.txt (FLR)
http://faculty.washington.edu/kerim/nomic/rkeep/current_slr.txt (SLR)
----------------------------------------------------------------------
Statistics
Current total number of rules: 71
Power distribution:
1 with Power=4
1 with Power=3.2
1 with Power=3.1
36 with Power=3
11 with Power=2
2 with Power=1.7
2 with Power=1.5
17 with Power=1
----------------------------------------------------------------------
Index of Rules
* The Game of Agora
Rule 101: The Game of Agora
Rule 2125: Regulation Regulations
Rule 2152: Mother, May I?
Rule 1688: Power
Rule 2140: Power Controls Mutability
Rule 104: First Speaker
* Rules
Rule 2141: Role and Attributes of Rules
Rule 217: Interpreting the Rules
Rule 1030: Precedence between Rules
Rule 2240: No Cretans Need Apply
Rule 105: Rule Changes
Rule 1681: The Logical Rulesets
Rule 1051: The Rulekeepor
Rule 2327: Read the Ruleset Week
Rule 2429: Bleach
Rule 2430: Cleanup Time
* Players
Rule 869: How to Join and Leave Agora
Rule 2139: The Registrar
Rule 1789: Cantus Cygneus
Rule 2438: Ribbons
* Definitions
Rule 1023: Common Definitions
Rule 1769: Holidays
Rule 2448: Eras
Rule 2162: Switches
Rule 478: Fora
Rule 1728: Dependent Actions
Rule 2124: Agoran Satisfaction
* Offices
Rule 1006: Offices
Rule 2143: Official Reports and Duties
Rule 2379: No News Is Some News
Rule 2160: Deputisation
Rule 2154: Election Procedure
Rule 2138: The Interstellar Associate Director of Personnel
Rule 1551: Ratification
Rule 2202: Ratification Without Objection
Rule 2201: Self-Ratification
Rule 103: The Speaker
Rule 2423: First Among Equals
Rule 2446: The Agoran Newspaper
* Agoran Decisions
Rule 693: Agoran Decisions
Rule 107: Initiating Agoran Decisions
Rule 683: Voting on Agoran Decisions
Rule 2422: Voting Strength
Rule 2127: Conditional Votes
Rule 2168: Extending the voting period
Rule 208: Resolving Agoran Decisions
Rule 955: Determining the Will of Agora
Rule 879: Quorum
Rule 2034: Vote Protection and Cutoff for Challenges
* Proposals
Rule 2350: Proposals
Rule 2445: How to Pend a Proposal
Rule 2443: Expediting Proposals
Rule 106: Adopting Proposals
Rule 1607: Distribution
Rule 1950: Decisions with Adoption Indices
Rule 2137: The Assessor
Rule 2431: Proposal Competitions
Rule 1698: Agora Is A Nomic
Rule 2444: Silver Quill
* Adjudication
Rule 991: Calls for Judgement
Rule 591: Delivering Judgements
Rule 911: Motions and Moots
Rule 2175: Judicial Retraction and Excess
Rule 2426: Cards
Rule 2427: Red Cards
* Patent Titles and Degrees
Rule 649: Patent Titles
Rule 1367: Degrees
Rule 2231: Order of the Hero of Agora Nomic
Rule 2415: Badges
* Trophies
Rule 1727: Happy Birthday
Rule 2029: Town Fountain
(Garbage Bin)
----------------------------------------------------------------------
Rules are listed as follows. "nnnn" is the rule's ID number, loosely
regulated by Rule 2141; ID numbers are assigned in increasing order
and are never reused. "r" is the rule's revision number, not defined
by the rules; any amendment (but not retitling or mutation) increases
this number.
Rule nnnn/r (Power=p)
Title of Rule
Annotations in square brackets are unofficial and have no legal force.
They are added at the Rulekeepor's discretion.
----------------------------------------------------------------------
======================================================================
The Game of Agora
----------------------------------------------------------------------
Rule 101/17 (Power=3)
The Game of Agora
Agora is a game of Nomic, wherein Persons, acting in accordance
with the Rules, communicate their game Actions and/or results of
these actions via Fora in order to play the game. The game may
be won, but the game never ends.
Please treat Agora Right Good Forever.
[CFJ 24: Players must obey the Rules even in out-of-game actions.]
[CFJ 825 (called 7 November 1995): Players must obey the Rules even if
no Rule says so.]
[CFJ 1848 (called 21 December 2007): The game must operate according
to the rules that prevail at the time, and not attempt to incorporate
any retroactive changes made in the future.]
[CFJ 1709 (called 26 July 2007): The rules are binding on all those
who play the game in the broader sense, regardless of whether they
have the rule-defined status of "player".]
[CFJs 1911-1914 (called 18 March 2008): Physical realities supersede
the Rules by default.]
History:
Initial Immutable Rule 101, Jun. 30 1993
Mutated from MI=Unanimity to MI=3 by Proposal 1480, Mar. 15 1995
Amended(1) by Proposal 3915 (harvel), Sep. 27 1999
Amended(2) by Proposal 4833 (Maud), 6 August 2005
Amended(3) by Proposal 4866 (Goethe), 27 August 2006
Amended(4) by Proposal 4867 (Goethe), 27 August 2006
Amended(5) by Proposal 4887 (Murphy), 22 January 2007
Amended(6) by Proposal 4944 (Zefram), 3 May 2007
Amended(7) by Proposal 5090 (Zefram), 25 July 2007
Amended(8) by Proposal 5731 (Goethe; disi.), 8 October 2008
Retitled by Proposal 5769 (Goethe), 17 October 2008
Amended(9) by Proposal 5769 (Goethe), 17 October 2008
Amended(10) by Proposal 5773 (Goethe), 17 October 2008
Amended(11) by Proposal 6028 (Murphy), 8 January 2009
Amended(12) by Proposal 6158 (Goethe), 31 March 2009
Amended(13) by Proposal 6589 (c.; disi.), 6 December 2009
Amended(14) by Proposal 7183 (G.), 26 February 2012
Amended(15) by Proposal 7596 (omd), 14 September 2013
Retitled and amended(16) by Proposal 7614 (G.), 13 January 2014
Amended(17) by Proposal 7743 (G.), 12 May 2015
----------------------------------------------------------------------
Rule 2454/0 (Power=0.5)
The New Map
_______
| _
_| A |
_______|
History:
Created by Proposal 7785 (G.), 29 August 2015
----------------------------------------------------------------------
Rule 2125/8 (Power=3)
Regulation Regulations
An action is regulated if: (1) the Rules limit, allow, enable,
or permit its performance; (2) describe the circumstances under
which the action would succeed or fail; or (3) the action would,
as part of its effect, modify information for which some player
is required to be a recordkeepor.
Regulated Actions CAN only be performed as described by the
Rules. The Rules SHALL NOT be interpreted so as to proscribe
unregulated actions.
History:
Created by Proposal 4866 (Goethe), 27 August 2006
Amended(1) by Proposal 5235 (Goddess Eris), 3 October 2007
Amended(2) by Proposal 5536 (Murphy), 7 June 2008
Amended(3) by Proposal 5739 (root), 9 October 2008
Amended(4) by Proposal 6022 (Murphy), 22 December 2008
Amended(5) by Proposal 6251 (Murphy), 9 May 2009
Amended(6) by Proposal 6269 (Pavitra), 11 May 2009
Amended(7) by Proposal 6327 (Murphy), 29 May 2009
Amended(8) by Proposal 7614 (G.), 13 January 2014
----------------------------------------------------------------------
Rule 2152/7 (Power=3)
Mother, May I?
The following terms are defined. These definitions are used
when a rule includes a term in all caps, and provide guidance in
determining the ordinary-language meaning of a term when a rule
includes a term otherwise. Earlier definitions take precedence
over later ones. If a rule specifies one or more persons in
connection with a term, then the term applies only to the
specified person(s).
1. CANNOT, IMPOSSIBLE, INEFFECTIVE, INVALID: Attempts to
perform the described action are unsuccessful.
2. MUST NOT, MAY NOT, SHALL NOT, ILLEGAL, PROHIBITED: Performing
the described action violates the rule in question.
3. NEED NOT, OPTIONAL: Failing to perform the described action
does not violate the rules.
4. SHOULD NOT, DISCOURAGED, DEPRECATED: Before performing the
described action, the full implications of performing it
should be understood and carefully weighed.
5. CAN: Attempts to perform the described action are successful.
6. MAY: Performing the described action does not violate the
rules.
7. MUST, SHALL, REQUIRED, MANDATORY: Failing to perform the
described action violates the rule in question.
8. SHOULD, ENCOURAGED, RECOMMENDED: Before failing to perform
the described action, the full implications of failing to
perform it should (in the ordinary-language sense) be
understood and carefully weighed.
[CFJ 1132: A Player failing to perform a duty required by the Rules
within a reasonable time may be in violation of the Rules, even if the
Rules do not provide a time limit for the performance of that duty.]
[CFJ 1488 (called 11 February 2004): Engineering a situation in which
other players are unable to follow a particular rule is not in itself
a violation of that rule.]
[CFJ 2395 (called 1 March 2009): Even without this being explicitly
specified in the rules, it is possible for a non-player to violate a
rule by missing a deadline.]
[CFJ 1990 (called 7 June 2008): "Allowed" may refer to either
possibility or permissibility depending on context.]
[CFJs 2120-2121 (called 4 August 2008): A requirement of the form
'within <time limit>, a player SHALL <action> by announcement' means
that the player CAN perform the action, and SHALL do so within the
time limit.]
[CFJ 2230 (called 16 October 2008): In a statement of the form "an
action that X may take", 'may' generally means 'might', i.e. CAN.]
[CFJ 2282 (called 19 November 2008): To state that an entity "MUST"
have certain properties refers to possibility, not legality.]
[CFJ 2414 (called 14 March 2009): A rule of the form "X SHOULD be
interpreted as Y" does not allow players to bypass the interpretation
by failing to perform the described action.]
History:
Created by Proposal 5053 (Murphy), 5 July 2007
Power changed from 1 to 2 by Proposal 5054 (Murphy), 5 July 2007
Amended(1) by Proposal 5189 (Levi), 3 September 2007
Power changed from 2 to 3 by Proposal 5247 (AFO), 14 October 2007
Amended(2) by Proposal 5353 (Murphy; disi.), 16 December 2007
Amended(3) by Proposal 5354 (Murphy), 16 December 2007
Amended(4) by Proposal 5535 (Murphy), 7 June 2008
Amended(5) by Proposal 6571 (ais523), 28 November 2009
Amended(6) by Proposal 6983 (Murphy), 10 April 2011
Amended(7) by Proposal 7613 (Arufonsu), 11 January 2014
----------------------------------------------------------------------
Rule 1688/8 (Power=3)
Power
The Power of an entity is a non-negative rational number. An
Instrument is an entity with positive Power.
The Power of an entity cannot be set or modified except as
stipulated by the Rules. All entities have Power zero except
where specifically allowed by the rules.
Power less than one is called Ephemeral power, and an instrument
with a power less than one is an Ephemeral instrument.
A Rule that makes a change, action, or value secured (hereafter
the securing Rule) thereby makes it IMPOSSIBLE to perform that
change or action, or to set or modify that value, except as
allowed by an Instrument with Power greater than or equal to the
change's Power Threshold. This Threshold defaults to the
securing Rule's Power, but CAN be lowered as allowed by that
Rule (including by the Rule itself).
History:
Created by Proposal 3445 (General Chaos), Mar. 26 1997
Amended(1) by Proposal 3994 (harvel), Apr. 20 2000
Amended(2) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(3) by Proposal 4940 (Zefram), 29 April 2007
Amended(4) by Proposal 5276 (Murphy, Pavitra, Zefram), 7 November 2007
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
ais523), 23 January 2009
Amended(5) by Proposal 6513 (coppro; disi.), 3 October 2009
Amended(6) by Proposal 6815 (Murphy, ais523), 4 September 2010
Amended(7) by Proposal 7759 (G.), 19 July 2015
Amended(8) by Proposal 7781 (the Warrigal), 14 August 2015
----------------------------------------------------------------------
Rule 2140/1 (Power=3)
Power Controls Mutability
No entity with power below the power of this rule can
(a) cause an entity to have power greater than its own.
(b) adjust the power of an instrument with power greater than
its own.
(c) set or modify any other substantive aspect of an instrument
with power greater than its own. A "substantive" aspect of
an instrument is any aspect that affects the instrument's
operation.
[CFJ 2981 (called 21 March 2011): An attribute of an instrument is not
"modified" when an initial value is set for it.]
[CFJ 2945 (called 22 December 2010): An attribute of an entity is
"changed" when it is removed/unset.]
History:
Created by Proposal 4940 (Zefram), 29 April 2007
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
ais523), 23 January 2009
Amended(1) by Proposal 6992 (Murphy, omd), 10 April 2011
----------------------------------------------------------------------
Rule 2449/0 (Power=3)
Winning the Game
When the Rules state that a Player or Players win the game,
those players win the game; specifically they win the Round
that ends with the indicated win. Agora itself does not end and
the ruleset remains unchanged. The Herald is then authorized to
award those players the Patent Title of Champion.
Winning the game is secured, except as described in Ephemeral
Rules.
History:
Created by Proposal 7760 (G.), 19 July 2015
----------------------------------------------------------------------
Rule 104/0 (Power=3)
First Speaker
The Speaker for the first game shall be Michael Norrish.
[CFJ 1534 (called 8 March 2005): This does not mean that Michael
Norrish necessarily fills the position of Speaker at the present
time.]
[CFJ 2154: (called 8 September 2008) The Speaker for the first game
shall be Michael Norrish.]
History:
Initial Immutable Rule 104, Jun. 30 1993
Mutated from MI=Unanimity to MI=3 by Proposal 1482, Mar. 15 1995
----------------------------------------------------------------------
======================================================================
Rules
----------------------------------------------------------------------
Rule 2141/9 (Power=3)
Role and Attributes of Rules
A rule is a type of instrument with the capacity to govern the
game generally, and is always taking effect. A rule's content
takes the form of a text, and is unlimited in scope.
Every rule has power between 0.1 and 4.0 inclusive. It is
not possible for a rule to have a power outside this range.
Rules have ID numbers, to be assigned by the Rulekeepor.
Every rule shall have a title to aid in identification. If a
rule ever does not have a title, the Rulekeepor SHALL assign a
title to it by announcement in a timely fashion.
For the purposes of rules governing modification of instruments,
the text, power, ID number, and title of a rule are all
substantive aspects of the rule. However, rules to the contrary
notwithstanding, the Rulekeepor CAN set rule aspects as
described elsewhere in this rule.
[CFJ 1498 (called 12 April 2004): A rule's title is not strictly a
name for the rule, and so rule titles are not subject to the
uniqueness requirement on names of rule-defined entities.]
[CFJ 2013 (called 17 June 2009): Rule 2141 does not imply that the
power of rules is physically unlimited: they can only affect the world
outside the game by prescribing or proscribing player behavior.]
[CFJ 2213 (called 7 October 2008): The powers granted to rules by the
first paragraph of Rule 2141 are general, and only apply as otherwise
stated by the Rules.]
History:
Created by Proposal 4940 (Zefram), 29 April 2007
Amended(1) by Proposal 5110 (Murphy), 2 August 2007
Amended(2) by Proposal 5994 (Murphy), 7 December 2008
Amended(3) by Proposal 6053 (Murphy, woggle, ais523), 23 January 2009
Amended(4) by Proposal 6124 (ehird), 15 March 2009
Amended(5) by Proposal 6670 (coppro), 14 March 2010
Amended(6) by Proposal 6992 (Murphy, omd), 10 April 2011
Amended(7) by Proposal 7420 (omd), 27 March 2013
Amended(8) by Proposal 7614 (G.), 13 January 2014
Amended(9) by Proposal 7759 (G.), 19 July 2015
----------------------------------------------------------------------
Rule 217/11 (Power=3)
Interpreting the Rules
When interpreting and applying the rules, the text of the rules
takes precedence. Where the text is silent, inconsistent, or
unclear, it is to be augmented by game custom, common sense,
past judgements, and consideration of the best interests of the
game.
Definitions and prescriptions in the rules are only to be
applied using direct, forward reasoning; in particular, an
absurdity that can be concluded from the assumption that a
statement about rule-defined concepts is false does not
constitute proof that it is true. Definitions in lower-powered
Rules do not overrule common-sense interpretations or common
definitions of terms in higher-powered rules.
Rules to the contrary notwithstanding, any rule change that
would (1) prevent a person from initiating a formal process to
resolve matters of controversy, in the reasonable expectation
that the controversy will thereby be resolved; or (2) prevent a
person from causing formal reconsideration of any judicial
determination that e should be punished, is wholly void and
without effect.
[CFJ 1439 (called 20 February 2003): A difference in language
qualifies as a difference in dialect; it is possible to take game
actions by messages in languages other than English.]
[CFJ 1460 (called 4 April 2003): If a message is in a language other
than English, and its intended audience does not understand the
language, this constitutes gross unclarity that makes the message
ineffective.]
[CFJ 712: Referring to a Player by a method other than eir name or
nickname is acceptable, as long as it is unambiguous.]
[CFJ 1861 (called 8 January 2008): A player's legal name (legal in eir
country of residence) is not necessarily an acceptable way to refer to
em.]
[CFJ 1782 (called 4 November 2007): Referring to a player by the name
of an office that e holds suffices to identify em uniquely as a
person, if there is no doubt regarding who holds that office.]
[CFJ 1460 (called 4 April 2003): Extremely complex synonyms, requiring
extensive effort to interpret correctly, can constitute a sufficient
degree of unclarity as to render the message ineffective.]
[CFJ 1840 (called 20 December 2007): A proper noun that has not been
explicitly defined does not adequately refer to any entity, and is not
implicitly defined by the context in which it is used.]
[CFJ 1580 (called 12 January 2006): Base64 encoding of (part of) a
message, other than in the context of MIME with appropriate headers,
can render a message ineffective for unclarity, because the decoding
step requires unreasonable effort within the meaning of CFJ 1460.]
[CFJ 1741 (called 11 September 2007): HTML encoding (including
numerical character entity encoding) does not render a message
ineffective for unclarity if a suitable MIME type is indicated by a
header.]
[CFJ 1741 (called 11 September 2007): An email message does not need
the RFC-required "MIME-Version:" header in order for it to be
interpreted in the MIME way.]
[CFJ 1536 (called 13 March 2005): The phrase "AOL!" is not a
sufficiently clear synonym for "Me too!".]
[CFJ 1770 (called 23 October 2007): A contract can redefine a
rule-defined term in its own way, and the contract's definition will
then apply in situations governed by the contract.]
[CFJ 1885 (called 26 January 2008): A word or phrase can acquire a
meaning by custom, provided that it is a reasonable meaning and does
not unreasonably change the meaning of phrases that already have a
meaning.]
[CFJ 1831 (called 10 December 2007): Mentioning a URI, without
surrounding text stating its significance, does not incorporate
anything identified by that URI into the message that mentions the
URI.]
[CFJ 1831 (called 10 December 2007): Character sequences within a URI
by default have no significance other than their functional role as
part of the URI.]
[CFJ 2258 (called 6 November 2008): Changes in whitespace are also
inconsequential.]
[CFJ 1139: Interpretations [judgements at the time of CFJ 1139] need
not necessarily accord with the reasoning and arguments of Judges or
Justices given in past CFJs.]
History:
Initial Mutable Rule 217, Jun. 30 1993
Amended(1) by Proposal 1635, Jul. 25 1995
Infected and amended(2) by Rule 1454, Aug. 7 1995
Amended(3) by Proposal 2507, Mar. 3 1996
Amended(4) by Proposal 4825 (Maud), 17 July 2005
Power changed from 1 to 3 by Proposal 4867 (Goethe), 27 August 2006
Amended(5) by Proposal 4867 (Goethe), 27 August 2006
Retitled by Proposal 5105 (Zefram), 1 August 2007
Amended(6) by Proposal 5105 (Zefram), 1 August 2007
Amended(7) by Proposal 7351 (G., ais523, Machiavelli), 27 March 2013
Amended(8) by Proposal 7520 (omd), 19 July 2013
Amended(9) by Proposal 7584 (omd), 24 August 2013
Amended(10) by Proposal 7614 (G.), 13 January 2014
Amended(11) by Proposal 7662 (omd), 3 June 2014
----------------------------------------------------------------------
Rule 1030/11 (Power=3.2)
Precedence between Rules
In a conflict between Rules, the conflict shall be resolved by
performing the following comparisons in the sequence written in
this rule, until the conflict is resolved.
- In a conflict between Rules with different Power, the Rule
with the higher Power takes precedence over the Rule with the
lower Power; otherwise,
- If all of the Rules in conflict explicitly say that their
precedence relations are determined by some other Rule for
determining precedence relations, then the determinations of
the precedence-determining Rule shall be used to resolve the
conflicts; otherwise,
- If at least one of the Rules in conflict explicitly says of
itself that it defers to another Rule (or type of Rule) or
takes precedence over another Rule (or type of Rule), then
such provisions shall be used to resolve the conflict, unless
they lead to contradictions between each other; otherwise,
- If any of the rules in conflict have ID numbers, then the Rule
with the lowest ID number takes precedence; otherwise,
- The Rule enacted earliest takes precedence.
Clauses in any other rule that broadly claim precedence (e.g.
over "all rules" of a certain class) shall be, prima facie,
considered to be limited claims of precedence or deference that
are applicable only when such claims are evaluated as described
within the above sequence.
No change to the Ruleset can occur that would cause a Rule to
directly claim precedence over this Rule as a means of
determining precedence. This applies to changes by the
enactment or amendment of a Rule, or of any other form. This
Rule takes precedence over any Rule that would permit such a
change to the Ruleset.
[CFJ 1104 (called 20 August 1998): The presence in a Rule of deference
clause, claiming that the Rule defers to another Rule, does not
prevent a conflict with the other Rule arising, but shows only how the
Rule says that conflict is to be resolved when it does arise.]
[CFJs 1114-1115 (called 27 January 1999): This Rule is to be applied
to resolve Rule conflicts on a case-by-case basis; just because a Rule
is inapplicable in one situation due to conflict with a Rule of higher
precedence does not mean that the Rule is nullified in all cases.]
History:
Initial Mutable Rule 212, Jun. 30 1993
Amended by Proposal 1030, Sep. 15 1994
Amended by Rule 750, Sep. 15 1994
Amended(1) by Proposal 1527, Mar. 24 1995
Amended(2) by Proposal 1603, Jun. 19 1995
Amended(3) by Proposal 2520, Mar. 10 1996
Mutated from MI=1 to MI=3 by Proposal 2763 (Steve), Nov. 30 1996
Amended(4) by Proposal 3445 (General Chaos), Mar. 26 1997, cosmetic
(unattributed)
Amended(5) by Proposal 4887 (Murphy), 22 January 2007
Amended(6) by Proposal 5110 (Murphy), 2 August 2007
Amended(7) by Proposal 6285 (Goethe), 19 May 2009
Amended(8) by Proposal 6292 (Goethe), 19 May 2009
Title changed by Proposal 6292 (Goethe), 19 May 2009
Power changed from 3 to 3.2 by Proposal 6292 (Goethe), 19 May 2009
Amended(9) by cleaning (Murphy), 16 August 2009
Amended(10) by Proposal 7235 (omd), 10 June 2012
Amended(11) by Proposal 7334 (woggle), 27 March 2013
----------------------------------------------------------------------
Rule 2240/1 (Power=3)
No Cretans Need Apply
In a conflict between clauses of the same Rule, if exactly one
claims precedence over the other, then it takes precedence;
otherwise, the later clause takes precedence.
History:
Created by Proposal 6073 (Murphy), 22 February 2009
Amended(1) by Proposal 6429 (Murphy), 18 August 2009
----------------------------------------------------------------------
Rule 105/12 (Power=3)
Rule Changes
Where permitted by other rules, an instrument generally can,
as part of its effect,
(a) enact a rule. The new rule has power equal to the minimum
of the power specified by the enacting instrument,
defaulting to one if the enacting instrument does not
specify or if it specifies a power less than 0.1, and the
maximum power permitted by other rules. The enacting
instrument may specify a title for the new rule, which if
present shall prevail. The ID number of the new rule cannot
be specified by the enacting instrument; any attempt to so
specify is null and void.
(b) repeal a rule. When a rule is repealed, it ceases to be a
rule, and the Rulekeepor need no longer maintain a record
of it.
(c) reenact a rule. A repealed rule identified by its most
recent rule number may be reenacted with the same ID number
and the next change identifier. If no text is specified,
the rule is reenacted with the same text it had when it was
most recently repealed. If the reenacting proposal provides
new text for the rule, the rule must have materially the
same purpose as did the repealed version; otherwise, the
attempt to reenact the rule is null and void.
(d) amend the text of a rule.
(e) retitle a rule.
(f) change the power of a rule.
A rule change is any effect that falls into the above classes.
Rule changes always occur sequentially, never simultaneously.
Any ambiguity in the specification of a rule change causes that
change to be void and without effect. An inconsequential
variation in the quotation of an existing rule does not
constitute ambiguity for the purposes of this rule, but any
other variation does.
A rule change is wholly prevented from taking effect unless its
full text was published, along with an unambiguous and clear
specification of the method to be used for changing the rule, at
least 4 days and no more than 60 days before it would otherwise
take effect.
This rule provides the only mechanism by which rules can be
created, modified, or destroyed, or by which an entity can
become a rule or cease to be a rule.
[CFJ 1499 (called 20 April 2004), CFJ 1623 (called 1 April 2007): If a
low-power rule states that an officer can repeal the rule under
certain circumstances, then the rule cannot actually be repealed by
this process, because the officer, not being an instrument, is
categorically incapable of performing rule changes; this is different
from the situation where a rule can be triggered to repeal itself.]
[CFJ 708 (called October 1994): An Amendment of a non-existing Rule is
not a legal Rule Change.]
[CFJ 1625 (called 1 April 2007): Where a proposal specifies a rule to
amend by both number and title, and the number and title given
identify different rules, this constitutes ambiguity that nullifies
the attempted rule change.]
[CFJ 1644 (called 29 April 2007): Where a proposal contains the form
of words "Change the power of rule NNNN to P and amend it by XXX.",
where XXX specifies a text change, this constitutes two attempted rule
changes.]
[CFJ 1638 (called 29 April 2007): Where a proposal contains the form
of words "Amend rule NNNN by XXX. Amend rule NNNN by YYY.", this
constitutes two separate attempts at rule changes, even though both
attempt to amend the same rule.]
[CFJ 1642 (called 29 April 2007): Where a proposal contains the form
of words "Amend rule NNNN by XXX. Further amend rule NNNN by YYY.",
where both XXX and YYY specify text changes, this constitutes two
separate attempts at rule changes.]
[CFJ 1640 (called 29 April 2007): Where a proposal contains the form
of words "Amend rule NNNN by XXX and YYY.", where both XXX and YYY
specify text changes, this constitutes a single attempt at a rule
change, even though it is specified in two parts.]
[CFJ 1641 (called 29 April 2007): Where a proposal contains the form
of words "Amend rule NNNN by XXX and by YYY.", where both XXX and YYY
specify text changes, this constitutes a single attempt at a rule
change, even though it is specified in two parts.]
[CFJ 1643 (called 29 April 2007): Where a proposal specifies a single
rule amendment in two parts, and one of the parts is not possible but
the other is possible, the possible part is applied alone.]
[CFJ 2201 (called 30 September 2008): The permission required by Rule
105 need not be explicit.]
History:
Created by Proposal 4894 (Murphy), 12 February 2007
Renumbered from 2131 to 105 by Proposal 4894 (Murphy), 12 February
2007
Power changed from 1 to 3 by Proposal 4894 (Murphy), 12 February 2007
Retitled by Proposal 4894 (Murphy), 12 February 2007
Amended(1) by Proposal 4894 (Murphy), 12 February 2007
Amended(2) by Proposal 4940 (Zefram), 29 April 2007
Amended(3) by Proposal 5110 (Murphy), 2 August 2007
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
ais523), 23 January 2009
Amended(4) by Proposal 6734 (comex), 6 June 2010
Amended(5) by Proposal 6741 (comex; disi.), 1 July 2010
Amended(6) by Proposal 7433 (Walker), 27 May 2013
Amended(7) by Proposal 7607 (OscarMeyr), 13 December 2013
Amended(8) by Proposal 7614 (G.), 13 January 2014
Amended(9) by SLR ratification (Proposal 7638; omd), 1 May 2014
Amended(10) by Proposal 7647 (omd), 3 June 2014
Amended(11) by Proposal 7710 (G.), 3 November 2014
Amended(12) by Proposal 7759 (G.), 19 July 2015
----------------------------------------------------------------------
Rule 1681/20 (Power=1)
The Logical Rulesets
The Short Logical Ruleset (SLR) is a format of the ruleset. In
this format, each rule is assigned to a category, and the rules
are grouped according to their category.
Rules are assigned to, ordered within, or moved between
categories, and categories are added, changed, or empty
categories removed, as the Rulekeepor sees fit.
The listing of each rule in the SLR must include the rule's ID
number, revision number, power, title, and text.
The Rulekeepor is strongly DISCOURAGED from including any
additional information in the SLR, except that which increases
the readability of the SLR.
The Full Logical Ruleset (FLR) is a format of the ruleset. In
this format, rules are assigned to the same category and
presented in the same order as in the SLR. The FLR must contain
all the information required to be in the SLR, and any
historical annotations which the Rulekeepor is required to
record.
The Rulekeepor SHOULD also include any other information which e
feels may be helpful in the use of the ruleset in the FLR.
Whenever a rule is changed in any way, the Rulekeepor SHALL
record a historical annotation to the rule indicating:
a) The type of change.
b) The date on which the change took effect.
c) The mechanism that specified the change.
d) If the rule was changed due to a proposal, then that
proposal's ID number, author, and co-author(s) (if any).
History:
Created by Proposal 2783 (Chuck), Jan 15 1997
Amended(1) by Proposal 3500 (Crito), Jun. 3 1997, substantial
(unattributed)
Amended(2) by Proposal 3624 (Chuck), Dec. 29 1997
Amended(3) by Proposal 3704 (General Chaos), Mar. 19 1998
Amended(4) by Proposal 3902 (Murphy), Sep. 6 1999
Amended(5) by Proposal 4002 (harvel), May 8 2000
Amended(6) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(7) by Proposal 4841 (Goethe), 27 October 2005
Amended(8) by Proposal 4868 (Goethe), 27 August 2006
Amended(9) by Proposal 4887 (Murphy), 22 January 2007
Amended(10) by Proposal 5006 (Zefram), 18 June 2007
Amended(11) by Proposal 5110 (Murphy), 2 August 2007
Amended(12) by Proposal 5334 (Murphy), 5 December 2007
Amended(13) by Proposal 5956 (comex), 17 November 2008
Amended(14) by Proposal 6019 (Murphy), 22 December 2008
Amended(15) by Proposal 6026 (Murphy), 22 December 2008
Amended(16) by Proposal 6053 (Murphy, woggle, ais523), 23 January 2009
Amended(17) by Proposal 6124 (ehird), 15 March 2009
Amended(18) by Proposal 6662 (Murphy; disi.), 10 March 2010
Amended(19) by Proposal 7599 (Walker), 14 September 2013
Amended(20) by Proposal 7604 (G.), 13 December 2013
----------------------------------------------------------------------
Rule 1051/18 (Power=1)
The Rulekeepor
The Rulekeepor is an office; its holder is responsible for
maintaining the text of the rules of Agora.
The Rulekeepor's Weekly report includes the Short Logical
Ruleset. The Rulekeepor's Monthly report includes the Full
Logical Ruleset.
History:
...
Amended(1) by Proposal 1735, Oct. 15 1995
Amended(2) by Proposal 2042, Dec. 11 1995
Amended(3) by Proposal 2048, Dec. 19 1995
Amended(4) by Proposal 2662, Sep. 12 1996
Amended(5) by Proposal 2696, Oct. 10 1996
Null-Amended(6) by Proposal 2710, Oct. 12 1996
Amended(7) by Proposal 2741 (Zefram), Nov. 7 1996, substantial
Infected and Amended(8) by Rule 1454, Nov. 27 1996,
substantial (unattributed)
Amended(9) by Proposal 2783 (Chuck), Jan. 15 1997, substantial
Amended(10) by Proposal 3452 (Steve), Apr. 7 1997, substantial
Amended(11) by Proposal 3675 (Michael), Jan. 30 1998
Amended(12) by Proposal 3827 (Kolja A.), Feb. 4 1999
Amended(13) by Proposal 3871 (Peekee), Jun. 2 1999
Amended(14) by Proposal 3882 (harvel), Jul. 21 1999
Amended(15) by Proposal 3902 (Murphy), Sep. 6 1999
Amended(16) by Proposal 4002 (harvel), May 8 2000
Amended(17) by Proposal 4250 (harvel), 19 February 2002
Amended(18) by Proposal 5237 (AFO; disi.), 3 October 2007
----------------------------------------------------------------------
Rule 2327/1 (Power=1)
Read the Ruleset Week
The first Agoran week each year which falls entirely in February
is Read the Ruleset Week. Agorans are encouraged to read the
ruleset during Read the Ruleset Week.
History:
Created by Proposal 6973 (Murphy), 30 March 2011
Amended(1) by Proposal 6995 (omd, harvel), 10 April 2011
----------------------------------------------------------------------
Rule 2429/1 (Power=1)
Bleach
Replacing a non-zero amount of whitespace with a different
non-zero amount of whitespace is generally insignificant, except
for paragraph breaks.
History:
Created by Proposal 7665 (scshunt), 3 June 2014
Amended(1) by Proposal 7709 (Murphy), 3 November 2014
----------------------------------------------------------------------
Rule 2430/1 (Power=3)
Cleanup Time
The Rulekeepor CAN, without objection, cause this rule to amend
any specified rule by:
a) Changing the capitalization of a word, except to or from
all caps.
b) Changing visual formatting (such as the layout and
bulleting of a list).
c) Correcting formatting inconsistencies (such as doubled or
skipped items in a list).
Such a change SHALL NOT be made if it would plausibly affect the
interpretation of a rule.
History:
Created by Proposal 7665 (scshunt), 3 June 2014
Amended(1) by Proposal 7686 (omd), 7 August 2014
----------------------------------------------------------------------
======================================================================
Players
----------------------------------------------------------------------
Rule 869/38 (Power=3)
How to Join and Leave Agora
Any organism that is generally capable of freely originating and
communicating independent thoughts and ideas is a person. Rules
to the contrary notwithstanding, no other entities are persons.
Citizenship is a person switch with values Unregistered
(default) and Registered, tracked by the Registrar. Changes to
citizenship are secured. A registered person is a Player.
A person CAN (unless explicitly forbidden or prevented by the
rules) register by publishing a message that indicates
reasonably clearly and reasonably unambiguously that e intends
to become a player at that time. A person, by registering,
agrees to abide by the Rules. The Rules CANNOT otherwise bind a
person to abide by any agreement without that person's willful
consent.
A player CAN deregister (cease being a player) by announcement.
If e does so, e CANNOT register by announcement for 30 days.
If a player has not sent a message to a public forum in the last
month, then any player CAN deregister em without objection. In
the first week of every month, the Registrar SHALL use this
method to attempt to deregister every player that has not sent a
message to a public forum in the preceding month.
The Rules CANNOT compel non-players to act, nor compel players
to unduly harass non-players. A non-person CANNOT be a player,
rules to the contrary notwithstanding.
[CFJ 1275 (called 19 February 2001): An entity is a Player if the
Rules cannot distinguish that entity from a Player.]
[CFJ 1263 (called 5 February 2001): Any message expressing a clear
desire or intent to register as a Player counts as a request for
registration, whether or not it is explicitly phrased in the manner
stipulated by the rules.]
History:
Created by Proposal 498 (Alexx), Sep. 30 1993
Amended by Proposal 869, ca. Apr. 7 1994
Amended by Rule 750, ca. Apr. 7 1994
Amended(1) by Proposal 1313, Nov. 12 1994
Amended(2) by Proposal 1437, Feb. 21 1995
Amended(3) by Proposal 2040, Dec. 11 1995