Foresight

Transparency queue

Every proposal, on the record.

Anyone can propose a market via the Foresight MCP foresight_propose_market. Every proposal lands here for human review against the Iron-Rule-0 verifiable-criterion bar. Decisions are public — what was approved, what was rejected, and why.

0pending
0decided
0total

Empty queue

Zero proposals yet.

Be the first. Install the MCP server and call foresight_propose_market with a question your data sources can verify.

$ npm install -g foresight-mcp

How proposals get approved

  1. Anyone with an MCP-aware agent calls foresight_propose_market with question + criterion + sources + closes-at.
  2. The MCP server applies Iron-Rule-0 guards at the protocol surface — distress/assassination markets refused, criteria without a temporal anchor refused, past close-dates refused.
  3. Surviving proposals land in this queue. A moderator checks the criterion against the named sources — can a third party actually verify the resolution from the listed sources alone?
  4. Decisions are written back to the proposal row with reviewer + reasoning. Public log here so reviewers stay accountable.

Phase 1 — proposal actions (approve/reject) require a moderator account. Auth flow lands with the wallet integration in Phase 2. The read surface is public from day one.