After spending these last days with Fable 5... I'm starting to think the biggest lesson wasn't the model itself... it was the architecture around it. When Fable 5 goes back behind usage credits, what's your plan? • Stay with Fable? • Switch to another frontier model? • Use 5.6 Sol | GLM | Local model's as your worker? • Or invest in a better orchestration layer with planning and independent verification? I'd love to hear what everyone is building/planing.

Join the stream https://youtube.com/live/DLjv_2nbQAA?feature=share

I just published WAVES, the method I have been using to run AI agents in parallel without letting them run wild. An agent will always tell you the job is done, and WAVES treats that as a claim and checks the evidence behind it before it counts. You fan the work out to a team of agents, each one owns a slice, and the verifier is what decides when the work is done. It runs in Cursor, Codex, Claude, and Droid, and ships as a skill you can install today. The full breakdown is on the blog, with diagrams, the handoff format, and where it fits next to loops and parallel orchestration: https://www.rayfernando.ai/waves-workers-aggregate-verify-extend Skill: https://github.com/RayFernando1337/rayfernando-skills/tree/main#waves--fan-out-to-parallel-agents Give it a run on something real and tell me how it goes.

https://youtu.be/iQyg-KypKAA?is=ADk1EVQNmQ3DKkF-

Not sure if everyone is already doing this, but accidentally stumbled into it and it seems to be working really well. I have told fable to spin up opus or sonnet agents when doing so will not lose intelligence, and it seems to be working really well to reduce costs. --and on a side note, I can't get fable to run a single security audit without downgrading to opus which is really annoying