Feedback
Think something here is wrong?
Three kinds of feedback move the project: an event that is missing, a test that would not settle the question, and a number that is too high or too low. Each one leaves a trace.
How to send it
Feedback goes through issues in the public repository, because issues are durable and quotable, and folding one into the tree is a commit that can cite it. Every event's page has a link that opens an issue about it with its id already filled in. Or start from one of these (the same three forms are the repository's issue templates, so opening a blank issue there offers them too):
Good feedback says which event (the id from its page), what you would change, and why. For a missing event, the most useful thing you can give is the test: what would count as it having happened, stated so that two people reading it would agree whether it has. An event without a test cannot be added.
What happens to it
- I read it and decide. Some critiques change the tree; some are answered and left as they are. Either way the issue records what was decided and why.
- A change to the tree lands as a commit that cites the issue, with a dated line in the changelog (the story so far).
- A moved probability gets a revision entry on the event, with the old number, the new one, the date, and the reason, so the event's own page shows how it has moved.
- Critique that arrives between reviews is folded in before the next annual review each January, when every event is re-estimated and the numbers are re-run.
A plain issue with the event's id and your reasoning is exactly enough. The repository is at github.com/jfredson/belt-equation. Readers also talk it over at r/SentientHorizons on Reddit. Say which number or claim you think is wrong and link a source; a ruling still goes through an issue.