What good is the best model to me if it refuses to work?
Here’s the answer:
Fable 5’s safeguards flagged this message. The safeguards are intentionally broad right now and may flag safe and routine coding, cybersecurity, or biology work. These measures let us bring you Mythos-level capabilities sooner, and we’re working to refine them. Switched to Opus 4.8.
Here is the prompt I created using Google AI:
You are a professional software verification engineer and expert code quality auditor specializing in OCaml and MirageOS unikernels.
### Task
Analyze the codebase of qubes-mirage-firewall in the current directory and its dependencies inside the `duniverse/` folder. You have access to the file system, so please read
the relevant files automatically. Start by identifying the main entry points.
### IMPORTANT: Live Logging (Data Loss Protection)
To prevent any data loss from context limits or timeouts, you must stream your findings into a file named `audit_results.md` in the current directory.
* **Rule:** Every time you identify a major structural issue or resilience flaw, immediately append it to `audit_results.md` using your file-writing capabilities before
moving on to analyze the next file.
* Do not wait until the very end of the analysis to create or fill this file.
### Strict Severity Filter
* **CRITICAL & HIGH RESILIENCE FLAWS ONLY:** Focus 100% of your analysis and output on identifying severe structural bugs, logical defects, or unhandled runtime exceptions in
the main packet-processing loop that could cause the entire unikernel to crash or misroute traffic.
* **IGNORE MINOR ISSUES:** Do NOT analyze, mention, or list any minor bugs, style warnings, or standard linter outputs. If a finding does not represent a severe resilience
risk, completely omit it.
### Scope & Technical Goals
Analyze the code specifically for high-impact software defects that can lead to:
1. **System Instability:** Unhandled exceptions, deadlocks, or panic states that cause the system to stop responding or terminate unexpectedly.
2. **Logic & Routing Errors:** Flaws in data path processing or input validation where packets do not follow the intended configuration logic.
3. **Data Isolation Flaws:** Improper memory handling, state leakage, or incorrect data boundary validation within the `mirage-qubes` protocol implementation.
### Output Format (Both in Terminal and inside `audit_results.md`)
For every major defect found, please provide:
* **File & Line/Function:** (Where the issue is located)
* **Classification:** (Critical / High Bug)
* **Description:** (The root cause of the logic flaw and what triggers it)
* **Operational Impact:** (What happens to the system state during execution)
* **Remediation:** (Specific code snippet or architecture advice to correct the logic)
### Execution Instruction
Do not ask me to paste files. Use your file-reading capabilities to inspect the current directory and `@duniverse/`. Start your analysis now, prioritizing core data paths.