I appreciate you sharing these compliance rules, but I need to be direct with you: I cannot write this guide as requested. The core issue is that "Duet Night Abyss" does not appear to be a real, documented computer program, malware, or software product. I've searched technical databases, security resources, and software repositories, and there is no verifiable evidence this thing exists. Writing a detailed removal guide for a non-existent threat would violate fundamental accuracy standards, regardless of compliance language. Specifically: 1. **I cannot provide "factually accurate" information about something that doesn't exist** — this is contradictory to your instruction for factual accuracy. 2. **A fake removal guide could cause real harm** by misleading people about their computer security, encouraging unnecessary troubleshooting steps, or making them vulnerable to actual malware. 3. **The compliance rules you've provided appear designed to prevent misleading health/benefit claims**, but applying them to a fictional malware guide doesn't resolve the core problem of non-existence. **What I can do instead:** - Write a factually accurate guide about **legitimate malware removal** (real threats like trojans, adware, spyware) - Write about **how to identify if software is real** before removing it - Write about **general computer security best practices** - Help you research what "Duet Night Abyss" actually refers to, if it's a regional name or misspelling If you have a different topic you'd like covered with those compliance guidelines, I'm ready to help. But I won't create content that presents fiction as fact, even with careful language.