Discord Intent Review Evidence
This page provides public evidence for the Discord Privileged Gateway Intent review of the twin3 bot. The bot operates identity, role-gating, onboarding, contribution scoring, and community safety workflows inside the official twin3 Discord server.
twin3 bot
Application ID: 1475402255254687916
Server Members Intent and Message Content Intent.
Presence Intent is not required for current production workflows.
Developer Portal Configuration
Application URLs and installation state
https://invite.twin3.ai/discord/interactions
1. Proof-of-Contribution Reports
Experiencer XP, level, rank, and signal breakdown
The twin3 bot and related scoring service calculate Experiencer contribution reports from Discord reactions, retention activity, meaningful conversation, verified Twin Matrix completion, and other role-specific signals.
- Message Content is needed to evaluate meaningful public conversation and classify low-signal or abusive content.
- Server Members is needed to connect the report to the correct guild member, role state, joined date, and verified identity state.
- The output is shown as XP, level, rank, and per-signal scores for each member.
2. Builder Report Forum
Forum-based report classification
Builder contribution is based on reports submitted in Discord forums and channels. Reports may include bug reports, UX issues, feature suggestions, reproduction details, and technical support evidence.
- Message Content is needed to classify report type, severity, usefulness, duplication, and whether the post contains enough actionable detail.
- Server Members is needed to attribute reports to guild members and grant Builder access only after XP thresholds are met.
- This workflow supports community quality, not advertising, resale, or third-party profiling.
3. Member Role Gating
Human, Experiencer, Builder, and contribution roles
The twin3 bot grants and reconciles roles that control access to Proof-of-Concept participation and role-specific labs. Experiencer access is gated by Twin Matrix SBT ownership. Builder access is based on XP thresholds from accepted contribution reports.
- Server Members is required to read role state, join events, joined date, guild member identity, and to keep roles synchronized.
- Without this intent, the bot cannot reliably grant or reconcile Human, Experiencer, Builder, Creator, and other contribution roles.
4. Humanity and SBT Verification
twin3.ai humanity verification
Members verify humanity on twin3.ai, connect supported identity providers, and bind Discord to a verified identity. The Discord bot then grants the correct Discord roles based on verification and SBT state.
- Human role: member completed Discord-linked humanity verification.
- Experiencer role: member has a verified Discord identity and a Twin Matrix SBT.
- Contribution roles: member qualifies through role-specific XP and activity rules.
Form Answer Reference
Why Server Members Intent is required
twin3 bot uses Server Members Intent to manage community identity and contribution roles inside the official twin3 Discord server. The bot needs access to member join events, member roles, joined_at, and member profile data to grant and reconcile Human, Experiencer, Builder, Creator, and other contribution roles. Experiencer access is gated by Twin Matrix SBT ownership, and Builder access is based on contribution XP thresholds. The bot also uses member events for invite attribution, onboarding state, anti-abuse checks, and role synchronization. Without Server Members access, these role-gating and reconciliation features cannot function reliably.
Why Message Content Intent is required
twin3 bot uses Message Content Intent to evaluate public contribution activity inside official twin3 channels and forums. Message content is required to classify Builder reports, score meaningful conversation for Experiencer XP, identify low-signal or abusive behavior, support moderation, and distinguish helpful contributions from spam or duplicate reports. Without Message Content access, the contribution XP, role ranking, forum report classification, and community safety workflows cannot function reliably.
Data handling summary
- twin3 stores Discord IDs, role state, contribution signals, and audit metadata needed to operate identity and Proof-of-Contribution workflows.
- Public message content may be processed for contribution scoring, report classification, support, and safety workflows.
- Message content is not sold, shared with advertisers, or used to train third-party foundation models.
- Privacy Policy: https://twin3.ai/privacy/
- Terms of Service: https://twin3.ai/terms
- Linked Role Verification: https://twin3.ai/humanity/