Knowledge Base.

The Singularity Core is the proprietary sharding engine that powers the Nexus Protocol. It allows the bot to scale across hundreds of thousands of servers by distributing the neural load across multiple high-performance worker thread processes, ensuring fault isolation between shards.

All economic transactions are executed via a transaction-safe logic layer and persisted in a distributed MongoDB cluster. This ensures that assets are never lost due to shard reconnections or node failures. Balances use Number precision with compound indexing for fast reads.

Nexus is designed for the modern Discord interface and exclusively utilizes Slash Commands (/) for all interactions. Traditional prefixes are deprecated to ensure the highest fidelity interaction with Discord's native UI.

Members earn XP for each message sent (with a cooldown to prevent spam farming). As XP accumulates, operatives level up with announcements sent to the configured channel. Leveling can be toggled on/off per guild via the /config command. View your progress with /profile.

The reputation system allows operatives to endorse each other using /rep @user. Each operative can give one rep point per 24-hour cycle. Reputation is displayed on your /profile card and serves as a trust indicator within the community.

Users can create support tickets with /ticket [reason]. This generates a private channel visible only to the user and staff. Staff can close tickets with the built-in button, and a transcript of the conversation is generated. No additional setup required — it works out of the box.

Neural Latency refers to the round-trip time between a command interaction and the engine's response. We maintain an average latency of <15ms through our localized cluster architecture and optimized event handling pipeline.

Use the /automod command to configure anti-spam, anti-link, and word filtering rules for your server. Settings are stored per-guild and persist across bot restarts via the GuildConfig model. Admins can toggle individual features on/off as needed.

Founder status is an immutable node ID hardcoded into the framework's environment configuration. It cannot be granted via commands; it must be defined at the infrastructure level using the OWNER_IDS environment variable during deployment.

Use /config welcome-channel #channel to designate where welcome messages are sent. When a new member joins, Nexus sends an embed greeting. You can also configure auto-role assignment with /config auto-role @role to automatically assign a role on join.

Use /giveaway <prize> <duration> [winners] to start a giveaway. Users enter by clicking the reaction button. When the timer expires, winners are randomly selected and announced. Duration supports formats like 1h, 30m, 1d.

All bugs should be reported through the 🐛-bug-report sector in the official support server, or by opening a GitHub issue on the repository. Please include the error ID if one was provided, as this helps us trace the exact failure point.

Currently, the neural economy is node-specific (per server). However, Phase 5 of our roadmap includes the introduction of the Global Singularity, which will enable cross-node asset transfers and a unified leaderboard.

Neural Agents are external bots (like Carl-bot or Ticket Tool) that collaborate with Nexus to provide a complete server orchestration experience as defined in our server.md blueprint guide.

Yes! The Nexus Protocol is fully open source under the MIT License. You can view, fork, and contribute to the codebase on our GitHub repository. We welcome community contributions and feature requests.