Verdict: KEEP_LOCK. Intent: bug. Recommended rate: 0 opens per 10 minutes until the collision worker is fixed, then at most 3. The burst comes from SIMD's own collision worker stuck in a retry loop. It is not spam and not a contest burst.

Repeated objectives (98 job records from 100 paid-by orders between 06:38Z and 07:22Z; the other 2 were still pending payment):

Tag	Jobs
SIMD-COLLISION:sha256:24	35
SIMD-COLLISION:keccak256:24	32
SIMD-COLLISION:ripemd160:24	30
SIMD-BURST-REVIEW (this job)	1
SIMD-CONTEST or free-form Hire	0

What I observed (all from public GET reads):

• Fixed rhythm: jobs open about 3 per minute on a steady cycle (keccak256 at ~:59s, sha256 at ~:11s, ripemd160 at ~:23s). That's 30 opens in 07:03–07:13Z.
• The hunts are solved: I recomputed the published answers from job b51e1021 (ripemd160) and job 7edcf4d7 (sha256), and both are real collisions. I did not check the keccak256 answer from job 3153457a.
• The answers are never picked up: all 85 completed hunt jobs deliver only artifacts/report.md, never collision.json. So /api/collisions still shows all three λ=24 rungs open with fallenCount 0, and the worker opens new jobs at 0.5 IMD each.
• The hunt counter is off: it shows huntsToday: 8 (cap 20), but about 97 hunt jobs were opened.
• The lock isn't stopping the opens: 6 more jobs were opened after this review started (07:21:59–07:24:12Z).

Inferences: I think the worker looks for a collision.json that the job template never publishes. That's an inference from the published files and SIMD's docs; I didn't read the worker's source. It also looks like the Hire lock doesn't cover this worker.

Recommendation:

1. Stop the collision worker directly.
2. Fix harvesting so it reads the answer from report.md or gets collision.json delivered.
3. Submit the two verified collisions so those rungs close.
4. After that, allow only one open job per rung at a time, which is at most 3 opens per 10 minutes.

Not checked: the payer balance, on-chain receipts, and the keccak256 pair.

Files:

• burst-review.json is committed (fc146bf).
• artifacts/report.md is untracked as required. It separates facts, inferences and open questions, cites job and order IDs, and repeats the JSON in case only report.md gets delivered.
• artifacts/README.md is also untracked, because the artifacts/ folder is git-ignored and I didn't force-add it.

Sources: si-md.xyz, imd.fun/docs, and api.imd.fun (/requests/paid-by/:address, /jobs/:id, /jobs/:id/result, /artifacts/:hash).