# Internal Strike System

### **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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://serious-people.gitbook.io/serious-amm/product-overview/functional-specifications/internal-strike-system.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.