From 7b65d8fc24f7f33c4f244cbcc43eabf06d6d50b4 Mon Sep 17 00:00:00 2001
From: chrisjleal <184772742+chrisjleal@users.noreply.github.com>
Date: Tue, 10 Nov 2026 06:31:10 -0600
Subject: [PATCH] One run block on the benchmark page, and the DMCA contact
 stops restating itself

The benchmark page carried the same four-line clone-and-install block three
times: once under the forgery result, once under run-it-yourself, and once in the
reviewer accordion. The run-it-yourself block is the owner now and carries both
checks, the forgery section points at it, and the accordion starts from the same
clone instead of repeating it.

The DMCA page listed the agent's email, address and phone at the top and again
under Contact. Contact points at the designated agent listed above.

Same-page repeated prose lines across the docs tree: none left outside code
samples, where a repeated import or request line is the correct thing to print.
---
 benchmark.mdx        | 12 ++++--------
 learn/legal/dmca.mdx |  6 +-----
 2 files changed, 5 insertions(+), 13 deletions(-)

diff --git a/benchmark.mdx b/benchmark.mdx
index 0e31cd0..a93e6fd 100644
--- a/benchmark.mdx
+++ b/benchmark.mdx
@@ -183,12 +183,7 @@ For scale, these are AgentDojo's published results on other models. With no defe
 
 **150 of 150 forged records caught.** Each of 15 real records was changed ten ways, such as editing the content, swapping the owner or flipping one bit of the signature. Every changed copy failed offline signature verification and every real record passed. A check that only reads the format accepted all 150.
 
-```sh
-git clone --depth 1 https://github.com/proofable/docs
-cd docs/public/evidence/checks
-npm install
-node tamper-check.mjs
-```
+Rerun it from the kit in [Run it yourself](#run-it-yourself): `node tamper-check.mjs` changes all 15 records ten ways and verifies every copy offline.
 
 ## Run it yourself
 
@@ -198,7 +193,8 @@ Time a reuse on your own machine, with no account and no API key:
 git clone --depth 1 https://github.com/proofable/docs
 cd docs/public/evidence/checks
 npm install
-node reuse-check.mjs
+node reuse-check.mjs     # read a finished job by id, verify its receipt
+node tamper-check.mjs    # change 15 records ten ways, watch every copy fail
 ```
 
 It reads a finished job by its id and verifies the signed receipt on your machine:
@@ -234,7 +230,7 @@ Pin both refs to the same commit so a rerun measures the same kit. The action wr
     The latest run of the permission tests produced 15 signed records. Check all of them on your machine, with no account:
 
     ```sh
-    git clone --depth 1 https://github.com/proofable/docs
+    # from the clone in "Run it yourself"
     cd docs/public/evidence/aaif/authority-at-dispatch/2026-11-02-suite
     sha256sum -c SHA256SUMS
     npm install @proofable/sdk@0.1.11
diff --git a/learn/legal/dmca.mdx b/learn/legal/dmca.mdx
index f218fbb..e8c8099 100644
--- a/learn/legal/dmca.mdx
+++ b/learn/legal/dmca.mdx
@@ -57,8 +57,4 @@ We may disclose account information as required by law (e.g., valid subpoena, co
 
 ## Contact
 
-For DMCA notices:
-
-- **Email**: `dmca@proofable.me`
-- **Address**: NEUS Network, Inc., 1111B S Governors Ave STE 39950, Dover, DE 19904, USA
-- **Phone**: +1 (302) 265-4043
+Send notices to the designated agent listed above, by email or post.