§5.2 says `verified` is a list, but its example writes a single mapping

[leoafarias]

Summary

§5.2 defines verified as a list, but the spec's own example writes a single mapping.

The rule (SPEC.md L388):

verified: A list of verification events, each with by (an actor) and at (an ISO 8601 datetime).

The example ten lines later (L398):

verified: { by: human:ahormati, at: 2026-06-25T09:00:00Z }

The shipped acme_retail bundle uses the list form:

verified:
  - { by: human:jsmith@acme, at: 2026-07-01T09:00:00Z }

So a consumer that follows the rule rejects the spec's example, and one that follows the example may not expect several events.

Question

Is a single mapping an accepted shorthand for a one-event list?

• If yes: say so in §5.2, for example "a verification event, or a list of verification events", and list the bare mapping as tolerated input in §11.
• If no: change the examples to the list form.

The Dart okf package already treats a bare verified mapping as one event (its conformance matrix, row "§5.2, §11"), so the first option matches existing consumer behavior.