The Friction That Stopped Waste

One observation from using agentic engineering with Brighter is that the old adage of “work expands to the resources available” is definitely true. In an OSS context, where I am paying for tokens out of pocket, that is my call, but the trade-offs need thought in commercial settings. Quality From The Loop The cause, I think, is that the loop of generate => evaluate => repeat. It helps drive quality, typically higher than we would have reached through manual effort. I set this up so a sub-agent (or new agent) with a fresh context can review our last milestone. The review agent assigns a score derived from its evaluation. We want to ignore findings below a certain score as “noise” so we don’t get too many “false positives.” We break the loop when all of the evaluation findings fall below that threshold. Typically, the review process is run after gathering requirements, creating the program design, building the task list, and generating the code. In essence, it helps to prevent the slop…