head	1.1587;
access;
symbols
	vr20070321:1.227
	vr20070212:1.225
	vr20070122:1.221
	vr20061201:1.208
	vr20060920:1.207
	vr20060827d:1.207
	vr20060827c:1.205
	vr20060827b:1.204
	vr20060827a:1.202
	vr20060530:1.201
	vr20060522:1.200
	vr20060318:1.198
	vr20060101a:1.197
	vr20051204:1.195
	vr20051109:1.195
	vr20051027:1.194
	vr20051002:1.193
	vr20050806:1.191
	vr20050730:1.190
	vr20050722:1.187
	vr20050717:1.186
	vr20050710:1.184
	vr20050620b:1.180
	vr20050620a:1.179
	vr20050620:1.177
	vr20050619:1.177
	vr20050615:1.176
	vr20050606:1.175
	vr20050603:1.174
	vr20050525:1.173
	vr20050515a:1.172
	vr20050515:1.171
	vr20050505b:1.167
	vr20050505a:1.167
	vr20050505:1.167
	vr20050425:1.165
	vr20050418a:1.164
	vr20050418:1.162
	vr20050413:1.161
	vr20050409a:1.160
	vr20050409:1.159
	vr20050329:1.156
	vr20050322:1.155
	vr20050312:1.152
	vr20050306:1.151
	vr20050219:1.150
	vr20050123:1.149
	vr20050109:1.148
	vr20041219:1.147
	vr20041204:1.146
	vr20041120:1.145
	vr20041001:1.144
	vr20040921:1.143
	vr20040910:1.142
	vr20040808:1.141
	vr20040711:1.140
	vr20040704a:1.139
	vr20040704:1.137
	vr20040615:1.136
	vr20040531:1.134
	vr20040514:1.133
	vr20040502:1.132
	vr20040427:1.131
	vr20040411:1.130
	vr20040406:1.129
	vr20040322a:1.127
	vr20040322:1.126
	vr20040227:1.125
	vr20040124:1.121
	vr20040113:1.120
	vr20031216:1.119
	vr20031123:1.118
	vr20031116:1.117
	vr20031108:1.116
	vr20031026:1.115
	vr20031017:1.114
	vr20031002:1.113
	vr20030916:1.110
	vr20030908:1.109
	vr20030828:1.108
	vr20030730:1.107
	vr20030718:1.104
	vr20030710:1.103
	vr20030620:1.102
	vr20030605:1.99
	vr20030513:1.98
	vr20030506:1.97
	vr20030428:1.94
	vr20030424:1.93
	vr20030423:1.92
	vr20030326:1.91
	vr20030317:1.87
	vr20030222a:1.84
	vr20030303:1.83
	vr20030222:1.80
	vr20030203:1.79
	vr20030128:1.78
	vr20030116:1.77
	vr20030102:1.76
	vr20021216:1.75
	vr20021125:1.74
	vr20021106:1.71
	vr20021116:1.72
	vr20021030:1.70
	vr20021023:1.69
	vr20021017:1.68
	vr20020925:1.67
	vr20021005:1.66
	vr20020917:1.65
	vr20020911:1.64
	vr20020906:1.63
	vr20020829:1.62
	vr20020823:1.61
	vr20020816:1.60
	vr20020807:1.59
	vr20020720:1.58
	vr20020711:1.57
	vr20020708:1.56
	vr20020630a:1.55
	vr20020630:1.54
	vr20020609a:1.54
	vr20020609:1.53
	vr20020531:1.52
	vr20020528:1.52
	vr20020517:1.51
	vr20020510:1.50
	vr20020505:1.49
	vr20020416:1.48
	vr20020403:1.46
	vr20020328:1.45
	vr20020322:1.44
	vr20020317:1.43
	vr20020304:1.42
	vr20020221:1.40
	vr20020219:1.40
	vr20020129:1.39
	vr20020208:1.39
	vr20011129:1.34
	vr20011122:1.34
	vr20011017:1.33
	vr20011010:1.33
	vr20011003:1.32
	vr20010929:1.32
	vr20010910:1.31
	vr20010903:1.29
	vr20010828:1.28
	vr20010808:1.25
	vr20010726:1.24
	vr20010718:1.23
	vr20010709:1.18
	vr20010707:1.16
	vr20010626:1.13
	vr20010621:1.12
	an20010616:1.12
	vr20010611b:1.10
	vr20010611:1.9
	vr20010605:1.8;
locks; strict;
comment	@# @;


1.1587
date	2012.02.05.22.45.05;	author comex;	state Exp;
branches;
next	1.1586;

1.1586
date	2012.02.05.22.43.49;	author comex;	state Exp;
branches;
next	1.1585;

1.1585
date	2012.02.03.03.11.30;	author comex;	state Exp;
branches;
next	1.1584;

1.1584
date	2012.02.03.03.10.57;	author comex;	state Exp;
branches;
next	1.1583;

1.1583
date	2012.02.03.03.10.32;	author comex;	state Exp;
branches;
next	1.1582;

1.1582
date	2012.02.03.03.09.08;	author comex;	state Exp;
branches;
next	1.1581;

1.1581
date	2012.01.29.19.09.54;	author comex;	state Exp;
branches;
next	1.1580;

1.1580
date	2012.01.29.19.09.09;	author comex;	state Exp;
branches;
next	1.1579;

1.1579
date	2012.01.29.18.56.22;	author comex;	state Exp;
branches;
next	1.1578;

1.1578
date	2011.12.08.00.54.31;	author comex;	state Exp;
branches;
next	1.1577;

1.1577
date	2011.12.08.00.53.47;	author comex;	state Exp;
branches;
next	1.1576;

1.1576
date	2011.12.08.00.52.56;	author comex;	state Exp;
branches;
next	1.1575;

1.1575
date	2011.12.08.00.50.48;	author comex;	state Exp;
branches;
next	1.1574;

1.1574
date	2011.11.07.04.45.20;	author comex;	state Exp;
branches;
next	1.1573;

1.1573
date	2011.11.07.04.42.43;	author comex;	state Exp;
branches;
next	1.1572;

1.1572
date	2011.11.07.04.40.43;	author comex;	state Exp;
branches;
next	1.1571;

1.1571
date	2011.11.07.04.37.56;	author comex;	state Exp;
branches;
next	1.1570;

1.1570
date	2011.11.07.04.36.24;	author comex;	state Exp;
branches;
next	1.1569;

1.1569
date	2011.11.07.04.14.12;	author comex;	state Exp;
branches;
next	1.1568;

1.1568
date	2011.10.17.00.23.24;	author comex;	state Exp;
branches;
next	1.1567;

1.1567
date	2011.08.21.01.47.10;	author comex;	state Exp;
branches;
next	1.1566;

1.1566
date	2011.08.21.01.37.23;	author comex;	state Exp;
branches;
next	1.1565;

1.1565
date	2011.08.21.01.36.47;	author comex;	state Exp;
branches;
next	1.1564;

1.1564
date	2011.08.21.01.33.40;	author comex;	state Exp;
branches;
next	1.1563;

1.1563
date	2011.07.31.21.20.50;	author comex;	state Exp;
branches;
next	1.1562;

1.1562
date	2011.07.31.21.20.23;	author comex;	state Exp;
branches;
next	1.1561;

1.1561
date	2011.07.31.21.19.29;	author comex;	state Exp;
branches;
next	1.1560;

1.1560
date	2011.07.31.21.18.26;	author comex;	state Exp;
branches;
next	1.1559;

1.1559
date	2011.07.31.21.17.21;	author comex;	state Exp;
branches;
next	1.1558;

1.1558
date	2011.07.31.21.16.05;	author comex;	state Exp;
branches;
next	1.1557;

1.1557
date	2011.07.31.21.12.58;	author comex;	state Exp;
branches;
next	1.1556;

1.1556
date	2011.07.31.21.12.09;	author comex;	state Exp;
branches;
next	1.1555;

1.1555
date	2011.07.31.21.11.10;	author comex;	state Exp;
branches;
next	1.1554;

1.1554
date	2011.07.31.21.09.15;	author comex;	state Exp;
branches;
next	1.1553;

1.1553
date	2011.07.06.01.38.27;	author comex;	state Exp;
branches;
next	1.1552;

1.1552
date	2011.07.05.03.55.05;	author comex;	state Exp;
branches;
next	1.1551;

1.1551
date	2011.07.05.03.54.20;	author comex;	state Exp;
branches;
next	1.1550;

1.1550
date	2011.06.26.00.20.36;	author comex;	state Exp;
branches;
next	1.1549;

1.1549
date	2011.06.26.00.16.50;	author comex;	state Exp;
branches;
next	1.1548;

1.1548
date	2011.06.26.00.14.53;	author comex;	state Exp;
branches;
next	1.1547;

1.1547
date	2011.06.26.00.13.51;	author comex;	state Exp;
branches;
next	1.1546;

1.1546
date	2011.06.26.00.11.34;	author comex;	state Exp;
branches;
next	1.1545;

1.1545
date	2011.06.26.00.08.28;	author comex;	state Exp;
branches;
next	1.1544;

1.1544
date	2011.06.26.00.07.57;	author comex;	state Exp;
branches;
next	1.1543;

1.1543
date	2011.06.26.00.06.50;	author comex;	state Exp;
branches;
next	1.1542;

1.1542
date	2011.06.26.00.06.16;	author comex;	state Exp;
branches;
next	1.1541;

1.1541
date	2011.06.26.00.05.24;	author comex;	state Exp;
branches;
next	1.1540;

1.1540
date	2011.06.26.00.04.13;	author comex;	state Exp;
branches;
next	1.1539;

1.1539
date	2011.06.26.00.03.38;	author comex;	state Exp;
branches;
next	1.1538;

1.1538
date	2011.06.26.00.01.08;	author comex;	state Exp;
branches;
next	1.1537;

1.1537
date	2011.06.26.00.00.22;	author comex;	state Exp;
branches;
next	1.1536;

1.1536
date	2011.06.25.23.59.47;	author comex;	state Exp;
branches;
next	1.1535;

1.1535
date	2011.06.15.17.43.39;	author comex;	state Exp;
branches;
next	1.1534;

1.1534
date	2011.05.31.22.49.06;	author comex;	state Exp;
branches;
next	1.1533;

1.1533
date	2011.05.31.22.48.19;	author comex;	state Exp;
branches;
next	1.1532;

1.1532
date	2011.05.18.03.14.49;	author comex;	state Exp;
branches;
next	1.1531;

1.1531
date	2011.05.18.03.13.47;	author comex;	state Exp;
branches;
next	1.1530;

1.1530
date	2011.05.18.02.54.05;	author comex;	state Exp;
branches;
next	1.1529;

1.1529
date	2011.05.18.02.51.57;	author comex;	state Exp;
branches;
next	1.1528;

1.1528
date	2011.05.18.02.46.53;	author comex;	state Exp;
branches;
next	1.1527;

1.1527
date	2011.05.18.02.42.11;	author comex;	state Exp;
branches;
next	1.1526;

1.1526
date	2011.05.18.02.41.33;	author comex;	state Exp;
branches;
next	1.1525;

1.1525
date	2011.05.18.02.40.49;	author comex;	state Exp;
branches;
next	1.1524;

1.1524
date	2011.05.18.02.39.38;	author comex;	state Exp;
branches;
next	1.1523;

1.1523
date	2011.05.18.02.37.16;	author comex;	state Exp;
branches;
next	1.1522;

1.1522
date	2011.05.18.02.30.39;	author comex;	state Exp;
branches;
next	1.1521;

1.1521
date	2011.05.18.02.28.47;	author comex;	state Exp;
branches;
next	1.1520;

1.1520
date	2011.05.18.02.26.01;	author comex;	state Exp;
branches;
next	1.1519;

1.1519
date	2011.05.18.02.24.19;	author comex;	state Exp;
branches;
next	1.1518;

1.1518
date	2011.05.18.02.23.50;	author comex;	state Exp;
branches;
next	1.1517;

1.1517
date	2011.05.18.02.21.05;	author comex;	state Exp;
branches;
next	1.1516;

1.1516
date	2011.05.18.02.18.13;	author comex;	state Exp;
branches;
next	1.1515;

1.1515
date	2011.05.18.02.14.23;	author comex;	state Exp;
branches;
next	1.1514;

1.1514
date	2011.05.18.02.13.39;	author comex;	state Exp;
branches;
next	1.1513;

1.1513
date	2011.05.18.02.12.52;	author comex;	state Exp;
branches;
next	1.1512;

1.1512
date	2011.05.18.01.55.46;	author comex;	state Exp;
branches;
next	1.1511;

1.1511
date	2011.04.24.00.06.04;	author comex;	state Exp;
branches;
next	1.1510;

1.1510
date	2011.04.24.00.03.32;	author comex;	state Exp;
branches;
next	1.1509;

1.1509
date	2011.04.23.23.56.36;	author comex;	state Exp;
branches;
next	1.1508;

1.1508
date	2011.04.23.23.52.13;	author comex;	state Exp;
branches;
next	1.1507;

1.1507
date	2011.04.23.23.51.25;	author comex;	state Exp;
branches;
next	1.1506;

1.1506
date	2011.04.23.23.30.09;	author comex;	state Exp;
branches;
next	1.1505;

1.1505
date	2011.04.23.23.28.29;	author comex;	state Exp;
branches;
next	1.1504;

1.1504
date	2011.04.23.23.27.29;	author comex;	state Exp;
branches;
next	1.1503;

1.1503
date	2011.04.23.23.22.16;	author comex;	state Exp;
branches;
next	1.1502;

1.1502
date	2011.04.23.23.21.33;	author comex;	state Exp;
branches;
next	1.1501;

1.1501
date	2011.04.23.23.20.01;	author comex;	state Exp;
branches;
next	1.1500;

1.1500
date	2011.04.12.20.40.11;	author comex;	state Exp;
branches;
next	1.1499;

1.1499
date	2011.04.12.20.39.27;	author comex;	state Exp;
branches;
next	1.1498;

1.1498
date	2011.04.12.20.37.34;	author comex;	state Exp;
branches;
next	1.1497;

1.1497
date	2011.04.12.20.35.39;	author comex;	state Exp;
branches;
next	1.1496;

1.1496
date	2011.04.12.20.30.11;	author comex;	state Exp;
branches;
next	1.1495;

1.1495
date	2011.04.12.20.29.42;	author comex;	state Exp;
branches;
next	1.1494;

1.1494
date	2011.04.12.20.27.26;	author comex;	state Exp;
branches;
next	1.1493;

1.1493
date	2011.04.12.20.26.41;	author comex;	state Exp;
branches;
next	1.1492;

1.1492
date	2011.03.30.18.21.40;	author comex;	state Exp;
branches;
next	1.1491;

1.1491
date	2011.03.30.18.19.04;	author comex;	state Exp;
branches;
next	1.1490;

1.1490
date	2011.03.30.18.17.30;	author comex;	state Exp;
branches;
next	1.1489;

1.1489
date	2011.03.30.18.16.21;	author comex;	state Exp;
branches;
next	1.1488;

1.1488
date	2011.03.30.18.15.03;	author comex;	state Exp;
branches;
next	1.1487;

1.1487
date	2011.03.30.18.13.34;	author comex;	state Exp;
branches;
next	1.1486;

1.1486
date	2011.03.30.18.12.16;	author comex;	state Exp;
branches;
next	1.1485;

1.1485
date	2011.03.30.18.11.04;	author comex;	state Exp;
branches;
next	1.1484;

1.1484
date	2011.03.30.18.07.19;	author comex;	state Exp;
branches;
next	1.1483;

1.1483
date	2011.03.30.18.06.09;	author comex;	state Exp;
branches;
next	1.1482;

1.1482
date	2011.03.30.18.03.02;	author comex;	state Exp;
branches;
next	1.1481;

1.1481
date	2011.03.30.18.02.33;	author comex;	state Exp;
branches;
next	1.1480;

1.1480
date	2011.03.03.21.49.48;	author comex;	state Exp;
branches;
next	1.1479;

1.1479
date	2011.01.16.23.55.37;	author comex;	state Exp;
branches;
next	1.1478;

1.1478
date	2011.01.16.23.54.52;	author comex;	state Exp;
branches;
next	1.1477;

1.1477
date	2011.01.16.23.53.31;	author comex;	state Exp;
branches;
next	1.1476;

1.1476
date	2011.01.14.04.33.54;	author comex;	state Exp;
branches;
next	1.1475;

1.1475
date	2011.01.14.04.29.47;	author comex;	state Exp;
branches;
next	1.1474;

1.1474
date	2011.01.14.04.28.43;	author comex;	state Exp;
branches;
next	1.1473;

1.1473
date	2011.01.14.04.28.07;	author comex;	state Exp;
branches;
next	1.1472;

1.1472
date	2011.01.14.04.27.24;	author comex;	state Exp;
branches;
next	1.1471;

1.1471
date	2011.01.14.04.26.38;	author comex;	state Exp;
branches;
next	1.1470;

1.1470
date	2011.01.14.04.24.33;	author comex;	state Exp;
branches;
next	1.1469;

1.1469
date	2011.01.14.04.24.02;	author comex;	state Exp;
branches;
next	1.1468;

1.1468
date	2011.01.14.04.21.23;	author comex;	state Exp;
branches;
next	1.1467;

1.1467
date	2011.01.14.04.19.04;	author comex;	state Exp;
branches;
next	1.1466;

1.1466
date	2011.01.14.04.18.04;	author comex;	state Exp;
branches;
next	1.1465;

1.1465
date	2011.01.14.04.16.58;	author comex;	state Exp;
branches;
next	1.1464;

1.1464
date	2011.01.14.04.15.18;	author comex;	state Exp;
branches;
next	1.1463;

1.1463
date	2011.01.14.04.13.39;	author comex;	state Exp;
branches;
next	1.1462;

1.1462
date	2011.01.14.04.12.45;	author comex;	state Exp;
branches;
next	1.1461;

1.1461
date	2011.01.03.00.48.16;	author comex;	state Exp;
branches;
next	1.1460;

1.1460
date	2010.12.22.01.50.05;	author comex;	state Exp;
branches;
next	1.1459;

1.1459
date	2010.12.22.01.49.43;	author comex;	state Exp;
branches;
next	1.1458;

1.1458
date	2010.12.22.01.47.51;	author comex;	state Exp;
branches;
next	1.1457;

1.1457
date	2010.12.20.19.43.28;	author comex;	state Exp;
branches;
next	1.1456;

1.1456
date	2010.12.20.19.35.20;	author comex;	state Exp;
branches;
next	1.1455;

1.1455
date	2010.12.14.20.01.05;	author comex;	state Exp;
branches;
next	1.1454;

1.1454
date	2010.12.06.06.04.55;	author comex;	state Exp;
branches;
next	1.1453;

1.1453
date	2010.12.06.06.00.09;	author comex;	state Exp;
branches;
next	1.1452;

1.1452
date	2010.12.06.05.58.19;	author comex;	state Exp;
branches;
next	1.1451;

1.1451
date	2010.12.06.05.56.47;	author comex;	state Exp;
branches;
next	1.1450;

1.1450
date	2010.12.06.05.54.04;	author comex;	state Exp;
branches;
next	1.1449;

1.1449
date	2010.12.06.05.50.25;	author comex;	state Exp;
branches;
next	1.1448;

1.1448
date	2010.11.30.23.55.06;	author comex;	state Exp;
branches;
next	1.1447;

1.1447
date	2010.11.30.23.52.18;	author comex;	state Exp;
branches;
next	1.1446;

1.1446
date	2010.11.23.00.17.50;	author comex;	state Exp;
branches;
next	1.1445;

1.1445
date	2010.11.23.00.16.52;	author comex;	state Exp;
branches;
next	1.1444;

1.1444
date	2010.11.23.00.13.24;	author comex;	state Exp;
branches;
next	1.1443;

1.1443
date	2010.11.23.00.08.17;	author comex;	state Exp;
branches;
next	1.1442;

1.1442
date	2010.11.22.23.55.17;	author comex;	state Exp;
branches;
next	1.1441;

1.1441
date	2010.11.22.23.53.04;	author comex;	state Exp;
branches;
next	1.1440;

1.1440
date	2010.11.22.23.49.13;	author comex;	state Exp;
branches;
next	1.1439;

1.1439
date	2010.11.22.23.48.29;	author comex;	state Exp;
branches;
next	1.1438;

1.1438
date	2010.11.22.23.45.13;	author comex;	state Exp;
branches;
next	1.1437;

1.1437
date	2010.11.22.23.44.06;	author comex;	state Exp;
branches;
next	1.1436;

1.1436
date	2010.11.11.21.54.36;	author comex;	state Exp;
branches;
next	1.1435;

1.1435
date	2010.11.11.21.49.59;	author comex;	state Exp;
branches;
next	1.1434;

1.1434
date	2010.11.11.21.46.05;	author comex;	state Exp;
branches;
next	1.1433;

1.1433
date	2010.11.11.21.32.45;	author comex;	state Exp;
branches;
next	1.1432;

1.1432
date	2010.11.11.21.27.44;	author comex;	state Exp;
branches;
next	1.1431;

1.1431
date	2010.11.11.21.26.01;	author comex;	state Exp;
branches;
next	1.1430;

1.1430
date	2010.11.11.21.25.15;	author comex;	state Exp;
branches;
next	1.1429;

1.1429
date	2010.11.11.21.22.35;	author comex;	state Exp;
branches;
next	1.1428;

1.1428
date	2010.10.18.22.09.52;	author comex;	state Exp;
branches;
next	1.1427;

1.1427
date	2010.10.08.20.28.48;	author comex;	state Exp;
branches;
next	1.1426;

1.1426
date	2010.10.07.19.50.07;	author comex;	state Exp;
branches;
next	1.1425;

1.1425
date	2010.10.07.19.37.32;	author comex;	state Exp;
branches;
next	1.1424;

1.1424
date	2010.09.27.00.42.42;	author comex;	state Exp;
branches;
next	1.1423;

1.1423
date	2010.09.21.20.36.56;	author comex;	state Exp;
branches;
next	1.1422;

1.1422
date	2010.09.10.21.39.17;	author comex;	state Exp;
branches;
next	1.1421;

1.1421
date	2010.09.10.21.37.45;	author comex;	state Exp;
branches;
next	1.1420;

1.1420
date	2010.09.10.21.29.37;	author comex;	state Exp;
branches;
next	1.1419;

1.1419
date	2010.09.10.21.29.03;	author comex;	state Exp;
branches;
next	1.1418;

1.1418
date	2010.09.10.21.27.33;	author comex;	state Exp;
branches;
next	1.1417;

1.1417
date	2010.09.10.21.18.59;	author comex;	state Exp;
branches;
next	1.1416;

1.1416
date	2010.09.10.21.18.07;	author comex;	state Exp;
branches;
next	1.1415;

1.1415
date	2010.09.05.04.03.14;	author comex;	state Exp;
branches;
next	1.1414;

1.1414
date	2010.09.04.22.53.11;	author comex;	state Exp;
branches;
next	1.1413;

1.1413
date	2010.09.04.22.50.30;	author comex;	state Exp;
branches;
next	1.1412;

1.1412
date	2010.09.04.22.46.07;	author comex;	state Exp;
branches;
next	1.1411;

1.1411
date	2010.09.04.22.44.19;	author comex;	state Exp;
branches;
next	1.1410;

1.1410
date	2010.09.04.22.41.38;	author comex;	state Exp;
branches;
next	1.1409;

1.1409
date	2010.09.04.19.02.54;	author comex;	state Exp;
branches;
next	1.1408;

1.1408
date	2010.09.04.19.00.01;	author comex;	state Exp;
branches;
next	1.1407;

1.1407
date	2010.09.04.18.56.56;	author comex;	state Exp;
branches;
next	1.1406;

1.1406
date	2010.09.03.15.35.05;	author comex;	state Exp;
branches;
next	1.1405;

1.1405
date	2010.08.30.03.28.07;	author comex;	state Exp;
branches;
next	1.1404;

1.1404
date	2010.08.30.03.25.29;	author comex;	state Exp;
branches;
next	1.1403;

1.1403
date	2010.08.30.03.24.50;	author comex;	state Exp;
branches;
next	1.1402;

1.1402
date	2010.08.30.03.23.50;	author comex;	state Exp;
branches;
next	1.1401;

1.1401
date	2010.08.30.03.20.52;	author comex;	state Exp;
branches;
next	1.1400;

1.1400
date	2010.08.30.03.20.22;	author comex;	state Exp;
branches;
next	1.1399;

1.1399
date	2010.08.30.03.18.36;	author comex;	state Exp;
branches;
next	1.1398;

1.1398
date	2010.08.30.03.10.52;	author comex;	state Exp;
branches;
next	1.1397;

1.1397
date	2010.08.30.03.09.25;	author comex;	state Exp;
branches;
next	1.1396;

1.1396
date	2010.08.30.03.08.07;	author comex;	state Exp;
branches;
next	1.1395;

1.1395
date	2010.08.30.03.02.59;	author comex;	state Exp;
branches;
next	1.1394;

1.1394
date	2010.08.23.02.26.54;	author comex;	state Exp;
branches;
next	1.1393;

1.1393
date	2010.08.23.02.26.20;	author comex;	state Exp;
branches;
next	1.1392;

1.1392
date	2010.08.23.02.25.17;	author comex;	state Exp;
branches;
next	1.1391;

1.1391
date	2010.08.23.02.23.50;	author comex;	state Exp;
branches;
next	1.1390;

1.1390
date	2010.08.22.04.41.01;	author comex;	state Exp;
branches;
next	1.1389;

1.1389
date	2010.08.21.03.52.08;	author comex;	state Exp;
branches;
next	1.1388;

1.1388
date	2010.08.20.00.10.53;	author comex;	state Exp;
branches;
next	1.1387;

1.1387
date	2010.08.12.18.03.05;	author comex;	state Exp;
branches;
next	1.1386;

1.1386
date	2010.08.12.18.00.55;	author comex;	state Exp;
branches;
next	1.1385;

1.1385
date	2010.08.12.18.00.04;	author comex;	state Exp;
branches;
next	1.1384;

1.1384
date	2010.08.12.17.59.28;	author comex;	state Exp;
branches;
next	1.1383;

1.1383
date	2010.08.12.17.53.38;	author comex;	state Exp;
branches;
next	1.1382;

1.1382
date	2010.08.12.17.49.19;	author comex;	state Exp;
branches;
next	1.1381;

1.1381
date	2010.08.12.17.48.41;	author comex;	state Exp;
branches;
next	1.1380;

1.1380
date	2010.08.12.17.48.03;	author comex;	state Exp;
branches;
next	1.1379;

1.1379
date	2010.08.12.17.45.07;	author comex;	state Exp;
branches;
next	1.1378;

1.1378
date	2010.08.12.17.40.54;	author comex;	state Exp;
branches;
next	1.1377;

1.1377
date	2010.08.12.17.40.06;	author comex;	state Exp;
branches;
next	1.1376;

1.1376
date	2010.08.12.17.38.58;	author comex;	state Exp;
branches;
next	1.1375;

1.1375
date	2010.08.04.17.51.14;	author comex;	state Exp;
branches;
next	1.1374;

1.1374
date	2010.08.04.17.46.56;	author comex;	state Exp;
branches;
next	1.1373;

1.1373
date	2010.08.02.20.55.48;	author comex;	state Exp;
branches;
next	1.1372;

1.1372
date	2010.08.02.20.52.20;	author comex;	state Exp;
branches;
next	1.1371;

1.1371
date	2010.08.02.20.49.08;	author comex;	state Exp;
branches;
next	1.1370;

1.1370
date	2010.08.02.20.45.30;	author comex;	state Exp;
branches;
next	1.1369;

1.1369
date	2010.08.02.20.44.55;	author comex;	state Exp;
branches;
next	1.1368;

1.1368
date	2010.08.02.20.43.01;	author comex;	state Exp;
branches;
next	1.1367;

1.1367
date	2010.08.02.03.54.52;	author comex;	state Exp;
branches;
next	1.1366;

1.1366
date	2010.07.29.02.27.57;	author comex;	state Exp;
branches;
next	1.1365;

1.1365
date	2010.07.27.02.11.31;	author comex;	state Exp;
branches;
next	1.1364;

1.1364
date	2010.07.23.17.45.42;	author comex;	state Exp;
branches;
next	1.1363;

1.1363
date	2010.07.23.17.45.03;	author comex;	state Exp;
branches;
next	1.1362;

1.1362
date	2010.07.02.00.49.18;	author comex;	state Exp;
branches;
next	1.1361;

1.1361
date	2010.07.02.00.30.21;	author comex;	state Exp;
branches;
next	1.1360;

1.1360
date	2010.07.02.00.29.11;	author comex;	state Exp;
branches;
next	1.1359;

1.1359
date	2010.07.02.00.25.30;	author comex;	state Exp;
branches;
next	1.1358;

1.1358
date	2010.06.15.17.50.55;	author comex;	state Exp;
branches;
next	1.1357;

1.1357
date	2010.06.15.17.03.15;	author comex;	state Exp;
branches;
next	1.1356;

1.1356
date	2010.06.15.17.00.39;	author comex;	state Exp;
branches;
next	1.1355;

1.1355
date	2010.06.15.16.59.52;	author comex;	state Exp;
branches;
next	1.1354;

1.1354
date	2010.06.15.16.58.33;	author comex;	state Exp;
branches;
next	1.1353;

1.1353
date	2010.06.10.17.07.52;	author comex;	state Exp;
branches;
next	1.1352;

1.1352
date	2010.06.10.17.06.45;	author comex;	state Exp;
branches;
next	1.1351;

1.1351
date	2010.05.30.03.46.43;	author comex;	state Exp;
branches;
next	1.1350;

1.1350
date	2010.05.26.15.41.53;	author comex;	state Exp;
branches;
next	1.1349;

1.1349
date	2010.05.22.15.51.34;	author comex;	state Exp;
branches;
next	1.1348;

1.1348
date	2010.05.22.15.50.29;	author comex;	state Exp;
branches;
next	1.1347;

1.1347
date	2010.05.22.15.46.39;	author comex;	state Exp;
branches;
next	1.1346;

1.1346
date	2010.05.22.15.45.36;	author comex;	state Exp;
branches;
next	1.1345;

1.1345
date	2010.05.18.13.42.03;	author comex;	state Exp;
branches;
next	1.1344;

1.1344
date	2010.05.08.20.47.41;	author comex;	state Exp;
branches;
next	1.1343;

1.1343
date	2010.05.05.01.22.46;	author comex;	state Exp;
branches;
next	1.1342;

1.1342
date	2010.05.04.21.58.14;	author comex;	state Exp;
branches;
next	1.1341;

1.1341
date	2010.05.04.21.55.00;	author comex;	state Exp;
branches;
next	1.1340;

1.1340
date	2010.05.04.21.39.08;	author comex;	state Exp;
branches;
next	1.1339;

1.1339
date	2010.05.04.21.32.30;	author comex;	state Exp;
branches;
next	1.1338;

1.1338
date	2010.05.04.21.26.45;	author comex;	state Exp;
branches;
next	1.1337;

1.1337
date	2010.04.26.22.09.10;	author comex;	state Exp;
branches;
next	1.1336;

1.1336
date	2010.04.25.19.36.14;	author comex;	state Exp;
branches;
next	1.1335;

1.1335
date	2010.04.25.19.35.39;	author comex;	state Exp;
branches;
next	1.1334;

1.1334
date	2010.04.25.19.32.59;	author comex;	state Exp;
branches;
next	1.1333;

1.1333
date	2010.04.25.19.28.40;	author comex;	state Exp;
branches;
next	1.1332;

1.1332
date	2010.04.25.19.26.49;	author comex;	state Exp;
branches;
next	1.1331;

1.1331
date	2010.04.25.19.25.28;	author comex;	state Exp;
branches;
next	1.1330;

1.1330
date	2010.04.25.19.19.42;	author comex;	state Exp;
branches;
next	1.1329;

1.1329
date	2010.04.25.16.42.19;	author comex;	state Exp;
branches;
next	1.1328;

1.1328
date	2010.04.19.00.46.35;	author comex;	state Exp;
branches;
next	1.1327;

1.1327
date	2010.04.05.19.59.17;	author comex;	state Exp;
branches;
next	1.1326;

1.1326
date	2010.04.05.19.54.27;	author comex;	state Exp;
branches;
next	1.1325;

1.1325
date	2010.04.05.19.52.21;	author comex;	state Exp;
branches;
next	1.1324;

1.1324
date	2010.04.05.19.50.03;	author comex;	state Exp;
branches;
next	1.1323;

1.1323
date	2010.04.05.19.49.12;	author comex;	state Exp;
branches;
next	1.1322;

1.1322
date	2010.03.17.21.36.52;	author comex;	state Exp;
branches;
next	1.1321;

1.1321
date	2010.03.17.21.36.07;	author comex;	state Exp;
branches;
next	1.1320;

1.1320
date	2010.03.14.03.07.49;	author comex;	state Exp;
branches;
next	1.1319;

1.1319
date	2010.03.12.01.23.52;	author comex;	state Exp;
branches;
next	1.1318;

1.1318
date	2010.03.12.01.22.52;	author comex;	state Exp;
branches;
next	1.1317;

1.1317
date	2010.03.12.01.09.24;	author comex;	state Exp;
branches;
next	1.1316;

1.1316
date	2010.03.12.00.52.13;	author comex;	state Exp;
branches;
next	1.1315;

1.1315
date	2010.03.12.00.51.13;	author comex;	state Exp;
branches;
next	1.1314;

1.1314
date	2010.03.11.18.35.52;	author comex;	state Exp;
branches;
next	1.1313;

1.1313
date	2010.03.11.18.24.20;	author comex;	state Exp;
branches;
next	1.1312;

1.1312
date	2010.03.11.18.23.08;	author comex;	state Exp;
branches;
next	1.1311;

1.1311
date	2010.03.11.18.20.08;	author comex;	state Exp;
branches;
next	1.1310;

1.1310
date	2010.03.11.18.18.27;	author comex;	state Exp;
branches;
next	1.1309;

1.1309
date	2010.03.11.18.16.59;	author comex;	state Exp;
branches;
next	1.1308;

1.1308
date	2010.03.11.18.16.03;	author comex;	state Exp;
branches;
next	1.1307;

1.1307
date	2010.03.11.18.12.28;	author comex;	state Exp;
branches;
next	1.1306;

1.1306
date	2010.03.11.18.08.45;	author comex;	state Exp;
branches;
next	1.1305;

1.1305
date	2010.03.11.18.02.06;	author comex;	state Exp;
branches;
next	1.1304;

1.1304
date	2010.03.11.17.59.40;	author comex;	state Exp;
branches;
next	1.1303;

1.1303
date	2010.03.06.19.11.46;	author comex;	state Exp;
branches;
next	1.1302;

1.1302
date	2010.03.06.19.07.51;	author comex;	state Exp;
branches;
next	1.1301;

1.1301
date	2010.02.28.17.34.12;	author comex;	state Exp;
branches;
next	1.1300;

1.1300
date	2010.02.22.17.35.15;	author comex;	state Exp;
branches;
next	1.1299;

1.1299
date	2010.02.22.01.39.16;	author comex;	state Exp;
branches;
next	1.1298;

1.1298
date	2010.02.21.18.30.53;	author comex;	state Exp;
branches;
next	1.1297;

1.1297
date	2010.02.21.17.58.39;	author comex;	state Exp;
branches;
next	1.1296;

1.1296
date	2010.02.21.17.57.34;	author comex;	state Exp;
branches;
next	1.1295;

1.1295
date	2010.02.21.17.55.27;	author comex;	state Exp;
branches;
next	1.1294;

1.1294
date	2010.02.21.17.50.12;	author comex;	state Exp;
branches;
next	1.1293;

1.1293
date	2010.02.21.17.36.45;	author comex;	state Exp;
branches;
next	1.1292;

1.1292
date	2010.02.21.17.33.22;	author comex;	state Exp;
branches;
next	1.1291;

1.1291
date	2010.02.21.17.32.37;	author comex;	state Exp;
branches;
next	1.1290;

1.1290
date	2010.02.21.17.30.25;	author comex;	state Exp;
branches;
next	1.1289;

1.1289
date	2010.02.21.17.29.18;	author comex;	state Exp;
branches;
next	1.1288;

1.1288
date	2010.02.21.17.28.22;	author comex;	state Exp;
branches;
next	1.1287;

1.1287
date	2010.02.07.22.11.48;	author comex;	state Exp;
branches;
next	1.1286;

1.1286
date	2010.02.07.19.32.29;	author comex;	state Exp;
branches;
next	1.1285;

1.1285
date	2010.02.07.19.31.37;	author comex;	state Exp;
branches;
next	1.1284;

1.1284
date	2010.02.07.19.30.46;	author comex;	state Exp;
branches;
next	1.1283;

1.1283
date	2010.02.07.19.29.27;	author comex;	state Exp;
branches;
next	1.1282;

1.1282
date	2010.01.30.20.21.11;	author comex;	state Exp;
branches;
next	1.1281;

1.1281
date	2010.01.30.19.55.28;	author comex;	state Exp;
branches;
next	1.1280;

1.1280
date	2010.01.20.20.12.48;	author comex;	state Exp;
branches;
next	1.1279;

1.1279
date	2009.12.19.03.33.38;	author comex;	state Exp;
branches;
next	1.1278;

1.1278
date	2009.12.19.03.32.00;	author comex;	state Exp;
branches;
next	1.1277;

1.1277
date	2009.12.19.03.31.06;	author comex;	state Exp;
branches;
next	1.1276;

1.1276
date	2009.12.19.03.29.12;	author comex;	state Exp;
branches;
next	1.1275;

1.1275
date	2009.12.19.03.28.26;	author comex;	state Exp;
branches;
next	1.1274;

1.1274
date	2009.12.19.03.27.13;	author comex;	state Exp;
branches;
next	1.1273;

1.1273
date	2009.12.19.03.24.12;	author comex;	state Exp;
branches;
next	1.1272;

1.1272
date	2009.12.08.02.02.29;	author comex;	state Exp;
branches;
next	1.1271;

1.1271
date	2009.12.06.22.11.43;	author comex;	state Exp;
branches;
next	1.1270;

1.1270
date	2009.12.06.22.08.17;	author comex;	state Exp;
branches;
next	1.1269;

1.1269
date	2009.11.29.17.30.11;	author comex;	state Exp;
branches;
next	1.1268;

1.1268
date	2009.11.29.17.27.40;	author comex;	state Exp;
branches;
next	1.1267;

1.1267
date	2009.11.29.17.26.41;	author comex;	state Exp;
branches;
next	1.1266;

1.1266
date	2009.11.29.17.25.37;	author comex;	state Exp;
branches;
next	1.1265;

1.1265
date	2009.11.29.17.24.37;	author comex;	state Exp;
branches;
next	1.1264;

1.1264
date	2009.11.29.17.21.35;	author comex;	state Exp;
branches;
next	1.1263;

1.1263
date	2009.11.29.16.57.28;	author comex;	state Exp;
branches;
next	1.1262;

1.1262
date	2009.11.29.16.55.15;	author comex;	state Exp;
branches;
next	1.1261;

1.1261
date	2009.11.19.23.06.03;	author comex;	state Exp;
branches;
next	1.1260;

1.1260
date	2009.11.19.23.05.09;	author comex;	state Exp;
branches;
next	1.1259;

1.1259
date	2009.11.15.00.39.35;	author comex;	state Exp;
branches;
next	1.1258;

1.1258
date	2009.11.15.00.37.30;	author comex;	state Exp;
branches;
next	1.1257;

1.1257
date	2009.11.15.00.35.54;	author comex;	state Exp;
branches;
next	1.1256;

1.1256
date	2009.11.15.00.29.36;	author comex;	state Exp;
branches;
next	1.1255;

1.1255
date	2009.11.15.00.28.30;	author comex;	state Exp;
branches;
next	1.1254;

1.1254
date	2009.11.07.21.41.42;	author comex;	state Exp;
branches;
next	1.1253;

1.1253
date	2009.11.07.21.39.46;	author comex;	state Exp;
branches;
next	1.1252;

1.1252
date	2009.11.05.23.26.31;	author comex;	state Exp;
branches;
next	1.1251;

1.1251
date	2009.11.05.23.25.42;	author comex;	state Exp;
branches;
next	1.1250;

1.1250
date	2009.11.05.21.35.21;	author comex;	state Exp;
branches;
next	1.1249;

1.1249
date	2009.11.05.21.34.40;	author comex;	state Exp;
branches;
next	1.1248;

1.1248
date	2009.11.05.21.33.57;	author comex;	state Exp;
branches;
next	1.1247;

1.1247
date	2009.11.05.21.30.32;	author comex;	state Exp;
branches;
next	1.1246;

1.1246
date	2009.11.05.21.29.02;	author comex;	state Exp;
branches;
next	1.1245;

1.1245
date	2009.11.05.21.27.54;	author comex;	state Exp;
branches;
next	1.1244;

1.1244
date	2009.10.26.23.04.06;	author comex;	state Exp;
branches;
next	1.1243;

1.1243
date	2009.10.24.01.35.24;	author comex;	state Exp;
branches;
next	1.1242;

1.1242
date	2009.10.24.01.35.05;	author comex;	state Exp;
branches;
next	1.1241;

1.1241
date	2009.10.24.01.29.19;	author comex;	state Exp;
branches;
next	1.1240;

1.1240
date	2009.10.24.01.27.00;	author comex;	state Exp;
branches;
next	1.1239;

1.1239
date	2009.10.24.01.26.17;	author comex;	state Exp;
branches;
next	1.1238;

1.1238
date	2009.10.24.01.25.19;	author comex;	state Exp;
branches;
next	1.1237;

1.1237
date	2009.10.24.01.24.01;	author comex;	state Exp;
branches;
next	1.1236;

1.1236
date	2009.10.24.01.22.53;	author comex;	state Exp;
branches;
next	1.1235;

1.1235
date	2009.10.24.01.21.49;	author comex;	state Exp;
branches;
next	1.1234;

1.1234
date	2009.10.24.01.20.44;	author comex;	state Exp;
branches;
next	1.1233;

1.1233
date	2009.10.22.23.26.22;	author comex;	state Exp;
branches;
next	1.1232;

1.1232
date	2009.10.22.23.25.41;	author comex;	state Exp;
branches;
next	1.1231;

1.1231
date	2009.10.22.23.25.01;	author comex;	state Exp;
branches;
next	1.1230;

1.1230
date	2009.10.22.23.24.14;	author comex;	state Exp;
branches;
next	1.1229;

1.1229
date	2009.10.22.23.23.22;	author comex;	state Exp;
branches;
next	1.1228;

1.1228
date	2009.10.04.04.10.26;	author comex;	state Exp;
branches;
next	1.1227;

1.1227
date	2009.10.04.04.09.37;	author comex;	state Exp;
branches;
next	1.1226;

1.1226
date	2009.10.04.04.07.39;	author comex;	state Exp;
branches;
next	1.1225;

1.1225
date	2009.10.04.04.06.22;	author comex;	state Exp;
branches;
next	1.1224;

1.1224
date	2009.10.04.04.05.28;	author comex;	state Exp;
branches;
next	1.1223;

1.1223
date	2009.10.03.22.58.26;	author comex;	state Exp;
branches;
next	1.1222;

1.1222
date	2009.09.29.19.47.53;	author comex;	state Exp;
branches;
next	1.1221;

1.1221
date	2009.09.29.19.46.55;	author comex;	state Exp;
branches;
next	1.1220;

1.1220
date	2009.09.29.19.46.19;	author comex;	state Exp;
branches;
next	1.1219;

1.1219
date	2009.09.23.22.26.30;	author comex;	state Exp;
branches;
next	1.1218;

1.1218
date	2009.09.19.02.08.16;	author comex;	state Exp;
branches;
next	1.1217;

1.1217
date	2009.09.19.02.07.18;	author comex;	state Exp;
branches;
next	1.1216;

1.1216
date	2009.09.19.01.58.20;	author comex;	state Exp;
branches;
next	1.1215;

1.1215
date	2009.09.19.01.57.16;	author comex;	state Exp;
branches;
next	1.1214;

1.1214
date	2009.09.19.01.56.16;	author comex;	state Exp;
branches;
next	1.1213;

1.1213
date	2009.09.19.01.55.38;	author comex;	state Exp;
branches;
next	1.1212;

1.1212
date	2009.09.19.01.53.41;	author comex;	state Exp;
branches;
next	1.1211;

1.1211
date	2009.09.19.01.49.19;	author comex;	state Exp;
branches;
next	1.1210;

1.1210
date	2009.09.19.01.47.19;	author comex;	state Exp;
branches;
next	1.1209;

1.1209
date	2009.09.19.01.44.55;	author comex;	state Exp;
branches;
next	1.1208;

1.1208
date	2009.09.15.15.22.26;	author comex;	state Exp;
branches;
next	1.1207;

1.1207
date	2009.09.15.14.59.22;	author comex;	state Exp;
branches;
next	1.1206;

1.1206
date	2009.09.15.14.58.43;	author comex;	state Exp;
branches;
next	1.1205;

1.1205
date	2009.09.15.14.54.14;	author comex;	state Exp;
branches;
next	1.1204;

1.1204
date	2009.09.15.14.52.58;	author comex;	state Exp;
branches;
next	1.1203;

1.1203
date	2009.09.15.14.52.17;	author comex;	state Exp;
branches;
next	1.1202;

1.1202
date	2009.09.15.14.50.38;	author comex;	state Exp;
branches;
next	1.1201;

1.1201
date	2009.09.03.22.31.02;	author comex;	state Exp;
branches;
next	1.1200;

1.1200
date	2009.09.01.16.42.59;	author comex;	state Exp;
branches;
next	1.1199;

1.1199
date	2009.09.01.16.41.19;	author comex;	state Exp;
branches;
next	1.1198;

1.1198
date	2009.09.01.16.39.23;	author comex;	state Exp;
branches;
next	1.1197;

1.1197
date	2009.08.27.21.32.31;	author comex;	state Exp;
branches;
next	1.1196;

1.1196
date	2009.08.27.21.31.20;	author comex;	state Exp;
branches;
next	1.1195;

1.1195
date	2009.08.27.21.28.43;	author comex;	state Exp;
branches;
next	1.1194;

1.1194
date	2009.08.27.21.15.00;	author comex;	state Exp;
branches;
next	1.1193;

1.1193
date	2009.08.27.21.14.11;	author comex;	state Exp;
branches;
next	1.1192;

1.1192
date	2009.08.27.21.12.14;	author comex;	state Exp;
branches;
next	1.1191;

1.1191
date	2009.08.27.21.08.48;	author comex;	state Exp;
branches;
next	1.1190;

1.1190
date	2009.08.19.02.23.19;	author comex;	state Exp;
branches;
next	1.1189;

1.1189
date	2009.08.19.02.21.26;	author comex;	state Exp;
branches;
next	1.1188;

1.1188
date	2009.08.19.02.20.55;	author comex;	state Exp;
branches;
next	1.1187;

1.1187
date	2009.08.19.02.15.56;	author comex;	state Exp;
branches;
next	1.1186;

1.1186
date	2009.08.19.02.15.07;	author comex;	state Exp;
branches;
next	1.1185;

1.1185
date	2009.08.19.02.11.01;	author comex;	state Exp;
branches;
next	1.1184;

1.1184
date	2009.08.19.02.10.35;	author comex;	state Exp;
branches;
next	1.1183;

1.1183
date	2009.08.19.02.08.45;	author comex;	state Exp;
branches;
next	1.1182;

1.1182
date	2009.08.19.02.04.28;	author comex;	state Exp;
branches;
next	1.1181;

1.1181
date	2009.08.17.00.37.40;	author comex;	state Exp;
branches;
next	1.1180;

1.1180
date	2009.08.17.00.36.34;	author comex;	state Exp;
branches;
next	1.1179;

1.1179
date	2009.08.17.00.29.30;	author comex;	state Exp;
branches;
next	1.1178;

1.1178
date	2009.08.17.00.24.34;	author comex;	state Exp;
branches;
next	1.1177;

1.1177
date	2009.08.09.18.28.35;	author comex;	state Exp;
branches;
next	1.1176;

1.1176
date	2009.08.08.17.05.48;	author comex;	state Exp;
branches;
next	1.1175;

1.1175
date	2009.08.08.17.05.00;	author comex;	state Exp;
branches;
next	1.1174;

1.1174
date	2009.08.08.03.22.27;	author comex;	state Exp;
branches;
next	1.1173;

1.1173
date	2009.08.08.03.14.15;	author comex;	state Exp;
branches;
next	1.1172;

1.1172
date	2009.08.08.03.10.21;	author comex;	state Exp;
branches;
next	1.1171;

1.1171
date	2009.08.08.03.06.18;	author comex;	state Exp;
branches;
next	1.1170;

1.1170
date	2009.08.06.22.20.12;	author comex;	state Exp;
branches;
next	1.1169;

1.1169
date	2009.08.06.03.06.15;	author comex;	state Exp;
branches;
next	1.1168;

1.1168
date	2009.07.31.23.32.32;	author comex;	state Exp;
branches;
next	1.1167;

1.1167
date	2009.07.31.23.30.56;	author comex;	state Exp;
branches;
next	1.1166;

1.1166
date	2009.07.31.23.24.46;	author comex;	state Exp;
branches;
next	1.1165;

1.1165
date	2009.07.31.22.53.10;	author comex;	state Exp;
branches;
next	1.1164;

1.1164
date	2009.07.31.22.50.58;	author comex;	state Exp;
branches;
next	1.1163;

1.1163
date	2009.07.31.22.49.17;	author comex;	state Exp;
branches;
next	1.1162;

1.1162
date	2009.07.30.20.26.26;	author comex;	state Exp;
branches;
next	1.1161;

1.1161
date	2009.07.30.20.23.31;	author comex;	state Exp;
branches;
next	1.1160;

1.1160
date	2009.07.30.20.13.41;	author comex;	state Exp;
branches;
next	1.1159;

1.1159
date	2009.07.30.20.12.00;	author comex;	state Exp;
branches;
next	1.1158;

1.1158
date	2009.07.30.20.09.57;	author comex;	state Exp;
branches;
next	1.1157;

1.1157
date	2009.07.30.20.08.14;	author comex;	state Exp;
branches;
next	1.1156;

1.1156
date	2009.07.30.20.05.47;	author comex;	state Exp;
branches;
next	1.1155;

1.1155
date	2009.07.30.20.03.29;	author comex;	state Exp;
branches;
next	1.1154;

1.1154
date	2009.07.10.17.43.48;	author comex;	state Exp;
branches;
next	1.1153;

1.1153
date	2009.07.10.17.27.11;	author comex;	state Exp;
branches;
next	1.1152;

1.1152
date	2009.07.10.15.33.30;	author comex;	state Exp;
branches;
next	1.1151;

1.1151
date	2009.07.10.15.32.47;	author comex;	state Exp;
branches;
next	1.1150;

1.1150
date	2009.07.10.15.30.44;	author comex;	state Exp;
branches;
next	1.1149;

1.1149
date	2009.07.10.15.29.27;	author comex;	state Exp;
branches;
next	1.1148;

1.1148
date	2009.07.10.15.29.00;	author comex;	state Exp;
branches;
next	1.1147;

1.1147
date	2009.07.10.15.28.20;	author comex;	state Exp;
branches;
next	1.1146;

1.1146
date	2009.07.10.15.24.22;	author comex;	state Exp;
branches;
next	1.1145;

1.1145
date	2009.07.07.23.28.49;	author comex;	state Exp;
branches;
next	1.1144;

1.1144
date	2009.07.07.01.21.25;	author comex;	state Exp;
branches;
next	1.1143;

1.1143
date	2009.07.06.20.47.01;	author comex;	state Exp;
branches;
next	1.1142;

1.1142
date	2009.07.06.20.46.19;	author comex;	state Exp;
branches;
next	1.1141;

1.1141
date	2009.07.06.16.49.25;	author comex;	state Exp;
branches;
next	1.1140;

1.1140
date	2009.07.06.16.47.52;	author comex;	state Exp;
branches;
next	1.1139;

1.1139
date	2009.07.06.15.40.13;	author comex;	state Exp;
branches;
next	1.1138;

1.1138
date	2009.07.06.15.26.36;	author comex;	state Exp;
branches;
next	1.1137;

1.1137
date	2009.07.06.15.25.56;	author comex;	state Exp;
branches;
next	1.1136;

1.1136
date	2009.07.06.15.24.32;	author comex;	state Exp;
branches;
next	1.1135;

1.1135
date	2009.06.26.19.59.37;	author comex;	state Exp;
branches;
next	1.1134;

1.1134
date	2009.06.26.19.54.44;	author comex;	state Exp;
branches;
next	1.1133;

1.1133
date	2009.06.26.19.52.19;	author comex;	state Exp;
branches;
next	1.1132;

1.1132
date	2009.06.26.19.51.25;	author comex;	state Exp;
branches;
next	1.1131;

1.1131
date	2009.06.26.19.48.56;	author comex;	state Exp;
branches;
next	1.1130;

1.1130
date	2009.06.26.19.45.22;	author comex;	state Exp;
branches;
next	1.1129;

1.1129
date	2009.06.26.19.44.02;	author comex;	state Exp;
branches;
next	1.1128;

1.1128
date	2009.06.26.19.42.40;	author comex;	state Exp;
branches;
next	1.1127;

1.1127
date	2009.06.26.19.38.58;	author comex;	state Exp;
branches;
next	1.1126;

1.1126
date	2009.06.26.19.36.53;	author comex;	state Exp;
branches;
next	1.1125;

1.1125
date	2009.06.26.19.31.31;	author comex;	state Exp;
branches;
next	1.1124;

1.1124
date	2009.06.17.22.15.08;	author comex;	state Exp;
branches;
next	1.1123;

1.1123
date	2009.06.17.22.13.17;	author comex;	state Exp;
branches;
next	1.1122;

1.1122
date	2009.06.17.22.12.17;	author comex;	state Exp;
branches;
next	1.1121;

1.1121
date	2009.06.17.22.10.56;	author comex;	state Exp;
branches;
next	1.1120;

1.1120
date	2009.06.11.18.47.02;	author comex;	state Exp;
branches;
next	1.1119;

1.1119
date	2009.06.11.18.45.04;	author comex;	state Exp;
branches;
next	1.1118;

1.1118
date	2009.06.11.18.43.59;	author comex;	state Exp;
branches;
next	1.1117;

1.1117
date	2009.06.01.19.28.59;	author comex;	state Exp;
branches;
next	1.1116;

1.1116
date	2009.05.30.01.45.16;	author comex;	state Exp;
branches;
next	1.1115;

1.1115
date	2009.05.30.01.42.57;	author comex;	state Exp;
branches;
next	1.1114;

1.1114
date	2009.05.30.01.36.55;	author comex;	state Exp;
branches;
next	1.1113;

1.1113
date	2009.05.30.01.33.15;	author comex;	state Exp;
branches;
next	1.1112;

1.1112
date	2009.05.30.01.31.57;	author comex;	state Exp;
branches;
next	1.1111;

1.1111
date	2009.05.30.01.30.24;	author comex;	state Exp;
branches;
next	1.1110;

1.1110
date	2009.05.30.01.29.08;	author comex;	state Exp;
branches;
next	1.1109;

1.1109
date	2009.05.30.01.27.35;	author comex;	state Exp;
branches;
next	1.1108;

1.1108
date	2009.05.30.01.25.18;	author comex;	state Exp;
branches;
next	1.1107;

1.1107
date	2009.05.26.19.19.25;	author comex;	state Exp;
branches;
next	1.1106;

1.1106
date	2009.05.26.17.41.01;	author comex;	state Exp;
branches;
next	1.1105;

1.1105
date	2009.05.26.17.38.31;	author comex;	state Exp;
branches;
next	1.1104;

1.1104
date	2009.05.26.17.35.44;	author comex;	state Exp;
branches;
next	1.1103;

1.1103
date	2009.05.26.17.34.51;	author comex;	state Exp;
branches;
next	1.1102;

1.1102
date	2009.05.26.17.34.06;	author comex;	state Exp;
branches;
next	1.1101;

1.1101
date	2009.05.26.17.32.14;	author comex;	state Exp;
branches;
next	1.1100;

1.1100
date	2009.05.26.17.30.53;	author comex;	state Exp;
branches;
next	1.1099;

1.1099
date	2009.05.26.17.28.39;	author comex;	state Exp;
branches;
next	1.1098;

1.1098
date	2009.05.26.17.25.32;	author comex;	state Exp;
branches;
next	1.1097;

1.1097
date	2009.05.26.17.22.03;	author comex;	state Exp;
branches;
next	1.1096;

1.1096
date	2009.05.25.20.44.18;	author comex;	state Exp;
branches;
next	1.1095;

1.1095
date	2009.05.20.16.55.35;	author comex;	state Exp;
branches;
next	1.1094;

1.1094
date	2009.05.20.16.53.12;	author comex;	state Exp;
branches;
next	1.1093;

1.1093
date	2009.05.20.16.50.06;	author comex;	state Exp;
branches;
next	1.1092;

1.1092
date	2009.05.20.16.49.10;	author comex;	state Exp;
branches;
next	1.1091;

1.1091
date	2009.05.20.16.48.56;	author comex;	state Exp;
branches;
next	1.1090;

1.1090
date	2009.05.20.16.45.46;	author comex;	state Exp;
branches;
next	1.1089;

1.1089
date	2009.05.20.13.43.01;	author comex;	state Exp;
branches;
next	1.1088;

1.1088
date	2009.05.20.13.37.21;	author comex;	state Exp;
branches;
next	1.1087;

1.1087
date	2009.05.20.13.36.15;	author comex;	state Exp;
branches;
next	1.1086;

1.1086
date	2009.05.20.13.34.45;	author comex;	state Exp;
branches;
next	1.1085;

1.1085
date	2009.05.20.13.34.29;	author comex;	state Exp;
branches;
next	1.1084;

1.1084
date	2009.05.20.13.32.02;	author comex;	state Exp;
branches;
next	1.1083;

1.1083
date	2009.05.20.13.28.55;	author comex;	state Exp;
branches;
next	1.1082;

1.1082
date	2009.05.14.19.28.10;	author comex;	state Exp;
branches;
next	1.1081;

1.1081
date	2009.05.13.15.12.32;	author comex;	state Exp;
branches;
next	1.1080;

1.1080
date	2009.05.11.23.57.43;	author comex;	state Exp;
branches;
next	1.1079;

1.1079
date	2009.05.11.19.46.07;	author comex;	state Exp;
branches;
next	1.1078;

1.1078
date	2009.05.11.19.45.20;	author comex;	state Exp;
branches;
next	1.1077;

1.1077
date	2009.05.11.19.43.19;	author comex;	state Exp;
branches;
next	1.1076;

1.1076
date	2009.05.11.19.42.38;	author comex;	state Exp;
branches;
next	1.1075;

1.1075
date	2009.05.11.19.10.50;	author comex;	state Exp;
branches;
next	1.1074;

1.1074
date	2009.05.11.19.09.27;	author comex;	state Exp;
branches;
next	1.1073;

1.1073
date	2009.05.11.19.08.47;	author comex;	state Exp;
branches;
next	1.1072;

1.1072
date	2009.05.11.01.07.44;	author comex;	state Exp;
branches;
next	1.1071;

1.1071
date	2009.05.11.01.06.48;	author comex;	state Exp;
branches;
next	1.1070;

1.1070
date	2009.05.11.01.05.27;	author comex;	state Exp;
branches;
next	1.1069;

1.1069
date	2009.05.11.01.03.45;	author comex;	state Exp;
branches;
next	1.1068;

1.1068
date	2009.05.11.01.02.18;	author comex;	state Exp;
branches;
next	1.1067;

1.1067
date	2009.05.11.01.00.20;	author comex;	state Exp;
branches;
next	1.1066;

1.1066
date	2009.05.11.00.59.00;	author comex;	state Exp;
branches;
next	1.1065;

1.1065
date	2009.05.11.00.57.16;	author comex;	state Exp;
branches;
next	1.1064;

1.1064
date	2009.05.11.00.55.41;	author comex;	state Exp;
branches;
next	1.1063;

1.1063
date	2009.05.11.00.54.17;	author comex;	state Exp;
branches;
next	1.1062;

1.1062
date	2009.05.04.19.32.10;	author comex;	state Exp;
branches;
next	1.1061;

1.1061
date	2009.05.04.19.29.23;	author comex;	state Exp;
branches;
next	1.1060;

1.1060
date	2009.05.04.19.26.39;	author comex;	state Exp;
branches;
next	1.1059;

1.1059
date	2009.05.04.19.24.27;	author comex;	state Exp;
branches;
next	1.1058;

1.1058
date	2009.05.04.19.23.24;	author comex;	state Exp;
branches;
next	1.1057;

1.1057
date	2009.05.04.19.21.34;	author comex;	state Exp;
branches;
next	1.1056;

1.1056
date	2009.04.29.22.13.43;	author comex;	state Exp;
branches;
next	1.1055;

1.1055
date	2009.04.29.22.00.16;	author comex;	state Exp;
branches;
next	1.1054;

1.1054
date	2009.04.27.15.25.58;	author comex;	state Exp;
branches;
next	1.1053;

1.1053
date	2009.04.27.15.24.12;	author comex;	state Exp;
branches;
next	1.1052;

1.1052
date	2009.04.27.15.22.48;	author comex;	state Exp;
branches;
next	1.1051;

1.1051
date	2009.04.27.15.19.58;	author comex;	state Exp;
branches;
next	1.1050;

1.1050
date	2009.04.27.15.18.50;	author comex;	state Exp;
branches;
next	1.1049;

1.1049
date	2009.04.27.15.16.59;	author comex;	state Exp;
branches;
next	1.1048;

1.1048
date	2009.04.27.15.13.42;	author comex;	state Exp;
branches;
next	1.1047;

1.1047
date	2009.04.27.15.11.43;	author comex;	state Exp;
branches;
next	1.1046;

1.1046
date	2009.04.27.15.10.06;	author comex;	state Exp;
branches;
next	1.1045;

1.1045
date	2009.04.27.15.08.27;	author comex;	state Exp;
branches;
next	1.1044;

1.1044
date	2009.04.27.15.02.37;	author comex;	state Exp;
branches;
next	1.1043;

1.1043
date	2009.04.27.14.55.29;	author comex;	state Exp;
branches;
next	1.1042;

1.1042
date	2009.04.25.23.37.10;	author comex;	state Exp;
branches;
next	1.1041;

1.1041
date	2009.04.20.13.24.44;	author comex;	state Exp;
branches;
next	1.1040;

1.1040
date	2009.04.17.14.00.00;	author comex;	state Exp;
branches;
next	1.1039;

1.1039
date	2009.04.17.11.59.31;	author comex;	state Exp;
branches;
next	1.1038;

1.1038
date	2009.04.17.11.57.30;	author comex;	state Exp;
branches;
next	1.1037;

1.1037
date	2009.04.14.14.27.31;	author comex;	state Exp;
branches;
next	1.1036;

1.1036
date	2009.04.14.14.13.21;	author comex;	state Exp;
branches;
next	1.1035;

1.1035
date	2009.04.13.19.42.27;	author comex;	state Exp;
branches;
next	1.1034;

1.1034
date	2009.04.13.19.40.09;	author comex;	state Exp;
branches;
next	1.1033;

1.1033
date	2009.04.13.19.38.46;	author comex;	state Exp;
branches;
next	1.1032;

1.1032
date	2009.04.13.19.37.48;	author comex;	state Exp;
branches;
next	1.1031;

1.1031
date	2009.04.13.19.15.34;	author comex;	state Exp;
branches;
next	1.1030;

1.1030
date	2009.04.13.19.11.56;	author comex;	state Exp;
branches;
next	1.1029;

1.1029
date	2009.03.31.22.27.05;	author comex;	state Exp;
branches;
next	1.1028;

1.1028
date	2009.03.31.22.25.27;	author comex;	state Exp;
branches;
next	1.1027;

1.1027
date	2009.03.31.22.23.42;	author comex;	state Exp;
branches;
next	1.1026;

1.1026
date	2009.03.31.22.22.21;	author comex;	state Exp;
branches;
next	1.1025;

1.1025
date	2009.03.31.21.29.48;	author comex;	state Exp;
branches;
next	1.1024;

1.1024
date	2009.03.31.21.28.36;	author comex;	state Exp;
branches;
next	1.1023;

1.1023
date	2009.03.31.21.17.18;	author comex;	state Exp;
branches;
next	1.1022;

1.1022
date	2009.03.31.21.16.09;	author comex;	state Exp;
branches;
next	1.1021;

1.1021
date	2009.03.27.18.19.33;	author comex;	state Exp;
branches;
next	1.1020;

1.1020
date	2009.03.23.20.04.01;	author comex;	state Exp;
branches;
next	1.1019;

1.1019
date	2009.03.23.19.22.48;	author comex;	state Exp;
branches;
next	1.1018;

1.1018
date	2009.03.23.19.14.27;	author comex;	state Exp;
branches;
next	1.1017;

1.1017
date	2009.03.23.19.13.01;	author comex;	state Exp;
branches;
next	1.1016;

1.1016
date	2009.03.23.19.08.55;	author comex;	state Exp;
branches;
next	1.1015;

1.1015
date	2009.03.19.13.19.14;	author comex;	state Exp;
branches;
next	1.1014;

1.1014
date	2009.03.19.13.16.01;	author comex;	state Exp;
branches;
next	1.1013;

1.1013
date	2009.03.16.16.56.31;	author comex;	state Exp;
branches;
next	1.1012;

1.1012
date	2009.03.16.16.48.38;	author comex;	state Exp;
branches;
next	1.1011;

1.1011
date	2009.03.16.16.31.15;	author comex;	state Exp;
branches;
next	1.1010;

1.1010
date	2009.03.16.16.29.30;	author comex;	state Exp;
branches;
next	1.1009;

1.1009
date	2009.03.16.16.27.20;	author comex;	state Exp;
branches;
next	1.1008;

1.1008
date	2009.03.16.16.23.57;	author comex;	state Exp;
branches;
next	1.1007;

1.1007
date	2009.03.16.16.21.51;	author comex;	state Exp;
branches;
next	1.1006;

1.1006
date	2009.03.16.16.17.21;	author comex;	state Exp;
branches;
next	1.1005;

1.1005
date	2009.03.16.16.15.30;	author comex;	state Exp;
branches;
next	1.1004;

1.1004
date	2009.03.16.16.13.09;	author comex;	state Exp;
branches;
next	1.1003;

1.1003
date	2009.03.16.15.40.34;	author comex;	state Exp;
branches;
next	1.1002;

1.1002
date	2009.03.16.15.31.33;	author comex;	state Exp;
branches;
next	1.1001;

1.1001
date	2009.03.12.00.20.31;	author comex;	state Exp;
branches;
next	1.1000;

1.1000
date	2009.03.05.14.28.39;	author comex;	state Exp;
branches;
next	1.999;

1.999
date	2009.03.05.14.26.29;	author comex;	state Exp;
branches;
next	1.998;

1.998
date	2009.03.01.20.45.12;	author comex;	state Exp;
branches;
next	1.997;

1.997
date	2009.03.01.20.43.53;	author comex;	state Exp;
branches;
next	1.996;

1.996
date	2009.03.01.20.43.10;	author comex;	state Exp;
branches;
next	1.995;

1.995
date	2009.03.01.20.41.19;	author comex;	state Exp;
branches;
next	1.994;

1.994
date	2009.03.01.20.39.49;	author comex;	state Exp;
branches;
next	1.993;

1.993
date	2009.03.01.20.36.47;	author comex;	state Exp;
branches;
next	1.992;

1.992
date	2009.02.27.20.07.30;	author comex;	state Exp;
branches;
next	1.991;

1.991
date	2009.02.27.18.05.45;	author comex;	state Exp;
branches;
next	1.990;

1.990
date	2009.02.22.01.09.52;	author comex;	state Exp;
branches;
next	1.989;

1.989
date	2009.02.22.01.07.36;	author comex;	state Exp;
branches;
next	1.988;

1.988
date	2009.02.22.01.05.10;	author comex;	state Exp;
branches;
next	1.987;

1.987
date	2009.02.22.01.04.03;	author comex;	state Exp;
branches;
next	1.986;

1.986
date	2009.02.22.01.03.27;	author comex;	state Exp;
branches;
next	1.985;

1.985
date	2009.02.22.00.58.20;	author comex;	state Exp;
branches;
next	1.984;

1.984
date	2009.02.22.00.57.22;	author comex;	state Exp;
branches;
next	1.983;

1.983
date	2009.02.22.00.56.26;	author comex;	state Exp;
branches;
next	1.982;

1.982
date	2009.02.22.00.53.55;	author comex;	state Exp;
branches;
next	1.981;

1.981
date	2009.02.22.00.52.45;	author comex;	state Exp;
branches;
next	1.980;

1.980
date	2009.02.22.00.51.11;	author comex;	state Exp;
branches;
next	1.979;

1.979
date	2009.02.22.00.41.17;	author comex;	state Exp;
branches;
next	1.978;

1.978
date	2009.02.22.00.38.32;	author comex;	state Exp;
branches;
next	1.977;

1.977
date	2009.02.22.00.28.16;	author comex;	state Exp;
branches;
next	1.976;

1.976
date	2009.02.22.00.23.13;	author comex;	state Exp;
branches;
next	1.975;

1.975
date	2009.02.22.00.20.21;	author comex;	state Exp;
branches;
next	1.974;

1.974
date	2009.02.22.00.19.29;	author comex;	state Exp;
branches;
next	1.973;

1.973
date	2009.02.16.23.56.25;	author comex;	state Exp;
branches;
next	1.972;

1.972
date	2009.02.16.23.49.40;	author comex;	state Exp;
branches;
next	1.971;

1.971
date	2009.02.15.21.43.02;	author comex;	state Exp;
branches;
next	1.970;

1.970
date	2009.02.15.21.35.10;	author comex;	state Exp;
branches;
next	1.969;

1.969
date	2009.02.13.22.05.29;	author comex;	state Exp;
branches;
next	1.968;

1.968
date	2009.02.12.23.39.10;	author comex;	state Exp;
branches;
next	1.967;

1.967
date	2009.02.05.14.37.35;	author comex;	state Exp;
branches;
next	1.966;

1.966
date	2009.02.05.14.14.16;	author comex;	state Exp;
branches;
next	1.965;

1.965
date	2009.02.05.14.11.33;	author comex;	state Exp;
branches;
next	1.964;

1.964
date	2009.02.05.14.05.20;	author comex;	state Exp;
branches;
next	1.963;

1.963
date	2009.02.05.14.02.55;	author comex;	state Exp;
branches;
next	1.962;

1.962
date	2009.01.26.18.57.55;	author comex;	state Exp;
branches;
next	1.961;

1.961
date	2009.01.23.23.06.24;	author comex;	state Exp;
branches;
next	1.960;

1.960
date	2009.01.23.23.05.25;	author comex;	state Exp;
branches;
next	1.959;

1.959
date	2009.01.23.23.01.07;	author comex;	state Exp;
branches;
next	1.958;

1.958
date	2009.01.23.22.59.47;	author comex;	state Exp;
branches;
next	1.957;

1.957
date	2009.01.23.22.45.47;	author comex;	state Exp;
branches;
next	1.956;

1.956
date	2009.01.23.14.17.25;	author comex;	state Exp;
branches;
next	1.955;

1.955
date	2009.01.19.04.40.42;	author comex;	state Exp;
branches;
next	1.954;

1.954
date	2009.01.19.04.39.43;	author comex;	state Exp;
branches;
next	1.953;

1.953
date	2009.01.19.04.38.10;	author comex;	state Exp;
branches;
next	1.952;

1.952
date	2009.01.19.04.36.32;	author comex;	state Exp;
branches;
next	1.951;

1.951
date	2009.01.19.04.34.54;	author comex;	state Exp;
branches;
next	1.950;

1.950
date	2009.01.19.04.33.58;	author comex;	state Exp;
branches;
next	1.949;

1.949
date	2009.01.19.04.32.55;	author comex;	state Exp;
branches;
next	1.948;

1.948
date	2009.01.19.04.31.35;	author comex;	state Exp;
branches;
next	1.947;

1.947
date	2009.01.19.04.30.43;	author comex;	state Exp;
branches;
next	1.946;

1.946
date	2009.01.09.21.37.10;	author comex;	state Exp;
branches;
next	1.945;

1.945
date	2009.01.09.20.58.56;	author comex;	state Exp;
branches;
next	1.944;

1.944
date	2009.01.09.20.56.35;	author comex;	state Exp;
branches;
next	1.943;

1.943
date	2009.01.09.20.52.44;	author comex;	state Exp;
branches;
next	1.942;

1.942
date	2009.01.09.20.50.50;	author comex;	state Exp;
branches;
next	1.941;

1.941
date	2009.01.09.20.48.27;	author comex;	state Exp;
branches;
next	1.940;

1.940
date	2009.01.09.20.45.47;	author comex;	state Exp;
branches;
next	1.939;

1.939
date	2009.01.09.20.44.27;	author comex;	state Exp;
branches;
next	1.938;

1.938
date	2009.01.09.20.42.09;	author comex;	state Exp;
branches;
next	1.937;

1.937
date	2008.12.27.02.38.10;	author comex;	state Exp;
branches;
next	1.936;

1.936
date	2008.12.27.02.31.12;	author comex;	state Exp;
branches;
next	1.935;

1.935
date	2008.12.27.02.24.10;	author comex;	state Exp;
branches;
next	1.934;

1.934
date	2008.12.23.03.06.12;	author comex;	state Exp;
branches;
next	1.933;

1.933
date	2008.12.23.02.54.29;	author comex;	state Exp;
branches;
next	1.932;

1.932
date	2008.12.23.02.51.01;	author comex;	state Exp;
branches;
next	1.931;

1.931
date	2008.12.23.02.48.26;	author comex;	state Exp;
branches;
next	1.930;

1.930
date	2008.12.23.02.34.36;	author comex;	state Exp;
branches;
next	1.929;

1.929
date	2008.12.18.23.54.14;	author comex;	state Exp;
branches;
next	1.928;

1.928
date	2008.12.18.23.51.30;	author comex;	state Exp;
branches;
next	1.927;

1.927
date	2008.12.15.23.05.48;	author comex;	state Exp;
branches;
next	1.926;

1.926
date	2008.12.15.22.49.46;	author comex;	state Exp;
branches;
next	1.925;

1.925
date	2008.12.15.22.46.48;	author comex;	state Exp;
branches;
next	1.924;

1.924
date	2008.12.10.23.59.43;	author comex;	state Exp;
branches;
next	1.923;

1.923
date	2008.12.10.23.57.40;	author comex;	state Exp;
branches;
next	1.922;

1.922
date	2008.12.07.16.54.19;	author comex;	state Exp;
branches;
next	1.921;

1.921
date	2008.12.07.16.50.41;	author comex;	state Exp;
branches;
next	1.920;

1.920
date	2008.12.07.16.47.00;	author comex;	state Exp;
branches;
next	1.919;

1.919
date	2008.12.07.16.44.43;	author comex;	state Exp;
branches;
next	1.918;

1.918
date	2008.12.07.16.39.51;	author comex;	state Exp;
branches;
next	1.917;

1.917
date	2008.12.07.16.35.55;	author comex;	state Exp;
branches;
next	1.916;

1.916
date	2008.12.07.16.31.28;	author comex;	state Exp;
branches;
next	1.915;

1.915
date	2008.12.07.16.30.19;	author comex;	state Exp;
branches;
next	1.914;

1.914
date	2008.12.07.16.29.33;	author comex;	state Exp;
branches;
next	1.913;

1.913
date	2008.12.07.16.26.01;	author comex;	state Exp;
branches;
next	1.912;

1.912
date	2008.12.03.22.15.27;	author comex;	state Exp;
branches;
next	1.911;

1.911
date	2008.12.03.22.12.20;	author comex;	state Exp;
branches;
next	1.910;

1.910
date	2008.12.03.22.11.40;	author comex;	state Exp;
branches;
next	1.909;

1.909
date	2008.12.03.21.58.17;	author comex;	state Exp;
branches;
next	1.908;

1.908
date	2008.12.03.21.57.43;	author comex;	state Exp;
branches;
next	1.907;

1.907
date	2008.11.29.19.02.57;	author comex;	state Exp;
branches;
next	1.906;

1.906
date	2008.11.29.18.58.05;	author comex;	state Exp;
branches;
next	1.905;

1.905
date	2008.11.29.18.56.49;	author comex;	state Exp;
branches;
next	1.904;

1.904
date	2008.11.29.18.54.04;	author comex;	state Exp;
branches;
next	1.903;

1.903
date	2008.11.27.00.38.04;	author comex;	state Exp;
branches;
next	1.902;

1.902
date	2008.11.27.00.35.28;	author comex;	state Exp;
branches;
next	1.901;

1.901
date	2008.11.27.00.31.57;	author comex;	state Exp;
branches;
next	1.900;

1.900
date	2008.11.27.00.16.11;	author comex;	state Exp;
branches;
next	1.899;

1.899
date	2008.11.27.00.15.07;	author comex;	state Exp;
branches;
next	1.898;

1.898
date	2008.11.27.00.13.28;	author comex;	state Exp;
branches;
next	1.897;

1.897
date	2008.11.20.02.46.36;	author comex;	state Exp;
branches;
next	1.896;

1.896
date	2008.11.18.20.33.37;	author comex;	state Exp;
branches;
next	1.895;

1.895
date	2008.11.18.20.29.48;	author comex;	state Exp;
branches;
next	1.894;

1.894
date	2008.11.17.20.42.07;	author comex;	state Exp;
branches;
next	1.893;

1.893
date	2008.11.15.19.43.32;	author comex;	state Exp;
branches;
next	1.892;

1.892
date	2008.11.15.19.41.11;	author comex;	state Exp;
branches;
next	1.891;

1.891
date	2008.11.15.19.34.02;	author comex;	state Exp;
branches;
next	1.890;

1.890
date	2008.11.15.19.33.02;	author comex;	state Exp;
branches;
next	1.889;

1.889
date	2008.11.15.19.29.18;	author comex;	state Exp;
branches;
next	1.888;

1.888
date	2008.11.15.19.28.03;	author comex;	state Exp;
branches;
next	1.887;

1.887
date	2008.11.14.23.04.42;	author comex;	state Exp;
branches;
next	1.886;

1.886
date	2008.11.14.17.26.55;	author comex;	state Exp;
branches;
next	1.885;

1.885
date	2008.11.14.17.24.22;	author comex;	state Exp;
branches;
next	1.884;

1.884
date	2008.11.14.17.22.55;	author comex;	state Exp;
branches;
next	1.883;

1.883
date	2008.11.14.17.21.15;	author comex;	state Exp;
branches;
next	1.882;

1.882
date	2008.11.14.17.19.17;	author comex;	state Exp;
branches;
next	1.881;

1.881
date	2008.11.07.19.02.08;	author comex;	state Exp;
branches;
next	1.880;

1.880
date	2008.11.07.18.48.47;	author comex;	state Exp;
branches;
next	1.879;

1.879
date	2008.11.03.16.17.35;	author comex;	state Exp;
branches;
next	1.878;

1.878
date	2008.11.03.16.13.27;	author comex;	state Exp;
branches;
next	1.877;

1.877
date	2008.11.01.23.35.39;	author comex;	state Exp;
branches;
next	1.876;

1.876
date	2008.11.01.23.33.22;	author comex;	state Exp;
branches;
next	1.875;

1.875
date	2008.11.01.23.32.32;	author comex;	state Exp;
branches;
next	1.874;

1.874
date	2008.11.01.23.29.07;	author comex;	state Exp;
branches;
next	1.873;

1.873
date	2008.11.01.22.51.53;	author comex;	state Exp;
branches;
next	1.872;

1.872
date	2008.11.01.22.48.07;	author comex;	state Exp;
branches;
next	1.871;

1.871
date	2008.11.01.22.45.52;	author comex;	state Exp;
branches;
next	1.870;

1.870
date	2008.10.30.22.36.07;	author comex;	state Exp;
branches;
next	1.869;

1.869
date	2008.10.29.17.07.35;	author comex;	state Exp;
branches;
next	1.868;

1.868
date	2008.10.29.17.00.36;	author comex;	state Exp;
branches;
next	1.867;

1.867
date	2008.10.29.16.00.07;	author comex;	state Exp;
branches;
next	1.866;

1.866
date	2008.10.29.15.59.21;	author comex;	state Exp;
branches;
next	1.865;

1.865
date	2008.10.28.22.54.24;	author comex;	state Exp;
branches;
next	1.864;

1.864
date	2008.10.28.22.50.48;	author comex;	state Exp;
branches;
next	1.863;

1.863
date	2008.10.28.22.49.47;	author comex;	state Exp;
branches;
next	1.862;

1.862
date	2008.10.22.21.25.13;	author comex;	state Exp;
branches;
next	1.861;

1.861
date	2008.10.22.21.23.18;	author comex;	state Exp;
branches;
next	1.860;

1.860
date	2008.10.22.21.22.08;	author comex;	state Exp;
branches;
next	1.859;

1.859
date	2008.10.22.21.16.50;	author comex;	state Exp;
branches;
next	1.858;

1.858
date	2008.10.22.21.12.13;	author comex;	state Exp;
branches;
next	1.857;

1.857
date	2008.10.22.21.03.55;	author comex;	state Exp;
branches;
next	1.856;

1.856
date	2008.10.22.21.01.17;	author comex;	state Exp;
branches;
next	1.855;

1.855
date	2008.10.22.20.59.03;	author comex;	state Exp;
branches;
next	1.854;

1.854
date	2008.10.22.20.57.22;	author comex;	state Exp;
branches;
next	1.853;

1.853
date	2008.10.17.14.32.06;	author comex;	state Exp;
branches;
next	1.852;

1.852
date	2008.10.17.14.25.23;	author comex;	state Exp;
branches;
next	1.851;

1.851
date	2008.10.17.14.20.18;	author comex;	state Exp;
branches;
next	1.850;

1.850
date	2008.10.17.14.18.21;	author comex;	state Exp;
branches;
next	1.849;

1.849
date	2008.10.17.14.11.42;	author comex;	state Exp;
branches;
next	1.848;

1.848
date	2008.10.17.14.10.21;	author comex;	state Exp;
branches;
next	1.847;

1.847
date	2008.10.17.14.07.48;	author comex;	state Exp;
branches;
next	1.846;

1.846
date	2008.10.17.14.06.35;	author comex;	state Exp;
branches;
next	1.845;

1.845
date	2008.10.16.17.14.29;	author comex;	state Exp;
branches;
next	1.844;

1.844
date	2008.10.16.17.12.37;	author comex;	state Exp;
branches;
next	1.843;

1.843
date	2008.10.16.17.08.18;	author comex;	state Exp;
branches;
next	1.842;

1.842
date	2008.10.16.17.06.01;	author comex;	state Exp;
branches;
next	1.841;

1.841
date	2008.10.16.17.03.52;	author comex;	state Exp;
branches;
next	1.840;

1.840
date	2008.10.16.17.01.57;	author comex;	state Exp;
branches;
next	1.839;

1.839
date	2008.10.09.18.40.35;	author comex;	state Exp;
branches;
next	1.838;

1.838
date	2008.10.09.18.39.35;	author comex;	state Exp;
branches;
next	1.837;

1.837
date	2008.10.09.18.30.30;	author comex;	state Exp;
branches;
next	1.836;

1.836
date	2008.10.08.21.53.01;	author comex;	state Exp;
branches;
next	1.835;

1.835
date	2008.10.08.21.45.32;	author comex;	state Exp;
branches;
next	1.834;

1.834
date	2008.10.08.21.39.05;	author comex;	state Exp;
branches;
next	1.833;

1.833
date	2008.10.08.19.21.10;	author comex;	state Exp;
branches;
next	1.832;

1.832
date	2008.10.08.19.17.40;	author comex;	state Exp;
branches;
next	1.831;

1.831
date	2008.10.08.19.15.35;	author comex;	state Exp;
branches;
next	1.830;

1.830
date	2008.10.08.19.12.53;	author comex;	state Exp;
branches;
next	1.829;

1.829
date	2008.10.08.19.09.49;	author comex;	state Exp;
branches;
next	1.828;

1.828
date	2008.10.08.19.08.25;	author comex;	state Exp;
branches;
next	1.827;

1.827
date	2008.10.08.18.48.03;	author comex;	state Exp;
branches;
next	1.826;

1.826
date	2008.10.08.15.43.38;	author comex;	state Exp;
branches;
next	1.825;

1.825
date	2008.10.08.15.36.11;	author comex;	state Exp;
branches;
next	1.824;

1.824
date	2008.10.08.15.32.16;	author comex;	state Exp;
branches;
next	1.823;

1.823
date	2008.10.08.15.26.37;	author comex;	state Exp;
branches;
next	1.822;

1.822
date	2008.10.08.15.23.26;	author comex;	state Exp;
branches;
next	1.821;

1.821
date	2008.10.08.15.19.02;	author comex;	state Exp;
branches;
next	1.820;

1.820
date	2008.10.03.19.13.04;	author comex;	state Exp;
branches;
next	1.819;

1.819
date	2008.10.02.23.32.07;	author xemocne;	state Exp;
branches;
next	1.818;

1.818
date	2008.10.01.21.34.42;	author xemocne;	state Exp;
branches;
next	1.817;

1.817
date	2008.10.01.21.34.18;	author xemocne;	state Exp;
branches;
next	1.816;

1.816
date	2008.10.01.21.22.31;	author comex;	state Exp;
branches;
next	1.815;

1.815
date	2008.09.20.19.09.54;	author comex;	state Exp;
branches;
next	1.814;

1.814
date	2008.09.20.19.08.32;	author comex;	state Exp;
branches;
next	1.813;

1.813
date	2008.09.16.21.33.31;	author comex;	state Exp;
branches;
next	1.812;

1.812
date	2008.09.15.19.55.53;	author comex;	state Exp;
branches;
next	1.811;

1.811
date	2008.09.09.17.10.07;	author comex;	state Exp;
branches;
next	1.810;

1.810
date	2008.09.03.19.39.38;	author comex;	state Exp;
branches;
next	1.809;

1.809
date	2008.09.03.19.38.53;	author comex;	state Exp;
branches;
next	1.808;

1.808
date	2008.09.03.19.38.05;	author comex;	state Exp;
branches;
next	1.807;

1.807
date	2008.09.03.19.37.06;	author comex;	state Exp;
branches;
next	1.806;

1.806
date	2008.09.03.19.36.22;	author comex;	state Exp;
branches;
next	1.805;

1.805
date	2008.09.01.20.13.15;	author comex;	state Exp;
branches;
next	1.804;

1.804
date	2008.08.29.01.42.48;	author comex;	state Exp;
branches;
next	1.803;

1.803
date	2008.08.13.22.00.03;	author comex;	state Exp;
branches;
next	1.802;

1.802
date	2008.08.13.03.59.06;	author comex;	state Exp;
branches;
next	1.801;

1.801
date	2008.07.06.18.28.07;	author zefram;	state Exp;
branches;
next	1.800;
commitid	RomO6ig4kHzZZL9t;

1.800
date	2008.07.06.18.26.54;	author zefram;	state Exp;
branches;
next	1.799;
commitid	yVodeO1cTZgzZL9t;

1.799
date	2008.07.02.20.55.45;	author zefram;	state Exp;
branches;
next	1.798;
commitid	BTlvlGZTdScCWg9t;

1.798
date	2008.07.02.20.52.43;	author zefram;	state Exp;
branches;
next	1.797;
commitid	Z1XkX5t3c8gzVg9t;

1.797
date	2008.07.02.20.41.42;	author zefram;	state Exp;
branches;
next	1.796;
commitid	nUy63mXAjLnNRg9t;

1.796
date	2008.07.02.20.40.21;	author zefram;	state Exp;
branches;
next	1.795;
commitid	qDajvay8wljhRg9t;

1.795
date	2008.06.22.13.03.04;	author zefram;	state Exp;
branches;
next	1.794;
commitid	hWWtDHTWeZWmEW7t;

1.794
date	2008.06.22.12.58.59;	author zefram;	state Exp;
branches;
next	1.793;
commitid	roybT3xxBFVYCW7t;

1.793
date	2008.06.22.12.57.06;	author zefram;	state Exp;
branches;
next	1.792;
commitid	bHvIzJTWHQXkCW7t;

1.792
date	2008.06.22.12.54.22;	author zefram;	state Exp;
branches;
next	1.791;
commitid	E5jRekkiK1MoBW7t;

1.791
date	2008.06.22.12.53.14;	author zefram;	state Exp;
branches;
next	1.790;
commitid	EZyki1UxdoA0BW7t;

1.790
date	2008.06.22.12.48.07;	author zefram;	state Exp;
branches;
next	1.789;
commitid	uLhUx3jJnClfzW7t;

1.789
date	2008.06.22.12.38.41;	author zefram;	state Exp;
branches;
next	1.788;
commitid	BRRq07DYF731wW7t;

1.788
date	2008.06.22.12.30.28;	author zefram;	state Exp;
branches;
next	1.787;
commitid	08jGre8WGCZbtW7t;

1.787
date	2008.06.22.12.29.00;	author zefram;	state Exp;
branches;
next	1.786;
commitid	TsRVakVKi0VGsW7t;

1.786
date	2008.06.14.14.36.24;	author zefram;	state Exp;
branches;
next	1.785;
commitid	8RbUtN5ERapjqV6t;

1.785
date	2008.06.11.22.48.49;	author zefram;	state Exp;
branches;
next	1.784;
commitid	UbTaqwpFlYqffA6t;

1.784
date	2008.06.11.22.42.14;	author zefram;	state Exp;
branches;
next	1.783;
commitid	jkH2e9hpxllZcA6t;

1.783
date	2008.06.11.22.39.32;	author zefram;	state Exp;
branches;
next	1.782;
commitid	2lCNVYcRNVY3cA6t;

1.782
date	2008.06.11.22.36.00;	author zefram;	state Exp;
branches;
next	1.781;
commitid	T8JPSltkfQVQaA6t;

1.781
date	2008.06.04.22.54.07;	author zefram;	state Exp;
branches;
next	1.780;
commitid	IJ04pHVEtn21vG5t;

1.780
date	2008.06.04.22.52.55;	author zefram;	state Exp;
branches;
next	1.779;
commitid	f9CY2dtb3pOBuG5t;

1.779
date	2008.06.04.22.51.53;	author zefram;	state Exp;
branches;
next	1.778;
commitid	vIH0FRetGlTfuG5t;

1.778
date	2008.06.04.22.49.39;	author zefram;	state Exp;
branches;
next	1.777;
commitid	DjKlh42EAJbutG5t;

1.777
date	2008.05.30.09.46.17;	author zefram;	state Exp;
branches;
next	1.776;
commitid	8pxlbg6QpoWHiY4t;

1.776
date	2008.05.30.09.45.14;	author zefram;	state Exp;
branches;
next	1.775;
commitid	Yd4XDUSER6LkiY4t;

1.775
date	2008.05.30.09.44.10;	author zefram;	state Exp;
branches;
next	1.774;
commitid	WQnnSN8bk5eZhY4t;

1.774
date	2008.05.30.09.41.22;	author zefram;	state Exp;
branches;
next	1.773;
commitid	6XKaRD2X9DKZgY4t;

1.773
date	2008.05.30.09.39.04;	author zefram;	state Exp;
branches;
next	1.772;
commitid	MBDS7nkcvOCegY4t;

1.772
date	2008.05.30.09.37.38;	author zefram;	state Exp;
branches;
next	1.771;
commitid	zrLwppiI01VJfY4t;

1.771
date	2008.05.30.09.36.18;	author zefram;	state Exp;
branches;
next	1.770;
commitid	HFKjeOEbbVxhfY4t;

1.770
date	2008.05.11.18.12.34;	author zefram;	state Exp;
branches;
next	1.769;
commitid	cCiT1X6GekWbIz2t;

1.769
date	2008.05.11.18.10.59;	author zefram;	state Exp;
branches;
next	1.768;
commitid	iyjLnGMZTXYHHz2t;

1.768
date	2008.05.11.18.09.30;	author zefram;	state Exp;
branches;
next	1.767;
commitid	ijnZQlCjRqPcHz2t;

1.767
date	2008.05.11.18.08.11;	author zefram;	state Exp;
branches;
next	1.766;
commitid	XZljWqQd7htKGz2t;

1.766
date	2008.05.11.18.07.11;	author zefram;	state Exp;
branches;
next	1.765;
commitid	hzIZuYYbmdTpGz2t;

1.765
date	2008.05.11.18.04.17;	author zefram;	state Exp;
branches;
next	1.764;
commitid	pph7Gni4s2UpFz2t;

1.764
date	2008.04.27.18.37.21;	author zefram;	state Exp;
branches;
next	1.763;
commitid	hEUxuJzLE7oFiM0t;

1.763
date	2008.04.27.18.35.45;	author zefram;	state Exp;
branches;
next	1.762;
commitid	BprAU5Q2jID6iM0t;

1.762
date	2008.04.27.18.35.28;	author zefram;	state Exp;
branches;
next	1.761;
commitid	lQugFzESb1A1iM0t;

1.761
date	2008.04.27.18.06.34;	author zefram;	state Exp;
branches;
next	1.760;
commitid	LhOOpsU5R9768M0t;

1.760
date	2008.04.27.18.05.02;	author zefram;	state Exp;
branches;
next	1.759;
commitid	gLftWrX5fxVy7M0t;

1.759
date	2008.04.27.18.03.18;	author zefram;	state Exp;
branches;
next	1.758;
commitid	bjfRFe5HK4iZ6M0t;

1.758
date	2008.04.27.18.01.20;	author zefram;	state Exp;
branches;
next	1.757;
commitid	R0m7uidzc36j6M0t;

1.757
date	2008.04.27.17.58.10;	author zefram;	state Exp;
branches;
next	1.756;
commitid	4wxocUCbP7Kd5M0t;

1.756
date	2008.04.27.17.56.26;	author zefram;	state Exp;
branches;
next	1.755;
commitid	hIyunaL39yKC4M0t;

1.755
date	2008.04.27.17.54.38;	author zefram;	state Exp;
branches;
next	1.754;
commitid	pYVLxHDyFgm04M0t;

1.754
date	2008.04.27.17.53.09;	author zefram;	state Exp;
branches;
next	1.753;
commitid	RpEVTfDhPNMu3M0t;

1.753
date	2008.04.15.15.02.28;	author zefram;	state Exp;
branches;
next	1.752;
commitid	QTPYIlUko4wQudZs;

1.752
date	2008.04.15.14.56.49;	author zefram;	state Exp;
branches;
next	1.751;
commitid	5PeMW78EoQ0VsdZs;

1.751
date	2008.04.02.09.14.34;	author zefram;	state Exp;
branches;
next	1.750;
commitid	86cPWrKuLwZpZvXs;

1.750
date	2008.04.02.09.11.32;	author zefram;	state Exp;
branches;
next	1.749;
commitid	qpWOWbrsbXYmYvXs;

1.749
date	2008.04.02.09.10.36;	author zefram;	state Exp;
branches;
next	1.748;
commitid	jMZjNhCXo7A3YvXs;

1.748
date	2008.03.30.22.36.15;	author zefram;	state Exp;
branches;
next	1.747;
commitid	DPjP6BvfC96qwcXs;

1.747
date	2008.03.25.22.23.25;	author zefram;	state Exp;
branches;
next	1.746;
commitid	ruwL6jxYIHTYByWs;

1.746
date	2008.03.25.22.17.18;	author zefram;	state Exp;
branches;
next	1.745;
commitid	1H6Qtq16UlqSzyWs;

1.745
date	2008.03.25.22.12.29;	author zefram;	state Exp;
branches;
next	1.744;
commitid	mJmMHRfcsuseyyWs;

1.744
date	2008.03.25.22.10.31;	author zefram;	state Exp;
branches;
next	1.743;
commitid	OFG5SdUcATpyxyWs;

1.743
date	2008.03.19.10.00.41;	author zefram;	state Exp;
branches;
next	1.742;
commitid	jHaKQ1JLvup8HIVs;

1.742
date	2008.03.19.09.48.37;	author zefram;	state Exp;
branches;
next	1.741;
commitid	SgU6F2xcbS4ZCIVs;

1.741
date	2008.03.19.09.45.41;	author zefram;	state Exp;
branches;
next	1.740;
commitid	6jks9BxQHRcZBIVs;

1.740
date	2008.03.19.09.43.55;	author zefram;	state Exp;
branches;
next	1.739;
commitid	ZLC8XdRjkkHnBIVs;

1.739
date	2008.03.19.09.41.30;	author zefram;	state Exp;
branches;
next	1.738;
commitid	THUHWBmwL6GyAIVs;

1.738
date	2008.03.19.09.39.04;	author zefram;	state Exp;
branches;
next	1.737;
commitid	PPYxTSBeDfKIzIVs;

1.737
date	2008.03.12.19.44.16;	author zefram;	state Exp;
branches;
next	1.736;
commitid	DhKy3ysoaoui9SUs;

1.736
date	2008.03.12.19.39.33;	author zefram;	state Exp;
branches;
next	1.735;
commitid	gF1Iyq3Ar4sE7SUs;

1.735
date	2008.03.12.19.33.04;	author zefram;	state Exp;
branches;
next	1.734;
commitid	XgvndlEysyAr5SUs;

1.734
date	2008.03.12.19.20.55;	author zefram;	state Exp;
branches;
next	1.733;
commitid	iY7HFF4y3zze1SUs;

1.733
date	2008.03.12.19.19.29;	author zefram;	state Exp;
branches;
next	1.732;
commitid	J8h1ImSwgZpN0SUs;

1.732
date	2008.03.11.20.49.21;	author zefram;	state Exp;
branches;
next	1.731;
commitid	K3pcIjIr6ZIxxKUs;

1.731
date	2008.03.11.17.15.30;	author zefram;	state Exp;
branches;
next	1.730;
commitid	e7fnMoojZVNcmJUs;

1.730
date	2008.03.05.10.44.53;	author zefram;	state Exp;
branches;
next	1.729;
commitid	MXfumx08YFlcoVTs;

1.729
date	2008.03.05.10.41.27;	author zefram;	state Exp;
branches;
next	1.728;
commitid	t8iaBmYjurl1nVTs;

1.728
date	2008.03.05.10.34.02;	author zefram;	state Exp;
branches;
next	1.727;
commitid	ikxZgGd4bhgtkVTs;

1.727
date	2008.03.05.10.31.38;	author zefram;	state Exp;
branches;
next	1.726;
commitid	tC7f6WnfrkfEjVTs;

1.726
date	2008.02.27.14.57.20;	author zefram;	state Exp;
branches;
next	1.725;
commitid	Zm57tjDImgtL03Ts;

1.725
date	2008.02.25.11.45.16;	author zefram;	state Exp;
branches;
next	1.724;
commitid	nrSf9QbDt4iQ0MSs;

1.724
date	2008.02.25.11.43.17;	author zefram;	state Exp;
branches;
next	1.723;
commitid	dU90CrNqLhc80MSs;

1.723
date	2008.02.25.11.16.56;	author zefram;	state Exp;
branches;
next	1.722;
commitid	MmHXIWA3LgI5RLSs;

1.722
date	2008.02.25.11.06.36;	author zefram;	state Exp;
branches;
next	1.721;
commitid	H6tXE2ELZhjzNLSs;

1.721
date	2008.02.25.10.51.11;	author zefram;	state Exp;
branches;
next	1.720;
commitid	We2BUiJGEIoiILSs;

1.720
date	2008.02.20.11.17.52;	author zefram;	state Exp;
branches;
next	1.719;
commitid	Z5CCBxQoPW6p18Ss;

1.719
date	2008.02.20.11.15.29;	author zefram;	state Exp;
branches;
next	1.718;
commitid	Zh5S0ViT8s8A08Ss;

1.718
date	2008.02.20.11.12.11;	author zefram;	state Exp;
branches;
next	1.717;
commitid	DzokAT4vASfsZ7Ss;

1.717
date	2008.02.20.11.07.53;	author zefram;	state Exp;
branches;
next	1.716;
commitid	AcZmPe47xzSYX7Ss;

1.716
date	2008.02.20.11.00.14;	author zefram;	state Exp;
branches;
next	1.715;
commitid	44jpq9xz2zBmV7Ss;

1.715
date	2008.02.19.17.29.03;	author zefram;	state Exp;
branches;
next	1.714;
commitid	mFtIS0BzBFEJ62Ss;

1.714
date	2008.02.19.17.28.40;	author zefram;	state Exp;
branches;
next	1.713;
commitid	3jmGuqUg1Y6C62Ss;

1.713
date	2008.02.19.17.27.13;	author zefram;	state Exp;
branches;
next	1.712;
commitid	bqBMQVikgbc762Ss;

1.712
date	2008.02.19.17.25.19;	author zefram;	state Exp;
branches;
next	1.711;
commitid	Rw2VTztvTxut52Ss;

1.711
date	2008.02.19.17.23.57;	author zefram;	state Exp;
branches;
next	1.710;
commitid	H7ExeN948c2052Ss;

1.710
date	2008.02.07.19.51.25;	author zefram;	state Exp;
branches;
next	1.709;
commitid	u7SrmVgNxLivhvQs;

1.709
date	2008.02.07.19.46.47;	author zefram;	state Exp;
branches;
next	1.708;
commitid	nHxhDhdFjWjUfvQs;

1.708
date	2008.02.06.10.30.51;	author zefram;	state Exp;
branches;
next	1.707;
commitid	Dhw8IUtjAoKbdkQs;

1.707
date	2008.02.06.10.27.34;	author zefram;	state Exp;
branches;
next	1.706;
commitid	jRbS5QxqWWn3ckQs;

1.706
date	2008.02.06.10.20.08;	author zefram;	state Exp;
branches;
next	1.705;
commitid	WOUhQkt5zE0t9kQs;

1.705
date	2008.02.05.16.02.56;	author zefram;	state Exp;
branches;
next	1.704;
commitid	U15asXKBoQM55eQs;

1.704
date	2008.02.05.09.48.05;	author zefram;	state Exp;
branches;
next	1.703;
commitid	YHYpqi9LToBs0cQs;

1.703
date	2008.02.04.18.40.50;	author zefram;	state Exp;
branches;
next	1.702;
commitid	e7HOUEqPo15gZ6Qs;

1.702
date	2008.02.04.18.39.02;	author zefram;	state Exp;
branches;
next	1.701;
commitid	BJvCS3xPE4qEY6Qs;

1.701
date	2008.02.04.14.22.12;	author zefram;	state Exp;
branches;
next	1.700;
commitid	YNvTdUbTzR2xy5Qs;

1.700
date	2008.02.04.12.04.10;	author zefram;	state Exp;
branches;
next	1.699;
commitid	efznKJsRBtAaN4Qs;

1.699
date	2008.02.04.12.03.43;	author zefram;	state Exp;
branches;
next	1.698;
commitid	pqkGVSPZdIv1N4Qs;

1.698
date	2008.02.02.10.04.04;	author zefram;	state Exp;
branches;
next	1.697;
commitid	KBpLyrc5fUIXbOPs;

1.697
date	2008.02.01.11.11.20;	author zefram;	state Exp;
branches;
next	1.696;
commitid	vV5OajjfQS02BGPs;

1.696
date	2008.02.01.11.08.03;	author zefram;	state Exp;
branches;
next	1.695;
commitid	QjrlbciiahEUzGPs;

1.695
date	2008.02.01.11.06.38;	author zefram;	state Exp;
branches;
next	1.694;
commitid	3MkHgQC7LZEqzGPs;

1.694
date	2008.02.01.11.04.56;	author zefram;	state Exp;
branches;
next	1.693;
commitid	daoQLAduiiKQyGPs;

1.693
date	2008.02.01.10.47.47;	author zefram;	state Exp;
branches;
next	1.692;
commitid	npmscZ4I4q2XsGPs;

1.692
date	2008.01.23.12.14.50;	author zefram;	state Exp;
branches;
next	1.691;
commitid	ElqHL4orND0KexOs;

1.691
date	2008.01.22.10.33.51;	author zefram;	state Exp;
branches;
next	1.690;
commitid	d7BjJ65OpA17IoOs;

1.690
date	2008.01.22.10.29.28;	author zefram;	state Exp;
branches;
next	1.689;
commitid	wa5WDJxcDgrBGoOs;

1.689
date	2008.01.22.10.26.29;	author zefram;	state Exp;
branches;
next	1.688;
commitid	iA9hd3T5v4hAFoOs;

1.688
date	2008.01.21.20.22.32;	author zefram;	state Exp;
branches;
next	1.687;
commitid	BEIgbDskP9M10kOs;

1.687
date	2008.01.21.10.31.37;	author zefram;	state Exp;
branches;
next	1.686;
commitid	xlvs1EYcDxYfJgOs;

1.686
date	2008.01.18.17.00.06;	author zefram;	state Exp;
branches;
next	1.685;
commitid	LcFB9eQKMfNyYUNs;

1.685
date	2008.01.17.10.21.41;	author zefram;	state Exp;
branches;
next	1.684;
commitid	vmc39GJcF7ZSNKNs;

1.684
date	2008.01.16.23.51.04;	author zefram;	state Exp;
branches;
next	1.683;
commitid	1JnfZ9tNemDxjHNs;

1.683
date	2008.01.16.16.49.55;	author zefram;	state Exp;
branches;
next	1.682;
commitid	su2G58hgEdx3ZENs;

1.682
date	2008.01.16.16.07.06;	author zefram;	state Exp;
branches;
next	1.681;
commitid	cTwlIkAtLXcnKENs;

1.681
date	2008.01.16.16.05.04;	author zefram;	state Exp;
branches;
next	1.680;
commitid	jMYXjDmUWMDGJENs;

1.680
date	2008.01.16.15.41.39;	author zefram;	state Exp;
branches;
next	1.679;
commitid	oSycyrBPDqJEBENs;

1.679
date	2008.01.16.15.36.19;	author zefram;	state Exp;
branches;
next	1.678;
commitid	kMHu5v8148qLzENs;

1.678
date	2008.01.16.15.34.08;	author zefram;	state Exp;
branches;
next	1.677;
commitid	9SJHvITacy23zENs;

1.677
date	2008.01.16.15.32.15;	author zefram;	state Exp;
branches;
next	1.676;
commitid	4Q623SVO8MWqyENs;

1.676
date	2008.01.16.15.28.51;	author zefram;	state Exp;
branches;
next	1.675;
commitid	swxnhXZWReagxENs;

1.675
date	2008.01.16.15.09.27;	author zefram;	state Exp;
branches;
next	1.674;
commitid	VbwB59bYU34BqENs;

1.674
date	2008.01.16.15.05.45;	author zefram;	state Exp;
branches;
next	1.673;
commitid	MAHUo4uvPTClpENs;

1.673
date	2008.01.16.14.34.38;	author zefram;	state Exp;
branches;
next	1.672;
commitid	l7OuKYDumzjFeENs;

1.672
date	2008.01.16.14.28.00;	author zefram;	state Exp;
branches;
next	1.671;
commitid	IJoFcjXZzRoocENs;

1.671
date	2008.01.16.14.25.23;	author zefram;	state Exp;
branches;
next	1.670;
commitid	x1nWf2TBYWgtbENs;

1.670
date	2008.01.15.20.19.45;	author zefram;	state Exp;
branches;
next	1.669;
commitid	bMjzvUDcpSQ2byNs;

1.669
date	2008.01.15.17.10.49;	author zefram;	state Exp;
branches;
next	1.668;
commitid	cVHWSxFtL68f8xNs;

1.668
date	2008.01.15.01.27.37;	author zefram;	state Exp;
branches;
next	1.667;
commitid	tAG4zaPQk5SxUrNs;

1.667
date	2008.01.14.21.19.07;	author zefram;	state Exp;
branches;
next	1.666;
commitid	BmV2JvXhMzPpxqNs;

1.666
date	2008.01.14.15.49.39;	author zefram;	state Exp;
branches;
next	1.665;
commitid	3wZUKqnHpN3oIoNs;

1.665
date	2008.01.14.13.58.12;	author zefram;	state Exp;
branches;
next	1.664;
commitid	SXFAyAl7qCc96oNs;

1.664
date	2008.01.14.12.41.51;	author zefram;	state Exp;
branches;
next	1.663;
commitid	ZM2pHWoa573VFnNs;

1.663
date	2008.01.10.14.42.01;	author zefram;	state Exp;
branches;
next	1.662;
commitid	jJ26W3Lhqf8atSMs;

1.662
date	2008.01.10.14.27.31;	author zefram;	state Exp;
branches;
next	1.661;
commitid	hsEGvQXZhN3boSMs;

1.661
date	2008.01.10.12.57.53;	author zefram;	state Exp;
branches;
next	1.660;
commitid	eKzM2gUiSUPpTRMs;

1.660
date	2008.01.10.11.32.06;	author zefram;	state Exp;
branches;
next	1.659;
commitid	4btRclCAO1IZpRMs;

1.659
date	2008.01.09.17.12.30;	author zefram;	state Exp;
branches;
next	1.658;
commitid	USM4YqUk6C3MkLMs;

1.658
date	2008.01.07.17.48.10;	author zefram;	state Exp;
branches;
next	1.657;
commitid	YUGlg6Azrx00BvMs;

1.657
date	2008.01.02.14.28.10;	author zefram;	state Exp;
branches;
next	1.656;
commitid	wpOXdVB5AS4mEQLs;

1.656
date	2008.01.02.14.27.12;	author zefram;	state Exp;
branches;
next	1.655;
commitid	o6txaLoAQwVVDQLs;

1.655
date	2008.01.02.14.25.46;	author zefram;	state Exp;
branches;
next	1.654;
commitid	U6gFWG4hFfpxDQLs;

1.654
date	2008.01.02.14.24.26;	author zefram;	state Exp;
branches;
next	1.653;
commitid	bQE4BLq9oLT4DQLs;

1.653
date	2008.01.02.14.21.49;	author zefram;	state Exp;
branches;
next	1.652;
commitid	Ug1MM6FFZ9HaCQLs;

1.652
date	2008.01.02.14.19.11;	author zefram;	state Exp;
branches;
next	1.651;
commitid	34RU2N2qFmpgBQLs;

1.651
date	2008.01.02.14.17.08;	author zefram;	state Exp;
branches;
next	1.650;
commitid	H1tpX2ks9w4zAQLs;

1.650
date	2008.01.02.14.15.50;	author zefram;	state Exp;
branches;
next	1.649;
commitid	t3lSG3IP5KW7AQLs;

1.649
date	2008.01.02.14.14.23;	author zefram;	state Exp;
branches;
next	1.648;
commitid	IgAyhgpNZ8dBzQLs;

1.648
date	2008.01.02.14.12.24;	author zefram;	state Exp;
branches;
next	1.647;
commitid	5mfBaPAgF44VyQLs;

1.647
date	2008.01.02.14.10.42;	author zefram;	state Exp;
branches;
next	1.646;
commitid	vFamPysl187myQLs;

1.646
date	2008.01.02.14.06.39;	author zefram;	state Exp;
branches;
next	1.645;
commitid	1M6aDlRIbtcYwQLs;

1.645
date	2007.12.22.23.44.48;	author zefram;	state Exp;
branches;
next	1.644;
commitid	B29AOdFrpeYa5uKs;

1.644
date	2007.12.22.18.37.23;	author zefram;	state Exp;
branches;
next	1.643;
commitid	9jBn3HYCmc6MnsKs;

1.643
date	2007.12.22.00.42.32;	author zefram;	state Exp;
branches;
next	1.642;
commitid	w9QQzoWn82s1rmKs;

1.642
date	2007.12.22.00.32.48;	author zefram;	state Exp;
branches;
next	1.641;
commitid	NeRYGbWGgdMGnmKs;

1.641
date	2007.12.21.22.41.29;	author zefram;	state Exp;
branches;
next	1.640;
commitid	wPwZEPv1saQuLlKs;

1.640
date	2007.12.21.22.37.52;	author zefram;	state Exp;
branches;
next	1.639;
commitid	W9kukZ1TcehfKlKs;

1.639
date	2007.12.21.01.07.25;	author zefram;	state Exp;
branches;
next	1.638;
commitid	Ej4374BpofwyBeKs;

1.638
date	2007.12.20.17.44.19;	author zefram;	state Exp;
branches;
next	1.637;
commitid	Aecd1YjNHh3y9cKs;

1.637
date	2007.12.20.17.41.05;	author zefram;	state Exp;
branches;
next	1.636;
commitid	M9mRhGgAV2qr8cKs;

1.636
date	2007.12.20.17.38.00;	author zefram;	state Exp;
branches;
next	1.635;
commitid	hVruY8sMy36o7cKs;

1.635
date	2007.12.20.17.34.10;	author zefram;	state Exp;
branches;
next	1.634;
commitid	QM4K5SWMpFu46cKs;

1.634
date	2007.12.20.17.31.07;	author zefram;	state Exp;
branches;
next	1.633;
commitid	l2qGYnQ2cjy15cKs;

1.633
date	2007.12.20.17.23.14;	author zefram;	state Exp;
branches;
next	1.632;
commitid	gTHKJsrILlzj2cKs;

1.632
date	2007.12.20.17.16.18;	author zefram;	state Exp;
branches;
next	1.631;
commitid	a44Kj2UwMfvVZbKs;

1.631
date	2007.12.20.17.09.36;	author zefram;	state Exp;
branches;
next	1.630;
commitid	rI3IF1ygtO5EXbKs;

1.630
date	2007.12.20.17.06.55;	author zefram;	state Exp;
branches;
next	1.629;
commitid	gIThD3oLVdGHWbKs;

1.629
date	2007.12.20.17.05.24;	author zefram;	state Exp;
branches;
next	1.628;
commitid	maF6misNDiGcWbKs;

1.628
date	2007.12.20.17.01.52;	author zefram;	state Exp;
branches;
next	1.627;
commitid	6kPDxoArmRMYUbKs;

1.627
date	2007.12.20.12.35.41;	author zefram;	state Exp;
branches;
next	1.626;
commitid	dV12W6BxzBAEraKs;

1.626
date	2007.12.20.11.24.26;	author zefram;	state Exp;
branches;
next	1.625;
commitid	jBlQF2ZvMPIc3aKs;

1.625
date	2007.12.20.02.41.15;	author zefram;	state Exp;
branches;
next	1.624;
commitid	sSpgZqGEpoeJ97Ks;

1.624
date	2007.12.19.21.54.27;	author zefram;	state Exp;
branches;
next	1.623;
commitid	awomWe4leJ5mz5Ks;

1.623
date	2007.12.19.21.53.15;	author zefram;	state Exp;
branches;
next	1.622;
commitid	HKAsHAMqcSqWy5Ks;

1.622
date	2007.12.19.21.51.33;	author zefram;	state Exp;
branches;
next	1.621;
commitid	sMX21t9d25qmy5Ks;

1.621
date	2007.12.19.21.50.43;	author zefram;	state Exp;
branches;
next	1.620;
commitid	ee9K3g053EZ4y5Ks;

1.620
date	2007.12.19.21.49.29;	author zefram;	state Exp;
branches;
next	1.619;
commitid	YocalXDj7mFEx5Ks;

1.619
date	2007.12.19.21.40.12;	author zefram;	state Exp;
branches;
next	1.618;
commitid	PUHKbbct8RTsu5Ks;

1.618
date	2007.12.10.14.01.22;	author zefram;	state Exp;
branches;
next	1.617;
commitid	e0UpeuXPIRhVeTIs;

1.617
date	2007.12.10.13.31.25;	author zefram;	state Exp;
branches;
next	1.616;
commitid	wjK71vn7ZTfH4TIs;

1.616
date	2007.12.10.12.54.41;	author zefram;	state Exp;
branches;
next	1.615;
commitid	pP6NmAg2iEW6SSIs;

1.615
date	2007.12.10.12.53.16;	author zefram;	state Exp;
branches;
next	1.614;
commitid	wYpbRwSyDJnDRSIs;

1.614
date	2007.12.10.12.50.33;	author zefram;	state Exp;
branches;
next	1.613;
commitid	Kv4a76o8V4DHQSIs;

1.613
date	2007.12.10.12.36.39;	author zefram;	state Exp;
branches;
next	1.612;
commitid	DiJo91NMQ2hVLSIs;

1.612
date	2007.12.10.12.27.40;	author zefram;	state Exp;
branches;
next	1.611;
commitid	YnbzWu3hUI3RISIs;

1.611
date	2007.12.05.23.17.23;	author zefram;	state Exp;
branches;
next	1.610;
commitid	MmxyzDhiKU5HtiIs;

1.610
date	2007.12.05.23.12.29;	author zefram;	state Exp;
branches;
next	1.609;
commitid	heAPCRYxx7A1siIs;

1.609
date	2007.12.05.23.07.07;	author zefram;	state Exp;
branches;
next	1.608;
commitid	UvdkWgyAV61cqiIs;

1.608
date	2007.12.05.23.04.15;	author zefram;	state Exp;
branches;
next	1.607;
commitid	p7vs4mEiL7ccpiIs;

1.607
date	2007.12.05.22.59.53;	author zefram;	state Exp;
branches;
next	1.606;
commitid	NvvvpMzS6f6HniIs;

1.606
date	2007.12.05.22.49.08;	author zefram;	state Exp;
branches;
next	1.605;
commitid	9E1DCQBM6Sn1kiIs;

1.605
date	2007.12.05.22.46.52;	author zefram;	state Exp;
branches;
next	1.604;
commitid	JxePfSwn8YWejiIs;

1.604
date	2007.12.05.22.45.43;	author zefram;	state Exp;
branches;
next	1.603;
commitid	jnkeMX1DhYzQiiIs;

1.603
date	2007.12.05.22.15.50;	author zefram;	state Exp;
branches;
next	1.602;
commitid	7PiCEGaIVH3A8iIs;

1.602
date	2007.12.05.02.22.33;	author zefram;	state Exp;
branches;
next	1.601;
commitid	FpnlBtiew5LcxbIs;

1.601
date	2007.12.05.02.13.02;	author zefram;	state Exp;
branches;
next	1.600;
commitid	ekP6hKTeTfQWtbIs;

1.600
date	2007.12.04.17.44.45;	author zefram;	state Exp;
branches;
next	1.599;
commitid	izm6ECci2K0AF8Is;

1.599
date	2007.12.04.15.12.18;	author zefram;	state Exp;
branches;
next	1.598;
commitid	sG398HNDeOJhP7Is;

1.598
date	2007.12.02.22.20.43;	author zefram;	state Exp;
branches;
next	1.597;
commitid	ogz5OYdiRRyfgUHs;

1.597
date	2007.12.02.22.15.17;	author zefram;	state Exp;
branches;
next	1.596;
commitid	AikpHuG4NdnoeUHs;

1.596
date	2007.12.02.22.12.22;	author zefram;	state Exp;
branches;
next	1.595;
commitid	Y9CJNNz1drqodUHs;

1.595
date	2007.12.02.22.10.33;	author zefram;	state Exp;
branches;
next	1.594;
commitid	5xNed50efJfKcUHs;

1.594
date	2007.12.02.22.07.01;	author zefram;	state Exp;
branches;
next	1.593;
commitid	lQTNml2M0u6ybUHs;

1.593
date	2007.12.02.22.03.55;	author zefram;	state Exp;
branches;
next	1.592;
commitid	1bg1bBPpcf0uaUHs;

1.592
date	2007.12.02.22.01.50;	author zefram;	state Exp;
branches;
next	1.591;
commitid	7BCAWucvhyDL9UHs;

1.591
date	2007.12.02.21.58.11;	author zefram;	state Exp;
branches;
next	1.590;
commitid	oiIUTtHAsfaw8UHs;

1.590
date	2007.12.02.21.55.09;	author zefram;	state Exp;
branches;
next	1.589;
commitid	xJQDgTM7iXyt7UHs;

1.589
date	2007.12.02.21.53.30;	author zefram;	state Exp;
branches;
next	1.588;
commitid	cHWBhyM2E1EU6UHs;

1.588
date	2007.12.02.21.51.16;	author zefram;	state Exp;
branches;
next	1.587;
commitid	zCPsT53xCNe96UHs;

1.587
date	2007.12.02.21.49.40;	author zefram;	state Exp;
branches;
next	1.586;
commitid	3GNHPMHZlOUz5UHs;

1.586
date	2007.12.02.21.46.31;	author zefram;	state Exp;
branches;
next	1.585;
commitid	IeAPjNKyYmRu4UHs;

1.585
date	2007.12.02.21.42.52;	author zefram;	state Exp;
branches;
next	1.584;
commitid	Psva9bSkE5og3UHs;

1.584
date	2007.12.02.21.19.42;	author zefram;	state Exp;
branches;
next	1.583;
commitid	lpsix5w2t1MiVTHs;

1.583
date	2007.11.29.16.03.38;	author zefram;	state Exp;
branches;
next	1.582;
commitid	0Laq5fNMA4kRguHs;

1.582
date	2007.11.29.11.58.14;	author zefram;	state Exp;
branches;
next	1.581;
commitid	Ajvi9ZtuV1YEUsHs;

1.581
date	2007.11.29.11.24.28;	author zefram;	state Exp;
branches;
next	1.580;
commitid	OvzXi27J72X3JsHs;

1.580
date	2007.11.29.02.10.23;	author zefram;	state Exp;
branches;
next	1.579;
commitid	7hUWEFSToyWZEpHs;

1.579
date	2007.11.28.16.03.42;	author zefram;	state Exp;
branches;
next	1.578;
commitid	wTWI0mws93DSimHs;

1.578
date	2007.11.28.09.43.54;	author zefram;	state Exp;
branches;
next	1.577;
commitid	qzjjNDeIrmdAckHs;

1.577
date	2007.11.27.16.58.49;	author zefram;	state Exp;
branches;
next	1.576;
commitid	DM51WS4Eav7MDeHs;

1.576
date	2007.11.20.00.12.37;	author zefram;	state Exp;
branches;
next	1.575;
commitid	yBs8QDTYy99wifGs;

1.575
date	2007.11.19.23.47.01;	author zefram;	state Exp;
branches;
next	1.574;
commitid	aubaUDfj5MbK9fGs;

1.574
date	2007.11.19.18.07.42;	author zefram;	state Exp;
branches;
next	1.573;
commitid	REbJKcszn0JlhdGs;

1.573
date	2007.11.19.12.21.01;	author zefram;	state Exp;
branches;
next	1.572;
commitid	KEDGARGvOREombGs;

1.572
date	2007.11.18.18.09.04;	author zefram;	state Exp;
branches;
next	1.571;
commitid	O8V6BGQyu9ILj5Gs;

1.571
date	2007.11.16.10.24.23;	author zefram;	state Exp;
branches;
next	1.570;
commitid	QQpvShmCtr2kOMFs;

1.570
date	2007.11.15.11.09.44;	author zefram;	state Exp;
branches;
next	1.569;
commitid	AVY5yDbqp1dW5FFs;

1.569
date	2007.11.15.11.07.30;	author zefram;	state Exp;
branches;
next	1.568;
commitid	N4Meee2MFYla5FFs;

1.568
date	2007.11.15.11.06.14;	author zefram;	state Exp;
branches;
next	1.567;
commitid	Qoaq2figHO8K4FFs;

1.567
date	2007.11.15.11.04.48;	author zefram;	state Exp;
branches;
next	1.566;
commitid	X9Ks15E9YpNe4FFs;

1.566
date	2007.11.12.18.23.35;	author zefram;	state Exp;
branches;
next	1.565;
commitid	4Koj5I2bv0EJAjFs;

1.565
date	2007.11.11.20.19.47;	author zefram;	state Exp;
branches;
next	1.564;
commitid	9wn7Bbb2FZ0xgcFs;

1.564
date	2007.11.07.17.56.41;	author zefram;	state Exp;
branches;
next	1.563;
commitid	3jMLMWOmVH0uBFEs;

1.563
date	2007.11.07.15.25.33;	author zefram;	state Exp;
branches;
next	1.562;
commitid	3KQlA7dX9mVDLEEs;

1.562
date	2007.11.07.15.24.22;	author zefram;	state Exp;
branches;
next	1.561;
commitid	fetLE84iydweLEEs;

1.561
date	2007.11.07.15.18.31;	author zefram;	state Exp;
branches;
next	1.560;
commitid	VbJ35biZu5CdJEEs;

1.560
date	2007.11.07.15.15.05;	author zefram;	state Exp;
branches;
next	1.559;
commitid	G8UQXrf9Zfi3IEEs;

1.559
date	2007.11.07.15.13.28;	author zefram;	state Exp;
branches;
next	1.558;
commitid	4SA0JpDhu4RtHEEs;

1.558
date	2007.11.07.15.09.48;	author zefram;	state Exp;
branches;
next	1.557;
commitid	EqGk7HQ0AzidGEEs;

1.557
date	2007.11.07.15.07.20;	author zefram;	state Exp;
branches;
next	1.556;
commitid	DgmIqEOQ93QnFEEs;

1.556
date	2007.11.07.15.03.52;	author zefram;	state Exp;
branches;
next	1.555;
commitid	rVZEN4IehHncEEEs;

1.555
date	2007.11.07.15.02.38;	author zefram;	state Exp;
branches;
next	1.554;
commitid	uCGxZgsftqfMDEEs;

1.554
date	2007.11.07.14.59.29;	author zefram;	state Exp;
branches;
next	1.553;
commitid	3F4lQ5jaXY0FCEEs;

1.553
date	2007.11.07.09.35.03;	author zefram;	state Exp;
branches;
next	1.552;
commitid	J2BSkxaCOwFnPCEs;

1.552
date	2007.11.06.18.11.46;	author zefram;	state Exp;
branches;
next	1.551;
commitid	rwbcQiYh8E7EIxEs;

1.551
date	2007.11.05.17.28.11;	author zefram;	state Exp;
branches;
next	1.550;
commitid	tuun9snwY6IGvpEs;

1.550
date	2007.11.05.00.01.56;	author zefram;	state Exp;
branches;
next	1.549;
commitid	bgdoALOMggaGIjEs;

1.549
date	2007.11.04.18.44.28;	author zefram;	state Exp;
branches;
next	1.548;
commitid	DjfP2axws3FQXhEs;

1.548
date	2007.10.31.10.24.18;	author zefram;	state Exp;
branches;
next	1.547;
commitid	OJIynOVm0ZCekJDs;

1.547
date	2007.10.31.10.13.43;	author zefram;	state Exp;
branches;
next	1.546;
commitid	AA54Q87ClYxAgJDs;

1.546
date	2007.10.28.19.49.09;	author zefram;	state Exp;
branches;
next	1.545;
commitid	wOPRDAyYAc1XxoDs;

1.545
date	2007.10.28.18.57.08;	author zefram;	state Exp;
branches;
next	1.544;
commitid	xbLKPq9fWO69goDs;

1.544
date	2007.10.28.16.41.45;	author zefram;	state Exp;
branches;
next	1.543;
commitid	8tdojLt7IhrIvnDs;

1.543
date	2007.10.28.16.36.17;	author zefram;	state Exp;
branches;
next	1.542;
commitid	U5vTWbI3lAkNtnDs;

1.542
date	2007.10.28.16.33.54;	author zefram;	state Exp;
branches;
next	1.541;
commitid	Fwf5p7TahfuXsnDs;

1.541
date	2007.10.28.16.21.01;	author zefram;	state Exp;
branches;
next	1.540;
commitid	KodnuY6nQMeAonDs;

1.540
date	2007.10.24.10.18.15;	author zefram;	state Exp;
branches;
next	1.539;
commitid	AkHxs5Ewfi5XvPCs;

1.539
date	2007.10.22.22.50.53;	author zefram;	state Exp;
branches;
next	1.538;
commitid	Up4sikRtEiUgKDCs;

1.538
date	2007.10.21.20.23.19;	author zefram;	state Exp;
branches;
next	1.537;
commitid	APP0cci6c9WEXuCs;

1.537
date	2007.10.21.16.19.09;	author zefram;	state Exp;
branches;
next	1.536;
commitid	n0uQDjQLhz2PBtCs;

1.536
date	2007.10.20.20.56.20;	author zefram;	state Exp;
branches;
next	1.535;
commitid	CHRBvJjzwSJVanCs;

1.535
date	2007.10.18.09.29.12;	author zefram;	state Exp;
branches;
next	1.534;
commitid	IIwo865bLAifr3Cs;

1.534
date	2007.10.18.09.27.19;	author zefram;	state Exp;
branches;
next	1.533;
commitid	qMFu4NJ9PguBq3Cs;

1.533
date	2007.10.16.11.07.24;	author zefram;	state Exp;
branches;
next	1.532;
commitid	9b7UDmcJeMBT2OBs;

1.532
date	2007.10.16.11.04.53;	author zefram;	state Exp;
branches;
next	1.531;
commitid	33BPLFOjmTl32OBs;

1.531
date	2007.10.16.11.02.22;	author zefram;	state Exp;
branches;
next	1.530;
commitid	hJHvViR2vVHc1OBs;

1.530
date	2007.10.16.10.59.37;	author zefram;	state Exp;
branches;
next	1.529;
commitid	GWVCX1bkXCuf0OBs;

1.529
date	2007.10.16.10.55.44;	author zefram;	state Exp;
branches;
next	1.528;
commitid	vjJPHykBaA2VYNBs;

1.528
date	2007.10.16.10.52.54;	author zefram;	state Exp;
branches;
next	1.527;
commitid	6ZiZqRGBOzSUXNBs;

1.527
date	2007.10.09.10.03.28;	author zefram;	state Exp;
branches;
next	1.526;
commitid	rz9WdKEOn6ZVUTAs;

1.526
date	2007.10.08.22.36.57;	author zefram;	state Exp;
branches;
next	1.525;
commitid	aytUGoxJCPpn7QAs;

1.525
date	2007.10.08.16.30.29;	author zefram;	state Exp;
branches;
next	1.524;
commitid	nQmZH2RRWdwH5OAs;

1.524
date	2007.10.08.10.50.21;	author zefram;	state Exp;
branches;
next	1.523;
commitid	0cNhXs3gB2v0dMAs;

1.523
date	2007.10.03.16.36.43;	author zefram;	state Exp;
branches;
next	1.522;
commitid	MAHp5XzQ2jaNhaAs;

1.522
date	2007.10.03.16.30.19;	author zefram;	state Exp;
branches;
next	1.521;
commitid	ctUVUwcjKZUBfaAs;

1.521
date	2007.10.03.13.37.59;	author zefram;	state Exp;
branches;
next	1.520;
commitid	A2OzJu7U4Ptsi9As;

1.520
date	2007.10.03.13.36.33;	author zefram;	state Exp;
branches;
next	1.519;
commitid	YutZCn8OE090i9As;

1.519
date	2007.10.03.13.35.03;	author zefram;	state Exp;
branches;
next	1.518;
commitid	OgFloyLg8ysuh9As;

1.518
date	2007.10.03.13.31.57;	author zefram;	state Exp;
branches;
next	1.517;
commitid	n32U5b2145Yog9As;

1.517
date	2007.10.03.13.21.06;	author zefram;	state Exp;
branches;
next	1.516;
commitid	K4ypmpHDP1TGc9As;

1.516
date	2007.10.03.13.18.22;	author zefram;	state Exp;
branches;
next	1.515;
commitid	KRQg6pKeXAkLb9As;

1.515
date	2007.10.03.13.16.41;	author zefram;	state Exp;
branches;
next	1.514;
commitid	ozV60PKKiA7ab9As;

1.514
date	2007.10.03.13.11.58;	author zefram;	state Exp;
branches;
next	1.513;
commitid	wQxWTOFSdk3z99As;

1.513
date	2007.10.03.13.02.38;	author zefram;	state Exp;
branches;
next	1.512;
commitid	iKsYFuY4svum69As;

1.512
date	2007.10.03.11.32.29;	author zefram;	state Exp;
branches;
next	1.511;
commitid	FoA7WxblKfypB8As;

1.511
date	2007.09.29.21.10.48;	author zefram;	state Exp;
branches;
next	1.510;
commitid	KxMF5syQbRfNVFzs;

1.510
date	2007.09.27.14.22.10;	author zefram;	state Exp;
branches;
next	1.509;
commitid	ged4lqMbETcwJnzs;

1.509
date	2007.09.25.21.23.01;	author zefram;	state Exp;
branches;
next	1.508;
commitid	rqITgUwjJnmX7azs;

1.508
date	2007.09.24.11.01.28;	author zefram;	state Exp;
branches;
next	1.507;
commitid	x0ReAHwehOgIIYys;

1.507
date	2007.09.24.08.56.22;	author zefram;	state Exp;
branches;
next	1.506;
commitid	QrgY8lhGwxuN1Yys;

1.506
date	2007.09.22.06.14.56;	author zefram;	state Exp;
branches;
next	1.505;
commitid	gCQvlzgBqgupcHys;

1.505
date	2007.09.18.12.10.27;	author zefram;	state Exp;
branches;
next	1.504;
commitid	GgTNuAx4uvxkidys;

1.504
date	2007.09.17.10.08.25;	author zefram;	state Exp;
branches;
next	1.503;
commitid	wRKC4ZWLfbjtE4ys;

1.503
date	2007.09.14.09.49.20;	author zefram;	state Exp;
branches;
next	1.502;
commitid	4qGBDWGp1eUSDGxs;

1.502
date	2007.09.14.09.47.52;	author zefram;	state Exp;
branches;
next	1.501;
commitid	QpzOZC7L4cupDGxs;

1.501
date	2007.09.14.09.46.56;	author zefram;	state Exp;
branches;
next	1.500;
commitid	IrsLOKtkoC85DGxs;

1.500
date	2007.09.14.09.42.45;	author zefram;	state Exp;
branches;
next	1.499;
commitid	LfpjPlWhqPMEBGxs;

1.499
date	2007.09.09.17.02.59;	author zefram;	state Exp;
branches;
next	1.498;
commitid	UuIGPVExlBVCc5xs;

1.498
date	2007.09.09.17.01.45;	author zefram;	state Exp;
branches;
next	1.497;
commitid	waJB2i0Mwujec5xs;

1.497
date	2007.09.09.16.55.39;	author zefram;	state Exp;
branches;
next	1.496;
commitid	nEmaBs2WzCG8a5xs;

1.496
date	2007.09.09.16.54.42;	author zefram;	state Exp;
branches;
next	1.495;
commitid	9UCTyWtenE9O95xs;

1.495
date	2007.09.09.16.52.33;	author zefram;	state Exp;
branches;
next	1.494;
commitid	wbU7t7enWnM495xs;

1.494
date	2007.09.09.16.50.02;	author zefram;	state Exp;
branches;
next	1.493;
commitid	OedTqc475ubd85xs;

1.493
date	2007.09.06.10.55.18;	author zefram;	state Exp;
branches;
next	1.492;
commitid	f91y0kUrScvtgFws;

1.492
date	2007.09.06.10.51.17;	author zefram;	state Exp;
branches;
next	1.491;
commitid	HoqnBL8XeL46fFws;

1.491
date	2007.09.06.10.49.00;	author zefram;	state Exp;
branches;
next	1.490;
commitid	5Lj13FK6lrSkeFws;

1.490
date	2007.09.06.10.47.37;	author zefram;	state Exp;
branches;
next	1.489;
commitid	hmfin5STO5kQdFws;

1.489
date	2007.09.06.10.44.56;	author zefram;	state Exp;
branches;
next	1.488;
commitid	5ZyNxH2bDdhWcFws;

1.488
date	2007.09.06.10.43.21;	author zefram;	state Exp;
branches;
next	1.487;
commitid	9Eff3VFsp9gocFws;

1.487
date	2007.09.03.18.43.14;	author zefram;	state Exp;
branches;
next	1.486;
commitid	GSkMepmm9khZWjws;

1.486
date	2007.08.30.14.43.39;	author zefram;	state Exp;
branches;
next	1.485;
commitid	VWlyRx58r1RKKMvs;

1.485
date	2007.08.30.11.46.45;	author zefram;	state Exp;
branches;
next	1.484;
commitid	VMwfQpMefKK4MLvs;

1.484
date	2007.08.29.23.23.59;	author zefram;	state Exp;
branches;
next	1.483;
commitid	NEfTtCHq1tngFHvs;

1.483
date	2007.08.29.16.38.47;	author zefram;	state Exp;
branches;
next	1.482;
commitid	8oXvqqAkskagqFvs;

1.482
date	2007.08.29.12.50.14;	author zefram;	state Exp;
branches;
next	1.481;
commitid	kvDSfgUB853N9Evs;

1.481
date	2007.08.29.11.18.39;	author zefram;	state Exp;
branches;
next	1.480;
commitid	PfBE85bvAMCtEDvs;

1.480
date	2007.08.29.11.16.49;	author zefram;	state Exp;
branches;
next	1.479;
commitid	UzveeCvYyzHQDDvs;

1.479
date	2007.08.29.11.15.40;	author zefram;	state Exp;
branches;
next	1.478;
commitid	KLXAK4m5JmfsDDvs;

1.478
date	2007.08.29.11.14.33;	author zefram;	state Exp;
branches;
next	1.477;
commitid	j9Hvg6Gv1zl4DDvs;

1.477
date	2007.08.29.11.12.04;	author zefram;	state Exp;
branches;
next	1.476;
commitid	EIkzswpBOpEdCDvs;

1.476
date	2007.08.29.11.09.34;	author zefram;	state Exp;
branches;
next	1.475;
commitid	i3cGYyrY8LfmBDvs;

1.475
date	2007.08.29.11.03.23;	author zefram;	state Exp;
branches;
next	1.474;
commitid	eQOKI33BqEYezDvs;

1.474
date	2007.08.29.11.00.24;	author zefram;	state Exp;
branches;
next	1.473;
commitid	kCIHhl1E0UndyDvs;

1.473
date	2007.08.29.10.59.31;	author zefram;	state Exp;
branches;
next	1.472;
commitid	ZXYaYHslfqyUxDvs;

1.472
date	2007.08.29.10.58.25;	author zefram;	state Exp;
branches;
next	1.471;
commitid	oRl4IFmWS3fxxDvs;

1.471
date	2007.08.29.10.57.08;	author zefram;	state Exp;
branches;
next	1.470;
commitid	ZJxwzSHzzIT5xDvs;

1.470
date	2007.08.29.10.55.07;	author zefram;	state Exp;
branches;
next	1.469;
commitid	gbul57EPUZdpwDvs;

1.469
date	2007.08.29.10.54.15;	author zefram;	state Exp;
branches;
next	1.468;
commitid	BdSZozoEA3u6wDvs;

1.468
date	2007.08.29.10.53.02;	author zefram;	state Exp;
branches;
next	1.467;
commitid	7KyPHJtIsNzGvDvs;

1.467
date	2007.08.29.10.50.03;	author zefram;	state Exp;
branches;
next	1.466;
commitid	bui4bc7UYobFuDvs;

1.466
date	2007.08.29.10.48.46;	author zefram;	state Exp;
branches;
next	1.465;
commitid	MUTbq3CNuDVduDvs;

1.465
date	2007.08.29.10.46.44;	author zefram;	state Exp;
branches;
next	1.464;
commitid	ZUHRshKRYgNutDvs;

1.464
date	2007.08.29.10.45.32;	author zefram;	state Exp;
branches;
next	1.463;
commitid	HAZy4cEilZB3tDvs;

1.463
date	2007.08.29.10.43.56;	author zefram;	state Exp;
branches;
next	1.462;
commitid	7qBY63RDJgQwsDvs;

1.462
date	2007.08.29.10.41.59;	author zefram;	state Exp;
branches;
next	1.461;
commitid	6c1OC1aAnQzRrDvs;

1.461
date	2007.08.29.10.34.55;	author zefram;	state Exp;
branches;
next	1.460;
commitid	uaB9byiv89HrpDvs;

1.460
date	2007.08.29.10.34.32;	author zefram;	state Exp;
branches;
next	1.459;
commitid	j0P6u7dqYEwjpDvs;

1.459
date	2007.08.28.06.19.01;	author zefram;	state Exp;
branches;
next	1.458;
commitid	2WPc3F99biUC1uvs;

1.458
date	2007.08.23.22.28.42;	author zefram;	state Exp;
branches;
next	1.457;

1.457
date	2007.08.23.14.13.42;	author zefram;	state Exp;
branches;
next	1.456;

1.456
date	2007.08.23.12.12.56;	author zefram;	state Exp;
branches;
next	1.455;

1.455
date	2007.08.22.17.28.52;	author zefram;	state Exp;
branches;
next	1.454;

1.454
date	2007.08.22.10.33.28;	author zefram;	state Exp;
branches;
next	1.453;

1.453
date	2007.08.21.18.19.39;	author zefram;	state Exp;
branches;
next	1.452;

1.452
date	2007.08.21.14.39.44;	author zefram;	state Exp;
branches;
next	1.451;

1.451
date	2007.08.20.16.38.29;	author zefram;	state Exp;
branches;
next	1.450;

1.450
date	2007.08.20.10.55.21;	author zefram;	state Exp;
branches;
next	1.449;

1.449
date	2007.08.19.15.10.33;	author zefram;	state Exp;
branches;
next	1.448;

1.448
date	2007.08.19.15.08.28;	author zefram;	state Exp;
branches;
next	1.447;

1.447
date	2007.08.19.15.06.50;	author zefram;	state Exp;
branches;
next	1.446;

1.446
date	2007.08.19.15.00.29;	author zefram;	state Exp;
branches;
next	1.445;

1.445
date	2007.08.19.14.58.54;	author zefram;	state Exp;
branches;
next	1.444;

1.444
date	2007.08.19.14.56.38;	author zefram;	state Exp;
branches;
next	1.443;

1.443
date	2007.08.18.02.39.36;	author zefram;	state Exp;
branches;
next	1.442;

1.442
date	2007.08.17.10.24.33;	author zefram;	state Exp;
branches;
next	1.441;

1.441
date	2007.08.17.10.22.00;	author zefram;	state Exp;
branches;
next	1.440;

1.440
date	2007.08.17.10.19.13;	author zefram;	state Exp;
branches;
next	1.439;

1.439
date	2007.08.17.10.18.07;	author zefram;	state Exp;
branches;
next	1.438;

1.438
date	2007.08.15.15.59.08;	author zefram;	state Exp;
branches;
next	1.437;

1.437
date	2007.08.13.12.31.28;	author zefram;	state Exp;
branches;
next	1.436;

1.436
date	2007.08.13.12.27.24;	author zefram;	state Exp;
branches;
next	1.435;

1.435
date	2007.08.13.12.22.36;	author zefram;	state Exp;
branches;
next	1.434;

1.434
date	2007.08.13.12.21.27;	author zefram;	state Exp;
branches;
next	1.433;

1.433
date	2007.08.13.12.18.03;	author zefram;	state Exp;
branches;
next	1.432;

1.432
date	2007.08.13.12.17.05;	author zefram;	state Exp;
branches;
next	1.431;

1.431
date	2007.08.13.12.14.13;	author zefram;	state Exp;
branches;
next	1.430;

1.430
date	2007.08.13.12.12.42;	author zefram;	state Exp;
branches;
next	1.429;

1.429
date	2007.08.13.12.10.37;	author zefram;	state Exp;
branches;
next	1.428;

1.428
date	2007.08.13.09.50.49;	author zefram;	state Exp;
branches;
next	1.427;

1.427
date	2007.08.13.09.47.22;	author zefram;	state Exp;
branches;
next	1.426;

1.426
date	2007.08.13.09.31.02;	author zefram;	state Exp;
branches;
next	1.425;

1.425
date	2007.08.08.10.02.52;	author zefram;	state Exp;
branches;
next	1.424;

1.424
date	2007.08.08.10.01.22;	author zefram;	state Exp;
branches;
next	1.423;

1.423
date	2007.08.07.20.27.18;	author zefram;	state Exp;
branches;
next	1.422;

1.422
date	2007.08.07.20.21.24;	author zefram;	state Exp;
branches;
next	1.421;

1.421
date	2007.08.03.15.19.40;	author zefram;	state Exp;
branches;
next	1.420;

1.420
date	2007.08.02.10.12.07;	author zefram;	state Exp;
branches;
next	1.419;

1.419
date	2007.08.02.10.09.52;	author zefram;	state Exp;
branches;
next	1.418;

1.418
date	2007.08.02.09.58.45;	author zefram;	state Exp;
branches;
next	1.417;

1.417
date	2007.08.02.09.49.18;	author zefram;	state Exp;
branches;
next	1.416;

1.416
date	2007.08.02.09.36.10;	author zefram;	state Exp;
branches;
next	1.415;

1.415
date	2007.08.02.09.19.18;	author zefram;	state Exp;
branches;
next	1.414;

1.414
date	2007.08.02.09.18.13;	author zefram;	state Exp;
branches;
next	1.413;

1.413
date	2007.08.01.16.38.15;	author zefram;	state Exp;
branches;
next	1.412;

1.412
date	2007.08.01.10.01.44;	author zefram;	state Exp;
branches;
next	1.411;

1.411
date	2007.08.01.10.00.23;	author zefram;	state Exp;
branches;
next	1.410;

1.410
date	2007.08.01.09.54.20;	author zefram;	state Exp;
branches;
next	1.409;

1.409
date	2007.08.01.09.50.52;	author zefram;	state Exp;
branches;
next	1.408;

1.408
date	2007.08.01.09.42.36;	author zefram;	state Exp;
branches;
next	1.407;

1.407
date	2007.08.01.09.41.34;	author zefram;	state Exp;
branches;
next	1.406;

1.406
date	2007.07.25.21.53.22;	author zefram;	state Exp;
branches;
next	1.405;

1.405
date	2007.07.25.21.51.57;	author zefram;	state Exp;
branches;
next	1.404;

1.404
date	2007.07.25.21.50.03;	author zefram;	state Exp;
branches;
next	1.403;

1.403
date	2007.07.25.21.33.48;	author zefram;	state Exp;
branches;
next	1.402;

1.402
date	2007.07.25.21.31.27;	author zefram;	state Exp;
branches;
next	1.401;

1.401
date	2007.07.24.22.50.02;	author zefram;	state Exp;
branches;
next	1.400;

1.400
date	2007.07.23.21.54.30;	author zefram;	state Exp;
branches;
next	1.399;

1.399
date	2007.07.23.21.47.01;	author zefram;	state Exp;
branches;
next	1.398;

1.398
date	2007.07.23.09.22.12;	author zefram;	state Exp;
branches;
next	1.397;

1.397
date	2007.07.23.08.05.56;	author zefram;	state Exp;
branches;
next	1.396;

1.396
date	2007.07.23.08.01.01;	author zefram;	state Exp;
branches;
next	1.395;

1.395
date	2007.07.23.07.59.41;	author zefram;	state Exp;
branches;
next	1.394;

1.394
date	2007.07.23.07.58.16;	author zefram;	state Exp;
branches;
next	1.393;

1.393
date	2007.07.23.07.56.37;	author zefram;	state Exp;
branches;
next	1.392;

1.392
date	2007.07.21.08.29.05;	author zefram;	state Exp;
branches;
next	1.391;

1.391
date	2007.07.19.11.53.27;	author zefram;	state Exp;
branches;
next	1.390;

1.390
date	2007.07.19.06.38.15;	author zefram;	state Exp;
branches;
next	1.389;

1.389
date	2007.07.18.20.07.11;	author zefram;	state Exp;
branches;
next	1.388;

1.388
date	2007.07.18.10.01.29;	author zefram;	state Exp;
branches;
next	1.387;

1.387
date	2007.07.18.09.55.55;	author zefram;	state Exp;
branches;
next	1.386;

1.386
date	2007.07.18.09.37.14;	author zefram;	state Exp;
branches;
next	1.385;

1.385
date	2007.07.18.09.30.14;	author zefram;	state Exp;
branches;
next	1.384;

1.384
date	2007.07.18.09.20.16;	author zefram;	state Exp;
branches;
next	1.383;

1.383
date	2007.07.11.08.40.59;	author zefram;	state Exp;
branches;
next	1.382;

1.382
date	2007.07.11.08.34.41;	author zefram;	state Exp;
branches;
next	1.381;

1.381
date	2007.07.11.08.26.07;	author zefram;	state Exp;
branches;
next	1.380;

1.380
date	2007.07.11.08.18.08;	author zefram;	state Exp;
branches;
next	1.379;

1.379
date	2007.07.11.08.11.58;	author zefram;	state Exp;
branches;
next	1.378;

1.378
date	2007.07.11.08.10.12;	author zefram;	state Exp;
branches;
next	1.377;

1.377
date	2007.07.11.08.08.17;	author zefram;	state Exp;
branches;
next	1.376;

1.376
date	2007.07.11.08.07.20;	author zefram;	state Exp;
branches;
next	1.375;

1.375
date	2007.07.11.08.05.53;	author zefram;	state Exp;
branches;
next	1.374;

1.374
date	2007.07.09.05.50.04;	author zefram;	state Exp;
branches;
next	1.373;

1.373
date	2007.07.09.05.41.00;	author zefram;	state Exp;
branches;
next	1.372;

1.372
date	2007.07.09.05.38.00;	author zefram;	state Exp;
branches;
next	1.371;

1.371
date	2007.07.05.09.56.25;	author zefram;	state Exp;
branches;
next	1.370;

1.370
date	2007.07.05.09.54.19;	author zefram;	state Exp;
branches;
next	1.369;

1.369
date	2007.07.05.09.49.47;	author zefram;	state Exp;
branches;
next	1.368;

1.368
date	2007.07.05.09.44.17;	author zefram;	state Exp;
branches;
next	1.367;

1.367
date	2007.07.05.09.43.12;	author zefram;	state Exp;
branches;
next	1.366;

1.366
date	2007.07.05.09.37.47;	author zefram;	state Exp;
branches;
next	1.365;

1.365
date	2007.07.05.09.36.38;	author zefram;	state Exp;
branches;
next	1.364;

1.364
date	2007.07.01.21.16.54;	author zefram;	state Exp;
branches;
next	1.363;

1.363
date	2007.07.01.19.40.15;	author zefram;	state Exp;
branches;
next	1.362;

1.362
date	2007.07.01.09.17.38;	author zefram;	state Exp;
branches;
next	1.361;

1.361
date	2007.07.01.09.08.50;	author zefram;	state Exp;
branches;
next	1.360;

1.360
date	2007.07.01.09.06.53;	author zefram;	state Exp;
branches;
next	1.359;

1.359
date	2007.07.01.09.02.51;	author zefram;	state Exp;
branches;
next	1.358;

1.358
date	2007.07.01.09.02.24;	author zefram;	state Exp;
branches;
next	1.357;

1.357
date	2007.07.01.08.56.52;	author zefram;	state Exp;
branches;
next	1.356;

1.356
date	2007.07.01.08.54.14;	author zefram;	state Exp;
branches;
next	1.355;

1.355
date	2007.06.29.06.51.28;	author zefram;	state Exp;
branches;
next	1.354;

1.354
date	2007.06.28.16.12.40;	author zefram;	state Exp;
branches;
next	1.353;

1.353
date	2007.06.28.15.16.04;	author zefram;	state Exp;
branches;
next	1.352;

1.352
date	2007.06.28.14.52.33;	author zefram;	state Exp;
branches;
next	1.351;

1.351
date	2007.06.28.08.46.42;	author zefram;	state Exp;
branches;
next	1.350;

1.350
date	2007.06.28.08.45.11;	author zefram;	state Exp;
branches;
next	1.349;

1.349
date	2007.06.28.08.36.12;	author zefram;	state Exp;
branches;
next	1.348;

1.348
date	2007.06.28.08.33.45;	author zefram;	state Exp;
branches;
next	1.347;

1.347
date	2007.06.28.08.30.34;	author zefram;	state Exp;
branches;
next	1.346;

1.346
date	2007.06.28.08.25.34;	author zefram;	state Exp;
branches;
next	1.345;

1.345
date	2007.06.28.08.23.10;	author zefram;	state Exp;
branches;
next	1.344;

1.344
date	2007.06.28.08.21.51;	author zefram;	state Exp;
branches;
next	1.343;

1.343
date	2007.06.28.08.20.07;	author zefram;	state Exp;
branches;
next	1.342;

1.342
date	2007.06.28.08.19.07;	author zefram;	state Exp;
branches;
next	1.341;

1.341
date	2007.06.28.08.17.30;	author zefram;	state Exp;
branches;
next	1.340;

1.340
date	2007.06.28.08.15.47;	author zefram;	state Exp;
branches;
next	1.339;

1.339
date	2007.06.28.08.14.13;	author zefram;	state Exp;
branches;
next	1.338;

1.338
date	2007.06.25.14.19.24;	author zefram;	state Exp;
branches;
next	1.337;

1.337
date	2007.06.25.14.13.28;	author zefram;	state Exp;
branches;
next	1.336;

1.336
date	2007.06.25.14.11.18;	author zefram;	state Exp;
branches;
next	1.335;

1.335
date	2007.06.24.08.33.37;	author zefram;	state Exp;
branches;
next	1.334;

1.334
date	2007.06.24.08.31.47;	author zefram;	state Exp;
branches;
next	1.333;

1.333
date	2007.06.24.08.24.51;	author zefram;	state Exp;
branches;
next	1.332;

1.332
date	2007.06.24.08.23.58;	author zefram;	state Exp;
branches;
next	1.331;

1.331
date	2007.06.24.08.21.56;	author zefram;	state Exp;
branches;
next	1.330;

1.330
date	2007.06.24.08.20.07;	author zefram;	state Exp;
branches;
next	1.329;

1.329
date	2007.06.24.08.16.22;	author zefram;	state Exp;
branches;
next	1.328;

1.328
date	2007.06.24.08.14.58;	author zefram;	state Exp;
branches;
next	1.327;

1.327
date	2007.06.24.08.12.04;	author zefram;	state Exp;
branches;
next	1.326;

1.326
date	2007.06.18.20.07.29;	author zefram;	state Exp;
branches;
next	1.325;

1.325
date	2007.06.18.08.51.29;	author zefram;	state Exp;
branches;
next	1.324;

1.324
date	2007.06.18.08.50.12;	author zefram;	state Exp;
branches;
next	1.323;

1.323
date	2007.06.18.08.39.45;	author zefram;	state Exp;
branches;
next	1.322;

1.322
date	2007.06.18.08.34.10;	author zefram;	state Exp;
branches;
next	1.321;

1.321
date	2007.06.13.08.29.08;	author zefram;	state Exp;
branches;
next	1.320;

1.320
date	2007.06.13.07.44.48;	author zefram;	state Exp;
branches;
next	1.319;

1.319
date	2007.06.12.07.49.31;	author zefram;	state Exp;
branches;
next	1.318;

1.318
date	2007.06.12.07.48.13;	author zefram;	state Exp;
branches;
next	1.317;

1.317
date	2007.06.12.07.42.06;	author zefram;	state Exp;
branches;
next	1.316;

1.316
date	2007.06.08.09.11.46;	author zefram;	state Exp;
branches;
next	1.315;

1.315
date	2007.06.08.00.53.47;	author zefram;	state Exp;
branches;
next	1.314;

1.314
date	2007.06.08.00.51.49;	author zefram;	state Exp;
branches;
next	1.313;

1.313
date	2007.06.08.00.36.01;	author zefram;	state Exp;
branches;
next	1.312;

1.312
date	2007.06.08.00.08.40;	author zefram;	state Exp;
branches;
next	1.311;

1.311
date	2007.06.06.09.13.04;	author zefram;	state Exp;
branches;
next	1.310;

1.310
date	2007.06.06.09.08.50;	author zefram;	state Exp;
branches;
next	1.309;

1.309
date	2007.06.06.09.05.46;	author zefram;	state Exp;
branches;
next	1.308;

1.308
date	2007.06.06.09.00.44;	author zefram;	state Exp;
branches;
next	1.307;

1.307
date	2007.06.06.08.59.15;	author zefram;	state Exp;
branches;
next	1.306;

1.306
date	2007.06.06.08.50.23;	author zefram;	state Exp;
branches;
next	1.305;

1.305
date	2007.06.06.08.47.21;	author zefram;	state Exp;
branches;
next	1.304;

1.304
date	2007.06.06.08.46.13;	author zefram;	state Exp;
branches;
next	1.303;

1.303
date	2007.06.04.09.05.34;	author zefram;	state Exp;
branches;
next	1.302;

1.302
date	2007.06.04.09.03.50;	author zefram;	state Exp;
branches;
next	1.301;

1.301
date	2007.06.04.09.02.49;	author zefram;	state Exp;
branches;
next	1.300;

1.300
date	2007.06.04.08.53.20;	author zefram;	state Exp;
branches;
next	1.299;

1.299
date	2007.06.04.08.51.57;	author zefram;	state Exp;
branches;
next	1.298;

1.298
date	2007.06.04.08.50.04;	author zefram;	state Exp;
branches;
next	1.297;

1.297
date	2007.05.31.13.03.58;	author zefram;	state Exp;
branches;
next	1.296;

1.296
date	2007.05.31.09.26.44;	author zefram;	state Exp;
branches;
next	1.295;

1.295
date	2007.05.31.09.24.22;	author zefram;	state Exp;
branches;
next	1.294;

1.294
date	2007.05.31.09.22.06;	author zefram;	state Exp;
branches;
next	1.293;

1.293
date	2007.05.31.09.19.19;	author zefram;	state Exp;
branches;
next	1.292;

1.292
date	2007.05.31.09.17.46;	author zefram;	state Exp;
branches;
next	1.291;

1.291
date	2007.05.26.08.40.37;	author zefram;	state Exp;
branches;
next	1.290;

1.290
date	2007.05.26.08.26.38;	author zefram;	state Exp;
branches;
next	1.289;

1.289
date	2007.05.24.23.04.52;	author zefram;	state Exp;
branches;
next	1.288;

1.288
date	2007.05.23.09.06.44;	author zefram;	state Exp;
branches;
next	1.287;

1.287
date	2007.05.23.09.05.42;	author zefram;	state Exp;
branches;
next	1.286;

1.286
date	2007.05.23.09.03.23;	author zefram;	state Exp;
branches;
next	1.285;

1.285
date	2007.05.23.08.58.19;	author zefram;	state Exp;
branches;
next	1.284;

1.284
date	2007.05.19.06.09.02;	author zefram;	state Exp;
branches;
next	1.283;

1.283
date	2007.05.18.09.00.03;	author zefram;	state Exp;
branches;
next	1.282;

1.282
date	2007.05.14.22.06.21;	author zefram;	state Exp;
branches;
next	1.281;

1.281
date	2007.05.14.19.34.56;	author zefram;	state Exp;
branches;
next	1.280;

1.280
date	2007.05.11.21.59.16;	author zefram;	state Exp;
branches;
next	1.279;

1.279
date	2007.05.11.02.15.28;	author zefram;	state Exp;
branches;
next	1.278;

1.278
date	2007.05.07.06.43.30;	author zefram;	state Exp;
branches;
next	1.277;

1.277
date	2007.05.07.06.31.59;	author zefram;	state Exp;
branches;
next	1.276;

1.276
date	2007.05.07.06.25.19;	author zefram;	state Exp;
branches;
next	1.275;

1.275
date	2007.05.07.06.21.57;	author zefram;	state Exp;
branches;
next	1.274;

1.274
date	2007.05.03.10.02.32;	author zefram;	state Exp;
branches;
next	1.273;

1.273
date	2007.05.03.09.59.28;	author zefram;	state Exp;
branches;
next	1.272;

1.272
date	2007.05.03.09.55.27;	author zefram;	state Exp;
branches;
next	1.271;

1.271
date	2007.05.03.09.52.52;	author zefram;	state Exp;
branches;
next	1.270;

1.270
date	2007.05.01.23.53.19;	author zefram;	state Exp;
branches;
next	1.269;

1.269
date	2007.05.01.23.40.56;	author zefram;	state Exp;
branches;
next	1.268;

1.268
date	2007.04.30.20.00.42;	author zefram;	state Exp;
branches;
next	1.267;

1.267
date	2007.04.29.22.58.52;	author zefram;	state Exp;
branches;
next	1.266;

1.266
date	2007.04.29.22.40.00;	author zefram;	state Exp;
branches;
next	1.265;

1.265
date	2007.04.29.22.09.38;	author zefram;	state Exp;
branches;
next	1.264;

1.264
date	2007.04.29.22.06.39;	author zefram;	state Exp;
branches;
next	1.263;

1.263
date	2007.04.29.22.04.50;	author zefram;	state Exp;
branches;
next	1.262;

1.262
date	2007.04.29.22.00.25;	author zefram;	state Exp;
branches;
next	1.261;

1.261
date	2007.04.29.21.57.46;	author zefram;	state Exp;
branches;
next	1.260;

1.260
date	2007.04.29.21.52.30;	author zefram;	state Exp;
branches;
next	1.259;

1.259
date	2007.04.23.20.28.25;	author zefram;	state Exp;
branches;
next	1.258;

1.258
date	2007.04.20.22.38.34;	author zefram;	state Exp;
branches;
next	1.257;

1.257
date	2007.04.19.07.03.23;	author zefram;	state Exp;
branches;
next	1.256;

1.256
date	2007.04.19.07.00.59;	author zefram;	state Exp;
branches;
next	1.255;

1.255
date	2007.04.16.19.11.11;	author zefram;	state Exp;
branches;
next	1.254;

1.254
date	2007.04.12.04.54.27;	author zefram;	state Exp;
branches;
next	1.253;

1.253
date	2007.04.11.22.42.22;	author zefram;	state Exp;
branches;
next	1.252;

1.252
date	2007.04.11.21.55.57;	author zefram;	state Exp;
branches;
next	1.251;

1.251
date	2007.04.11.06.36.28;	author zefram;	state Exp;
branches;
next	1.250;

1.250
date	2007.04.10.15.38.44;	author zefram;	state Exp;
branches;
next	1.249;

1.249
date	2007.04.10.13.18.51;	author zefram;	state Exp;
branches;
next	1.248;

1.248
date	2007.04.06.08.03.37;	author zefram;	state Exp;
branches;
next	1.247;

1.247
date	2007.04.02.22.10.43;	author zefram;	state Exp;
branches;
next	1.246;

1.246
date	2007.04.02.22.06.33;	author zefram;	state Exp;
branches;
next	1.245;

1.245
date	2007.04.02.22.05.26;	author zefram;	state Exp;
branches;
next	1.244;

1.244
date	2007.04.02.22.02.28;	author zefram;	state Exp;
branches;
next	1.243;

1.243
date	2007.04.02.22.00.39;	author zefram;	state Exp;
branches;
next	1.242;

1.242
date	2007.04.01.23.06.55;	author zefram;	state Exp;
branches;
next	1.241;

1.241
date	2007.03.31.23.30.41;	author zefram;	state Exp;
branches;
next	1.240;

1.240
date	2007.03.31.20.11.45;	author zefram;	state Exp;
branches;
next	1.239;

1.239
date	2007.03.30.14.32.47;	author zefram;	state Exp;
branches;
next	1.238;

1.238
date	2007.03.30.10.54.17;	author zefram;	state Exp;
branches;
next	1.237;

1.237
date	2007.03.28.21.51.35;	author zefram;	state Exp;
branches;
next	1.236;

1.236
date	2007.03.27.15.32.48;	author zefram;	state Exp;
branches;
next	1.235;

1.235
date	2007.03.27.15.32.27;	author zefram;	state Exp;
branches;
next	1.234;

1.234
date	2007.03.23.16.02.36;	author zefram;	state Exp;
branches;
next	1.233;

1.233
date	2007.03.23.15.22.54;	author zefram;	state Exp;
branches;
next	1.232;

1.232
date	2007.03.23.10.39.20;	author zefram;	state Exp;
branches;
next	1.231;

1.231
date	2007.03.22.16.49.55;	author zefram;	state Exp;
branches;
next	1.230;

1.230
date	2007.03.22.16.22.26;	author zefram;	state Exp;
branches;
next	1.229;

1.229
date	2007.03.22.16.12.41;	author zefram;	state Exp;
branches;
next	1.228;

1.228
date	2007.03.22.16.12.07;	author zefram;	state Exp;
branches;
next	1.227;

1.227
date	2007.03.22.13.23.34;	author zefram;	state Exp;
branches;
next	1.226;

1.226
date	2007.03.22.13.21.53;	author zefram;	state Exp;
branches;
next	1.225;

1.225
date	2007.03.22.12.58.29;	author zefram;	state Exp;
branches;
next	1.224;

1.224
date	2007.03.22.12.56.25;	author zefram;	state Exp;
branches;
next	1.223;

1.223
date	2007.03.22.12.39.58;	author zefram;	state Exp;
branches;
next	1.222;

1.222
date	2007.03.22.12.25.36;	author zefram;	state Exp;
branches;
next	1.221;

1.221
date	2007.03.22.12.01.37;	author zefram;	state Exp;
branches;
next	1.220;

1.220
date	2007.03.22.11.56.59;	author zefram;	state Exp;
branches;
next	1.219;

1.219
date	2007.03.22.11.54.01;	author zefram;	state Exp;
branches;
next	1.218;

1.218
date	2007.03.22.11.53.07;	author zefram;	state Exp;
branches;
next	1.217;

1.217
date	2007.03.22.11.40.00;	author zefram;	state Exp;
branches;
next	1.216;

1.216
date	2007.03.22.11.37.32;	author zefram;	state Exp;
branches;
next	1.215;

1.215
date	2007.03.22.11.34.48;	author zefram;	state Exp;
branches;
next	1.214;

1.214
date	2007.03.22.11.32.12;	author zefram;	state Exp;
branches;
next	1.213;

1.213
date	2007.03.22.11.29.10;	author zefram;	state Exp;
branches;
next	1.212;

1.212
date	2007.03.22.11.24.32;	author zefram;	state Exp;
branches;
next	1.211;

1.211
date	2007.03.22.11.14.56;	author zefram;	state Exp;
branches;
next	1.210;

1.210
date	2007.01.07.23.02.46;	author michaeln;	state Exp;
branches;
next	1.209;

1.209
date	2006.12.06.22.20.28;	author michaeln;	state Exp;
branches;
next	1.208;

1.208
date	2006.12.03.23.33.28;	author michaeln;	state Exp;
branches;
next	1.207;

1.207
date	2006.11.27.00.46.51;	author michaeln;	state Exp;
branches;
next	1.206;

1.206
date	2006.11.26.23.38.17;	author michaeln;	state Exp;
branches;
next	1.205;

1.205
date	2006.11.09.02.51.39;	author michaeln;	state Exp;
branches;
next	1.204;

1.204
date	2006.09.19.00.37.34;	author michaeln;	state Exp;
branches;
next	1.203;

1.203
date	2006.09.18.23.38.56;	author michaeln;	state Exp;
branches;
next	1.202;

1.202
date	2006.09.11.01.35.12;	author michaeln;	state Exp;
branches;
next	1.201;

1.201
date	2006.07.17.23.45.40;	author michaeln;	state Exp;
branches;
next	1.200;

1.200
date	2006.07.17.23.37.57;	author michaeln;	state Exp;
branches;
next	1.199;

1.199
date	2006.03.21.02.14.34;	author michaeln;	state Exp;
branches;
next	1.198;

1.198
date	2006.03.21.02.13.24;	author michaeln;	state Exp;
branches;
next	1.197;

1.197
date	2006.03.07.23.39.38;	author michaeln;	state Exp;
branches;
next	1.196;

1.196
date	2005.12.12.01.28.00;	author michaeln;	state Exp;
branches;
next	1.195;

1.195
date	2005.12.04.22.09.44;	author michaeln;	state Exp;
branches;
next	1.194;

1.194
date	2005.12.04.22.04.54;	author michaeln;	state Exp;
branches;
next	1.193;

1.193
date	2005.10.17.00.52.52;	author michaeln;	state Exp;
branches;
next	1.192;

1.192
date	2005.09.01.23.22.38;	author michaeln;	state Exp;
branches;
next	1.191;

1.191
date	2005.09.01.23.21.53;	author michaeln;	state Exp;
branches;
next	1.190;

1.190
date	2005.08.07.23.30.41;	author michaeln;	state Exp;
branches;
next	1.189;

1.189
date	2005.07.25.00.42.16;	author michaeln;	state Exp;
branches;
next	1.188;

1.188
date	2005.07.25.00.25.58;	author michaeln;	state Exp;
branches;
next	1.187;

1.187
date	2005.07.25.00.21.15;	author michaeln;	state Exp;
branches;
next	1.186;

1.186
date	2005.07.25.00.17.49;	author michaeln;	state Exp;
branches;
next	1.185;

1.185
date	2005.07.25.00.17.12;	author michaeln;	state Exp;
branches;
next	1.184;

1.184
date	2005.07.10.23.45.20;	author michaeln;	state Exp;
branches;
next	1.183;

1.183
date	2005.07.04.07.20.23;	author michaeln;	state Exp;
branches;
next	1.182;

1.182
date	2005.07.04.07.03.22;	author michaeln;	state Exp;
branches;
next	1.181;

1.181
date	2005.06.28.04.59.36;	author michaeln;	state Exp;
branches;
next	1.180;

1.180
date	2005.06.28.04.58.21;	author michaeln;	state Exp;
branches;
next	1.179;

1.179
date	2005.06.28.00.34.24;	author michaeln;	state Exp;
branches;
next	1.178;

1.178
date	2005.06.24.07.57.41;	author michaeln;	state Exp;
branches;
next	1.177;

1.177
date	2005.06.24.07.54.38;	author michaeln;	state Exp;
branches;
next	1.176;

1.176
date	2005.06.24.07.20.24;	author michaeln;	state Exp;
branches;
next	1.175;

1.175
date	2005.06.24.07.08.13;	author michaeln;	state Exp;
branches;
next	1.174;

1.174
date	2005.06.06.01.07.09;	author michaeln;	state Exp;
branches;
next	1.173;

1.173
date	2005.06.06.01.01.34;	author michaeln;	state Exp;
branches;
next	1.172;

1.172
date	2005.06.06.00.42.44;	author michaeln;	state Exp;
branches;
next	1.171;

1.171
date	2005.06.06.00.38.02;	author michaeln;	state Exp;
branches;
next	1.170;

1.170
date	2005.05.30.06.31.04;	author michaeln;	state Exp;
branches;
next	1.169;

1.169
date	2005.05.20.00.45.57;	author michaeln;	state Exp;
branches;
next	1.168;

1.168
date	2005.05.19.01.15.47;	author michaeln;	state Exp;
branches;
next	1.167;

1.167
date	2005.05.19.01.13.00;	author michaeln;	state Exp;
branches;
next	1.166;

1.166
date	2005.05.16.01.50.07;	author michaeln;	state Exp;
branches;
next	1.165;

1.165
date	2005.05.13.01.06.23;	author michaeln;	state Exp;
branches;
next	1.164;

1.164
date	2005.05.09.00.26.29;	author michaeln;	state Exp;
branches;
next	1.163;

1.163
date	2005.05.09.00.25.27;	author michaeln;	state Exp;
branches;
next	1.162;

1.162
date	2005.05.06.01.41.33;	author michaeln;	state Exp;
branches;
next	1.161;

1.161
date	2005.05.06.00.00.04;	author michaeln;	state Exp;
branches;
next	1.160;

1.160
date	2005.04.14.00.39.17;	author michaeln;	state Exp;
branches;
next	1.159;

1.159
date	2005.04.14.00.33.57;	author michaeln;	state Exp;
branches;
next	1.158;

1.158
date	2005.04.14.00.11.52;	author michaeln;	state Exp;
branches;
next	1.157;

1.157
date	2005.04.08.00.14.55;	author michaeln;	state Exp;
branches;
next	1.156;

1.156
date	2005.04.04.06.42.29;	author michaeln;	state Exp;
branches;
next	1.155;

1.155
date	2005.04.04.06.16.44;	author michaeln;	state Exp;
branches;
next	1.154;

1.154
date	2005.03.17.23.29.25;	author michaeln;	state Exp;
branches;
next	1.153;

1.153
date	2005.03.14.06.47.02;	author michaeln;	state Exp;
branches;
next	1.152;

1.152
date	2005.03.14.06.44.38;	author michaeln;	state Exp;
branches;
next	1.151;

1.151
date	2005.03.14.06.34.15;	author michaeln;	state Exp;
branches;
next	1.150;

1.150
date	2005.03.14.06.26.02;	author michaeln;	state Exp;
branches;
next	1.149;

1.149
date	2005.02.07.00.24.11;	author michaeln;	state Exp;
branches;
next	1.148;

1.148
date	2005.02.07.00.19.31;	author michaeln;	state Exp;
branches;
next	1.147;

1.147
date	2005.02.07.00.15.38;	author michaeln;	state Exp;
branches;
next	1.146;

1.146
date	2005.02.06.23.48.10;	author michaeln;	state Exp;
branches;
next	1.145;

1.145
date	2004.12.03.00.08.30;	author michaeln;	state Exp;
branches;
next	1.144;

1.144
date	2004.10.08.01.40.18;	author michaeln;	state Exp;
branches;
next	1.143;

1.143
date	2004.10.08.01.31.14;	author michaeln;	state Exp;
branches;
next	1.142;

1.142
date	2004.10.08.00.52.33;	author michaeln;	state Exp;
branches;
next	1.141;

1.141
date	2004.10.08.00.39.48;	author michaeln;	state Exp;
branches;
next	1.140;

1.140
date	2004.07.26.02.04.10;	author michaeln;	state Exp;
branches;
next	1.139;

1.139
date	2004.07.26.01.51.42;	author michaeln;	state Exp;
branches;
next	1.138;

1.138
date	2004.07.26.01.50.45;	author michaeln;	state Exp;
branches;
next	1.137;

1.137
date	2004.07.26.01.39.33;	author michaeln;	state Exp;
branches;
next	1.136;

1.136
date	2004.07.26.01.25.06;	author michaeln;	state Exp;
branches;
next	1.135;

1.135
date	2004.06.28.00.57.16;	author michaeln;	state Exp;
branches;
next	1.134;

1.134
date	2004.06.01.06.33.56;	author michaeln;	state Exp;
branches;
next	1.133;

1.133
date	2004.06.01.06.05.46;	author michaeln;	state Exp;
branches;
next	1.132;

1.132
date	2004.05.11.05.14.17;	author michaeln;	state Exp;
branches;
next	1.131;

1.131
date	2004.05.11.04.58.55;	author michaeln;	state Exp;
branches;
next	1.130;

1.130
date	2004.04.27.01.45.48;	author michaeln;	state Exp;
branches;
next	1.129;

1.129
date	2004.04.27.01.41.41;	author michaeln;	state Exp;
branches;
next	1.128;

1.128
date	2004.04.21.06.57.49;	author michaeln;	state Exp;
branches;
next	1.127;

1.127
date	2004.03.24.06.48.21;	author michaeln;	state Exp;
branches;
next	1.126;

1.126
date	2004.03.24.06.36.57;	author michaeln;	state Exp;
branches;
next	1.125;

1.125
date	2004.03.24.05.53.54;	author michaeln;	state Exp;
branches;
next	1.124;

1.124
date	2004.03.03.23.10.16;	author michaeln;	state Exp;
branches;
next	1.123;

1.123
date	2004.03.02.22.07.03;	author michaeln;	state Exp;
branches;
next	1.122;

1.122
date	2004.02.11.23.02.44;	author michaeln;	state Exp;
branches;
next	1.121;

1.121
date	2004.02.03.22.59.45;	author michaeln;	state Exp;
branches;
next	1.120;

1.120
date	2004.01.18.22.54.57;	author michaeln;	state Exp;
branches;
next	1.119;

1.119
date	2003.12.16.22.57.16;	author michaeln;	state Exp;
branches;
next	1.118;

1.118
date	2003.11.24.00.51.40;	author michaeln;	state Exp;
branches;
next	1.117;

1.117
date	2003.11.20.00.13.38;	author michaeln;	state Exp;
branches;
next	1.116;

1.116
date	2003.11.19.23.49.54;	author michaeln;	state Exp;
branches;
next	1.115;

1.115
date	2003.10.26.23.38.39;	author michaeln;	state Exp;
branches;
next	1.114;

1.114
date	2003.10.23.00.20.21;	author michaeln;	state Exp;
branches;
next	1.113;

1.113
date	2003.10.13.01.07.37;	author michaeln;	state Exp;
branches;
next	1.112;

1.112
date	2003.10.13.01.06.55;	author michaeln;	state Exp;
branches;
next	1.111;

1.111
date	2003.09.22.03.43.15;	author michaeln;	state Exp;
branches;
next	1.110;

1.110
date	2003.09.19.01.26.06;	author michaeln;	state Exp;
branches;
next	1.109;

1.109
date	2003.09.19.01.18.43;	author michaeln;	state Exp;
branches;
next	1.108;

1.108
date	2003.09.01.14.02.03;	author michaeln;	state Exp;
branches;
next	1.107;

1.107
date	2003.08.13.05.49.47;	author michaeln;	state Exp;
branches;
next	1.106;

1.106
date	2003.08.13.05.44.44;	author michaeln;	state Exp;
branches;
next	1.105;

1.105
date	2003.08.04.02.20.04;	author michaeln;	state Exp;
branches;
next	1.104;

1.104
date	2003.07.21.00.29.40;	author michaeln;	state Exp;
branches;
next	1.103;

1.103
date	2003.07.14.01.08.05;	author michaeln;	state Exp;
branches;
next	1.102;

1.102
date	2003.06.23.00.41.26;	author michaeln;	state Exp;
branches;
next	1.101;

1.101
date	2003.06.23.00.40.41;	author michaeln;	state Exp;
branches;
next	1.100;

1.100
date	2003.06.15.23.47.37;	author michaeln;	state Exp;
branches;
next	1.99;

1.99
date	2003.06.09.01.45.46;	author michaeln;	state Exp;
branches;
next	1.98;

1.98
date	2003.05.19.00.21.52;	author michaeln;	state Exp;
branches;
next	1.97;

1.97
date	2003.05.13.01.57.41;	author michaeln;	state Exp;
branches;
next	1.96;

1.96
date	2003.05.13.01.56.52;	author michaeln;	state Exp;
branches;
next	1.95;

1.95
date	2003.05.02.00.06.27;	author michaeln;	state Exp;
branches;
next	1.94;

1.94
date	2003.04.30.04.30.49;	author michaeln;	state Exp;
branches;
next	1.93;

1.93
date	2003.04.30.03.33.47;	author michaeln;	state Exp;
branches;
next	1.92;

1.92
date	2003.04.30.02.05.45;	author michaeln;	state Exp;
branches;
next	1.91;

1.91
date	2003.04.14.04.25.31;	author michaeln;	state Exp;
branches;
next	1.90;

1.90
date	2003.04.07.08.10.12;	author michaeln;	state Exp;
branches;
next	1.89;

1.89
date	2003.04.07.05.32.49;	author michaeln;	state Exp;
branches;
next	1.88;

1.88
date	2003.04.02.01.29.50;	author michaeln;	state Exp;
branches;
next	1.87;

1.87
date	2003.03.19.02.12.07;	author michaeln;	state Exp;
branches;
next	1.86;

1.86
date	2003.03.19.02.10.04;	author michaeln;	state Exp;
branches;
next	1.85;

1.85
date	2003.03.18.23.58.36;	author michaeln;	state Exp;
branches;
next	1.84;

1.84
date	2003.03.18.23.46.45;	author michaeln;	state Exp;
branches;
next	1.83;

1.83
date	2003.03.18.23.21.05;	author michaeln;	state Exp;
branches;
next	1.82;

1.82
date	2003.03.13.22.17.20;	author michaeln;	state Exp;
branches;
next	1.81;

1.81
date	2003.03.09.21.15.18;	author michaeln;	state Exp;
branches;
next	1.80;

1.80
date	2003.02.24.01.37.54;	author michaeln;	state Exp;
branches;
next	1.79;

1.79
date	2003.02.10.04.01.33;	author michaeln;	state Exp;
branches;
next	1.78;

1.78
date	2003.02.02.23.24.09;	author mn200;	state Exp;
branches;
next	1.77;

1.77
date	2003.01.19.23.32.21;	author mn200;	state Exp;
branches;
next	1.76;

1.76
date	2003.01.13.01.34.42;	author mn200;	state Exp;
branches;
next	1.75;

1.75
date	2002.12.29.07.05.55;	author mn200;	state Exp;
branches;
next	1.74;

1.74
date	2002.12.08.11.46.33;	author mn200;	state Exp;
branches;
next	1.73;

1.73
date	2002.11.25.13.24.32;	author mn200;	state Exp;
branches;
next	1.72;

1.72
date	2002.11.18.10.49.33;	author mn200;	state Exp;
branches;
next	1.71;

1.71
date	2002.11.11.11.26.21;	author mn200;	state Exp;
branches;
next	1.70;

1.70
date	2002.11.04.11.18.06;	author mn200;	state Exp;
branches;
next	1.69;

1.69
date	2002.10.25.10.08.07;	author mn200;	state Exp;
branches;
next	1.68;

1.68
date	2002.10.25.09.40.41;	author mn200;	state Exp;
branches;
next	1.67;

1.67
date	2002.10.13.16.00.03;	author mn200;	state Exp;
branches;
next	1.66;

1.66
date	2002.10.11.16.32.07;	author mn200;	state Exp;
branches;
next	1.65;

1.65
date	2002.09.20.10.18.14;	author mn200;	state Exp;
branches;
next	1.64;

1.64
date	2002.09.20.10.07.35;	author mn200;	state Exp;
branches;
next	1.63;

1.63
date	2002.09.20.09.53.20;	author mn200;	state Exp;
branches;
next	1.62;

1.62
date	2002.08.29.10.13.58;	author mn200;	state Exp;
branches;
next	1.61;

1.61
date	2002.08.29.10.08.54;	author mn200;	state Exp;
branches;
next	1.60;

1.60
date	2002.08.20.11.02.09;	author mn200;	state Exp;
branches;
next	1.59;

1.59
date	2002.08.18.20.52.04;	author mn200;	state Exp;
branches;
next	1.58;

1.58
date	2002.07.23.09.34.03;	author mn200;	state Exp;
branches;
next	1.57;

1.57
date	2002.07.23.09.30.52;	author mn200;	state Exp;
branches;
next	1.56;

1.56
date	2002.07.12.08.58.14;	author mn200;	state Exp;
branches;
next	1.55;

1.55
date	2002.07.03.09.17.22;	author mn200;	state Exp;
branches;
next	1.54;

1.54
date	2002.06.14.08.52.47;	author mn200;	state Exp;
branches;
next	1.53;

1.53
date	2002.06.14.08.27.33;	author mn200;	state Exp;
branches;
next	1.52;

1.52
date	2002.06.07.10.03.51;	author mn200;	state Exp;
branches;
next	1.51;

1.51
date	2002.05.24.11.15.24;	author mn200;	state Exp;
branches;
next	1.50;

1.50
date	2002.05.17.09.09.06;	author mn200;	state Exp;
branches;
next	1.49;

1.49
date	2002.05.07.09.38.35;	author mn200;	state Exp;
branches;
next	1.48;

1.48
date	2002.04.22.16.30.59;	author mn200;	state Exp;
branches;
next	1.47;

1.47
date	2002.04.22.16.29.30;	author mn200;	state Exp;
branches;
next	1.46;

1.46
date	2002.04.04.09.47.13;	author mn200;	state Exp;
branches;
next	1.45;

1.45
date	2002.04.04.08.56.06;	author mn200;	state Exp;
branches;
next	1.44;

1.44
date	2002.03.25.11.57.50;	author mn200;	state Exp;
branches;
next	1.43;

1.43
date	2002.03.19.11.07.33;	author mn200;	state Exp;
branches;
next	1.42;

1.42
date	2002.03.12.11.34.08;	author mn200;	state Exp;
branches;
next	1.41;

1.41
date	2002.03.06.09.36.20;	author mn200;	state Exp;
branches;
next	1.40;

1.40
date	2002.02.25.12.53.17;	author mn200;	state Exp;
branches;
next	1.39;

1.39
date	2002.02.19.10.55.54;	author mn200;	state Exp;
branches;
next	1.38;

1.38
date	2002.02.19.10.53.39;	author mn200;	state Exp;
branches;
next	1.37;

1.37
date	2002.02.15.10.55.35;	author mn200;	state Exp;
branches;
next	1.36;

1.36
date	2002.02.11.10.08.22;	author mn200;	state Exp;
branches;
next	1.35;

1.35
date	2002.01.09.10.43.08;	author mn200;	state Exp;
branches;
next	1.34;

1.34
date	2001.12.02.21.44.59;	author mn200;	state Exp;
branches;
next	1.33;

1.33
date	2001.10.16.09.33.38;	author mn200;	state Exp;
branches;
next	1.32;

1.32
date	2001.10.01.11.56.49;	author mn200;	state Exp;
branches;
next	1.31;

1.31
date	2001.09.14.10.41.21;	author mn200;	state Exp;
branches;
next	1.30;

1.30
date	2001.09.14.10.39.47;	author mn200;	state Exp;
branches;
next	1.29;

1.29
date	2001.09.07.09.02.51;	author mn200;	state Exp;
branches;
next	1.28;

1.28
date	2001.08.31.08.47.11;	author mn200;	state Exp;
branches;
next	1.27;

1.27
date	2001.08.16.08.15.24;	author mn200;	state Exp;
branches;
next	1.26;

1.26
date	2001.08.16.08.11.07;	author mn200;	state Exp;
branches;
next	1.25;

1.25
date	2001.08.13.11.00.38;	author mn200;	state Exp;
branches;
next	1.24;

1.24
date	2001.07.29.15.44.33;	author mn200;	state Exp;
branches;
next	1.23;

1.23
date	2001.07.27.09.25.09;	author mn200;	state Exp;
branches;
next	1.22;

1.22
date	2001.07.27.09.23.35;	author mn200;	state Exp;
branches;
next	1.21;

1.21
date	2001.07.22.17.39.40;	author mn200;	state Exp;
branches;
next	1.20;

1.20
date	2001.07.22.17.39.05;	author mn200;	state Exp;
branches;
next	1.19;

1.19
date	2001.07.22.17.33.33;	author mn200;	state Exp;
branches;
next	1.18;

1.18
date	2001.07.15.17.26.53;	author mn200;	state Exp;
branches;
next	1.17;

1.17
date	2001.07.15.17.23.36;	author mn200;	state Exp;
branches;
next	1.16;

1.16
date	2001.07.15.17.07.47;	author mn200;	state Exp;
branches;
next	1.15;

1.15
date	2001.07.15.17.06.14;	author mn200;	state Exp;
branches;
next	1.14;

1.14
date	2001.07.06.08.40.07;	author mn200;	state Exp;
branches;
next	1.13;

1.13
date	2001.06.29.09.30.05;	author mn200;	state Exp;
branches;
next	1.12;

1.12
date	2001.06.15.09.49.33;	author mn200;	state Exp;
branches;
next	1.11;

1.11
date	2001.06.15.09.34.23;	author mn200;	state Exp;
branches;
next	1.10;

1.10
date	2001.06.15.09.14.43;	author mn200;	state Exp;
branches;
next	1.9;

1.9
date	2001.06.15.08.07.23;	author mn200;	state Exp;
branches;
next	1.8;

1.8
date	2001.06.08.08.51.02;	author mn200;	state Exp;
branches;
next	1.7;

1.7
date	2001.06.08.08.49.03;	author mn200;	state Exp;
branches;
next	1.6;

1.6
date	2001.06.05.08.32.21;	author mn200;	state Exp;
branches;
next	1.5;

1.5
date	2001.06.05.08.31.17;	author mn200;	state Exp;
branches;
next	1.4;

1.4
date	2001.05.22.08.32.01;	author mn200;	state Exp;
branches;
next	1.3;

1.3
date	2001.05.22.08.21.51;	author mn200;	state Exp;
branches;
next	1.2;

1.2
date	2001.05.22.08.14.28;	author mn200;	state Exp;
branches;
next	1.1;

1.1
date	2001.05.18.12.21.20;	author mn200;	state Exp;
branches;
next	;


desc
@Full Logical ruleset - will maintain this as long as I am Rulekeepor.
@


1.1587
log
@effects of proposal 7160
@
text
@THE FULL LOGICAL RULESET

Last proposal with recorded effect on this ruleset: 7160
Last change to this ruleset: by Proposal 7160

Last updated: 5 February 2012

Highest Rule ID number ever assigned: 2359

----------------------------------------------------------------------

Statistics

Current total number of rules: 101

Power distribution:
       1 with Power=4
       1 with Power=3.2
      38 with Power=3
      25 with Power=2
       8 with Power=1.7
       3 with Power=1.5
       1 with Power=1.1
      24 with Power=1

----------------------------------------------------------------------

Index of Categories

      * The Game of Agora
      * Rules
      * Players
      * Economy
      * Definitions
      * Offices
      * Agoran Decisions
      * Proposals
      * Adjudication
      * Patent Titles and Degrees
      * Trophies

----------------------------------------------------------------------

Index of Rules

      * The Game of Agora
      Rule 2105: The Map of Agora
      Rule  101: The Rights of Agorans
      Rule 2125: Regulation Regulations
      Rule 1586: Definition and Continuity of Entities
      Rule 1688: Power
      Rule 2140: Power Controls Mutability
      Rule  104: First Speaker
      Rule 2326: The President
      Rule 2348: Presidential Power
      Rule 2344: Anarchy
      Rule  103: The Speaker
      Rule 2339: Intention
      Rule 2359: The Power Of Agora
      Rule 2351: Agora, Adult
      Rule 2357: Wisdom of the Elders
      Rule 2358: Win by Paradox

      * 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 2340: Notability
      Rule 1051: The Rulekeepor
      Rule 2327: Read the Ruleset Week

      * Players
      Rule  869: How to Join and Leave Agora
      Rule 2170: Who Am I?
      Rule 2150: Personhood
      Rule 2328: Public Agreements
      Rule 2139: The Registrar
      Rule 1789: Cantus Cygneus
      Rule 2130: Activity

      * Economy
      Rule 2166: Assets
      Rule 2343: Victory Conditions
      Rule 2337: Promises
      Rule 2338: Cashing Promises
      Rule 2356: Naughtiness
      Rule 2354: Costs

      * Definitions
      Rule  754: Definition Definitions
      Rule 2152: Mother, May I?
      Rule 1023: Common Definitions
      Rule 2347: Speed
      Rule 1769: Holidays
      Rule 2329: Festival Days
      Rule 2146: Indices
      Rule 2162: Switches
      Rule  478: Fora
      Rule 1728: Dependent Actions
      Rule 2288: Induction
      Rule 2124: Agoran Satisfaction
      Rule 2333: Contests
      Rule 2334: Timers

      * Offices
      Rule 1006: Offices
      Rule 2143: Official Reports and Duties
      Rule 2160: Deputisation
      Rule 2154: Election Procedure
      Rule 2276: Assumption of Vacant Offices
      Rule 2138: The Interstellar Associate Director of Personnel
      Rule 2352: The Ambassador
      Rule 1551: Ratification
      Rule 2202: Ratification Without Objection
      Rule 2201: Self-Ratification

      * Agoran Decisions
      Rule  693: Agoran Decisions
      Rule  107: Initiating Agoran Decisions
      Rule  683: Voting on Agoran Decisions
      Rule 2127: Conditional Votes
      Rule 2280: Implicit 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  106: Adopting Proposals
      Rule 1607: Distribution
      Rule 1950: Decisions with Adoption Indices
      Rule 2137: The Assessor
      Rule 1698: Agora Is A Nomic

      * Adjudication
      Rule  991: Judicial Cases Generally
      Rule 2158: Judges
      Rule  591: Inquiry Cases
      Rule 1504: Criminal Cases
      Rule 2277: Appeals of Criminal Cases
      Rule 2205: Judicial Arguments and Evidence
      Rule 2157: Judicial Panels
      Rule 2341: Judgements by Judicial Panels
      Rule 2318: Motions to Reconsider
      Rule  911: Appeal Cases
      Rule 2342: Judicial Appeals Panels
      Rule 2175: Judicial Retraction and Excess
      Rule 1868: Judge Assignment Generally
      Rule 1871: The Standing Court
      Rule 2204: Linked Assignments
      Rule 2164: Judicial Self-Recusal and Case Transfer
      Rule 2212: Judicial Declarations

      * Patent Titles and Degrees
      Rule  649: Patent Titles
      Rule 1367: Degrees
      Rule 2231: Order of the Hero of Agora Nomic

      * Trophies
      Rule 1727: Happy Birthday
      Rule 2355: For It Was Not To B
      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.  History entries are required by Rule 1681; an ellipsis
(...) indicates that the history is incomplete.

Rule nnnn/r (Power=p)
Title of Rule

      Text of rule.

History:
List of changes to the rule.

Annotations in square brackets are unofficial and have no legal force.
They are added at the Rulekeepor's discrection, except for
annotations starting with a CFJ number, which are mandated by Rule
2340.  A judicial case is Notable if and only if it has such an
annotation in this document.

----------------------------------------------------------------------

======================================================================
The Game of Agora
      A category concerning this nomic generally, constitutional
      matters, and relationships between the most fundamental nomic
      entities.
----------------------------------------------------------------------

Rule 2105/4 (Power=1)
The Map of Agora

                               ____  _        /|
                    DARWIN ->  \_  |/ |      / \
                              __/    /      |  |
            <- DSV          /      /        |  \
                        _   \      \_       |   \
                  MORNINGTON CRESCENT ->    /    |  <- GOETHE BARRIER
                 _ _/       |         \_/\_/     \     REEF
                / \\ <- SHARK BAY      |         |
               /            |          |          \ <- TOWNSVILLE
            ___/            |          |           \_
         __/                |          |  .___o  )   |
        /                   |          | ~~vv ===~~~ <-OSCAR'S MIRE
       /           O <- SHERLOCK NESS  |             |/\
      |                     |          |               |_
      |                     |          |  EMERALD ->     \
      \                     |__________=_____,             \ BRISBANE
       /                    |                |             | <-'
       \      O <- LT. ANNE MOORE            |        __  _\
        \                   |                |_______/  \/ |  LORD
         |                __/\      <- TARACOOLA          /   HOWE ->
         \  PERTH      __/    \_             /           /
          | <-'  _  __/         |   /| IVANHOE ->       | <-.
          /    _/ \/             \ / /       |         /  WOLLONGONG
         |_   /     <- ESPERANTO  v /__     |_        / <- CANBERRA
           \_/                         \    | \_    _|
                  __   __              |    |   \__/           \_
                 __ \ / __              \___=_  ___|            \_
                /  \ | /  \     MANUBOURNE -> \/      NEW C.LAND \}
                    \|/                                           \)
               _,.---v---._                 /\__                   )`-']
      /\__/\  /            \                |   |  COPPRO STRAIGHT(    !
      \_  _/ /              \                |  /      MICHAELTON->)  /
        \ \_|           @@ __|                \_/ <- HOBART    |^\  (_/
         \                \_                                 (  |
          \     ,__/       /                                 /  *
        ~~~`~~~~~~~~~~~~~~/~~~~                  BREE_523->/~   /
                                            MURPHENDELL--> #   /
                                                         /   |BOBCHURCH
                                             PAVRITTON->/  _|
                                                       {__/
                                                     /  @@
                                    WOOBLEING HEIGHTS

History:
Created by Proposal 4735 (Maud), 5 May 2005
Amended(1) by Proposal 4807 (Sherlock), 15 June 2005
Amended(2) by Proposal 4866 (Goethe), 27 August 2006
Amended(3) by Proposal 4946 (Zefram), 3 May 2007
Amended(4) by Proposal 6581 (G.), 28 November 2009

----------------------------------------------------------------------

Rule 101/13 (Power=3)
The Rights of Agorans

      WHEREAS Agora, since its inception, has functioned not only as a
      game but as a society, and WHEREAS a society, to function, must
      balance its Rules with the natural rights of its participants,
      BE IT HEREBY PROCLAIMED that no interpretation of Agoran law or
      binding agreement may substantially limit or remove a person's
      rights as defined by this Rule, except through the explicit and
      legal amendment of this Rule.  This rule takes precedence over
      any rule which would allow or mandate restrictions of the rights
      contained herein.

         i. Every person has the right, though not necessarily the
            ability, to perform actions that are not prohibited or
            regulated by the Rules, with the sole exception of
            changing the Rules, which is permitted only when the Rules
            explicitly or implicitly permit it.

        ii. Every person has the right to initiate a formal process to
            resolve matters of controversy, in the reasonable
            expectation that the controversy will thereby be resolved.
            Every person has the right to cause formal reconsideration
            of any judicial determination that e should be punished.

       iii. Every person has the right to refuse to become party to
            a binding agreement.  The absence of a person's explicit,
            willful consent shall be considered a refusal.

        iv. Every person has the right to not be considered bound by
            an agreement, or an amendment to an agreement, or a Rule
            Change, which e has not had the reasonable opportunity to
            review.  For the purpose of protecting this right, a rule
            change which would otherwise take effect without its
            substance being subject to general player review through a
            reasonably public process is wholly prevented from taking
            effect.

         v. Every player has the right of participation in the fora.

        vi. Every person has the right to not be penalized more than
            once for any single action or inaction.  However, this
            right is not violated by replacing part or all of a
            penalty with a different but comparable penalty, e.g. when
            the rules governing penalties are amended.

       vii. Every player has the right to deregister; e may continue
            to accrue obligations and penalties after deregistration
            but, if e wishes to ignore the game, such penalties shall
            not unduly harass em.

      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".]

[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 1856 (called 29 December 2007): The requirement that "no
interpretation of Agoran law may abridge ... a person's defined
rights" means that it must be feasible, given the practical limits of
Agoran evidence-gathering, to remain reasonably sure that a person's
defined rights are not being limited.]

[CFJ 1768 (called 22 October 2007): The right of participation in the
fora is the right to participate in them for their intended purposes,
and is not necessarily infringed by regulations regarding the manner
and type of participation.]

[CFJ 1738 (called 29 August 2007): An obligation on a player to not
publish statements that e believes are true would conflict with the
right of participation in the fora.]

[CFJ 1753 (called 28 September 2007): The right to cease playing
applies only to those who have the rule-defined status of "player",
not to those who play the game in the broader sense without having
that official status.]

[CFJs 1911-1914 (called 18 March 2008): Physical realities supersede
the Rules by default.]

[CFJ 2220 (called 11 October 2008): Consent to join a binding
agreement may be an effect of another action, such as joining a
foreign nomic, as long as the action is triggered by free will and the
actor is reasonably aware of the effect.]

[CFJ 2246 (called 30 October 2008): Joining a contract does not imply
consent to be acted on behalf of simply because the contract might be
amended in the future to allow it.]

[CFJ 2264 (called 11 November 2008): The right to refuse to become
party to an agreement does not apply to amendments to existing
agreements.]

[CFJ 2361 (called 26 January 2009): The withholding of a reward for
doing something may or may not constitute a penalty for not doing it,
depending on the circumstances.]

[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 2410 (called 11 March 2009): Consent to join a binding agreement
may be given privately.]

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

----------------------------------------------------------------------

Rule 2125/7 (Power=3)
Regulation Regulations

      A regulated action is an action satisfying any of the following:

      a) It is IMPOSSIBLE.

      b) It is ILLEGAL.

      c) The rules explicitly state that it CAN be performed while
         certain conditions are satisfied.  Such an action CANNOT be
         performed except as allowed by the rules.  In particular, if
         the action in question is publishing a type of document, then
         a public message is not that type of document (even if it is
         labeled as such) except as allowed by the rules.

      d) The rules explicitly state that it MAY be performed while
         certain conditions are satisfied.  Except as allowed by the
         rules, performing such an action is the Class-N Crime of
         Restricted Behavior, where N is the maximum power of the
         rules explicitly allowing it (rounded up as needed to become
         a valid Class of Crime).

      e) It would, as part of its effect, modify information for which
         some player is required to be a recordkeepor.  Such an action
         CANNOT modify that information except as allowed by the
         rules.

      f) A judicial finding has determined that it is regulated, and
         has not been superseded by subsequent legislation.

      A person SHOULD NOT violate a rule.

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

----------------------------------------------------------------------

Rule 1586/8 (Power=2)
Definition and Continuity of Entities

      If multiple rules attempt to define an entity with the same
      name, then they refer to the same entity.  A rule-defined
      entity's name CANNOT be changed to be the same as another
      rule-defined entity's name.

      A rule referring to an entity by name refers to the entity that
      had that name when the rule first came to include that
      reference, even if the entity's name has since changed.

      If the rules are amended such that they no longer define an
      entity, then that entity and its attributes cease to exist.

      If the rules are amended such that they define an entity both
      before and after the amendment, but with different attributes,
      then that entity and its attributes continue to exist to
      whatever extent is possible under the new definitions.

[CFJ 1807 (called 25 November 2007): Rule-defined entities include
pending timed events, which can therefore occur under modified rules
even if the events that originally triggered them would not trigger
them under the new rules.]

[CFJ 1922 (called 4 April 2008): Without legislation to the contrary,
documents attempting to define an entity with the same name define
distinct entities.]

History:
Created by Proposal 2481, Feb. 16 1996
Amended(1) by Proposal 2795 (Andre), Jan. 30 1997, substantial
Amended(2) by Proposal 3999 (harvel), May 2 2000
Power changed from 1 to 2 by Proposal 3999 (harvel), May 2 2000
Amended(3) by Proposal 5077 (Murphy), 18 July 2007
Amended(4) by Proposal 5723 (Murphy), 7 October 2008
Amended(5) by Proposal 5836 (Murphy), 12 October 2008
Amended(6) by cleaning (comex), 26 January 2009
Amended(7) by Proposal 6650 (coppro), 10 March 2010
Amended(8) by Proposal 6981 (Murphy, omd), 10 April 2011

----------------------------------------------------------------------

Rule 1688/6 (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.

      A Rule that secures a change, action, or value (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

----------------------------------------------------------------------

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.

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 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

----------------------------------------------------------------------

Rule 2326/2 (Power=2)
The President

      The President is a second-class person.  Causing the President
      to act is secured.

      A first-class Player CAN cause the President to take actions
      Without Objection, or with Agoran Consent.

      Should the President incur obligations under the Rules, then the
      Speaker SHALL act to satisfy these obligations.

History:
Created by Proposal 6961 (G.), 3 March 2011
Amended(1) by Proposal 7029 (Walker), 16 May 2011
Amended(2) by Proposal 7030 (Walker), 16 May 2011

----------------------------------------------------------------------

Rule 2348/0 (Power=1)
Presidential Power

      The President's power is equal to the power of this Rule.

History:
Created by Proposal 7067 (G.), 16 June 2011

----------------------------------------------------------------------

Rule 2344/0 (Power=1)
Anarchy

      If a player causes the President to cease to be a player, then
      that player satisfies the Victory Condition of Anarchy.

      If the President is ever not a player, any person may register
      em by announcement.

History:
Created by Proposal 7040 (scshunt), 16 May 2011

----------------------------------------------------------------------

Rule 103/10 (Power=2)
The Speaker

      The Speaker is an imposed office and a figurehead of Agora. The
      Speaker is a person who has proven themselves to be worthy of
      the title, and for a time can direct Agoran government affairs.

      The Speaker is the single player who holds the most Postulated
      Offices, or if there is no such player, the player who was most
      recently Speaker.

      The Speaker CAN, by announcement, cause the President to take
      actions that are not otherwise IMPOSSIBLE, except for
      deregistration.  Causing the President to perform ILLEGAL
      actions in this manner is the Class-6 crime of Misleading the
      Leader.

[Cross-references (10 July 2009): the Speaker's duties are:
  * figurehead (Rule 103)
  * bestow favors (Rule 103)]

History:
Initial Immutable Rule 103, Jun. 30 1993
Mutated from MI=Unanimity to MI=3 by Proposal 1481, Mar. 15 1995
Amended(1) by Proposal 3829 (Steve), Feb. 8 1999
Retitled by Proposal 4944 (Zefram), 3 May 2007
Amended(2) by Proposal 4944 (Zefram), 3 May 2007
Retitled by Proposal 5257 (AFO), 27 October 2007
Amended(3) by Proposal 5257 (AFO), 27 October 2007
Amended(4) by Proposal 5407 (root), 22 January 2008
Power changed from 3 to 1 by Proposal 5947 (ais523), 15 November 2008
Amended(5) by Proposal 6026 (Murphy), 22 December 2008
Amended(6) by Proposal 6490 (coppro), 18 September 2009
Power changed from 1 to 2 by Proposal 6821 (G., ais523), 4 September
  2010
Amended(7) by Proposal 6821 (G., ais523), 4 September 2010
Retitled by Proposal 6961 (G.), 3 March 2011
Amended(8) by Proposal 6961 (G.), 3 March 2011
Amended(9) by Proposal 7006 (Walker), 20 April 2011
Amended(10) by Proposal 7084 (omd), 23 July 2011

----------------------------------------------------------------------

Rule 2339/1 (Power=1)
Intention

      Agora Nomic is intended to be a person.

      When Agora Nomic is a person, any player CAN cause em to take
      actions without objection or with Agoran Consent.

History:
Created by Proposal 7021 (Walker), 5 May 2011
Amended(1) by Proposal 7112 (Walker), 20 August 2011

----------------------------------------------------------------------

Rule 2359/0 (Power=1)
The Power Of Agora

      If Agora is a person, Agora has power equal to the power of this
      rule.

History:
Created by Proposal 7160 (441344), 5 February 2012

----------------------------------------------------------------------

Rule 2351/1 (Power=3)
Agora, Adult

      Agora can make its own decisions. If, at any time, Agora wishes
      to counteract a decision, then that decision, rules to the
      contrary notwithstanding, has no effect. The game of Agora, but
      not any other player of it, can make arbitrary changes to the
      gamestate.

History:
Created by Proposal 7095 (Yally), 23 July 2011
Amended(1) by Proposal 7128 (scshunt), 6 November 2011

----------------------------------------------------------------------

Rule 2357/0 (Power=2)
Wisdom of the Elders

      An Elder is a player who has been registered continuously for at
      least 32 days, and also registered for at least 128 days total
      (not necessarily contiguously).

      An Elder can declare a Gerontocracy with 3 Elder support, unless
      a Gerontocracy was declared within the preceding 28 days.

      During the 32 days after a Gerontocracy is declared:
        * Any Elder CAN flip any non-Elder to supine by announcement;
        * Any Elder CAN flip any office held by a non-Elder to Assumed
          by announcement;
        * Non-Elders CANNOT Assume offices, even if other rules say
          they can;
        * Any Elder, with 4 Elder Support, CAN set the Adoption Index
          of any Agoran Decision with an Adoption Index to 4294967296.

History:
Created by Proposal 7134 (ais523), 6 November 2011

----------------------------------------------------------------------

Rule 2358/0 (Power=1)
Win by Paradox

      A turtle is an inquiry case on the possibility or legality of a
      rule-defined action (actual or hypothetical, but not arising
      from that case itself, and not occurring after the initiation of
      that case) which has the judgement UNDECIDABLE.

      When a turtle has continuously been a turtle for one week, its
      initiator satisfies the Victory Condition of Paradox.

History:
Created by Proposal 7138 (omd), 19 November 2011

----------------------------------------------------------------------

======================================================================
Rules
      A category concerning the rules of the game, including the
      processes of changing the rules.
----------------------------------------------------------------------

Rule 2141/6 (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.  In
      particular, a rule may define in-game entities and regulate
      their behaviour, make instantaneous changes to the state of
      in-game entities, prescribe or proscribe certain player
      behaviour, modify the rules or the application thereof, or do
      any of these things in a conditional manner.

      Every rule has power between one and four 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 as soon as possible.

      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

----------------------------------------------------------------------

Rule 217/6 (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.

[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

----------------------------------------------------------------------

Rule 1030/9 (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,

      - The Rule with the lower ID number 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

----------------------------------------------------------------------

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/5 (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, 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) amend the text of a rule.

      (d) retitle a rule.

      (e) 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.

      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

----------------------------------------------------------------------

Rule 1681/18 (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

----------------------------------------------------------------------

Rule 2340/1 (Power=1)
Notability

      Notability is a judicial case switch with values Incidental
      (default) and Notable, tracked by the Rulekeepor in eir monthly
      report. A player CAN, with two support, make a case Notable. A
      player CAN, without two objections, make a case Incidental.

      The Rulekeepor SHALL annotate the FLR to draw attention to
      Notable cases, specifying the ID number of the case and
      including a brief description of the precedent it sets.

      The players involved in making a case Notable SHOULD suggest
      where the FLR should be so annotated.

History:
Created by Proposal 7022 (Walker, Murphy, omd), 5 May 2011
Amended(1) by Proposal 7064 (Murphy), 16 June 2011

----------------------------------------------------------------------

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.

[Cross-references (2 August 2007): the Rulekeepor's duties are:
  * manage ID numbers of rules (Rule 2141)
  * assign title to rule (Rule 2141)
  * report ruleset in two formats (Rule 1051)
  * manage Logical Ruleset categories (Rule 1681)
  * annotate the Full Logical Ruleset (Rule 1681)
  * maintain historical rule annotations (Rule 1681)]

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

----------------------------------------------------------------------

======================================================================
Players
      A category concerning players, including the processes of
      becoming and ceasing to be players, and game-relevant aspects of
      players.
----------------------------------------------------------------------

Rule 869/32 (Power=2)
How to Join and Leave Agora

      Citizenship is an entity switch with values Unregistered
      (default) and Registered, tracked by the registrar.  A player is
      an entity whose citizenship is Registered.  Changes to
      citizenship are secured.

      The verb "to be registered" means to become a player (i.e., to
      have one's citizenship changed from Unregistered to Registered),
      and the verb "to be deregistered" means to cease to be a player
      (i.e., to have one's citizenship changed from Registered to
      Unregistered).  Where the verb "to register" or "to deregister"
      is used without an explicit direct object, the action is
      implicitly reflexive.

      A first-class 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 second-class person CAN register with Agoran Consent.

      A non-person CANNOT be registered (or created in a Registered
      state), rules to the contrary notwithstanding.

      A player CAN deregister by announcement.  A person CANNOT
      register within thirty days after being deregistered, unless
      rules define the method of deregistration as passive.

      A player who is not a person and has never been a first-class
      person CAN be deregistered by any player by announcement.

[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
Amended(4) by Proposal 2599, May 11 1996
Amended(5) by Proposal 2718, Oct. 23 1996
Amended(6) by Proposal 3475 (Murphy), May 11 1997, substantial
Amended(7) by Proposal 3740 (Repeal-O-Matic), May 8 1998
Amended(8) by Proposal 3923 (harvel), Oct. 10 1999
Amended(9) by Proposal 4011 (Wes), Jun. 1 2000
Amended(10) by Proposal 4147 (Wes), 13 May 2001
Amended(11) by Proposal 4155 (harvel), 18 May 2001
Amended(12) by Proposal 4430 (Cecilius), 16 January 2003
Amended(13) by Proposal 4451 (Cecilius), 22 February 2003
Amended(14) by Proposal 4523 (Murphy), 28 August 2003
Amended(15) by Proposal 4693 (Maud), 18 April 2005
Amended(16) by Proposal 4802 (Maud), 15 June 2005
Amended(17) by Proposal 4833 (Maud), 6 August 2005
Amended(18) by Proposal 4989 (Zefram), 6 June 2007
Amended(19) by Proposal 5007 (Zefram), 18 June 2007
Amended(20) by Proposal 5011 (Zefram), 24 June 2007
Amended(21) by Proposal 5086 (Zefram), 1 August 2007
Amended(22) by Proposal 5111 (Murphy), 2 August 2007
Amended(23) by Proposal 5117 (Zefram; disi.), 8 August 2007
Amended(24) by Proposal 5156 (Zefram), 29 August 2007
Amended(25) by Proposal 5271 (Murphy), 7 November 2007
Power changed from 1 to 2 by Proposal 5728 (ihope), 7 October 2008
Amended(26) by Proposal 5728 (ihope), 7 October 2008
Amended(27) by Proposal 5973 (woggle), 25 November 2008
Amended(28) by Proposal 6099 (Pavitra), 22 February 2009
Amended(29) by Proposal 6349 (Pavitra), 17 June 2009
Amended(30) by Proposal 6382 (Murphy), 3 July 2009
Amended(31) by Proposal 6620 (Murphy; disi.), 4 February 2010
Amended(32) by Proposal 6974 (Murphy), 30 March 2011

----------------------------------------------------------------------

Rule 2170/6 (Power=3)
Who Am I?

      Rules regarding persons pertain to those persons directly, not
      to rule-defined avatars or other entities representing those
      persons within Agora.

      A person SHALL NOT make a public statement intended to mislead
      others as to the identity of its publisher.

      A player SHALL NOT select a confusing nickname, including but
      not limited to a name that has generally been used to refer to
      another entity within the past three months.

      A public message's (possibly implicit) claim as to the identity
      of its publisher is self-ratifying, provided that the claim is
      neither ambiguous nor self-contradictory, and no challenge of
      identity pertaining to the claimed publisher has been issued
      within one month before its publication.  Upon a judicial
      finding that the claimed publisher of one or more messages
      (hereafter the Sock Puppet) was not a person, if any of those
      claims have already self-ratified, then the judge SHALL as soon
      as possible publish a judicial declaration that the Sock Puppet
      was a person during one or more time periods, and SHOULD ensure
      that it corresponds to general belief prior to that finding.

      The Executor of a public message is the first-class person who
      sends it, or who most directly and immediately causes it to be
      sent.  (Upon a judicial finding that the Executor of a public
      message cannot otherwise be determined within reasonable effort,
      the judge SHALL as soon as possible publish a judicial
      declaration specifying the identity of that message's Executor.)
      The executor of an action performed by announcement is the
      executor of the announcement.

[CFJs 2184-2192 (called 24 September 2008): A message signature
containing a unique nickname is not a self-ratifying claim that its
publisher is distinct from other generally-recognized persons.]

[CFJ 2300 (called 5 December 2008): The Executor of a public message
is not necessarily a person who took action at the time the message
was sent.]

[CFJ 2325 (called 5 January 2009): Only the selection of a nickname
for the purposes of Agora is relevant to this rule.]

History:
Created by Proposal 5212 (Murphy), 8 September 2007
Amended(1) by Proposal 5445 (Goethe, Murphy), 21 February 2008
Amended(2) by Proposal 5671 (Murphy, Pavrita), 12 August 2008
Amended(3) by Proposal 5716 (Murphy), 7 October 2008
Amended(4) by Proposal 5717 (Murphy), 7 October 2008
Amended(5) by Proposal 5741 (Murphy), 16 October 2008
Amended(6) by Proposal 6571 (ais523), 28 November 2009

----------------------------------------------------------------------

Rule 2150/6 (Power=3)
Personhood

      A person is an entity defined as such by rules with power of at
      least 2.  A person CAN generally be the subject of rights and
      obligations under the rules.

      Any biological organism that is generally capable of
      communicating by email in English (including via a translation
      service) is a person.

      A first-class person is a person of a biological nature.  All
      other persons are second-class.

      The basis of a first-class person is the singleton set
      consisting of that person.

[CFJ 1700 (called 10 July 2007): The requirement of capability to
communicate by email can be satisfied even if the players of Agora do
not know the organism's email address.]

[CFJ 1685 (called 31 May 2007): Being in a mindless job (e.g.,
keyboard, stenographer, spokesman) may create a rebuttable presumption
against personhood and against one having spoken on one's own behalf.]

[CFJ 2398 (called 3 March 2009): Young children may or may not be
considered persons, depending on their communication skills.]

History:
Created by Proposal 5007 (Zefram), 18 June 2007
Amended(1) by Proposal 5061 (Zefram), 9 July 2007
Amended(2) by Proposal 5303 (root), 24 November 2007
Amended(3) by Proposal 5476 (Murphy; disi.), 27 March 2008
Power changed from 2 to 3 by Proposal 5509 (root; disi.), 28 May 2008
Amended(4) by Proposal 5760 (comex), 16 October 2008
Amended(5) by Proposal 5790 (Murphy), 22 October 2008
Amended(6) by Proposal 6022 (Murphy), 22 December 2008

----------------------------------------------------------------------

Rule 2328/0 (Power=2)
Public Agreements

      An agreement between two or more players is a person if all of
      the following are true:

        a) It clearly indicates that it is intended to be a person.
        b) Its text has been published.

History:
Created by Proposal 6976 (Murphy, MRW and Associates), 30 March 2011

----------------------------------------------------------------------

Rule 2139/4 (Power=2)
The Registrar

      The Registrar is an office; its holder is responsible for
      keeping track of players.

      The Registrar's report includes:

      a) A list of all players, including information sufficient to
         identify and contact each player.
      b) The date on which each player most recently became a player.
      c) The Activity of each player, and when each Inactive player
         became Inactive.
      d) For each former player for which the information is
         reasonably available, the dates on which e registered and
         deregistered.

      The portion of a public message purporting to be a Registrar's
      report that lists each player implies that no players other than
      those listed exist and is self-ratifying.

      The Registrar is also responsible for tracking any switches that
      would otherwise lack an officer to track them.

[CFJ 1703 (called 13 July 2007): A player cannot change eir nickname
by announcement if the new nickname that e specifies is the current
nickname of another player.]

[CFJ 1361 (called 7 May 2002): Purporting to assign a new nickname,
previously unused to refer to any entity, to another player is
successful, but does not displace the target's existing name or
nickname.]

[CFJ 1489 (called 11 February 2004): Watchers are not a rule-defined
element of the game.]

[CFJ 1420 (called 17 December 2002): The list of watchers, customarily
published with the registrar's report, is part of the game state, even
though it is not mentioned in the rules and no one is obliged to track
or publish it.]

[Cross-references (13 February 2008): the Registrar's duties are:
  * track citizenship (Rule 869)
  * report players' identity and contact details (Rule 2139)
  * report registration dates (Rule 2139)
  * issue Writ of FAGE (Rule 1789)
  * report deregistration by Writ of FAGE (Rule 1789)
  * track player activity and report change dates (Rule 2130)
  * track forum publicity (Rule 478)
  * report fora (Rule 478)
  * change the publicity of a forum (Rule 478)]

History:
Created by Proposal 4939 (Murphy), 29 April 2007
Amended(1) by Proposal 5172 (Murphy), 29 August 2007
Amended(2) by Proposal 6322 (Wooble), 26 May 2009
Amended(3) twice by Proposal 6567 (Walker), 28 November 2009
Power changed from 1 to 2 by Proposal 6567 (Walker), 28 November 2009
Amended(4) by Proposal 7141 (G.), 19 November 2011

----------------------------------------------------------------------

Rule 1789/7 (Power=2)
Cantus Cygneus

      Whenever a Player feels that e has been treated so egregiously
      by the Agoran community that e can no longer abide to be a part
      of it, e may submit a document to the Registrar, clearly labeled
      a Cantus Cygneus, detailing eir grievances and expressing eir
      reproach for those who e feels have treated em so badly.

      As soon as possible after receiving a Cantus Cygneus, the
      Registrar shall publish this document along with a Writ of
      Fugere Agorae Grandissima Exprobratione, commanding the Player
      to be deregistered. The Registrar shall note the method of
      deregistration for that Player in subsequent Registrar Reports.

      The Player is deregistered as of the posting of the Writ, and
      the notation in the Registrar's Report will ensure that,
      henceforth, all may know said Player deregistered in a Writ of
      FAGE.

[CFJ 1594 (called 16 December 2006): Players can be deregistered due
to this rule even if there is no Registrar.]

[CFJ 2358 (called 26 January 2009): A document which is labeled as a
Cantus Cygneus but does not actually detail grievances, etc. is not a
Cantus Cygneus.]

History:
Created by Proposal 3705 (Crito), Mar. 9 1998
Amended(1) by Proposal 4099 (Murphy), Jan. 15 2001
Amended(2) by Proposal 4147 (Wes), 13 May 2001
Amended(3) by Proposal 4825 (Maud), 17 July 2005
Power changed from 1 to 2 by Proposal 5780 (comex, ehird), 22 October
  2008
Amended(4) by Proposal 5815 (Pavitra, Murphy), 1 November 2008
Amended(5) by Proposal 5991 (Elysion), 7 December 2008
Amended(6) by Proposal 6099 (Pavitra), 22 February 2009
Amended(7) by Proposal 6338 (Murphy), 29 May 2009

----------------------------------------------------------------------

Rule 2130/13 (Power=2)
Activity

      Activity is a player switch with values Active (default) and
      Inactive, tracked by the Registrar.  The Registrar's report
      includes the date on which each non-Active player's activity
      last changed.

      A player CAN flip eir activity by announcement.  "To go on hold"
      is to become Inactive; "to come off hold" is to become Active.

      A player CAN flip another player's activity to Inactive without
      objection.

      A player who has been continuously Inactive for at least three
      months CAN be deregistered by any other player without
      objection.  This is a passive method of deregistration.

History:
Created by Proposal 4893 (Murphy), 12 February 2007
Amended(1) by Proposal 4966 (Zefram), 3 June 2007
Amended(2) by Proposal 4967 (Zefram), 3 June 2007
Amended(3) by Proposal 4985 (Zefram), 6 June 2007
Amended(4) by Proposal 4986 (Zefram), 6 June 2007
Amended(5) by Proposal 5004 (Zefram), 13 June 2007
Retitled by Proposal 5111 (Murphy), 2 August 2007
Amended(6) by Proposal 5111 (Murphy), 2 August 2007
Amended(7) by Proposal 5116 (Zefram; disi.), 8 August 2007
Amended(8) by Proposal 5258 (AFO), 18 October 2007
Amended(9) by Proposal 5271 (Murphy), 7 November 2007
Power changed from 1 to 2 by Proposal 5947 (ais523), 15 November 2008
Amended(10) by Proposal 6100 (Pavitra; disi.), 22 February 2009
Amended(11) by Proposal 6666 (Murphy), 10 March 2010
Amended(12) by Proposal 6974 (Murphy), 30 March 2011
Amended(13) by Proposal 6984 (Murphy), 10 April 2011

----------------------------------------------------------------------

======================================================================
Economy
      A category concerning asset-based gameplay.
----------------------------------------------------------------------

Rule 2166/16 (Power=2)
Assets

      An asset is an entity defined as such by a rule or contest
      (hereafter its backing document), and existing solely because
      its backing document defines its existence.

      Each asset has exactly one owner.  If an asset would otherwise
      lack an owner, it is owned by the Lost and Found Department.  If
      an asset's backing document restricts its ownership to a class
      of entities, then that asset CANNOT be gained by or transferred
      to an entity outside that class, and is transferred to the Lost
      and Found Department if it is owned by an entity outside that
      class.  If an asset is owned by the Lost and Found department
      any player CAN transfer or destroy it without objection.

      The Lost and Found department may own any asset, and have assets
      transferred to and from it, regardless of the asset's backing
      document or any Rule, Rules to the contrary notwithstanding.

      The recordkeepor of a class of assets is the entity (if any)
      defined as such by, and bound by, its backing document.  That
      entity's report includes a list of all instances of that class
      and their owners.  This portion of that entity's report is
      self-ratifying.

      An asset whose backing document is not a rule generally CAN be
      created by its recordkeepor by announcement, subject to
      modification by its backing document.  To "gain" an asset is to
      have it created in one's possession; to "award" an asset to an
      entity is to create it in that entity's possession.

      An asset generally CAN be destroyed by its owner by
      announcement, and an asset owned by the Lost and Found
      Department generally CAN be destroyed by its recordkeepor by
      announcement, subject to modification by its backing document.
      To "lose" (syn. "spend") an asset is to have it destroyed from
      one's possession; to "revoke" an asset from an entity is to
      destroy it from that entity's possession.

      An asset generally CAN be transferred by its owner to another
      entity by announcement, subject to modification by its backing
      document.  A fixed asset is one defined as such by its backing
      document, and CANNOT be transferred; any other asset is liquid.

      A currency is a class of asset defined as such by its backing
      document.  Instances of a currency with the same owner are
      fungible.  The Minimum Unit Quantity (MUQ) of each currency is
      one.

[CFJs 1790-1791 (called 11 November 2007): The self-ratifying asset
report is the complete list of ownerships of assets of that class; a
partial list does not self-ratify.]

[CFJ 1850 (called 22 December 2007): The general ability of the
recordkeepor to create assets does not include an ability to determine
who possesses them when created, so they are necessarily owned by the
Lost and Found Department [at the time of CFJ 1850, the Bank] upon
creation.]

[CFJ 1910 (called 10 March 2008): When an existing entity is defined
as an asset, the change of its owner from "undefined" to the Lost and
Found Department [Bank at the time of CFJ 1910] counts as a transfer,
and fails if the Lost and Found Department is outside of the class of
objects that can own the entity.]

[CFJ 2176 (called 22 September 2008): Entities may be fungible even if
not defined as such by this rule.]

[CFJ 2309 (called 11 December 2008): If two separate documents attempt
to define an asset with the same name, they refer to the same entity,
but the entity is not an asset.]

History:
Created by Proposal 5173 (Murphy), 29 August 2007
Amended(1) by Proposal 5216 (Murphy), 13 September 2007
Amended(2) by Proposal 5388 (Murphy), 1 January 2008
Amended(3) by Proposal 5475 (Murphy), 24 March 2008
Amended(4) by Proposal 5476 (Murphy; disi.), 27 March 2008
Amended(5) by Proposal 5496 (Murphy), 23 April 2008
Amended(6) by Proposal 5833 (Murphy, Taral), 12 November 2008
Amended(7) by Proposal 5840 (root), 12 November 2008
Amended(8) by Proposal 5974 (Murphy; disi.), 25 November 2008
Amended(9) by Proposal 6023 (Murphy), 22 December 2008
Assigned to Committee on Finance by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(10) by Proposal 6161 (Murphy), 31 March 2009
Amended(11) by Proposal 6253 (Quazie), 9 May 2009
Amended(12) by cleaning (Murphy), 16 August 2009
Amended(13) by Proposal 6430 (coppro; disi.), 18 August 2009
Amended(14) twice by Proposal 6650 (coppro), 10 March 2010
Amended(15) by Proposal 6792 (omd), 27 August 2010
Amended(16) by Proposal 6916 (omd; disi.), 2 January 2011

----------------------------------------------------------------------

Rule 2343/7 (Power=1.7)
Victory Conditions

      Victory Conditions and Losing Conditions are conditions
      explicitly defined as such by the Rules.  Such conditions are
      generally satisfied instantaneously, not continuously.

      A Victory Announcement is a published statement labeled as a
      Victory Announcement that states clearly that a specified person
      or persons have satisfied a specified Victory Condition while
      not satisfying any Losing Conditions (and explicitly and clearly
      states which persons and which victory condition).  A Victory
      Announcement is self-ratifying.

      The remainder of this rule notwithstanding, if an event's
      Victory Deadline has passed, then a person CANNOT Win the Game
      due to that event, and its Victory Deadline CANNOT be extended.
      An event's Victory Deadline is initially 28 days after the
      event, and CANNOT be extended except as specified by this rule.
      If it is within 28 days of passing, then anyone CAN extend it by
      28 days by announcement.  (Initiating, assigning a judge to, or
      judging a judicial case substantially relevant to the event
      implicitly counts as such an announcement.)

      When a Victory Announcement ratifies, or a judgement confirming
      the veracity of a victory announcement has been in effect and
      unappealed for one week, and provided the person(s) named have
      not already won via substantially the same events, the person(s)
      Win the Game.  There is no other method of winning the game.
      Winning the game does not cause Agora to end.

      The Herald SHALL award the Patent Title Champion to any person
      who wins the game, as soon as possible after the win.  The
      Herald SHOULD note the method of winning in eir report.

      Any person who wins the game while knowingly breaking a Rule, or
      while willingly and knowingly being a party to a Rules breach,
      where the breach is directly and substantially responsible for
      the win, commits the Class-4 Crime of Poor Sportsmanship.  If
      any party is found GUILTY of this crime, then, as soon as
      possible after the judgement has been in effect for one week,
      the Herald SHALL, as part of the punishment, revoke any Champion
      title awarded to the guilty parties as a result of the win.

History:
Created by Proposal 7039 (scshunt), 16 May 2011
Amended(1) by Proposal 7078 (omd), 16 June 2011
Amended(2) by Proposal 7098 (omd), 23 July 2011
Amended(3) by Proposal 7135 (G.), 6 November 2011
Amended(4) by Proposal 7139 (omd), 19 November 2011
Amended(5) by Proposal 7146 (omd), 25 January 2012
Amended(6) by Proposal 7147 (Murphy), 25 January 2012
Amended(7) by Proposal 7148 (Murphy), 25 January 2012

----------------------------------------------------------------------

Rule 2337/4 (Power=3)
Promises

      Promises are a class of assets.  Horton is an Office and the
      recordkeepor for promises; Horton's weekly report includes the
      text, author, conditions, and owner of all existing promises.
      The Tree is an entity for holding promises.  Ownership of
      promises is limited to persons, judicial panels, and the Tree.

      A Player (the promise's author) CAN create a promise in eir
      possession by announcement, clearly specifying its text.
      Optionally, the author CAN, in the creating message, specify one
      or more conditions required to be true for the promise to be
      cashed, and/or one or more conditions required to be true for
      the promise not to be destroyed when cashed.

      To submit a promise means to create that promise and then
      transfer it to the Tree.

      Promises with the same text, author, and conditions are
      fungible.

      Creating and cashing promises is secured with power threshold 3;
      any other modifications to promise holdings are secured with
      power threshold 2.

History:
Created by Proposal 7015 (G., ais523), 23 April 2011
Amended(1) by Proposal 7026 (Murphy, omd; disi.), 5 May 2011
Power changed from 2 to 3 by Proposal 7027 (omd), 5 May 2011
Amended(2) by Proposal 7082 (omd, Pavitra), 4 July 2011
Amended(3) by Proposal 7100 (ais523), 23 July 2011
Amended(4) by Proposal 7101 (Pavitra), 23 July 2011

----------------------------------------------------------------------

Rule 2338/2 (Power=3)
Cashing Promises

      An entity CAN cash a promise in eir possession by announcing
      that e does so, provided either that all conditions required to
      be true for the promise to be cashed are true, or it has no such
      conditions.  To do so, e must clearly and unambiguously identify
      the promise and SHOULD publish its text.

      When a promise is cashed, the text of the promise is interpreted
      as if it were published by its author as a standalone statement;
      if that statement requires additional context, that context MUST
      be supplied within the body of the message indicating the
      cashing.  Cashing a promise destroys it, unless the promise has
      at least one condition required to be true for it not to be
      destroyed when cashed, and all such conditions are true.

      If a promise is possessed by the Tree, any player except the
      promise's author CAN transfer it to emself by announcement, if e
      cashes the promise in the same message in which e transfers it
      to emself.

      Horton CAN destroy any promise Without Objection.

History:
Created by Proposal 7015 (G., ais523), 23 April 2011
Amended(1) by Proposal 7026 (Murphy, omd; disi.), 5 May 2011
Power changed from 2 to 3 by Proposal 7027 (omd), 5 May 2011
Amended(2) by Proposal 7100 (ais523), 23 July 2011

----------------------------------------------------------------------

Rule 2356/0 (Power=1)
Naughtiness

      A person CAN taunt the police by announcement specifying an
      integer from 1 to 14 inclusive. Doing so is the Class-N Crime of
      Naughtiness, where N is the specified integer.

History:
Created by Proposal 7132 (Pavitra), 6 November 2011

----------------------------------------------------------------------

Rule 2354/0 (Power=1)
Costs

      The documents defining the conditions for performing an action
      can specify another action as a cost; paying the cost becomes a
      condition for performing the original action.  A person has paid
      the cost for an attempt to perform an action if e performed each
      action so defined as a cost:

      (1) in the same message as the attempt,
      (2) clearly indicating that the action was a payment of that
          cost for that attempt, and
      (3) not indicating that it was a payment for any other cost or
          attempt.

      If the cost is defined in assets, the required action is
      destroying those assets, or, if the documents specify a
      recipient entity, transferring them to that entity.

History:
Created by Proposal 7117 (omd), 20 August 2011

----------------------------------------------------------------------

======================================================================
Definitions
      A category of definitions of terms and procedures that are
      widely used and do not readily fall into any other category.
----------------------------------------------------------------------

Rule 754/15 (Power=3)
Definition Definitions

      Regularity of communication being essential for the healthy
      function of any nomic, it is hereby resolved:

      (1) A difference in spelling, grammar, capitalization, or
          dialect, or the use of a synonym or abbreviation in place of
          a word or phrase is inconsequential in all forms of
          communication, as long as the difference does not create an
          ambiguity in meaning, except for the purpose of reporting on
          or quoting the text of a legal document.  A difference
          between two nonempty spans of whitespace is inconsequential
          in all forms of communication for all purposes.

      (2) A term explicitly defined by the Rules, along with its
          ordinary-language synonym not explicitly defined by the
          rules, by default has that meaning when used in any Rule of
          equal or lesser power, as well as any Rule of greater power
          that is clearly intended to comply with that meaning.

          The following clauses, where X and Y are both nouns or noun
          phrases, mean "X is/are defined as Y" unless they obviously
          have a different meaning:

            a) "X is/are Y"
            b) "Y is/are known as X"

      (3) Any term primarily used in mathematical or legal contexts,
          and not addressed by previous provisions of this Rule, by
          default has the meaning it has in those contexts.

      (4) Any term not addressed by previous provisions of this Rule
          by default has its ordinary-language meaning.

      In determining the ordinary-language meaning of a term,
      definitions contained in lower-powered Rules, are relevant and
      may provide guidance in helping to determine the meaning of a
      rule, but are not binding (especially if they differ greatly
      from the definitions that would be used otherwise).

      This rule takes precedence over any other rules which dictate
      terminology or grammar.

[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.]

History:
Created by Proposal 435 (Alexx), Aug. 30 1993
Amended by Proposal 754 (KoJen), Dec. 1 1993
Amended by Rule 750, Dec. 1 1993
Amended(1) by Proposal 2042, Dec. 11 1995
Infected and Amended(2) by Rule 1454, Dec. 17 1995
Amended(3) by Proposal 3452 (Steve), Apr. 7 1997, substantial
Amended(4) by Proposal 3915 (harvel), Sep. 27 1999
Power changed from 1 to 3 by Proposal 4507 (Murphy), 20 June 2003
Amended(5) by Proposal 4507 (Murphy), 20 June 2003
Amended(6) by Proposal 4866 (Goethe), 27 August 2006
Amended(7) by Proposal 5038 (Zefram), 28 June 2007
Amended(8) by Proposal 5834 (Goethe), 12 November 2008
Amended(9) by Proposal 6021 (Murphy), 22 December 2008
Amended(10) by Proposal 6384 (Murphy), 3 July 2009
Amended(11) by Proposal 6571 (ais523), 28 November 2009
Amended(12) by Proposal 6650 (coppro), 10 March 2010
Amended(13) by Proposal 6732 (comex), 6 June 2010
Amended(14) by Proposal 6741 (comex; disi.), 1 July 2010
Amended(15) by Proposal 6981 (Murphy, omd), 10 April 2011

----------------------------------------------------------------------

Rule 2152/6 (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. SHOULD NOT, DISCOURAGED, DEPRECATED:  Before performing the
         described action, the full implications of performing it
         should be understood and carefully weighed.

      4. CAN: Attempts to perform the described action are successful.

      5. MAY: Performing the described action does not violate the
         rules.

      6. MUST, SHALL, REQUIRED, MANDATORY:  Failing to perform the
         described action violates the rule in question.

      7. 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 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

----------------------------------------------------------------------

Rule 1023/28 (Power=2)
Common Definitions

      The following terms are defined:

      (a) The phrases "in a timely fashion" and "as soon as possible"
          mean "within X days", where X is 14 when the Speed is Slow,
          7 when it is Normal and 5 when it is Fast. This time period
          is set when the requirement is created (ie. X days before
          the limit ends). A requirement to perform an action at an
          exact instant (e.g.  "when X, Y SHALL Z"), but not "in the
          same message", is instead interpreted as a requirement to
          perform that action in a timely fashion after that instant.

      (b) Agoran epochs:

          (1) Agoran days begin at midnight UTC.

          (2) Agoran weeks begin at midnight UTC on Monday.

          (3) Agoran months begin at midnight UTC on the first day of
              each Gregorian month.

          (4) Agoran quarters begin when the Agoran months of January,
              April, July, and October begin.

          (5) Agoran years begin when the Agoran month of January
              begins.

          (5) A pivot is either the instant at which Agora Nomic began
              (June 30, 1993, 00:04:30 GMT +1200) or an instant at
              which at least one person won the game.  When used as a
              period of time, a "game" is the period of time between a
              pivot and the next pivot.

          These definitions do not apply to relative durations (e.g.
          "within <number> days after <event>").

History:
Created by Proposal 805, ca. Jan. or Feb. 1994
Amended by Proposal 907, ca. Apr. or May 1994
Amended by Rule 750, ca. Apr. or May 1994
Amended by Proposal 1023, Sep. 5 1994
Amended by Rule 750, Sep. 5 1994
Amended(1) by Proposal 1413, Feb. 1 1995
Amended(2) by Proposal 1434, Feb. 14 1995
Amended(3) by Proposal 1682, Aug. 22 1995
Amended(4) by Proposal 1727, Oct. 6 1995
Amended(5) by Proposal 2042, Dec. 11 1995
Amended(6) by Proposal 2489, Feb. 16 1996
Amended(7) by Proposal 2567, Apr. 12 1996
Mutated from MI=1 to MI=2 by Proposal 2602, May 26 1996
Amended(8) by Proposal 2629, Jul. 4 1996
Amended(9) by Proposal 2770 (Steve), Dec. 19 1996
Amended(10) by Proposal 3823 (Oerjan), Jan. 21 1999
Amended(11) by Proposal 3823 (Oerjan), Jan. 21 1999
Amended(12) by Proposal 3897 (harvel), Aug. 27 1999
Amended(13) by Proposal 3950 (harvel), Dec. 8 1999
Amended(14) by Proposal 4004 (Steve), May 8 2000
Amended(15) by Proposal 4278 (harvel), 3 April 2002
Amended(16) by Proposal 4406 (Murphy), 30 October 2002
Amended(17) by Proposal 4866 (Goethe), 27 August 2006
Amended(18) by Proposal 4938 (Murphy), 29 April 2007
Amended(19) by Proposal 5005 (root), 18 June 2007
Amended(20) by Proposal 5077 (Murphy), 18 July 2007
Amended(21) by Proposal 5102 (Zefram), 1 August 2007
Amended(22) by Proposal 5081 (Zefram; disi.), 1 August 2007
Amended(23) by Proposal 5408 (root), 22 January 2008
Amended(24) by Proposal 6046 (comex), 13 January 2009
Amended(25) by Proposal 6321 (Murphy; disi.), 26 May 2009
Amended(26) by Proposal 6535 (Murphy), 4 November 2009
Amended(27) by Proposal 6660 (Murphy; disi.), 10 March 2010
Amended(28) by Proposal 7045 (Walker), 16 May 2011

----------------------------------------------------------------------

Rule 2347/1 (Power=2)
Speed

      The Speed switch is an Agora Nomic switch, tracked by the
      Assessor, with values of Slow, Normal (default) and Fast. The
      Speed switch is secured.

      When the Speed has not been changed in the past month, the
      President CAN flip the Speed to Normal or Fast by announcement.
      At any time, players CAN flip it to a given value with Agoran
      Consent. In case of a lull, players CAN flip it to Slow without
      objection.

History:
Created by Proposal 7045 (Walker), 16 May 2011
Amended(1) by Proposal 7063 (G.), 16 June 2011

----------------------------------------------------------------------

Rule 1769/10 (Power=3)
Holidays

      A Holiday is a period of time designated as such by the Rules.

      The period each year from midnight GMT on the morning of 24
      December to the beginning of the first Agoran week to begin
      after 2 January is a Holiday.

      During a Holiday, the Promotor SHALL NOT distribute any
      proposals, and the Clerk of the Courts SHALL NOT assign a judge
      to any judicial case, and judges SHALL NOT assign judgement to
      any judicial case.

      If some Rule requires that an action be done prior to a given
      time, and that given time falls during a Holiday, or within the
      72-hour period immediately following that Holiday, then that
      action need not be done until 72 hours after that Holiday ends.

      If some Rule bases the time of a future event (including the
      time limit to perform an action) upon the time of another event,
      and

      a) that other event occurs during a Holiday, then the time at
         which that Holiday ends shall be used instead for the purpose
         of determining the time of the future event.

      b) the future event would occur during a Holiday, then the
         future event occurs 72 hours after the end of that Holiday
         instead.

      This Rule takes precedence over all Rules pertaining to the
      timing of events, and over all Rules which require events to be
      performed before a specified time.

[CFJ 1434 (called 24 January 2003): The registration of a player is an
event for the purposes of Rule 1769.]

[CFJ 1434 (called 24 January 2003): The expiration of a rule-defined
period is an event for the purposes of Rule 1769.]

[CFJ 1480 (called 5 January 2004): An automatic event specified to
occur at regular calendar intervals, for example quarterly, happens at
its specified time even if that is during a holiday.]

History:
Created by Proposal 3679 (General Chaos), Jan. 30 1998
Amended(1) by Proposal 4036 (Oerjan), Aug. 7 2000
Amended(2) by Proposal 01-003 (Steve), Feb. 2 2001
Amended(3) by Proposal 4866 (Goethe), 27 August 2006
Amended(4) by Proposal 5077 (Murphy), 18 July 2007
Amended(5) by Proposal 5086 (Zefram), 1 August 2007
Amended(6) by Proposal 5484 (Murphy; disi.), 2 April 2008
Amended(7) by Proposal 5535 (Murphy), 7 June 2008
Power changed from 2 to 3 by Proposal 5701 (ais523), 1 October 2008
Amended(8) by Proposal 7050 (omd), 16 May 2011
Amended(9) by Proposal 7150 (Murphy), 25 January 2012
Amended(10) by Proposal 7151 (Murphy), 25 January 2012

----------------------------------------------------------------------

Rule 2329/0 (Power=1)
Festival Days

      Agora Nomic recognizes and celebrates the following:

        * January 12-14 - Agora's Unbirthday observed (as described
          elsewhere)
        * April 1 - April Fool's Day
        * May 25 - Towel Day
        * June 30 - Agora's Birthday (as described elsewhere)
        * November 5 - Guy Fawkes Night
        * December 23 - Festivus

History:
Created by Proposal 6977 (Murphy, David Nicol), 30 March 2011

----------------------------------------------------------------------

Rule 2146/1 (Power=2)
Indices

      Indices are elements of the extended real numbers, which is a
      total order consisting of the real numbers plus a minimum
      element, called negative infinity, and a maximum element, called
      positive infinity or unanimity.

      The ratio of a positive index to zero is positive infinity.  The
      ratio of a negative index to zero is negative infinity.  The
      ratio of zero to any index is zero.

History:
Created by Proposal 4979 (Zefram, Maud), 31 May 2007
Amended(1) by Proposal 5113 (Murphy, Maud), 2 August 2007

----------------------------------------------------------------------

Rule 2162/1 (Power=2)
Switches

      A type of switch is a property that the rules define as a
      switch, and specify the following:

      a) The type(s) of entity possessing an instance of that switch.
         No other entity possesses an instance of that switch.

      b) One or more possible values for instances of that switch,
         exactly one of which is designated as the default.  No other
         values are possible for instances of that switch.

      c) Exactly one officer who tracks instances of that switch.
         That officer's report includes the value of each instance of
         that switch whose value is not its default value.

      At any given time, each instance of a switch has exactly one
      possible value for that type of switch.  If an instance of a
      switch comes to have a value, it ceases to have any other value.
      If an instance of a switch would otherwise fail to have a
      possible value, it comes to have its default value.

      "To flip an instance of a switch" is to make it come to have a
      given value.  "To become X" (where X is a possible value of
      exactly one of the subject's switches) is to flip that switch to
      X.

History:
Created by Proposal 5111 (Murphy), 2 August 2007
Amended(1) by Proposal 5271 (Murphy), 7 November 2007

----------------------------------------------------------------------

Rule 478/30 (Power=3)
Fora

      Freedom of speech being essential for the healthy functioning of
      any non-Imperial nomic, it is hereby resolved that no Player
      shall be prohibited from participating in the Fora.

      Publicity is a forum switch with values Public, Discussion, and
      Foreign (default), tracked by the Registrar.  Changes to
      publicity are secured.

      The Registrar's report includes, for each forum with non-Foreign
      publicity, sufficient instructions for players to receive
      messages there.

      The Registrar may change the publicity of a forum without
      objection as long as:

      (a) e sends eir announcement of intent to that forum; and

      (b) 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 active 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. A
      person "publishes" or "announces" something by sending a public
      message.

      Where the rules define an action that CAN be performed "by
      announcement", a person performs that action by unambiguously
      and clearly specifying the action and announcing that e performs
      it.  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.

[CFJs 1451-1452 (called 6 March 2003): A message that is split into
multiple email messages can qualify as a single message for game
purposes, if it is obvious how to combine the parts to reconstruct the
single message.]

[CFJ 752 (called 13 March 1995): Something sent to a Player who is
obligated to send it to all Players is sufficient for sending
something to the PF.]

[CFJ 813 (called 22 October 1995): A Player need not prove that e can
receive the PF.]

[CFJ 831 (called 10 November 1995): The Date: header of a message is
not necessarily the time at which the message takes effect.]

[CFJ 2205 (called 2 October 2008): A message takes effect at exactly
one of the times date-stamped on it; selecting which one is a matter
of game custom.]

[CFJ 2212 (called 7 October 2008): An IRC channel is a forum.]

[CFJ 2211 (called 7 October 2008): It is generally possible for an IRC
channel to be a public forum.

[CFJ 2214 (called 7 October 2008): Some IRC messages, such as NICK,
are sent to all members of an IRC channel but are not sent via that
channel.]

[CFJ 866 (called 8 April 1996): A message is "received" when the
message enters the recipient's normal technical domain of control,
whether this be eir private machine or eir private account on a shared
machine (but not the shared machine itself, if the recipient does not
control it).]

[CFJ 1112: In order to submit a Proposal, in the sense of R1865 and
elsewhere, it is not sufficient that a collection of text 'with the
clear indication that that text is intended to become a Proposal'
(R1483) merely be sent to the Public Forum by a Proposing Entity; the
collection of text must also be received in the Public Forum.]

[CFJ 1314 (called 15 August 2001): If a message sent to a public forum
is rejected by the list moderator, it still qualifies as having been
sent via a public forum.]

[CFJ 1905 (called 7 February 2008): Regardless of CFJ 1314, a message
has not been sent via a forum until most persons who have arranged to
receive messages via the forum receive it.]

[CFJ 1888 (called 31 January 2008): Sending a message to a Discussion
Forum, or other mailing list except for a Public Forum, does not
qualify as sending it to all players.]

[CFJ 1631 (called 29 April 2007): Public announcements must be made in
the message body; the subject line is insignificant.]

[CFJ 1784 (called 5 November 2007): An undescriptive or misleading
subject line does not deprive the message body of effect.]

[CFJ 1880 (called 22 January 2008): A phrase that would, in the
message body, cancel the effect of the rest of the message, does not
have such an effect if it appears in the subject line.]

[CFJ 1761 (called 30 September 2007): Publishing part of a message is
a different action from publishing the whole message.]

[CFJ 1646 (called 30 April 2007): The act of "publishing" or
"announcing" is accomplished when the message has left the sender's
technical domain of control, indicated by one of the "Received:"
headers.]

[CFJ 1695 (called 23 June 2007): A partnership, which by its nature
can't directly send email, can participate in the fora by means of its
members sending messages on its behalf, if its governing agreement
says so.]

[CFJ 1719 (called 12 August 2007): A player can, if e intends, have
public messages sent on eir behalf, including via a web form that
allows all-comers to send messages on eir behalf without specific
approval.]

[CFJs 1833-1834 (called 18 December 2007): A player can, by
contractual arrangement, grant another player the capacity to act by
announcement on eir behalf.]

[CFJ 1893 (called 3 February 2008): A non-consensual non-contractual
arrangement cannot grant a player the capacity to act by announcement
on behalf of another.]

[CFJ 2397 (caled 3 March 2009): A player can grant or revoke
permission at will for another player to act by announcement on eir
behalf.]

[CFJ 2322 (called 24 December 2008): The ability to act on behalf can
be created by any willful agreement.]

[CFJ 1336 (called 13 December 2001): A public statement that one
wishes to perform an action that one can perform by announcement can
constitute an announcement that performs that action.]

[CFJ 1621 (called 8 February 2007): Where an action can be performed
by announcement, announcing that one deems something to be the case
that would result from that action does not constitute performing the
action.]

[CFJ 1584 (called 24 February 2006), CFJ 1728 (called 20 August 2007):
Saying "I do X 1000 times", where X is something that can be done by
announcement, is an acceptable shorthand for 1000 instances of "I do
X", but this shorthand cannot be used with an infinite repeat count,
because it is impossible to write out an infinite number of instances
of "I do X".]

[CFJ 1774 (called 1 November 2007): Saying "I do X 10000 times", where
X is something that can be done by announcement, does not necessarily
achieve 10000 instances of X, if writing out 10000 instances of "I do
X" would be a substantial effort such that using the shorthand is
abusive.  The presumption is in favour of the shorthand being
successful.]

[CFJ 1775 (called 1 November 2007): If an announcement of the form "I
do X N times" is not be acceptable shorthand for N instances of "I do
X", then the announcement is completely nullified, and does not have
the effect of M instances of "I do X" for any non-zero repeat count
M.]

[CFJ 1730 (called 22 August 2007): An appropriate announcement will
accomplish an action even if its author believed the action was
impossible.]

[CFJ 1841 (called 20 December 2007): A message-based action cannot be
retroactive.]

[CFJ 1971 (called 22 May 2008): An announcement with a general
disclaimer as to its contents cannot fulfill a requirement to report
information, but it may successfully cause game actions to be taken if
the actions do not depend on the truth value of the disclaimed
contents.]

[CFJ 2133 (called 9 August 2008): A disclaimed statement cannot cause
an action to be taken by announcement.]

[CFJ 2112 (called 23 July 2008): An action is only taken by
announcement if the Rules define it as such; e.g., posting an
objection to a dependent action is not an action taken by
announcement.]

[CFJ 2151 (called 5 September 2008): Some unregulated actions, such as
celebrating and revealing things, can be taken by announcement.]

[CFJ 2086 (called 15 July 2008): Message-based actions are always
taken in some order, never precisely simultaneously, possibly unless
otherwise stated.]

[CFJ 2179 (called 23 September 2008): An message-based action can be
taken even if its sender cannot be identified.]

[CFJ 2221 (called 13 October 2008): When an action is specified as
"can do X in order to do Y", and a player does X without specifying
intent to do Y, e does not do Y.]

[CFJ 2238 (called 22 October 2008): The requirement of unambiguous
specification applies to the parameters of an action.]

[CFJ 2363 (called 1 February 2009): "X can do Y by doing Z" does not
imply that X can do Z.]

[CFJ 2441 (called 6 April 2009): Due to a limitation of the mailing
list archives, attaching a message with a particular text does not
count as publishing that text.]

[CFJ 3025 (called 15 May 2011): If it is clear what he did, then it
must be clear what he did; if it is not clear what he did, then it is
not clear what he did.]

History:
Created by Proposal 478 (Jim Shea), Sep. 20 1993
Amended(1) by Proposal 1477, Mar. 8 1995
Amended(2) by Proposal 1576, Apr. 28 1995
Amended(3) by Proposal 1610, Jul. 10 1995
Amended(4) by Proposal 1700, Sep. 1 1995
Amended(5) by Proposal 2052, Dec. 19 1995
Amended(6) by Proposal 2400, Jan. 20 1996
Amended(7) by Proposal 2739 (Swann), Nov. 7 1996, substantial
Amended(8) by Proposal 2791 (Andre), Jan. 30 1997, substantial
Amended(9) by Proposal 3521 (Chuck), Jun. 23 1997, substantial
Amended(10) by Proposal 3823 (oerjan), Jan. 21 1999
Amended(11) by Proposal 4147 (Wes), 13 May 2001
Amended(12) by Proposal 4248 (Murphy), 19 February 2002
Amended(13) by Proposal 4456 (Maud), 22 February 2003
Power changed from 1 to 3 by Proposal 4690 (root), 18 April 2005
Amended(14) by Proposal 4690 (root), 18 April 2005
Amended(15) by Proposal 4833 (Maud), 6 August 2005
Amended(16) by Proposal 4866 (Goethe), 27 August 2006
Amended(17) by Proposal 4939 (Murphy), 29 April 2007
Amended(18) by Proposal 5014 (Zefram), 24 June 2007
Amended(19) by Proposal 5111 (Murphy), 2 August 2007
Amended(20) by Proposal 5172 (Murphy), 29 August 2007
Amended(21) by Proposal 5272 (Murphy; disi.), 7 November 2007
Amended(22) by Proposal 5291 (root), 14 November 2007
Amended(23) by Proposal 5535 (Murphy), 7 June 2008
Amended(24) by Proposal 5613 (Quazie), 29 July 2008
Amended(25) by Proposal 5639 (Murphy), 29 July 2008
Amended(26) by Proposal 5818 (comex), 1 November 2008
Amended(27) by Proposal 6022 (Murphy), 22 December 2008
Amended(28) by Proposal 6785 (coppro; disi.), 22 August 2010
Amended(29) by Proposal 6963 (Murphy), 20 March 2011
Amended(30) by Proposal 7073 (woggle), 16 June 2011

----------------------------------------------------------------------

Rule 1728/32 (Power=3)
Dependent Actions

      A rule which purports to allow a person (the performer) to
      perform an action by a set of one or more of the following
      methods (N is 1 unless otherwise specified):

       1) Without N Objections, where N is a positive integer no
          greater than 8.  ("Without Objection" is shorthand for this
          method with N = 1.)
       2) With N Supporters, where N is a positive integer.  ("With
          Support" is shorthand for this method with N = 1.)
       3) With N Agoran Consent, where N is an integer multiple of 0.1
          with a minimum of 1.
       4) With Notice.

      thereby allows em to perform the action by announcement if all
      of the following are true:

       a) A person (the initiator) announced intent to perform the
          action, unambiguously and clearly specifying the action and
          method(s) (including the value of N for each method), at
          most fourteen days earlier, and (if the action depends on
          objections or notice) at least X days earlier, where X is a
          number which depends on the Speed at the time of intention
          as follows: Slow: 5, Normal: 4, Fast: 2.

       b) At least one of the following is true:

            1) The performer is the initiator.

            2) The initiator was authorized to perform the action due
               to holding a rule-defined position now held by the
               performer.

            3) The initiator is authorized to perform the action, the
               action depends on support, the performer has supported
               the intent, and the rule authorizing the performance
               does not explicitly prohibit supporters from performing
               it.

       c) Agora is Satisfied with the announced intent, as defined by
          other rules.

       d) If a set of conditions for the performance of the action was
          given in the announcement of intent to perform the action,
          all those conditions are met.

      The actor SHOULD publish a list of supporters if the action
      depends on support, and a list of objectors if it depends on
      objections.

[CFJ 1722 (called 15 August 2007): The method of dependent action need
not be described exactly: an approximate but inexact description
suffices, as does the rule-defined term.]

[CFJ 1802 (called 19 November 2007): The phrase "by Agoran Support" is
not an unambiguous description of a method of dependent action.]

History:
Created by Proposal 3521 (Chuck), Jun. 23 1997
Infected and Amended(1) by Rule 1454, Nov. 2 1997, substantial
  (unattributed)
Amended(2) by Rule 1728, Nov. 16 1997, substantial
Amended(3) by Proposal 3812 (Steve), Dec. 21 1998
Amended(4) by Proposal 3836 (General Chaos), Mar. 2 1999
Amended(5) by Proposal 3950 (harvel), Dec. 8 1999
Amended(6) by Proposal 3973 (harvel), Feb. 14 2000
Amended(7) by Proposal 3991 (Steve), Mar. 30 2000
Amended(8) by Proposal 4011 (Wes), Jun. 1 2000
Power changed from 1 to 2 by Proposal 4121 (Ziggy), Mar. 16 2001
Amended(9) by Proposal 4121 (Ziggy), Mar. 16 2001
Amended(10) by Proposal 4279 (harvel), 3 April 2002
Amended(11) by Proposal 4461 (Maud), 17 March 2003
Amended(12) by Proposal 4915 (Murphy), 2 April 2007
Amended(13) by Proposal 4981 (Zefram), 31 May 2007
Amended(14) by Proposal 4999 (Zefram), 12 June 2007
Amended(15) by Proposal 5007 (Zefram), 18 June 2007
Amended(16) by Proposal 5113 (Murphy, Maud), 2 August 2007
Amended(17) by Proposal 5370 (Zefram), 20 December 2007
Amended(18) by Proposal 5445 (Goethe, Murphy), 21 February 2008
Amended(19) by Proposal 5543 (Murphy, Pavitra, root), 16 June 2008
Amended(20) by Proposal 5775 (Murphy), 17 October 2008
Amended(21) by Proposal 5818 (comex), 1 November 2008
Power changed from 2 to 3 by Proposal 5947 (ais523), 15 November 2008
Amended(22) by Proposal 5995 (Murphy), 7 December 2008
Amended(23) by Proposal 6041 (Murphy, Warrigal), 13 January 2009
Amended(24) by Proposal 6204 (Murphy), 27 April 2009
Amended(25) by Proposal 6437 (Murphy), 18 August 2009
Amended(26) by Proposal 6448 (BobTHJ), 27 August 2009
Amended(27) by Proposal 6474 (c.), 15 September 2009
Amended(28) by Proposal 6512 (c.; disi.), 3 October 2009
Amended(29) by Proposal 6619 (Murphy; disi.), 4 February 2010
Amended(30) by Proposal 6650 (coppro), 10 March 2010
Amended(31) by Proposal 6981 (Murphy, omd), 10 April 2011
Amended(32) by Proposal 7045 (Walker), 16 May 2011

----------------------------------------------------------------------

Rule 2288/2 (Power=3)
Induction

      If a person CAN perform an action by announcement, e CAN perform
      it with N support, without N objections, with N Agoran Consent,
      or with notice, where N is a number appropriate for that form of
      dependent action.

      If a person CAN perform an action with notice, e CAN perform it
      without N objections, where N is an appropriate number.

      If a person CAN perform an action with M support, e CAN
      perform it with N support, where N is an appropriate number
      greater than M.

      If a person CAN perform an action without M objections, e CAN
      perform it without N objections, where N is an appropriate
      number less than M.

      If a person CAN perform an action via multiple different means
      of dependent actions, e CAN perform that action via multiple of
      them at the same time.

      If a player CAN perform an action with 0 support, then e CAN
      perform it by announcement.

History:
Created by Proposal 6675 (comex), 22 March 2010
Amended(1) by Proposal 6807 (coppro), 27 August 2010
Amended(2) by Proposal 6969 (Murphy), 20 March 2011

----------------------------------------------------------------------

Rule 2124/16 (Power=2)
Agoran Satisfaction

      A Supporter of a dependent action is an eligible entity who has
      publicly posted (and not withdrawn) support (syn. "consent") for
      an announcement of intent to perform the action.  An Objector to
      a dependent action is an eligible entity who has publicly posted
      (and not withdrawn) an objection to the announcement of intent
      to perform the action.

      The entities eligible to support or object to a dependent action
      are, by default, all first-class players, subject to
      modification by the document authorizing the dependent action.
      However, the previous sentence notwithstanding, the Executor of
      the announcement of intent is not eligible to support it.

      Agora is Satisfied with an intent to perform a specific action
      if and only if:

      (1) if the action is to be performed Without N Objections, then
          it has fewer than N objectors;

      (2) if the action is to be performed With N supporters, then it
          has N or more supporters; and

      (3) if the action is to be performed with N Agoran Consent, then
          the ratio of supporters to objectors is greater than N, or
          the action has at least one supporter and no objectors.

      The above notwithstanding, if the action depends on objections,
      and an objection to it has been withdrawn within the past 24
      hours, then Agora is not Satisfied with the intent.

      A person CANNOT support or object to an announcement of intent
      before the intent is announced, or after e has withdrawn the
      same type of response.

History:
Created by Proposal 4853 (Goethe), 18 March 2006
Amended(1) by Proposal 4866 (Goethe), 27 August 2006
Amended(2) by Proposal 4868 (Goethe), 27 August 2006
Amended(3) by Proposal 4978 (Murphy), 31 May 2007
Retitled by Proposal 5113 (Murphy, Maud), 2 August 2007
Amended(4) by Proposal 5113 (Murphy, Maud), 2 August 2007
Amended(5) by Proposal 5370 (Zefram), 20 December 2007
Power changed from 1 to 2 by Proposal 5445 (Goethe, Murphy), 21
  February 2008
Retitled by Proposal 5445 (Goethe, Murphy), 21 February 2008
Amended(6) by Proposal 5445 (Goethe, Murphy), 21 February 2008
Amended(7) by Proposal 5504 (Murphy), 10 May 2008
Amended(8) by Proposal 5767 (Murphy), 17 October 2008
Amended(9) by Proposal 5995 (Murphy), 7 December 2008
Amended(10) by Proposal 6027 (Elysion), 8 January 2009
Amended(11) by Proposal 6306 (Murphy), 26 May 2009
Amended(12) by Proposal 6410 (coppro; disi.), 30 July 2009
Amended(13) by Proposal 6448 (BobTHJ), 27 August 2009
Amended(14) by Proposal 6475 (c.; disi.), 15 September 2009
Amended(15) by Proposal 6512 (c.; disi.), 3 October 2009
Amended(16) by cleaning (Keba), 20 August 2010

----------------------------------------------------------------------

Rule 2333/3 (Power=1)
Contests

      A player CAN make a non-contest document into a contest without
      3 objections; he then becomes that contest's contestmaster.  The
      document should contain a list of instructions for the players
      of Agora to play a type of subgame, which should be fair and
      generally allow all players to join and participate on an equal
      footing.  Anyone CAN cause a contest to cease to be a contest
      with notice and with 3 support.

      The contest's instructions should include conditions under which
      persons "win the contest".  Upon a true announcement by the
      contestmaster that one or more persons satisfy those conditions,
      all those persons satisfy the Victory Condition of Victory.
      Intentionally making a false such announcement is the Class-4
      Crime of Gaming the System.

      The contestmaster's weekly report contains all matters defined
      by the instructions to be part of eir weekly report, as well as
      the instructions.

      The contestmaster is, prima facie, the adjudicator of contest
      instructions and disputes.  Disputes should in general, be
      resolved with the spirit of the instructions in mind.  For the
      purpose of determining the internal gamestate of a contest
      (including whether its contestmaster falsely announced that
      persons won the contest), its instructions are generally
      interpreted in the same manner as a rule, but the reasonable
      opinion of the contestmaster takes precedence.  The
      contestmaster CAN change the instructions, or any internal
      gamestate defined by them, without 3 objections, but SHOULD only
      do so to improve gameplay or resolve disputes within the spirit
      of the original contest.  E can also appoint a new contestmaster
      without objection.

      An entity is bound by a contest if and only if it is its
      contestmaster.

History:
Created by Proposal 6991 (omd), 10 April 2011
Amended(1) by Proposal 7080 (scshunt), 16 June 2011
Amended(2) by Proposal 7087 (omd), 23 July 2011
Amended(3) by Proposal 7149 (G.), 25 January 2012

----------------------------------------------------------------------

Rule 2334/0 (Power=2)
Timers

      A timer is a switch whose values are the non-negative integers
      (default zero), representing a number of seconds.  Timer values
      and changes can be expressed in terms of larger durations (e.g.
      "1 day" is equivalent to "86400 seconds").

      Each timer is either counting down or not counting down.  When a
      timer has been continuously counting down for 1 second since its
      last change, it decreases by 1.

      When reporting a timer value, it is sufficient to provide enough
      information that its value at the time of the report can be
      calculated with reasonable effort (e.g. "<value> as of <date>
      00:00:00 UTC and has been counting down since then").

History:
Created by Proposal 7002 (Murphy), 20 April 2011

----------------------------------------------------------------------

======================================================================
Offices
      A category concerning administrative positions held by persons
      within the game.
----------------------------------------------------------------------

Rule 1006/32 (Power=2)
Offices

      An office is a role defined as such by the rules.  Each office
      is either vacant (default) or filled (held) by exactly one
      player.  An officer is the holder of an office, who may be
      referred to by the name of that office.

      An imposed office is an office described as such by the rule
      defining it.  All others are elected.

      The holder of an elected office CAN resign it by announcement,
      causing it to become vacant.  Any player CAN cause an office to
      become vacant without objection.

[CFJ 1660 (called 13 May 2007): This rule does not define the meaning
of the term "office", in the sense meant by Rule 754, but rather
references the usual English definition of "office" and governs
offices as thus defined.]

[CFJ 1702 (called 12 July 2007): A requirement to submit something to
an officer is satisfied by publishing it, even if that office is
vacant at the time.]

History:
Created by Proposal 386 (Alexx), Aug. 16 1993
Amended by Proposal 733 (Ronald Kunne), Nov. 24 1993
Amended by Proposal 881, ca. Apr. 13 1994
Amended by Rule 750, ca. Apr. 13 1994
Amended by Proposal 1006, ca. Aug. 25 1994
Amended by Rule 750, ca. Aug. 25 1994
Amended(1) by Proposal 1336, Nov. 22 1994
Amended(2) by Proposal 1582, May 15 1995
Amended(3) by Proposal 1699, Sep. 1 1995
Amended(4) by Proposal 1763, Oct. 31 1995
Amended(5) by Proposal 2442, Feb. 6 1996
Amended(6) by Proposal 2623, Jun. 19 1996
Amended(7) by Proposal 3902 (Murphy), Sep. 6 1999
Amended(8) by Proposal 4002 (harvel), May 8 2000
Amended(9) by Proposal 4250 (harvel), 19 February 2002
Amended(10) by Proposal 4868 (Goethe), 27 August 2006
Amended(11) by Proposal 4887 (Murphy), 22 January 2007
Amended(12) by Proposal 4889 (Murphy), 22 January 2007
Amended(13) by Proposal 4939 (Murphy), 29 April 2007
Amended(14) by Proposal 4956 (Murphy), 7 May 2007
Amended(15) by Proposal 4980 (Murphy), 31 May 2007
Amended(16) by Proposal 5029 (Murphy), 28 June 2007
Amended(17) by Proposal 5059 (Zefram, Goethe), 9 July 2007
Amended(18) by Proposal 5070 (Zefram), 11 July 2007
Amended(19) by Proposal 5088 (Murphy), 25 July 2007
Amended(20) by Proposal 5103 (Zefram), 1 August 2007
Power changed from 1 to 2 by Proposal 5133 (Zefram), 13 August 2007
Amended(21) by Proposal 5133 (Zefram), 13 August 2007
Amended(22) by Proposal 5239 (AFO), 3 October 2007
Amended(23) by Proposal 5407 (root), 22 January 2008
Amended(24) by Proposal 5519 (Murphy), 28 May 2008
Amended(25) by Proposal 5534 (root; disi.), 7 June 2008
Amended(26) by Proposal 5986 (Murphy), 7 December 2008
Amended(27) by Proposal 6023 (Murphy), 22 December 2008
Assigned to Committee on Administration by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009
Amended(28) by Proposal 6372 (G.), 23 June 2009
Amended(29) by cleaning (Murphy), 16 August 2009
Amended(30) by Proposal 6482 (c.), 18 September 2009
Amended(31) by cleaning (Murphy), 6 March 2010
Amended(32) by Proposal 6790 (Wooble), 27 August 2010

----------------------------------------------------------------------

Rule 2143/15 (Power=1)
Official Reports and Duties

      For each office:

      a) If any task is defined by the rules as part of that office's
         weekly duties, then the holder of that office SHALL perform
         it at least once each week, except if the Speed is Slow, in
         which case the duties SHALL be completed once each fortnight.
         If any information is defined by the rules as part of that
         office's weekly report, then the holder of that office SHALL
         maintain all such information, and the publication of all
         such information is part of that office's weekly duties.

      b) If any task is defined by the rules as part of that office's
         monthly duties, then the holder of that office SHALL perform
         it at least once each month.  If any information is defined
         by the rules as part of that office's monthly report, then
         the holder of that office SHALL maintain all such
         information, and the publication of all such information is
         part of that office's monthly duties.

      Any information defined by the rules as part of an office's
      report, without specifying which one, is part of its weekly
      report.  Failure of the holder of an office to perform any duty
      required of that office within the allotted time is the Class-2
      crime of Tardiness.

      While performing weekly or monthly duties or publishing weekly
      or monthly reports, officers SHALL NOT publish information that
      is inaccurate or misleading.

      Reports SHALL be published in plain text.  Tabular data must
      line up properly when viewed in a monospaced font.  Publishing a
      report that deviates from these regulations is the Class 2 Crime
      of Making My Eyes Bleed.

[CFJ 2392 (called 27 February 2009): Publishing an intentionally
incomplete report does not satisfy this rule's requirement to publish
a report.]

History:
Created by Proposal 4970 (Zefram), 23 May 2007
Amended(1) by Proposal 5239 (AFO), 3 October 2007
Retitled by Proposal 5485 (root), 9 April 2008
Amended(2) by Proposal 5485 (root), 9 April 2008
Amended(3) by Proposal 5956 (comex), 17 November 2008
Amended(4) by Proposal 6030 (Murphy; disi.), 8 January 2009
Assigned to Committee on Administration by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009
Amended(5) by Proposal 6155 (comex), 31 March 2009
Amended(6) by Proposal 6175 (Yally), 7 April 2009
Amended(7) by Proposal 6224 (comex), 27 April 2009
Amended(8) by Proposal 6322 (Wooble), 26 May 2009
Amended(9) by Proposal 6368 (C-walker), 23 June 2009
Amended(10) by Proposal 6428 (BobTHJ), 18 August 2009
Amended(11) by cleaning (Murphy), 6 March 2010
Amended(12) by Proposal 6664 (Murphy; disi.), 10 March 2010
Amended(13) by cleaning (Murphy), 29 July 2010
Amended(14) by Proposal 6967 (Wooble), 20 March 2011
Amended(15) by Proposal 7045 (Walker), 16 May 2011

----------------------------------------------------------------------

Rule 2160/7 (Power=3)
Deputisation

      Any player (a deputy) CAN perform an action as if e held a
      particular office (deputise for that office) if all of the
      following are true:

        (a) The rules require the holder of that office, by virtue of
            holding that office, to perform the action (or, if the
            office is vacant, would so require if the office were
            filled).  This requirement is fulfilled by the deputy
            performing the action.

        (b) A time limit by which the rules require the action to be
            performed has expired, or the office is vacant.

        (c) If the office is filled, then the deputy announced between
            two and fourteen days earlier that e intended to deputise
            for that office for the purposes of the particular action.

        (d) It would be POSSIBLE for the deputy to perform the action,
            other than by deputisation, if e held the office.

[CFJ 1776 (called 1 November 2007): A requirement to perform an
action, for the purposes of this rule, can be a logical implication
from rules and circumstances, not just directly imposed by the rules.
In particular, it is possible to deputise to rotate the bench.]

[CFJ 2400 (called 6 March 2009): Deputisation is generally treated as
if the deputy gained the office immediately before the action, and
lost it immediately after.]

History:
Created by Proposal 5103 (Zefram), 1 August 2007
Amended(1) by Proposal 5200 (Zefram; disi.), 8 September 2007
Amended(2) by Proposal 5414 (Murphy), 26 January 2008
Amended(3) by Proposal 5454 (Murphy), 9 March 2008
Power changed from 1 to 3 by Proposal 5983 (Warrigal), 29 November
  2008
Assigned to Committee on Administration by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009
Amended(4) by Proposal 6129 (Goethe), 15 March 2009
Amended(5) by Proposal 6144 (Wooble), 23 March 2009
Amended(6) by Proposal 6218 (Murphy), 27 April 2009
Amended(7) by Proposal 6482 (c.), 18 September 2009

----------------------------------------------------------------------

Rule 2154/34 (Power=2)
Election Procedure

      A player CAN initiate an election for a specified elected office
      for which no election is already in progress

       a) by announcement, if e is the IADoP, or the office is vacant
          or assumed, or no election has been initiated for the office
          within 90 days before the announcement;

       b) with 4 Supporters, otherwise.

      When an election is initiated, the current holder of the office
      (if any) is initially considered to have been nominated and have
      accepted.

      During the first four days of the election (the nomination
      period), any player CAN by announcement nominate one or more
      active players.

      As soon as possible after the nomination period ends, the IADoP
      SHALL initiate an Agoran decision to determine the new
      officeholder. For this decision:

       1) The valid options are the active players (hereafter the
          candidates) who, during the election,

            a) received and accepted a nomination for the office
               before the decision was initiated (self-nomination
               constitutes acceptance), and

            b) did not decline a nomination for the office.

          The set of candidates can change after the decision is
          initiated.

       2) The eligible voters are the active first-class players.

       3) Each eligible voter's voting limit is one.

       4) If there are no valid options for the Decision, the IADoP
          SHALL, in place of initiating the decision, announce this
          fact, ending the election.  If there is exactly one valid
          option for the Decision, the IADoP SHALL, in place of
          initiating the Decision, announce the valid option (the
          candidate), thus installing that candidate into the office
          and ending the election.

      Upon the resolution of this decision, its outcome (if a
      candidate) is installed into the office, and the election ends.

History:
Created by Proposal 5059 (Zefram, Goethe), 9 July 2007
Amended(1) by Proposal 5096 (Murphy; disi.), 25 July 2007
Amended(2) by Proposal 5108 (Zefram; disi.), 2 August 2007
Amended(3) by Proposal 5133 (Zefram), 13 August 2007
Amended(4) by Proposal 5224 (Murphy), 23 September 2007
Amended(5) by Proposal 5407 (root), 22 January 2008
Amended(6) by Proposal 5452 (Murphy), 1 March 2008
Amended(7) by Proposal 5453 (Murphy), 1 March 2008
Amended(8) by Proposal 5491 (Murphy), 23 April 2008
Amended(9) by Proposal 5497 (Murphy; disi.), 23 April 2008
Amended(10) by Proposal 5499 (Goethe), 23 April 2008
Amended(11) by Proposal 5503 (root), 1 May 2008
Amended(12) by Proposal 5608 (Murphy), 29 July 2008
Amended(13) by Proposal 5609 (Murphy), 29 July 2008
Amended(14) by Proposal 5683 (Wooble), 8 September 2008
Amended(15) by SLR ratification (comex), 24 September 2008
Amended(16) by Proposal 5730 (comex; disi.), 7 October 2008
Amended(17) by Proposal 5806 (Wooble; disi.), 30 October 2008
Amended(18) by Proposal 5797 (Taral), 3 November 2008
Amended(19) by Proposal 5831 (Murphy), 6 November 2008
Amended(20) by Proposal 5998 (Sgeo), 7 December 2008
Assigned to Committee on Administration by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009
Amended(21) by Proposal 6157 (Goethe, OscarMeyr, Wooble), 31 March
  2009
Amended(22) by Proposal 6293 (Goethe), 19 May 2009
Amended(23) by Proposal 6296 (Murphy), 19 May 2009
Amended(24) by Proposal 6305 (Taral), 26 May 2009
Amended(25) by Proposal 6356 (Yally), 23 June 2009
Amended(26) by Proposal 6396 (Yally), 17 July 2009
Amended(27) by Proposal 6403 (coppro), 30 July 2009
Amended(28) by Proposal 6411 (Yally), 30 July 2009
Amended(29) by Proposal 6651 (coppro), 10 March 2010
Amended(30) by Proposal 6665 (Murphy; disi.), 10 March 2010
Amended(31) by Proposal 6696 (coppro), 25 April 2010
Amended(32) by Proposal 6845 (Tanner L. Swett), 3 October 2010
Amended(33) by Proposal 6969 (Murphy), 20 March 2011
Amended(34) by Proposal 6972 (G.), 30 March 2011

----------------------------------------------------------------------

Rule 2276/3 (Power=2)
Assumption of Vacant Offices

      Assumption is an elected office switch, tracked by the IADoP
      with values Postulated (default) and Assumed. Changes to
      Assumption are secured.  An active first-class player can make
      emself the holder of an elected office by announcement, provided
      that the office is either vacant or Assumed.

      Upon doing so, the office's Assumption is flipped to Assumed.

      When the holder of an office ceases to be an active player, the
      office's Assumption is flipped to Assumed.

      When a person comes to hold an office, or would come to hold an
      office if e did not hold it already, by a means other than the
      one provided by this Rule, then the Assumption of that office is
      flipped to Postulated.

      If a player has held an Assumed office continuously since the
      last time it was Postulated, e can flip its Assumption to
      Postulated by announcement.

History:
Created by Proposal 6506 (Pavitra), 3 October 2009
Amended(1) by Proposal 6528 (coppro; disi.), 23 October 2009
Amended(2) by Proposal 6529 (Pavitra; disi.), 23 October 2009
Amended(3) by Proposal 6761 (coppro), 2 August 2010

----------------------------------------------------------------------

Rule 2138/13 (Power=1)
The Interstellar Associate Director of Personnel

      The Interstellar Associate Director of Personnel (IADoP) is an
      office; its holder is responsible for keeping track of officers
      and reports.

      The IADoP's report includes the following:

      a) The holder of each office.
      b) The date on which each holder last came to hold that office.
      c) The date when the most recent nomination period for that
         office began.
      d) The date when that office's reports were last published.

      The portion of a public message purporting to be an IADoP's
      report that lists the holder of each office is self-ratifying.

[CFJ 1672 (called 18 May 2007): The Interstellar Associate Director of
Personnel is the Director of Personnel.]

[Cross-references (1 March 2008): the IADoP's duties are:
  * hold election for office where contested (Rule 2154)
  * report officeholding (Rule 2138)]

History:
Created by Proposal 4939 (Murphy), 29 April 2007
Amended(1) by Proposal 4956 (Murphy), 7 May 2007
Amended(2) by Proposal 5237 (AFO; disi.), 3 October 2007
Amended(3) by Proposal 5367 (Levi; disi.), 20 December 2007
Amended(4) by Proposal 5517 (Wooble; disi.), 28 May 2008
Amended(5) by Proposal 5718 (ais523), 7 October 2008
Assigned to Committee on Administration by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009
Amended(6) by Proposal 6175 (Yally), 7 April 2009
Amended(7) by Proposal 6175 (Yally), 7 April 2009
Amended(8) by Proposal 6230 (Wooble), 4 May 2009
Amended(9) by Proposal 6282 (Yally), 19 May 2009
Amended(10) and title changed by Proposal 6377 (coppro; disi.),
  3 July 2009
Amended(11) by Proposal 6493 (coppro; disi.), 18 September 2009
Retitled and amended(12) by Proposal 6667 (Murphy), 10 March 2010
Retitled and amended(13) by Proposal 6975 (Murphy), 30 March 2011

----------------------------------------------------------------------

Rule 2352/2 (Power=1)
The Ambassador

      The Ambassador is an office; its holder is responsible for
      managing the affairs of state of Agora.

History:
Created by Proposal 7097 (omd), 23 July 2011
Amended(1) by Proposal 7133 (omd), 6 November 2011
Amended(2) by Proposal 7159 (441344), 5 February 2012

----------------------------------------------------------------------

Rule 1551/15 (Power=3)
Ratification

      A public document is part (possibly all) of a public message.

      When a public document is ratified, rules to the contrary
      notwithstanding, the gamestate is modified to what it would be
      if, at the time the ratified document was published, the
      gamestate had been minimally modified to make the ratified
      document as true and accurate as possible.  Such a modification
      cannot add inconsistencies between the gamestate and the rules,
      and it cannot include a rule change unless the ratified document
      purports to include the text, title, and/or power of the rule
      being changed.  If no such modification is possible, or
      multiple substantially distinct possible modifications would be
      equally appropriate, the ratification fails.

      An internally inconsistent document generally cannot be
      ratified; however, if such a document can be divided into a
      summary section and a main section, where the only purpose of
      the summary section is to summarize information in the main
      section, and the main section is internally consistent,
      ratification of the document proceeds as if it contained only
      the main section.

      Text purportedly about previous instances of ratification (e.g.
      a report's date of last ratification) is excluded from
      ratification.

      Ratifying a public document is secured.

[CFJ 2165 (called 16 September 2008): Ratification can create legal
fictions, but does not always.]

History:
Created by Proposal 2425, Jan. 30 1996
Infected and Amended(1) by Rule 1454, Feb. 4 1997, substantial
  (unattributed)
Amended(2) by Proposal 3445 (General Chaos), Mar. 26 1997, substantial
Amended(3) by Proposal 3704 (General Chaos), Mar. 19 1998
Amended(4) by Proposal 3889 (harvel), Aug. 9 1999
Amended(5) by Proposal 4147 (Wes), 13 May 2001
Power changed from 1 to 3 by Proposal 4832 (Maud), 6 August 2005
Amended(6) by Proposal 4832 (Maud), 6 August 2005
Amended(7) by Proposal 4868 (Goethe), 27 August 2006
Amended(8) by Proposal 5101 (Zefram), 1 August 2007
Amended(9) by Proposal 5212 (Murphy), 8 September 2007
Amended(10) by Proposal 5275 (Murphy), 7 November 2007
Amended(11) by Proposal 5315 (Murphy), 28 November 2007
Amended(12) by Proposal 5459 (Murphy), 9 March 2008
Amended(13) by Proposal 6570 (Murphy), 28 November 2009
Amended(14) by Proposal 6930 (ais523), 2 January 2011
Amended(15) by Proposal 6938 (omd), 2 January 2011

----------------------------------------------------------------------

Rule 2202/4 (Power=3)
Ratification Without Objection

      Any player CAN, without objection, ratify a public document,
      specifying its scope. If that document is an official report or
      a substantial portion thereof, until such a time as that report
      or portion is again ratified, the date and scope of the
      ratification become a part of the report.

      Ratification Without Objection CANNOT cause the repeal,
      amendment, enactment, or mutation of any Rule, rules to the
      contrary notwithstanding.

      A player SHALL NOT knowingly use or announce intent to use
      Ratification Without Objection to ratify a (prior to
      ratification) incorrect document when a corrected document could
      be produced with reasonable effort, unless the general nature of
      the document's error and reason for ratifying it is clearly and
      plainly described in the announcement of intent.  Such
      ratification or announcement of intent to ratify is the Class-8
      Crime of Endorsing Forgery.

[CFJ 1836 (called 18 December 2007): Ratification of an official
document affects only those aspects of gamestate that are defined to
be part of the official report, and not aspects that are incidentally
reported on; in particular, ratification of an official report on
certain parameters pertaining to each player does not ratify the list
of players.]

[CFJ 2289 (called 25 November 2008): Ratification Without Objection of
a value inseparable from another value may change the latter value
even if it is not directly part of the report being ratified.]

History:
Created by Proposal 5459 (Murphy), 9 March 2008
Amended(1) by Proposal 6048 (Wooble), 13 January 2009
Amended(2) by Proposal 6174 (woggle), 7 April 2009
Amended(3) by Proposal 6340 (G.), 11 June 2009
Amended(4) by Proposal 6754 (coppro; disi.), 2 August 2010

----------------------------------------------------------------------

Rule 2201/5 (Power=3)
Self-Ratification

      A public document defined by the rules as self-ratifying is
      ratified when it is continuously undoubted for one week.

      A doubt is an explicit public challenge via one of the following
      methods, identifying a document and explaining the scope and
      nature of a perceived error in it:

       a) An inquiry case, appropriate for questions of legal
          interpretation.

       b) A claim of error, appropriate for matters of fact.  The
          publisher of the original document SHALL (if e was required
          to publish that document) or SHOULD (otherwise) do one of
          the following as soon as possible:

              i) Deny the claim (causing it to cease to be a doubt).
             ii) Publish a revision.
            iii) 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.

[CFJ 1690 (called 19 June 2007): A challenge to a self-ratifying
document [at the time of CFJ 1690, the resolution of an Agoran
decision] must explicitly identify the document, either individually
or as part of a set, and explicitly contest the accuracy of some
aspect of it.]

[CFJs 1790-1791 (called 11 November 2007): A challenge to any part of
a self-ratifying document prevents ratification of all parts of it.]

History:
Created by Proposal 5459 (Murphy), 9 March 2008
Amended(1) by Proposal 6106 (Murphy, ais523), 22 February 2009
Amended(2) by Proposal 6243 (Murphy), 9 May 2009
Amended(3) by Proposal 6622 (Murphy), 20 February 2010
Amended(4) by Proposal 6744 (Murphy), 1 July 2010
Amended(5) by Proposal 6922 (Murphy; disi.), 2 January 2011

----------------------------------------------------------------------

======================================================================
Agoran Decisions
      A category concerning the means by which this nomic makes
      collective decisions.
----------------------------------------------------------------------

Rule 693/14 (Power=3)
Agoran Decisions

      When the rules calls for an Agoran decision to be made, the
      decision-making process takes place in the following three
      stages, each described elsewhere:

          (a) Initiation of the decision.
          (b) Voting of the people.
          (c) Resolution of the decision.

      When submitting a ballot, a player can select PRESENT (syn.
      ABSTAIN) rather than one of the options provided by the
      decision. Rules to the contrary notwithstanding, a ballot cast
      for PRESENT is considered to be a valid ballot, but, unless
      specified otherwise, does not count as a valid option.

History:
Initial Mutable Rule 205, Jun. 30 1993
Amended by Proposal 693 (Wes), Nov. 12 1993
Amended(1) by Proposal 1564 (Steve), Apr. 28 1995
Infected and Amended(2) by Rule 1454, Sep. 14 1997, substantial
  (unattributed)
Amended(3) by Rule 693, Sep. 28 1997, substantial
Amended(4) by Proposal 3809 (General Chaos), Dec. 7 1998
Amended(5) by Proposal 3921 (Wes), Oct. 3 1999
Amended(6) by Proposal 3968 (harvel), Feb. 4 2000
Power changed from 1 to 2 by Proposal 4040 (Oerjan), Aug. 7 2000
Power changed from 2 to 3 by Proposal 4811 (Maud,Goethe), 20 June 2005
Amended(7) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(8) by Proposal 4868 (Goethe), 27 August 2006
Amended(9) by Proposal 4887 (Murphy), 22 January 2007
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(10) by Proposal 6403 (coppro), 30 July 2009
Amended(11) by Proposal 6441 (Murphy; disi.), 27 August 2009
Amended(12) by Proposal 6452 (Murphy; disi.), 27 August 2009
Amended(13) by Proposal 6465 (coppro; disi.), 15 September 2009
Amended(14) by Proposal 6617 (Murphy; disi.), 4 February 2010

----------------------------------------------------------------------

Rule 107/15 (Power=3)
Initiating Agoran Decisions

      An Agoran decision is initiated when a person authorized to
      initiate it publishes a valid notice which sets forth the intent
      to initiate the decision.  This notice is invalid if it lacks
      any of the following information, and the lack is correctly
      identified within one week after the notice is published:

      (a) The matter to be decided (for example, "the adoption of
          proposal 4781").

      (b) A description of the class of eligible voters sufficient to
          enable public agreement on which persons are eligible.  In
          particular, an explicit list of the eligible voters is
          always sufficient for this purpose.

      (c) A clear indication of the options available.

      (d) The identity of the vote collector.

      (e) Any additional information defined by the rules as essential
          parameters.

      The publication of such a valid notice initiates the voting
      period for the decision. Where {X, Y} is a given Speed followed
      by a number of days, the voting period lasts for Y days when the
      Speed is X at the time of initiation: {Slow, 14}, {Normal, 7},
      {Fast, 5}. The minimum voting period for a decision with at
      least two options is five days.  The vote collector for a
      decision with less than two options CAN and SHALL end the voting
      period by announcement, if it has not ended already, and
      provided that e resolves the decision in the same message.

      The voting period for a decision cannot be set or changed to a
      duration longer than fourteen days.

[CFJ 1650 (called 6 May 2007): The intent to initiate the decision and
the information required in the notice need not be explicit.]

[CFJ 1743 (called 18 September 2007): If the notice does not mention
voter eligibility but the type of Agoran decision is clear and the
rule defining the relevant type of Agoran decision fully determines
the class of eligible voters, then the notice thereby implicitly
describes the class of eligible voters.]

[CFJ 1722 (called 15 August 2007): Information that is explicitly
presented in the notice takes precedence over any information that
would be implicit, even where the explicit information is inaccurate
and the implicit information would have been accurate.]

[CFJ 1651 (called 6 May 2007): If a R107 notice initiating an Agoran
decision does not contain an explicit list of the eligible voters, and
there is later a dispute (evidenced by submission of a CFJ) over which
voters were eligible at that time, then the notice's description of
the class of eligible voters was necessarily insufficient to enable
public agreement on which persons are eligible.]

[CFJ 1652 (called 6 May 2007): The set of eligible voters on an Agoran
decision can change during its voting period.]

History:
Initial Immutable Rule 107, Jun. 30 1993
Mutated from MI=Unanimity to MI=3 by Proposal 1391, Jan. 24 1995
Amended(1) by Proposal 3889 (harvel), Aug. 9 1999
Amended(2) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(3) by Proposal 4868 (Goethe), 27 August 2006
Amended(4) by Proposal 4964 (Murphy), 3 June 2007
Amended(5) by Proposal 5113 (Murphy, Maud), 2 August 2007
Amended(6) by Proposal 5229 (root), 27 September 2007
Amended(7) by Proposal 5413 (root), 26 January 2008
Amended(8) by Proposal 5445 (Goethe, Murphy), 21 February 2008
Amended(9) by Proposal 5455 (Murphy), 1 March 2008
Amended(10) by Proposal 5948 (Murphy; disi.), 15 November 2008
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(11) by Proposal 6157 (Goethe, OscarMeyr, Wooble), 31 March
  2009
Amended(12) by Proposal 6816 (G., Keba), 4 September 2010
Amended(13) by Proposal 6945 (Murphy, omd; disi.), 16 January 2011
Amended(14) by Proposal 6981 (Murphy, omd), 10 April 2011
Amended(15) by Proposal 7045 (Walker), 16 May 2011

----------------------------------------------------------------------

Rule 683/17 (Power=3)
Voting on Agoran Decisions

      An eligible voter on a particular Agoran decision submits a
      ballot to the vote collector by publishing a valid notice
      indicating which one of the available options e selects.  To be
      valid, the ballot must satisfy the following conditions:

      (a) The ballot is submitted during the voting period for the
          decision, and the submitter is an eligible voter at the
          time of submission.

      (b) The ballot clearly identifies the matter to be decided.

      (c) The ballot clearly identifies the option selected by the
          voter.

      (d) The voter has not publicly retracted the ballot during the
          voting period.  ("Changing" a vote is equivalent to
          retracting it and casting a vote with the new value.)

      Among the otherwise-valid votes on an Agoran decision, only the
      first N submitted by each entity are valid, where N is the
      entity's voting limit on that decision.  The voting limit of an
      entity that is not an eligible voter on an Agoran decision is
      zero.  The voting limit of an eligible voter on an Agoran
      decision is two, except where rules say otherwise.

      The strength of an option is the number of valid ballots
      selecting that option.

      Other rules may place further constraints on the validity of
      ballots.  This rule takes precedence over any rule that would
      loosen the constraints specified by this rule.

[CFJ 1609 (called 13 January 2007): To "clearly identif[y] the matter
to be decided" does not necessarily require specifying it in detail.]

[CFJs 1852-1853 (called 23 December 2007): Claiming to submit more
votes than ones voting limit on the decision does not constitute the
making of a false statement.]

History:
Initial Mutable Rule 207, Jun. 30 1993
Amended by Proposal 683 (Jeffrey S.), Nov. 10 1993
Amended(1) by Proposal 1473, Mar. 8 1995
Amended(2) by Proposal 1531, Mar. 24 1995
Amended(3) by Proposal 1554, Apr. 17 1995
Amended(4) by Proposal 1641, Aug. 1 1995
Amended(5) by Proposal 2590, May 1 1996
Amended(6) by Proposal 3718 (Steve), Apr. 3 1998
Amended(7) by Proposal 3937 (Wes), Oct. 31 1999
Amended(8) by Proposal 3968 (harvel), Feb. 4 2000
Amended(9) by Proposal 3972 (Peekee), Feb. 14 2000
Amended(10) by Proposal 4190 (Steve), 18 July 2001
Amended(11) by Proposal 4699 (Sherlock), 18 April 2005
Power changed from 1 to 3 by Proposal 4811 (Maud,Goethe), 20 June 2005
Amended(12) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(13) by Proposal 4964 (Murphy), 3 June 2007
Amended(14) by Proposal 5078 (Zefram), 18 July 2007
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(15) by Proposal 6378 (Murphy), 3 July 2009
Amended(16) by Proposal 7032 (omd), 16 May 2011
Amended(17) by Proposal 7077 (omd), 16 June 2011

----------------------------------------------------------------------

Rule 2127/6 (Power=1)
Conditional Votes

      If a vote on an Agoran decision is submitted conditionally (e.g.
      "FOR if <X> is true, otherwise AGAINST"), then the selected
      option is evaluated based on the value of the condition(s) at
      the end of the voting period, and is clearly specified if and
      only if the value of the condition(s) can be reasonably
      determined (without circularity or paradox) from information
      reasonably available during the voting period.  If the option
      cannot be clearly identified, a vote of PRESENT is cast.

      Casting a vote endorsing another voter is equivalent to
      conditionally casting a vote whose value is the same as the most
      common value (if any) among that voter's valid votes on that
      decision.

      Casting a vote denouncing another voter is equivalent to
      conditionally casting a vote whose value is opposite to the most
      common value (if any) among that voter's valid votes on that
      decision.  FOR and AGAINST are opposites.

[CFJ 2449 (called 14 April 2009): For an endorsement or denouncement,
the identity of the voter in question is part of the condition.]

History:
Created by Proposal 4875 (Goethe), 1 December 2006
Amended(1) by Proposal 5427 (Murphy), 9 February 2008
Amended(2) by Proposal 5506 (Murphy; disi.), 10 May 2008
Amended(3) by Proposal 5746 (Murphy), 16 October 2008
Amended(4) by Proposal 6331 (Murphy), 29 May 2009
Amended(5) by Proposal 6383 (Murphy), 3 July 2009
Amended(6) by Proposal 6403 (coppro), 30 July 2009

----------------------------------------------------------------------

Rule 2280/0 (Power=3)
Implicit Votes

      When an eligible voter on an Agoran decision attempts to cast
      ballots without explicitly specifying the number of ballots to
      be cast (e.g. "FOR" instead of "FOR*1" or "FOR*3"), e casts a
      number of ballots equal to eir voting limit on that decision.

History:
Created by Proposal 6585 (c.; disi.), 6 December 2009

----------------------------------------------------------------------

Rule 2168/7 (Power=1)
Extending the voting period

      Whenever the voting period of an Agoran decision would end, and
      the result would be FAILED QUORUM, the length of the voting
      period for that decision is instead increased to 14 days, except
      if it is already that length, provided this has not already
      happened for the decision in question.

      Upon such an occurrence, the vote collector for the decision
      SHALL issue a humiliating public reminder to the slackers who
      have not yet cast any votes on it despite being eligible, and
      CAN end its voting period by announcement (resolving it
      constitutes an implicit announcement that its voting period is
      first ended) if the result would no longer be FAILED QUORUM, or
      if the decision is whether to adopt a proposal and no voter
      (other than possibly the proposal's author) has voted FOR.

History:
Created by Proposal 5191 (root), 6 September 2007
Amended(1) by Proposal 5979 (Murphy), 25 November 2008
Amended(2) by Proposal 6115 (Murphy), 1 March 2009
Amended(3) by Proposal 6294 (Yally), 19 May 2009
Amended(4) by Proposal 6328 (Murphy), 29 May 2009
Amended(5) by Proposal 6329 (Murphy), 29 May 2009
Amended(6) by Proposal 6504 (Murphy; disi.), 3 October 2009
Amended(7) by Proposal 7045 (Walker), 16 May 2011

----------------------------------------------------------------------

Rule 208/8 (Power=3)
Resolving Agoran decisions

      The vote collector for an unresolved Agoran decision CAN resolve
      it by announcement, indicating the option selected by Agora.  If
      it was required to be initiated, then e SHALL resolve it as soon
      as possible after the end of the voting period.  To be valid,
      this announcement must satisfy the following conditions:

      (a) It is published after the voting period has ended.

      (b) It clearly identifies the matter to be resolved.

      (c) It specifies the outcome, as described elsewhere, and, if
          there was more than one valid option, provides a tally of
          the voters' valid ballots on the various options.

      Each Agoran decision has exactly one vote collector, defaulting
      to the initiator of the decision.  If the vote collector is
      defined by reference to a position (or, in the default case, if
      the initiator was so defined), then the vote collector is the
      current holder of that position.

      This rule takes precedence over any rule that would provide
      another mechanism by which an Agoran decision may be resolved.

[CFJ 1711 (called 1 August 2007): If a purported resolution notice
refers via a References: header to a previous notice with an
incomplete vote tally and lists additional votes but does not give
revised totals, this does not qualify as including a vote tally.]

[CFJ 1810 (called 28 November 2007): If a purported resolution notice
refers via an approximate date header to a previous notice with an
incomplete vote tally and lists additional votes but does not give
revised totals, this does qualify as including a vote tally.]

[CFJ 1822 (called 4 December 2007): If a purported resolution notice
includes invalid votes in its tally of votes, this makes the notice
invalid.]

History:
Initial Mutable Rule 208, Jun. 30 1993
Amended(1) by Proposal 1401, Jan. 29 1995
Amended(2) by Proposal 1531, Mar. 24 1995
Power changed from 1 to 3 by Proposal 4811 (Maud, Goethe), 20 June
  2005
Amended(3) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(4) by Proposal 5113 (Murphy, Maud), 2 August 2007
Amended(5) by Proposal 5229 (root), 27 September 2007
Amended(6) by Proposal 5450 (Murphy), 27 February 2008
Amended(7) by Proposal 5453 (Murphy), 1 March 2008
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(8) by Proposal 6746 (coppro; disi.), 1 July 2010

----------------------------------------------------------------------

Rule 955/17 (Power=3)
Determining the Will of Agora

      After an Agoran Decision's voting period ends, it has an outcome
      (syn. "the <appropriate noun> chosen by Agora").

      (a) If there is more than one available option, and the number
          of distinct voters who submitted valid ballots is less than
          quorum, then the outcome is FAILED QUORUM, regardless of the
          remainder of this rule.  Otherwise, the decision achieved
          quorum.

      (b) If the decision has an adoption index, then the voting index
          is the ratio of the strength of FOR to the strength of
          AGAINST.  If the voting index is greater than 1, and greater
          than or equal to the decision's adoption index, then the
          outcome is ADOPTED; otherwise, the outcome is REJECTED.

      (c) Otherwise, the outcome is the option with the most votes.
          In case of a tie, the vote collector SHALL select one of the
          leaders as the outcome. If there are no options, the outcome
          is null.

[CFJs 1673-1675 (called 20 May 2007): Quorum for an Agoran decision is
determined at the time the vote collector makes the calculations
described in Rule 955.]

History:
Initial Mutable Rule 209, Jun. 30 1993
Amended by Proposal 396 (KoJen), Aug. 23 1993
Amended by Proposal 658, Oct. 29 1993
Amended by Proposal 761, Dec. 8 1993
Amended by Rule 750, Dec. 8 1993
Amended by Proposal 955, Jul. 25 1994
Amended by Rule 750, Jul. 25 1994
Amended(1) by Proposal 1279, Oct. 24 1994
Amended(2) by Proposal 1531, Mar. 24 1995
Amended(3) by Proposal 1723, Oct. 6 1995
Mutated from MI=1 to MI=3 by Proposal 2398, Jan. 20 1996
Amended(4) by Proposal 3721 (Steve), Apr. 16 1998
Amended(5) by Proposal 3818 (Chuck), Dec. 21 1998
Amended(6) by Proposal 4263 (Steve), 4 March 2002
Amended(7) by Proposal 4302 (Murphy), 17 May 2002
Amended(8) by Proposal 4412 (Steve), 6 November 2002
Amended(9) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(10) by Proposal 4868 (Goethe), 27 August 2006
Amended(11) by Proposal 5113 (Murphy, Maud), 2 August 2007
Amended(12) by Proposal 5418 (root), 2 February 2008
Amended(13) by Proposal 5445 (Goethe, Murphy), 21 February 2008
Amended(14) by Proposal 5783 (Murphy), 22 October 2008
Amended(15) by Proposal 5948 (Murphy; disi.), 15 November 2008
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(16) by Proposal 6336 (coppro; disi.), 29 May 2009
Amended(17) by Proposal 6403 (coppro), 30 July 2009

----------------------------------------------------------------------

Rule 879/27 (Power=2)
Quorum

      Quorum for an Agoran decision is N/3 (where N is the number of
      eligible voters with a positive voting limit on that decision),
      rounded up, with a minimum of five (unless this is greater than
      N, in which case quorum is N).

[CFJ 1562 (called 3 May 2005): A cancelled vote on a Proposal does not
count towards quorum.]

[CFJs 1673-1675 (called 20 May 2007): Quorum for an Agoran decision
changes as the set of eligible voters changes.]

History:
Initial Mutable Rule 201, Jun. 30 1993
Amended by Proposal 879, Apr. 13 1994
Amended by Rule 750, Apr. 13 1994
Amended(1) by Proposal 1471, Mar. 8 1995
Amended(2) by Proposal 1554, Apr. 17 1995
Amended(3) by Proposal 1708, Sep. 4 1995
Infected and Amended(4) by Rule 1454, Jul. 27 1996
Amended(5) by Proposal 2786 (Steve), Jan. 15 1997, substantial
Amended(6) by Proposal 3643 (General Chaos), Dec. 29 1997
Amended(7) by Proposal 3777 (Blob), Aug. 3 1998
Amended(8) by Proposal "A Separation of Powers" (Steve, Without
  Objection), Apr. 20 1999
Amended(9) by Proposal 3897 (harvel), Aug. 27 1999
Amended(10) by Proposal 3956 (harvel), Dec. 28 1999
Amended(11) by Proposal 3972 (Peekee), Feb. 14 2000
Power changed from 1 to 2 by Proposal 3980 (Steve), Mar. 1 2000
Amended(12) by Proposal 3980 (Steve), Mar. 1 2000
Amended(13) by Proposal 4018 (Kelly), Jun. 21 2000
Amended(14) by Proposal 4239 (Murphy), 29 January 2002
Amended(15) by Proposal 4276 (Steve), 28 March 2002
Amended(16) by Proposal 4278 (harvel), 3 April 2002
Amended(17) by Proposal 4282 (Goethe), 16 April 2002
Amended(18) by Proposal 4311 (root), 28 May 2002
Amended(19) by Proposal 4410 (Steve), 6 November 2002
Amended(20) by Proposal 4576 (root), 31 May 2004
Amended(21) by Proposal 4665 (Kolja), 9 April 2005
Amended(22) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(23) by Proposal 4964 (Murphy), 3 June 2007
Amended(24) by Proposal 4997 (Zefram, Goddess Eris), 6 June 2007
Amended(25) by Proposal 5000 (Murphy), 12 June 2007
Amended(26) by Proposal 5113 (Murphy, Maud), 2 August 2007
Amended(27) by Proposal 5445 (Goethe, Murphy), 21 February 2008

----------------------------------------------------------------------

Rule 2034/6 (Power=3)
Vote Protection and Cutoff for Challenges

      Any proposal that would otherwise change the validity of any
      existing vote on any specific unresolved Agoran decision is
      wholly without effect, rules to the contrary notwithstanding.
      This does not prevent amendment of the rules governing the
      validity of votes on Agoran decisions in general.

      Once an Agoran decision has been resolved, votes on it CANNOT be
      validly submitted or retracted, and its outcome CANNOT be
      changed in any way, rules to the contrary notwithstanding.  This
      does not prevent correcting errors in reporting its resolution.

      A public document purporting to resolve an Agoran decision
      constitutes self-ratifying claims that

       a) such a decision existed,
       b) it was resolved as indicated, and
       c) (if the indicated outcome was to adopt a proposal) such a
          proposal existed, was adopted, and took effect.

History:
Created by Proposal 4366 (Steve), 23 August 2002
Amended(1) by Proposal 4637 (Murphy), 19 February 2005
Amended(2) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(3) by Proposal 5212 (Murphy), 8 September 2007
Amended(4) by Proposal 5275 (Murphy), 7 November 2007
Amended(5) by Proposal 6139 (Murphy), 15 March 2009
Amended(6) by Proposal 6180 (Murphy; disi.), 7 April 2009

----------------------------------------------------------------------

======================================================================
Proposals
      A category concerning the primary and plenipotent system by
      which changes are made to the game.
----------------------------------------------------------------------

Rule 2350/1 (Power=3)
Proposals

      A proposal is a fixed body of text which has been made into a
      proposal using a process specifically described in the Rules.

      A player CAN create a proposal by publishing ("submitting") a
      body of text and an associated title with a clear indication
      that it is intended to become a proposal, which places the
      proposal in the Proposal Pool.  The author (syn. proposer) of a
      proposal is the player who submitted it.  A player CAN remove
      (syn. retract, withdraw) a proposal e authored from the Proposal
      Pool by announcement.

      A co-author of a proposal is a person (other than its author)
      unambiguously identified as such by its author when it was
      submitted.

History:
Created by Proposal 7083 (Walker), 4 July 2011
Amended(1) by Proposal 7086 (G., omd), 23 July 2011

----------------------------------------------------------------------

Rule 106/34 (Power=3)
Adopting Proposals

      If the option selected by Agora on a decision about whether to
      adopt a proposal is ADOPTED, then the proposal in question is
      adopted, and unless other rules prevent it from taking effect,
      its power is set to the minimum of four and its adoption index,
      and then it takes effect.  Except as prohibited by other rules,
      a proposal that takes effect CAN and does, as part of its
      effect, apply the changes that it specifies.  If the proposal
      cannot make some such changes, this does not preclude the other
      changes from taking place.

      If there is no Agoran Decision to adopt a particular proposal
      that has an outcome of ADOPTED, that proposal CANNOT take
      effect, rules to the contrary notwithstanding.

      Preventing a proposal from taking effect is a secured change;
      this does not apply to generally preventing changes to specified
      areas of the gamestate, nor to a proposal preventing itself from
      taking effect (its no-effect clause is generally interpreted as
      applying only to the rest of the proposal).

[CFJ 1647 (called 30 April 2007): Preceding a proposal-like text with
the heading "Proposal:" and a title can be sufficient to clearly
indicate that it is intended to become a proposal, but is not if it
can be interpreted as quoting an existing proposal.]

[CFJ 1717 (called 8 August 2007): Preceding a proposal-like text with
the question "What is the title of this proposal?" can be sufficient
to clearly indicate that it is intended to become a proposal.]

[CFJ 1885 (called 26 January 2008): "AGAINT" is a variant spelling of
"AGAINST", not a customary synonym for "FOR", despite its former
private usage with the latter meaning.]

[CFJ 1639 (called 29 April 2007): Where a proposal attempts two
separate amendments of the text of the same rule, if one of the
attempted amendments is not possible and the other is then the
possible amendment does in fact occur, unless the proposal explicitly
requires a different resolution.]

[CFJ 1781 (called 4 November 2007): Proposal distribution is not
governed by this rule, so for the promotor to distribute a proposal
that is not in the proposal pool is not a violation of this rule.]

[CFJ 1841 (called 20 December 2007): It is possible for a proposal to
have retroactive effect.]

[CFJ 2162 (called 14 September 2008): The retroactive effect of a
proposal cannot actually alter the past.]

[CFJ 2163 (called 14 September 2008): There is no possible proposal
text that would cause a proposal to take effect without being
adopted.]

[CFJ 2259 (called 6 November 2008): The possibility of the
instantaneous effects of a proposal are governed by the rules.]

History:
Initial Immutable Rule 106, Jun. 30 1993
Mutated from MI=Unanimity to MI=3 by Proposal 1073, Oct. 4 1994
Amended by Proposal 1278, Oct. 24 1994
Renumbered from 1073 to 106 by Rule 1295, Nov. 1 1994
Infected, but not amended, by Rule 1454, May 7 1995
Amended(1) by Proposal 3736 (Blob), May 3 1998
Amended(2) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(3) by Proposal 4868 (Goethe), 27 August 2006
Amended(4) by Proposal 4918 (OscarMeyr), 2 April 2007
Amended(5) by Proposal 4939 (Murphy), 29 April 2007
Amended(6) by Proposal 5010 (Levi), 24 June 2007
Amended(7) by Proposal 5078 (Zefram), 18 July 2007
Amended(8) by Proposal 5083 (Zefram), 1 August 2007
Amended(9) by Proposal 5334 (Murphy), 5 December 2007
Amended(10) by Proposal 5356 (root), 16 December 2007
Amended(11) by Proposal 5418 (root), 2 February 2008
Amended(12) by Proposal 5453 (Murphy), 1 March 2008
Amended(13) by Proposal 5572 (Murphy), 4 July 2008
Amended(14) by Proposal 6001 (Goethe), 7 December 2008
Amended(15) by Proposal 6022 (Murphy), 22 December 2008
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(16) by cleaning (comex), 12 February 2009
Amended(17) by Proposal 6089 (Goethe), 22 February 2009
Amended(18) by Proposal 6090 (Murphy, ais523), 22 February 2009
Amended(19) by Proposal 6113 (Goethe), 1 March 2009
Amended(20) by Proposal 6222 (coppro), 27 April 2009
Amended(21) by Proposal 6398 (C-walker; disi.), 17 July 2009
Amended(22) by Proposal 6414 (C-walker), 8 August 2009
Amended(23) by Proposal 6469 (coppro; disi.), 15 September 2009
Amended(24) by Proposal 6571 (ais523), 28 November 2009
Amended(25) by Proposal 6625 (Murphy), 20 February 2010
Amended(26) by Proposal 6656 (coppro), 1 March 2010
Amended(27) by Proposal 6721 (coppro; disi), 21 May 2010
Amended(28) by Proposal 6732 (comex), 13 June 2010
Amended(29) by Proposal 6823 (Murphy, omd), 10 September 2010
Amended(30) by Proposal 6968 (Murphy, scshunt, Wooble), 20 March 2011
Amended(31) by Proposal 7013 (omd), 23 April 2011
Amended(32) by Proposal 7081 (Murphy), 4 July 2011
Amended(33) by Proposal 7083 (Walker), 4 July 2011
Amended(34) by Propossal 7086 (G., omd), 23 July 2011

----------------------------------------------------------------------

Rule 1607/33 (Power=3)
Distribution

      The Promotor is an office; its holder is responsible for
      receiving and distributing proposals.

      A player specifically permitted by the Rules to distribute a
      Proposal CAN distribute the proposal by publishing it with the
      clear intent of distributing it.  When a proposal is
      distributed, it is removed from the Proposal Pool.  The
      distribution of a proposal initiates the Agoran decision of
      whether to adopt the proposal, as described elsewhere.  Removing
      a proposal from the Pool by a means other than initiating an
      Agoran Decision to adopt it is secured.

      The Promotor CAN distribute a proposal which is in the Proposal
      Pool at any time.  In a given Agoran week, the Promotor SHALL,
      as part of eir weekly duties, distribute all proposals in the
      Proposal Pool that were in the Pool at the beginning of that
      week.

      Distributed proposals have ID numbers, to be assigned by the
      Promotor.

      If there is a Proposal in the Pool that it would otherwise be
      IMPOSSIBLE for any active player to distribute, then any player
      CAN distribute that Proposal Without 3 Objections.

      The Promotor's report includes a list of all proposals in the
      Proposal Pool.

[CFJ 1546 (called 14 April 2005), CFJ 1669 (called 16 May 2007): If a
proposal is purportedly distributed with a text that differs from the
submitted text, this constitutes a legal distribution of the submitted
proposal if and only if the difference does not affect the meaning of
the proposal.]

[CFJ 1655 (called 9 May 2007): Distributing a purported proposal whose
text consists of the texts of two submitted proposals and separating
matter from the message that submitted them both, if both submitted
proposals have non-null effects, does not constitute a legal
distribution of either of the submitted proposals.]

[CFJ 1656 (called 9 May 2007): If the Promotor purports to distribute
a proposal, but the distributed text does not match any proposal in
the proposal pool, this constitutes the effective (albeit prohibited)
distribution of a new proposal.]

[CFJ 1780 (called 4 November 2007): If the Promotor creates a new
proposal by distribution, by accidentally mangling the text of a
proposal in the pool, and the new proposal is very similar in meaning
to the one on which it is based (with only inconsequential
differences), then the author of the new proposal is the author of the
proposal on which it is based.]

[CFJ 1780 (called 4 November 2007): If the Promotor accidentally
creates a new proposal by distribution, and the new proposal is
seriously different from any proposal in the pool, then the new
proposal has no author.]

[Cross-references (2 August 2007): the Promotor's duties are:
  * not distribute proposals during holiday (Rule 1769)
  * distribute proposals (Rule 1607)
  * manage ID numbers of distributed proposals (Rule 1607)
  * report proposal pool (Rule 1607)]

History:
Created by Proposal 2522, Mar. 10 1996
Amended(1) by Proposal 2662, Sep. 12 1996
Amended(2) by Proposal 2696, Oct. 10 1996
Null-Amended(3) by Proposal 2710, Oct. 12 1996
Amended(4) by Proposal 3827 (Kolja A.), Feb. 4 1999
Amended(5) by Proposal 3871 (Peekee), Jun. 2 1999
Amended(6) by Proposal 3902 (Murphy), Sep. 6 1999
Amended(7) by Proposal 4002 (harvel), May 8 2000
Amended(8) by Proposal 4050 (t), Aug. 15 2000
Amended(9) by Proposal 4085 (Blob), Nov. 16 2000
Amended(10) by Proposal 4250 (harvel), 19 February 2002
Amended(11) by Proposal 4486 (Michael), 24 April 2003
Amended(12) by Proposal 4868 (Goethe), 27 August 2006
Amended(13) by Proposal 5077 (Murphy), 18 July 2007
Amended(14) by Proposal 5110 (Murphy), 2 August 2007
Amended(15) by Proposal 5112 (Murphy), 2 August 2007
Amended(16) by Proposal 5418 (root), 2 February 2008
Amended(17) by Proposal 5457 (Murphy), 9 March 2008
Amended(18) by Proposal 5485 (root), 9 April 2008
Power changed from 1 to 2 by Proposal 5947 (ais523), 15 November 2008
Amended(19) by Proposal 6001 (Goethe), 7 December 2008
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(20) by Proposal 6313 (Goethe), 26 May 2009
Amended(21) by Proposal 6341 (G.), 11 June 2009
Amended(22) by Proposal 6394 (Goethe), 10 July 2009
Amended(23) by Proposal 6395 (coppro), 17 July 2009
Amended(24) by Proposal 6406 (C-walker), 7 August 2009
Amended(25) by Proposal 6500 (coppro; disi.), 26 September 2009
Amended(26) by Proposal 6531 (Walker), 23 October 2009
Amended(27) by Proposal 6541 (Murphy), 4 November 2009
Amended(28) by Proposal 6550 (Tiger; disi.), 13 November 2009
Amended(29) by Proposal 6793 (Wooble), 27 August 2010
Amended(30) by Proposal 6961 (G.), 3 March 2011
Amended(31) by Proposal 7033 (omd), 16 May 2011
Amended(32) by Proposal 7069 (Walker), 16 June 2011
Amended(33) by Proposal 7083 (Walker), 4 July 2011

----------------------------------------------------------------------

Rule 1950/23 (Power=3)
Decisions with Adoption Indices

      Adoption index is a switch possessed by Agoran decisions, whose
      value is either "none" (default) or an integral multiple of 0.1
      from 1.0 to 9.9.

      Chamber is a switch possessed by Agoran decisions with adoption
      indices, with values Ordinary (default) and Democratic.

      Determining whether to adopt a proposal is an Agoran decision.
      By default, this decision has an adoption index of 1.0 and is
      Ordinary; if the proposer specified valid, non-"none" values for
      the adoption index and/or Chamber when submitting the proposal,
      those values are set at the initiation of the decision. Changing
      either value is secured with a power threshold of 2. The vote
      collector for this decision is the Assessor.

      An Agoran decision with an adoption index has the following
      essential parameters:

      a) Its adoption index.
      b) Its author (and co-authors, if any).
      c) Its Chamber.

      The eligible voters on a decision with an adoption index are
      those entities that were active first-class players at the start
      of its voting period.  Setting or changing an entity's voting
      limit on such a decision is secured with a power threshold of 2
      if the decision is Ordinary, or 3 otherwise.

      For any Agoran decision with an adoption index, the available
      options are FOR and AGAINST.

History:
Created by Proposal 4032 (t), Jul. 24 2000
Amended(1) by Proposal 4085 (Blob), Nov. 16 2000
Amended(2) by Proposal 4221 (Steve), 10 October 2001
Amended(3) by Proposal 4282 (Goethe), 16 April 2002
Amended(4) by Proposal 4352 (OscarMeyr), 7 August 2002
Amended(5) by Proposal 4370 (OscarMeyr), 6 September 2002
Amended(6) by Proposal 4486 (Michael), 24 April 2003
Amended(7) by Proposal 4539 (Goethe), 16 November 2003
Amended(8) by Proposal 4576 (root), 31 May 2004
Amended(9) by Proposal 4624 (Goethe), 20 November 2004
Amended(10) by Proposal 4665 (Kolja), 9 April 2005
Amended(11) by Proposal 4685 (Quazie, Murphy), 18 April 2005
Power changed from 2 to 3 by Proposal 4811 (Maud,Goethe), 20 June 2005
Amended(12) by Proposal 4811 (Maud, Goethe), 20 June 2005
Amended(13) by Proposal 4868 (Goethe), 27 August 2006
Amended(14) by Proposal 4972 (Goddess Eris), 23 May 2007
Amended(15) by Proposal 4964 (Murphy), 3 June 2007
Amended(16) by Proposal 5000 (Murphy), 12 June 2007
Amended(17) by Proposal 5007 (Zefram), 18 June 2007
Amended(18) by Proposal 5047 (root), 1 July 2007
Retitled by Proposal 5078 (Zefram), 18 July 2007
Amended(19) by Proposal 5078 (Zefram), 18 July 2007
Retitled by Proposal 5418 (root), 2 February 2008
Amended(20) by Proposal 5418 (root), 2 February 2008
Amended(21) by Proposal 6961 (G.), 3 March 2011
Retitled and amended(22) by Proposal 7013 (omd), 23 April 2011
Amended(23) by Proposal 7083 (Walker), 4 July 2011

----------------------------------------------------------------------

Rule 2137/2 (Power=1)
The Assessor

      The Assessor is an office; its holder is responsible for
      collecting votes and keeping track of related properties.

[CFJs 1758-1759 (called 30 September 2007): If Assessorship changes
hands, vote collection duties move with it.]

[Cross-references (1 March 2008): the Assessor's duties are:
  * vote collector for proposals (Rule 106)]

History:
Created by Proposal 4939 (Murphy), 29 April 2007
Amended(1) by Proposal 5078 (Zefram), 18 July 2007
Amended(2) by Proposal 5453 (Murphy), 1 March 2008
Assigned to Committee on Rules by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009

----------------------------------------------------------------------

Rule 1698/3 (Power=3)
Agora Is A Nomic

      Agora is ossified if it is IMPOSSIBLE for any reasonable
      combination of actions by players to cause arbitrary rule
      changes to be made and/or arbitrary proposals to be adopted
      within a four-week period.

      If, but for this rule, the net effect of a proposal would cause
      Agora to become ossified, it cannot take effect, rules to the
      contrary notwithstanding.  If any other single change to the
      gamestate would cause Agora to become ossified, it is cancelled
      and does not occur, rules to the contrary notwithstanding.

History:
Created by Proposal 3465 (Steve), Apr. 26 1997
Retitled by Proposal 5536 (Murphy), 7 June 2008
Amended(1) by Proposal 5536 (Murphy), 7 June 2008
Amended(2) by Proposal 7075 (scshunt), 16 June 2011
Amended(3) by Proposal 7088 (omd), 23 July 2011

----------------------------------------------------------------------

======================================================================
Adjudication
      A category concerning the judicial system by which matters of
      controversy are resolved.
----------------------------------------------------------------------

Rule 991/12 (Power=2)
Judicial Cases Generally

      A judicial case, also known as a call for judgement (CFJ), is a
      procedure to settle a matter of controversy.

      Each judicial case has exactly one subclass, with particular
      features as defined by other rules.  Subclasses of judicial case
      exist only as defined by the rules.  Defining a subclass of
      judicial case is secured, with a power threshold of 1.7.  A
      judicial case's subclass CAN be specified by its initiator, or
      otherwise defaults to inquiry.

      The Clerk of the Courts (CotC) is an office, responsible for
      managing judicial activity.  The CotC's report includes the
      status of all judicial cases without a judgement.

      Judicial cases (other than appeal cases, which have historically
      been identified by reference to the prior case) have ID numbers,
      to be assigned by the Clerk of the Courts.

[CFJs 1692-1693 (called 20 June 2007): A CFJ can be unambiguously
referenced by using the customarily-assigned sequence numbers, even if
the number was not assigned in the public forum, provided that those
involved accept it as unambiguous at the time.]

[CFJ 1355 (called 28 April 2002): Titles for CFJs are unregulated, so
it is possible for a title to be assigned to a CFJ informally.]

[Cross-references (28 May 2008): the Clerk of the Courts' duties
are:
  * not assign judges during holiday (Rule 1769)
  * report open judicial cases (Rule 991)
  * manage ID numbers of non-appeal judicial cases (Rule 991)
  * refuse excess CFJ (Rule 2175)
  * assign judge to judicial case (Rule 1868)
  * not assign a poorly qualified judge (Rule 1868)
  * track player posture (Rule 1871)
  * rotate the bench (Rule 1871)
  * recuse tardy judge (Rule 2158)]

History:
Initial Mutable Rule 213, Jun. 30 1993
Amended by Proposal 407 (Alexx), Sep. 3 1993
Amended by Proposal 991, ca. Aug. 12 1994
Amended by Rule 750, ca. Aug. 12 1994
Infected and amended(1) by Rule 1454, Oct. 23 1995
Amended(2) by Proposal 2042, Dec. 11 1995
Amended(3) by Proposal 2457, Feb. 16 1996
Mutated from MI=1 to MI=2 by Proposal 2669, Sep. 19 1996
Amended(4) by Proposal 4170 (Elysion), 26 June 2001
Amended(5) by Proposal 4298 (Murphy), 17 May 2002
Amended(6) by Proposal 4867 (Goethe), 27 August 2006
Amended(7) by Proposal 5015 (Zefram), 24 June 2007
Retitled by Proposal 5086 (Zefram), 1 August 2007
Amended(8) by Proposal 5086 (Zefram), 1 August 2007
Amended(9) by Proposal 5110 (Murphy), 2 August 2007
Amended(10) by Proposal 5317 (Murphy), 28 November 2007
Amended(11) by Proposal 5464 (Murphy), 13 March 2008
Assigned to Committee on the Judiciary by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009
Amended(12) by Proposal 7050 (omd), 16 May 2011

----------------------------------------------------------------------

Rule 2158/10 (Power=2)
Judges

      At any time, each judicial case is either open (default),
      suspended, or has exactly one judgement.  This is a persistent
      status that changes only according to the rules.  The possible
      types of judgement for a judicial case depend on the type of
      case.

      When a judicial case is open and has a judge assigned to it, the
      judge CAN assign a valid judgement to it by announcement, and
      SHALL do so as soon as possible, unless e is recused from the
      case before the time limit for doing so has expired.  A judge
      SHOULD NOT assign an inappropriate judgement to any judicial
      case.  A judgement is valid and/or appropriate only as defined
      by the rules.  Defining these things is secured, with a power
      threshold of 1.7.  If more than one judgement is valid and
      appropriate, then the choice between them is left to the judge's
      discretion.

      When a non-appeal judicial case is open, and its judge has
      violated a time limit to assign a judgement to it, or is not an
      active player, the Clerk of the Courts SHALL recuse that judge
      with cause by announcement as soon as possible; however, this
      requirement is waived if the judge assigns a judgement to it
      first.

[CFJ 1804 (called 19 November 2007): A judge should give the judgement
that e believes is appropriate, and if e does so in good faith then e
can be EXCUSED if the judgement is later found to have been
inappropriate.]

[CFJ 1871 (called 15 January 2008): The appropriateness of a judgement
is determined solely by the facts of the case, and is independent of
the reasoning used by a judge to decide on the judgement.]

History:
Created by Proposal 5086 (Zefram), 1 August 2007
Amended(1) by Proposal 5151 (root), 29 August 2007
Amended(2) by Proposal 5317 (Murphy), 28 November 2007
Amended(3) by Proposal 5429 (Zefram), 9 February 2008
Amended(4) by Proposal 5464 (Murphy), 13 March 2008
Amended(5) by Proposal 5474 (Murphy), 24 March 2008
Amended(6) by Proposal 6045 (Taral), 13 January 2009
Assigned to Committee on the Judiciary by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009
Amended(7) by Proposal 6391 (Murphy), 10 July 2009
Amended(8) by Proposal 6399 (Wooble), 17 July 2009
Amended(9) by Proposal 6404 (Murphy; disi.), 30 July 2009
Amended(10) by Proposal 7050 (omd), 16 May 2011

----------------------------------------------------------------------

Rule 591/35 (Power=1.7)
Inquiry Cases

      Inquiry cases are a subclass of judicial cases.  An inquiry
      case's purpose is to determine the veracity of a particular
      statement.  An inquiry case CAN be initiated by any first-class
      person, by announcement which includes the statement to be
      inquired into.  (Including a yes/no question is equivalent to
      including a statement that the answer to that question is yes,
      and for such a case, YES and NO are synonymous with the
      judgements TRUE and FALSE respectively.)

      The initiator is unqualified to be assigned as judge of the
      case, and in the initiating announcement e CAN disqualify one
      person from assignment as judge of the case.

      The valid judgements for an inquiry case are as follows, based
      on the truth or falsity of the statement at the time the inquiry
      case was initiated:

      * FALSE, appropriate if the statement was factually and
        logically false

      * TRUE, appropriate if the statement was factually and logically
        true

      * UNDECIDABLE, appropriate if the statement was logically
        undecidable or otherwise not capable of being accurately
        described as either false or true

      * IRRELEVANT, appropriate if the veracity of the statement is
        not relevant to the game or is an overly hypothetical
        extrapolation of the game or its rules to conditions that
        don't actually exist, or if it can be trivially determined
        from the outcome of another (possibly still undecided)
        judicial case that was not itself judged IRRELEVANT

      * UNDETERMINED, appropriate if the statement is nonsensical or
        too vague, or if the information available to the judge is
        insufficient to determine which of the FALSE, TRUE, and
        UNDECIDABLE judgements is appropriate; however, uncertainty as
        to how to interpret or apply the rules cannot constitute
        insufficiency of information for this purpose

      * MALFORMED, appropriate if the text identified by the initiator
        as the statement cannot be parsed as a single statement in the
        ordinary-language sense; however, a compound statement (e.g.
        "X and Y", "X or Y") counts as a single statement

      Players SHOULD take the judgement of the question in an inquiry
      case, and the reasoning by which it was reached, into account
      when attempting to determine what is possible and/or legal in
      future play (including when making future judgements); but the
      judgement does not directly affect the veracity of the
      statement.

[CFJ 1835 (called 18 December 2007): A question cannot generally take
the place of a statement in initiating an inquiry case.]

[CFJ 1903 (called 6 February 2008): The question-statement equivalence
established by this rule applies only for the purposes of the subject
of an inquiry case, not for acting by announcement.]

[CFJ 1671 (called 17 May 2007): The truth or falsity of a statement
can be determined as of the initiation of a CFJ even if public
knowledge at the time of initiation was not sufficient to determine
it.]

[CFJ 1482 (called 10 February 2004): If the truth of a CFJ statement
logically depends on the truth of statements of a previously-called
CFJ which has not yet been judged, the judge is entitled to treat this
as a situation of insufficient information being available.]

[CFJ 1744 (called 18 September 2007): It is not the job of the judge
to hunt down or request the information that would be required to
render a substantive judgement.]

[CFJ 1771 (called 28 October 2007): If an inquiry case revolves around
the interpretation of a specific message, and the initiator does not
provide a reasonable reference to that message , the judge is entitled
to treat this as a situation of insufficient information being
available.]

[CFJ 1732 (called 23 August 2007): If a particular player holds a
particular office, and an inquiry case on a statement that that player
holds that office is judged FALSE, that player still holds that
office.]

[CFJ 2281 (called 19 November 2008): For the purposes of determining
the validity of an inquiry case, the term "statement" should be
interpreted loosely.]

History:
Initial Mutable Rule 216, Jun. 30 1993
Amended by Proposal 409 (Alexx), Aug. 26 1993
Amended by Proposal 591 (KoJen), Oct. 21 1993
Amended(1) by Proposal 1320, Nov. 21 1994
Amended(2) by Proposal 1487, Mar. 15 1995
Amended(3) by Proposal 2457, Feb. 16 1996
Amended(4) by Proposal 2662, Sep. 12 1996
Amended(5) by Proposal 2710, Oct. 12 1996
Infected and Amended(6) by Rule 1454, Nov. 27 1996, substantial
  (unattributed)
Amended(7) by Proposal 3452 (Steve), Apr. 7 1997, substantial
Amended(8) by Proposal 3463 (Harlequin), Apr. 17 1997, substantial
Infected and Amended(9) by Rule 1454, May 7 1997, substantial
  (unattributed)
Amended(10) by Rule 591, May 21 1997, substantial
Amended(11) by Proposal 3629 (General Chaos), Dec. 29 1997,
  substantial
Amended(12) by Proposal 3645 (elJefe), Dec. 29 1997
Amended(13) by Proposal 3889 (harvel), Aug. 9 1999
Amended(14) by Proposal 3897 (harvel), Aug. 27 1999
Amended(15) by Proposal 3968 (harvel), Feb. 4 2000
Amended(16) by Proposal 3998 (harvel), May 2 2000
Amended(17) by Proposal 4147 (Wes), 13 May 2001
Amended(18) by Proposal 4298 (Murphy), 17 May 2002
Amended(19) by Proposal 5068 (Zefram), 11 July 2007
Retitled by Proposal 5086 (Zefram), 1 August 2007
Power changed from 1 to 1.7 by Proposal 5086 (Zefram), 1 August 2007
Amended(20) by Proposal 5086 (Zefram), 1 August 2007
Amended(21) by Proposal 5296 (root), 28 November 2007
Amended(22) by Proposal 5360 (Murphy), 20 December 2007
Amended(23) by Proposal 5371 (Zefram), 20 December 2007
Amended(24) by Proposal 5425 (Murphy), 6 February 2008
Amended(25) by Proposal 5470 (Murphy), 24 March 2008
Amended(26) by Proposal 5476 (Murphy; disi.), 27 March 2008
Amended(27) by Proposal 5964 (Murphy), 18 November 2008
Amended(28) by Proposal 6002 (Murphy), 7 December 2008
Amended(29) by Proposal 6024 (Murphy), 22 December 2008
Amended(30) by Proposal 6044 (Goethe), 13 January 2009
Assigned to Committee on the Judiciary by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009
Amended(31) by Proposal 6571 (ais523), 28 November 2009
Amended(32) by Proposal 6931 (omd), 2 January 2011
Amended(33) by Proposal 7022 (Walker, Murphy, omd), 5 May 2011
Amended(34) by Proposal 7050 (omd), 16 May 2011
Amended(35) by Proposal 7078 (omd), 16 June 2011

----------------------------------------------------------------------

Rule 1504/57 (Power=2)
Criminal Cases

      Criminal cases are a subclass of judicial cases.  Any person can
      initiate a criminal case by announcement, specifying:

      (a) a person (the Accused),
      (b) an action the Accused allegedly performed or failed to
          perform, and
      (c) a rule allegedly violated by that action/inaction.

      The initiator and each member of the Accused's basis are
      unqualified to be assigned as judge of the case.

      The valid judgements for a criminal case are as follows:

      * GUILTY with a valid sentence, appropriate if the judge finds,
        beyond a reasonable doubt, that ALL of the following are true:
       (a) the Accused breached the specified rule via the specified
           act;
       (b) the breach occurred within 30 days prior to the case being
           initiated;
       (c) judgement has not already been reached in another criminal
           case with the same Accused, the same rule, and
           substantially the same alleged act;
       (d) the Accused could have reasonably believed that the alleged
           act did violate the specified rule;
       (e) the Accused could have reasonably avoided committing the
           breach without committing a different breach of equal or
           greater severity.

      * NOT GUILTY, appropriate if GUILTY is not appropriate.  In
        delivering this verdict, the judge SHOULD indicate which of
        the sub-requirements for a finding of guilty were not found to
        be true beyond a reasonable doubt.

      When a sentence has been assigned as part of a GUILTY judgement,
      the Accused is known as the ninny, and the sentence is in
      effect.

      The valid sentences are:

      * DISCHARGE, appropriate only in extraordinary circumstances, if
        any available non-null punishment would be manifestly unjust.
        Has no effect.

      * APOLOGY with a set of up to ten prescribed words (the empty
        set if none is explicitly specified), appropriate for rule
        breaches of small consequence.  When in effect, the ninny
        SHALL as soon as possible publish a formal apology of at least
        200 words, including all the prescribed words, explaining eir
        error, shame, remorse, and ardent desire for self-improvement.
        Failure to do so is a Class-3 Crime of Failure to Apologize.

      * FINE with an amount of one class of asset, appropriate for
        rule breaches of small consequence.  An amount is only valid
        if the currency's backing document binds the ninny (the Rules
        are considered to bind all players) or the ninny has this
        amount of the asset, and the backing document specifies a
        maximum FINE amount, and the amount is no greater than the
        maximum.  When in effect, the ninny SHALL, as soon as
        possible, either destroy this amount of eir asset or transfer
        it to the Lost and Found Department. The ninny is only obliged
        to perform one destruction or transfer per case, even if
        sentences of this type are assigned more than once or go into
        effect more than once.

      * COMMUNITY SERVICE with a set of up to five tasks (the
        prescribed tasks) that the ninny CAN reasonably and legally
        perform, appropriate for rule breaches of moderate consequence
        if the severity of the rule breach is reasonably correlated
        with the consequences of performing the tasks, and especially
        if any other available non-null punishment would be either
        unjust or insufficient.  The balance between compensatory and
        punitive service is left to the judge's discretion.  While a
        sentence of this type is in effect, the ninny SHALL perform
        the prescribed tasks (as soon as possible, unless a different
        time limit is specified).

      * TIME OUT with a number of days between 7 and 21.  Stasis is a
        player timer, tracked by the Registrar.  When a sentence of
        TIME OUT goes into effect, the ninny becomes inactive, and eir
        stasis timer increases by the specified amount; when it ceases
        to be in effect, eir stasis timer is decreased by the
        specified amount.  While a player is inactive, eir stasis
        timer is counting down.  While a player's stasis timer is
        positive, e CANNOT become active.

      * EXILE, appropriate for rule breaches of the highest severity.
        When a judgement of EXILE has been in effect continuously for
        one week, the ninny is deregistered and CANNOT register for
        two months after that time.  During this period, e is known as
        a Fugitive.  Being a Fugitive is the Losing Condition of
        Seeking Asylum.

      Players SHOULD NOT create rules defining Crimes of a Class
      greater than 14.

[CFJ 1720 (called 12 August 2007): Where a criminal charge is
expressed in the form "violating rule NNNN by XXX", the alleged act
for the purposes of the rules is only "XXX".]

[CFJ 1845 (called 20 December 2007): Mentioning a rule in a section
labelled "arguments" in a message that attempts to initiate a criminal
case does not constitute clearly specifying the rule allegedly
breached.]

[CFJs 1857-1858 (called 31 December 2007): Ignorance of the law is not
appropriate grounds for a verdict of UNAWARE.]

[CFJ 1804 (called 19 November 2007): A verdict of EXCUSED is
appropriate where a person mistakenly, in good faith, believes that
eir action is legal when it is not.]

[CFJs 1808-1809 (called 28 November 2007): Sentencing a ninny to
"APOLOGY" without explicitly giving a set of prescribed words
constitutes sentencing the ninny to APOLOGY with the empty set of
prescribed words.]

[CFJ 1846 (called 20 December 2007): For the purposes of prescribed
words, words do not need to be a standard part of the language.]

[CFJ 1924 (called 10 April 2008): A duration need not be a fixed
amount of time.]

History:
Created by Proposal 1682, Aug. 22 1995
Amended(1) by Proposal 2570, Apr. 12 1996
Amended(2) by Proposal 2677, Sep. 26 1996
Infected and Amended(3) by Rule 1454, Jan. 8 1997, substantial
  (unattributed)
Amended(4) by Proposal 3452 (Steve), Apr. 7 1997, substantial
Amended(5) by Proposal 3533 (General Chaos), Jul. 15 1997, substantial
Amended(6) by Proposal 3704 (General Chaos), Mar. 19 1998
Amended(7) by Proposal 4406 (Murphy), 30 October 2002
Amended(8) by Proposal 4867 (Goethe), 27 August 2006
Amended(9) by Proposal 4887 (Murphy), 22 January 2007
Retitled by Proposal 5086 (Zefram), 1 August 2007
Power changed from 1 to 1.7 by Proposal 5086 (Zefram), 1 August 2007
Amended(10) by Proposal 5086 (Zefram), 1 August 2007
Amended(11) by Proposal 5109 (Zefram; disi.), 2 August 2007
Amended(12) by Proposal 5132 (Zefram), 13 August 2007
Amended(13) by Proposal 5135 (Wooble), 17 August 2007
Amended(14) by Proposal 5153 (Murphy), 29 August 2007
Amended(15) by Proposal 5155 (root), 29 August 2007
Amended(16) by Proposal 5223 (root), 30 September 2007
Amended(17) by Proposal 5294 (Murphy), 22 November 2007
Amended(18) by Proposal 5349 (Murphy), 13 December 2007
Amended(19) by Proposal 5371 (Zefram), 20 December 2007
Amended(20) by Proposal 5386 (Murphy, Zefram), 1 January 2008
Amended(21) by Proposal 5404 (Murphy, pikhq, root), 16 January 2008
Amended(22) by Proposal 5436 (Murphy), 13 February 2008
Amended(23) by Proposal 5493 (Murphy), 23 April 2008
Amended(24) by Proposal 5631 (BobTHJ), 29 July 2008
Amended(25) by Proposal 5634 (Taral), 29 July 2008
Amended(26) by Proposal 5642 (Sgeo, ais523, root,
BobTHJ, Wooble, Murphy, Zefram, Goethe, Pavitra),
  29 July 2008
Amended(27) by Proposal 5624 (Murphy), 29 July 2008
Amended(28) by Proposal 5650 (Pavrita), 29 July 2008
Amended(29) by Proposal 5711 (Murphy, woggle), 7 October 2008
Power changed from 1.7 to 2 by Proposal 5728 (ihope), 7 October 2008
Amended(30) by Proposal 5728 (ihope), 7 October 2008
Amended(31) by Proposal 5808 (Murphy; disi.), 1 November 2008
Amended(32) by Proposal 6000 (Murphy), 7 December 2008
Amended(33) by Proposal 6010 (ais523, Goethe, Murphy, comex,
  OscarMeyr), 14 December 2008
Amended(34) by Proposal 6024 (Murphy), 22 December 2008
Assigned to Committee on Crime by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(35) by Proposal 6054 (Wooble), 23 January 2009
Amended(36) by Proposal 6112 (Taral), 1 March 2009
Amended(37) by Proposal 6119 (Goethe), 1 March 2009
Amended(38) by Proposal 6146 (Murphy), 23 March 2009
Amended(39) by Proposal 6206 (coppro), 27 April 2009
Amended(40) by Proposal 6354 (ais523), 17 June 2009
Amended(41) by Proposal 6355 (Yally), 23 June 2009
Amended(42) by Proposal 6401 (Murphy), 17 July 2009
Amended(43) by Proposal 6463 (C-walker), 15 September 2009
Amended(44) by Proposal 6522 (Walker), 23 October 2009
Amended(45) by Proposal 6535 (Murphy), 4 November 2009
Amended(46) by Proposal 6557 (BobTHJ; disi.), 13 November 2009
Amended(47) by cleaning (Murphy), 6 March 2010
Amended(48) by Proposal 6932 (scshunt), 2 January 2011
Amended(49) by Proposal 6961 (G.), 3 March 2011
Amended(50) by Proposal 7002 (Murphy), 20 April 2011
Amended(51) by Proposal 7005 (Walker, Yally, G.), 20 April 2011
Amended(52) by Proposal 7010 (Walker), 20 April 2011
Amended(53) by Proposal 7012 (Walker), 20 April 2011
Amended(54) by Proposal 7034 (omd), 16 May 2011
Amended(55) by Proposal 7050 (omd), 16 May 2011
Amended(56) by Proposal 7118 (scshunt), 20 August 2011
Amended(57) by Proposal 7146 (omd), 25 January 2012

----------------------------------------------------------------------

Rule 2277/3 (Power=2)
Appeals of Criminal Cases

      An appeal concerning any assignment of judgement in a criminal
      case within the past week CAN be initiated by the accused by
      announcement.

History:
Created by Proposal 6536 (Murphy), 4 November 2009
Amended(1) by cleaning (omd), 30 November 2010
Amended(2) by Proposal 6961 (G.), 3 March 2011
Amended(3) by Proposal 7050 (omd), 16 May 2011

----------------------------------------------------------------------

Rule 2205/3 (Power=1)
Judicial Arguments and Evidence

      Each of the following participants in a judicial case SHOULD
      present such arguments and/or evidence (explicitly labeled)
      relevant to that case as e is reasonably able to collect:

      1) The initiator, when initiating the case.

      2) For a criminal case, the defendant, during the pre-trial
         phase.

      3) The judge, when delivering judgement.

      When submitting arguments and/or evidence, a player SHOULD
      classify matters of legal interpretation as arguments, and
      matters of fact as evidence.

History:
Created by Proposal 5487 (Murphy), 9 April 2008
Amended(1) by Proposal 5526 (Murphy), 2 June 2008
Amended(2) by Proposal 6571 (ais523), 28 November 2009
Amended(3) by Proposal 6985 (Walker), 10 April 2011

----------------------------------------------------------------------

Rule 2157/6 (Power=1.7)
Judicial Panels

      A judicial panel is a structure whereby a group of two or more
      persons (its members) act together for the purpose of judging
      judicial cases.  A judicial panel's membership cannot change,
      and if two panels have the same membership then they are the
      same panel.  Judicial panels exist implicitly, without any
      specific act of formation.

      A judicial panel CAN send messages by means of any of its
      members sending a message identified as being from the panel,
      with the unanimous Support of the panel's other members.  By
      this mechanism a judicial panel can act, in situations where the
      rules state that an action is performed by sending a message.
      The rules may specify other mechanisms by which the judicial
      panel CAN act.

      A judicial panel can incur obligations.  The members of a panel
      SHALL act collectively to ensure that the panel satisfies all of
      its obligations.

History:
Created by Proposal 5086 (Zefram), 1 August 2007
Amended(1) by Proposal 5134 (root), 17 August 2007
Amended(2) by Proposal 5361 (Goethe), 20 December 2007
Amended(3) by Proposal 5439 (Murphy), 13 February 2008
Amended(4) by Proposal 5498 (Goethe), 23 April 2008
Amended(5) by Proposal 5552 (Murphy, root), 21 June 2008
Amended(6) by Proposal 6014 (Goethe), 18 December 2008
Assigned to Committee on the Judiciary by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009

----------------------------------------------------------------------

Rule 2341/0 (Power=1.7)
Judgements by Judicial Panels

      As soon as possible after a judicial panel is assigned to a
      case, each member of the panel SHALL publish an opinion
      indicating a valid judgement to assign to the case -- only the
      last such published opinion for each member is used to determine
      the outcome.  Each member SHOULD choose an appropriate
      judgement, and include arguments for eir choice.

      If, immediately after either all members have so published or
      the time limit for so publishing has ended, a majority of the
      members have opined for the same judgement, the panel acts to
      deliver the judgement in question.  If the panel publishes a
      valid judgement via another mechanism specified in the Rules,
      the requirement for individual members to publish individual
      opinions is waived.

      If an open case is assigned to a judicial panel, and one of its
      members previously published an opinion for that case as part of
      the same or a different judicial panel, then that opinion stands
      for the newly-assigned panel unless the case was judged and
      reopened in the meanwhile.

History:
Created by Proposal 7038 (scshunt), 16 May 011

----------------------------------------------------------------------

Rule 2318/2 (Power=1.7)
Motions to Reconsider

      If a non-Appeals judicial case (1) has a judgement that has been
      in effect for less than seven days and not been appealed, and
      (2) has not had a Motion to Reconsider filed for it at any time
      while it has been assigned to its current judge, then any Player
      CAN file a Motion to Reconsider the case with 2 Support, or by
      announcement if e is that case's judge.

      When a Motion to Reconsider is so filed, the case is rendered
      open again.  A player who files such a Motion SHOULD include
      arguments as to why the case needs reconsideration, and such
      arguments become part of the record of the case.

History:
Created by Proposal 6869 (G.), 8 November 2010
Amended(1) by Proposal 7050 (omd), 16 May 2011
Amended(2) by Proposal 7065 (scshunt), 16 June 2011

----------------------------------------------------------------------

Rule 911/47 (Power=1.7)
Appeal Cases

      Appeal cases are a subclass of judicial cases.  An appeal case's
      purpose is to determine the appropriateness of a judgement that
      has been assigned to a judicial case, and make remedy if the
      judgement was poorly chosen.  The assignment of judgement being
      questioned (appealed against, or appealed) is referred to as the
      prior assignment; the word "prior" in this rule is used to refer
      to the circumstances of the prior assignment.

      An appeal concerning any assignment of judgement in a non-appeal
      case within the past two weeks CAN be initiated by any player
      with 2 support.  However, rules to the contrary notwithstanding,
      an appeal CANNOT be initiated concerning an assignment caused by
      a judgement in an appeal case, nor an assignment for which an
      appeal has already been initiated.

      The entities qualified to be assigned as judge of an appeal case
      are the judicial panels consisting of three members, where each
      of the members is qualified to be assigned as judge of the prior
      case and none is the prior judge.  If possible, the CotC SHALL
      assign a panel where each of the members is well qualified to be
      assigned as judge of the prior case.

      The valid judgements for an appeal case are of the form
      "<action> with prejudice" or "<action> without prejudice".  Such
      a judgement is generally appropriate if and only if
      (1) the action is appropriate, and
      (2) the judgement is with prejudice if and only if the prior
          judge made an error in eir judgement which could have been
          reasonably avoided, or generally inappropriately discharged
          eir duties in the case.

      The valid values of <action> and their associated effects are as
      follows:

      * AFFIRM, appropriate if the prior judgement was appropriate for
        the prior case; the prior judgement is assigned to the prior
        case again

      * REMAND, appropriate if there is serious doubt about whether
        the prior judgement was appropriate; the prior case is
        rendered open again; the judge SHOULD assign this judgement if
        the judge believes that the judge of the prior case will make
        a better judgement if given a new opportunity

      * REMIT, appropriate if there is serious doubt about whether the
        prior judgement was appropriate, or if the prior judge
        exhibited corruptive self-interest (material, with a specific
        and obvious impact on eir judgement and arguments, and not
        arising merely due to a difference of opinion or a wholly
        incidental material benefit common among many players); the
        judge of the prior case (if any) is recused, and the prior
        case is rendered open again; the judge SHOULD assign this
        judgement if the judge believes that the judge of the prior
        case will not make a better judgement if given a new
        opportunity

      * OVERRULE with a valid replacement judgement for the prior
        case, appropriate if the prior judgement was inappropriate in
        the prior case and the replacement judgement is appropriate
        for the prior case; the replacement judgement is assigned to
        the prior case

      The appropriateness of the prior judgement is measured at the
      time it was assigned.

      When an appeal case is initiated, the prior case is suspended,
      and remains so until the appeal case is judged.

      The judge of a previously-appealed case SHALL NOT assign the
      same judgement to it without new reasoning that addresses the
      serious doubt about its appropriateness.  Violating this
      prohibition is the Class-2 Crime of Lazy Judging.

      A person SHALL NOT appeal a judgement (except on a criminal
      case) unless e reasonably believes that the judgement might be
      inappropriate.

[CFJ 1597 (called 22 December 2006): It is possible to appeal a
judgement even if it is not certain that the judgement exists.]

[CFJ 1800 (called 18 November 2007): An announcement of the form "I
call for the appeal of <judgement>" has the effect of initiating the
Agoran decision on whether to approve appealing the cited judgement.]

History:
Created by Proposal 384 (Alexx), Aug. 16 1993
Amended by Proposal 690 (Ronald Kunne), Nov. 11 1993
Amended by Proposal 911, May 4 1994
Amended by Rule 750, May 4 1994
Amended(1) by Proposal 1345, Nov. 29 1994
Amended(2) by Proposal 1487, Mar. 15 1995
Amended(3) by Proposal 1511, Mar. 24 1995
Amended(4) by Proposal 2457, Feb. 16 1996
Amended(5) by Proposal 2553, Mar. 22 1996
Amended(6) by Proposal 2685, Oct. 3 1996
Amended(7) by Proposal 3532 (General Chaos), Jul. 15 1997, cosmetic
  (unattributed)
Amended(8) by Proposal 3559 (Murphy), Oct. 24 1997, susbtantial
Amended(9) by Proposal 4213 (Taral), 29 September 2001
Amended(10) by Proposal 4278 (harvel), 3 April 2002
Amended(11) by Proposal 4298 (Murphy), 17 May 2002
Amended(12) by Proposal 4579 (Murphy), 15 June 2004
Amended(13) by Proposal 4825 (Maud), 17 July 2005
Amended(14) by Proposal 4867 (Goethe), 27 August 2006
Amended(15) by Proposal 5051 (Zefram), 5 July 2007
Retitled by Proposal 5086 (Zefram), 1 August 2007
Power changed from 1 to 1.7 by Proposal 5086 (Zefram), 1 August 2007
Amended(16) by Proposal 5086 (Zefram), 1 August 2007
Amended(17) by Proposal 5359 (Murphy), 20 December 2007
Amended(18) by Proposal 5361 (Goethe), 20 December 2007
Amended(19) by Proposal 5436 (Murphy), 13 February 2008
Amended(20) by Proposal 5466 (Murphy), 13 March 2008
Amended(21) by Proposal 5610 (Murphy, Goethe), 29 July 2008
Amended(22) by Proposal 5726 (Murphy), 7 October 2008
Amended(23) by Proposal 6002 (Murphy), 7 December 2008
Amended(24) by Proposal 6014 (Goethe), 18 December 2008
Amended(25) by Proposal 6024 (Murphy), 22 December 2008
Assigned to Committee on the Judiciary by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009
Amended(26) by Proposal 6211 (comex), 27 April 2009
Amended(27) by Proposal 6229 (Murphy), 4 May 2009
Amended(28) by Proposal 6327 (Murphy), 29 May 2009
Amended(29) by Proposal 6334 (Goethe, ais523), 29 May 2009
Amended(30) by Proposal 6334 (Goethe, ais523), 29 May 2009
Amended(31) by Proposal 6376 (Murphy), 23 June 2009
Amended(32) by Proposal 6510 (Murphy), 3 October 2009
Amended(33) by Proposal 6542 (Murphy), 7 November 2009
Amended(34) twice by Proposal 6571 (ais523), 28 November 2009
Amended(35) by Proposal 6605 (Murphy), 19 January 2010
Amended(36) by cleaning (Murphy), 6 March 2010
Amended(37) by Proposal 6705 (comex), 25 April 2010
Amended(38) by Proposal 6726 (coppro), 22 May 2010
Amended(39) by Proposal 6811 (Murphy), 4 September 2010
Amended(40) by Proposal 6969 (Murphy), 20 March 2011
Amended(41) by Proposal 7038 (scshunt), 16 May 2011
Amended(42) by Proposal 7042 (Murphy; disi.), 16 May 2011
Amended(43) by Proposal 7049 (omd), 16 May 2011
Amended(44) by Proposal 7050 (omd), 16 May 2011
Amended(45) by Proposal 7072 (woggle), 16 June 2011
Amended(46) by Proposal 7078 (omd), 16 June 2011
Amended(47) by Proposal 7152 (Murphy), 25 January 2012

----------------------------------------------------------------------

Rule 2342/0 (Power=1.7)
Judicial Appeals Panels

      If the time period for judging an appeals case ends with no
      majority opinion among members of the panel assigned to it, then
      the CotC CAN, and SHALL as soon as possible, by announcement
      cause the panel to judge either REMAND or REMIT with or without
      prejudice, whichever e feels is most appropriate. E SHALL NOT
      assign the case to another panel solely due to its failure to
      judge. These requirements are waived if the panel delivers a
      judgment in the meanwhile.

History:
Created by Proposal 7038 (scshunt), 16 May 011

----------------------------------------------------------------------

Rule 2175/6 (Power=1)
Judicial Retraction and Excess

      A new case is a judicial case (other than an appeal case) that
      has not had any judge assigned to it.  The initiator of a new
      case CAN retract it by announcement, thus causing it to cease to
      be a judicial case.

      An excess case is a new case whose initiator previously
      initiated five or more cases during the same week as that case.
      A person SHALL NOT initiate an excess case.  The Clerk of the
      Courts CAN refuse an excess case by  announcement, thus causing
      it to cease to be a judicial case.  When e does so, e fulfills
      any obligations with regards to that case.

History:
Created by Proposal 5284 (root, pikhq), 7 November 2007
Retitled by Proposal 5301 (Murphy), 28 November 2007
Amended(1) by Proposal 5301 (Murphy), 28 November 2007
Amended(2) by Proposal 5384 (Murphy), 1 January 2008
Amended(3) by Proposal 5768 (Murphy), 17 October 2008
Amended(4) by Proposal 6024 (Murphy), 22 December 2008
Amended(5) by Proposal 6445 (coppro; disi.), 27 August 2009
Amended(6) by Proposal 6944 (omd; disi.), 16 January 2011

----------------------------------------------------------------------

Rule 1868/18 (Power=2)
Judge Assignment Generally

      At any time, a judicial case either has no judge assigned to it
      (default) or has exactly one entity assigned to it as judge.
      This is a persistent status that changes only according to the
      rules.

      When a judicial case is open and has no judge assigned, the CotC
      CAN assign a qualified entity to be its judge by announcement,
      and SHALL do so as soon as possible.

      The entities qualified to be assigned as judge of a judicial
      case are the active first-class players who have not previously
      been assigned as its judge, subject to modification by other
      rules.  Being unqualified to be assigned as a judge does not
      inherently prevent an entity from continuing to be judge of a
      case to which e is already assigned.  Rules to the contrary
      notwithstanding, second-class players are always unqualified to
      judge.

      When a player is poorly qualified to be assigned as judge of a
      judicial case, the Clerk of the Courts SHALL not assign em to be
      the judge of that case; if e has done so, and that player is
      still the judge of that case, then e CAN recuse that judge from
      that case by announcement.

      Making an entity unqualified or poorly qualified to judge is
      secured, with a power threshold of 1.5.

      To recuse a judge from a case is to deassign em as its judge.
      Assigning a judge to a case implicitly recuses its existing
      judge, if any.  A recusal "with cause" is a recusal defined as
      such by the rules.

      A player CAN favor or disfavor a judicial case by announcement.
      When assigning a judge to a judicial case, the CotC, if
      possible, SHALL assign a player who has favored it and SHALL NOT
      assign a player who has disfavored it.

[CFJ 1186: The Clerk of the Courts is required by Rule 1868 to select
a Judge who is qualified ["eligible" at the time of CFJ 1186] at the
time that the Judge is selected, regardless of whether that Player was
qualified at the time that the CFJ was actually called for or when the
identity of that Player is announced.]

History:
Created by Proposal 3816 (Repeal-O-Matic), Dec. 21 1998
Amended(1) by Proposal 3962 (Wes), Jan. 20 2000
Amended(2) by Proposal 4166 (Elysion), 11 June 2001
Amended(3) by Proposal 4298 (Murphy), 17 May 2002
Amended(4) by Proposal 4867 (Goethe), 27 August 2006
Amended(5) by Proposal 5040 (Zefram), 28 June 2007
Amended(6) by Proposal 5069 (Zefram), 11 July 2007
Retitled by Proposal 5086 (Zefram), 1 August 2007
Power changed from 1 to 2 by Proposal 5086 (Zefram), 1 August 2007
Amended(7) by Proposal 5086 (Zefram), 1 August 2007
Amended(8) by Proposal 5151 (root), 29 August 2007
Amended(9) by Proposal 5217 (Murphy; disi.), 13 September 2007
Amended(10) by Proposal 5248 (AFO; disi.), 14 October 2007
Amended(11) by Proposal 5277 (Murphy, Zefram), 7 November 2007
Amended(12) by Proposal 5317 (Murphy), 28 November 2007
Amended(13) by Proposal 6024 (Murphy), 22 December 2008
Assigned to Committee on the Judiciary by Proposal 6053 (Murphy,
  woggle, ais523), 23 January 2009
Amended(14) by Proposal 6264 (comex), 11 May 2009
Amended(15) by Proposal 6279 (Murphy), 19 May 2009
Amended(16) by Proposal 6510 (Murphy), 3 October 2009
Amended(17) by Proposal 6961 (G.), 3 March 2011
Amended(18) by Proposal 7050 (omd), 16 May 2011

----------------------------------------------------------------------

Rule 1871/28 (Power=1.5)
The Standing Court

      Posture is a player switch, tracked by the Clerk of the Courts,
      with the following values:

      * Standing.  Standing players are generally qualified to judge.

      * Sitting.  Sitting players are poorly qualified to judge, but
        will generally become qualified when the CotC rotates the
        bench.

      * Leaning.  Leaning players are poorly qualified to judge, but
        are generally qualified to serve on appeal panels.

      * Supine (default).  Supine players are unqualified to judge.

      Changes to posture are secured.

      A player CAN flip eir posture to any non-standing value by
      announcement.

      When the CotC assigns a player as judge, that player becomes
      sitting.

      The CotC CAN rotate the bench (change all sitting players to
      standing) by announcement, but SHALL NOT do so unless, of the
      judicial cases requiring assignment:

       a) no entity is well-qualified to be assigned to any of them;

       b) e immediately afterwards (in the same announcement) assigns
          a judge to at least one of them.

      When the CotC recuses a non-supine player with cause, e CAN flip
      that player's posture to supine by announcement in a timely
      fashion.

[CFJ 1765 (called 16 October 2007): When the CotC is obliged to change
a player's posture due to recusal, this rule makes em capable of doing
so.]

[CFJ 1766 (called 16 October 2007): When the CotC is obliged to change
a player's posture due to recusal, eir capability to do so exists as
long as the obligation does, and this obligation does not terminate
due to the time limit running out.]

History:
Created by Proposal 3821 (Blob), Jan. 12 1999
Amended(1) by Proposal 4298 (Murphy), 17 May 2002
Amended(2) by Proposal 4342 (root), 8 July 2002
Amended(3) by Proposal 4523 (Murphy), 28 August 2003
Amended(4) by Proposal 4563 (OscarMeyr), 6 April 2004
Amended(5) by Proposal 4596 (Murphy), 4 July 2004
Amended(6) by Proposal 4648 (Kolja), 22 March 2005
Amended(7) by Proposal 4691 (root), 18 April 2005
Amended(8) by Proposal 4867 (Goethe), 27 August 2006
Amended(9) by Proposal 4912 (Murphy), 21 March 2007
Amended(10) by Proposal 4958 (Murphy), 3 June 2007
Retitled by Proposal 4991 (Murphy), 6 June 2007
Amended(11) by Proposal 4991 (Murphy), 6 June 2007
Amended(12) by Proposal 5069 (Zefram), 11 July 2007
Power changed from 1 to 1.5 by Proposal 5086 (Zefram), 1 August 2007
Amended(13) by Proposal 5086 (Zefram), 1 August 2007
Amended(14) by Proposal 5111 (Murphy), 2 August 2007
Amended(15) by Proposal 5248 (AFO; disi.), 14 October 2007
Amended(16) by Proposal 5249 (AFO), 14 October 2007
Amended(17) by Proposal 5250 (AFO), 14 October 2007
Amended(18) by Proposal 5251 (Goddess Eris), 14 October 2007
Amended(19) by Proposal 5259 (Zefram), 27 October 2007
Amended(20) by Proposal 5261 (root; disi.), 31 October 2007
Amended(21) by Proposal 5456 (Goddess Eris), 9 March 2008
Amended(22) by Proposal 5468 (Murphy), 13 March 2008
Amended(23) by Proposal 5474 (Murphy), 24 March 2008
Amended(24) by Proposal 5500 (Murphy; disi.), 26 April 2008
Amended(25) by Proposal 5771 (root), 17 October 2008
Amended(26) by Proposal 6400 (Murphy), 17 July 2009
Amended(27) by Proposal 6483 (Pavitra), 18 September 2009
Amended(28) by Proposal 6967 (Wooble), 20 March 2011

----------------------------------------------------------------------

Rule 2204/0 (Power=1.5)
Linked Assignments

      When the Clerk of the Courts assigns a player as judge of two or
      more judicial cases consecutively in the same announcement, that
      player only becomes sitting upon the last such assignment, rules
      to the contrary notwithstanding.  The CotC SHOULD NOT do this
      unless those cases are closely related in their subject matter.

History:
Created by Proposal 5468 (Murphy), 13 March 2008

----------------------------------------------------------------------

Rule 2164/4 (Power=1)
Judicial Self-Recusal and Case Transfer

      The judge of a judicial case CAN recuse emself from it at any
      time by announcement.  Such a recusal is with cause if and only
      if e has been assigned to the case for at least four days.

      An entity (the transferee) CAN, with consent from the current
      judge of a judicial case (the transferor), assign emself as the
      new judge of that case, provided that e is qualified to be
      assigned as judge of that case, and e immediately (in the same
      announcement) assigns a judgement to that case.

History:
Created by Proposal 5131 (Zefram), 13 August 2007
Amended(1) by Proposal 5151 (root), 29 August 2007
Amended(2) by Proposal 5465 (Murphy), 13 March 2008
Amended(3) by Proposal 6024 (Murphy), 22 December 2008
Amended(4) by Proposal 7050 (omd), 16 May 2011

----------------------------------------------------------------------

Rule 2212/1 (Power=1.7)
Judicial Declarations

      A judicial declaration is a document labeled as such and
      published by a person purporting to be the judge of a specific
      judicial case, which contains only information e would be
      required by the Rules, were e the judge, to publish in a
      judicial declaration.

      The author of a judicial declaration SHOULD attempt to ratify it
      without objection immediately after publishing it; players
      SHOULD NOT object to such an attempt unless the judicial
      declaration was invalid or illegally published.

History:
Created by Proposal 5715 (Murphy), 7 October 2008
Amended(1) by Proposal 6923 (omd, G.; disi.), 2 January 2011

----------------------------------------------------------------------

======================================================================
Patent Titles and Degrees
      A category concerning titles of honor and dishonor.
----------------------------------------------------------------------

Rule 649/32 (Power=1.5)
Patent Titles

      A Patent Title is a legal item given in recognition of a
      person's distinction.  The Herald is an office; its holder is
      responsible for tracking Patent Titles.

      A person specifically authorized by the rules to award (revoke)
      a Patent Title SHALL do so as soon as possible after the
      conditions authorizing em to do so are announced, unless there
      is an open judicial case contesting the validity of those
      conditions.  Awarding or revoking a Patent Title by any other
      method is secured.

      While a Patent Title has been awarded to (and not revoked from)
      an entity, that entity is said to Bear that Patent Title.  The
      status of Bearing a Patent Title can only be changed as
      explicitly set out in the Rules.  The Herald's monthly report
      includes a list of each Patent Title that at least one entity
      Bears, with a list of which entities Bear it.

      As soon as possible after a patent title is awarded or revoked,
      the herald SHALL announce the award or revocation.

      When a patent title is used as a noun to refer to bearers of the
      patent title, it is assumed to refer only to persons who Bear
      that patent title unless context clearly indicates otherwise.

[CFJ 1525 (called 15 November 2004): If a patent title is defined by
the rules, and previously the rules defined a patent title with the
same spelling but a different award condition, the two are the same
patent title.]

[CFJ 1592 (called 1 December 2006): A patent title, once borne, is
borne until explicitly revoked, even if the rule defining the patent
title is repealed or the patent title was never defined by a rule.]

[CFJ 1731 (called 23 August 2007): It is possible for an entity [a
person at the time of CFJ 1731] to bear more than one instance of a
patent title simultaneously.]

[CFJ 1591 (called 1 December 2006): Where a person bears the patent
title X, and X is not also defined by the rules to have some special
meaning, it is correct to say that that person "is an X".]

[Cross-references (9 February 2008): the Herald's duties are:
  * report Patent Titles (Rule 649)
  * announce award or revocation of Patent Title (Rule 649)
  * initiate decision for degree award (Rule 1367)
  * award degrees (Rule 1367)]

History:
Created by Proposal 649 (Wes), ca. Oct. 22 1993
...
Amended(1) by Proposal 1334, Nov. 22 1994
Amended(2) by Proposal 1681, Aug. 22 1995
Amended(3) by Proposal 2532, Mar. 10 1996
Amended(4) by Proposal 2693, Oct. 3 1996
Amended(5) by Proposal 2807 (Andre), Feb. 8 1997, cosmetic
  (unattributed)
Amended(6) by Proposal 3445 (General Chaos), Mar. 26 1997, substantial
Amended(7) by Proposal 3488 (Zefram), May 19 1997, substantial
  (unattributed)
Amended(8) by Proposal 3849 (Vlad), Apr. 6 1999
Amended(9) by Proposal 3860 (Peekee), May 12 1999
Amended(10) by Proposal 3914 (Elysion), Sep. 19 1999
Amended(11) by Proposal 3916 (harvel), Sep. 27 1999
Amended(11) by Proposal 3968 (harvel), Feb. 4 2000
Amended(12) by Proposal 4002 (harvel), May 8 2000
Amended(13) by Proposal 4110 (Ziggy), Feb. 13 2001
Amended(14) by Proposal 4147 (Wes), 13 May 2001
Amended(15) by Proposal 4497 (Steve), 13 May 2003
Amended(16) by Proposal 4691 (root), 18 April 2005
Amended(17) by Proposal 4824 (Maud, Manu), 17 July 2005
Amended(18) by Proposal 4865 (Goethe), 27 August 2006
Amended(19) by Proposal 5036 (Zefram), 28 June 2007
Amended(20) by Proposal 5084 (Zefram; disi.), 1 August 2007
Amended(21) by Proposal 5112 (Murphy), 2 August 2007
Amended(22) by Proposal 5123 (Zefram; disi.), 13 August 2007
Amended(23) by Proposal 5237 (AFO; disi.), 3 October 2007
Amended(24) by Proposal 5239 (AFO), 3 October 2007
Amended(25) by Proposal 5341 (Goethe), 8 December 2007
Amended(26) by Proposal 5412 (woggle), 26 January 2008
Power changed from 1 to 1.5 by Proposal 5437 (Goethe), 13 February
  2008
Amended(27) by Proposal 5437 (Goethe), 13 February 2008
Amended(28) by Proposal 6047 (comex), 13 January 2009
Amended(29) by Proposal 6175 (Yally), 7 April 2009
Amended(30) by cleaning (Wooble), 13 April 2009
Amended(31) by Proposal 6424 (Murphy), 16 August 2009
Amended(32) by Proposal 7050 (omd), 16 May 2011

----------------------------------------------------------------------

Rule 1367/15 (Power=3)
Degrees

      Certain patent titles are known as degrees.  The degrees are

      - Associate of Nomic                 (A.N.)
      - Bachelor of Nomic                  (B.N.)
      - Master of Nomic                    (M.N.)
      - Doctor of Nomic History            (D.N.Hist.)
      - Doctor of Nomic Science            (D.N.Sci.)
      - Doctor of Nomic Philosophy         (D.N.Phil.)

      Degrees are ranked in the order they appear in this rule, with
      degrees listed later being ranked higher.

      A degree CANNOT be awarded to any person more than once, and
      CANNOT be revoked once awarded.

      After a player publishes a suitable thesis with explicit intent
      to qualify for a degree (the specific degree need not be
      mentioned), the Herald SHALL, as soon as possible, initiate an
      Agoran Decision to award that player (the author) a degree as
      follows:

       - The available options are FAILING GRADE and each degree that
         the author does not have. The available options can change
         during the voting period.

       - The eligible voters are each active player at the time the
         decision is initiated.

       - Each player's voting limit on the decision is one plus the
         number of degrees e holds.

       - The specific thesis for which the degree is to be awarded is
         an essential parameter of the decision (but not the text of
         that thesis).

       - The outcome is, rules to the contrary notwithstanding, the
         highest-ranked degree such that more than half the votes cast
         were for that degree or a higher degree, or FAILING GRADE if
         there was no such degree.

      When the Herald resolves the decision, e CAN and SHALL award the
      author the degree selected by Agora, or no degree if FAILING
      GRADE was the outcome.

History:
Created by Proposal 1367, Jan. 5 1995
Infected and Amended(1) by Rule 1454, Feb. 12 1996
Amended(2) by Proposal 3452 (Steve), Apr. 7 1997, substantial
Amended(3) by Proposal 3741 (Murphy), May 8 1998
Amended(4) by Proposal 3889 (harvel), Aug. 9 1999
Amended(5) by Proposal 4002 (harvel), May 8 2000
Amended(6) by Proposal 4110 (Ziggy), Feb. 13 2001
Amended(7) by Proposal 4865 (Goethe), 27 August 2006
Amended(8) by Proposal 5085 (Zefram), 1 August 2007
Power changed from 1 to 1.5 by Proposal 5085 (Zefram), 1 August 2007
Amended(9) by Proposal 5243 (root; disi.), 7 October 2007
Amended(10) by Proposal 5276 (Murphy, Pavitra, Zefram), 7 November
  2007
Amended(11) by Proposal 5437 (Goethe), 13 February 2008
Power changed from 1.5 to 1 by Proposal 5947 (ais523), 15 November
  2008
Amended(12) by Proposal 5955 (ais523, Elysion, Murphy; disi.), 18
  November 2008
Amended(13) by Proposal 6257 (coppro), 11 May 2009
Amended(14) by Proposal 6624 (Murphy), 20 February 2010
Amended(15) by Proposal 6717 (coppro), 4 May 2010
Power changed from 1 to 3 by Proposal 6717 (coppro), 4 May 2010

----------------------------------------------------------------------

Rule 2231/3 (Power=3)
Order of the Hero of Agora Nomic

      The set of patent titles defined in this rule constitute the
      Order of the Hero of Agora Nomic; the titles may be collectively
      referred to as "Heroic titles" and a Bearer of a Heroic title as
      a Hero.

      Heroic titles are Agora's premier titles of distinction, and CAN
      be awarded to persons for meritorious service only by a proposal
      of power 3 or greater, which SHOULD explain why those persons
      are qualified.  Players SHOULD NOT cause heroic titles to be
      revoked.  Heroes are entitled to use the abbreviation of eir
      title as post-nomial letters in Agora communications and
      reports.

      The Heroic titles in decreasing precedence are:

      Grand Hero of Agora Nomic (GHAN) -- This title may be awarded to
      any person obviously and directly responsible for the existence
      of Agora and/or Nomic in general.  As this title is the highest
      honour that Agora may bestow, a Bearer of this title OUGHT to be
      treated right good forever.

      Hero of Agora Nomic (HAN) -- This title may be awarded to any
      person for outstanding meritorious service to Agora above and
      beyond the call of duty.

History:
Created by Proposal 6016 (OscarMeyr), 18 December 2008
Amended(1) by cleaning (Murphy), 16 August 2009
Amended(2) by Proposal 6571 (ais523), 28 November 2009
Power changed from 2 to 3 by Proposal 6626 (Murphy), 20 February 2010
Amended(3) by Proposal 6626 (Murphy), 20 February 2010

----------------------------------------------------------------------

======================================================================
Trophies
      A category concerning commemoration and symbolism.
----------------------------------------------------------------------

Rule 1727/17 (Power=1)
Happy Birthday

      WHEREAS, in June 1993, the world's only MUD-based nomic, Nomic
      World, had recently collapsed; yet, many of its players enjoyed
      nomic and did not wish to forego such a noble pursuit;

      And WHEREAS, Originator Chuck Carroll therefore composed an
      Initial Ruleset for an email nomic, based on the Initial
      Rulesets of Peter Suber, inventor of Nomic, and on the Rulesets
      of Nomic World and other nomics,

      And WHEREAS, a nomic thus rose like a phoenix from the ashes of
      Nomic World, played on the mailing list originally set up for
      discussion of Nomic World, and coming into existence at June 30,
      1993, 00:04:30 GMT +1200, with a message sent by FIRST SPEAKER
      Michael Norrish, which read, in part,

          "I see no reason to let this get bogged down; there are no
          precedents or rules that cover this situation, so I think we
          may as well begin directly.... Proposals for new rules are
          invited. In accordance with the rules, these will be
          published, numbered and distributed by me at my earliest
          convenience."

      And WHEREAS, this nomic began as a humble and nameless nomic,
      known unofficially as yoyo, after the mailing list it was played
      on, until its Players, much later, gave it its OFFICIAL NAME of
      Agora,

      And WHEREAS, Agora has now become the wisest, noblest, eldest,
      and most interesting of all active email nomics, due to the hard
      work and diligence of Agorans as well as the frequent advice of
      Agoraphobes,

      And WHEREAS, Agorans desire to joyously commemorate Agora's
      founding,

      BE IT THEREFORE RESOLVED that Agora's Birthday is defined to be
      the entire day of June 30, GMT +1200, of each year.

      BE IT FURTHERMORE RESOLVED that Agora's Unbirthday is defined to
      be the entire day of December 30, GMT +1200, of each year; but,
      since that falls within a Holiday, is observed during the entire
      days of January 12 through 14, GMT +1200, of each year.

History:
Created by Proposal 3513 (Chuck), Jun. 16 1997
Amended(1) by Proposal 3530 (Chuck), Jun. 30 1997, substantial
Amended(2) by Proposal 3533 (General Chaos), Jul. 15 1997, substantial
Amended(3) by Proposal 3543 (Harlequin), Aug. 17 1997, substantial
Amended(4) by Proposal 3897 (harvel), Aug. 27 1999
Amended(5) by Proposal 3915 (harvel), Sep. 27 1999
Amended(6) by Proposal 3940 (Blob), Nov. 15 1999
Amended(7) by Proposal 4018 (Kelly), Jun. 21 2000
Amended(8) by Proposal 4099 (Murphy), Jan. 15 2001
Amended(9) by Proposal 4147 (Wes), 13 May 2001
Amended(10) by Proposal 4159 (Kelly), 5 June 2001
Amended(11) by Proposal 4367 (Steve), 23 August 2002
Amended(12) by Proposal 4376 (Steve), 6 September 2002
Amended(13) by Proposal 4486 (Michael), 24 April 2003
Amended(14) by Proposal 4743 (Manu), 5 May 2005
Amended(???) by Proposal 4839 (Goethe), 2 October 2005
Amended(???) by Proposal 4866 (Goethe), 27 August 2006
Amended(15) by Proposal 4880 (Murphy), 22 January 2007
Amended(16) by Proposal 4887 (Murphy), 22 January 2007
Amended(17) by Proposal 5364 (Murphy), 20 December 2007

----------------------------------------------------------------------

Rule 2355/0 (Power=1.1)
For It Was Not To B

      WHEREAS B Nomic, a well-played Nomic, did claim to pass a
      proposal directing a player to end the game, where that person
      fled B in hopes of never having to use that terrible power; and

      WHEREAS B Nomic was in fact recently discovered to have been
      locked in perpetual Emergency since 2002, such that its game can
      never advance; and

      WHEREAS B Nomic's imagined gameplay did at one point submit to
      being a Protectorate of Agora, indicating its consent to be
      ruled by the most glorious of Nomic; and

      WHEREAS B Nomic's imagined gameplay did later adopt the entire
      Ruleset of Agora, indicating true reverence as imitation is the
      sincerest form of flattery; and

      WHEREAS B Nomic was renowned for its pedantry, a true virtue
      among Nomics; and

      WHEREAS Agora should honour its Protectorates, even those that
      departed it and, in fact, was never actually able to submit to
      Agora's rule; and

      WHEREAS Agora should honour any Nomic deserving of true
      greatness;

      BE IT HEREBY PROCLAIMED that the entirety of June 5th in each
      year be observed in Agora as B Nomic Memorial Day; and

      BE IT ALSO HEREBY PROCLAIMED that on B Nomic Memorial Day,
      players should exhibit legendary pedantry and attempt to find
      places in Agoran history where the rules were misapplied with
      still-lasting effects.

History:
Created by Proposal 7120 (scshunt), 10 September 2011

----------------------------------------------------------------------

Rule 2029/0 (Power=4)
Town Fountain

                      /\   /\
                      / \ / \
                         T
                        his
                      Power-4
               Rule (the first ever)
                was placed to honor
           The Agoran  Spirit Of The Game
           by Goethe, Steve, Murphy, root
           and OscarMeyr, Scamsters. Look
           on our works, ye Marvy, but do
      always Dance a Powerful Dance.  Hail Eris!

[CFJ 1881 (called 25 January 2008): This rule does not impose an
obilgation to always Dance a Powerful Dance, because "Marvy" is
currently undefined.]

[CFJ 1736 (called 23 August 2007): Failing to hail Eris does not
necessarily constitute a violation of this rule.]

History:
Created by Proposal 4329 (Goethe), 9 June 2002

----------------------------------------------------------------------

======================================================================
Garbage Bin
      CFJ annotations that do not currently apply to any specific
      rules, but are likely to do so in the future, at which point
      they can be reattached.
----------------------------------------------------------------------

Contracts / Binding Agreements

[CFJ 1892 (called 2 February 2008): An agreement that is not binding
is thereby not a contract.]

[CFJ 1901 (called 4 February 2008): An agreement that is binding is
thereby a contract, even if it doesn't impose any obligations.]

[CFJ 1892 (called 2 February 2008): An agreement's text can disclaim
contract/binding status, thereby nullifying itself, by explicitly
describing itself as a non-contract or as non-binding.]

[CFJ 1872 (called 15 January 2008): Being a player is not a
prerequisite for becoming party to a contract.]

[CFJ 1796 (called 14 November 2007): If a person announces that e
agrees to be bound by a particular text as a contract, without saying
who this agreement is with, and the contract text does not regulate
who can become a party to it, then any person can become a party to
the contract by announcement.]

[CFJ 1455 (called 14 March 2003): A contract cannot cause an
otherwise-insignificant action by a non-party to constitute consent to
be bound by the contract.]

[CFJ 1856 (called 29 December 2007): A contract is null and void if
the courts do not have sufficient evidence that a person's
contract-related rights (in Rule 101) are not being infringed.  This
includes evidence that the party to the contract has reviewed the
rules and has direct prior knowledge of the fora.]

[CFJ 1686 (called 7 June 2007): A person who is not a party to an
agreement categorically cannot violate it.]

[CFJ 1752 (called 28 September 2007): Deregistration does not
implicitly cause the ex-player to leave a contract.]

[CFJ 1842 (called 20 December 2007): A contract may use retroactive
operations internally for the purposes of determining obligations of
the parties, but such legal fictions do not affect Agora as a whole.]

[CFJ 1836 (called 18 December 2007): A contract cannot have
retroactive effect.]

[CFJ 1843 (called 20 December 2007): Becoming a party to a contract
cannot occur retroactively, for the purposes of determining
justiciability of the contract.]

[CFJ 1816 (called 2 December 2007): A contract is not generally able
to define terms used by the rules.]

[CFJ 1819 (called 3 December 2007): A contract is not able to create
new ways of winning the game.]

[CFJ 1835 (called 18 December 2007): An authorisation granted by a
party in a contract takes precedence over a unilateral statement by
that party that purports to cancel that authorisation.]

[CFJ 1921 (called 2 April 2008): Agreements with informal phrasing can
be considered contracts, but only when made in a medium where lying is
against the Rules (i.e. a public forum).]

[CFJ 2302 (called 7 December 2008): The scope of the text of a
contract is limited compared to that of a rule; in particular, a
contract cannot cause a paradox by setting undecidable conditions on
joining it.]

----------------------------------------------------------------------

Truthfulness

[CFJ 1739 (called 29 August 2007): A quotation can result in a
violation of Rule 2215 (then 2149), depending on the context of the
rest of the message.]

[CFJ 1849 (called 21 December 2007): Violation of Rule 2215 (then
2149) can occur without any intent to misdirect.]

[CFJ 1887 (called 30 January 2008): Publicly making the statement
"This statement is a lie." would most likely be a violation of rule
2215 (then 2149), because it is logically indeterminate and so making
it would not be telling the truth, and its logical indeterminacy would
be understood by any reasonable player.]

[CFJ 2103 (called 21 July 2008): Making the statement "I lie." is not
a violation of Rule 2215 if the author is lying down.]

[CFJ 2399 (called 4 March 2009): Even if a type of behavior is likely
to cause false statements to be accidentally published, a person does
not violate Rule 2215 by engaging in it if there is no specific
statement e believes is false.]

----------------------------------------------------------------------

Miscellaneous

[CFJ 2276a (called 20 November 2008): When a rule allows, as an
action, a quantity to be increased which is defined elsewhere as a
fixed value, and that action is taken, the rule thereby redefines the
quantity as one more than it would otherwise be.]

----------------------------------------------------------------------

END OF THE FULL LOGICAL RULESET
@


1.1586
log
@effects of proposal 7159
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7159
Last change to this ruleset: by Proposal 7159
d8 1
a8 1
Highest Rule ID number ever assigned: 2358
d14 1
a14 1
Current total number of rules: 100
a22 1
      23 with Power=1
d24 1
d59 1
d659 11
@


1.1585
log
@effects of proposal 7152
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7152
Last change to this ruleset: by Proposal 7152
d6 1
a6 1
Last updated: 2 February 2012
d3019 1
a3019 1
Rule 2352/1 (Power=1)
a3024 4
      Any player CAN, with Agoran Consent, cause Agora to post a blog
      post (specifying its title, text, and list of categories) or
      comment (specifying its text) to BlogNomic.

d3028 1
@


1.1584
log
@effects of proposal 7151
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7151
Last change to this ruleset: by Proposal 7151
d4592 1
a4592 1
Rule 911/46 (Power=1.7)
d4661 1
a4661 1
      and remains so until the the appeal case is judged.
d4735 1
@


1.1583
log
@effects of proposal 7150
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7150
Last change to this ruleset: by Proposal 7150
d2017 1
a2017 1
Rule 1769/9 (Power=3)
d2022 4
a2051 4
      The period each year from midnight GMT on the morning of 24
      December to the beginning of the first Agoran week to begin
      after 2 January is a Holiday.

d2074 1
@


1.1582
log
@effects of proposal 7149
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7149
Last change to this ruleset: by Proposal 7149
d2017 1
a2017 1
Rule 1769/8 (Power=3)
d2023 3
a2025 3
      proposals, and judges SHALL NOT be assigned to any judicial
      case, and judges SHALL NOT assign judgement to any judicial
      case.
d2073 1
@


1.1581
log
@effects of proposal 7148
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7148
Last change to this ruleset: by Proposal 7148
d6 1
a6 1
Last updated: 29 January 2012
d2591 1
a2591 1
Rule 2333/2 (Power=1)
d2603 1
a2603 1
      persons "win the contest".  Upon an announcement by the
d2634 1
@


1.1580
log
@effects of proposal 7147
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7147
Last change to this ruleset: by Proposal 7147
d1558 1
a1558 1
Rule 2343/6 (Power=1.7)
d1572 10
d1610 1
@


1.1579
log
@effects of proposal 7146
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7146
Last change to this ruleset: by Proposal 7146
d1558 1
a1558 1
Rule 2343/5 (Power=1.7)
d1575 3
a1577 3
      not already won via the same events, the person(s) Win the Game.
      There is no other method of winning the game.  Winning the game
      does not cause Agora to end.
d1599 1
@


1.1578
log
@effects of proposal 7141
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7141
Last change to this ruleset: by Proposal 7141
d6 1
a6 1
Last updated: 7 December 2011
d1558 1
a1558 1
Rule 2343/4 (Power=1.7)
d1561 10
a1570 8
      A Victory Condition is a condition explicitly defined by the
      rules as a victory condition.  Victory Conditions are satisfied
      instantaneously, not continuously.  A Victory Announcement is a
      published statement labeled as a Victory Announcement that
      states clearly that a specified person or persons have satisfied
      a specified and rules-defined victory condition (and explicitly
      and clearly states which persons and which victory condition).
      A Victory Announcement is self-ratifying.
d1598 1
d4254 1
a4254 1
Rule 1504/56 (Power=2)
d4345 3
a4347 1
        two months after that time.
d4446 1
@


1.1577
log
@effects of proposal 7139
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7139
Last change to this ruleset: by Proposal 7139
d1316 1
a1316 1
Rule 2139/3 (Power=2)
d1337 3
d1374 1
@


1.1576
log
@effects of proposal 7138
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7138
Last change to this ruleset: by Proposal 7138
d1554 1
a1554 1
Rule 2343/3 (Power=1.7)
d1558 2
a1559 1
      rules as a victory condition.  A Victory Announcement is a
d1591 1
@


1.1575
log
@effects of proposal 7136
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7136
Last change to this ruleset: by Proposal 7136
d8 1
a8 1
Highest Rule ID number ever assigned: 2357
d14 1
a14 1
Current total number of rules: 99
d23 1
a23 1
      22 with Power=1
d61 1
d697 16
@


1.1574
log
@effects of proposal 7135
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7135
Last change to this ruleset: by Proposal 7135
d6 1
a6 1
Last updated: 6 November 2011
d14 1
a14 1
Current total number of rules: 100
d23 1
a23 1
      23 with Power=1
a113 1
      Rule 2353: The Conductor
a2993 12
Rule 2353/0 (Power=1)
The Conductor

      The Conductor is an office; its holder is responsible for
      tracking any switches that would otherwise lack an officer to
      track them.

History:
Created by Proposal 7099 (Murphy), 23 July 2011

----------------------------------------------------------------------

@


1.1573
log
@effects of proposal 7134
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7134
Last change to this ruleset: by Proposal 7134
d84 1
a84 1
      Rule 2343: Victory Cases
d1538 2
a1539 2
Rule 2343/2 (Power=1.7)
Victory Cases
d1541 27
a1567 32
      Victory cases are a subclass of judicial cases. Any person CAN
      initiate a victory case by announcement, specifying a person
      (the Enlaureled) that allegedly satisfied a Victory Condition,
      the Victory Condition allegedly satisfied, and the means by
      which it was allegedly satisfied.

      The entities eligible to be assigned as judges of a victory case
      are those judicial panels consisting of three first-class
      players, none of them having called the case or been
      disqualified as below. A player can be disqualified from judging
      a victory case with Agoran Consent. The CotC SHOULD NOT assign a
      panel to a victory case if there is a pending intent to
      disqualify one of its members unless it is clear that the intent
      will fail. Players SHOULD be disqualified only if they have a
      vested interest in the victory, such as having been a
      co-scammer.

      The valid judgements for a victory case are GLORY, appropriate
      if the Victory Condition was satisfied as described and a
      judgment of GLORY has not already been reached on an earlier
      case over substantially the same victory, and SHAME, appropriate
      otherwise.

      When a judgment of GLORY has continuously been in effect for two
      weeks, the Enlaureled is deemed to have won the game as
      specified.  The Herald shall forthwith award the patent title
      Champion to the winner. Winning the game does not cause Agora to
      end.

      An appeal concerning any assignment of judgement in a victory
      case within the past week CAN be initiated by the Enlaureled by
      announcement.
d1573 1
@


1.1572
log
@effects of proposal 7133
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7133
Last change to this ruleset: by Proposal 7133
d8 1
a8 1
Highest Rule ID number ever assigned: 2356
d14 1
a14 1
Current total number of rules: 99
d20 1
a20 1
      24 with Power=2
d60 1
d673 24
@


1.1571
log
@effects of proposal 7132
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7132
Last change to this ruleset: by Proposal 7132
d2958 1
a2958 1
Rule 2352/0 (Power=1)
d2964 3
a2966 3
      When the office of Ambassador first becomes filled, the holder
      SHALL as soon as possible attempt to cause Agora to become a
      player of BlogNomic.
d2970 1
@


1.1570
log
@Rule 2330 repealed by Proposal 7131 (Murphy), 6 November 2011; Rule 2349 repealed by Proposal 7131 (Murphy), 6 November 2011; Rule 2331 repealed by Proposal 7131 (Murphy), 6 November 2011; Rule 2335 repealed by Proposal 7131 (Murphy), 6 November 2011; Rule 2336 repealed by Proposal 7131 (Murphy), 6 November 2011; Rule 2345 repealed by Proposal 7131 (Murphy), 6 November 2011; Rule 2346 repealed by Proposal 7131 (Murphy), 6 November 2011
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7131
Last change to this ruleset: by Proposal 7131
d8 1
a8 1
Highest Rule ID number ever assigned: 2355
d14 1
a14 1
Current total number of rules: 98
d23 1
a23 1
      22 with Power=1
d86 1
d1624 12
@


1.1569
log
@effects of proposal 7128
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7128
Last change to this ruleset: by Proposal 7128
d14 1
a14 1
Current total number of rules: 105
d20 1
a20 1
      29 with Power=2
d23 1
a23 1
      24 with Power=1
a82 5
      Rule 2330: Points
      Rule 2349: Spending Points
      Rule 2331: Proposal Points
      Rule 2335: Judge Points
      Rule 2336: Officer Points
a85 2
      Rule 2345: Bets
      Rule 2346: Betting Markets
a1511 100
Rule 2330/2 (Power=2)
Points

      Points are a currency. Ownership of points is restricted to
      Players. A player's score is the number of points e owns.
      Changes to point holdings are secured.

      The Scorekeepor is an office, and the recordkeepor of points.

      The maximum FINE amount for points is 25.

History:
Created by Proposal 6989 (Wooble), 10 April 2011
Amended(1) by Proposal 7008 (Walker), 20 April 2011
Amended(2) by Proposal 7011 (G.), 20 April 2011

----------------------------------------------------------------------

Rule 2349/0 (Power=2)
Spending Points

      Where the Rules state that a player CAN perform an action 'as a
      Spending Action', this means that the player CAN perform this
      action by destroying a number of Points in eir possession equal
      to the cost of that action, provided they have enough Points.
      Each Point can only count towards one Spending Action. If a
      player CAN perform an action by spending 0 points, e CAN perform
      it by announcement.

      Each spending action has a base cost, which is a non-negative
      integer defaulting to five. The base cost of each spending
      action is tracked by the Scorekeepor, and players CAN change it
      without two objections. The cost of a spending action is
      generally its base cost, subject to modification by other Rules.

History:
Created by Proposal 7074 (Walker), 16 June 2011

----------------------------------------------------------------------

Rule 2331/2 (Power=2)
Proposal Points

      When the Agoran Decision to adopt a proposal is resolved, if the
      outcome is ADOPTED, the author of the proposal gains 2  points
      for each valid vote FOR the proposal, less 1 point for each
      valid vote AGAINST the proposal. Each co-author of the proposal
      gains 2 points.

History:
Created by Proposal 6989 (Wooble), 10 April 2011
Amended(1) by Proposal 7025 (Murphy), 5 May 2011
Amended(2) by Proposal 7053 (omd), 26 May 2011

----------------------------------------------------------------------

Rule 2335/1 (Power=2)
Judge Points

      When a judge assigns a judgement to a non-appeal judicial case
      within any time limits for doing so, e gains 5 points, unless e
      has already assigned judgement to the same case before.

      If an appeals panel assigns a judgement with prejudice, then any
      member of the panel CAN, within a week of the disposition
      judgement being assigned, by announcement, destroy any points
      the prior judge earned for judging the case.

      When an appeals panel assigns a judgement to a case within any
      time limits for doing so, each member of the panel gains 2
      points.

History:
Created by Proposal 7007 (Walker), 20 April 2011
Amended(1) by Proposal 7043 (Walker), 16 May 2011

----------------------------------------------------------------------

Rule 2336/1 (Power=2)
Officer Points

      Weekly Salary is an office switch, tracked by the Scorekeepor,
      with values of the non-negative integers (default zero). At the
      beginning of each week, each officer gains a number of points
      equal to the Weekly Salary of eir office.

      Monthly Salary is an office switch, tracked by the Scorekeepor,
      with values of the non-negative integers (default zero). At the
      beginning of each month, each officer gains a number of points
      equal to the Monthly Salary of eir office.

      Players can change the Weekly or Monthly Salary of an office
      without two objections or with Agoran Consent.

History:
Created by Proposal 7009 (Walker), 20 April 2011
Amended(1) by Proposal 7035 (scshunt), 16 May 2011

----------------------------------------------------------------------

a1622 83
Rule 2345/1 (Power=1)
Bets

      The betting period for a decision on the adoption of a proposal
      or a degree begins when the proposal or thesis is submitted; the
      betting period for an election begins when the nomination period
      begins. The betting period for each decision ends when the
      decision is initiated.

      During the betting period for a given Agoran Decision, each
      active player (the Better) CAN submit a Bet privately to the
      vote collector for that decision.

      To be valid, a Bet must
      a) consist of an indication of which outcome the Better thinks
         Agora will select in a specified decision,
      b) clearly indicate the number of Points staked in the Bet - a
         number of Points less than or equal to the number of Points
         the Better owns,
      c) not be sent to anyone other than the Better and the vote
         collector,
      d) not be submitted by the vote collector, and
      e) be submitted during the betting period for the decision.

      The validity of a Bet is measured when its betting market is
      resolved. Only the last Bet submitted by each player (which
      would otherwise be valid) is valid.

      Players SHALL NOT reveal the details of any Bet to any person
      other than the vote collector before the betting period has
      finished, except where allowed by this Rule; violating this
      requirement is the Class-6 Crime of Collusion.

      If the vote collector for a decision changes before the decision
      has been resolved, and one or more Bets have been submitted for
      the decision, then the previous vote collector SHALL inform the
      new collector of these Bets and their contents privately, before
      the decision is resolved. The previous vote collector becomes
      eligible to submit Bets for the decision if the betting period
      has not ended, and any previous Bets submitted by the new vote
      collector become invalid.

History:
Created by Proposal 7044 (Walker), 16 May 2011
Amended(1) by Proposal 7076 (omd), 16 June 2011

----------------------------------------------------------------------

Rule 2346/0 (Power=1)
Betting Markets

      There is a betting market on a decision if
      a) more than one player has submitted a valid Bet on the
         decision,
      b) more than one outcome was Betted on, and
      c) at least one of the Bets was for the correct outcome.

      After a decision has been resolved, the vote collector CAN
      resolve the betting market (if any) on the decision, and SHALL
      do so as soon as possible.

      The resolution of a betting market reveals the outcome betted on
      by each Better, and the number of Points they staked, in valid
      Bets. Upon the valid resolution of a betting market
      a) any Points staked on an incorrect outcome are destroyed
      b) an equal (or less due to rounding) number of Points are
         awarded to the player(s) who Betted on the correct outcome,
         such that the proportion of Points gained by each winning
         Better is directly proportional to the number of Points they
         staked, rounded down as necessary.

      To be valid, the resolution must specify how many Points are
      lost and gained by each Better.

      The resolution of a betting market constitutes a self-ratifying
      claim that the Bets in the resolution are valid, and that no
      other valid Bets were submitted for the decision.

History:
Created by Proposal 7044 (Walker), 16 May 2011

----------------------------------------------------------------------

@


1.1568
log
@effects of proposal 7120
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7120
Last change to this ruleset: by Proposal 7120
d6 1
a6 1
Last updated: 16 October 2011
d663 1
a663 1
Rule 2351/0 (Power=3)
d669 1
a669 1
      not any player of it, can make arbitrary changes to the
d674 1
@


1.1567
log
@effects of proposal 7114; Rule 2332 repealed by Proposal 7114 (scshunt), 20 August 2011
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7114
Last change to this ruleset: by Proposal 7114
d6 1
a6 1
Last updated: 20 August 2011
d8 1
a8 1
Highest Rule ID number ever assigned: 2354
d14 1
a14 1
Current total number of rules: 104
d24 1
d170 1
d5400 42
@


1.1566
log
@effects of proposal 7118
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7118
Last change to this ruleset: by Proposal 7118
d14 1
a14 1
Current total number of rules: 105
d20 1
a20 1
      30 with Power=2
a87 1
      Rule 2332: Winning by Points
a1658 19
Rule 2332/3 (Power=2)
Winning by Points

      A player CAN destroy 250 points in the possession of any
      indicated player to cause the indicated player to satisfy the
      Victory Condition of Accumulation.

      When a player satisfies the Victory Condition of Accumulation,
      half of every other player's points (rounded down) are
      destroyed.

History:
Created by Proposal 6989 (Wooble), 10 April 2011
Retitled and amended(1) by Proposal 7039 (scshunt), 16 May 2011
Amended(2) by Proposal 7061 (G.), 16 June 2011
Amended(3) by Proposal 7062 (G.), 16 June 2011

----------------------------------------------------------------------

@


1.1565
log
@effects of proposal 7117
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7117
Last change to this ruleset: by Proposal 7117
d4413 1
a4413 1
Rule 1504/55 (Power=2)
d4433 1
a4433 1
       (b) the breach occurred within 90 days prior to the case being
d4602 1
@


1.1564
log
@effects of proposal 7112
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7112
Last change to this ruleset: by Proposal 7112
d8 1
a8 1
Highest Rule ID number ever assigned: 2353
d14 1
a14 1
Current total number of rules: 104
d23 1
a23 1
      23 with Power=1
d93 1
d1830 24
@


1.1563
log
@effects of proposal 7101
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7101
Last change to this ruleset: by Proposal 7101
d6 1
a6 1
Last updated: 31 July 2011
d647 1
a647 1
Rule 2339/0 (Power=1)
d652 3
d657 1
@


1.1562
log
@effects of proposal 7100
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7100
Last change to this ruleset: by Proposal 7100
d1674 1
a1674 1
Rule 2337/3 (Power=3)
d1690 3
d1706 1
@


1.1561
log
@effects of proposal 7099
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7099
Last change to this ruleset: by Proposal 7099
d1674 1
a1674 1
Rule 2337/2 (Power=3)
d1681 1
a1681 1
      promises is limited to persons and the Tree.
d1702 1
d1706 1
a1706 1
Rule 2338/1 (Power=3)
d1709 3
a1711 3
      A Player CAN cash a promise in eir possession by announcing that
      e does so, provided either that all conditions required to be
      true for the promise to be cashed are true, or it has no such
d1734 1
@


1.1560
log
@effects of proposal 7098
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7098
Last change to this ruleset: by Proposal 7098
d8 1
a8 1
Highest Rule ID number ever assigned: 2352
d14 1
a14 1
Current total number of rules: 103
d23 1
a23 1
      22 with Power=1
d118 1
d3132 12
@


1.1559
log
@effects of proposal 7097
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7097
Last change to this ruleset: by Proposal 7097
d1611 1
a1611 1
Rule 2343/1 (Power=1.7)
d1614 5
a1618 5
      Victory cases are a subclass of judicial cases. Any person
      believing emself to have satisfied a Victory Condition may
      initiate a victory case with support, indicating the precise
      Victory Condition which e believes to have satisfied and how e
      believes e satisfied it.
d1638 8
a1645 3
      weeks, the caller is deemed to have won the game as specified.
      The Herald shall forthwith award the patent title Champion to
      the winner. Winning the game does not cause Agora to end.
d1650 1
@


1.1558
log
@effects of proposal 7095
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7095
Last change to this ruleset: by Proposal 7095
d8 1
a8 1
Highest Rule ID number ever assigned: 2351
d14 1
a14 1
Current total number of rules: 102
d23 1
a23 1
      21 with Power=1
d117 1
d3110 15
@


1.1557
log
@effects of proposal 7088
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7088
Last change to this ruleset: by Proposal 7088
d8 1
a8 1
Highest Rule ID number ever assigned: 2350
d14 1
a14 1
Current total number of rules: 101
d19 1
a19 1
      37 with Power=3
d58 1
a136 1
      The Promotor
d655 14
@


1.1556
log
@effects of proposal 7087
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7087
Last change to this ruleset: by Proposal 7087
d139 1
a139 1
      Rule 1698: Agora Is a Nomic
d4041 2
a4042 2
Rule 1698/2 (Power=3)
Agora Is a Nomic
d4044 10
a4053 12
      In the interest of safeguarding Agora's nomic-ness, if a change
      to the gamestate would otherwise make it IMPOSSIBLE to make
      arbitrary rule changes and/or adopt arbitrary proposals within a
      four-week period by any combinations of actions by players, then
      that change is canceled and does not occur, any rule to the
      contrary notwithstanding.

      For the purposes of this rule, the effects of a single proposal,
      including any actions performed automatically as a consequence
      of the proposal's adpotion, constitute a single change to the
      gamestate and will all be canceled if the proposal would leave
      the game as something other than a Nomic.
d4060 1
@


1.1555
log
@effects of proposal 7086
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7086
Last change to this ruleset: by Proposal 7086
d2670 1
a2670 1
Rule 2333/1 (Power=1)
d2682 5
a2686 3
      one or more persons win the contest. When one or more persons
      win a contest, those persons satisfy the Victory Condition of
      Victory.
d2712 1
@


1.1554
log
@effects of proposal 7084
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7084
Last change to this ruleset: by Proposal 7084
d3717 1
a3717 1
Rule 2350/0 (Power=3)
a3721 6
      When a person creates a proposal, e SHOULD ensure that it
      specifies one or more changes to the gamestate.  Except as
      prohibited by other rules, a proposal that takes effect CAN, as
      part of its effect, apply the changes that it specifies.  If the
      proposal cannot make some such changes, this does not preclude
      the other changes from taking place.
d3737 1
d3741 1
a3741 1
Rule 106/33 (Power=3)
d3748 9
a3756 5
      and then it takes effect.

      A proposal with a decision on which the option selected by Agora
      is not ADOPTED does not take effect, rules to the contrary
      notwithstanding.
d3841 1
@


1.1553
log
@effects of proposal 7083
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7083
Last change to this ruleset: by Proposal 7083
d6 1
a6 1
Last updated: 5 July 2011
d602 1
a602 1
Rule 103/9 (Power=2)
d609 3
a611 3
      The Speaker is the single first-class player who holds the most
      Postulated Offices, or if there is no such player, the player
      who was most recently Speaker.
d641 1
@


1.1552
log
@effects of proposal 7082
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7082
Last change to this ruleset: by Proposal 7082
d6 1
a6 1
Last updated: 4 July 2011
d8 1
a8 1
Highest Rule ID number ever assigned: 2349
d14 1
a14 1
Current total number of rules: 100
d19 2
a20 2
      35 with Power=3
      31 with Power=2
d133 1
d135 2
a136 1
      Rule 1607: The Promotor
d3716 2
a3717 2
Rule 106/32 (Power=3)
Adopting Proposals
d3723 4
a3726 4
      prohibited by other rules, a proposal that takes effect CAN and
      does, as part of its effect, apply the changes that it
      specifies.  If the proposal cannot make some such changes, this
      does not preclude the other changes from taking place.
a3735 13
      A player specifically permitted by the Rules to distribute a
      Proposal CAN distribute the proposal by publishing it with the
      clear intent of distributing it.  When a proposal is
      distributed, it is removed from the Proposal Pool.  The
      distribution of a proposal initiates the Agoran decision of
      whether to adopt the proposal, as described elsewhere.  Removing
      a proposal from the Pool by a means other than initiating an
      Agoran Decision to adopt it is secured.

      If there is a Proposal in the Pool that it would otherwise be
      IMPOSSIBLE for any active player to distribute, then any player
      CAN distribute that Proposal Without 3 Objections.

d3740 13
a3752 12
      Determining whether to adopt a proposal is an Agoran decision.
      By default, this decision has an adoption index of 1.0 and is
      Ordinary; if the proposer specified valid, non-"none" values for
      the adoption index and/or Chamber when submitting the proposal,
      those values are set at the initiation of the decision.
      Changing either value is secured with a power threshold of 2.
      The vote collector for this decision is the Assessor.

      If the option selected by Agora on this decision is ADOPTED,
      then the proposal is adopted, and unless other rules prevent it
      from taking effect, its power is set to the minimum of four and
      its adoption index, and then it takes effect.
d3840 1
d3844 2
a3845 2
Rule 1607/32 (Power=2)
The Promotor
d3850 8
a3857 7
      Priority is an undistributed proposal switch with values of the
      integers (default zero), tracked by the Promotor. A player CAN,
      as a Spending Action, increase or decrease the Priority of a
      specified proposal by one.

      The Legislative Volume is 5 when the Speed is Slow, 10 when it
      is Normal and 20 when it is Fast.
d3861 3
a3863 7
      as part of eir weekly duties, out of all of the proposals which
      were in the pool at the beginning of the week, distribute the X
      proposals with the greatest Priority, breaking ties in favour of
      those proposals which were submitted first, where X is the
      minimum of the Legislative Volume and the number of such
      proposals. The Promotor SHALL NOT distribute any other
      proposals.
d3868 4
d3947 1
d3951 1
a3951 1
Rule 1950/22 (Power=3)
d3961 8
d3976 6
a3984 6
      The eligible voters on a decision with an adoption index are
      those entities that were active first-class players at the start
      of its voting period.  Setting an entity's voting limit on such
      a decision is secured with a power threshold of 2 if the
      decision is Ordinary, or 3 otherwise.

d4012 1
@


1.1551
log
@effects of proposal 7081
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7081
Last change to this ruleset: by Proposal 7081
d1649 1
a1649 1
Rule 2337/1 (Power=3)
d1668 3
a1670 2
      The creation, transferring, cashing, and destruction of promises
      is secured.
d1676 1
@


1.1550
log
@effects of proposal 7080
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7080
Last change to this ruleset: by Proposal 7080
d6 1
a6 1
Last updated: 25 June 2011
d3712 1
a3712 1
Rule 106/31 (Power=3)
d3719 4
a3722 4
      prohibited by other rules, a proposal that takes effect CAN, as
      part of its effect, apply the changes that it specifies.  If the
      proposal cannot make some such changes, this does not preclude
      the other changes from taking place.
d3847 1
@


1.1549
log
@effects of proposal 7078
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7078
Last change to this ruleset: by Proposal 7078
d2665 1
a2665 1
Rule 2333/0 (Power=1)
d2677 3
a2679 5
      persons "win the contest".  Upon an announcement by the
      contestmaster that one or more persons satisfy those conditions,
      all those persons win the game of Agora.  (This does not end the
      game.)  Intentionally making a false such announcement is the
      Class-4 Crime of Gaming the System.
d2704 1
@


1.1548
log
@effects of proposal 7077
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7077
Last change to this ruleset: by Proposal 7077
d1593 1
a1593 1
Rule 2343/0 (Power=1.7)
d1613 5
a1617 6
      A victory case has a judicial question on ascendancy, which is
      always applicable. The valid judgments for this question are
      GLORY, appropriate if the Victory Condition was satisfied as
      described and a judgment of GLORY has not already been reached
      on an earlier case over substantially the same victory, and
      SHAME, appropriate otherwise.
d1626 1
d4181 1
a4181 1
Rule 591/34 (Power=1.7)
d4216 1
a4216 1
        judicial case
d4318 1
d4641 1
a4641 1
Rule 911/45 (Power=1.7)
d4712 1
a4712 1
      The judge of a previously-appealed question SHALL NOT assign the
d4717 3
a4719 3
      A person SHALL NOT appeal a judgement (except on a question of
      sentencing) unless e reasonably believes that the judgement
      might be inappropriate.
d4783 1
@


1.1547
log
@effects of proposal 7069
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7069
Last change to this ruleset: by Proposal 7069
d3362 1
a3362 1
Rule 683/16 (Power=3)
d3367 1
a3367 1
      indicating which two of the available options e selects.  To be
d3426 1
@


1.1546
log
@effects of proposal 7074 (out of order)
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7074
Last change to this ruleset: by Proposal 7074
d3850 1
a3850 1
Rule 1607/31 (Power=2)
d3856 8
d3866 7
a3872 3
      as part of eir weekly duties, distribute all proposals in the
      Proposal Pool that were in the Pool at the beginning of that
      week.
d3950 2
a3951 1
Amended(31) by Proposal 7033 (omd), 16 May 2011
@


1.1545
log
@effects of proposal 7076
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7076
Last change to this ruleset: by Proposal 7076
d8 1
a8 1
Highest Rule ID number ever assigned: 2348
d14 1
a14 1
Current total number of rules: 99
d20 1
a20 1
      30 with Power=2
d82 1
d1511 22
@


1.1544
log
@effects of proposal 7075
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7075
Last change to this ruleset: by Proposal 7075
d1686 1
a1686 1
Rule 2345/0 (Power=1)
d1714 4
a1717 4
      Players SHALL NOT reveal the existence or details of any Bet to
      any person other than the vote collector before the betting
      period has finished, except where allowed by this Rule;
      violating this requirement is the Class-6 Crime of Collusion.
d1730 1
@


1.1543
log
@effects of proposal 7073
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7073
Last change to this ruleset: by Proposal 7073
d3995 1
a3995 1
Rule 1698/1 (Power=3)
d4005 6
d4015 1
@


1.1542
log
@effects of proposal 7072
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7072
Last change to this ruleset: by Proposal 7072
d2196 1
a2196 1
Rule 478/29 (Power=3)
d2228 1
a2228 1
      message,.
d2443 1
@


1.1541
log
@effects of proposal 7067
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7067
Last change to this ruleset: by Proposal 7067
d4594 1
a4594 1
Rule 911/44 (Power=1.7)
d4668 1
a4668 2
      prohibition is the Class-N Crime of Lazy Judging, where N is the
      judge's rank when e so judged.
d4735 1
@


1.1540
log
@effects of proposal 7065
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7065
Last change to this ruleset: by Proposal 7065
d8 1
a8 1
Highest Rule ID number ever assigned: 2347
d14 1
a14 1
Current total number of rules: 98
d23 1
a23 1
      20 with Power=1
d54 1
d575 10
@


1.1539
log
@effects of proposal 7064
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7064
Last change to this ruleset: by Proposal 7064
d4561 1
a4561 1
Rule 2318/1 (Power=1.7)
d4568 2
a4569 1
      CAN file a Motion to Reconsider the case with 2 Support.
d4579 1
@


1.1538
log
@effects of proposal 7063
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7063
Last change to this ruleset: by Proposal 7063
d968 1
a968 1
Rule 2340/0 (Power=1)
d980 3
d985 1
@


1.1537
log
@effects of proposal 7062
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7062
Last change to this ruleset: by Proposal 7062
d2033 1
a2033 1
Rule 2347/0 (Power=2)
d2036 3
a2038 3
      The Speed switch is a single switch, tracked by the Assessor,
      with values of Slow, Normal (default) and Fast. The Speed switch
      is secured.
d2048 1
@


1.1536
log
@effects of proposal 7061
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7061
Last change to this ruleset: by Proposal 7061
d1592 1
a1592 1
Rule 2332/2 (Power=2)
d1599 4
d1607 1
@


1.1535
log
@expand annotation
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7053
Last change to this ruleset: by Proposal 7053
d6 1
a6 1
Last updated: 31 May 2011
d1592 1
a1592 1
Rule 2332/1 (Power=2)
d1595 2
a1596 1
      A player CAN destroy 250 points in eir possession to satisfy the
d1602 1
@


1.1534
log
@effects of proposal 7053
@
text
@d2847 2
a2848 1
from rules and circumstances, not just directly imposed by the rules.]
@


1.1533
log
@low-entropy annotation
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7050
Last change to this ruleset: by Proposal 7050
d6 1
a6 1
Last updated: 17 May 2011
d1495 1
a1495 1
Rule 2331/1 (Power=2)
d1498 5
a1502 18
      When the Agoran Decision to adopt a proposal is resolved:

      * if the outcome is ADOPTED, the author of the proposal gains 2
        points for each valid vote FOR the proposal, less 1 point for
        each valid vote AGAINST the proposal. Each co-author of the
        proposal gains 2 points.

      * if the outcome is REJECTED, the author of the proposal loses 2
        points for each valid vote AGAINST the proposal, less 1 point
        for each valid vote FOR the proposal. If e would lose fewer
        than 2 points, e loses 2 points.

      * if the outcome is FAILED QUORUM, the author of the proposal
        gains 2 points.

      However, if the author clearly identified the proposal as
      disinterested when e submitted it, then no one gains or loses
      any points due to its outcome.
d1507 1
@


1.1532
log
@effects of proposal 7032
@
text
@d2396 4
@


1.1531
log
@effects of proposal 7050
@
text
@d3321 1
a3321 1
Rule 683/15 (Power=3)
d3326 1
a3326 1
      indicating which one of the available options e selects.  To be
d3347 1
a3347 1
      decision is one, except where rules say otherwise.
d3384 1
@


1.1530
log
@effects of proposal 7049
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7049
Last change to this ruleset: by Proposal 7049
d139 1
a139 1
      Rule 2158: Judicial Questions
d2056 1
a2056 1
Rule 1769/7 (Power=3)
d2064 1
a2064 1
      question.
d2111 1
d4000 1
a4000 1
Rule 991/11 (Power=2)
d4015 1
a4015 2
      status of all judicial cases that either require a judge or have
      at least one applicable judicial question that has no judgement.
d4061 1
d4065 2
a4066 11
Rule 2158/9 (Power=2)
Judicial Questions

      A judicial question is a question that arises within a judicial
      case.  Judicial questions arise only as defined by the rules.
      Defining a judicial question is secured, with a power threshold
      of 1.7.

      At any time, each judicial question is either inapplicable
      (default) or applicable.  This is not a persistent status, but
      is evaluated instantaneously.
d4068 1
a4068 1
      At any time, each judicial question is either open (default),
d4071 2
a4072 2
      types of judgement for a judicial question depend on the type of
      question.
d4074 17
a4090 20
      When a judicial question is applicable and open, its case
      requires a judge.

      When a judicial question is applicable and open, and its case
      has a judge assigned to it, the judge CAN assign a valid
      judgement to it by announcement, and SHALL do so as soon as
      possible, unless e is recused from the case before the time
      limit for doing so has expired.  A judge SHOULD NOT assign an
      inappropriate judgement to any judicial question.  A judgement
      is valid and/or appropriate only as defined by the rules.
      Defining these things is secured, with a power threshold of 1.7.
      If more than one judgement is valid and appropriate, then the
      choice between them is left to the judge's discretion.

      When a judicial question on a non-appeal case is applicable and
      open, and its judge has violated a time limit to assign a
      judgement to it, or is not an active player, the Clerk of the
      Courts SHALL recuse that judge with cause by announcement as
      soon as possible; however, this requirement is waived if the
      judge assigns a judgement to it first.
d4114 1
d4118 1
a4118 1
Rule 591/33 (Power=1.7)
d4134 3
a4136 4
      An inquiry case has a judicial question on veracity, which is
      always applicable.  The valid judgements for this question are
      as follows, based on the truth or falsity of the statement at
      the time the inquiry case was initiated:
d4153 1
a4153 1
        judicial question which was not itself judged IRRELEVANT
d4254 1
d4258 1
a4258 1
Rule 1504/54 (Power=2)
d4272 1
a4272 3
      A criminal case has a judicial question on culpability, which is
      applicable at all times following the call for judgement.  The
      valid judgements for this question are:
d4274 2
a4275 2
      * GUILTY, appropriate if the judge finds, beyond a reasonable
        doubt, that ALL of the following are true:
d4294 2
a4295 6
      A criminal case has a judicial question on sentencing, which is
      applicable if the question on culpability is applicable and has
      a judgement of GUILTY.  If a criminal case has an applicable
      question on sentencing which has a judgement, the Accused is
      hereafter known as the ninny, the judgement in the question on
      sentencing is known as the sentence, and the sentence is in
d4321 3
a4323 3
        to perform one destruction or transfer per question on
        sentencing, even if sentences of this type are assigned more
        than once or go into effect more than once.
d4446 1
d4450 1
a4450 1
Rule 2277/2 (Power=2)
a4456 9
      Unless otherwise specified, an appeal of a judgement in a
      criminal case is assumed to be appealing the question of
      culpability.

      When a judgement on a criminal case's question of culpability is
      suspended, the judgement (if any) on its question of sentencing
      is also suspended.  Afterward, if the first judgement is
      assigned again, then so is the second.

d4461 1
d4555 1
a4555 1
Rule 2318/0 (Power=1.7)
d4558 10
a4567 11
      If a non-Appeals judicial question (1) has a judgement that has
      been in effect for less than seven days and not been appealed,
      and (2) has not had a Motion to Reconsider filed for it at any
      time while it has been assigned to its current judge, then any
      Player CAN file a Motion to Reconsider the question with 2
      Support.

      When a Motion to Reconsider is so filed, the question is
      rendered open again.  A player who files such a Motion SHOULD
      include arguments as to why the question needs reconsideration,
      and such arguments become part of the record of the case.
d4571 1
d4575 1
a4575 1
Rule 911/43 (Power=1.7)
d4580 1
a4580 1
      has been assigned to a judicial question, and make remedy if the
d4600 1
a4600 3
      An appeal case has a judicial question on disposition, which is
      applicable if and only if the prior question is applicable.  The
      valid judgements for the question on disposition are of the form
d4613 2
a4614 2
        the prior question; the prior judgement is assigned to the
        prior question again
d4617 1
a4617 1
        the prior judgement was appropriate; the prior question is
d4629 1
a4629 1
        question is rendered open again; the judge SHOULD assign this
d4635 4
a4638 4
        question, appropriate if the prior judgement was inappropriate
        in the prior question and the replacement judgement is
        appropriate for the prior question; the replacement judgement
        is assigned to the prior question
d4643 2
a4644 3
      When an appeal case is initiated, the prior question is
      suspended, and remains so until the question on disposition in
      the appeal case is judged.
d4716 1
d4764 1
a4764 1
Rule 1868/17 (Power=2)
d4772 3
a4774 7
      At any time, a judicial case either does not require a judge
      (default) or requires a judge.  This is not a persistent status,
      but is evaluated instantaneously.

      When a judicial case requires a judge and has no judge assigned,
      the CotC CAN assign a qualified entity to be its judge by
      announcement, and SHALL do so as soon as possible.
d4833 1
d4933 1
a4933 1
Rule 2164/3 (Power=1)
d4944 1
a4944 2
      announcement) assigns a judgement to a judicial question in that
      case.
d4951 1
d4980 1
a4980 1
Rule 649/31 (Power=1.5)
d4990 1
a4990 1
      is an open judicial question contesting the validity of those
d5070 1
@


1.1529
log
@effects of proposal 7045
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7045
Last change to this ruleset: by Proposal 7045
d4598 1
a4598 1
Rule 911/42 (Power=1.7)
d4678 4
d4741 1
@


1.1528
log
@effects of proposal 7044
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7044
Last change to this ruleset: by Proposal 7044
d8 1
a8 1
Highest Rule ID number ever assigned: 2346
d14 1
a14 1
Current total number of rules: 97
d20 1
a20 1
      29 with Power=2
d95 1
d1962 1
a1962 1
Rule 1023/27 (Power=2)
d1968 7
a1974 5
          mean "within seven days".  A requirement to perform an
          action at an exact instant (e.g.  "when X, Y SHALL Z"), but
          not "in the same message", is instead interpreted as a
          requirement to perform that action in a timely fashion after
          that instant.
d2034 19
d2430 1
a2430 1
Rule 1728/31 (Power=3)
d2453 3
a2455 1
          objections or notice) at least four days earlier.
d2525 1
d2765 1
a2765 1
Rule 2143/14 (Power=1)
d2772 6
a2777 5
         it at least once each week.  If any information is defined by
         the rules as part of that office's weekly report, then the
         holder of that office SHALL maintain all such information,
         and the publication of all such information is part of that
         office's weekly duties.
d2825 1
d3235 1
a3235 1
Rule 107/14 (Power=3)
d3260 5
a3264 3
      period for the decision.  By default, the voting period lasts
      for seven days.  The minimum voting period for a decision with
      at least two options is seven days.  The vote collector for a
d3316 1
d3435 1
a3435 1
Rule 2168/6 (Power=1)
d3440 3
a3442 2
      period for that decision is instead doubled, provided this has
      not already happened for the decision in question.
d3461 1
@


1.1527
log
@effects of proposal 7043
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7043
Last change to this ruleset: by Proposal 7043
d8 1
a8 1
Highest Rule ID number ever assigned: 2344
d14 1
a14 1
Current total number of rules: 95
d23 1
a23 1
      18 with Power=1
d88 2
d1675 82
@


1.1526
log
@effects of proposal 7042
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7042
Last change to this ruleset: by Proposal 7042
d1520 1
a1520 1
Rule 2335/0 (Power=2)
d1524 2
a1525 1
      within any time limits for doing so, e gains 5 points.
d1538 1
@


1.1525
log
@effects of proposal 7040
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7040
Last change to this ruleset: by Proposal 7040
d4480 1
a4480 1
Rule 911/41 (Power=1.7)
d4499 4
a4502 5
      are the judicial panels consisting of max(3,1+2*R) members
      (where R is the rank of the prior case), where each of the
      members is qualified to be assigned as judge of the prior case
      and none is the prior judge.  If possible, the CotC SHALL assign
      a panel where each of the members is well qualified to be
d4618 1
@


1.1524
log
@effects of proposal 7039
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7039
Last change to this ruleset: by Proposal 7039
d8 1
a8 1
Highest Rule ID number ever assigned: 2343
d14 1
a14 1
Current total number of rules: 94
d23 1
a23 1
      17 with Power=1
d54 1
d571 14
@


1.1523
log
@effects of proposal 7038
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7038
Last change to this ruleset: by Proposal 7038
d8 1
a8 1
Highest Rule ID number ever assigned: 2342
d14 1
a14 1
Current total number of rules: 93
d21 1
a21 1
       7 with Power=1.7
d83 2
a84 1
      Rule 2332: Winning
d1547 2
a1548 2
Rule 2332/0 (Power=2)
Winning
d1550 39
a1588 3
      A player CAN destroy 250 points in eir possession to win the
      game. When a player wins the game, the Scorekeepor is authorized
      to award em the patent title Champion.
d1592 1
@


1.1522
log
@effects of proposal 7035
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7035
Last change to this ruleset: by Proposal 7035
d8 1
a8 1
Highest Rule ID number ever assigned: 2340
d14 1
a14 1
Current total number of rules: 91
d21 1
a21 1
       5 with Power=1.7
d140 1
d143 1
d4378 29
d4427 1
a4427 1
Rule 911/40 (Power=1.7)
a4501 40
      As soon as possible after a judicial panel is assigned, each
      member of the panel SHALL publish an appeals opinion indicating
      a valid judgement to assign to the case -- only the last such
      published opinion for each member is used to determine the
      outcome.  Each member SHOULD choose an appropriate judgement,
      and include arguments for eir choice.  If prejudice is not
      explicitly specified, then an opinion indicating AFFIRM or
      REMAND implicitly indicates without prejudice, while an opinion
      indicating REMIT or OVERRULE implicitly indicates with
      prejudice.

      If, immediately after either all members have so published or
      the time limit for so publishing has ended, a majority of the
      members have opined for the same judgement, the panel acts to
      deliver the judgement in question.  If the panel publishes a
      valid judgement via another mechanism specified in the Rules,
      the requirement for individual members to publish individual
      opinions is waived.

      If the time period ends with no majority judgement, then the
      CotC CAN, and SHALL as soon as possible, by announcement cause
      the panel to judge either REMAND or REMIT with or without
      prejudice, whichever e feels is most appropriate.

      Any panel member CAN publish a formal Concurring Opinion with
      panel member support, provided that the panel has judged AFFIRM,
      and SHOULD do so if and only if the reasoning by which the prior
      judge reached eir judgement was incorrect in whole or part.  A
      Concurring Opinion SHOULD explain the nature of the error(s) in
      the prior judge's reasoning.  Each Concurring Opinion has an
      error rating, an integer from 1 to 99, with larger numbers
      corresponding to larger errors in reasoning; it CAN be specified
      in the announcement of intent, or else defaults to 50.

      In the week after the panel publishes a valid judgement, any
      panel member CAN publish a formal Dissenting Opinion with
      Support.  This Dissenting Opinion becomes a part of the record
      of the case; it can be used as an aid to help interpret the
      decision.

d4565 18
@


1.1521
log
@effects of proposal 7034; Rule 2230 repealed by Proposal 7034 (omd), 16 May 2011
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7034
Last change to this ruleset: by Proposal 7034
d1522 1
a1522 1
Rule 2336/0 (Power=2)
d1525 2
a1526 2
      Weekly Salary is an office switch, tracked by the IADoP, with
      values of the non-negative integers (default zero). At the
d1530 2
a1531 2
      Monthly Salary is an office switch, tracked by the IADoP, with
      values of the non-negative integers (default zero). At the
d1540 1
@


1.1520
log
@effects of proposal 7033
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7033
Last change to this ruleset: by Proposal 7033
d14 1
a14 1
Current total number of rules: 92
d20 1
a20 1
      30 with Power=2
a135 1
      Rule 2230: Notices of Violation
d4094 2
a4095 2
Rule 2230/19 (Power=2)
Notices of Violation
d4097 2
a4098 81
      A player CAN publish a Notice of Violation (NoV) with N support,
      where N is the one half of the number of valid NoVs e previously
      published during the same week, rounded down. An NoV is invalid
      if it lacks any of the following information, and the lack is
      correctly identified within one week after the NoV is published:
       (a) The identity of the Accused;
       (b) The allegedly illegal action/inaction in question;
       (c) The Rule that was allegedly broken;
       (d) If the Rules specify exactly one Class-N Crime (where N is
           a positive integer) as being associated with the alleged
           breach, then the name of that Crime and the value of N;
           otherwise, the Power of the Rule that was allegedly broken.

      Knowingly issuing a NoV with incorrect information is ILLEGAL,
      and the Class-4 Crime of Libel.

      A NoV is valid if and only if:
        (1) it clearly specifies the required information for a NoV;
        (2) no previous valid NoV specified substantially identical
            information (i.e. the same violation for the same specific
            act).
        (3) when a crime is named, the crime is specified within the
            Rules.

      Neither a NoV's incorrectness (i.e. whether its allegation is
      false) nor its unfairness (i.e. whether the punishment resulting
      from leaving it Uncontested would be manifestly unfair according
      to the guidance of the Rules) affects its validity.

      As soon as possible after a player makes an announcement that is
      reasonably recognizable as an attempt to issue such a NoV, the
      CotC SHALL announce whether the NoV was valid.  Such an
      announcement is self-ratifying.  Affirming the validity of the
      NoV does not in itself certify the correctness of the
      allegation.

      A valid NoV is initially Uncontested unless a Crime is named,
      Contested otherwise.  Within four days after the publication of
      an Uncontested NoV, any player CAN make it Contested by
      announcement; a player SHOULD do so if e believes it is
      incorrect and/or unfair.  An Uncontested NoV becomes Contested
      upon the initiation of a judicial case questioning its
      incorrectness and/or unfairness (but not merely by questioning
      its validity).

      If a NoV is Uncontested and was published at least four days
      ago, any player CAN cause it to become Closed by announcement.
      Any player CAN cause a NoV specifying em as Accused to become
      Closed by announcement. When a NoV becomes Closed, a number of
      points in the Accused's possession are destroyed equal to the
      Class of the specified Crime, or in its absence the Power of the
      violated rule, rounded up.  If a Closed NoV becomes Contested,
      the points are still destroyed, but CAN be later recreated by
      judicial processes as described elsewhere.

      Valid NOVs have ID numbers, to be assigned by the CotC.

History:
Created by Proposal 6010 (ais523, Goethe, Murphy, comex, OscarMeyr),
  14 December 2008
Amended(1) by Proposal 6036 (ais523, Wooble; disi.), 13 January 2009
Assigned to Committee on Crime by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(2) by Proposal 6056 (Taral), 23 January 2009
Amended(3) by Proposal 6057 (Taral), 23 January 2009
Amended(4) by Proposal 6063 (Taral; disi.), 4 February 2009
Amended(5) by Proposal 6093 (Murphy), 22 February 2009
Amended(6) by Proposal 6094 (ais523), 22 February 2009
Amended(7) by Proposal 6103 (Murphy), 22 February 2009
Amended(8) by Proposal 6079 (Murphy), 22 February 2009
Amended(9) by Proposal 6120 (Murphy), 5 March 2009
Amended(10) by Proposal 6138 (Murphy), 15 March 2009
Amended(11) by Proposal 6307 (BobTHJ; disi.), 26 May 2009
Amended(12) by Proposal 6327 (Murphy), 29 May 2009
Amended(13) by Proposal 6427 (BobTHJ), 18 August 2009
Amended(14) by Proposal 6575 (G.; disi.), 28 November 2009
Amended(15) by Proposal 6718 (coppro), 4 May 2010
Amended(16) by Proposal 6961 (G.), 3 March 2011
Amended(17) by Proposal 6967 (Wooble), 20 March 2011
Amended(18) by Proposal 7010 (Walker), 20 April 2011
Amended(19) by Proposal 7024 (Murphy), 5 May 2011
d4100 4
a4103 1
----------------------------------------------------------------------
d4105 2
a4106 10
Rule 1504/53 (Power=2)
Criminal Cases

      Criminal cases are a subclass of judicial cases.  Any
      first-class person can initiate a criminal case by an
      announcement calling for judgement on the circumstances
      surrounding a specified valid Notice of Violation alleging a
      rules breach by a single entity (the Accused).  The initiator
      and each member of the Accused's basis are unqualified to be
      assigned as judge of the case.
d4119 2
a4120 3
           case, or punishment already applied through another
           uncontested notice of violation, with the same Accused, the
           same rule, and substantially the same alleged act;
a4131 5
      When a judicial question on culpability is judged after a number
      of the Accused's points have been destroyed due to the
      associated notice, the Accused CAN recreate those points in eir
      possession by announcement.

d4287 1
a4869 2
  * announce whether a notice of violation is valid (Rule 2230)
  * assign ID numbers to valid notices of violation (Rule 2230)
@


1.1519
log
@effects of proposal 7030
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7030
Last change to this ruleset: by Proposal 7030
d3634 1
a3634 1
Rule 1607/30 (Power=2)
a3639 4
      Distributability is switch possessed by proposals in the
      proposal pool, tracked by the Promotor, with values
      Distributable (default) and Undistributable.

d3642 3
a3644 4
      as part of eir weekly duties, distribute any proposal that is in
      the Proposal Pool and was Distributable at the beginning of that
      Agoran week.  The Promotor SHALL NOT distribute an
      Undistributable proposal.
d3722 1
@


1.1518
log
@effects of proposal 7029
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7029
Last change to this ruleset: by Proposal 7029
d549 1
a549 1
Rule 2326/1 (Power=2)
d558 3
d564 1
@


1.1517
log
@effects of proposal 7027
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7027
Last change to this ruleset: by Proposal 7027
d549 1
a549 1
Rule 2326/0 (Power=2)
d552 2
a553 4
      The President is a second-class person.  The President CAN only
      take actions as explicitly described/caused by a Rule or other
      instrument of a power equal to or greater than the power of this
      Rule.
d560 1
@


1.1516
log
@effects of proposal 7026
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7026
Last change to this ruleset: by proposal 7026
d19 2
a20 2
      33 with Power=3
      32 with Power=2
d583 2
a584 2
  * figurehead (rule 103)
  * bestow favors (rule 103)]
d973 6
a978 6
  * manage ID numbers of rules (rule 2141)
  * assign title to rule (rule 2141)
  * report ruleset in two formats (rule 1051)
  * manage Logical Ruleset categories (rule 1681)
  * annotate the Full Logical Ruleset (rule 1681)
  * maintain historical rule annotations (rule 1681)]
d1255 9
a1263 9
  * track citizenship (rule 869)
  * report players' identity and contact details (rule 2139)
  * report registration dates (rule 2139)
  * issue Writ of FAGE (rule 1789)
  * report deregistration by Writ of FAGE (rule 1789)
  * track player activity and report change dates (rule 2130)
  * track forum publicity (rule 478)
  * report fora (rule 478)
  * change the publicity of a forum (rule 478)]
d1553 1
a1553 1
Rule 2337/1 (Power=2)
d1578 1
d1582 1
a1582 1
Rule 2338/1 (Power=2)
d1609 1
d1926 1
a1926 1
event for the purposes of rule 1769.]
d1929 1
a1929 1
period is an event for the purposes of rule 1769.]
d2543 1
a2543 1
of the term "office", in the sense meant by rule 754, but rather
d2851 2
a2852 2
  * hold election for office where contested (rule 2154)
  * report officeholding (rule 2138)]
d3371 1
a3371 1
described in rule 955.]
d3684 4
a3687 4
  * not distribute proposals during holiday (rule 1769)
  * distribute proposals (rule 1607)
  * manage ID numbers of distributed proposals (rule 1607)
  * report proposal pool (rule 1607)]
d3793 1
a3793 1
  * vote collector for proposals (rule 106)]
d3859 9
a3867 9
  * not assign judges during holiday (rule 1769)
  * report open judicial cases (rule 991)
  * manage ID numbers of non-appeal judicial cases (rule 991)
  * refuse excess CFJ (rule 2175)
  * assign judge to judicial case (rule 1868)
  * not assign a poorly qualified judge (rule 1868)
  * track player posture (rule 1871)
  * rotate the bench (rule 1871)
  * recuse tardy judge (rule 2158)]
d4959 6
a4964 6
  * report Patent Titles (rule 649)
  * announce award or revocation of Patent Title (rule 649)
  * announce whether a notice of violation is valid (rule 2230)
  * assign ID numbers to valid notices of violation (rule 2230)
  * initiate decision for degree award (rule 1367)
  * award degrees (rule 1367)]
d5255 1
a5255 1
contract-related rights (in rule 101) are not being infringed.  This
d5300 1
a5300 1
violation of rule 2215 (then 2149), depending on the context of the
d5303 1
a5303 1
[CFJ 1849 (called 21 December 2007): Violation of rule 2215 (then
d5317 1
a5317 1
not violate rule 2215 by engaging in it if there is no specific
@


1.1515
log
@effects of proposal 7025
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7025
Last change to this ruleset: by proposal 7025
d1553 1
a1553 1
Rule 2337/0 (Power=2)
d1564 4
a1567 3
      Optionally, the author CAN, in the creating message, specify a
      set of conditions required to be true for the promise to be
      cashed.  The default is that the promise has no conditions.
d1577 1
d1581 1
a1581 1
Rule 2338/0 (Power=2)
d1585 4
a1588 4
      e does so, provided either that the promise has no conditions,
      or all of the conditions of the promise are true.  To do so, e
      must clearly and unambiguously identify the promise and SHOULD
      publish its text.
d1594 3
a1596 4
      cashing.  Cashing a promise destroys it, unless the conditions
      of the promise explicitly and clearly include conditions under
      which the promise is not so destroyed, and these conditions are
      true.
d1607 1
@


1.1514
log
@effects of proposal 7024
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7024
Last change to this ruleset: by proposal 7024
d1472 1
a1472 1
Rule 2331/0 (Power=2)
d1490 4
d1496 1
@


1.1513
log
@effects of proposal 7022
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7022
Last change to this ruleset: by proposal 7022
d4087 1
a4087 1
Rule 2230/18 (Power=2)
d4121 1
a4121 1
      Herald SHALL announce whether the NoV was valid.  Such an
d4170 1
@


1.1512
log
@effects of proposal 7021
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7021
Last change to this ruleset: by proposal 7021
d6 1
a6 1
Last updated: 23 April 2011
d8 1
a8 1
Highest Rule ID number ever assigned: 2339
d14 1
a14 1
Current total number of rules: 91
d23 1
a23 1
      16 with Power=1
d64 1
d163 6
a168 5
[Rules are listed as follows.  "nnnn" is the rule's ID number,
mandated by rule 2141.  "r" is the revision number, which is not
defined by the rules.  "p" is the rule's power, as defined by rule
1688 and governed by rule 2141.  Rule titles are governed by rule
2141.]
d175 2
a176 2
[Annotations in square brackets are unofficial, added at the
rulekeepor's discretion.  These annotations have no legal force.]
d178 5
a182 3
History:
Historical annotations required by rule 1681.
An ellipsis (...) indicates that the history is incomplete.
d945 17
d3947 1
a3947 1
Rule 591/32 (Power=1.7)
d4002 1
a4002 2
      statement.  The Rulekeepor is ENCOURAGED to annotate rules to
      draw attention to relevant inquiry case judgements.
d4083 1
@


1.1511
log
@effects of proposal 7015
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7015
Last change to this ruleset: by proposal 7015
d8 1
a8 1
Highest Rule ID number ever assigned: 2338
d14 1
a14 1
Current total number of rules: 90
d23 1
a23 1
      15 with Power=1
d55 1
d603 10
@


1.1510
log
@effects of proposal 7013
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7013
Last change to this ruleset: by proposal 7013
d8 1
a8 1
Highest Rule ID number ever assigned: 2336
d14 1
a14 1
Current total number of rules: 88
d20 1
a20 1
      30 with Power=2
d82 2
d1516 56
@


1.1509
log
@effects of proposal 7012
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7012
Last change to this ruleset: by proposal 7012
d124 1
a124 1
      Rule 1950: Voting on Democratic Decisions
d3394 1
a3394 1
Rule 106/30 (Power=3)
a3430 4
      The adoption index of a proposal is an integral multiple of 0.1
      from 1.0 to 9.9.  It may be set by the proposer at the time of
      submission, or otherwise defaults to 1.0.

d3432 6
a3437 4
      The adoption index of this decision is set to the adoption index
      of the proposal at the initiation of the decision. Changing the
      adoption index of the decision is secured with a power threshold
      of 2.  The vote collector for this decision is the Assessor.
d3528 1
d3628 6
a3633 2
Rule 1950/21 (Power=3)
Voting on Democratic Decisions
d3635 2
a3636 2
      An Agoran decision with an adoption index is a Democratic
      decision.
d3643 1
d3648 5
a3652 4
      The eligible voters on a democratic decision are those entities
      that were active first-class players at the start of its voting
      period.  The voting limit of each eligible voter on a democratic
      decision is one.
d3680 1
@


1.1508
log
@effects of proposal 7011
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7011
Last change to this ruleset: by proposal 7011
d4077 1
a4077 1
Rule 1504/52 (Power=2)
d4172 1
a4172 1
        positive, e SHALL NOT become active.
d4272 1
@


1.1507
log
@effects of proposal 7010
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7010
Last change to this ruleset: by proposal 7010
d1420 1
a1420 1
Rule 2330/1 (Power=2)
d1423 2
a1424 2
      Points are a fixed currency. Ownership of points is restricted
      to Players. A player's score is the number of points e owns.
d1434 1
@


1.1506
log
@effects of proposal 7009
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7009
Last change to this ruleset: by proposal 7009
d3990 1
a3990 1
Rule 2230/17 (Power=2)
d4038 11
a4048 1
      Valid NOVs have ID numbers, to be assigned by the Herald.
d4072 1
d4076 1
a4076 1
Rule 1504/51 (Power=2)
d4112 5
d4270 1
@


1.1505
log
@effects of proposal 7008
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7008
Last change to this ruleset: by proposal 7008
d8 1
a8 1
Highest Rule ID number ever assigned: 2335
d14 1
a14 1
Current total number of rules: 87
d20 1
a20 1
      29 with Power=2
d80 1
d1480 21
@


1.1504
log
@effects of proposal 7007
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7007
Last change to this ruleset: by proposal 7007
d1419 1
a1419 1
Rule 2330/0 (Power=2)
d1428 2
d1432 1
@


1.1503
log
@effects of proposal 7006
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7006
Last change to this ruleset: by proposal 7006
d8 1
a8 1
Highest Rule ID number ever assigned: 2334
d14 1
a14 1
Current total number of rules: 86
d20 1
a20 1
      28 with Power=2
d79 1
d1456 20
@


1.1502
log
@effects of proposal 7005
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7005
Last change to this ruleset: by proposal 7005
d556 1
a556 1
Rule 103/8 (Power=2)
d563 3
a565 2
      The Speaker is the single first-class player (if any) who holds
      the most Postulated Offices.
d594 1
@


1.1501
log
@effects of proposal 7002
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 7002
Last change to this ruleset: by proposal 7002
d4017 1
a4017 1
Rule 1504/50 (Power=2)
d4109 5
d4205 1
@


1.1500
log
@effects of proposal 6995
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6995
Last change to this ruleset: by proposal 6995
d6 1
a6 1
Last updated: 12 April 2011
d8 1
a8 1
Highest Rule ID number ever assigned: 2333
d14 1
a14 1
Current total number of rules: 85
d20 1
a20 1
      27 with Power=2
d94 1
d2351 22
d4017 1
a4017 1
Rule 1504/49 (Power=2)
d4100 8
a4107 3
      * TIME OUT with a number of days between 7 and 21. The ninny
        becomes inactive, and SHALL NOT become active for the number
        of days specified, as long as the sentence remains in effect.
d4199 1
@


1.1499
log
@effects of proposal 6992
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6992
Last change to this ruleset: by proposal 6992
d965 1
a965 1
Rule 2327/0 (Power=1)
d968 3
a970 2
      During Read the Ruleset Week (the first Agoran week each year
      that begins in February), Agorans SHOULD do so.
d974 1
@


1.1498
log
@effects of proposal 6991
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6991
Last change to this ruleset: by proposal 6991
d498 1
a498 1
Rule 2140/0 (Power=3)
d508 2
a509 2
      (c) modify any other substantive aspect of an instrument with
          power greater than its own.  A "substantive" aspect of
d517 1
d601 1
a601 1
Rule 2141/5 (Power=3)
d616 1
a616 2
      Rules have ID numbers, to be assigned by the Rulekeepor, and are
      strictly ordered.
d619 2
a620 2
      rule ever does not have a title, the Rulekeepor shall assign
      a title to it by announcement as soon as possible.
d624 3
a626 1
      substantive aspects of the rule.
d647 1
@


1.1497
log
@effects of proposal 6989
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6989
Last change to this ruleset: by proposal 6989
d8 1
a8 1
Highest Rule ID number ever assigned: 2332
d14 1
a14 1
Current total number of rules: 84
d23 1
a23 1
      14 with Power=1
d93 1
d2301 44
@


1.1496
log
@effects of proposal 6985
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6985
Last change to this ruleset: by proposal 6985
d8 1
a8 1
Highest Rule ID number ever assigned: 2329
d14 1
a14 1
Current total number of rules: 81
d20 1
a20 1
      24 with Power=2
d32 1
d75 6
a92 1
      Rule 2166: Assets
d1309 150
a2299 96
Rule 2166/16 (Power=2)
Assets

      An asset is an entity defined as such by a rule or contest
      (hereafter its backing document), and existing solely because
      its backing document defines its existence.

      Each asset has exactly one owner.  If an asset would otherwise
      lack an owner, it is owned by the Lost and Found Department.  If
      an asset's backing document restricts its ownership to a class
      of entities, then that asset CANNOT be gained by or transferred
      to an entity outside that class, and is transferred to the Lost
      and Found Department if it is owned by an entity outside that
      class.  If an asset is owned by the Lost and Found department
      any player CAN transfer or destroy it without objection.

      The Lost and Found department may own any asset, and have assets
      transferred to and from it, regardless of the asset's backing
      document or any Rule, Rules to the contrary notwithstanding.

      The recordkeepor of a class of assets is the entity (if any)
      defined as such by, and bound by, its backing document.  That
      entity's report includes a list of all instances of that class
      and their owners.  This portion of that entity's report is
      self-ratifying.

      An asset whose backing document is not a rule generally CAN be
      created by its recordkeepor by announcement, subject to
      modification by its backing document.  To "gain" an asset is to
      have it created in one's possession; to "award" an asset to an
      entity is to create it in that entity's possession.

      An asset generally CAN be destroyed by its owner by
      announcement, and an asset owned by the Lost and Found
      Department generally CAN be destroyed by its recordkeepor by
      announcement, subject to modification by its backing document.
      To "lose" (syn. "spend") an asset is to have it destroyed from
      one's possession; to "revoke" an asset from an entity is to
      destroy it from that entity's possession.

      An asset generally CAN be transferred by its owner to another
      entity by announcement, subject to modification by its backing
      document.  A fixed asset is one defined as such by its backing
      document, and CANNOT be transferred; any other asset is liquid.

      A currency is a class of asset defined as such by its backing
      document.  Instances of a currency with the same owner are
      fungible.  The Minimum Unit Quantity (MUQ) of each currency is
      one.

[CFJs 1790-1791 (called 11 November 2007): The self-ratifying asset
report is the complete list of ownerships of assets of that class; a
partial list does not self-ratify.]

[CFJ 1850 (called 22 December 2007): The general ability of the
recordkeepor to create assets does not include an ability to determine
who possesses them when created, so they are necessarily owned by the
Lost and Found Department [at the time of CFJ 1850, the Bank] upon
creation.]

[CFJ 1910 (called 10 March 2008): When an existing entity is defined
as an asset, the change of its owner from "undefined" to the Lost and
Found Department [Bank at the time of CFJ 1910] counts as a transfer,
and fails if the Lost and Found Department is outside of the class of
objects that can own the entity.]

[CFJ 2176 (called 22 September 2008): Entities may be fungible even if
not defined as such by this rule.]

[CFJ 2309 (called 11 December 2008): If two separate documents attempt
to define an asset with the same name, they refer to the same entity,
but the entity is not an asset.]

History:
Created by Proposal 5173 (Murphy), 29 August 2007
Amended(1) by Proposal 5216 (Murphy), 13 September 2007
Amended(2) by Proposal 5388 (Murphy), 1 January 2008
Amended(3) by Proposal 5475 (Murphy), 24 March 2008
Amended(4) by Proposal 5476 (Murphy; disi.), 27 March 2008
Amended(5) by Proposal 5496 (Murphy), 23 April 2008
Amended(6) by Proposal 5833 (Murphy, Taral), 12 November 2008
Amended(7) by Proposal 5840 (root), 12 November 2008
Amended(8) by Proposal 5974 (Murphy; disi.), 25 November 2008
Amended(9) by Proposal 6023 (Murphy), 22 December 2008
Assigned to Committee on Finance by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(10) by Proposal 6161 (Murphy), 31 March 2009
Amended(11) by Proposal 6253 (Quazie), 9 May 2009
Amended(12) by cleaning (Murphy), 16 August 2009
Amended(13) by Proposal 6430 (coppro; disi.), 18 August 2009
Amended(14) twice by Proposal 6650 (coppro), 10 March 2010
Amended(15) by Proposal 6792 (omd), 27 August 2010
Amended(16) by Proposal 6916 (omd; disi.), 2 January 2011

----------------------------------------------------------------------

@


1.1495
log
@effects of proposal 6984
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6984
Last change to this ruleset: by proposal 6984
d4087 1
a4087 1
Rule 2205/2 (Power=1)
d4099 1
a4099 4
      3) For an equity case, the parties to the agreement in question,
         during the pre-trial phase.

      4) The judge, when delivering judgement.
d4109 1
@


1.1494
log
@effects of proposal 6983
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6983
Last change to this ruleset: by proposal 6983
d1264 1
a1264 1
Rule 2130/12 (Power=2)
a1281 2
      Having been inactive within the past week is a Losing Condition.

d1298 1
@


1.1493
log
@effects of proposal 6981
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6981
Last change to this ruleset: by proposal 6981
d1442 1
a1442 1
Rule 2152/5 (Power=3)
d1466 1
a1466 1
         rule in question.
d1503 1
@


1.1492
log
@effects of proposal 6977
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6977
Last change to this ruleset: by proposal 6977
d6 1
a6 1
Last updated: 30 March 2011
d417 1
a417 1
Rule 1586/7 (Power=2)
d420 4
a423 4
      If multiple rules (hereafter documents) attempt to define an
      entity with the same name, then they refer to the same entity.
      A document-defined entity's name CANNOT be changed to be the
      same as another document-defined entity's name.
d425 2
a426 2
      A document referring to an entity by name refers to the entity
      that had that name when the document first came to include that
d429 7
a435 8
      If the documents defining an entity are repealed or amended such
      that they no longer define that entity, then that entity and its
      properties cease to exist.

      If the documents defining an entity are amended such that they
      still define that entity but with different properties, then
      that entity and its properties continue to exist to whatever
      extent is possible under the new definitions.
d456 1
d1309 1
a1309 1
Rule 754/14 (Power=3)
d1324 5
a1328 4
      (2) A term explicitly defined by the Rules by default has that
          meaning when used in any Rule of equal or lesser power, as
          do its ordinary-language synonyms not explicitly defined by
          the rules.
d1438 1
d1953 1
a1953 1
Rule 1728/30 (Power=3)
d1961 4
a1964 2
          greater than 8.
       2) With N Supporters, where N is a positive integer.
d2045 1
d2783 1
a2783 1
Rule 107/13 (Power=3)
d2815 3
d2861 1
@


1.1491
log
@effects of proposal 6976
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6976
Last change to this ruleset: by proposal 6976
d8 1
a8 1
Highest Rule ID number ever assigned: 2328
d14 1
a14 1
Current total number of rules: 80
d23 1
a23 1
      13 with Power=1
d79 1
d1635 18
@


1.1490
log
@effects of proposal 6975
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6975
Last change to this ruleset: by proposal 6975
d8 1
a8 1
Highest Rule ID number ever assigned: 2327
d14 1
a14 1
Current total number of rules: 79
d20 1
a20 1
      23 with Power=2
d69 1
d1150 14
@


1.1489
log
@effects of proposal 6974
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6974
Last change to this ruleset: by proposal 6974
d92 1
a92 1
      Rule 2138: The Interplanetary Associate Director of Personnel
d2509 2
a2510 2
Rule 2138/12 (Power=1)
The Interplanetary Associate Director of Personnel
d2512 1
a2512 1
      The Interplanetary Associate Director of Personnel (IADoP) is an
d2527 2
a2528 2
[CFJ 1672 (called 18 May 2007): The Interplanetary Associate Director
of Personnel is the Director of Personnel.]
d2551 1
@


1.1488
log
@effects of proposal 6973
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6973
Last change to this ruleset: by proposal 6973
d971 1
a971 1
Rule 869/31 (Power=2)
d997 3
a999 4
      A player CAN deregister by announcement. A person CANNOT
      register within thirty days after being deregistered by any
      means other than by a mechanism that the rules explicitly
      describe as a means of honorable deregistration.
d1048 1
d1248 1
a1248 1
Rule 2130/11 (Power=2)
d1264 1
a1264 1
      objection.  This is a means of honorable deregistration.
d1283 1
@


1.1487
log
@effects of proposal 6972
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6972
Last change to this ruleset: by proposal 6972
d8 1
a8 1
Highest Rule ID number ever assigned: 2326
d14 1
a14 1
Current total number of rules: 78
d23 1
a23 1
      12 with Power=1
d63 1
d953 11
@


1.1486
log
@more effects of proposal 6969
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6969
Last change to this ruleset: by proposal 6969
d2372 1
a2372 1
Rule 2154/33 (Power=2)
d2378 3
a2380 3
       a) by announcement, if e is the IADoP, or the office is vacant,
          or no election has been initiated for the office within 90
          days before the announcement;
d2461 1
@


1.1485
log
@effects of proposal 6969
@
text
@d1997 1
a1997 1
Rule 2288/1 (Power=3)
d2020 3
d2026 1
@


1.1484
log
@effects of proposal 6968
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6968
Last change to this ruleset: by proposal 6968
d2368 1
a2368 1
Rule 2154/32 (Power=2)
d2399 1
a2399 4
            b) did not decline a nomination for the office, and

            c) are Senators if there is currently an Emergency
               Session.
d2404 1
a2404 4
       2) The eligible voters are the active first-class players,
          unless there is an Emergency Session at the time the
          decision is initiated, in which case the eligible voters are
          the active Senators.
d2456 1
d3750 1
a3750 1
      A player CAN publish a Notice of Violation (NoV) for N support,
d4108 1
a4108 1
Rule 911/39 (Power=1.7)
d4202 4
a4205 19
      If the time period ends with no majority judgement, then:

      - if the Justiciar has published an opinion on the case
        clearly marked as the Justiciar's Opinion and indicating a
        valid judgement, and that judgement is the same as one given
        by at least one panel member (other than the Justiciar), then
        the panel delivers that judgement;

      - otherwise, the case enters an overtime period, which
        lasts for four days.  The CotC SHOULD publicly remind the
        Justiciar when an overtime period begins.  During this period,
        if the Justiciar publishes a Justiciar's Opinion that is the
        same as one panel member's as described above, then the panel
        delivers that judgement;

      - otherwise, the CotC CAN and SHALL, asap after the overtime
        period ends, act for the panel by announcement to judgement of
        either REMAND or REMIT with or without prejudice, whichever e
        feels is most appropriate.
d4285 1
@


1.1483
log
@effects of proposal 6967; Rule 2153 repealed by Proposal 6967 (Wooble), 20 March 2011
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6967
Last change to this ruleset: by proposal 6967
d19 2
a20 2
      34 with Power=3
      22 with Power=2
d3155 1
a3155 1
Rule 106/29 (Power=3)
d3160 6
a3165 7
      When creating proposals, the person who creates them SHOULD
      ensure that the proposal outlines changes to be made to Agora,
      such as enacting, repealing, or amending rules, or making other
      explicit changes to the gamestate. When a proposal that includes
      such explicit changes takes effect, it applies those changes to
      the gamestate. If the proposal cannot make some such changes,
      this does not preclude the other changes from taking place.
d3290 1
@


1.1482
log
@effects of proposal 6964; Rule 1750 repealed by Proposal 6964 (Wooble), 20 March 2011
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6963
Last change to this ruleset: by proposal 6963
d14 1
a14 1
Current total number of rules: 79
d19 2
a20 2
      33 with Power=3
      23 with Power=2
d23 1
a23 1
      13 with Power=1
a76 1
      Rule 2153: Interest Index
a1605 19
Rule 2153/3 (Power=1)
Interest Index

      An entity's interest index is an integer from 0 to 3, default
      value 1.  When altering an entity's interest index, a person
      SHOULD try to pick a new value which reflects the complexity of
      that entity.

      "Disinterested" is a synonym for "interest index 0".

History:
Created by Proposal 5056 (Murphy), 5 July 2007
Retitled by Proposal 5176 (Murphy), 29 August 2007
Amended(1) by Proposal 5176 (Murphy), 29 August 2007
Amended(2) by Proposal 5970 (Murphy), 20 November 2008
Amended(3) by Proposal 6571 (ais523), 28 November 2009

----------------------------------------------------------------------

d2259 1
a2259 1
Rule 2143/13 (Power=1)
d2283 2
a2284 3
      required of that office within the allotted time is the Class-N
      crime of Tardiness, where N is the Interest Index of that
      office.
d2317 1
d3752 1
a3752 1
Rule 2230/16 (Power=2)
d3755 5
a3759 6
      A player CAN publish a Notice of Violation (NoV) for a fee of N
      ergs, where N is the one half of the number of valid NoVs e
      previously published during the same week, rounded down. An NoV
      is invalid if it lacks any of the following information, and the
      lack is correctly identified within one week after the NoV is
      published:
d3823 1
d4411 1
a4411 1
Rule 1871/27 (Power=1.5)
a4435 4
      A sitting player that assigns judgement in a disinterested
      judicial case CAN and MAY become standing by announcement in the
      same message in which e assigns judgement to that case.

d4489 1
@


1.1481
log
@effects of proposal 6963
@
text
@d14 1
a14 1
Current total number of rules: 80
d23 1
a23 1
      14 with Power=1
a62 1
      Rule 1750: Read the Ruleset Week
a952 17
Rule 1750/4 (Power=1)
Read the Ruleset Week

      The first Agoran week each year which falls entirely in February
      is known as Read the Vladivostok Telephone Directory Week.
      During this time, Agorans SHALL read the Vladivostok Telephone
      Directory.

History:
Created by Proposal 3601 (Chuck), Dec. 9 1997
Amended(1) by Proposal 4398 (harvel), 23 October 2002
Amended(2) by Proposal 6026 (Murphy), 22 December 2008
Amended(3) by Proposal 6882 (G.; disi.), 20 November 2010
Amended(4) by Proposal 6937 (omd), 2 January 2011

----------------------------------------------------------------------

@


1.1480
log
@effects of proposal 6961; Rule 2186 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2245 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2110 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2221 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2223 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2268 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2177 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2319 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2215 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2228 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2229 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2312 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2325 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2296 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2227 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2196 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2222 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2250 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2267 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2156 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2279 repealed by Proposal 6961 (G.), 3 March 2011; Rule 1450 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2134 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2313 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2317 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2281 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2224 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2188 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2309 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2322 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2246 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2225 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2226 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2248 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2282 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2289 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2295 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2283 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2284 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2287 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2293 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2308 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2320 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2323 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2321 repealed by Proposal 6961 (G.), 3 March 2011; Rule 1922 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2314 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2255 repealed by Proposal 6961 (G.), 3 March 2011; Rule 402 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2316 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2270 repealed by Proposal 6961 (G.), 3 March 2011; Rule 2286 repealed by Proposal 6961 (G.), 3 March 2011
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6961
Last change to this ruleset: by proposal 6961
d6 1
a6 1
Last updated: 3 March 2011
d1696 1
a1696 1
Rule 478/28 (Power=3)
d1704 2
a1705 1
      Foreign (default), tracked by the Registrar.
d1938 1
@


1.1479
log
@effects of proposal 6946
@
text
@d3 2
a4 2
Last proposal with recorded effect on this ruleset: 6946
Last change to this ruleset: by proposal 6946
d6 1
a6 1
Last updated: 16 January 2011
d8 1
a8 1
Highest Rule ID number ever assigned: 2325
d14 1
a14 1
Current total number of rules: 132
d19 5
a23 5
      38 with Power=3
      44 with Power=2
       7 with Power=1.7
       6 with Power=1.5
      35 with Power=1
a36 1
      * Economy
a37 1
      * The Court
a50 3
      Rule 2186: Victory
      Rule 2245: Win by Not Losing
      Rule 2110: Win by Paradox
d52 2
a62 1
      Rule 2221: Cleanliness
a63 1
      Rule 2223: Win by Junta
a68 1
      Rule 2268: Entanglement
a71 6
      Rule 2177: The Senate
      Rule 2319: Messy Statements
      Rule 2215: Truthiness
      Rule 2228: Rests
      Rule 2229: Just Resting
      Rule 2312: The Pariah
a77 1
      Rule 2296: Festival Days
d85 1
a85 1
      Rule 2325: Zombies
a89 1
      Rule 2227: Interest Index of Offices
a101 1
      Rule 2196: Standard Classes of Agoran Decisions
a103 1
      Rule 2222: Maximum Voting Limits
a111 4
      Rule 2313: Urgent Proposals
      Rule 2317: Leet Leadership
      Rule 2281: Proposal Cleanup
      Rule 2224: Interest Index of Proposals
a112 2
      Rule 2250: Officer's Proposals
      Rule 2267: Judge's Proposals
a113 2
      Rule 2156: Voting on Ordinary Decisions
      Rule 2279: Voting Limits on Ordinary Decisions
a114 1
      Rule 1450: Separation of Powers
a115 4
      Rule 2134: Win by Clout
      Rule 2188: Win by Proposal
      Rule 2309: The Propose-O-Matic
      Rule 2322: Groups
a118 2
      Rule 2246: Submitting a CFJ to the Justiciar
      Rule 2225: Interest Index of Judicial Cases
a130 2
      Rule 2226: Judicial Rank
      Rule 2248: Second-Class Judges
a134 14
      * Economy
      Rule 2166: Assets
      Rule 2282: Energy
      Rule 2289: Capacitors
      Rule 2295: Rewards
      Rule 2283: Fees
      Rule 2284: Fee-based actions
      Rule 2287: Props
      Rule 2293: Leadership Tokens
      Rule 2308: Contests
      Rule 2320: Auctions and the Default Auction Procedure
      Rule 2323: Fee-based auctions
      Rule 2321: Proposal Points

a136 1
      Rule 1922: Defined Regular Patent Titles
a139 9
      * The Court
      Rule 2314: The List of Succession
      Rule 2255: The Court
      Rule  402: Identity of the Speaker
      Rule  103: Role of the Speaker
      Rule 2316: Church and State
      Rule 2270: Coups D'etat
      Rule 2286: Veto and Rubberstamp

a142 1
      Rule 2324: Dictatorship
d512 2
a513 2
Rule 2186/9 (Power=2)
Victory
d515 1
a515 11
      Winning Conditions and Losing Conditions are conditions defined
      as such by the rules.  If such a condition is defined by the
      rules as being satisfied when an event occurs (as opposed to
      being satisfied while certain other conditions hold), then it
      thereafter continues to be satisfied until the rules explicitly
      say otherwise.

      When one or more persons satisfy at least one Winning Condition
      and do not satisfy any Losing Conditions, all such persons win
      the game.  The game CANNOT be won in any other way, rules to the
      contrary notwithstanding.
d517 3
a519 4
      Each Winning Condition should (if needed) specify a cleanup
      procedure to prevent an arbitrary number of wins arising from
      essentially the same conditions.  When one or more persons win
      the game:
d521 2
a522 28
        a) For each Winning Condition satisfied by at least one of
           those persons, its cleanup procedure (if any) occurs.

        b) Each of those persons ceases to satisfy any Winning
           Conditions.

      A win announcement is an announcement meeting all of these
      requirements:

        a) It is factually correct.

        b) It is explicitly labeled as a win announcement and/or
           clearly states that one or more persons thereby win the
           game.

        c) If it was a win announcement, then it would cause one or
           more Winning Conditions to be satisfied, as defined by
           other rules.

[Cross-references (9 January 2008): list of Winning Conditions:
  * Clout (rule 2134)
  * Dictatorship (rule 2223)
  * Game Club (rule 2308)
  * Leadership (rule 2293)
  * Legislation (rule 2188)
  * Paradox (rule 2110)
  * Respect (rule 2287)
  * Solitude (rule 2186)]
d525 2
a526 11
Created by Proposal 5394 (Murphy, Goddess Eris, OscarMeyr, Zefram),
  16 January 2008
Amended(1) by Proposal 5791 (Murphy), 22 October 2008
Amended(2) by Proposal 5792 (Murphy), 22 October 2008
Amended(3) by Proposal 6023 (Murphy), 22 December 2008
Amended(4) by Proposal 6052 (Murphy), 23 January 2009
Amended(5) by Proposal 6083 (ais523), 22 February 2009
Amended(6) by Proposal 6198 (Murphy), 27 April 2009
Amended(7) by Proposal 6433 (coppro; disi.), 18 August 2009
Amended(8) by Proposal 6657 (Murphy), 10 March 2010
Amended(9) by Proposal 6782 (Murphy), 11 August 2010
d530 2
a531 2
Rule 2245/0 (Power=1)
Win by Not Losing
d533 4
a536 3
      While a player is the only active first-class player not to
      satisfy at least one Losing Condition, e satisfies the Winning
      Condition of Solitude.
d538 2
a539 3
      Cleanup procedure:  The same person cannot satisfy this Winning
      Condition again until at least one other player ceases to
      satisfy any Losing Condition.
d542 1
a542 1
Created by Proposal 6198 (Murphy), 27 April 2009
d546 2
a547 2
Rule 2110/5 (Power=1)
Win by Paradox
d549 3
a551 4
      A tortoise is an inquiry case on the possibility or legality of
      a rule-defined action (actual or hypothetical, but not arising
      from that case itself, and not occurring after the initiation of
      that case) for which the question of veracity is UNDECIDABLE.
d553 2
a554 3
      Upon a win announcement that a tortoise has continuously been a
      tortoise for no greater than four and no less than two weeks,
      the initiator satisfies the Winning Condition of Paradox.
d556 5
a560 5
      Cleanup procedure:  Each winner satisfying this Winning
      Condition SHALL, as soon as possible, make a reasonable attempt
      to resolve the paradox.  The same person can not satisfy this
      Winning Condition again for the same tortoise or for any other
      tortoise that was linked to it in assignment.
d562 3
a564 25
History:
Created by Proposal 4781 (Sherlock), 3 June 2005
Amended(1) by Proposal 4891 (Murphy), 22 January 2007
Amended(2) by Proposal 5195 (Zefram), 6 September 2007
Amended(3) by Proposal 5297 (Murphy), 22 November 2007
Amended(4) by Proposal 5394 (Murphy, Goddess Eris, OscarMeyr, Zefram),
  16 January 2008
Amended(5) by Proposal 5451 (root, Murphy, Zefram), 1 March 2008
Power changed from 3 to 2 by Proposal 5955 (ais523, Elysion, Murphy;
  disi.), 18 November 2008
Power changed from 2 to 1 by Proposal 6198 (Murphy), 27 April 2009

----------------------------------------------------------------------

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.]
d567 16
a582 2
Initial Immutable Rule 104, Jun. 30 1993
Mutated from MI=Unanimity to MI=3 by Proposal 1482, Mar. 15 1995
a953 19
Rule 2221/5 (Power=3)
Cleanliness

      Any player CAN clean a rule without objection by specifying one
      or more corrections to spelling, grammar, capitalization, and/or
      dialect, or to whether a synonym or abbreviation is used in
      place of a word or phrase, in the rule's text and/or title; the
      rule is amended by this rule as specified by that person.

History:
Created by Proposal 5975 (Murphy), 25 November 2008
Amended(1) by Proposal 6098 (comex), 22 February 2009
Amended(2) by Proposal 6291 (Murphy), 19 May 2009
Amended(3) by Proposal 6722 (Murphy), 21 May 2010
Amended(4) by Proposal 6732 (comex), 6 June 2010
Amended(5) by Proposal 6741 (comex; disi.), 1 July 2010

----------------------------------------------------------------------

a970 22
Rule 2223/2 (Power=1)
Win by Junta

      Upon a win announcement that a rule states that one or more
      persons CAN cause it to make arbitrary rule changes by
      announcement, all those persons satisfy the Winning Condition of
      Dictatorship.

      Cleanup procedure:  Those persons SHALL as soon as possible
      amend the rule so that it no longer states this, and SHOULD
      amend the rules to prevent this condition from being achieved
      again in essentially the same way.  Also, the power of Rule 2324
      is set to 2.

History:
Created by Proposal 5982 (Murphy), 29 November 2008
Amended(1) by Proposal 6162 (comex), 31 March 2009
Power changed from 2 to 1 by Proposal 6198 (Murphy), 27 April 2009
Amended(2) by Rule 2324 (omd), 22 December 2010

----------------------------------------------------------------------

a1155 11
Rule 2268/0 (Power=2)
Entanglement

      Two entities are entangled if and only if the intersection of
      their bases is non-empty.

History:
Created by Proposal 6485 (Murphy), 18 September 2009

----------------------------------------------------------------------

a1194 1
  * report senators (rule 2177)
d1203 1
a1203 2
  * change the publicity of a forum (rule 478)
  * award patent title of Left in a Huff (rule 1922)]
a1292 221
Rule 2177/17 (Power=2)
The Senate

      A Senator is any first-class player whose most recent
      registration was at least sixty days ago.  The set of all
      Senators is known as the Senate.  The Registrar's report
      includes a list of all Senators.

      A Senator CAN call an Emergency Session with 2 Senator
      supporters, provided no other emergency session existed at any
      time in the preceding 48 hours.  An emergency session lasts
      until it is terminated.  An unterminated emergency session
      terminates 21 days after it was called.  A Senator CAN terminate
      an emergency session without 3 Senator objections.  Terminating
      an emergency session is a secured change.  The Assessor's
      monthly report includes the dates when the most recent emergency
      session was called and terminated.

      The roll call of an emergency session is the set of Senators at
      the time the emergency session was called.  During emergency
      session, the previous definition of Senator does not apply;
      instead, a Senator is a first-class player who is a member of
      the roll call.  The Assessor's monthly report includes the roll
      call of the most recent emergency session.

      During emergency session, any Senator CAN, with 2 supporting
      Senators, declare a specified non-Senator Ineligible to vote on
      the decision to adopt a given proposal in its voting period.  A
      player's voting limit on a decision for which e is Ineligible is
      0 and cannot be modified, rules to the contrary notwithstanding.
      Any Senator CAN cause an Ineligible player to cease to be
      Ineligible to vote on a specified decision with 4 supporting
      Senators and without objection from a member of the Court (any
      of whom CAN object), restoring eir voting limit to what it would
      be if e had never been made Ineligible.

      When an emergency session begins, all non-Senators' postures
      become supine, and non-Senators CANNOT flip their posture while
      the session lasts.

      During an emergency session, any Senator CAN, with 2 supporting
      Senators, change an ordinary decision in its voting period to be
      democratic.

History:
Created by Proposal 5309 (Goethe), 24 November 2007
Amended(1) by Proposal 5331 (root), 5 December 2007
Amended(2) by Proposal 5332 (root), 5 December 2007
Amended(3) by Proposal 5333 (root), 5 December 2007
Amended(4) by Proposal 5333 (root), 5 December 2007
Amended(5) by Proposal 5357 (root; disi.), 16 December 2007
Amended(6) by Proposal 5944 (Taral, ais523), 15 November 2008
Amended(7) by Proposal 5945 (root), 15 November 2008
Amended(8) by Proposal 5979 (Murphy), 25 November 2008
Amended(9) by Proposal 6023 (Murphy), 22 December 2008
Amended(10) by cleaning (Yally), 5 March 2009
Amended(11) by Proposal 6199 (Murphy), 27 April 2009
Amended(12) by Proposal 6266 (Murphy, ais523), 11 May 2009
Amended(13) by Proposal 6319 (Murphy; disi.), 26 May 2009
Amended(14) by Proposal 6618 (Murphy; disi.), 4 February 2010
Amended(15) by Proposal 6733 (Wooble), 6 June 2010
Amended(16) by Proposal 6821 (G., ais523), 4 September 2010
Amended(17) by Proposal 6918 (Yally), 2 January 2011

----------------------------------------------------------------------

Rule 2319/0 (Power=3)
Messy Statements

      A statement is messy if its truth value cannot be evaluated in a
      top-down fashion without encountering some form of infinite
      regress, such as (but not limited to) self-reference.

      For the purposes of the rules, messy statements are considered
      inaccurate and incorrect regardless of their truth value.

History:
Created by Proposal 6870 (omd), 8 November 2010

----------------------------------------------------------------------

Rule 2215/3 (Power=1)
Truthiness

      A person SHALL NOT make a public statement on a matter relevant
      to the rules unless e reasonably believes that it is true (or,
      in the case of a public statement that one performs an action,
      that it is thereby effective).

      For the purpose of this rule:

       a) Merely quoting a statement does not constitute making that
          statement.

       b) Any conditional clause or other qualifier attached to a
          statement constitutes part of the statement; the nature of
          the whole is what is significant.

      The above notwithstanding, a person stating that e intends to
      perform an action in the future does not thereby violate this
      rule, as such a statement is often a requirement to keep eir
      options open.

[CFJ 1739 (called 29 August 2007): A quotation can result in a
violation of rule 2215 (then 2149), depending on the context of the
rest of the message.]

[CFJ 1849 (called 21 December 2007): Violation of rule 2215 (then
2149) can occur without any intent to misdirect.]

[CFJ 1887 (called 30 January 2008): Publicly making the statement
"This statement is a lie." would most likely be a violation of rule
2215 (then 2149), because it is logically indeterminate and so making
it would not be telling the truth, and its logical indeterminacy would
be understood by any reasonable player.]

[CFJ 2103 (called 21 July 2008): Making the statement "I lie." is not
a violation of Rule 2215 if the author is lying down.]

[CFJ 2399 (called 4 March 2009): Even if a type of behavior is likely
to cause false statements to be accidentally published, a person does
not violate rule 2215 by engaging in it if there is no specific
statement e believes is false.]

History:
Created by Proposal 5789 (Murphy, Zefram, Michael, Goethe), 22 October
  2008
Power changed from 2 to 1 by Proposal 5947 (ais523), 15 November 2008
Amended(1) by Proposal 6248 (Wooble), 9 May 2009
Amended(2) by Proposal 6537 (Walker; disi.), 4 November 2009
Amended(3) by Proposal 6564 (Murphy), 13 November 2009

----------------------------------------------------------------------

Rule 2228/6 (Power=2)
Rests

      Rests are a fixed currency.  The creation and destruction of
      Rests is secured with a power threshold of 1.7; a person
      generally CANNOT destroy rests except as permitted by Rules
      explicitly stating methods by which rests in particular CAN be
      destroyed.

      The Herald is the recordkeepor of Rests.

      Ownership of Rests is restricted to first-class persons. If, in
      the absence of this restriction, a number (N) of Rests would be
      created in the ownership of a non-first-class person, then for
      each member of that person's basis, N Rests are created in that
      member's possession.

      A first-class player CAN create Rests in eir own possession by
      announcement.

History:
Created by Proposal 6010 (ais523, Goethe, Murphy, comex, OscarMeyr),
  14 December 2008
Assigned to Committee on Crime by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(1) by Proposal 6060 (Wooble, comex, Goethe), 4 February 2009
Amended(2) by Proposal 6066 (comex, Goethe; disi.), 4 February 2009
Amended(3) by Proposal 6171 (Murphy), 7 April 2009
Amended(4) by Proposal 6394 (Goethe), 10 July 2009
Amended(5) by Proposal 6575 (G.; disi.), 28 November 2009
Amended(6) by cleaning (Murphy), 6 March 2010

----------------------------------------------------------------------

Rule 2229/4 (Power=2)
Just Resting

      Owning one or more Rests is a Losing Condition.

      While a player owns at least 24 Rests, that player CAN be
      deregistered by any player by announcement.  A person who owns
      at least 6 Rests, or where every member of eir basis owns 6
      Rests, CANNOT register, rules to the contrary notwithstanding.

      A person who has one or more rests but is not a player is a
      Fugitive.  The Herald's monthly report shall include a list of
      all Fugitives.  At the beginning of each month, half of each
      Fugitive's rests (rounded down) are destroyed.

History:
Created by Proposal 6010 (ais523, Goethe, Murphy, comex, OscarMeyr),
  14 December 2008
Assigned to Committee on Crime by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(1) by Proposal 6175 (Yally), 7 April 2009
Amended(2) by Proposal 6308 (coppro), 26 May 2009
Amended(3) by Proposal 6394 (Goethe), 10 July 2009
Amended(4) by Proposal 6575 (G.; disi.), 28 November 2009

----------------------------------------------------------------------

Rule 2312/1 (Power=1.7)
The Pariah

      The Pariah is an elected office, with no reports. Whenever a
      player becomes the Pariah, that player is awarded 23 Rests.

      If more than 6 Rests are destroyed in the Pariah's possession in
      any given week, the Pariah is awarded a sufficient number of
      Rests in order to bring eir net Rest loss that week up to no
      more than 6.

      Players are ENCOURAGED to enforce penalties for rules breaches
      against the Pariah, even really minor ones.

      Upon a win announcement that the Pariah has ever continuously
      had 0 Rests for an entire week whilst being the Pariah for all
      of that time, then the Pariah satisfies the Winning Condition of
      Cleanliness. Cleanup condition: The office of Pariah becomes
      vacant and that player ceases to satisfy this Winning Condition.

History:
Created by Proposal 6814 (ais523), 4 September 2010
Amended(1) by Proposal 6866 (coppro; disi.), 8 November 2010

----------------------------------------------------------------------

a1624 24
Rule 2296/0 (Power=1)
Festival Days

      Agora Nomic recognizes and celebrates the following:

        * January 12-14 - Agora's Unbirthday observed (as described
          elsewhere)
        * February 29 - St. Tib's Day
        * March 19 - Mojoday
        * April 1 - April Fool's Day
        * May 25 - Towel Day
        * June 30 - Agora's Birthday (as described elsewhere)
        * July 15 - Confuflux
        * August 12 - Zaraday
        * September 26 - Bureflux
        * October 24 - Maladay
        * November 5 - Guy Fawkes Night
        * December 8 - Afflux

History:
Created by Proposal 6737 (Murphy, David Nicol), 13 June 2010

----------------------------------------------------------------------

d2124 68
a2191 2
Rule 2325/0 (Power=1)
Zombies
d2193 3
a2195 23
      Each Player is always Noisy, Quiet, or Silent, but never more
      than one of these.  Whenever a Player posts to a Public Forum,
      or a new Player registers, that Player is Noisy.

      Any Player who has not caused another Player to become Quiet
      within the last 24 hours can cause another Active Noisy Player
      to become Quiet by stating that e is doing so, and clearly
      identifying that Player, in a Public Forum.  If a Player has
      been Quiet continuously for two weeks, e becomes Silent.  If a
      Player has been Inactive continuously for two months, e becomes
      Silent.

      Any Player can make a Silent Player a Zombie by publicly
      alleging that the Silent Player has abandoned the game.  A
      Player has abandoned the game if and only if e is Silent.  As
      soon as possible after a public allegation that a Player has
      abandoned the game, the Registrar shall publicly confirm or deny
      that the Player is a Zombie.

      If a Speaker has abandoned the game, e commits the Class 15
      Crime of Speaker Abandonment, to be detected and reported by any
      Player.  E ceases to be Speaker, and the Speaker-Elect becomes
      Speaker.  The previous Speaker then becomes a Zombie.
d2198 19
a2216 1
Created by Proposal 6926 (G.; disi.), 2 January 2011
d2357 2
a2358 2
Rule 2227/2 (Power=1)
Interest Index of Offices
d2360 3
a2362 18
      Each office has an interest index, tracked by the IADoP.

      A player CAN set an office's interest index without 2
      objections, or with Agoran Consent.

History:
Created by Proposal 5970 (Murphy), 20 November 2008
Amended(1) by Proposal 6246 (coppro), 9 May 2009
Amended(2) by Proposal 6413 (c-walker), 30 July 2009

----------------------------------------------------------------------

Rule 2160/7 (Power=3)
Deputisation

      Any player (a deputy) CAN perform an action as if e held a
      particular office (deputise for that office) if all of the
      following are true:
d2555 1
a2555 2
  * report officeholding (rule 2138)
  * award long service patent titles (rule 1922)]
a2909 26
Rule 2196/5 (Power=3)
Standard Classes of Agoran Decisions

      An Agoran decision with an adoption index is either ordinary or
      democratic.  All Agoran decisions with an adoption index are
      ordinary by default.

      If an Agoran decision has an adoption index, then the following
      are essential parameters:

      a) Its adoption index.
      b) Whether it is ordinary or democratic.

      For any Agoran decision with an adoption index, the available
      options are FOR and AGAINST.

History:
Created by Proposal 5418 (root), 2 February 2008
Amended(1) by Proposal 5455 (Murphy), 1 March 2008
Amended(2) by Proposal 6110 (Murphy), 1 March 2009
Amended(3) by Proposal 6403 (coppro), 30 July 2009
Amended(4) by Proposal 6441 (Murphy; disi.), 27 August 2009
Amended(5) by Proposal 6518 (BobTHJ), 19 October 2009

----------------------------------------------------------------------

a2958 17
Rule 2222/2 (Power=2)
Maximum Voting Limits

      Other rules to the contrary notwithstanding, no entity may have
      greater a voting limit than allowed by this rule.

      The maximum voting limit for any entity on an ordinary decision
      is 12. The maximum voting limit for any entity on any other
      decision is 1.

History:
Created by Proposal 5978 (Elysion), 25 November 2008
Amended(1) by Proposal 6394 (Goethe), 10 July 2009
Amended(2) by cleaning (Murphy), 3 October 2010

----------------------------------------------------------------------

d3330 1
a3330 70
Rule 2313/1 (Power=3)
Urgent Proposals

      A Proposal is Urgent if it is Interested and the text of the
      message wherein it is submitted explicitly states that it is an
      Urgent Proposal.

      The Promotor CAN distribute an Urgent Proposal as soon as it
      becomes Distributable, and e SHALL do so within four days unless
      it becomes undistributable in the mean time.  Failure to do so
      is the Class 1 Crime of Lack of Urgency.

      Rules to the contrary notwithstanding, the minimum and initial
      voting period of an Agoran decision to adopt an Urgent Proposal
      is four days.

History:
Created by Proposal 6816 (G., Keba), 4 September 2010
Amended(1) by Proposal 6946 (Murphy, omd; disi.), 16 January 2011

----------------------------------------------------------------------

Rule 2317/0 (Power=1)
Leet Leadership

      When an interested proposal consisting of exact 1337 words
      (excluding information like name, or adoption/interest index) is
      enacted, its proposer CAN in a timely fashion award emself a
      Leadership Token.

History:
Created by Proposal 6833 (Keba), 10 September 2010

----------------------------------------------------------------------

Rule 2281/0 (Power=3)
Proposal Cleanup

      The Promotor can, by announcement, remove a proposal from the
      Proposal Pool if it is Undistributable and has been in the
      Proposal Pool for in excess of one month.

History:
Created by Proposal 6599 (coppro), 14 December 2009

----------------------------------------------------------------------

Rule 2224/4 (Power=1)
Interest Index of Proposals

      Each proposal has an interest index, which CAN be set by its
      author at the time of submission, and CAN be changed (while
      undistributed) by any player without 2 objections, or by the
      Promotor or Assessor without 3 objections.

      The submitter of a proposal SHALL set its interest index to 0 if
      and only if the proposal's effects are limited to correcting
      errors and/or ambiguities, or if e is required by another rule
      to submit a disinterested proposal.

History:
Created by Proposal 5970 (Murphy), 20 November 2008
Amended(1) by Proposal 6453 (C-walker), 27 August 2009
Amended(2) by Proposal 6571 (ais523), 28 November 2009
Amended(3) by Proposal 6669 (Yally), 14 March 2010
Amended(4) by Proposal 6894 (Wooble), 20 November 2010

----------------------------------------------------------------------

Rule 1607/29 (Power=2)
d3338 1
a3338 1
      Undistributable (default) and Distributable.
a3346 13
      A player CAN flip a specified Interested proposal to
      Distributable without a number of objections equal to 4 - II
      (where II is the Interest Index of the specified proposal).
      A player CAN flip a specified Disinterested proposal to
      Distributable by announcement.

      For an Agoran decision of whether to adopt a proposal, the
      following are essential parameters:

      a) Its author (and co-authors, if any).
      b) Its interest index.
      c) Its Chamber.

d3422 1
d3426 2
a3427 2
Rule 2250/2 (Power=1)
Officer's Proposals
d3429 2
a3430 6
      If the submitter of a Proposal makes a claim that the proposal
      is submitted as part of an officer's duties in the same message
      in which the proposal was submitted, that proposal becomes
      Distributable upon entering the Proposal Pool.  Falsely claiming
      that a proposal is submitted as part of an officer's duties is
      the Class 6 Crime of Official Distribunannigans.
d3432 2
a3433 4
History:
Created by Proposal 6342 (Quazie), 11 June 2009
Amended(1) by Proposal 6393 (Wooble; disi.), 10 July 2009
Amended(2) by Proposal 6480 (Murphy), 18 September 2009
d3435 2
a3436 1
----------------------------------------------------------------------
d3438 2
a3439 18
Rule 2267/0 (Power=1.5)
Judge's Proposals

      If the submitter of a Proposal makes a claim that the proposal
      is directly relevant to a specified judgement delivered by em in
      the same message, and does not make such a claim about any other
      proposal in connection with the same judgement, then that
      proposal becomes Distributable upon entering the Proposal Pool.
      Falsely claiming that a proposal is relevant in this fashion is
      the Class 6 Crime of Judicial Distribunannigans.

History:
Created by Proposal 6480 (Murphy), 18 September 2009

----------------------------------------------------------------------

Rule 1950/20 (Power=3)
Voting on Democratic Decisions
d3471 1
a3471 66

----------------------------------------------------------------------

Rule 2156/17 (Power=2)
Voting on Ordinary Decisions

      The eligible voters on an ordinary decision are the players who
      were active at the start of its voting period. The voting limit
      of a player on an ordinary decision is defined elsewhere in the
      rules, but is fixed at the resolution of the Decision and
      thereafter CANNOT change, rules to the contrary notwithstanding.
      This restriction does not prevent a change that would change a
      voting limit from occurring; it only prevents it from actually
      effecting that limit.

History:
Created by Proposal 5078 (Zefram), 18 July 2007
Amended(1) by Proposal 5082 (Zefram), 1 August 2007
Amended(2) by Proposal 5141 (Zefram), 19 August 2007
Amended(3) by Proposal 5276 (Murphy, Pavitra, Zefram), 7 November 2007
Amended(4) by Proposal 5358 (Murphy), 20 December 2007
Retitled by Proposal 5418 (root), 2 February 2008
Amended(5) by Proposal 5418 (root), 2 February 2008
Amended(6) by Proposal 5447 (Pavitra), 24 February 2008
Amended(7) by Proposal 5625 (Murphy, OscarMeyr, Ivan Hope), 29 July
  2008
Amended(8) by Proposal 5679 (BobTHJ), 3 September 2008
Amended(9) by Proposal 5791 (Murphy), 22 October 2008
Amended(10) by Proposal 5985 (Murphy), 7 December 2008
Amended(11) by Proposal 6010 (ais523, Goethe, Murphy, comex,
  OscarMeyr), 14 December 2008
Amended(12) by cleaning (Murphy), 16 August 2009
Amended(13) by Proposal 6499 (Wooble; disi.), 26 September 2009
Amended(14) by Proposal 6531 (Walker), 23 October 2009
Amended(15) twice by Proposal 6549 (coppro; disi.), 13 November 2009
Amended(16) by Proposal 6616 (G., coppro, c., Murphy), 30 January 2010
Amended(17) by Proposal 6697 (coppro), 25 April 2010

----------------------------------------------------------------------

Rule 2279/2 (Power=2)
Voting Limits on Ordinary Decisions

      A player's voting limit on an Ordinary decision is the result of
      performing the following steps, in order:

          (1) Take the Influence Level associated with the player's
              position on the list of succession, or 5 if the player
              is the Speaker.

          (2) Reduce the value by half the number of Rests owned by
              the player.

          (3) Apply any other adjustments defined in other rules, in
              numerical order unless otherwise specified.

          (4) Round the value to the nearest non-negative integer,
              breaking ties upward.

      This rule takes precedence over any other rule which would
      modify a player's voting limit on an ordinary Decision.

History:
Created by Proposal 6549 (coppro; disi.), 13 November 2009
Amended(1) by Proposal 6697 (coppro), 25 April 2010
Amended(2) by Proposal 6821 (G., ais523), 4 September 2010
d3485 1
a3485 2
  * report date of most recent emergency session (rule 2177)
  * report roll call of most recent emergency session (rule 2177)]
a3495 30
Rule 1450/10 (Power=2)
Separation of Powers

      Lest the entire proposal process fall under the control of a
      single entity, any change that would result in the holders of
      Promotor and Assessor being entangled is canceled and does not
      occur, rules to the contrary notwithstanding.

      Lest the entire judicial process fall under the control of a
      single entity, any change that would result in the holder of
      Clerk of the Courts and the owner of Justiciar being entangled
      is canceled and does not occur, rules to the contrary
      notwithstanding.

History:
Created by Proposal 1547, Apr. 14 1995
Amended(1) by Proposal 2442, Feb. 6 1996
Amended(2) by Proposal 3742 (Harlequin), May 8 1998
Amended(3) by Proposal 4576 (root), 31 May 2004
Amended(4) by Proposal 4592 (Murphy), 4 July 2004
Amended(5) by Proposal 4868 (Goethe), 27 August 2006
Power changed from 1 to 2 by Proposal 4868 (Goethe), 27 August 2006
Amended(6) by Proposal 4939 (Murphy), 29 April 2007
Amended(7) by Proposal 5106 (Zefram), 1 August 2007
Amended(8) by Proposal 5476 (Murphy; disi.), 27 March 2008
Amended(9) by Proposal 5602 (Murphy), 29 July 2008
Amended(10) by Proposal 6485 (Murphy), 18 September 2009

----------------------------------------------------------------------

a3512 114
Rule 2134/7 (Power=2)
Win by Clout

      Upon a win announcement that a specified player's voting limit
      on an ordinary decision with a specified Chamber initiated at
      that time would exceed the combined voting limits of all other
      players on that decision, the specified player satisfies the
      Winning Condition of Clout.

      Cleanup procedure:  No player satisfies this Winning Condition
      again during the same month, the remainder of this rule
      notwithstanding.

History:
Created by Proposal 4930 (Goethe), 29 April 2007
Retitled by Proposal 5222 (root; disi.), 30 September 2007
Amended(1) by Proposal 5222 (root; disi.), 30 September 2007
Amended(2) by Proposal 5343 (Murphy), 8 December 2007
Retitled by Proposal 5394 (Murphy, Goddess Eris, OscarMeyr, Zefram),
  16 January 2008
Power changed from 1 to 2 by Proposal 5394 (Murphy, Goddess Eris,
  OscarMeyr, Zefram), 16 January 2008
Amended(3) by Proposal 5394 (Murphy, Goddess Eris, OscarMeyr, Zefram),
  16 January 2008
Amended(4) by Proposal 5418 (root), 2 February 2008
Amended(5) by Proposal 5625 (Murphy, OscarMeyr, Ivan Hope), 29 July
  2008
Amended(6) by Proposal 6624 (Murphy), 20 February 2010
Amended(7) by Proposal 6659 (Murphy; disi.), 10 March 2010

----------------------------------------------------------------------

Rule 2188/2 (Power=1)
Win by Proposal

      Upon a win announcement that a proposal awarding a win to one or
      more persons has been adopted, all those persons satisfy the
      Winning Condition of Legislation.

      Cleanup procedure: None of those persons can satisfy the
      condition again for the same proposal.

History:
Created by Proposal 5394 (Murphy, Goddess Eris, OscarMeyr, Zefram),
  16 January 2008
Amended(1) by Proposal 6162 (comex), 31 March 2009
Power changed from 2 to 1 by Proposal 6198 (Murphy), 27 April 2009
Amended(2) by Proposal 6787 (Murphy; disi.), 22 August 2010

----------------------------------------------------------------------

Rule 2309/1 (Power=1)
The Propose-O-Matic

      The Fearmongor is an Office. Its holder is responsible for
      ensuring the continuous change of the ruleset.

      Each week, the Fearmongor SHALL do the following:

         1) Select two rules at random.

         2) For each of those rules, submit a disinterested proposal
            with AI equal to that rules' power. One proposal SHALL
            specify only to repeal its rule, and, if necessary, to
            make a minimal set of other rule changes so that the game
            is not broken by the repeal; the other SHALL specify only
            to amend its rule.

         3) Submit a disinterested proposal with AI 1. It shall
            specify only the enactment of a rule which is identical to
            a rule which was, at one point, part of the Ruleset, and
            was not chosen for use in this clause in the prior six
            months.

         4) Make each of those proposals Distributable, clearly
            specifying that e is doing so to fulfill eir duties.

      Players MUST NOT make proposals submitted in accordance with
      this rule Undistributable.

History:
Created by Proposal 6798 (coppro), 27 August 2010
Amended(1) by Proposal 6861 (omd), 18 October 2010

----------------------------------------------------------------------

Rule 2322/0 (Power=1)
Groups

      A Group is an Organization with an associated SLC called its
      Ordinances. The Administrator for each Group is that Group's
      Ordinancekeepor, the Executor is its Vizier, and the set of
      Players within the Jurisdiction of its SLC is its Membership.

      A Group's Membership may contain any Player who is not a Member
      of any other Group. Initially, the Group's Membership must
      contain at least three Foundors. The Ordinancekeepor and the
      Vizier of a Group must, at all times, be Members of the Group;
      if either ceases to be a Member of the Group, it dissolves.

      Each Group has Mint Authority.

      A Group's Voting Power on a Democratic Proposal is as follows:

         (a) A Group containing fewer than three members: zero;
         (b) A Group containing at least three members: the number of
             Players divided by the number of Groups with at least
             three members, rounded down.

History:
Created by Proposal 6890 (G.; disi.), 20 November 2010

----------------------------------------------------------------------

a3583 69
Rule 2246/5 (Power=2)
Submitting a CFJ to the Justiciar

      The Justiciar is an imposed office. Its holder is defined else-
      where in the rules.

      The initiator of a judicial case CAN submit it to the Justiciar
      by announcement.  For such a case, the Justiciar CAN, in a
      timely manner, either accept or reject the case by announcement;
      until this time limit expires or the Justiciar rejects the case,
      the CotC CANNOT perform any of eir office's duties with regards
      to the case and does not incur any of eir office's obligations
      with regards to it.

      If the Justiciar accepts the case, e switches places with the
      CotC entirely with regards to that case; that is, e receives all
      obligations and all powers that the CotC would otherwise receive
      due to being CotC, and the CotC receives all obligations and
      powers that the Justiciar would otherwise receive due to being
      Justiciar. This includes any secondary duties required to
      fulfill obligations (such as rotating the bench). This takes
      precedence over Rules that would otherwise assign duties and
      powers regarding a judicial case to the Clerk of the Courts or
      the Justiciar due to holding one of those positions. A player
      CAN deputize for Justiciar to perform these duties as if it were
      an office.

      All persons are ENCOURAGED to submit a case to the Justiciar
      only when there is a good reason not to let it be processed by
      the Clerk of the Courts as usual.

History:
Created by Proposal 6181 (comex), 7 April 2009
Amended(1) by Proposal 6333 (coppro), 29 May 2009
Amended(2) by Proposal 6496 (coppro), 26 September 2009
Amended(3) by Proposal 6662 (Murphy; disi.), 10 March 2010
Amended(4) by Proposal 6752 (Murphy), 2 August 2010
Amended(5) by Proposal 6891 (coppro), 20 November 2010

----------------------------------------------------------------------

Rule 2225/4 (Power=1.5)
Interest Index of Judicial Cases

      Each judicial case has an interest index, which CAN be set by
      its initiator at the time of initiation, or otherwise defaults
      to zero.

      A player CAN, Without N Objections, increase or decrease the
      interest index of a judicial case by 1, where N is 4 minus the
      interest index of that case immediately prior to that change.

      A player CAN set the interest index of a disinterested judicial
      case to 1 by announcement.

      When a player recuses emself from a judicial case whose interest
      index equals eir rank, the case's interest index is increased by
      1 unless the recusing player announces in the same message that
      it should not.

History:
Created by Proposal 5970 (Murphy), 20 November 2008
Amended(1) by Proposal 6176 (Murphy), 7 April 2009
Amended(2) by Proposal 6259 (Quazie), 11 May 2009
Amended(3) by Proposal 6483 (Pavitra), 18 September 2009
Amended(4) by cleaning (Murphy), 2 August 2010

----------------------------------------------------------------------

d3788 1
a3788 1
Rule 2230/15 (Power=2)
a3836 10
      If a NoV is Uncontested and was published at least four days
      ago, any player CAN cause it to become Closed by announcement.
      Any player CAN cause a NoV specifying em as Accused to become
      Closed by announcement. When a NoV becomes Closed, a number of
      Rests are created in the possession of the Accused equal to the
      Class of the specified Crime, or in its absence the Power of the
      violated rule, rounded up.  If a Closed NoV becomes Contested,
      these Rests remain, but CAN be later destroyed by judicial
      processes as described elsewhere.

d3859 1
d3863 1
a3863 1
Rule 1504/48 (Power=2)
a3898 4
      When a judicial question on culpability is judged after a number
      of rests have been created in the Accused's possession due to
      the associated notice, those rests are destroyed.

a3920 5
      * SILENCE with a positive number less than 15 (X). If a
        judgement of SILENCE has been in effect continuously for one
        week (or longer), any player CAN once create a number of Rests
        equal to X in the possession of the ninny, by announcement.

d4039 1
d4043 1
a4043 1
Rule 2277/1 (Power=2)
a4053 5
      If a verdict or sentence that led to the creation of Rests is
      overruled, remanded, or reassigned, the Rests are still
      considered to have been created, but any player CAN destroy any
      Rests thus created by announcement.

d4062 1
d4371 1
a4371 1
Rule 1868/16 (Power=2)
d4388 7
a4394 5
      case are the active players who have not previously been
      assigned as its judge, subject to modification by other rules.
      Being unqualified to be assigned as a judge does not inherently
      prevent an entity from continuing to be judge of a case to which
      e is already assigned.
d4443 1
a4531 44
Rule 2226/4 (Power=1.5)
Judicial Rank

      Judicial rank is a player switch, tracked by the Clerk of the
      Courts, with the same range and default as interest indices.

      A player is poorly qualified to judge judicial cases whose
      interest index exceeds eir judicial rank.

      A player CAN flip eir judicial rank to any value by
      announcement, unless eir rank was decreased due to an overrule
      within the past 30 days.

      When an appeal of a judicial case is judged with prejudice, if
      the prior judge's judicial rank is higher than 0, then it is
      decreased by 1.

      A player CAN flip eir judicial rank from 0 to 1 with 3 support.

      "Supreme", "Circuit", "District", and "Night" are synonymous
      with judicial ranks 3, 2, 1, and 0, respectively.

History:
Created by Proposal 5970 (Murphy), 20 November 2008
Amended(1) by Proposal 6387 (Wooble), 10 July 2009
Amended(2) by Proposal 6407 (Wooble), 7 August 2009
Amended(3) by Proposal 6472 (Murphy), 15 September 2009
Amended(4) by Proposal 6705 (comex), 25 April 2010

----------------------------------------------------------------------

Rule 2248/0 (Power=2)
Second-Class Judges

      If any first-class member of a second-class person's basis would
      be unqualified to judge a given judicial case, even if e were
      registered, active, standing, hemming-and-hawing, and Supreme,
      then that second-class person is unqualified to judge that case.

History:
Created by Proposal 6279 (Murphy), 19 May 2009

----------------------------------------------------------------------

a4588 546
Economy
      A category concerning the simplest style of competition between
      players.
----------------------------------------------------------------------

Rule 2166/16 (Power=2)
Assets

      An asset is an entity defined as such by a rule or contest
      (hereafter its backing document), and existing solely because
      its backing document defines its existence.

      Each asset has exactly one owner.  If an asset would otherwise
      lack an owner, it is owned by the Lost and Found Department.  If
      an asset's backing document restricts its ownership to a class
      of entities, then that asset CANNOT be gained by or transferred
      to an entity outside that class, and is transferred to the Lost
      and Found Department if it is owned by an entity outside that
      class.  If an asset is owned by the Lost and Found department
      any player CAN transfer or destroy it without objection.

      The Lost and Found department may own any asset, and have assets
      transferred to and from it, regardless of the asset's backing
      document or any Rule, Rules to the contrary notwithstanding.

      The recordkeepor of a class of assets is the entity (if any)
      defined as such by, and bound by, its backing document.  That
      entity's report includes a list of all instances of that class
      and their owners.  This portion of that entity's report is
      self-ratifying.

      An asset whose backing document is not a rule generally CAN be
      created by its recordkeepor by announcement, subject to
      modification by its backing document.  To "gain" an asset is to
      have it created in one's possession; to "award" an asset to an
      entity is to create it in that entity's possession.

      An asset generally CAN be destroyed by its owner by
      announcement, and an asset owned by the Lost and Found
      Department generally CAN be destroyed by its recordkeepor by
      announcement, subject to modification by its backing document.
      To "lose" (syn. "spend") an asset is to have it destroyed from
      one's possession; to "revoke" an asset from an entity is to
      destroy it from that entity's possession.

      An asset generally CAN be transferred by its owner to another
      entity by announcement, subject to modification by its backing
      document.  A fixed asset is one defined as such by its backing
      document, and CANNOT be transferred; any other asset is liquid.

      A currency is a class of asset defined as such by its backing
      document.  Instances of a currency with the same owner are
      fungible.  The Minimum Unit Quantity (MUQ) of each currency is
      one.

[CFJs 1790-1791 (called 11 November 2007): The self-ratifying asset
report is the complete list of ownerships of assets of that class; a
partial list does not self-ratify.]

[CFJ 1850 (called 22 December 2007): The general ability of the
recordkeepor to create assets does not include an ability to determine
who possesses them when created, so they are necessarily owned by the
Lost and Found Department [at the time of CFJ 1850, the Bank] upon
creation.]

[CFJ 1910 (called 10 March 2008): When an existing entity is defined
as an asset, the change of its owner from "undefined" to the Lost and
Found Department [Bank at the time of CFJ 1910] counts as a transfer,
and fails if the Lost and Found Department is outside of the class of
objects that can own the entity.]

[CFJ 2176 (called 22 September 2008): Entities may be fungible even if
not defined as such by this rule.]

[CFJ 2309 (called 11 December 2008): If two separate documents attempt
to define an asset with the same name, they refer to the same entity,
but the entity is not an asset.]

History:
Created by Proposal 5173 (Murphy), 29 August 2007
Amended(1) by Proposal 5216 (Murphy), 13 September 2007
Amended(2) by Proposal 5388 (Murphy), 1 January 2008
Amended(3) by Proposal 5475 (Murphy), 24 March 2008
Amended(4) by Proposal 5476 (Murphy; disi.), 27 March 2008
Amended(5) by Proposal 5496 (Murphy), 23 April 2008
Amended(6) by Proposal 5833 (Murphy, Taral), 12 November 2008
Amended(7) by Proposal 5840 (root), 12 November 2008
Amended(8) by Proposal 5974 (Murphy; disi.), 25 November 2008
Amended(9) by Proposal 6023 (Murphy), 22 December 2008
Assigned to Committee on Finance by Proposal 6053 (Murphy, woggle,
  ais523), 23 January 2009
Amended(10) by Proposal 6161 (Murphy), 31 March 2009
Amended(11) by Proposal 6253 (Quazie), 9 May 2009
Amended(12) by cleaning (Murphy), 16 August 2009
Amended(13) by Proposal 6430 (coppro; disi.), 18 August 2009
Amended(14) twice by Proposal 6650 (coppro), 10 March 2010
Amended(15) by Proposal 6792 (omd), 27 August 2010
Amended(16) by Proposal 6916 (omd; disi.), 2 January 2011

----------------------------------------------------------------------

Rule 2282/4 (Power=2)
Energy

      Ergs are a class of fixed assets and a measure of each Player's
      energy; to increase or decrease an entity's energy is to change
      the number of ergs in eir possession.  Ownership of Ergs is
      restricted to players.

      At the beginning of each week:
       (a) All ergs and capacitors are destroyed; then
       (b) For each capacitor destroyed in item (a), an erg is awarded
           to its former owner.
       (c) For each player, that player is awarded 6 ergs if e is the
           Captain, 5 ergs if e is a Pilot, 3 ergs if e is a Marine,
           and 4 ergs otherwise; then
       (d) For each office, its holder is awarded a number of ergs
           equal to the interest index of that office.

      When a player registers, e is awarded 7 ergs.

      The Power Station Manager (PSM) is an office and the
      recordkeepor of ergs.  Eir weekly report shall include a list of
      all erg transactions of the previous week.

[Cross-references (30 January 2010): the Power Station Manager's
duties are:
  * recordkeepor of ergs (rule 2282)]

History:
Created by Proposal 6616 (G., coppro, c., Murphy), 30 January 2010
Amended(1) by Proposal 6632 (Yally), 20 February 2010
Amended(2) by Proposal 6682 (coppro), 5 April 2010
Amended(3) by Proposal 6679 (coppro), 22 March 2010
Amended(4) by Proposal 6804 (Murphy; disi.), 27 August 2010

----------------------------------------------------------------------

Rule 2289/1 (Power=2)
Capacitors

      Capacitors are a class of fixed assets tracked by the PSM; their
      ownership is restricted to players.

      When an event is described as earning a player a number of
      farads, e CAN, once per such event and in a timely fashion,
      award emself an equal number of capacitors (or half as many
      ergs, rounded down) by announcement, but only if e cites the
      specific event allowing em to do so in the announcement.

History:
Created by Proposal 6679 (coppro), 22 March 2010
Amended(1) by Proposal 6822 (Tanner L. Swett), 10 September 2010

----------------------------------------------------------------------

Rule 2295/1 (Power=2)
Rewards

      Whenever a player judges a case on time, e earns an number of
      farads equal to its interest index.

      Whenever a proposal is adopted, its author earns a number of
      farads equal to its interest index.

History:
Created by Proposal 6710 (coppro), 8 May 2010
Amended(1) by Proposal 6750 (Wooble; disi.), 20 July 2010

----------------------------------------------------------------------

Rule 2283/4 (Power=2)
Fees

      If the Rules associate a non-negative cost, price, charge, or
      fee with an action, that action is a fee-based action.  If the
      specified cost is not an integer, the actual fee is the next
      highest integer.

      A rule which purports to allow a person to perform an action for
      a fee thereby allows em to perform the action by announcement
      provided that:

         (a) in the announcement, e states that there is a fee for
             that action, and

         (b) the number of ergs in eir possession is greater than or
             equal to the fee.

      Upon such an announcement, a number of ergs equal to the fee is
      destroyed in eir possession.

      An attempt to perform a fee-based action is also implicitly a
      claim to be in possession of sufficient ergs to perform the
      action, and such a claim is self-ratifying.  If the claim is
      erroneous but self-ratifies, then the action is deemed to have
      occurred and destroyed all ergs in the possession of the
      claimant.  Making such a claim falsely is the Class-2 Crime of
      Assaulting the Batteries, but it is generally appropriate to
      DISCHARGE such a crime if it is disputed within four days.

      If the cost is explicitly associated with a specific non-erg,
      currently-existing currency, then the above applies with respect
      to the specified currency instead of ergs.

History:
Created by Proposal 6616 (G., coppro, c., Murphy), 30 January 2010
Amended(1) by Proposal 6725 (coppro; disi.), 22 May 2010
Amended(2) by cleaning (Keba), 29 August 2010
Amended(3) by Proposal 6867 (omd; disi.), 8 November 2010
Amended(4) by Proposal 6889 (G.; disi.), 20 November 2010

----------------------------------------------------------------------

Rule 2284/7 (Power=2)
Fee-based actions

      - A player CAN increase eir voting limit on a specified decision
        to adopt a proposal in its voting period by 2Q, by paying a
        fee of Q.  This rule defers to other Rules that define maximum
        voting limits.

      - A player CAN make a non-urgent proposal Distributable for a
        charge of 1 erg.

      - A player CAN make an urgent proposal Distributable for a
        charge of 3 ergs.

      - A player CAN make a proposal Undistributable for a charge of 2
        ergs.

      - A player CAN destroy a Rest in the possession of another
        player for a charge of 2 ergs.  A player CAN destroy one of
        eir own Rests for a charge of 3 ergs.

      - A player CAN make an ongoing Ordinary decision Democratic for
        a charge of 3 ergs.

      - A player CAN initiate an election for a specified Office for a
        charge of 3 ergs unless there is an ongoing election for that
        office.

      - A player CAN destroy an erg in the possession of a specified
        player for a charge of 2 ergs. The PSM SHALL note such a
        destruction in eir report.

      - A player CAN award emself a capacitor for a charge of 3 ergs.

      - A player CAN move an indicated player an indicated number of
        positions P on the list in an indicated direction (up or down)
        for a charge equal to one half (rounded down) of the sum of
        the Influence Levels of all the positions between the
        indicated player's starting and ending positions, inclusive.

History:
Created by Proposal 6616 (G., coppro, c., Murphy), 30 January 2010
Amended(1) by Proposal 6630 (Yally; disi.), 20 February 2010
Amended(2) by Proposal 6633 (coppro; disi.), 20 February 2010
Amended(3) by Proposal 6638 (Yally), 20 February 2010
Amended(4) by Proposal 6735 (coppro), 13 June 2010
Amended(5) by Proposal 6816 (G., Keba), 4 September 2010
Amended(6) by Proposal 6821 (G., ais523), 4 September 2010
Amended(7) by Proposal 6865 (G., coppro), 8 November 2010

----------------------------------------------------------------------

Rule 2287/7 (Power=1)
Props

      Props are a currency.

      The Air Traffic Controller is an office and the recordkeepor of
      props.

      Ownership of props is limited to first-class players.  Props
      CANNOT be created, transferred, or destroyed except as allowed
      by this rule or required by the rules in general.

      When a first-class player registers, 14 props are created in eir
      possession.  When a first-class player deregisters, eir props
      are destroyed.

      Once per week, each player CAN transfer a prop from one player
      to another, provided that e explains why e chose each player,
      and does not transfer it to emself.

      At the beginning of each quarter, one prop in the possession of
      each player possessing more than fourteen props is destroyed,
      and one prop is created in the possession of each player
      possessing less than fourteen props.

      Players with at least 19 props are Pilots; the Pilot with the
      most props (if any) is the Captain. Players with less than 9
      props are Marines.  As soon as possible after any of these
      statuses change, the Air Traffic Controller SHALL announce it.

      Upon a win announcement that one or more players each possess at
      least 30 props, all those players satisfy the Winning Condition
      of Respect.

      Cleanup procedure: All props are destroyed and 14 props are
      created in the possession of each player.

History:
Created by Proposal 6647 (Murphy), 6 March 2010
Amended(1) by Proposal 6676 (coppro), 22 March 2010
Amended(2) by Proposal 6677 (coppro), 22 March 2010
Amended(3) by Proposal 6763 (Yally), 4 August 2010
Amended(4) by Proposal 6799 (Keba; disi.), 27 August 2010
Amended(5) by Proposal 6803 (Murphy; disi.), 27 August 2010
Amended(6) by Proposal 6829 (Keba), 10 September 2010
Amended(7) by Proposal 6886 (Yally), 20 November 2010

----------------------------------------------------------------------

Rule 2293/2 (Power=1.7)
Leadership Tokens

      Leadership Tokens are a currency tracked by the Herald. A player
      CANNOT destroy (redeem) Leadership Tokens in eir possession
      except by announcement and for a specified one of the following
      effects:

        (a) A player CAN redeem 3 Leadership Tokens in eir possession
            to satisfy the Winning Condition of Leadership.
        (b) A player CAN redeem 1 Leadership Token in eir possession
            to destroy up to 4 Rests e owns.
        (c) A player CAN redeem 1 Leadership Token in eir possession
            to award emself 7 ergs.
        (d) A player CAN redeem 1 Leadership Token in eir possession
            to move any  player up or down by up to 5 spots on the
            List of Succession.

History:
Created by Proposal 6708 (coppro, comex, woggle), 4 May 2010
Power changed from 1 to 1.7 by Proposal 6708 (coppro, comex, woggle),
  4 May 2010
Amended(1) by Proposal 6876 (G.), 8 November 2010
Amended(2) by Proposal 6897 (scshunt), 5 December 2010

----------------------------------------------------------------------

Rule 2308/0 (Power=1)
Contests

      A player CAN make a non-contest document into a contest without
      3 objections; he then becomes that contest's contestmaster.  The
      document should contain a list of instructions for the players
      of Agora to play a type of subgame, which should be fair and
      generally allow all players to join and participate on an equal
      footing.  Anyone CAN cause a contest to cease to be a contest
      with notice and with 3 support.

      The contest's instructions should include conditions under which
      persons "win the contest".  Upon an announcement by the
      contestmaster that one or more persons satisfy those conditions,
      all those persons satisfy the Winning Condition of Game Club.
      Intentionally making a false such announcement is the Class-4
      Crime of Gaming the System.

      The contestmaster's weekly report contains all matters defined
      by the instructions to be part of eir weekly report, as well as
      the instructions.

      The contestmaster is, prima facie, the adjudicator of contest
      instructions and disputes.  Disputes should in general, be
      resolved with the spirit of the instructions in mind.  For the
      purpose of determining the internal gamestate of a contest
      (including whether its contestmaster falsely announced that
      persons won the contest), its instructions are generally
      interpreted in the same manner as a rule, but the reasonable
      opinion of the contestmaster takes precedence.  The
      contestmaster CAN change the instructions, or any internal
      gamestate defined by them, without 3 objections, but SHOULD only
      do so to improve gameplay or resolve disputes within the spirit
      of the original contest.  E can also appoint a new contestmaster
      without objection.

      An entity is bound by a contest if and only if it is its
      contestmaster.

History:
Created by Proposal 6792 (omd), 27 August 2010

----------------------------------------------------------------------

Rule 2320/2 (Power=1)
Auctions and the Default Auction Procedure

      When an Auction is to be held and the procedure is not
      specified, the Auctioneer may select a rules-d