Video walkthrough

Video walkthrough

Walkthrough of the public GPU validation workflow: setup, first run, raw logs, and downloadable SHA256 analysis package.

What to expect

GPU provisioning and first setup can take several minutes. Delete the environment when you are finished.
1
Brev provisions an independent NVIDIA GPU instance
The run happens in your Brev environment, not on TeleMemetry hardware.
2
Setup pulls the public validation harness
No private engine access is required for the public scoring pipeline.
3
The benchmark interface opens on your instance
You choose the turn count, field count, and episode count before running.
4
The scoring pipeline probes real nuPlan AV telemetry
Each answer is scored against the source record inside the public harness.
5
Download the analysis package
The package includes raw input/output logs, scoring records, and SHA256 receipts you can inspect.

Visual walkthrough

Step-by-step screenshots

Hover any screenshot to zoom. Add your notes in the comment area below each image.

Brev deploy page
01 Brev setup page
Brev setup page for the public validation harness. Confirm the GPU instance and start the setup flow.
Sign in to NVIDIA
02 Sign in to NVIDIA
NVIDIA account required for Brev billing. Enter your email to sign in or create a free account.
Confirm and deploy
03 Confirm and deploy
Confirm the instance settings before provisioning. This run belongs to your Brev account and GPU environment.
GPU provisioning
04 GPU provisioning
Brev allocates the L40S instance on MassedCompute. Configure, startup script, and health check run automatically in sequence.
All systems ready
05 All systems ready
When services report healthy, open the benchmark interface from the Brev service link.
Benchmark app - Verify + Package
06 Verify + Package
The benchmark app lets you set the input numbers, then run Verify + Package to generate the validation outputs.
Verification complete
07 Verification complete
The run reports pass/fail status and prepares the local result package for review.
Results summary
08 Results summary
Result summary shows verified turns, failures, average tokens per turn, and replay reduction for this public harness run.
Machine-readable result file
09 Machine-readable result file
Machine-readable result file records the run settings, scoring output, source commit, and artifact metadata.
GPU Environments dashboard
10 GPU Environments dashboard
Brev dashboard shows the running GPU environment and service links. Delete the environment when finished to stop billing.
Secure Links - services healthy
11 Secure Links
Service links expose the local benchmark page and notebook environment while the instance is running.
Delete the environment when done
12 Delete when done
General GPU hygiene still applies: delete provider environments you no longer need, and preserve any files before teardown.

Before you launch

What this benchmark demonstrates

The public validation harness demonstrates the scoring pipeline, raw logs, and SHA256 artifact package for an independently run GPU validation pass.

It does not prove production TeleMemetry internals. It does not claim to replace all databases, RAG, compression, or pruning in all systems. The certified registry runs in the evidence library are produced by the private production harness and carry the full artifact chain required for engineering due diligence.

Read the full IP boundary statement →

Run or inspect

Run the public harness

Open the Brev setup flow or inspect the reproduction repo first. The useful output is the package: raw input/output logs, scoring records, and SHA256 receipts you can check line by line.