Advanced opt-in RP module for VibeGuard admins

VibeGuard is first a Telegram group safety, moderation, AI recap, and community operations bot. Advanced RP is a separate, high-risk opt-in module for groups that intentionally choose that style of social interaction.

Do not enable it as part of normal onboarding. Do not enable it just because relationship modules, pairings, valentines, or other social tools are active. RP access is a separate decision.

A safe default is simple: leave it off unless the group owner has reviewed the setting, understands the audience, and accepts responsibility for the group culture.

The advanced RP module detects configured role-play trigger phrases inside Telegram group messages. When a trigger is valid, VibeGuard resolves the target member, applies cooldown and privilege rules, and returns a randomized outcome message.

Target resolution should prefer a replied-to message. If there is no reply target, the module can fall back to supported user references such as username, text mention, or known local member lookup.

The module should reject invalid targets where required, including self-targeting or bot-targeting cases. This helps reduce accidental activation and low-quality spam.

Admins control whether the module is available in the group. The feature should stay hidden or blocked when disabled.

Admin-facing controls should cover:

• Feature flag status
• Access requirements
• Age or access gate behavior where applicable
• Cooldown rules
• Privileged bypass behavior
• Voice artifact availability
• Visibility in Mini App or command surfaces
• Disable or reset options

Keep the setup conservative. Start with the narrowest access scope, then expand only if the group genuinely wants it.

Regular users can be subject to cooldowns so the module does not flood the chat. Admins or privileged ranks may have different cooldown behavior where the group allows it.

Some configured action categories may always succeed, while others may have randomized outcomes such as success, critical success, or failure. These mechanics should be explained at a high level, not turned into a public catalog of explicit prompts.

The module can attach configured voice artifacts where enabled. Voice assets may be stored locally or backed by external storage depending on the deployment. Admins should treat voice artifacts as sensitive external content and understand deletion or lifecycle expectations.

The explicit trigger catalog should not be duplicated in broad public docs. It belongs in controlled configuration or gated admin reference material.

Logs should avoid unnecessary explicit content. Store only what is needed for operations, abuse review, and support. If a group requests deletion of group-owned data, RP-related group records and external artifacts should follow the same authorized deletion principles as other VibeGuard group data where applicable.

This module should never weaken moderation. If a safety rule blocks policy-violating behavior after admins enable that rule, safety still wins.

Admins should review the RP module regularly if it is enabled.

Disable it if members are confused, if the group’s audience changes, if moderators cannot review misuse, or if the feature starts creating spam, pressure, or conflict.

For most public groups, marketplaces, job boards, crypto/Web3 communities, and support communities, the right setting is off. VibeGuard’s core value remains safety, moderation, AI recaps, Security Center, and community tools that work for a broader audience.

Expected result:

After reviewing this page, admins should understand:

The module is disabled by default. Group-level opt-in is required. Access controls and age/access gates matter. Cooldowns help reduce spam. Explicit trigger catalogs should not be published here. Logs should avoid unnecessary explicit content. Admins can keep the module off without affecting core VibeGuard features.

Troubleshooting:

Problem: RP triggers do not work in the group. Fix: Check whether the RP feature flag is enabled, whether the user has the required access, and whether the trigger matches the configured patterns.

Problem: A member triggered RP accidentally. Fix: Tighten trigger patterns, increase access requirements, add cooldowns, or disable the module.

Problem: RP messages are creating spam. Fix: Increase cooldowns, restrict the module to trusted members, or turn the feature off.

Problem: A voice artifact should not be available. Fix: Disable voice artifact delivery for the module and review external artifact lifecycle settings.

Problem: The module appears in a group where it should not. Fix: Check feature flags, Mini App visibility, command routing, and group-level settings. Disabled features should stay hidden or blocked.