Discussion about this post

User's avatar
Olga Ostrovskiy's avatar

What went the other way for me is verification. As the models absorbed more of the planning, the bottleneck moved to the one human in the loop. My agents run a books-to-travel product day and night, and what limits throughput is not tokens or orchestration, it is that everything still routes through me approving it. The harness feature I keep adding to, rather than deleting, is whatever makes a change reviewable in two minutes instead of twenty.

Jason Colapietro's avatar

What happens if it is wrong is the question that gets skipped hardest, and it is the one that should decide the architecture. Most harness complexity I have added was really compensating for having no answer to it. I ship a small public skill pack solo, and the honest fix was almost never more orchestration. It was recording each step so a wrong answer was findable.

No posts

Ready for more?