Demonstration Evidence

This page is the boundary between the architecture and a claim that the runner pool works in a real cluster.

Current status

The final unraid-lab evidence proves one controlled end-to-end run. The published documentation records links and immutable references rather than publishing credentials, JIT payloads, or full operational logs.

The diagrams elsewhere on this site explain the intended design and source contracts. The evidence below additionally proves that one GitHub Actions job completed on an Imp runner.

Source-backed walkthrough and live proof

The local playable walkthrough is a presenter-controlled, source-backed reconstruction. It does not contact GitHub, Kubernetes, or Unraid, and it is not a terminal capture. It uses the safe live identifiers below alongside current source behavior.

A future genuine recording requires the separately guarded Unraid live-capture runbook. That runbook is read-only and must follow a separately authorized harmless workflow; it must not mutate Unraid to recreate this historical result.

Verified release and live proof

• Controller/agent release: Publish Unraid Development Image run 34257216712 completed successfully for commit ab7b5532810b29207fe914841467bdf69b09ff02. The immutable images were ghcr.io/syscode-labs/imp-operator@sha256:6200bf562d99baf4307c2997a14fb3b2b7e8795f23372ebcef4b0e60711ed5e6 and ghcr.io/syscode-labs/imp-agent@sha256:1f921d79c56d91506fc85d4704f6823b297ce4c8510935ba60f27734a5707892.
• Runner-layer release: the live VM used ghcr.io/syscode-labs/imp-runner-layer@sha256:c8e0ffd4e719d0eb2c09d585801a46e300d773bc204deea0cdc2d568761b6e0a.
• Live workflow: Imp smoke run 34354436248, rerun attempt 6, completed successfully. Its smoke job 102581785413 ran on ephemeral runner imp-runner-1788975945509078350 in group omni-runner from 2026-09-09T17:55:17Z to 17:55:22Z.
• Live ImpVM: imp-system/github-runner-nvksj was Running with Ready=True; its VM-owned JIT Secret was removed after the guest exited with code 0, and the ephemeral GitHub runner deregistered.
• Pool recovery: after a 90-second settling window, ImpVMRunnerPool/github-runner had minIdle=1, maxConcurrent=1, activeCount=1, exactly one running VM, and no remaining JIT Secret. The successful VM was retained as the single idle warm-pool member; a VM deletion/replacement event was not observed.

No Secret value, JIT payload, token, or private key is published here. The runner-identity annotation and GitHub job correlation are sufficient to prove registration and assignment without exposing credential material.

What the recording must prove

flowchart LR
  demand[Observed pool demand] --> capacity[Imp capacity decision]
  capacity --> vm[ImpVM capacity member]
  vm --> ready[Guest ready over VSOCK]
  ready --> assigned[GitHub assigns a matching runner]
  assigned --> completed[Job completes]
  completed --> cleanup[One-time setup and runner clean up]
  cleanup --> capacity2[Pool restores required capacity]

Plain explanation: the recording needs to show the whole loop, not only that a VM booted. A working runner pool starts a job, finishes it, removes the one-time setup, and restores the pool.

Recording rules

The recording may show:

• a harmless queued GitHub Actions job;
• ImpVM metadata and lifecycle status;
• runner registration and job assignment;
• cleanup events and replacement capacity.

The recording must not show:

• GitHub App keys;
• installation tokens or JIT payloads;
• Secret data;
• full logs that might contain credentials.

Evidence checklist

Check	Required evidence
Job selection	The job is assigned to the intended Imp runner group.
VM creation	github-runner-nvksj is created and reaches Ready=True.
Guest handoff	The guest becomes ready and receives its setup through VSOCK.
Completion	GitHub reports the harmless job as completed.
Cleanup	The VM-owned JIT Secret and ephemeral GitHub runner registration are removed after the runner exits.
Replenishment	The pool returns to minIdle=1 with one retained idle VM; VM deletion is not required for this warm-pool result.

Related material

• Under the Hood explains the source-backed control path.
• Architecture visual aids provides the presentation diagrams.
• Runner Pool E2E Runbook is the operator runbook.