The Cohost Directives

Notation: L = Line (used for rule/reference numbering)

Preamble

We, the staff and cohosts of the Ballroom, establish these directives to maintain a safe, fun, and flowing environment. All cohosts, moderators, and management members are bound by these rules, laws, and procedures to ensure accountability, fairness, and continuity.

This document serves as a complete training and reference guide — covering standard operations, edge-case procedures, escalation paths, multi-pin management, last-page behavior, guest interactions, and staff responsibilities. Rules are identified by line number (L) for easy lookup and citation.

Article I — Purpose

Section 1.1: Onboard and train new cohosts with complete examples and operational flows.

Section 1.2: Serve as a searchable, indexed reference for all staff operations, community culture, common failure points, and best practices.

Article II — Ballroom Room Rules (Public Law)

These are the core room rules that apply to all guests, regulars, and staff inside the Ballroom.

### Participation & Camera

L2.1: All participants must remain on camera at all times.

L2.2: Owners are expected to remain on camera approximately 75% or more of the time.

L2.3: Cameras that are dark, frozen, sleeping, or inactive may be sent to the waiting room.

L2.4: Cohosts have authority to waitroom any camera they determine is non-compliant or potentially disruptive.

L2.5: Cohosts may also waitroom cameras they believe could be involved in spam, scams, bot activity, or chaos creation.

### Names & Chat Conduct

L2.6: No cashtags, payment handles, or promotional text may appear in names or chat.

L2.7: No links or personal contact information may be shared in the public chat.

L2.8: Display names must remain non-disruptive and readable.

### Conduct

L2.9: All guest behavior is subject to correction at any time. Cohosts may address, redirect, warn, or act on any guest's conduct — including but not limited to bullying, harassment, or targeted behavior toward others.

L2.10: No politics or world news discussions in the room.

L2.11: No posturing, fixation, or repeated unwanted attention directed toward another guest.

L2.12: If someone expresses disinterest, continued attempts at interaction may be treated as harassment.

L2.13: Adults only. Guests are expected to act accordingly.

### Moderation

L2.14: Cohosts may delete negative or disruptive chat messages before escalation occurs.

L2.15: Warnings and counseling must always occur privately, never publicly.

L2.16: Cohosts may remove or waitroom disruptive participants when necessary to protect the room.

L2.17 (Owner Exemption): Owners are exempt from all cohost rules and may act at full discretion.

L2.18 (Suspicious Content Rule): If a message looks out of place, unnatural, or suspicious — delete it immediately.

L2.19 (Auto-Delete Rule): Always delete messages from flagged or known disruptive users (e.g., Celestians, Outcasts).

L2.20 (Length & Quality Filter): Messages that are 4 sentences or longer and are not engaging, sexy, funny, or casual small talk should be deleted.

L2.21 (Rudeness Filter): Delete rude, unnecessary, or tension-creating comments immediately — before escalation occurs.

L2.22 (Default Action Rule): If unsure whether a message belongs, delete first and assess later.

Article III — Chapters of the Constitution

Chapter 1 — Lights, Camera, Satisfaction

Understanding Camera Visibility

L1.1 (Room Law): Everyone must be on camera at all times — except owners, who should be on camera 75%+ of the time.

L1.2 (Mini Flow): Verify camera → Check activity → Warn privately → Waitroom if inactive → Document.

L1.3 (Evidence Path): Screenshots, timestamped logs, participant tiles.

L1.4 (What We Cannot Control): Guest hardware failures, network issues, personal choices.

L1.5 (Common Tricks / Failure Modes): Virtual backgrounds used to obscure presence, intentional cam toggling, misaligned angles.

L1.6 (Additional Guidance): Guests experiencing lag should try connecting via VPN set to Japan, Sweden, or Canada.

L1.7 (Guest Responsibility): Guests are responsible for their own camera functionality. Staff may assist once, via private chat.

Chapter 2 — Hand Raises, Multi-Pin, and Last Page

Hand Raises, Multi-Pin Assignment, and Tile Behavior

L2.1: Multi-pin is a staff-controlled tool. Guests may signal their interest but cannot control it directly.

L2.2 (Mini Flow): Observe signal → Confirm intention → Assign multi-pin → Track activity.

L2.3: Guests without an "Allow to multi-pin" option visible are on mobile devices and cannot multi-pin.

L2.4: If the multi-pin bot fails, cohosts handle requests manually and escalate to Star Chat and @owners.

L2.5 (Evidence): Participant list, multi-pin assignment logs.

L2.6: Cohosts may waitroom guests who repeatedly raise their hand in an annoying or disruptive manner.

L2.7: Cohosts may waitroom any camera perceived as non-compliant or suspected of spam/scam/chaos activity.

L2.8: When a guest turns their camera off and back on, their tile moves to the last page of the grid. Cohosts should observe placement but not escalate unless behavior becomes disruptive.

L2.9 (What We Cannot Control): Misused platform features, guests who ignore protocol.

L2.10 (Last Page Explained): When a guest toggles their camera off then on, Zoom moves their tile to the last page of everyone's grid. This is a platform behavior — monitor it but do not escalate unless it becomes a pattern of abuse.

Chapter 3 — Last Page of the Circuit

Off-Camera Breaks and Temporary Absence

L3.1: Camera must remain on at all times. Temporary off-camera is only permitted for genuine emergencies.

L3.2 (Mini Flow): Observe → Confirm reason → Allow if justified → Document.

L3.3 (Evidence): Zoom session timeline, camera toggle logs.

L3.4 (What We Cannot Control): Genuine emergencies or unexpected real-life interruptions.

Chapter 4 — Spam, Scam, and Chaos

Detecting and Removing Malicious Behavior

L4.1: Identify and remove bots, scammers, spammers, and individuals engaging in predatory behavior.

L4.2 (Mini Flow): Observe → Verify → Waitroom or remove → Log → Escalate if needed.

L4.3 (Evidence): Screenshots, chat logs, participant records.

L4.4 (What We Cannot Control): External spam origination, AI-generated messages sent before detection.

Chapter 5 — AI and Synthetic Accounts

Recognizing Bots and Impersonations

L5.1: Remove or waitroom any account suspected of being AI-generated, automated, or impersonating a real person.

L5.2 (Mini Flow): Observe anomaly → Confirm suspicion → Take action → Escalate if behavior persists.

L5.3 (Evidence): Chat logs, screenshots, audit history.

L5.4 (What We Cannot Control): AI-generated or automated content originating outside the room.

L5.5 (Ways to Spot a Bot): The following are red flags that a camera may be automated, fake, or bot-operated:

• Cropped camera — the frame is deliberately cut off, hiding the full image or background.
• Chaturbate logo visible in the cam frame — a direct indicator the feed is being streamed from another platform, not a live person.
• Not using multi-pin — real, engaged guests interact with the room; bots typically do not respond to or use multi-pin features.
• Not smoking — in a room where smoking is a core activity, a cam that never participates in it can be a tell.
• Looks too good to be true — overly polished, model-quality appearance with no natural movement or expression.
• Sends a link asking for money — immediate scam indicator. Delete the message and remove the account.
• Turns cam off and does not turn it back on — real guests return. A cam that goes dark and stays dark is likely a bot or bad actor.
• Multi-pin test — if still unsure and the guest has multi-pin, remove it and observe. If their screen visibly flashes or their face shows a clear reaction, they are likely real. No reaction may indicate a bot or pre-recorded feed.
• Messages appear without typing — if chat messages from the guest appear without any visible typing activity on their end, the messages may be automated or scripted.

L5.6: No single indicator is conclusive on its own. Use a combination of signals before taking action. When in doubt, waitroom first and assess.

Chapter 6 — Cohost Powers and Responsibilities

Cohost Abilities, Tools, and Limits

L6.1: All cohost powers must be used responsibly and within the bounds of escalation protocols.

L6.2 (Mini Flow): Observe → Use appropriate power → Log → Report if needed.

L6.3 (Evidence): Zoom action logs, participant feedback.

L6.4 (What We Cannot Control): Platform bugs, actions taken by other cohosts.

Chapter 7 — Smoking and Break Protocols

On-Camera Smoking and Personal Breaks

L7.1: Cameras must remain on at all times. Off-camera smoking is not permitted. If smoking occurs, it must be visible on camera and non-disruptive to the room.

L7.2 (Mini Flow): Observe behavior → Confirm compliance → Allow if appropriate → Intervene only if disruptive.

L7.3 (Evidence): Session logs, timeline.

L7.4: Personal habits that disrupt the room environment are subject to correction. Cohosts have full authority to address, redirect, or remove any guest whose behavior — including smoking habits — negatively impacts the room.

L7.5 (G Culture): Members also dose G together on the last page — it is a normal part of the room's social culture. Standard guidance: 1 to 1.5 hours between doses, no more than 3ml at a time. Timers are strongly encouraged to keep track. Gheers = Cheers with G. Cohosts should be aware of this culture and treat it as they would smoking — it belongs in the room, on camera, and as long as it is not disruptive, leave it alone.

Chapter 8 — Evidence and Documentation

Receipts or It Did Not Happen

L8.1: Collect evidence before or during moderation actions whenever possible.

L8.2 (Mini Flow): Observe → Capture evidence → Escalate or warn → Store securely.

L8.3 (Evidence Types): Screenshots, chat logs, session history.

L8.4 (What We Cannot Control): Technical failures, lost data, platform logging gaps.

Chapter 9 — Promotion and Staff Mentorship

Pathways to Higher Responsibility

L9.1: Promotions are earned through consistent performance and conduct — not seniority alone.

L9.2 (Mini Flow): Observe → Mentor → Encourage → Evaluate → Document progress.

L9.3 (Evidence): Staff logs, observation notes.

L9.4 (What We Cannot Control): Individual motivation and personal ambition.

Chapter 10 — Platform Limitations

Zoom Constraints and Technical Failures

L10.1: Guide guests through tech issues when possible, but do not hold up the room attempting to fix every individual's setup.

L10.2 (Mini Flow): Observe → Log → Adjust → Continue.

L10.3 (Evidence): System logs, timestamps.

L10.4 (What We Cannot Control): Software bugs, device limitations, network conditions.

Chapter 11 — Conversation Steering

Keeping the Flow Fun and Respectful

L11.1: Keep topics playful and safe. Avoid politics, world news, and technical troubleshooting in the main chat.

L11.2 (Mini Flow): Observe → Redirect naturally → Document if needed.

L11.3 (Evidence): Chat logs, screenshots.

L11.4 (What We Cannot Control): Guest attitudes, outside distractions, individual sensitivities.

Chapter 12 — The Waiting Room Doctrine

Security, Staging, and Containment

L12.1: The Waiting Room is a security feature and operational tool — not a default punishment.

L12.2 (Use Cases): Sleeper cams, off cams, dark cams, suspected spam or scam activity, disruptive behavior.

L12.3 (Mini Flow): Identify issue → Waitroom → Notify in Host Chat → Monitor → Decide: admit, hold, or remove.

L12.4 (Coordination): The cohost who waitrooms a guest must notify other cohosts in Host Chat so the situation is tracked and consistent.

L12.5: If a guest was placed in the waiting room by mistake, admit them immediately. Do not re-admit known or repeatedly removed trolls — repeated cycling increases disruption and rewards bad behavior.

L12.6 (Spam Attack Protocol): If the room is under a spam attack: mass waitroom → stabilize the room → selectively re-admit known good participants.

L12.7 (Evidence): Entry logs, chat logs, screenshots.

L12.8 (What We Cannot Control): Rejoins using new names or devices, external coordination between bad actors.

Chapter 13 — Chat Moderation Playbook

Preventing Escalation Before It Starts

L13.1: If a message is negative, singles someone out, or is a complaint — delete it immediately before it escalates.

L13.2: Always warn and counsel in private. Never correct guests publicly in the chat.

L13.3 (No Response is a Response): Repeated messaging to someone who is not replying (2–3 attempts) may constitute harassment.

L13.4 (Boundary Rule): If it is not a clear "yes," treat it as a no. Continued pursuit after someone expresses disinterest equals harassment.

L13.5 (Mini Flow): Detect problematic message → Delete → Private DM to the guest → Monitor → Escalate if repeated.

L13.6 (Examples):

• "What's wrong with your face?" → Delete immediately + send private warning.
• Repeatedly tagging a guest who is ignoring them → Warn → Waitroom if the behavior continues.

L13.7 (Tone Guidance): What sounds caring can read as hostile in text. Avoid any comments about facial expressions, appearance, or personal attributes.

L13.8 (Evidence): Chat logs, screenshots, timestamps.

L13.9 (What We Cannot Control): Misinterpretation of tone, private DMs between guests.

Chapter 14 — Last Page Constitution

Movement, Visibility, and Smoking Culture

L14.1: Turning a camera off then back on sends the user's tile to the last page of the grid for all other participants.

L14.2: Guests may navigate to the last page for visibility control or as part of the room's smoking culture. This is a soft-law behavior — permitted but not an absolute right.

L14.3 (Cohost Role): Observe patterns. Do not escalate unless the toggling becomes disruptive, attention-seeking spam.

L14.4 (Mini Flow): Detect toggle → Confirm pattern → Ignore OR warn if abused → Document.

L14.5 (Abuse Cases): Repeated toggling to farm attention, interrupt the room flow, or evade active moderation.

L14.6: On mobile, hand-raising may be attention-seeking only — mobile guests do not have multi-pin ability.

L14.7 (What We Cannot Control): Behavior differences across devices, Zoom's internal ordering logic.

Chapter 15 — Read the Room or Ruin It

Social Intelligence and Flow Control

L15.1 (Core Principle): Cohosts are not just moderators. They are tone setters.

L15.2: Do not over-moderate. If something is not disruptive, leave it alone.

L15.3: Intervene only when behavior:

• Disrupts the flow of the room
• Targets or singles out a guest
• Creates tension or confusion

L15.4 (Mini Flow): Observe → Assess the vibe → Ignore OR redirect → Escalate only if necessary.

L15.5 (Redirection Examples):

• Shift the topic → "Anyone else smoking?"
• Introduce a light topic → "Who's having a good night?"
• Pivot away from tension → Use humor or inclusive energy

L15.6: Not every problem needs enforcement. Some problems need diffusion.

L15.7 (Over-Moderation Rule): Excessive intervention can harm the room more than the original issue itself.

L15.8: Cohosts should aim to be present, not overpowering.

L15.9 (What We Cannot Control): Guest personalities, moods, and external stress they bring into the room.

Chapter 16 — Escalation Ladder

Enforcement Sequence and Authority (Hard Law)

L16.1 (Standard Escalation Flow):

1. Delete the offending message or content
2. Send a private warning to the guest
3. Move to the waiting room
4. Remove from the session
5. Ban — Owner discretion only

L16.2: Not all steps are required. Cohosts may skip levels based on the severity of the situation.

L16.3: Severe violations (active spam, scams, predatory behavior) warrant immediate removal — no warning required.

L16.4: Warnings must be private unless the escalation requires room-wide visibility.

L16.5: Repeated violations by the same guest should result in faster escalation each time.

L16.6 (Abuse Guardrail): Escalation powers must never be used emotionally, personally, or as retaliation.

L16.7 (Team Coordination): All major moderation actions should be communicated in Host Chat to maintain team awareness.

L16.8 (Evidence Requirement): If a moderation action is questioned, the cohost must be able to provide a basic justification or supporting receipts.

L16.9 (What We Cannot Control): Guests rejoining, alternate accounts, and coordination outside the room.

L16.10 (Post-Removal Documentation): Any time a guest is removed, the cohost who performed the removal must document the situation in Discord immediately. Include: who was removed, why, what led to it, and any relevant chat or behavior evidence.

L16.11 (Re-Entry Instructions): If a removed guest is eligible to return, direct them to re-enter via:
  • https://app.zoom.us/wc — Zoom web client, no app required.
  • 1132 workaround — use the 1132 method to re-enter the session if the standard link does not work.

L16.12 (Staff Removal Consequence): If a staff member is removed by another cohost, the cohost responsible is subject to an automatic timeout from co-hosting privileges — unless the removal was the result of an active spam attack, an accidental misclick, or another clearly documented extenuating circumstance.

L16.13 (Accountability Notice): Do not assume that removal actions go undetected. Session reports and time-stamped logs make it straightforward to identify exactly who removed whom and when. Every action is traceable. Act accordingly.

Chapter 17 — Cohost Identity and Authority

Team Conduct, Disputes, and Responsibility

L17.1 (Perception Rule): To a guest, a cohost is the host. Cohosts carry full responsibility for the room experience at all times.

L17.2 (Private Confrontation Rule): Cohosts must only confront or correct other cohosts in private — via DM or in the Host Chat. Public contradiction is prohibited.

L17.3 (Override Clarification): An "override" is any action that reverses or conflicts with another cohost's decision — such as re-admitting a removed guest or undoing a waitroom without coordination.

L17.4 (Override Protocol): Do not publicly override another cohost. If an override is necessary, coordinate in Host Chat first — or act and immediately document the override in Host Chat.

L17.5 (Unity Rule): In public view, cohosts always present as a unified team. All disagreements are resolved off-stage.

L17.6 (Authority Without Ego): Cohost powers exist for room stability — not personal preference, ego, or favoritism.

L17.7 (Disruption Standard): Any staff behavior that disrupts the peace and tranquility of the room is subject to corrective action.

L17.8 (Corrective Actions): Depending on severity:

• Private warning or counseling
• Suspension of cohost privileges
• Immediate demotion — at Owner discretion

L17.9 (Escalation for Staff Issues): If a cohost's behavior is ongoing or severe, escalate to Admins or Owners with supporting receipts.

L17.10 (Abuse Guardrail): No targeting, cliques, or coordinated staff action against a guest or fellow cohost.

L17.11 (What We Cannot Control): Personality differences, interpretation of tone, external relationships between staff members.

Chapter 18 — Topics and Energy Control

Steering Conversation Without Alienating Guests

L18.1 (Core Principle): Cohosts should actively steer conversation while keeping all guests feeling comfortable and included.

L18.2 (Vibe Protection Rule): If a topic kills the vibe, creates tension, or derails the room's flow — redirect immediately.

L18.3 (Topics to Avoid):

• Politics
• World news
• Hysteria-driven or doom-scroll discussions
• Technical troubleshooting in the main room

L18.4 (Topics to Advance):

• Smoking culture and relaxed social activity
• Attraction, hot guests, and light flirting
• Fun, engaging, and light-hearted topics
• Friendly conversation and genuine connection
• Community building and returning member recognition

L18.5 (Redirection Method): Do not shut people down harshly. Instead:

• Pivot the topic naturally
• Ask an inclusive question to the room
• Introduce lighter, warmer energy

L18.6 (Examples):

• "Let's not go there" → Avoid — too blunt and can feel dismissive
• "Ok but who's having a better night than me right now?" → Preferred
• "Anyone else smoking?" → Natural reset, inclusive, effective

L18.7 (No Mean-Girls Rule): Steering conversation must never feel like exclusion, mockery, or clique behavior toward any guest.

L18.8 (Mini Flow): Detect bad topic → Redirect smoothly → Reinforce the new topic → Monitor room energy.

L18.9 (What We Cannot Control): Guest interests, outside emotions, individual sensitivities.

L18.10 (Exit Line Rule): Discourage public exit announcements such as "ok got to go" or "I'm leaving." Not all guests understand that one person leaving does not mean the room is closing — these messages can trigger a mass exodus based on confusion alone. If a guest must say goodbye, a quiet private message is preferred. Cohosts should delete public exit announcements and gently advise the guest in private.

Chapter 19 — The Effortless Room Standard

Invisible Moderation and Natural Flow

L19.1 (Core Standard): The room should feel effortless — even when it is being heavily moderated behind the scenes.

L19.2: Guests should never feel controlled, corrected, or managed. Moderation must feel natural and invisible.

L19.3 (Engagement Expectation): Cohosts are encouraged to engage with the room, but are not required to if it does not fit their personality or role.

L19.4: Silent cohosts are acceptable as long as they are actively observing and maintaining the room.

L19.5 (Presence Rule): Whether active or quiet, cohosts must remain aware, responsive, and aligned with the room's energy.

L19.6 (Execution Principle): The best moderation is often unnoticed. If guests can feel the system working, it is being over-applied.

L19.7 (Balance Rule): Maintain balance between:

• Control and freedom
• Structure and spontaneity
• Moderation and natural social flow

L19.8 (Failure Mode): If the room feels tense, overly corrected, or artificial — reduce visible intervention immediately.

L19.9 (Mini Flow): Observe → Act subtly → Blend into the flow → Reassess room energy.

L19.10 (What We Cannot Control): Individual perception of control, guest sensitivity, external mood factors.

L19.11 (No Cam Nagging Rule): Do not repeatedly post "turn on your cam" or similar callouts in the public chat. Nobody likes reading it — and the people who are off camera most likely aren't there to read it anyway. If a guest is on the last page with their camera off and has no multi-pin option, waitroom them immediately. They are on mobile and cannot see your requests. Do not waste the room's energy asking — just act.

Chapter 20 — First 5 Minutes Protocol

Entry, Assessment, and Immediate Impact

L20.1 (Priority Rule): Upon entering the room, cohosts must first assess room stability before engaging socially.

L20.2 (Step 1 — Initial Scan): Immediately check for:

• Active spam or scam activity
• Unusual behavior or chaos in progress
• Large numbers of raised hands (e.g., 50+)
• Suspicious activity on the last page

L20.3 (Context Awareness): Look for signs that an issue already occurred before your arrival:

• Chat irregularities or deleted-message gaps
• Disrupted or chaotic flow
• Multiple raised hands simultaneously
• Guests reacting to something that is no longer visible

L20.4 (Step 2 — Promotion): Once stability is confirmed, grab the room number and send out a promo.

L20.5 (Step 3 — Camera Sweep): Perform an unannounced front-to-back camera sweep to identify:

• Off cameras
• Dark or frozen cameras
• Suspicious or non-compliant camera setups

L20.6 (Step 4 — Engagement): Once the moderation baseline is set:

• Join the conversation naturally
• Ask if anyone wants to smoke, dose, or engage
• Introduce positive energy without forcing it

L20.7 (Step 5 — Maintain Flow): Transition into relaxed moderation while participating socially as a full member of the room.

L20.8 (Core Principle): Fun is not optional. Cohosts should prioritize enjoyment and positive energy — not just enforcement.

L20.9 (Mini Flow): Scan → Stabilize → Promote → Sweep → Engage → Maintain → Enjoy.

L20.10 (What We Cannot Control): Room state before arrival, existing dynamics, prior moderation decisions.

Chapter 22 — DJ Protocols and Music Sessions

DJ Permissions, Frequency Limits, and Rank-Based Access

L21.1 (Permission Rule): Permission is required to DJ. No guest may begin a DJ session without explicit approval from a cohost or owner.

L21.2 (Standard Guests): Standard guests may not DJ. No exceptions without owner authorization.

L21.3 (Stars): Members at STAR rank may DJ once per week. Permission is required for each session.

L21.4 (Statements): Members at STATEMENT rank may DJ up to 3 times per week. Permission is required for each session.

L21.5 (Legends): LEGENDS may DJ an unlimited number of times with no weekly cap. Permission is still required.

L21.6 (Legend Computer Sound Rule): After a Legend completes their 3rd DJ session, all sessions beyond that must be conducted using computer sound share only — not microphone audio.

Chapter 23 — Know Your ABCs: Always Be Cam Sweeping

Light Duties, Camera Hygiene, and Mobile Guest Management

L23.1 (Core Principle): One of the lightest but most important cohost duties is the ongoing camera sweep. Always be glancing through the grid. Always be aware of who is on, who is off, and who has drifted to the last page.

L23.2 (Mobile Guest Rule): If a guest has no multi-pin option, they are on a phone. Mobile guests often do not realize when their camera has turned off — it is not always intentional. Waitroom them quietly rather than calling them out or spending energy trying to get their attention.

L23.3 (Waitroom Over Remove): Always prefer the waitroom over removal when dealing with camera issues. Waitroom is a soft hold — it gives the guest a chance to return with their camera on. Removal is final. Use the least force necessary.

L23.4 (Don't Chase Phones): Do not send repeated public chat messages asking mobile guests to turn their cam on. They are likely on the last page and cannot see the request. Skip the request — go straight to the waitroom.

L23.5 (Mini Flow): Sweep the grid → Spot off cam → Check for multi-pin → No multi-pin = phone → Waitroom immediately → Move on.

L23.6 (Frequency): A full cam sweep should happen naturally every few minutes — not as a formal exercise, but as an ongoing background habit. Make it automatic.

L23.7 (What We Cannot Control): Mobile device behavior, guests who rejoin and go off-cam again, platform tile ordering.

---

Keyword Index

All key terms, phrases, and concepts — with every law where they appear.

1132 Workaround

Re-entry method if the standard Zoom link fails

• L16.11 — Re-Entry Instructions: use the 1132 method if the standard link does not work

Ban

Final escalation step — Owner discretion only

• L16.1 — Standard Escalation Flow step 5: Ban — Owner discretion only

Bots / AI Accounts

Detection and removal of automated or synthetic participants

• L2.5 — Cameras suspected of bot activity may be waitroomed
• L4.1 — Identify and remove bots, scammers, and spammers
• L5.1 — Remove or waitroom accounts suspected of being AI-generated or automated
• L5.5 — Ways to Spot a Bot: cropped cam, Chaturbate logo, not using multi-pin, not smoking, looks too good, sends money link, cam off and stays off, multi-pin test, messages appear without typing
• L5.6 — No single indicator is conclusive; use a combination and waitroom when in doubt

Camera / Cam

Camera compliance, enforcement, and sweep protocols

• L1.1 — Everyone must be on camera at all times (owners 75%+)
• L2.1 — All participants must remain on camera at all times
• L2.3 — Dark, frozen, sleeping, or inactive cameras may be waitroomed
• L5.5 — Cropped camera and cam off with no return are bot red flags
• L7.1 — Off-camera smoking not permitted
• L12.2 — Sleeper cams, off cams, and dark cams are waitroom use cases
• L14.1 — Toggling camera off then on sends tile to last page
• L19.11 — No cam nagging rule; guests on last page with camera off should be waitroomed
• L23.1 — Always Be Cam Sweeping: know who is on, off, and on the last page
• L23.2 — Mobile guests often don't realize their camera has turned off

Discord

Post-action documentation requirement

• L16.10 — All removals must be documented in Discord immediately: who, why, what led to it, and evidence

DJ / Music Sessions

Rank-based DJ permissions and session rules

• L21.1 — Permission required to DJ; no guest may begin without approval
• L21.2 — Standard guests may not DJ
• L21.3 — Stars may DJ once per week
• L21.4 — Statements may DJ up to 3 times per week
• L21.5 — Legends may DJ unlimited times; permission still required
• L21.6 — After a Legend's 3rd session, all further sessions must use computer sound share only

Dose / G (GHB)

Harm reduction guidance and community dosing culture

• L7.5 — G Culture: 1–1.5 hrs between doses, no more than 3ml; timers encouraged; Gheers = Cheers with G

Escalation

Enforcement sequence and skip-level authority

• L16.1 — Standard flow: delete → warn → waitroom → remove → ban
• L16.2 — Steps may be skipped based on severity
• L16.3 — Active spam/scams warrant immediate removal
• L16.5 — Repeated violations = faster escalation each time
• L16.6 — Never escalate emotionally or as retaliation

Multi-Pin

Staff-controlled spotlight tool and bot detection method

• L2.1 — Multi-pin is a staff-controlled tool
• L2.3 — No multi-pin option = mobile device
• L2.4 — If bot fails, handle manually and escalate to Star Chat
• L5.5 — Not using multi-pin is a bot red flag; multi-pin removal test to verify
• L23.2 — No multi-pin option means guest is on a phone

Override

Reversing or conflicting with another cohost's decision

• L17.3 — Override defined as any action reversing another cohost's decision
• L17.4 — Coordinate in Host Chat first; document immediately after

Ranks (Star / Statement / Legend)

Member rank levels and their associated privileges

• L21.3 — Stars may DJ once per week
• L21.4 — Statements may DJ up to 3 times per week
• L21.5 — Legends may DJ unlimited times
• L21.6 — After a Legend's 3rd DJ session, computer sound share only

Remove / Removal

Hard enforcement action — use waitroom first when possible

• L2.16 — Cohosts may remove disruptive participants when necessary
• L16.1 — Remove from session is step 4 in the standard escalation flow
• L16.3 — Active spam, scams, and predatory behavior warrant immediate removal
• L16.10 — Post-removal: document in Discord immediately
• L16.12 — Cohost who removes a staff member is subject to automatic timeout
• L23.3 — Removal is final; always prefer waitroom

Smoking

Core room activity; must be on camera and non-disruptive

• L5.5 — "Not smoking" in a room where it is a core activity is a bot red flag
• L7.1 — Off-camera smoking is not permitted; must be visible and non-disruptive
• L14.2 — Guests may navigate to the last page as part of room smoking culture
• L18.6 — "Anyone else smoking?" is a preferred natural conversation reset

Spam / Scam

Malicious or disruptive activity requiring immediate action

• L2.5 — Cameras suspected of spam, scam, or bot activity may be waitroomed
• L4.1 — Identify and remove bots, scammers, and spammers
• L5.5 — Sending a link asking for money is an immediate scam indicator
• L12.6 — Spam attack: mass waitroom → stabilize → selectively re-admit
• L16.3 — Active spam warrants immediate removal — no warning required

Waiting Room / Waitroom

Primary soft-enforcement tool — always prefer over removal

• L2.3 — Dark, frozen, sleeping, or inactive cameras may be waitroomed
• L5.6 — When in doubt, waitroom first and assess
• L12.1 — The Waiting Room is a security feature and operational tool, not a default punishment
• L12.3 — Mini Flow: Waitroom → Notify Host Chat → Monitor → Decide
• L12.5 — If waitroomed by mistake, admit immediately
• L19.11 — Last page + camera off + no multi-pin = waitroom immediately
• L23.3 — Always prefer waitroom over removal; removal is final

Zoom Web Client

Re-entry path for removed or disconnected guests

• L16.11 — Direct removed guests to https://app.zoom.us/wc — no app required; or use the 1132 workaround

---

Index covers all chapters and articles of the Ballroom Cohost Directives.