Coordination under the Living Book

Federation

How Nodes of the Guild coordinate without becoming a hierarchy.

“Guild Node – A decentralized local unit of the Guild’s mission, formed wherever compassion meets actionable stewardship.” — Living Book, Definitions

One Guild, many Nodes

Nodes are active groupings of Representatives coordinating in a shared place, time or context. They provide collaboration and mutual support, without independent budgets, accounts or ownership by default. This page does not assign people to Nodes or establish geographic boundaries.

What Nodes share

One Book

All Nodes operate under the Living Book. Amendments require full consensus of active Representatives and Guardians; the Book also specifies the Guildmaster’s lifetime edit and amendment-veto powers.

Treasury and the protected Vault

Guild Overhead, Betterment Fund and Compensation Costs are Treasury channels. The Perpetuity Vault is separate from Treasury, with principal protected and surplus yield governed by the Book.

One identity

All activity remains aligned with the Guild’s Mission and Core Values, which the Book makes unamendable. The motto expresses that shared commitment; this page does not declare a new absolute clause.

One Transparency Hub

The Transparency Hub publishes Guild records. Public availability must respect the Book’s privacy and consent requirements; this summary does not promise a per-Node reporting feature.

Coordination and local practice

Floor Registry. Representatives curate resources relevant to the communities they serve; a map is not a rule assigning Node membership.
Culture Circles. Voluntary spaces for shared understanding and participation.
Collaborative Actions. Shared work follows the Book’s consent, coordination and accountability provisions.
Rep Capacity. Capacity belongs to the actual people doing the work. Technical tags do not appoint them to a Node or create authority.
Local Agreements. Local practice must remain consistent with the Living Book.

How Nodes form

Node Recognition & Attestation describes two formation paths. Both require consensus among at least three existing Node Guardians, or the Guildmaster during formation phase. Consensus Across Scales also governs recognition decisions; this page does not replace either provision.

Bottom-up: a group of Representatives submits a written declaration identifying its community, proposed initial Representatives, and commitment to Core Values.
Top-down: the Guildmaster or regional Guardians may identify need and willing participants, documenting the same elements. Multiple recognized Nodes may serve the same area while honoring Guild values.

Cross-Node disputes

Credible concerns about a Node’s alignment trigger the Book’s inter-Node Arbitration Council of Guardians from at least three uninvolved Nodes. The Council distinguishes individual misconduct from systemic Node failure. Probation or de-recognition follows the specified Guild-wide process, with the Book’s appeal and care-continuity protections. Ordinary individual reports follow the separate Termination Policy and its Council and fallback provisions.

Records and remaining preparation

Consult the governance page for recorded Nodes and outcomes. A database entry does not itself recognize a Node. Detailed coordination procedures and assignments must follow the Book; internal protocol drafts are proposals and do not establish additional authority.