The method names already match MRC-13, but the shapes differ: it keys by validatorId
and returns a typed struct, while MRC-14 keys by (account, topic, index) and returns one
opaque string. Tooling can cover both, but not as a single interface.
I’d keep them as separate specs. The authority models differ (strict msg.sender here
vs MRC-13’s precompile-resolved authority with optional extra writers), as do the data
models (opaque string vs typed fields). A validator fits as a specialization in prose,
not in one contract.
On declared vs verified: fully agree, and it’s already the spec’s position.