diff --git a/AERE-CERTORA-FORMAL-VERIFICATION.md b/AERE-CERTORA-FORMAL-VERIFICATION.md
index 9a75192..324fab5 100644
--- a/AERE-CERTORA-FORMAL-VERIFICATION.md
+++ b/AERE-CERTORA-FORMAL-VERIFICATION.md
@@ -1,5 +1,7 @@
 # Spec 21: Certora formal-verification specifications for Aere Network's safety-critical contracts
 
+> **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it still is: each block is committed with classical ECDSA seals. It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 every QBFT consensus message must carry a valid Falcon-512 seal of its author. (Note applied to this document on 2026-09-27.)
+
 > **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 anchor blocks (every 32nd block, on every one since block 13,889,296) also carry, under the block hash, a certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md.
 
 Status date: 2026-07-19. Author: Aere Network engineering (self-authored CVL).
diff --git a/AERE-ENGINEERING-SECURITY-SPEC.md b/AERE-ENGINEERING-SECURITY-SPEC.md
index 11ad7ef..6882abc 100644
--- a/AERE-ENGINEERING-SECURITY-SPEC.md
+++ b/AERE-ENGINEERING-SECURITY-SPEC.md
@@ -1,5 +1,7 @@
 # Aere Network Engineering and Security Specification
 
+> **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it still is: each block is committed with classical ECDSA seals. It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 every QBFT consensus message must carry a valid Falcon-512 seal of its author. (Note applied to this document on 2026-09-27.)
+
 > **Note added 2026-09-24.** Validator-set figures in this document (N=7 with f=2 and a commit quorum of 5 of 7, or N=9 with a quorum of 6) describe the set on the date they were written. Since 2026-09-11 chain 2800 has ten validators (f=3, commit quorum 7 of 10), all still operated by the Foundation, one of them running the second, Nethermind-derived client. Since 2026-09-04 the anchor certificate carries Falcon-512 and SLH-DSA-SHA2-128s seals, at least six valid seals for each scheme, and since block 17,225,968 (2026-09-05) there is one anchor every 128 blocks. The live set and its quorum are at https://aere.network/docs/network/consensus.
 
 > **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 anchor blocks (every 32nd block, on every one since block 13,889,296) also carry, under the block hash, a certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md.
diff --git a/AERE-ERC7683-DESTINATION-SUMMARY.md b/AERE-ERC7683-DESTINATION-SUMMARY.md
index 75c0404..5d5cd7f 100644
--- a/AERE-ERC7683-DESTINATION-SUMMARY.md
+++ b/AERE-ERC7683-DESTINATION-SUMMARY.md
@@ -1,5 +1,7 @@
 # Spec 8 - ERC-7683 Destination Settler for Aere Network
 
+> **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it still is: each block is committed with classical ECDSA seals. It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 every QBFT consensus message must carry a valid Falcon-512 seal of its author. (Note applied to this document on 2026-09-27.)
+
 > **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 anchor blocks (every 32nd block, on every one since block 13,889,296) also carry, under the block hash, a certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md.
 
 ## What was built (all new files, deployed origin contracts untouched)
diff --git a/AERE-FORMAL-BROADEN-REPORT.md b/AERE-FORMAL-BROADEN-REPORT.md
index e3f399d..bd8f0f1 100644
--- a/AERE-FORMAL-BROADEN-REPORT.md
+++ b/AERE-FORMAL-BROADEN-REPORT.md
@@ -1,5 +1,7 @@
 # Formal-verification broadening: new contract SMT models + canonical runner consolidation
 
+> **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it still is: each block is committed with classical ECDSA seals. It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 every QBFT consensus message must carry a valid Falcon-512 seal of its author. (Note applied to this document on 2026-09-27.)
+
 > **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 anchor blocks (every 32nd block, on every one since block 13,889,296) also carry, under the block hash, a certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md.
 
 Date: 2026-07-19. Tooling: Python 3.14.4, z3 4.16.0 (real z3 verdicts, no fabricated greens).
diff --git a/AERE-POST-QUANTUM-GOVERNANCE.md b/AERE-POST-QUANTUM-GOVERNANCE.md
index 1f35700..e7f669d 100644
--- a/AERE-POST-QUANTUM-GOVERNANCE.md
+++ b/AERE-POST-QUANTUM-GOVERNANCE.md
@@ -1,5 +1,7 @@
 # Spec 29: Post-Quantum Governance
 
+> **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it still is: each block is committed with classical ECDSA seals. It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 every QBFT consensus message must carry a valid Falcon-512 seal of its author. (Note applied to this document on 2026-09-27.)
+
 > **Note added 2026-09-24.** Validator-set figures in this document (N=7 with f=2 and a commit quorum of 5 of 7, or N=9 with a quorum of 6) describe the set on the date they were written. Since 2026-09-11 chain 2800 has ten validators (f=3, commit quorum 7 of 10), all still operated by the Foundation, one of them running the second, Nethermind-derived client. Since 2026-09-04 the anchor certificate carries Falcon-512 and SLH-DSA-SHA2-128s seals, at least six valid seals for each scheme, and since block 17,225,968 (2026-09-05) there is one anchor every 128 blocks. The live set and its quorum are at https://aere.network/docs/network/consensus.
 
 > **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 anchor blocks (every 32nd block, on every one since block 13,889,296) also carry, under the block hash, a certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md.
diff --git a/AERE-PQ-SCREEN-SUMMARY.md b/AERE-PQ-SCREEN-SUMMARY.md
index 232a5c6..2e6a5e8 100644
--- a/AERE-PQ-SCREEN-SUMMARY.md
+++ b/AERE-PQ-SCREEN-SUMMARY.md
@@ -1,5 +1,7 @@
 # Spec 7: AerePQ-Screen (post-quantum compliance passport) - SUMMARY
 
+> **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it still is: each block is committed with classical ECDSA seals. It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 every QBFT consensus message must carry a valid Falcon-512 seal of its author. (Note applied to this document on 2026-09-27.)
+
 > **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 anchor blocks (every 32nd block, on every one since block 13,889,296) also carry, under the block hash, a certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md.
 
 ## What was built
diff --git a/AERE-PQ-SCREEN.md b/AERE-PQ-SCREEN.md
index 613150d..0af5ffc 100644
--- a/AERE-PQ-SCREEN.md
+++ b/AERE-PQ-SCREEN.md
@@ -1,5 +1,7 @@
 # AerePQ-Screen: an institution-grade post-quantum compliance passport
 
+> **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it still is: each block is committed with classical ECDSA seals. It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 every QBFT consensus message must carry a valid Falcon-512 seal of its author. (Note applied to this document on 2026-09-27.)
+
 > **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 anchor blocks (every 32nd block, on every one since block 13,889,296) also carry, under the block hash, a certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md.
 
 AerePQ-Screen upgrades Aere Network's compliance stack so it interoperates with the identity
diff --git a/AERE-QUANTUM-SAFE-NETWORKING.md b/AERE-QUANTUM-SAFE-NETWORKING.md
index d404b1f..75bf5d2 100644
--- a/AERE-QUANTUM-SAFE-NETWORKING.md
+++ b/AERE-QUANTUM-SAFE-NETWORKING.md
@@ -1,5 +1,7 @@
 # Aere Network Quantum-Safe Networking (Transport Layer)
 
+> **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it still is: each block is committed with classical ECDSA seals. It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 every QBFT consensus message must carry a valid Falcon-512 seal of its author. (Note applied to this document on 2026-09-27.)
+
 > **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 anchor blocks (every 32nd block, on every one since block 13,889,296) also carry, under the block hash, a certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md.
 
 **Spec #30, Wave 1. Design document. Status: NOT LIVE.**
diff --git a/AIP-PQ-TX-2026-07-18.md b/AIP-PQ-TX-2026-07-18.md
index 36710c6..cb3c211 100644
--- a/AIP-PQ-TX-2026-07-18.md
+++ b/AIP-PQ-TX-2026-07-18.md
@@ -1,5 +1,7 @@
 # AIP-8: Post-Quantum-Authorized Transaction Envelope (EIP-2718 Type 0x2A)
 
+> **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it still is: each block is committed with classical ECDSA seals. It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 every QBFT consensus message must carry a valid Falcon-512 seal of its author. (Note applied to this document on 2026-09-27.)
+
 > **Note added 2026-08-19.** Statements in this document that consensus on chain 2800 is (or remains) classical secp256k1 ECDSA QBFT were written before the post-quantum header anchor went live, and remain true for block-by-block finality. Since block 13,014,000 anchor blocks (every 32nd block, on every one since block 13,889,296) also carry, under the block hash, a certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with fewer than three valid seals (f+1 of nine; eight or nine are carried in practice). That is a post-quantum checkpoint about every 16 seconds, not a per-block quorum: the claim published on 2026-08-15 that from block 14,050,000 no block finalizes without a post-quantum quorum was wrong (the per-block rule armed at that height is retired in the shipped code in favour of the anchor rules) and was withdrawn on 2026-08-19. Details: https://aere.network/quantum.html and the aere-node repository, anchor/README.md.
 
 ## Preamble