Three things went wrong on Arteza this year and not one was reported by a user.
A spend function wrote bad balance events, so the ledger drifted and the cap I thought I had wasn't the cap. Nothing threw, nothing alerted. Our sign-in gate promised a credit amount that didn't match what the account actually got, and I only found it by opening every modal in the product one at a time and reading what it promised. And before launch I said the failure I expected from 111 one click apps wasn't a crash, it was an app returning something plausible and slightly wrong that nobody would bother to report.
We just published our September cloud pricing update, with a simulation to put the numbers in context.
The 33 list prices we track across AWS, GCP, Azure, OCI and DigitalOcean didn t change. We made two small corrections to our records, but found no provider price changes.
Then we modeled a load balancer, two app servers and a MySQL database in Cloud World Model, increasing traffic from 100 to 300 requests per second.
When we first started testing dolv with early users, we did not have an explicit approval workflow.
The assumption was that teams would configure the level of automation they wanted. Some would run fully autonomous. Some would check in. Trust levels would vary.
