Speaking of vulnerability task, my current view is that the right framing is discovery -> fixing, not “can one open model replace Opus everywhere.”
Discovery is the expensive part because it has to search broadly across a codebase. Fixing / patching is narrower once the relevant area is identified, so it is much more plausible to spend frontier-model dollars there.
Aisle’s earlier point was that the moat is the system / scaffold, not just the base model. (AISLE1) Their new post strengthens that materially: they now describe a public whole-codebase scanner, nano-analyzer, that scans files independently in three stages — context generation, vulnerability scan, and skeptical triage with grep plus an arbiter — and they report that it can replay the flagship Mythos FreeBSD bug and surface new real bugs from full-kernel scans. ([AISLE2](https://aisle.com/blog/system-over-model-zero-day-discovery-at-the-jagged-frontier "S