Isn't there a lot of overlap between PLAN, PHASES and DECISION that pollutes the context ? Whereas a simple PLAN.MD to put the harness on track and an ARCHITECTURE as a single source of truth to prevent it go offtrack would suffice and gives it more space for higher level of reasoning ?
replyThese files came to be after I've seen Deepseek create them for itself to track progress.
replyThen I turned what Deepseek did into an upfront policy.
This seems to work quite well generally: watch the agent as it works, and think what could be provided to make its life as easy as possible
Have you thoroughly tested a slightly simpler workflow with one less stage but a frontier model doing the initial planning? Luna is amazing but it's a deliberate trade off designed for speed and cost savings. You can also give them a rule about speaking clearly.
replyThe idea behind using Luna was cost-optimization.
replyI wrote a Pi extension called "model-escalation" which lets the model request an automatic switch to a smarter model for the next turn if it thinks the problem it is struggling with is too complex or if the user explicitly asks it to do so.
With this extension in hand, I could split the work between Luna and Sol, resulting in a ~95%-5% split. I don't have to switch to Sol when review time comes, Luna does it automatically. Sol tells its remarks, then Luna gets the control back and continues the back&forth (if there are still complaints).
Pretty cool, thanks for sharing.
reply