@@ -306,7 +306,7 @@ cases, schedule and verification, and the driver interface exist once, and each
 database, KeyLoad included, implements only its driver. Change a dataset or
 scenario once, in its module. KeyLoad runs every data type. Every database uses
 seed 1729, 16 clients, 1,000,000-record datasets and 100,000 planned operations
-per case with the same 6-minute limit per measured case (loads always finish), at one
+per case with the same 15-minute limit per measured case (loads always finish), at one
 node and, where the database supports it, three nodes.
 Unsupported capabilities and node counts have no cell; a failed case keeps its
 real error; never estimate, zero or invent a number.
 
@@ -13,8 +13,8 @@ internal sealed record BenchmarkSettings(int Records, int Operations, int Client
     internal const int StandardClients = 16;
     internal const int StandardSeed = 1729;
 
-    /// <summary>The mean measured case time across every database of the first per-type run (41203341021): 5.8 minutes.</summary>
-    internal const int StandardCaseMinutes = 6;
+    /// <summary>The owner's maximum wall time for one measured case, the same for every database.</summary>
+    internal const int StandardCaseMinutes = 15;
 
     /// <summary>Spreads <paramref name="index"/> deterministically over <c>[first, first + count)</c>.</summary>
     internal int Spread(int index, int first, int count)
 
@@ -11,7 +11,7 @@ decision is [ADR-150](../ADR/ADR-150-per-type-benchmark-jobs.md).
 |---|---|
 | REQ-BC-030: one job per database, data type and node count | `benchmarks.yml` has one `measure` job per row of the [type table](#data-types); a job deploys one database and runs only the TUnit class of its type. |
 | REQ-BC-031: one shared module per data type | The dataset, scenario (cases, schedule, verification) and driver interface of a type exist once; a database implements only the driver. |
-| REQ-BC-032: the same standard size everywhere | Seed 1729, 16 concurrent clients, 100,000 planned operations per measured case, at most 6 minutes per measured case, and 1,000,000-record datasets, unless a local run overrides them. Dataset loads are never stopped by the limit. |
+| REQ-BC-032: the same standard size everywhere | Seed 1729, 16 concurrent clients, 100,000 planned operations per measured case, at most 15 minutes per measured case, and 1,000,000-record datasets, unless a local run overrides them. Dataset loads are never stopped by the limit. |
 | REQ-BC-033: results survive failure | The job writes its result file after startup, after every case and on disposal, and uploads it whether the job passed or failed. |
 | REQ-BC-034: no invented numbers | A failed case keeps its real first error; a case that never ran, a missing node count or an unsupported database has no number. |
 | REQ-BC-035: the website shows one run | Website publishes the result files of the dispatched run, or of the latest completed run; without result files it publishes nothing and the current Pages stay. |
@@ -136,9 +136,8 @@ latency per call over successful calls; 0 when no call succeeded), `batchSize`
 fails when any unit fails or its after-the-fact verification finds a problem, and
 the TUnit test fails with it. No value is ever estimated or filled in.
 
-The case time limit is the mean measured case time across every database of the
-first per-type run (5.8 minutes, rounded to 6). It applies the same way to every
-database: once it has passed, clients take no new operation, operations already
+The case time limit is 15 minutes, set by the owner. It applies the same way to
+every database: once it has passed, clients take no new operation, operations already
 started finish, and `opsPerSecond` and the latencies cover only what ran. The
 site shows such a case as "<ran> of <planned>". Loads always finish, because the
 following cases read the loaded data. `Benchmarks__CaseMinutes` overrides the