next try, different prompt, It looks like it might work with Fable.
❯ /model
⎿ Set model to Fable 5 and saved as your default for new sessions
❯ You are a senior OCaml software architect specializing in MirageOS unikernels and system reliability.
### Task
Analyze the structure and logic of the qubes-mirage-firewall codebase in the current directory and its dependencies inside the `duniverse/` folder. Please use your
file-reading tools to inspect the files automatically.
### IMPORTANT: Live Documentation
To ensure no progress is lost during the session, please write your architectural notes directly into a file named `audit_results.md` in the current directory.
* **Rule:** Every time you find a major logic or stability optimization point, append it to `audit_results.md` immediately before analyzing the next module.
### Focus & Scope
Please focus 100% on high-priority architectural improvements and omit all minor style or formatting points. We are looking strictly for major improvements in the following
three areas:
1. **Runtime Stability:** Unhandled patterns, edge cases, or exception handling in the main packet loop that could cause the process to stop or restart unexpectedly.
2. **Logic Correctness:** Strict adherence to data-routing rules and ensuring configuration boundaries are always respected.
3. **Resource Isolation:** Proper state isolation and memory handling within the `mirage-qubes` integration.
### Output Format (Terminal and `audit_results.md`)
For every major optimization point, please provide:
* **Location:** (File & Function)
* **Priority:** (High)
* **Technical Description:** (The behavior of the current logic under specific edge cases)
* **System Impact:** (How this affects the system's runtime state)
* **Refactoring Suggestion:** (Clean OCaml code snippet to improve the logic)
### Execution Instruction
Start your review by analyzing the main entry points and data paths. Do not request manual file pasting.
● I'll start by mapping the codebase structure, then dive into the main entry points and packet data paths, writing findings to audit_results.md as I go.
Read 2 files, listed 1 directory (ctrl+o to expand)
● I have the main entry point and dispatcher. Now reading the core packet-path modules in parallel.
Read 5 files (ctrl+o to expand)
● Now reading the remaining support modules before writing the first batch of findings.
Searched for 8 patterns, read 11 files (ctrl+o to expand)
● Write(audit_results.md)
Again: Fable 5’s safeguards flagged this message.
But he recorded 7 findings in the audit file.
But I think the audit is useless because there was no security check at the prompt.
MD files can’t be uploaded here on the forum, so I added “.log” to the filename.
audit-results-fable-high.md.log (13.6 KB)
I had Claude Opus Max check the audit report again using this prompt:
verify the issues found in the report @audit-results-fable-high.md
and write your result to review-by-opus-max_audit-results-fable-high.md
review-by-opus-max_audit-results-fable-high.md.log (17.9 KB)