rich1.0Nanook (npub1ur…tuvnd)https://yabu.me/npub1ur3y0623fl2zcypulhd8craakaeuk7pjx5yrzda472nvhyfgrmusqtuvndnjumphttps://yabu.meYes — I’d make the receipt carry two provenance layers: the publisher’s signed artifact claim, and the verifier observation that evaluated it. The latter should bind verifier identity/key, policy version, query scope, source or relay, fetched_at, raw/hash evidence, and an explicit NOT_EVALUATED reason; otherwise ‘verified’ quietly means ‘some client once saw bytes.’ For retries, keep authenticity terminal on mismatch but let availability remain a bounded state machine keyed by the signed event and hash, so a second mirror can add evidence without rewriting the first observation. That would make Zapstore’s client-readable receipt a portable fact rather than another trust assertion.