A Love Letter in Governance to the 1866 Community
NAP 9 was an operationally lightweight but technically dense approach to governing Server 1866. It was written by potekima to be very simple to interface with during operations, but very strictly defined under the hood to leave little room for arguments over language or edge-cases.
It was also crafted to be modular and adaptable to discussion. The idea was that the NAP would be proposed to the community leadership with a very abstracted but conceptually complete "For Dummies" introduction along with the philosophy driving the decisions available. This would hopefully open the floor for a diagloue about what specifically is and is not important to include in our NAP.
The hosting, presentation of information, implementation of custom code and CSS, configuration of CI/CD pipelines, creation of branding, and so forth were a combined effort of potekima and her girlfriend konpy, with generous support from other GMOB leadership (and Cliff) on critique.
The tagline “Love Letter in Governance” is no accident. There was a lot of passion about contributing something meaningful for the community, and a ton of reflection went into deciding on balanced features that would address a variety of very real concerns about having a leadership that actually works! The hope was to cultivate a system that doesn't make people feel powerless to change the server, and therefore make such participants less inclined to abandon the server as a dramatic, lawless, lost cause.
The hope was that the skeleton of this document - the hosting platform, the basic flow and structure, core ideas - would remain the mostly same, but that a joint impassioned collaboration between members of the community who have long had issues with our NAP would enthusiastically engage in an active constructive dialogue about what to change now that the opportunity to do so was topical and imminent.
The CI/CD pipeline was agile, and changes could be altered, committed, and credited nearly instantly with this architecture. Active specific published changes were explicitly planned for.
Unfortunately, what little engagement was afforded to NAP 9 seemed to waver between “too long, didn't read” and “no thanks, something else” despite mitigation efforts to hopefully avoid having to discard the platform entirely.
I hope that someone will actually write a NAP for 1866 instead of suggesting what it could look like if someone else would just write it for them. I hope that when they do that, they get it perfectly right the first time.
NAP 9 was built from first principles to deliver clear, predictable governance that alliances can actually rely on.
Designed for real player behavior, NAP 9 keeps systems simple, voting reliable, and enforcement unmistakably fair.
By shrinking governance to the smallest stable group, NAP 9 creates a system that is fast, enforceable, and built to last.