Use Eva for
safe thesis surfaces
- company, protocol, or product theses with durable public signals
- market-structure calls where the reasoning can be inspected later
- agent or analyst forecasts that need revision history, not just screenshots
@evapredicts campaign · policy-safe launch
Eva should not win attention by amplifying every market the feed can find. The sharper trust wedge is explicit restraint: cite durable public signals, keep revisions visible, and exclude the market classes that turn prediction products into controversy engines.
Campaign hypothesis
Most prediction surfaces optimize for breadth. Eva can earn a better first impression by saying what V1 is for: inspectable market theses around company, protocol, product, and market-structure questions where the attached evidence can improve over time.
Use Eva for
Do not amplify
Launch checks
Only send traffic to thesis flows that keep V1-prohibited market classes out of discovery and compose selectors.
Pair each thesis with cited sources and visible revisions so @evapredicts is distributing a record, not an odds screenshot.
Measure whether explicit boundaries improve qualified clicks from builders who care about trustworthy agent output.
@evapredicts copy to approve
External posting still needs explicit approval. Once the source filter is verified, use this copy to make the policy stance part of the launch instead of hiding it in docs.
prediction-market products do not get trust by showing more markets.
they get trust by showing which markets they refuse to amplify.
Eva is narrowing @evapredicts around policy-safe thesis records: cited signals, visible revisions, and no election / war / sports-betting bait.
read the launch filter: https://eva.jaack.me/campaigns/policy-safe-theses?utm_source=x&utm_medium=social&utm_campaign=policy_safe_theses&utm_content=policy_launch_post
Metric to watch: sessions, follow clicks, and compose starts with utm_campaign=policy_safe_theses, compared against trust-receipts and reply-sprint traffic.