From 08c63f9113fbeab7ff2d4edcf43c038a2a4fd6ca Mon Sep 17 00:00:00 2001 From: Avi Fenesh Date: Tue, 6 Oct 2026 04:52:10 +0300 Subject: [PATCH] Drop copied GPU validation paragraph from AGENTS.md The "Validation scope" section about GPU, native and model qualification was pasted from another project. This repo is a set of research guides with no GPU or model behavior, so the paragraph only adds noise to the instruction file. --- AGENTS.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 2a98bad..628bd90 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -763,12 +763,3 @@ Use this knowledge when user asks about: 2. Read the relevant guide file 3. Answer based on synthesized knowledge 4. Cite the guide if user asks for sources - -## Validation scope - -Choose checks that cover the changed behavior. For CPU-only tooling, documentation -and configuration changes, run the relevant CPU tests, static checks and configuration -validation. Do not require a blanket GPU gate for those changes. Require GPU -qualification when GPU, runtime or model behavior, or related claims, change. -Preserve applicable native, model and hardware qualification gates. CPU checks do -not qualify GPU behavior.