Skip to main content

Title 13 — Amendments

This Title establishes the formal process for modifying the NAP 9 Covenant.
Amendments keep the framework adaptive while preserving legitimacy and procedural stability.

⚖️ Definitions​

TermDefinition
AmendmentA formal modification to any section of the NAP 9 Covenant.
Notice PeriodA mandatory waiting window before a vote may begin.
AdditiveAn amendment that introduces new text without altering existing provisions.
RevisoryAn amendment that modifies or replaces existing text.
RepealAn amendment that removes text.
StructuralAn amendment altering Titles, Articles, or overall organization.

Article I — Authority to Propose​

Section I — Eligible Proposers​

The following may submit amendments:

  • Any Full Member R5
  • Any designated Full Member delegate
  • Any Clerk (procedural or structural matters only)
  • A coalition of three Associate Members acting jointly

Section II — Ineligible Parties​

Individual players may not submit amendments directly; they must petition their R5 for sponsorship.

Article II — Proposal Requirements​

Section I — Required Contents​

A valid amendment proposal must include:

  • Exact section(s) to be modified
  • Full proposed text
  • A justification (1–5 sentences)
  • Amendment type: additive, revisory, repeal, structural
  • Retroactivity indicator (default: non-retroactive)
  • Activation timing or implementation schedule
  • Optional sunset clause

Section II — Clerk Validation​

Missing or incomplete elements result in Clerk rejection and required resubmission.

Article III — Notice & Posting​

Section I — Submission​

Proposers must submit to:

NAP Discord → #nap-proposals and notify Clerks.

Section II — Clerk Actions​

Clerks:

  1. Validate the proposal
  2. Assign an Amendment ID (A-YYMMDD-XX)
  3. Post to:
    • #nap-proposals (discussion)
    • #nap-announcements (read-only)

Section III — Notice Period​

A 24-hour Notice Period is required before voting begins.
Substantive edits reset the Notice Period.

Article IV — Voting Procedure​

Section I — Vote Window​

After Notice, Clerks open a 24-hour Long Vote.

Section II — Requirements​

  • Quorum: 5 votes
  • Passage: Supermajority (≥7 YES)
  • Abstain counts toward quorum
  • Absence does not
  • Votes are locked upon posting

Article V — Activation & Conflict Handling​

Section I — Activation​

Unless otherwise specified, amendments activate immediately upon passage.

Section II — Conflicts​

When an amendment conflicts with older text:

  • The amendment supersedes prior text immediately
  • Clerks mark superseded portions as RETIRED in the archives

Article VI — Failure & Reintroduction​

Section I — Waiting Period​

A failed amendment may not be resubmitted for 7 days.

Section II — Substantial Revision Exception​

If two Clerks jointly certify that the amendment has undergone substantial revision, it may be resubmitted immediately.

Article VII — Emergency Amendments​

Section I — Invocation​

Emergency status may be invoked when immediate action is required to prevent server-level harm and five (5) R5s jointly call it.

Section II — Procedure​

  • 1-hour Notice
  • 8-hour Vote
  • Supermajority (7 YES) required

Section III — Duration​

Emergency amendments expire in 30 days unless passed again through the standard process.

Article VIII — Conflicts of Interest​

Section I — Recusal​

An R5 must recuse if an amendment:

  • Targets their alliance
  • Targets their position
  • Grants them unique privileges

The Alternate votes instead.
If both are conflicted, the seat auto-ABSTAINS.

Article IX — Archive Requirements​

Section I — Archive Contents​

Clerks must store:

  • Amendment ID
  • Original and revised text
  • Vote breakdown
  • Activation/sunset details
  • Conflict-of-interest substitutions
  • Discussion records

Section II — Accessibility​

Archives must remain accessible to all Full Member R5s.

Article X — Workflow Summary (Non-Binding)​

  1. Proposal submitted → Clerk review
  2. Clerk validation → Amendment ID → 24h Notice
  3. 24h vote → 7 YES to pass
  4. Activation per text → archives updated → superseded text retired

Last amended by Council vote [not amended].