nickh007 commited on
Commit
f74a58b
·
verified ·
1 Parent(s): 0852493

card: the command that regenerates these bytes, the file's sha256, and a control a reader can run

Browse files
Files changed (1) hide show
  1. README.md +34 -0
README.md CHANGED
@@ -137,6 +137,40 @@ package ships and the test suite checks. Nothing in this file is hand-written:
137
  A further test asserts that **the committed JSONL is byte-equal to what the package generates**, and
138
  another asserts that **every counterexample in this file replays against its own model**.
139
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
140
  ## Labels, and one deliberate open question
141
 
142
  `KNOWN_COUNTEREXAMPLE` means the violation is published and cited. The single instance is the WPA2
 
137
  A further test asserts that **the committed JSONL is byte-equal to what the package generates**, and
138
  another asserts that **every counterexample in this file replays against its own model**.
139
 
140
+ ## The negative control, which you can run
141
+
142
+ A benchmark whose labels are 13 safe and 2 violated can be gamed by answering "safe" every time.
143
+ That is not a hypothetical here — it is a shipped baseline, so the floor is measurable rather than
144
+ argued:
145
+
146
+ ```bash
147
+ pip install protocol-bench
148
+ protocol-bench run always-safe
149
+ ```
150
+
151
+ recall on violated 0.000
152
+ recall on safe 1.000
153
+ detections claimed 0
154
+ valid counterexamples 0
155
+ TP 0 FP 0 FN 2 TN 13
156
+
157
+ **0.867 plain accuracy, 0.500 balanced accuracy, and nothing detected.** A submission reporting
158
+ 0.867 accuracy has matched a constant. This is why the headline metric is balanced accuracy and why
159
+ a detection is credited only when its counterexample replays.
160
+
161
+ ## Regenerating this file, exactly
162
+
163
+ ```bash
164
+ pip install protocol-bench
165
+ python -c "from protocol_bench.export import export_jsonl; export_jsonl('protocol_bench.jsonl')"
166
+ ```
167
+
168
+ sha256 a147f0e1871ddb80eadef51023223b85890c45bf2b4040769312532284ddb7a3 protocol_bench.jsonl
169
+
170
+ Checked on 2026-09-04: the bytes that command writes are identical to the file published here and
171
+ to the copy in the package repository. If your hash differs, the package version differs — say so
172
+ rather than assuming this file drifted.
173
+
174
  ## Labels, and one deliberate open question
175
 
176
  `KNOWN_COUNTEREXAMPLE` means the violation is published and cited. The single instance is the WPA2