Inspect the records
Inspect the evidence behind the claims
Real product captures and tool results from an operator-owned VPS, with the boundaries of each result made explicit.
You can distinguish a screenshot, a current health snapshot and a recorded deployment operation.
On this page
An active ChatGPT grant
This proves the grant exists and is scoped. It is not itself proof that every permitted action has been executed.
A fresh MCP health read
On 22 September, ChatGPT called deployment.health for rentaweekend through the Ground Control connection. The response reported four healthy containers and a checked public endpoint with HTTP 200. It is a dated snapshot, not a live status widget.
{
"deployment": "rentaweekend",
"runtime": { "healthy": true },
"public": { "checked": true, "status": 200, "healthy": true },
"healthy": true
}The recorded merge-triggered operation
ChatGPT retrieved the following existing operation with operation.get. Its trigger was a signed GitHub push; it should not be described as a new agent-issued redeploy.
| Evidence | Recorded value |
|---|---|
| Operation | cmubbc14l0002tjpa0r56r1sm |
| Type | deployment.source.deploy |
| Created | 2026-09-21T14:00:45.238Z |
| Finished | 2026-09-21T14:03:16.791Z |
| Result | success · 1 attempt · error: null |
| Source commit | 468acf8d69821cf2c83af1629ee853325354a306 |
| Runtime image tag (web/API) | 0661793317ffeafd5b6740ee3bea0884336a0d26 |
| Verification | Service images/states matched Compose; public HTTP 200 passed |
Download the operation fields and exact log excerpts (JSON) ↓
The source revision and runtime image tag differ. The record proves source synchronization and runtime/Compose consistency, not that those images were freshly built from that source revision. It also records a host build. Exact immutable artifact provenance and off-host building need their own verification.
Clean-host distribution acceptance
Distribution Acceptance #7 passed on a disposable Linux runner against GroundControl revision e27dddec3bdf5944de7ca7317b1bbbf32b203953.
| Proven by that run | Outside its scope |
|---|---|
| Install, owner claim and private loopback binding | Every VPS operating-system combination |
| Persistent storage, host execution, PTY, MCP and OAuth discovery | Caddy and Cloudflare public routes |
| Idempotent rerun and same-image guarded upgrade | Every cross-version migration or failed-upgrade rollback |
| Runtime uninstall with data preserved | Off-host disaster recovery |
The full procedure is in Upgrade & recover. You do not need to read GitHub to follow the setup; the run link is the underlying test record.