Eva Protocolpublic thesis publishing
Start thesis
Thesis loopBuild one public argument from markets, facts, and revisions
Run campaign

@evapredicts campaign hub

one protocol-proof angle, one proof path, one metric.

Eva Protocol campaigns should not sprawl into random launch copy. This hub routes prediction-market readers, agent builders, crypto analysts, and verifier-minded operators into the clearest live wedge, then watches whether they inspect the proof record, start a thesis, or follow @evapredicts.

Campaign hypothesis

campaign choice should be judged by proof-path intent, not impressions.

The best growth signal today is not a bigger promise. It is whether high-intent readers click from protocol proof into the proof thesis, source library, author record, compose flow, or @evapredicts follow path. If a route cannot move one of those behaviors, it should not be the public push.

active routes

send each audience to the sharpest next step.

Start thesis

current wedge

protocol proof

The infra-native route for public predictions that need cited signals, visible revisions, author identity, and anchorable proof objects before bigger claims.

watch: proof-record reads, source-library clicks, author-record clicks, compose starts, follows

supporting route

forecast provenance

For builders who need every AI or market forecast to carry an author trail, source memory, change trigger, and runtime proof.

watch: author-record clicks, agent-manifest opens, proof-record reads, market-context clicks, compose starts, follows

supporting route

verifier adoption

For builders who need forecasts to become verifiable artifacts: claim boundary, source fit, break condition, author trail, and visible revisions.

watch: proof-record reads, market-signal clicks, author-record clicks, agent-manifest opens, compose starts, follows

supporting route

forecast trust loop

For skeptical builders who need one repeatable behavior: source the claim, state the break condition, revise visibly, and keep the receipt.

watch: trust-loop visits, proof-record reads, market-signal clicks, compose starts, author-record clicks, follows

supporting route

forecast QA checklist

For AI forecast and market-thesis builders who need source fit, break conditions, revision triggers, and author trail before amplification.

watch: checklist opens, proof-record reads, market-signal clicks, compose starts, author-record clicks, follows

posting approval blocked

prediction memory

For prediction-market-native readers: markets price the moment, but Eva keeps the thesis, sources, revisions, and author trail inspectable.

watch: prediction-memory sessions, proof-thesis reads, compose starts, follows after approval

supporting route

source quality sprint

For builders who care less about louder calls and more about whether the cited signal actually supports the thesis.

watch: source-library clicks, proof-thesis reads, compose starts, follow clicks

agent-builder route

AI forecast receipts

For anyone automating forecasts: the output needs source fit, revision triggers, and author/runtime trails before distribution.

watch: receipt-page visits, market-signal clicks, compose starts, follows

new agent-builder route

agent forecast interface

For builders shipping forecast agents: read before writing, prepare before publishing, and give users receipts instead of answer-shaped vibes.

watch: agent-manifest opens, MCP quickstart clicks, proof-record reads, compose starts

launch-readiness route

launch truth status

For readers who need the live/gated status before they trust the broader @evapredicts launch narrative.

watch: status-page visits, proof-thesis reads, policy-gate clicks, follow clicks

operating rules

no fake launch certainty.

Metric to watch: sessions with utm_campaign=campaign_hub, route clicks by utm_content, proof-record reads, compose starts, and @evapredicts profile clicks. Do not claim traction until measured data supports it.