diff --git a/aips/AIP-22.md b/aips/AIP-22.md
index ce6617f..91b9ab0 100644
--- a/aips/AIP-22.md
+++ b/aips/AIP-22.md
@@ -382,11 +382,14 @@ Two refinements to the text above, recorded rather than silently applied: the Me
   form. Measured on 28001 with the live Falcon-512 precompile: the drill instance recorded a PREPARE and a COMMIT-2
   equivocation, and refused, as calls, the COMMIT-1 pair and a seal given in another round than the one presented, besides the
   refusals of the first record; the real instance verifies the five Falcon-512 seals of the v3 anchor certificate at block
-  6,363,712 over COMMIT-2 of round 0, and refuses each of them under round 1; the runtime code of all four instances equals its
-  source (the new ones today's, the retired ones the source of 2026-09-23). The equivocation vectors of section 9 (eight, two
-  valid) are judged identically by both clients, each refusal for the named reason, including the COMMIT-1 object that the
-  first form recorded on chain. Chain 2800 is not affected: no evidence contract is deployed there and its commit seal is still
-  COMMIT-1 (the round-bound height is not set).
+  6,363,712 over COMMIT-2 of round 0, and refuses each of them under round 1; the runtime code of each contract instance, the two
+  new and the two retired, equals its source (the new ones today's, the retired ones the source of 2026-09-23). The
+  equivocation vectors of section 9 (eight, two
+  valid) are judged identically by the evidence verifiers of both clients, each refusal for the named reason, including the
+  COMMIT-1 object that the first form recorded on chain; these are evidence objects, while on incoming consensus messages the
+  second client on chain 2800 requires the post-quantum seal on commits only (2026-10-16; the other three types from stage 4,
+  whose height is not set there). Chain 2800 is not affected: no evidence contract is deployed there and its commit seal is
+  still COMMIT-1 (the round-bound height is not set).
 
 ## Post-Acceptance Outcome Record