feat(cuda): add non-certifying real-NVIDIA E3 evidence - #13
Merged
Merged
Conversation
added 15 commits
July 24, 2026 14:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an opt-in, manual first-stage evidence path for the bounded TensorFlow CUDA E3 candidate while preserving the existing non-certifying contract.
_rextio_nativeextension in the same process as the active TensorFlow wheel.matmul -> bias_add -> relu -> reduce_mean(axis=1)GPU:0 slice, numerical parity, input immutability, output lifetime, repeated calls, and the five implemented negative boundaries.Evidence semantics
This does not promote CUDA support or certification:
support_claim=falsecertification_ready=falsekernel_activity_verified=falseruntime_transfer_profiled=falseThe evidence is self-attested by the manual harness. The offline verifier checks canonical schema and payload integrity only; it does not authenticate the producer, recompute artifacts, prove execution, certify hardware, or establish performance.
Hosted CI remains GPU-free. It does not install/import TensorFlow in the CUDA evidence lane, load the extension, or execute CUDA. A real-NVIDIA run remains an explicit later operator action.
Review hardening included
Cargo.lockwith the pinned toolchain before the required--lockedbuild.EXT_SUFFIX./proc/self/mapspaths for the three TensorFlow DSOs and rejects deleted/suffixed aliases.Local verification
pytest -m 'not needs_cargo': 408 passed, 1 skippedgit diff --check: passedNo real GPU success is claimed by this PR.