Serious AMM
  • Welcome to the New AMM
  • Start Here
    • Introduction
      • The Problem As We See It
      • Our Solution
      • Audience
  • Product Overview
    • System Overview
      • High Level Definitions
      • Key Features
      • Architecture Summary
    • User Roles and Responsibilities
      • Builders
      • Service Providers
      • Serious Ambassadors
    • Functional Specifications
      • Constant Business Formula
      • Builder Verification
      • Profile Info
      • Notifications
      • Review System
      • Internal Strike System
  • Technical Overview
    • Technical Details
      • Development Roadmap
    • Security & Privacy
  • Guides, Community & Referrals
    • User Guide
      • Builder Walkthrough
      • Service Provider Walkthrough
      • Need Help?
    • Community & Contribution
      • Community Involvement
      • Wen Token Sers?
    • Referral Mechanics
      • Referrals
      • Rewards & Payouts
      • Why should I pay Serious People?
      • How to Pay
  • Other
    • Appendix
Powered by GitBook
On this page
  • Purpose
  • What Do We Want to Prevent?
  • Strike System Structure
  • What Counts as a Strike?
  • What Does Not Count as a Strike?
  • Enforcement Tools
  • Alert and Warning System
  1. Product Overview
  2. Functional Specifications

Internal Strike System

How We Maintain a Robust Ecosystem

Purpose

  • The Strike System exists to disincentivize bad actors and ensure a high standard of quality, accountability, and responsiveness on the platform.

What Do We Want to Prevent?

  • Bad form submissions (e.g., spammy, incomplete, or inaccurate requests).

  • Spamming the system with duplicate or irrelevant requests.

  • Non-responsiveness to partners, collaborators, and platform messages.

  • Poor behavior and bad business practices (e.g., abusive language, missed deadlines).

  • Attempting to game the system, fraud, or misrepresentation of skills or Builder details.

Strike System Structure

  • 3 Strike System: Three strikes lead to a temporary ban.

    • Strike 1: Warning message sent to the user explaining the issue.

    • Strike 2: Call scheduled to discuss the behavior and provide a chance for correction.

    • Strike 3: Temporary account suspension with an explanation of why.

  • Repeat Offenses: If users are banned twice, they receive a permanent ban, but they may appeal by submitting a support ticket.

What Counts as a Strike?

  • Unresponsiveness: Not responding to platform messages, Service Providers, or Builders, for more than 2 weeks.

  • Multiple Duplicate Requests: Submitting multiple requests for the same need without a valid technical issue.

  • Poor Ratings: Receiving multiple substantiated negative reviews within a short time period.

  • Failure to Report Business: Not reporting deals or engagements made through the platform.

  • Fraud & Misrepresentation: Claiming skills or Builder capabilities that are not backed by evidence or reality.

  • Abusive Behavior: Bullying, harassment, or unethical treatment of others on the platform.

What Does Not Count as a Strike?

  • Accidents or unintentional errors with clear, good-faith efforts to resolve the issue.

  • Edge cases where the user demonstrates a valid reason for their behavior.

  • Unsubstantiated negative reviews.

Enforcement Tools

  • Warnings: Simple warnings that notify the user of their infraction.

  • Temporary Bans: Short-term bans to encourage better behavior before full deactivation.

  • Permanent Bans: Full account deactivation for repeat offenses.

  • Pause on Deal flow: Pauses all deal flow for the user as a form of temporary restriction.

  • Probation Period: Instead of immediate bans, accounts can be placed in a "probation" status where users are warned that further issues will result in a ban.

  • Rating Adjustments: Star ratings may be reduced if it's relevant to the bad behavior.

Alert and Warning System

  • Notifications will be sent to users when they receive a request or message on the platform.

  • If no action is taken after 5 days, users are temporarily paused from deal flow and receive a follow-up message explaining the importance of responsiveness in the network.

  • If no action is taken after 7 days total (2 more days after the above message is sent), the user receives their first strike.

  • From there a call is scheduled to solicit feedback and to re-engage the party in best practices. If this call is missed or unscheduled it would result in a second strike.

  • If a user reaches 14 days total of unresponsiveness, the user receives 3 strikes and is temporarily banned.

  • If a user is banned twice, they are permanently banned. Appeals are available via a support ticket.

  • Strikes can also be administered for other offenses per the context above.

PreviousReview SystemNextTechnical Details

Last updated 4 months ago