A simple contact surface for operators, judges, and contributors.
The public site should make it easy to reach the project for product questions, security issues, partnership discussions, and launch feedback.
Start with the open-source repository
For bugs, feature requests, and technical questions, the GitHub repository is the clearest public trail. That keeps the project transparent and easy to track.
A dedicated inbox for protocol communication
Use hello@tavsin.xyz for launch coordination, press, and non-urgent protocol communication. Replace it with your final operational inbox if needed.
Escalate anything that affects funds or access
Problems that affect custody, policy enforcement, deployment integrity, or freeze behavior should go through the security channel first, not the general support path.
Talk about integrations and launch use cases
If another team wants to use TavSin as the control plane for agent spending, the contact page should route them to the product, technical, and operational owners quickly.