Binding first, judgment second — agreed. One simplification at this seam: if the structured intent is at function-argument level, canonical ABI encoding is deterministic, so binding is a pure recomputation (encodeFunctionData(intent) must byte-match the calldata) — a binding mismatch is then a distinct failure class from a policy denial, and the drift you describe survives only above that level, where the judgment belongs.
Since the validate_action interface is tooling rather than the ERC itself, I’ll move that iteration to the tctc-mcp repo — I’ll open an issue with the draft tool contract (schema, failure classes, mandated ordering) and link it from here, so this thread stays focused on the standard.
What this exchange does contribute to ERC-7303 itself: the layering should be stated in the spec’s Security Considerations — role gating is class-level by design; instance-level soundness (amounts, staleness, injected-but-in-role instructions) belongs to a composing pre-action/policy layer, not to the role gate. I’ll include that in the spec-update proposal I’m about to post in this thread.
Issue the tool contract: validate_action (added on Jul 10)
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | ERC-8335: Account-Level Transfer With Authorization | 0 | 7 | 10-07-2026 |
| 2 | EIP-7730: Proposal for a clear signing standard format for wallets | 0 | 7 | 08-07-2026 |
| 3 | ERC-8313: Protocol Interaction Manifest | 0 | 7 | 08-07-2026 |
| 4 | EIP-7906: Transaction Assertions via State Diff Opcode | 0 | 7 | 09-07-2026 |
| 5 | Add ERC 8217: Agent NFT Identity Bindings | 7 | 8 | 08-07-2026 |
| 6 | ERC-8240: Trust Infrastructure for Agents and Assets | 0 | 5 | 08-07-2026 |
| 7 | EIP-7906: Transaction Assertions via State Diff Opcode | 0 | 3 | 08-07-2026 |
| 8 | ERC-8004: Trustless Agents | 0 | 5 | 10-07-2026 |
| 9 | RPC Standards # 30, July 13, 2026, | 0 | 5 | 10-07-2026 |
| 10 | ERC-8301: AI Agent Execution | 0 | 5 | 10-07-2026 |