Skip to main content

Design Principles for NAP 9

Reference sheet for future edits, training, and audits. Use these principles to keep the system coherent as it evolves.

1) Clarity Over Completeness​

  • Prefer short, explicit rules to long, fuzzy ones.
  • Define inputs and outputs; avoid moral language and intent guessing.

2) Procedure Before Preference​

  • Cases begin only after a Clerk logs evidence.
  • Votes run on set windows; outcomes follow thresholds.
  • No “special exceptions” without an amendment or emergency vote.

3) Small, Accountable Governance​

  • Nine voting seats; quorum 5; supermajority 7.
  • Participation is enforced; silence has costs.
  • Delegates and alternates prevent empty chairs.

4) Neutral Operators​

  • Clerks run process, not politics.
  • Evidence, IDs, votes, and archives stay consistent regardless of alliances involved.

5) Predictable Escalation​

  • Behavior → category → penalty.
  • Repetition auto-escalates; evasion/tampering trigger higher scrutiny.
  • Tag-drop remains the only automatic blacklist rule.

6) Public, Timestamped Evidence​

  • No DM evidence; no cropped or edited media.
  • Server Time everywhere.
  • Invalid evidence = invalid case.

7) Land is Scheduled, Not Contested​

  • L6 rotation is scheduled infrastructure.
  • Non-Members have no land protection; Associates have L1–L5 only.
  • Capitol is free combat by consent with restitution rules.

8) Built for Real Behavior​

  • Assume people are busy, biased, and occasionally hostile.
  • Make compliance easy (clear steps, clear penalties).
  • Archive relentlessly to preserve memory and precedent.

9) Adaptive, Not Chaotic​

  • Use notice + supermajority for normal change; emergency amendments expire if not ratified.
  • Conflict-of-interest rules protect legitimacy.

10) Player-Legible Outputs​

  • Quickrefs, macros, and summaries help non-lawyers stay compliant.
  • Avoid jargon where a simple verb works.