# E77 — withdrawn / unsupported claims (correction 2026-11-16)

This is a correction, not a deletion. The 2026-11-14 E77 artifacts are preserved exactly as published. Four claims in them are **not supported by the evidence they ship** and must not be quoted as results:

| Claim as published | Status | Why |
|---|---|---|
| “80/80 adversarial vectors blocked” | **WITHDRAWN** | The artifact carries `adversarial_vectors_tested: 80` as a constant and **0** scenario records. There is no E77 security lab run behind it. |
| “410 tasks executed and independently verified” | **WITHDRAWN** | No per-task execution rows are in the bundle. The 410 figure cannot be independently recomputed. |
| “1,000,411 durable task records” | **RECLASSIFIED** | Most rows are synthetic filler inserted for a throughput test; they are not 1,000,411 executed tasks. The page said “not executed tasks” in small print but the headline was misleading. |
| “Pinned Ed25519 public key” | **WITHDRAWN** | The E77 signing keys were generated per build (`Ed25519PrivateKey.generate()`); the key was not pinned. |
| “1-hour endurance” | **WITHDRAWN** | The earlier citation pointed at a missing artifact; later evidence corrected it to `BLOCKED / NOT_RUN_IN_THIS_BUILD`. |

## What remains valid

- The E77 code and its 27-check offline verifier are real; the verifier checks internal consistency of the shipped bundle.
- The E77 self-grade was already **C+ (6.58/10)** and **production-ready: NO**.
- The 2026-11-14 audit identified these issues; this file records the public correction.

## How to treat this bundle

Quote E77 only as a **development milestone with withdrawn claims**, never as proof of 80/80 security, 410 verified tasks, one million executed tasks, a pinned key, or a one-hour campaign. The current evidence is Evolution 81.

*Correction recorded by FIRME AI CORPORATION, 2026-11-16. Evidence class: correction of record; no new run was performed.*
