proof.anchor-iota@1 + async worker + DA-locator/verify-link

[iret77]

proof.anchor-iota@1 (productive) + async anchor worker + DA-locator/verify-link. The DLT seam switched live, plus the data-availability surface (R9) that makes external verification real — a chain hash alone is not enough if the off-chain object can't be retrieved (Codex C4).

Verification (research.md, A3/F3/F4): the IOTA-Rebased profile is confirmed (ANP §13.2; IOTA Identity ships ML-DSA/SLH-DSA off-chain), but the first-party tooling is pre-GA (Identity Beta, Gas Station pre-1.0, Notarization/Hierarchies Alpha → R19). Consider binding the anchor primitive to IOTA Notarization (Locked/Dynamic) and trust-list resolution to Hierarchies instead of rolling our own anchor objects.

Scope

• IOTA-Rebased profile: anchor(hash, meta) / setStatus / confirmationState (ANP §6.2, §13.2)
• Async anchor worker (R14): retry, idempotency (duplicate anchor), finality timeout, dead-letter, metrics, user-visible degraded state
• DA-locator + public retrieval/verify-link surface (R9): what the link exposes, authorization, redaction, locator behavior, semantics for an unavailable object (void-on-unavailability)
• Ledger-timestamp precedence + skew handling (R18)

Done

A hash is anchored to the real chain · confirmation trickles in · an object is verifiable via verify-link independently of omadia.

ANP backflow

attest schema (together with epic #7).

Blocked by: #4 (objects); Stage A — anchor profile ↔ DID method alignment (#1).
Refs: plan.md §4.1, §5.2, R5/R9/R14/R18/R19.