Reject the cluster that runs fast but cannot recover — conditional result
HOLD: 1,050 tokens/s passes; 150 s recovery exceeds the 120 s limit by 30 s. Retest the full release after repair.derived
| Value kind | derived — Derived values are guide calculations; their result is only as fixed as the stated inputs, scope, and method. |
|---|---|
| Scope | Same fixed manifest and unsupported owner gates as the input ledger. The worked trace states the arithmetic and every condition required to reverse HOLD. |
| As of | 2026-09 |
| Source | DMTF publication catalogue — management/device-trust methods; guide hypothetical case, 2026-09-08. |
| Derivation | Useful throughput = 3,780,000 tokens/3,600 s = 1,050 tokens/s. The normal run clears 1,000 tokens/s, 89.0% quality and 50 ms p99. Recovery excess = 150−120 = 30 s, so the release is HOLD even though the normal run passes. The flip requires recovery ≤120 s, the same performance/quality gates, zero unresolved critical defects and successful inventory, authorized update, failed-update recovery and rollback checks on the restored manifest. A faster normal run alone cannot reverse the decision. |
| Review | checking…review by 2027-03-08 · standard cadence |
| Recorded changes | last 2026-09-16 |
| Claim id | guide2-t29-7-14-result |
Where the guide uses it
← Full numbers register — every date-stamped figure in the guide, with revision history.