Skip to main content

The Theory Driving NAP 9

How to build a NAP people will actually use on Server 1866

0. Why NAP 15 Failed​

  • Assumed ideal behavior: all R5s active, everyone wants to govern, evidence manages itself.
  • Too many seats, vague rules, zero institutional memory.
  • Result: selective enforcement, “vibes” decisions, stalled votes.

1. Design Principle​

“As few people as possible, with as much clarity as possible.”

  • Small enough to act fast.
  • Clear enough for half-asleep leaders.
  • Structured enough that personal drama cannot break it.
  • Simple enough that enforcement is predictable.

2. Why 9 Seats?​

Decision groups degrade after ~9–11 members. Nine is the governance sweet spot: coordination without consolidation, resilient to absences, stable during disputes. NAP 15 was too big; NAP 5 would centralize too far.

3. Clerks vs. Council​

  • R5s are busy, biased, or asleep; they shouldn’t run process.
  • Clerks handle evidence, cases, votes, and archives; Council judges outcomes.
  • Separation makes the system institutional, not personal.

4. Categorize Behavior, Don’t Debate Intent​

Humans argue intent forever. NAP 9 uses Minor → Moderate → Severe and predefined penalties. If behavior fits the category, apply the penalty—no psychoanalysis.

5. The Only Automatic Blacklist: Tag-Dropping​

  • Tag-drop hides identity and destabilizes diplomacy.
  • Instance 1 → 48h ban (untagged).
  • Instance 2 → automatic permanent blacklist (Supermajority to overturn).
  • Avoids drama by removing human discretion from the most volatile behavior.

6. Strict Land Rules​

Land is scarce, political, and tied to identity. NAP 9 keeps it predictable:

  • L6 rotation for Top 3 only.
  • Non-Members lose all land protection and must drop L6.
  • Diplomacy is mandatory; surprise takeovers are violations.

7. Protection vs. Independence​

You can be protected or independent, not both. Opting out means:

  • lose protection
  • drop L6 immediately
  • L1–L5 can be seized freely
  • cannot file cases or claim restitution

Clean boundaries reduce drama and exploitation.

8. Asynchronous Voting​

People sleep and work. Vote windows (24h/16h/8h) with quorum 5/9 keep throughput high across time zones. Participation is enforced; stalled votes become rare.

9. Why ABSTAIN Matters​

ABSTAIN enables conflict-of-interest recusal and acknowledges uncertainty without forcing bad votes. It stabilizes outcomes and preserves diplomacy.

10. Evidence Has to Be Harsh​

DMs lie, timestamps vanish, context gets cropped. Strict standards (uncropped, timestamped, in #evidence) are the price of legitimacy. Shaky cases erode trust and kill compliance.

11. Escalation Is Automatic​

Repetition and evasion climb tiers by rule (2 Minors → Moderate; 2 Moderates → Severe; evasion/tampering → Severe/Supermajority review). Consistency beats ad hoc debate—and teaches caution.

12. Amendments Keep the System Alive​

Servers change; static NAPs decay. Notice periods, supermajority, archives, and emergency amendments make adaptation legitimate instead of chaotic.

13. The Iron Rule​

A NAP must be structured enough to function and simple enough to survive human behavior.

NAP 9 is engineered for real people: clear, enforceable, predictable, and resilient.