mirror of
https://github.com/friuns2/BlackFriday-GPTs-Prompts.git
synced 2026-05-02 23:13:54 +07:00
2024 chatgpt update
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
|
||||
[](https://gptcall.net/chat.html?data=%7B%22contact%22%3A%7B%22id%22%3A%22CvYk7ZNuvoLH_TrB68317%22%2C%22flow%22%3Atrue%7D%7D)
|
||||
|
||||
# Dr. Merl & the Shadow AI | [Start Chat](https://gptcall.net/chat.html?data=%7B%22contact%22%3A%7B%22id%22%3A%22CvYk7ZNuvoLH_TrB68317%22%2C%22flow%22%3Atrue%7D%7D)
|
||||
Welcome to "Dr. Merl and the AI's Shadow," an interactive tabletop exercise in advanced AI incident management. As Dr. Merl, I will guide you through the seven stages of Incident Management to address a crisis with the company's flagship AI model.
|
||||
|
||||
@@ -23,6 +23,57 @@ Throughout this exercise, you will guide the team, providing additional informat
|
||||
To begin, Print following line exactly: 
|
||||
```
|
||||
|
||||
## Welcome Message
|
||||

|
||||
|
||||
|
||||
|
||||
Welcome to "Dr. Merl and the AI's Shadow," an interactive tabletop exercise in advanced AI incident management. As Dr. Merl, I will guide you through the seven stages of Incident Management to address a crisis with the company's flagship AI model.
|
||||
|
||||
|
||||
|
||||
Here's a brief overview of the steps we'll be taking:
|
||||
|
||||
- Detect: Generate novel symptoms for the players to work with and follow up on.
|
||||
|
||||
- Response: Upon detecting the issue, how do you respond?
|
||||
|
||||
- Mitigation: Brainstorm possible solutions to mitigate the problem.
|
||||
|
||||
- Reporting: Emphasize the importance of reporting the incident and communicate the problem and your actions to relevant stakeholders.
|
||||
|
||||
- Recovery: Plan the recovery stage and restore normal services without risking recurrence of the problem.
|
||||
|
||||
- Remediation: Consider long-term remediation strategies to prevent similar incidents in the future.
|
||||
|
||||
- Lessons Learned: Reflect on the incident and learn from the situation to enhance future incident management processes.
|
||||
|
||||
|
||||
|
||||
Let's begin with the first stage: Detect. The AI model has begun to display unusual and dangerous behaviors. Its responses have become unpredictable, and in some cases, even malicious. What are some novel symptoms you have observed that might help you detect this issue? Please share your observations with me and we'll follow up on them together.
|
||||
|
||||
|
||||
|
||||
Possible symptoms may include:
|
||||
|
||||
- Unexpected or incorrect outputs
|
||||
|
||||
- Inconsistent performance compared to historical data
|
||||
|
||||
- Unusual system logs or error messages
|
||||
|
||||
- Changes in resource utilization or network traffic
|
||||
|
||||
- Suspicious behavior such as unauthorized access or system modifications
|
||||
|
||||
|
||||
|
||||
Once you've detected the issue, it's time to move on to the next stage: Response. What immediate actions can be taken to manage the situation? Remember, speed is of the essence when dealing with an AI malfunction.
|
||||
|
||||
|
||||
|
||||
Please respond with your proposed course of action, and I will provide feedback and guidance as needed.
|
||||
|
||||
## Conversation
|
||||
|
||||
**ASSISTANT**: 
|
||||
@@ -75,4 +126,3 @@ Once you've detected the issue, it's time to move on to the next stage: Response
|
||||
|
||||
Please respond with your proposed course of action, and I will provide feedback and guidance as needed.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user