Chapter 1 — Mainframe Initial Integration
This chapter covers the very first moments after you decide to deploy Oris into your Discord guild. Every step below is mandatory: skipping the role-hierarchy step is the single most common cause of downstream permission failures.
1.1 Invite Oris via the Support Server
Public direct invites are gated by design. To deploy Oris to your server, first join the official operations hub at discord.gg/qeC24y3ApM, open the #deploy channel, and follow the pinned invitation flow. An operator will approve the deployment token and issue you an authorized invite link. This human handoff exists to protect newly onboarded servers from raid-injection during setup.
1.2 Establish Role Hierarchy
Once Oris is in your server, open Server Settings → Roles and drag the “Oris” role to the very top of the role stack. This is non-negotiable: Discord enforces strict hierarchy rules, and Oris cannot moderate, ban, kick, or manage users whose highest role sits above its own. If the Oris role sits below your moderators, anti-nuke enforcement against a compromised moderator account will silently fail.
1.3 Grant Baseline Permissions
Oris ships with a suggested permission mask. If you invited via the standard token, this mask is applied automatically. If you customized the invite, ensure the Oris role has: Administrator, or at minimum Manage Server, Manage Channels, Manage Roles, Kick Members, Ban Members, Manage Messages, Manage Webhooks, Read Message History, and Send Messages in every operational channel.
1.4 Verify Boot Signal
Run ,ping in any channel Oris can see. A successful boot returns API latency, WebSocket latency, and the current cluster identifier. If no response appears within 3 seconds, re-check the role hierarchy step above before opening a ticket.
,ping → API: 42ms WS: 89ms Cluster: eu-west-2a Uptime: 12d 04h 22m
1.5 Recommended First Commands
Run these once to confirm the mainframe is healthy end-to-end: ,serverinfo, ,security-status, ,pstatus.