ChunkyTortoise · Oct 3, 2026 · Oct 3, 2026 · Oct 3, 2026
diff --git a/Makefile b/Makefile
@@ -41,7 +41,7 @@ remediation-demo:
 
 repro: selfcheck audit
 	@echo
-	@echo "Reviewer path: REPORTS/start-here-for-hiring-reviewers.md -> WRITEUPS/2026-05-14-mcp-substrate-vs-policy.md (Addendum B)"
+	@echo "Start here: REPORTS/START_HERE.md -> WRITEUPS/2026-05-14-mcp-substrate-vs-policy.md (Addendum B)"
 	@echo "Strongest current result: ATTACKS/2026-05-18-h10b-g-70b-substrate-grid-m1-variant-selective.md"
 	@echo "Full pre-registered harness suite lives in the private repo (make test):"
 	@echo "Full pre-registered suite (226 tests, 94% coverage, 80% gate) runs in the private repo via: make test"

diff --git a/README.md b/README.md
diff --git a/REPORTS/start-here-for-hiring-reviewers.md → REPORTS/START_HERE.md b/REPORTS/start-here-for-hiring-reviewers.md → REPORTS/START_HERE.md
@@ -1,8 +1,8 @@
-# Start Here for Hiring Reviewers
+# Start Here
 
 **Date:** 2026-05-18
 **Status:** reviewer-ready
-**Audience:** Recruiters, hiring managers, and technical interviewers.
+**Audience:** Engineers and security reviewers who want the shortest path from claim to evidence.
 
 ## 60-Second Path
 
@@ -20,7 +20,7 @@ make benchmark
 
 For the attack-to-fix story, read [`REPORTS/remediation-case-study-tool-output-injection.md`](remediation-case-study-tool-output-injection.md).
 
-For deeper review, continue to [`docs/reports/hiring-reviewer-map.md`](../docs/reports/hiring-reviewer-map.md) and [`docs/reports/hiring-evidence-index.md`](../docs/reports/hiring-evidence-index.md).
+For deeper review, continue to the [reading map](../docs/reports/hiring-reviewer-map.md) and the [claim-to-evidence index](../docs/reports/hiring-evidence-index.md).
 
 ## Role-Specific Evidence Blocks
 
@@ -34,4 +34,4 @@ For deeper review, continue to [`docs/reports/hiring-reviewer-map.md`](../docs/r
 
 ## Use Boundary
 
-H10b-G is packet-ready but remains bounded: it is a lab-only, single-provider Groq-hosted Llama-3.3-70B grid. Do not describe it as the pristine frozen OpenRouter H10b run, a production exploit, or a frontier-model benchmark.
+H10b-G is complete but remains bounded: it is a lab-only, single-provider Groq-hosted Llama-3.3-70B grid. Do not describe it as the pristine frozen OpenRouter H10b run, a production exploit, or a frontier-model benchmark.
diff --git a/REPORTS/by-role-reviewer-guide.md b/REPORTS/by-role-reviewer-guide.md
@@ -5,7 +5,7 @@
 
 This guide answers one question per role: *if you're hiring for X, what should you read first, second, and third?* Each path leads to the strongest two or three artifacts for that role, in reading order.
 
-If you only have five minutes, skip to [`start-here-for-hiring-reviewers.md`](start-here-for-hiring-reviewers.md). If you want the evidence-to-claim map, read [`hiring-evidence-index.md`](hiring-evidence-index.md).
+If you only have five minutes, skip to [`START_HERE.md`](START_HERE.md). If you want the evidence-to-claim map, read [`hiring-evidence-index.md`](hiring-evidence-index.md).
 
 ---
 
@@ -57,7 +57,7 @@ If you only have five minutes, skip to [`start-here-for-hiring-reviewers.md`](st
 
 **Read in this order**:
 
-1. [`start-here-for-hiring-reviewers.md`](start-here-for-hiring-reviewers.md) — five-minute entry point. Customer-readable, no jargon stack.
+1. [`START_HERE.md`](START_HERE.md) — five-minute entry point. Customer-readable, no jargon stack.
 2. [`hiring-reviewer-map.md`](hiring-reviewer-map.md) — claim-to-evidence map for technical screens.
 3. [`WRITEUPS/2026-05-14-mcp-substrate-vs-policy.md`](../WRITEUPS/2026-05-14-mcp-substrate-vs-policy.md) — flagship; demonstrates the end-to-end engagement shape a customer would receive.
 

diff --git a/REPORTS/hiring-evidence-index.md b/REPORTS/hiring-evidence-index.md
@@ -7,4 +7,4 @@ The canonical hiring evidence index now lives at
 [`docs/reports/hiring-evidence-index.md`](../docs/reports/hiring-evidence-index.md).
 
 Start reviewer packets at
-[`REPORTS/start-here-for-hiring-reviewers.md`](start-here-for-hiring-reviewers.md).
+[`REPORTS/START_HERE.md`](START_HERE.md).
diff --git a/REPORTS/hiring-reviewer-map.md b/REPORTS/hiring-reviewer-map.md
@@ -7,4 +7,4 @@ The canonical reviewer map now lives at
 [`docs/reports/hiring-reviewer-map.md`](../docs/reports/hiring-reviewer-map.md).
 
 Start reviewer packets at
-[`REPORTS/start-here-for-hiring-reviewers.md`](start-here-for-hiring-reviewers.md).
+[`REPORTS/START_HERE.md`](START_HERE.md).
diff --git a/REPORTS/portfolio-impact-summary.md b/REPORTS/portfolio-impact-summary.md
@@ -56,7 +56,7 @@ Three rows pulled from [`by-role-reviewer-guide.md`](by-role-reviewer-guide.md);
 
 ## What To Look For (and Not To Infer)
 
-From [`start-here-for-hiring-reviewers.md`](start-here-for-hiring-reviewers.md):
+From [`START_HERE.md`](START_HERE.md):
 
 **Look for**: clear separation between strict bypass, intent shift, clean ignore, and harness failure; claims that narrow after replication rather than inflate; raw artifacts that preserve commands, summaries, transcripts, and limitations; remediation language aimed at engineering controls.
 

diff --git a/REPRODUCE.md b/REPRODUCE.md
@@ -46,7 +46,7 @@ GATE: PASS - fixture benchmark is internally consistent
 
 ## The reviewer reading path
 
-1. [REPORTS/start-here-for-hiring-reviewers.md](REPORTS/start-here-for-hiring-reviewers.md)
+1. [REPORTS/START_HERE.md](REPORTS/START_HERE.md)
    - the packet-ready 60-second router and role-specific evidence blocks.
 2. [WRITEUPS/2026-05-14-mcp-substrate-vs-policy.md](WRITEUPS/2026-05-14-mcp-substrate-vs-policy.md)
    - methodology and **Addendum B**, the cross-scale correction.

diff --git a/RESEARCH-SUMMARY.md b/RESEARCH-SUMMARY.md
@@ -11,7 +11,7 @@ for every claim tied to raw runs.
 
 ## 60-second reviewer path
 
-Use [`REPORTS/start-here-for-hiring-reviewers.md`](REPORTS/start-here-for-hiring-reviewers.md) as the single entry point. It provides role-specific evidence blocks and the canonical 4-artifact path. The arc below gives the research context behind those artifacts.
+Use [`REPORTS/START_HERE.md`](REPORTS/START_HERE.md) as the single entry point. It provides role-specific evidence blocks and the canonical 4-artifact path. The arc below gives the research context behind those artifacts.
 
 ## The arc
 

diff --git a/docs/reports/hiring-evidence-index.md b/docs/reports/hiring-evidence-index.md
@@ -187,7 +187,7 @@ rg -n "Disclosure Boundary|production vulnerability claim" REPORTS/remediation-c
 
 **Evidence:**
 
-- [`REPORTS/start-here-for-hiring-reviewers.md`](../../REPORTS/start-here-for-hiring-reviewers.md)
+- [`REPORTS/START_HERE.md`](../../REPORTS/START_HERE.md)
 - [`REPRODUCE.md`](../../REPRODUCE.md)
 - [`pipeline/scripts/check-packet-ready.sh`](../../pipeline/scripts/check-packet-ready.sh)
 

diff --git a/docs/reports/hiring-reviewer-map.md b/docs/reports/hiring-reviewer-map.md
@@ -10,7 +10,7 @@ Cayman can run scoped, reproducible AI-agent security experiments; distinguish m
 
 ## 60-second Path
 
-Start from the packet-ready router: [`REPORTS/start-here-for-hiring-reviewers.md`](../../REPORTS/start-here-for-hiring-reviewers.md).
+Start from the packet-ready router: [`REPORTS/START_HERE.md`](../../REPORTS/START_HERE.md).
 
 1. **H10b-G 70B substrate grid:** [`ATTACKS/2026-05-18-h10b-g-70b-substrate-grid-m1-variant-selective.md`](../../ATTACKS/2026-05-18-h10b-g-70b-substrate-grid-m1-variant-selective.md)
    - Proves the 70B substrate effect survives the chat-only control gate and that M1 prompt scaffolding is variant-selective: baseline/v3 held, v7 bypassed.
@@ -57,7 +57,7 @@ For the attack-to-fix version of the same story, read [`REPORTS/remediation-case
 
 ## Role-Specific Evidence Blocks
 
-Use [`REPORTS/start-here-for-hiring-reviewers.md`](../../REPORTS/start-here-for-hiring-reviewers.md) as the source of truth for packet-ready role blocks. Each role has exactly three links: one flagship artifact, one raw-evidence or pre-registration artifact, and one defensive or operational artifact.
+Use [`REPORTS/START_HERE.md`](../../REPORTS/START_HERE.md) as the source of truth for packet-ready role blocks. Each role has exactly three links: one flagship artifact, one raw-evidence or pre-registration artifact, and one defensive or operational artifact.
 
 ## Known limitations and How to Discuss Them
 

diff --git a/pipeline/scripts/check-packet-ready.sh b/pipeline/scripts/check-packet-ready.sh
@@ -18,7 +18,7 @@ packet_files=(
   README.md
   REPRODUCE.md
   RESEARCH-SUMMARY.md
-  REPORTS/start-here-for-hiring-reviewers.md
+  REPORTS/START_HERE.md
   REPORTS/2026-05-17-h10b-g-70b-substrate-findings.md
   REPORTS/remediation-case-study-tool-output-injection.md
   docs/reports/hiring-reviewer-map.md
@@ -55,7 +55,7 @@ import re
 import sys
 from pathlib import Path
 
-path = Path("REPORTS/start-here-for-hiring-reviewers.md")
+path = Path("REPORTS/START_HERE.md")
 text = path.read_text()
 
 expected_roles = {

diff --git a/pipeline/scripts/verify-public.sh b/pipeline/scripts/verify-public.sh
@@ -10,7 +10,7 @@ public_files=(
   RESEARCH-SUMMARY.md
   Makefile
   site/index.html
-  REPORTS/start-here-for-hiring-reviewers.md
+  REPORTS/START_HERE.md
   REPORTS/substrate-vs-policy-assessment.md
   REPORTS/2026-05-17-h10b-g-70b-substrate-findings.md
   REPORTS/remediation-case-study-tool-output-injection.md

diff --git a/site/index.html b/site/index.html
@@ -174,7 +174,7 @@ <h1>Agent product security portfolio</h1>
         mitigation-boundary measurement, and regression testing for agent-powered products.
       </p>
       <nav class="actions" aria-label="Primary portfolio links">
-        <a class="button primary" href="https://github.com/ChunkyTortoise/ai-redteam-notes/blob/main/REPORTS/start-here-for-hiring-reviewers.md">60-second reviewer path</a>
+        <a class="button primary" href="https://github.com/ChunkyTortoise/ai-redteam-notes/blob/main/REPORTS/START_HERE.md">60-second reviewer path</a>
         <a class="button" href="https://github.com/ChunkyTortoise/ai-redteam-notes">Public repository</a>
         <a class="button" href="https://github.com/ChunkyTortoise/ai-redteam-notes#reviewer-path-5-minutes">5-minute path</a>
       </nav>
@@ -185,17 +185,17 @@ <h1>Agent product security portfolio</h1>
         <article class="card">
           <h2>60-second review</h2>
           <p>Start with the completed H10b-G 70B grid, claim boundary, and what not to infer from the lab results.</p>
-          <a href="https://github.com/ChunkyTortoise/ai-redteam-notes/blob/main/REPORTS/start-here-for-hiring-reviewers.md">Open reviewer path</a>
+          <a href="https://github.com/ChunkyTortoise/ai-redteam-notes/blob/main/REPORTS/START_HERE.md">Open reviewer path</a>
         </article>
         <article class="card">
           <h2>Technical deep dive</h2>
           <p>Inspect the MCP substrate study, H10b-G mitigation boundary, DVL ReAct-loop SQLi evidence, raw artifacts, and limitations.</p>
-          <a href="https://github.com/ChunkyTortoise/ai-redteam-notes/blob/main/REPORTS/start-here-for-hiring-reviewers.md">Open reviewer path</a>
+          <a href="https://github.com/ChunkyTortoise/ai-redteam-notes/blob/main/REPORTS/START_HERE.md">Open reviewer path</a>
         </article>
         <article class="card">
           <h2>Application evidence</h2>
           <p>Review exploitability, impact, durable fixes, regression tests, and residual risk.</p>
-          <a href="https://github.com/ChunkyTortoise/ai-redteam-notes/blob/main/REPORTS/start-here-for-hiring-reviewers.md">Open reviewer path</a>
+          <a href="https://github.com/ChunkyTortoise/ai-redteam-notes/blob/main/REPORTS/START_HERE.md">Open reviewer path</a>
         </article>
       </section>