Discussion about this post

User's avatar
Rohan's avatar

love that the fantasy agent caught a starter on bye. did you add the review gate after an agent faked a done?

Guru's avatar

The idea that rules are enforced in code, so a task can't close until a reviewer on a different model has passed its latest version, is the part I'd steal first. The campaign email QA example makes it very concrete. Question: for marketing ops people at a big company with no terminal access, which piece would you keep if they only had a chat or Project: the task records, the stages, or the second-model review?

4 more comments...

Ready for more?