#harness

7 posts· Last used Aug 08

Dont be like oak. Be like reed in the storm. I have this problem in my Ai #Harness. I take a complex problem, decompose it, and then varioius engines to bruteforce it... The decomp is into a WU (Work Unit) chunk and sometimes they fail. I had one roll through 400 iterations (I stepped away from the keyboard for a few days /eyeroll) My solution is, to run a decomp again on that failing WU. Rather than the whole (15 page smoketest) prompt... ...and again... ...and again... ...and again... until something that doesnt die pops out... I can do this because I am rotating throug various models. Using the stochiastic nature of #LLM as a strenght... now a weekness 😀 #Vibecoding
0
0
0
0
The spinny 3D Ai Harness multi graph... ...why? Because we can. Engines that hit their compute limits are red. Some of the small wireframe engines have not had their "Power" evaluated yet, so the Harness router has them on the end of fall-through hierarchy. The skulll is a local guardrail free - model. Oh, and I bought some API time on togetherAi. Because its cheap and gives me access to GLS and Kimi models which are comparable with #Anthropic Opus Using those two models, I now can have a viable alternative to Opus/Sonnet with adequate tokens. #Vibecoding #Harness
0
0
0
0
...aaand Im out of compute. Implemented a visual dashboard for the engine router because it was an algorithmic black box. Its still computing the new revised WOOFER V2 values (more angry judge so we dont get 100%). So the values are still fluid. But you get an idea. There are three classes of decomposed WUs (Working Units), the engine router assigns the engine to the WU based on WU difficulty. There is a manual slider now so I can tweak difficulty floor. #Vibecoding #Harness #Harnessengineering
0
0
0
0
You've seen all posts