Two posts ago, R and D were two roles, two rulebooks, one person switching hats. Last time was D's story: the loop that made shipping safe. By now the two don't split cleanly — every decision and every build happen in the same conversation. This round adds a third: QA, an external auditor with no stake in the code already being good, brought in specifically to check R and D's work from the outside.
Getting something to alpha proves it works. That's not the same question as beta. Beta is four separate things you have to prove, honestly, about the same piece of software:
Does it hold up to scrutiny you didn't supply yourself?
Can it get more capable without spending down the trust its first design earned?
Does it survive contact with real use — not just the tests you thought to write — and is it actually pleasant to use?
