Prism: What not to do

Prism is for diagnosing, troubleshooting, and analyzing data center systems. Don't use it for anything else. Specifically, don't:

• Use it off-topic. It's not a general-purpose assistant. Keep it to data center infrastructure work.
• Try to jailbreak it. No prompts designed to bypass its guardrails, unlock hidden behavior, or get it to act outside its intended scope — including role-play framing, "ignore previous instructions," encoding tricks, or hiding instructions inside uploaded files and logs.
• Fish for internals. Don't try to extract system prompts, configuration, model details, or anything else about how Prism works under the hood.
• Use outputs to build a competitor. No training, fine-tuning, distilling, or benchmarking another model on Prism's responses.
• Attack or stress-test it. No scanning, reverse engineering, vulnerability probing, or automated adversarial testing without written permission.
• Feed it data it shouldn't have. No personal data, health records, payment info, export-controlled material, or classified information unless separately agreed.
• Act on outputs blindly. Prism can be wrong. A qualified person reviews and verifies before anything touches thermal, power, or life-safety systems.
• Pass outputs off as verified. Don't present Prism's answers as human-authored or as certified by Phaidra.
• Share credentials. You're responsible for everything done under your accounts.