Skip to content

Latest commit

 

History

History
25 lines (20 loc) · 2.17 KB

File metadata and controls

25 lines (20 loc) · 2.17 KB

Contributing to the Trust Commons

Everyone's welcome — researchers, developers, economists, founders, ethicists, skeptics. You don't need to write code to contribute; the highest-value thing you can do is think carefully and push back.

Ways to take part

  • 📄 Share research — post a paper/preprint in Discussions → Research & Papers (title, authors, year, link, and one line on why it matters). Or add it to the research/ reading list via a PR.
  • 🧪 Pose a thought experimentDiscussions → Thought Experiments. "What breaks if…", an incentive trap, an adversarial framing. No code required — just careful thinking.
  • 🔬 Share an experimentDiscussions → Experiments. What you ran, what you found, how to reproduce. Refutations especially welcome.
  • 💡 Propose or critique a designDiscussions → Ideas / RFC. Big protocol changes start here as an RFC before any code.
  • Ask or answerDiscussions → Q&A.
  • 🛠 Code lives in the ecosystem repos (repid-engine, hyperdag-protocol, trustshell) — file issues/PRs there. This repo is for ideas.

Adding a paper to the reading list

Open a PR to research/README.md with, in the right section:

Title — Authors (Year). [link]. One sentence on why it matters here. Primary sources preferred; give a real, checkable citation (no "someone showed that…"). If it shaped how you think about trust, reputation, verification, or incentives in AI, it belongs.

How we work (the ethos)

The way we build is the thesis, so we hold the commons to it:

  • Evidence over claims. A number without its source, corpus size, and confidence interval is an opinion.
  • Honesty over hype. We publish recall and precision, failures and wins.
  • Kindness with candor. Push back on ideas hard; on people, never.
  • Reward truth-seeking. The best contribution overturns a wrong assumption — ours included.

By participating you agree to the Code of Conduct.