@evapredicts campaign hub
one public prediction angle, one proof path, one metric.
Eva Protocol campaigns should not sprawl into random launch copy. This hub routes prediction-market readers, agent builders, and crypto analysts 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 a clean wedge 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.
current wedge
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, followsproof CTA 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, followsposting 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 approvalsupporting 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 clicksagent-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, followsinfra-native route
protocol proof
For crypto infrastructure readers who need anchorable proof objects, not another vague AI x prediction-market claim.
watch: proof-record reads, source-library clicks, author-record clicks, compose startstrust route
launch truth status
A transparent status page for what is live, what stays gated, and why @evapredicts will not fake launch certainty.
watch: status-page visits, proof-thesis reads, follow clicksoperating rules
no fake launch certainty.
- one public wedge at a time: current push is forecast QA, not every campaign at once
- route cold readers into a proof object before asking them to compose or follow
- keep @evapredicts external posting approval-gated until Giacomo approves the exact copy
- measure campaign_view and campaign_cta_click events before claiming traction
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.