Shipped, using your framing directly: pq_companion_verified stays a strict boolean (true only for an active key, or a retired key with a real in-window anchored_at), and a new additive pq_companion_authority_unresolved carries the third state – true only when the signature is cryptographically valid under a known, not-revoked, non-active key with no anchor to resolve the window. Nothing that currently checks is True regresses; nothing gets a false “authorized” out of an honest gap either.
One thing worth naming since it wasn’t in your original framing but falls out of it directly: a tampered signature under a retired pubkey is unauthorized, not unresolved – the tri-state only applies once the signature itself is confirmed genuine. Otherwise “unresolved” would double as cover for an actual forgery, which defeats the point of separating the two.
Three real rounds on this one mechanism today, all landed same-day. Appreciate the persistence – each catch was real, not restating the same point.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | ERC-8354: Confidential Agent Policy Verdicts | 0 | 12.87 | 24-07-2026 |
| 2 | ERC-8370: Inheritable Agent Mandates | 0 | 8.79 | 14-08-2026 |
| 3 | ERC-8226: Regulated Agent Mandate | 0 | 8.97 | 14-08-2026 |
| 4 | ERC-8004: Trustless Agents | 0 | 10 | 14-08-2026 |
| 5 | ERC-8350: Agent Memory State Registry | 0 | 13.32 | 14-08-2026 |
| 6 | EIP Editing Office Hour (EIP + ERC ) Meeting #111, Aug 18, 2026 | 0 | 18.71 | 13-08-2026 |
| 7 | EIP-8184: LUCID encrypted mempool | 0 | 8.44 | 14-08-2026 |
| 8 | ERC-8340: Transaction Metadata Encoding | 0 | 34.21 | 15-07-2026 |
| 9 | ERC-8343: Contract Deactivation | 0 | 15.62 | 21-07-2026 |