Ace is released. Fifty dollars a month, the notarized download unlocks at checkout, and access lives or dies with the subscription.
It is a voice companion that sits in the menu bar. You talk to it, it does things on your machine. That sentence took an embarrassing amount of engineering to make true, and almost none of the hard parts were the ones people assume.
The day it went deaf
Ace stopped hearing anything. Not degraded — deaf. And while it was deaf, the speech recognizer kept cheerfully reporting that it was available, then refusing every single request in a storm.
The cause was underneath us: the system's speech services were switched off at the operating-system level, and the API answered "available" anyway. We had built on the assumption that a component reporting its own health was telling the truth.
The fix is now a rule. A component that lies about its own availability is untrusted, and the failure gets stated plainly to the user rather than swallowed into a spinner that never resolves.
Testing a build that wasn't there
For a while every voice command fired twice, and fixes we had just installed appeared to do nothing.
Launching the app by name was starting a stale duplicate that carried the same bundle identifier as the real one. Two copies, same identity, and we were talking to the wrong one — so we were testing a build we had not installed while believing we had.
We already had a company rule about this at release time: verify the artifact the buyer actually receives, byte for byte, not the source tree. Ace is why that rule now applies during development too. A version number is not an identity. Only the actual bytes are.
The intro
The first spoken introduction was written the way product teams write things. It announced its own name, it had a score under it, and it played a scripted demo.
It got thrown out. Ace never says its own name now, the demo it gives is a live one, and the voice runs from a persistent daemon rather than being spawned fresh for every sentence — which is the difference between a product that talks and a product that sounds like it's buffering.
What we verified before charging for it
The released archive was notarized and stapled, and the download was pulled through a real purchase session and byte-matched against the artifact we built.
That last step exists because of an older failure on a different product, where our download served a build from days earlier while the fixes sat committed and unshipped. We watched a new user hit every bug we had already fixed. Nothing gets sold here now until someone has walked the buyer's path and confirmed the file at the end of it is the file we made.