Start hereOverviewPrerequisitesInstallationBootstrapAdministrationUsage & commands

Bootstrap

Taking a freshly-installed instance to a working org. Do this once, in order. By the end you'll have a logged-in identity, the managed role/channel set in Discord, two Stewards, and every other Discord admin removed.

Step 1 — First login (acceptance gate)

Open /auth/login and sign in with Discord. A successful login resolves you as a member. If it doesn't, check that DISCORD_OAUTH_REDIRECT_URI matches the registered redirect, and that you're a member of the configured guild.

Step 2 — Provision the managed role set

Reconcile the org's roles into Discord idempotently from the seeded structure — from the panel, or headless:

/provision sync · statusCreate/rename managed roles to match the org model; show drift.structure.manage

Re-running is safe: existing roles match by key and are left alone; renames re-apply; removed items soft-archive. If a role is missing, check the bot's role position and permissions, then re-run — it converges.

Channels. The structural channel tree is applied via the templates feature (see Administration). Starting from a bare guild, apply a template now to create the channel tree; it reconciles the same way roles do.

Step 3 — Set the org identity

Name, short name, mantra and colours are config rows seeded with placeholders. Set the non-governed ones directly:

/identity set · showEdit branding (short name, mantra, colours) and view current identity.config.write
The org name is special. Once governance is active, identity.name changes only by a vote: /identity propose-name. During initial bootstrap a Steward may set it directly; after that, treat the name as governed.

Step 4 — Steward setup & admin lockdown

The security-critical step. Stewards are the only platform administrators, and should be the only holders of Discord admin.

  1. Grant Steward to your two founders — on both the platform and Discord. Two, not one, so you always have a second key holder.
  2. Remove every other Discord administrator. Audit Server Settings → Roles for the Administrator permission and individual overrides; strip admin from everyone except the Stewards and the bot.
  3. Confirm and document who the Stewards are and when the lockdown was done.
Why: the safety model assumes destructive actions are mediated through governance. A stray Discord admin can bypass that by editing roles/channels directly. Locking admin to Stewards is what makes the "everything consequential is mediated" rule real.

Step 5 — Seed the operating rules

Review governance/economy defaults against your charter before members arrive:

/config list · setView/edit tithe %, quorum %, probation days, treasury threshold, council size. Audited.config.write

Next: Administration.