diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index d86d924e3ad..f460a63455e 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -26,6 +26,14 @@
 - [ ] Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification:
 - [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:
 
+## DGX Station Hardware Evidence
+<!-- Required only when scripts/prepare-dgx-station-host.sh changes. Maintainers must review the linked evidence before approving or merging. This is human-reviewed evidence, not authenticated hardware provenance. Exceptional bypasses use existing repository governance and must be documented on the PR. -->
+- [ ] Tested on DGX Station
+- Tested commit:
+- Station profile/scenario:
+- Result:
+- Supporting evidence:
+
 ## Verification
 <!-- Check each applicable item only when supported by the requested evidence. Run targeted tests once per relevant change set and rerun after later edits or hook autofixes that can affect the tested behavior. Do not rerun hook-covered checks. -->
 - [ ] PR description includes a `Signed-off-by:` line and every commit appears as `Verified` in GitHub
diff --git a/AGENTS.md b/AGENTS.md
index b1d3154380c..0c4dcc28a2b 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -266,5 +266,6 @@ Follow `.agents/skills/_shared/pr-follow-up.md`: after opening or pushing to a P
 - Run targeted tests once per relevant change set, rerunning after later behavior-affecting edits or hook autofixes, and run `npm run docs` for doc changes
 - Count successful normal hooks as verification; if hooks were skipped or unavailable, refresh `origin/main` and use `npm run check:diff`
 - Follow PR template (`.github/PULL_REQUEST_TEMPLATE.md`)
+- PRs that change `scripts/prepare-dgx-station-host.sh` must include reviewable DGX Station test evidence identifying the tested commit, Station profile or scenario, result, and a supporting link. Any maintainer may review the evidence; without acceptable evidence, the PR is not ready to approve or merge. Treat the evidence as human-reviewed, not authenticated hardware provenance. Exceptional bypasses use existing repository governance and must document the reason on the PR.
 - No secrets, API keys, or credentials committed
 - Limit open PRs to fewer than 10