Governance

Who holds power on the network, and why no one can keep it against the community.

Academy Network has editors and verifiers, but they are not owners. The community is the root of authority, and every power handed to anyone is checkable, bounded, and recallable. That is what lets the network run forever: no person, key, company, or founder is load-bearing, and nothing can be held hostage.

The one rule everything serves: the community can see what everyone with power does, can undo it, and can replace the people who hold it, without anyone's permission. Editors carry out the community's decisions; they do not get to overrule them.

Who holds what

Power sits where the work happens, and every layer answers to the community underneath it.

Who holds power, and what checks it
Role	What they do	What checks them
The community (everyone)	Reads, writes, reviews, and votes, weighted by earned standing	Nothing. It is the root of authority.
Verifiers	Review submissions and vote to publish, as a randomly drawn jury	Certified by peers, not appointed; recallable by community vote; cannot be overruled by editors
Editors	Curate the official index and rotate their own keys	Bound on every side by rules every node checks; replaceable by a no-confidence vote
The duke	Sets a guide's title and its one donate button	Owns properties only, never the content; reassignable for abuse

Standing: earned weight, not head count

Anyone can create an unlimited number of identities, so plain one-person-one-vote would be trivial to fake. Instead, every community vote is weighted by standing: credit you earn by actually contributing, by writing guides that get published and by reviewing other people's work. A brand-new identity has zero standing, so spinning up a thousand empty accounts buys exactly nothing. Standing cannot be bought, transferred, or handed out, and every node computes the same number from the public record, so any vote can be rechecked by anyone.

Verifiers are earned, not appointed

Editors do not choose who reviews content, because that would be indirect control over every outcome. Instead you become a verifier by demonstrating competence to the people already trusted in your subject: current verifiers certify you, and once enough of them have (three, to start), the editors must seat you. A verifier who reviews in bad faith can be removed by a community recall vote. The jury decides what gets published; editors cannot overrule it.

Community petitions

The community governs through one simple, public tool: a signed petition that everyone votes on, weighted by standing. The same mechanism that takes down a bad guide also removes forum boards and threads and standalone uploads, freezes or features a board, and governs the people and the rules.

What a petition can do
Petition	What it does
Remove content	Delists any published content, a guide, a forum board and every thread in it, a single thread, or a standalone upload, and purges it from every compliant node
Lock or feature	Freezes new posts on a busy board or thread, or floats a board to the top of the list. A reversible community decision, not a deletion.
Recall verifier	Strips a verifier who is reviewing in bad faith
Restore	Reverses an editor's revocation of approved content, an appeal against censorship
Change a setting	Forces a parameter, within safe limits, that the community wants changed
No confidence	Replaces the editors entirely (see below)

Every petition and every vote stays on the network permanently, so the whole governance history is public and auditable forever. Nothing happens in a back room, because there is no back room.

Editors are bound

Editors keep the official index tidy, but the protocol fences them in. Every node independently checks that editors do not:

publish a submission the jury rejected, or drop one the jury passed;
leave out a verifier the community certified, or keep one it recalled;
revoke approved content without a real, cited reason;
set the rules (thresholds, quorums, difficulty) outside safe bounds;
ignore a petition the community passed.

A manifest that breaks any of these is simply rejected by every client. Editors carry out the community's decisions; they cannot quietly override them.

Replacing the editors

Here is the ultimate check. If the editors are captured, compromised, absent, or just doing a bad job, the community can hold a no-confidence vote. It names a replacement set of editors, and if it passes (the highest bar on the network), every client follows the new editors instead. The old editors cannot block it, because clients verify the community's mandate for themselves rather than asking the incumbents' permission. There is no permanent ruling class, and the network can never die with its editors or be held hostage by them.

Why it lasts forever

The four guarantees
Guarantee	What it means
No capture	Seizing the editor keys still cannot censor passed content, stack the verifier roster, or block removals, and the community votes the captors out
No hostages	A no-confidence vote seats new editors with zero cooperation from the old ones
No Sybil rule	"The community" means earned standing, so consensus cannot be faked with throwaway accounts
No lock-in	The whole library is openly licensed, exportable to plain files in one click, and rebuildable from the public spec, so even total governance failure cannot destroy the knowledge or stop a clean fork

Founders start the network and seat the first verifiers, then hand authority to the community and step away. From that point on, Academy Network belongs to the people who use it, and there is no single point where anyone can take it back.