Skip to content

Prune post-1.0 runtime planning #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
GHoon-Lee merged 1 commit into from
May 15, 2026
Merged

Prune post-1.0 runtime planning #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Jupyter notebook open with an 8 GB tensor on the GPU and went to
lunch — `nvidia-smi` will show 1% utilization, but the card is
*unusable* by anyone else. This tool measures that.

> **Status:** main is being reset around the bare-metal 1.0 scope.
> **Status:** main tracks the bare-metal 1.0 scope.
> `gua doctor` checks only the current machine. `daemon` records NVML
> telemetry from the current NVIDIA host, `report` reads the resulting
> SQLite database, and `demo` runs anywhere with fake telemetry. The Go
Expand Down
357 changes: 0 additions & 357 deletions projects/auto-runtime-audit/plan.ko.md
View file
Open in desktop

This file was deleted.

Loading
Loading