Re-Verification

Type 1: General Re-Verification (Incident-Based)

• Snippet: -reverify

• Use Case: A specific incident, report, or moderation review raises general age concerns or irregularities. No explicit minor statement is required.

Type 2: Under-18 Statement or Implication

• Snippet: -reverify statement

• Use Case: A member states, implies, or jokes about being under 18 (e.g., mentions of high school, "not 18 yet," or age jokes). Intent does not matter—immediate re-verification is mandatory.

Type 3: Under-18 Role Selected After Partner/Cross-Verification

• Snippet: -reverify partner

• Use Case: A member previously verified via a partner server later selects an under-18 or minor-coded role. Overrides partner status and forces in-house verification.

Type 4: Under-18 Role Selected After In-House Verification

• Snippet: -reverify inhouse

• Use Case: A member who completed in-house verification later selects an under-18 role. Indicates serious account misuse or a trust breach.

Type 5: Conflicting or Changed Age Information

1. Raising an Age Concern

Any staff member who identifies an age issue must immediately escalate it to the Admin team. Do not question, confront, or debate the member in public channels.

2. Admin Initiation Procedure

Once an Admin determines re-verification is required, execute the following steps without deviation:

1. Open an Admin Outreach (Tier 2) ticket using /new and add the member.

2. Unverify the member immediately using /staff verification.

3. Post the corresponding -reverify snippet, tag the member, and give a strict 48-hour deadline using a formatted timestamp.

4. Disable ticket auto-close via /ticket autoclose action:Toggle.

5. Open a private discussion thread inside the ticket using /ticket notes.

3. Member Instructions