Who can do what
The ladder the code enforces — tools are ranked, gates run on every call, and the manifest a member's AI sees is not the manifest staff see.
Member
- Ask the AI questions (read-only knowledge search + summaries)
- Open tickets
- Vote in polls and suggestions
- Level up by chatting
Support
- Everything members can
- View tickets and take them
- Use staff AI read tools
- Propose server plans via staff AI (confirm-gated)
Moderator
- Everything support can
- Warn, timeout, kick
- Manage cases and notes
- Analytics tiles
Admin
- Everything moderators can
- Ban/unban, purge, lockdown tools
- Server configuration and modules
- Budget transparency
- AI plan management
- Staff digests
Owner / Co-owner
- Everything admins can
- Panic and antinuke controls
- Guild settings ownership
Discord permissions come first
The rank ladder decides which tools appear; Discord permissions decide whether a tool succeeds. The bot checks both — a moderator cannot use a tool that needs a Discord permission they lack, and the AI never acts above the asker's own reach.
Confirmations are rank-scoped
A staged proposal is owned by the staff member who armed it. Confirming requires the same rank that would run the equivalent slash command.
Members get read-only AI
Member-mode AI has no operational tools at all: knowledge search over public, staff-curated entries and channel topics the member can already see. The manifest of tools is generated per rank, per request.