I’d be curious what performance / behavior changes you’d observe with two changes:
- planner nodes and topo deepest for rescheduling, no inflight modifications. (repair protocol = redispatch root planner for rare cases where required; ~9% of the time for me)
- no review nodes; strongly enforced on orchestrator to always do adversarial reviews post-codegen and fix out of band
I found that putting myself in the graph is critical to ongoing fidelity, even if subpar to if I had written it all myself.
It’s shockingly effective due to rooting sub-DAGs into Planner nodes which are the only mutators of the DAG. The deepest topological leaf nodes become the blockers to the next Planner node.
The only other special node is a Human node; structurally impossible for agents to close (I rolled my own harness) and block on my attention.
I’ve been falling back to Opus 4.6 since 4.7 and 4.8. I recently found success in using Opus 4.6 for cheap orchestration and reasoning while Opus 4.8 High/Max agents do the work.
I made serious progress towards repairing a proof for a conjecture that was published 10 days ago but kept running into a wall with one of the Lemmas.
I threw Fable 5 Max at it with the same subagent set up and in an hour it claimed to have disproved a core theorem of the paper.
The Lean construction looks correct, but I still need to verify it rigorously. This is certainly not something Opus 4.6 Max could do and it’s likely something Opus 4.8 Max could do with more delicate orchestration and time. However, the “one-shot” Fable 5 did give me pause.
I would love to know how many countless others on HN, like me, find themselves reading about a very they have built and have been using for months talked about like it’s a revolutionary new idea.
> Schmidt, who served in various capacities as CEO, Chairman, and technical advisor to Google and its parent company Alphabet across several decades, ...
Cool utility! I would be remiss if I didn’t mention synctest [1] which is quite excellent for not only async time testing but also catching subtle concurrency bugs.