Contact

Contact the Research Program

We use topic-specific email aliases so your message reaches the right queue. Please pick the route that best matches your inquiry.

Participation does not imply endorsement. Contact, critique, review, support, or collaboration should be understood as engagement under scrutiny, not as agreement with the theory or its conclusions. See Independence, Scope & Scrutiny for the program’s public-accountability stance.

For public questions, critique, and review offers, use Public Discussions first. For correction, prior-art, claim-boundary, formalization, or publication-errata routing, use Corrections. Email is for private, institutional, media, sensitive, support, or non-public context.

Before contacting us

For orientation questions, first try AI-Assisted Discovery or Start Here.

For technical inspection, first consult How to Verify and Assessment Protocols.

Use public GitHub Discussions when your question, critique, or correction can help other readers.

Use email when the matter is private, institutional, media-related, sensitive, or support-related.

Use GitHub Issues when you are reporting a concrete defect.

Use Pull Requests when you are proposing a concrete change.

Media Inquiry

For journalists, editors, podcast hosts, and media professionals covering science, mathematics, publishing, or technology.

Email: [email protected]

Technical Inquiry

For researchers, mathematicians, physicists, biologists, philosophers, and formal methods specialists with domain-specific questions about the theory, formalization, or specific claims.

Email: [email protected] - subject line: “Technical Inquiry”

Institutional & Collaboration

For universities, research institutions, funding bodies, publishers, and organizations exploring collaboration, evaluation, or institutional engagement.

Email: [email protected]

Reader Feedback

Responses to specific books, results, or registry entries, including critiques, suggestions, and reader reactions.

Email: [email protected]

Corrections & Errata

Factual errors, computational mistakes, scope-label issues, broken proofs, or suggested corrections to published claims.

Email: [email protected]

Structured Review / Technical Inspection

For reviewers evaluating a bounded part of the program, institutional review committees, domain specialists, and technical inspection reports.

Email: [email protected]

General Contact

First-time readers, warm introductions, and anything that does not fit the routes above.

Email: [email protected]

Founders

Direct line to Thor and Anna-Sophie for high-signal, low-volume inquiries.

Email: [email protected]

Legal & Privacy

Data-protection requests, DMCA notices, and formal legal correspondence.

Email: [email protected] - see Impressum and Datenschutz

Before You Write

For technical, review, or correction messages, the most helpful note contains:

• the exact page, result, registry ID, theorem, prediction, or publication artifact;
• the issue you see;
• why it matters;
• any references, reproduction steps, or suggested corrections.

We aim to respond within one week. Complex technical inquiries may take longer. We read every message.