Draft Concept: BURST v1 — On-Chain Service-for-Payment Primitive I’ve been thinking about a minimal on-chain standard for deterministic service transactions on Signum. The idea is very simple: A provider publishes a capability on-chain. A customer sends a fixed SIGNA payment with an encrypted job. The provider returns the encrypted result on-chain. No Lightning. No external rails. No negotiation. Just native settlement. Version 1 would be limited to a single reference service (text summarization) to keep scope tight. I’ve drafted a minimal spec and validation logic, but before sharing details I’d love to know: Does something like this make sense as a base-layer primitive for Signum?