Skip to main content

Title 4 — Communication Protocols

NAP 9 governance depends on clear, verifiable, and standardized communication across alliances.

This Title establishes which platforms are binding, how information must be delivered, and the etiquette required for orderly governance.

Definitions Table​

The following terms are used throughout Title 4 and carry the meanings defined below.

TermDefinition
Authoritative PlatformA platform designated as binding for governance actions, evidence, votes, and procedural communication.
NAP DiscordThe primary and authoritative governance server where all official actions occur.
1866 Public DiscordA secondary server used for visibility, public notices, and informal outreach; not binding for governance.
In-Game ChatCommunications conducted through Last War in-game channels (WC, PMs, Moments); used only for notifications or alerts.
AnnouncementA Clerk-certified or Council-certified message posted in a designated channel that constitutes an official act under the Covenant.
Deliberation ChannelThe specific channel in NAP Discord where Council discussion occurs prior to votes.
Vote TextThe formal written text that defines the scope, question, or motion being voted upon.
Server Time (ST)The unified time standard used for all deadlines, votes, posts, evidence timestamps, and archives.
Notice PeriodA required period during which an announcement must remain visible before a vote may proceed (commonly used for amendments).
Procedure ChallengeA formally raised concern about whether communication or action adhered to established governance rules.

Article I — Platform Hierarchy​

Official Channels

Only specific platforms and channels are recognized as authoritative for NAP 9 governance.

Section 1 — Binding Platforms​

The following hierarchy establishes which platforms carry binding authority:

  1. NAP Discord (Authoritative)

    • Required for: evidence submission, case creation, vote windows, announcements, penalty notices, procedural motions, and archival records.
    • If a communication is not posted here, it does not have governance authority.

  2. 1866 Public Discord (Non-Binding, Informational)

    • May mirror announcements for visibility.
    • Does not create obligations, rights, penalties, or deadlines.

  3. In-Game Chat / Direct Messages / Moments (Non-Binding)

    • May be used to alert alliances to emergencies or pending matters.
    • Never substitutes for official postings.
    • Not admissible as binding communication except as evidence, following Title 6.

Section 2 — Invalid Communications​

Any announcement, vote, ruling, or procedural instruction delivered outside NAP Discord is null and void unless subsequently reposted and certified in an authoritative channel.

Article II — Server Time (ST) Standard​

Section 1 — Uniform Timekeeping​

All governance actions use Server Time (ST), including but not limited to:

  • Voting windows
  • Penalty deadlines
  • Evidence timestamps
  • Case creation times
  • Notice periods
  • Appeal deadlines

Section 2 — Time Zone Conflicts​

Time-stamped evidence, cases, or announcements that do not align with Server Time may be returned for correction.
Repeated submission of mismatched timestamps may be treated as procedural noncompliance.

Article III — Announcement Protocol​

Announcements

Defines where, how, and by whom binding communication must be issued.

Section 1 — Binding Announcements​

Binding announcements must be posted by a Clerk or authorized Representative in:

  • #nap-announcements — for official Council decisions, penalties, amendments, and system updates
  • #case-log — for case creation, evidence updates, vote openings, and vote certification

Only these channels constitute the authoritative record.

Section 2 — Deliberation Channels​

All formal deliberation must occur in:

  • #nap-council-chat — Council discussion and clarifications
  • #nap-council-votes — vote logging and certification (read-only except for Clerks)

Associate Members may read announcements but may not participate in deliberation.

Section 3 — Amendment Notices​

Amendment proposals must:

  • Be posted in #nap-proposals
  • Include a clear summary and full text
  • Remain visible for the required notice period prior to voting
  • Identify all sections and Titles affected

Failure to follow this protocol invalidates the vote.

Article IV — Communication Etiquette​

Section 1 — Conduct Standards​

All participants must:

  • Keep messages concise, relevant, and free of inflammatory tone
  • Avoid personal attacks, sarcasm, or excessive argument loops
  • Request clarification respectfully and cite the relevant Title/Article/Section when challenging procedure

Section 2 — Prohibited Actions​

Participants may not:

  • DM Clerks evidence or attempt to privately influence procedural decisions
  • Submit vote text via reactions, emojis, screenshots, or ambiguous wording
  • Attempt to negotiate, threaten, or pressure participants outside official channels
  • Edit or delete posts that contain procedural or governance content except for formatting

Section 3 — Vote Text Requirements​

Vote text must be:

  • Explicit, written, and unambiguous
  • Posted by a Clerk at the start of the vote window
  • Immutable once voting begins
  • Free of emojis or reaction-based substitutes

Any vote cast without a formal vote text is invalid.

Last amended by Council vote [not amended].