Summary

  • The Wikimedia Foundation Board’s approval of the 2026–27 annual plan and budget is a real institutional authorization with a fiscal period, reserve boundary and management escalation condition.
  • That authorization is not a page revision, a local consensus, a factual finding or a completed operational outcome; those claims require their own project-level evidence.
  • A two-clock receipt can make the connection between institutional work and editorial consequences visible without pretending that either layer governs by implication.

The fiscal clock records a real institutional act

The Wikimedia Foundation’s Board is not a ceremonial audience. Its Bylaws place the Foundation’s corporate powers and the management of its business and affairs under Board authority or direction, while allowing written delegation. The same instrument describes reserved Board powers over the Foundation’s regulations, policies, user agreements and other decisions necessary for continued functioning. Wikimedia Foundation Bylaws That is an institutional authority with legal and organizational consequences. Treating it as empty because Wikimedia projects depend on volunteers would erase an important control surface.

The Board’s 17 June 2026 resolution approving the 2026–27 annual plan and budget provides a useful example of what that surface can say clearly. It approves $230.0 million in revenue, $240.0 million in expenses and up to $10 million of reserve-funded expenses; it also states a twelve-to-eighteen-month working-capital reserve target. If management expects the fiscal-year change in net assets to differ from plan by more than five percent, the resolution directs consultation with the Chair of the Audit Committee. 2026–27 plan-and-budget resolution

Those facts are not minor. They specify a financial period, a defined authorization, a reserve boundary and one condition for escalation. A reader can ask whether the resolution was adopted, what it authorized, who was expected to act, and whether the stated financial condition arose. This is the fiscal clock: a bounded sequence of institutional decisions and reports.

But clarity about an institution’s budget is not clarity about the content of a page. The resolution does not name a page, select a source, weigh a claim, record a community discussion, accept a revision, resolve a content dispute or certify a reader-facing outcome. The proper conclusion is not that the Board’s resolution lacks force. It is that its force is of the kind the document records: authorization and oversight for Foundation work. A page-level editorial conclusion is a different claim and needs a different record.

Corporate oversight and editorial work are related, not interchangeable

The Board Handbook makes the distinction more precise. It describes the Board’s role as oversight rather than day-to-day management, and identifies decision-making, monitoring and leadership as Board functions. Board Handbook The Bylaws in turn describe the CEO as having charge of the Foundation’s business and affairs under Board direction and as carrying resolutions and directives into effect unless responsibility is otherwise assigned. Wikimedia Foundation Bylaws

That chain has real operational implications. A budget may fund staff, infrastructure, legal work, product development or support for communities. A policy may create an organizational obligation. A software change may later affect a project workflow. Yet none of those intermediate facts tells a reader what happened to a particular page. Between a fiscal authorization and a page result lie separate choices: scope, delegation, design, implementation, consultation where applicable, local practice, evidence evaluation, revision and review.

The May 2023 Movement Charter page is useful precisely when its status is read carefully. It is a published drafting-era version, not proof of a presently adopted constitutional allocation. It describes project communities as having substantial policy autonomy within their contexts and universal behavioral rules, and says communities are responsible for content policies, maintenance, workflows and editorial control. It also contains drafting notes and open questions. Movement Charter — May 2023 version The page can therefore show how one published governance proposal described community authority; it cannot settle the present authority of every community or override a binding Foundation action by assertion.

The same discipline applies to the community’s account of consensus. Meta-Wiki’s consensus page presents consensus as a collaborative practice while cautioning that it should not trump neutral-point-of-view requirements or other official policy. Meta-Wiki: Consensus It is useful evidence about a community practice and its stated limit. It is not a universal voting formula, corporate law or a receipt that a particular page has been correctly decided.

The error in public descriptions often runs both ways. One version treats a Board budget as if it directly settles content, flattening corporate stewardship, management execution and editorial judgment into one authority. The other treats a community process as if it makes financial, legal and infrastructure responsibilities disappear. Neither account preserves the different losses carried at each layer. The Board must govern the institution it is responsible for. Project contributors must evaluate and maintain the content under their project’s rules. A responsible description names both surfaces without borrowing a conclusion from either.

A two-clock receipt keeps causation honest

The practical remedy is not a theory that every page must be governed from the Boardroom, nor a theory that institutional actions cannot affect editorial work. It is a small two-clock receipt whenever someone claims a connection.

The fiscal side should identify the resolution or delegated decision, date, fiscal period, purpose, authorized amount or resource boundary, accountable institutional owner, stated trigger and later reported status. The editorial side should identify the relevant project, page or workflow only when genuinely in scope; the applicable policy; the evidence and discussion record; the revision or decision; the relevant local or global review mechanism; and any remaining uncertainty. A connector may then state what is known: for example, that an authorized activity was intended to support a workflow, or that a later implementation affected one.

It must not skip from a budget line to a claim that a page was settled correctly.

This is an editorial recommendation, not a Wikimedia Foundation requirement. Its purpose is to make the missing handoffs visible. A plan can be approved without a later initiative being delivered as originally imagined. A technical initiative can be delivered without settling a page-level debate. A community decision can be real without proving that it exhausted every institutional or legal constraint. A final page revision can be visible without revealing why an unrelated budget variance occurred.

Lu Heng’s distinction between a coordination record and the result it is asked to represent is useful here. A formal authorization may be necessary evidence for action, but it does not become proof of the running result merely by being official. Running-Code Primacy Likewise, affected participation and institutional authorization should not be silently merged. The Multi-Stakeholder Mirage The two-clock receipt leaves each actor’s claim no broader than the record that actor controls.

What this record does not prove

The cited sources do not establish the correctness, neutrality, consensus, safety or legality of any page; they do not identify an editor, Trustee, employee, community, local policy conflict, software change or intervention. They do not show that the 2026–27 plan caused any particular editorial outcome, nor that a project-community statement overrides a binding Foundation responsibility. The Movement Charter page is not used as proof of an adopted constitutional settlement. The two-clock receipt is Daniel Kade’s editorial proposal, not Wikimedia Foundation policy.

Sources