EXACT CLOUD RESOURCE
—
Awaiting provider evidence.
ISOLATED CLOUD RETIREMENT EXPERIMENT
Retire the service.
Check the work.
A separate, controlled test of an exact Cloud Run resource: compare synthetic work before and after retirement, verify provider absence, and keep sustainability conclusions tied to what was actually observed.
CONTROLLED STAGING · READ-ONLY RESULTSResource removal and carbon savings are different findings.
This experiment uses minimum instances of zero. An idle service could scale to zero without deletion. No continuous avoided runtime, physical server shutdown or carbon reduction follows from a service disappearing.
Loading the published experiment report…
The experiment report is unavailable.
No outcome has been inferred.
MATCHED SYNTHETIC WORK
—
Results, work rate and response-time target are checked separately.
ENERGY / CARBON SAVING
Not established
Resource evidence alone is insufficient. No sustainability saving is claimed by this page.
Did useful work continue?
Evidence not yet assessedResponses are independently recomputed from each request’s ID and payload. The before and after phases must use the same ordered payloads, fresh IDs, the same requested rate, comparable observed rates and a p95 response time below 2 seconds.
01 · BEFORE
Baseline work
—independently verified responses
02 · AFTER
Post-retirement work
—independently verified responses
03 · FRESH CANARY
New work after removal
—independently verified responses
| Observed phase | Verified / requested | Requested rate / s | Observed verified / s | p95 response |
|---|
This is a bounded fixture test.
These deterministic responses and ephemeral duplicate checks are not durable exactly-once customer business effects. This experiment does not replay the original seven-gate run or create a new signed retirement receipt.
Which resource was retired?
The retirement adapter binds the approved service identity and provider version. A provider operation is followed by an independent absence check; a same-name replacement must not be deleted.
- Exact resource
- Unavailable
- Provider-confirmed removal
- Unavailable
- Deployment configuration before retirement
- Unavailable
- Deployed image digest
- Unavailable
- Recorded provider UID
- Not included in this public summary
- Provider generation / ETag
- Not included in this public summary
- Reviewed preflight plan SHA256
- Not included in this public summary
What did the provider measure?
Only exactly scoped, valid provider points are reported. Missing data remains unavailable. Instance-count samples cannot be silently converted into instance-hours.
Instance-count samples
UnavailableNo provider observations supplied.
Billable instance time
UnavailableNo provider observations supplied.
No avoided-capacity extrapolation.
Minimum instances stay at zero. Removing this service does not justify multiplying its configured CPU or memory by 24 hours a day. Billing time is not electrical energy or a measured carbon footprint.
The conclusion the evidence supports
No carbon result has been supplied.