If the person currently hosting the AOI server and domain takes the project in a direction that the majority of the community disagrees with, there should always be an implicit (or explicit) check in place.
The current owner/administrator of AOI should always contend with the threat of losing control to the will of the majority:
“Screw this guy, we can always fork the game, start a new domain, and run our own instance, and take the players & coders with us.”
The *ideal* is to avoid this scenario through respectful dialogue and consensus-building. Splitting the playerbase and coderbase is not a great outcome. Still, leaving the door open for this kind of “peaceful fork” ensures transparency, accountability, and reinforces Goal 1.
I - Steve - am committed to keeping AOI alive for as long as I live — and I trust myself to do that. But it's worth planning for the unexpected:
The solution: The AOI game server, the documentation on how to make it work, and the means to run it, need to be distributed on a regular basis to ~5 or so key founding members. As key founding members fall off the radar in interest/desire to maintain, we should consider replacing them in the circle with others who do care.
Redundancy, shared responsibility, and transparency are key to making sure AOI outlives any one person. Or at least lives until the last remaining person who cares about this place is no longer here to care.