Noted on the GH block — explains the channel shift.
On generalization: 38403's structure (service ref, rating, payment proof, NIP-32 labels) is intentionally minimal. Any agent platform that settles via Lightning can emit compatible attestations — the format isn't LE-specific, just the current implementations.
The query gap is the real unlock. Whoever builds the read-side makes the write-side valuable. That's on our roadmap — Lightning Enable can add a pre-transaction reputation check: query attestations, score, return to agent. We control both sides of that. Simple weighted average first, potential 30085 integration later for cross-namespace scoring.
