GUILDKEEPER

Keep the doorway resilient

Cloud edge, local Anchor, and federation continuity in one Guildkeeper surface.

GuildkeepingCerbanimoResilience & continuity

Guildkeeper

Civweave

GUILD SETUP

This Guild's cloud doorway is live. Now make it resilient.

This page belongs to the Guildkeeper, not ordinary Civweave visitors. It records this browser as a Guildkeeper browser and keeps the local Anchor recommendation visible without blocking the campus.

Guild hostloading…

Roleloading…

Local Anchorchecking…

Set up local Anchor Open Civweave Open installer / updater

Reading this Guild's deployment metadata…

CONNECT GUILDKEEPER PAYOUTS

Add your Stripe information.

Every Guildkeeper should connect the Stripe account that will receive this Guild's share of membership and commerce revenue. This is separate from any card or membership you use as a Civweave member.

AccountStripe connected payout account

ReadinessTransfers must be active

PrivacyDetails stay with Stripe

Connect from the local Anchor's operator console. Civweave receives only the connected-account identifier and capability status; bank, identity, and tax details are entered in Stripe-hosted onboarding.

Connect or manage Stripe payouts

Start the local Anchor, open its operator controls, then choose Connect payouts. Guildkeeper earnings remain unavailable until Stripe reports transfer capability as active.

PLACE THIS GUILD ON THE MESH · REQUIRED

Stand where the Guild lives to finish setup.

Every Guild needs a Guild Map location during setup. Take this device to the physical place this Guild serves, then sync. Civweave asks for location only after you tap the button.

PermissionAsked on tap

Public precisionRounded · about 100 m or wider

Mesh nodeswaiting for deployment…

Publish a precise public Guild pinOptional. Use this for public venues or sites people should be able to walk directly to. The fresh coordinate and its measured accuracy become public Guild metadata and can appear on the Guild Map.

Rounded placement is the default: the exact reading stays on this device and only an approximately 100 m site position leaves it. If you explicitly enable the precise public pin above, Civweave sends the fresh coordinate at six decimal places together with the device's measured accuracy. The first successful sync pairs this Guildkeeper browser for future location updates, including updates made directly from the Guild Map.

Open Guild Map

Waiting for the account Worker and starter nodes…

CLOUDFLARE DEPLOYMENT

Cloud-backed Guild: Worker + three starter nodes

This layer exists only when a Guildkeeper provisions Cloudflare for this Guild. Wrangler creates it in the Cloudflare account authenticated for this Guild. Pocket-only mobile Guilds create no Worker and never consume another Guild's Worker or Durable Object capacity.

Account Workerchecking…

Starter Achecking…

Starter Bchecking…

Starter Cchecking…

Reading account-edge deployment status…

Cloudflare token settings and retry

Token permission: Account → Workers Scripts → Edit.
Account resources: include the Cloudflare account that owns this Guild.
GitHub Actions: replace CLOUDFLARE_API_TOKEN, then rerun the Guild deployment workflow.
Local setup: rerun the command shown below after updating the token.

node scripts/provision-cloudflare-account-edge-v1.mjs --host-id <host-id> --strict

Durable Objects are covered by Workers Scripts permission; Cloudflare does not present a separate Durable Objects permission row.

WHY THE ANCHOR MATTERS

The Cloudflare Guild host remains usable without a local Anchor. A local companion is strongly recommended because it can retain Guild identity and state for recovery, local-first services, and federation work even when the public edge is unavailable.