Metadata-backed
The artifact or build axis is published upstream.
Does not claim local success before execution.
Detect the machine, resolve overlooked compatibility constraints, and get a sourced install or repair plan. Executed plans are verified locally.
python -m pip install rigsolvev0.1.2 alpha / Python 3.10+ / Linux x86_64 + NVIDIA CUDA / Apache-2.0
$ rigsolve solve --want 'flash-attn==2.8.3' --target 'RTX 4090,driver=580.65,python=3.12,linux'matrix 2026.08.15 | evidence: metadata-backedtorch==2.9.0 index: cu126flash-attn==2.8.3 torch2.9 | cxx11abiTRUEwarning filename does not prove sm_89 kernel coverageDriver
runtime ceiling and minor-compatibility floor
CUDA
toolkit and binary runtime line
GPU
compute capability and architecture support
Python
interpreter, ABI, platform, and glibc
torch
release, index, and CUDA build
Extensions
torch coupling and C++ ABI
HOW IT WORKS
Machine state, package requests, and sourced facts enter one deterministic solver.
Read GPU, driver, toolkit, Python, platform, and installed package metadata without importing torch.
rigsolve detectCheck driver, CUDA, Python, platform, torch, ABI, architecture, package coupling, and known broken constraints.
rigsolve solvePrint an ordered plan or a reduced conflict with its evidence.
rigsolve whyEVIDENCE MODEL
Artifact metadata, successful imports, and GPU runs are separate claims. rigsolve reports the evidence it has.
Current bundled matrix
2026.08.15 / 114 sourced facts / 1 blocked upstream edge
Plans start from published build metadata; executed plans are verified on the local machine.
The artifact or build axis is published upstream.
Does not claim local success before execution.
The exact artifact installed in a recorded environment.
Does not prove import.
The package imported and its available build metadata was recorded.
Does not prove a GPU kernel ran.
A real kernel ran on the recorded GPU architecture.
Does not imply portability to other GPUs.
Detect, solve, check, and inspect the bundled matrix offline. No telemetry.
Review pip, uv, Dockerfile, TOML, JSON, or Colab output first. --execute installs and verifies.
Every matrix fact includes its source, date, and evidence level.
OPEN SOURCE
Precise reports and reviewed verification results extend hardware coverage.