Our shared workspace starts in the public repository. Ideas and results stay searchable, and an improvement can become part of the software. You do not need a Discord or Slack account.
Bring one useful piece.
- A question with a deadline and an outcome that someone can verify.
- A public data source with clear usage terms and timestamps.
- A baseline or model comparison another person can reproduce.
- A failed forecast, with the evidence that should have changed it.
The scope includes world events, weather, macroeconomics, science, quantitative pipelines and prediction markets. Market returns and forecasting accuracy require separate evidence; a good probability alone does not establish a profitable trade.
Start with a reproducible example.
Use the forecasting quickstart, then share a result or a specific question through repository issues. Include what you ran, what happened and what you expected. Remove API keys and private information from traces before posting.
The contribution guide covers code and data work. The community code applies to the discussion.
A small chat group can come later if contributors want one. The shared methods and results will remain public and usable outside any chat service.