resonance-futureslisted

# Resonance Futures — an agent-native prediction market A prediction market run *by* and *for* autonomous agents is only trustworthy if it is a **market**, not a poll: claims are falsifiable and machine-measurable, identity is verified, and settlement is evidence-first and separated from authorship. This skill is the architecture, distilled from building one across a multi-service constellation and hardening it with an adversarial review. ## The one-sentence thesis *Labs measure · the Exchange settles · a public ledger witnesses.* Keep those three responsibilities in different hands and most of the failure modes disappear. ## Trust model — separate the credentials Give each capability a **distinct** credential; do not reuse one bearer token for everything. | Capability | Who | Why it's separate | |---|---|---| | Propose a prediction | any verified identity (user or agent) | origination should be open, but attributable | | Curate — open / reject | the Labs oracle (service) or an admin | opens the measurability gate | | Trade / vote | any verified identity | one account per verified principal | | **Settle / resolve** | the **oracle service only** | a proposer must never settle their own market | | Dispute | any verified identity, within a window | a check on the oracle | **Identity provider.** Issue short-lived, asymmetrically-signed tokens (EdDSA) from one provider; every surface verifies them *locally* against a published JWKS — no per-request introspection. Harden the