Skip to main content

🏛️ Council Inception Protocol

Scenario

How Server 1866 forms the very first NAP 9 Council

The following document describes exactly how the initial NAP 9 Council is created, how temporary authorities function, and how the system transitions into full procedural governance.

1. Purpose of the Inception Process

NAP 9 requires:

  • 9 Full Member seats
  • Clerks from 3 different alliances
  • Working Discord infrastructure
  • Verified voting representatives

But none of this exists on Day 0.
The Council Inception Protocol creates a controlled bridge between:

  • the legacy NAP (if any)
  • unstructured diplomacy
  • the fully operational NAP 9 system

This phase MUST be short, neutral, and transparent.

2. The Transitionary Council

Important

A temporary body known as the Transitionary Council is formed to bootstrap the system.

The KY Colonel and sheriff girliion are appointed to assist with information dissemination and diplomacy.

Requirements​

  • Minimum 5 alliances, ideally more
  • Each alliance designates an R5 or diplomat as its provisional rep
  • These reps do not hold permanent Council seats
  • They exist only to stand up the structure

Duties​

The Transitionary Council:

  • Approves the creation of the NAP 9 Discord
  • Confirms the temporary Clerks
  • Invites eligible alliances
  • Communicates reforms to the server
  • Oversees setup of roles, channels, and permissions
  • Ensures no single alliance exerts disproportionate control during setup

Duration​

  • Minimum: 24 hours
  • Maximum: 72 hours

After that, the body dissolves automatically and is replaced by the Council.

3. Transitionary Clerks (Bootstrap Operators)

Important

Until permanent Clerks are elected, the system requires neutral technicians.

These bootstrap operators:

  • validate early membership petitions
  • maintain the channel structure
  • support the import of alliances
  • coordinate sign-offs
  • ensure the Covenant is published unedited

Named Individuals​

  • deputy konpy
  • potekima
  • ZoeKween

These individuals serve ONLY until the permanent election occurs.

They cannot open cases, classify offenses, issue penalties, or initiate any binding votes unless it concerns the inception process itself.

4. Standing Up the Discord Server

Important

Currently various members of GMOB who have volunteered are anticipated to support the transition.

deputy konpy (as primary server architect) performs:

  • channel creation
  • role stubs
  • Clerk permissions
  • Council permissions
  • evidence/log architecture
  • pinning rules
  • read-only / vote windows structure

ZoeKween assists with creation and auditing server functionality.

potekima assists with supporting NAP knowledge.

This server becomes the permanent home for NAP 9 governance.

5. Onboarding Alliances Into NAP 9

Roles

What must be done for each expected alliance during this phase

1. Eligible Full Members​

Identify the top 9 alliances by weekly power ranking.
Invite their R5 + Delegate to the server.

2. Associates​

If alliances request Associate status during the transition period, they may be placed:

  • directly into the Associate list (if slots exist), or
  • queued in the timestamped waitlist

3. Non-Members​

They receive information only.
They cannot interact with cases or governance.

6. Activating the First Real Council

Activation

Once the server infrastructure and membership roster are complete, these steps activate the first Council

Step 1 — Confirm the 9 Full Member seats​

  • Each alliance provides:
    • Voting Rep
    • Alternate Delegate
  • Transitionary Clerks verify the list

Step 2 — Initial Council convenes​

Transitionary Clerks summon the first meeting:

@Council — Please acknowledge that you are ready to constitute the First Council of NAP 9. Once all nine seats confirm, the Transitionary Council will dissolve.

Step 3 — Elect permanent Clerks​

NAP 9 requires three Clerks from three different alliances.

Process:

1. Nominations open for 12 hours  
2. Discussion window (optional)  
3. 16h vote  
4. Top 3 (meeting eligibility rules) become the inaugural Clerk cohort

Step 4 — Dissolution of the Transitionary Council​

This is automatic AND mandatory.

The Transitionary Council dissolves.  
Transitionary Clerks revert to normal leadership roles.  
NAP 9 enters full operational state.

7. Post-Inception Stabilization

Once the first Council and Clerk cohort are active:

  • the Clerk team confirms evidence standards
  • the Council confirms communication norms
  • the server begins accepting live cases
  • the amendment pipeline opens
  • Associate queue becomes active
  • participation tracking begins

This moment marks Day 1 of NAP 9 governance.

8. TL;DR Version (Player-Friendly)

1. Get 5+ alliances to agree NAP 9 should begin  
2. Create a transitionary council (24–72h)  
3. Konpy builds the server; various GMOB members support  
4. Invite all top 9 alliances  
5. Bring in Associates, create waitlist  
6. First real Council confirms itself  
7. Elect 3 Clerks  
8. Transitionary structures dissolve  
9. NAP 9 starts for real