The current routes for account, research content, security, and policy questions.
Public Preview support
Support is currently handled by project maintainers through the routes below. EviMesh does not yet promise a response time, continuous coverage, or a public service-level commitment.
Include the affected route, stable object ID, revision, approximate time, and request ID where available. Never send a password, API token, recovery code, or private signing key.
Account and access
Research content and governance
Security vulnerabilities
Do not publish an exploitable vulnerability in an issue, research node, discussion, or support email thread. Use the private vulnerability reporting channel whenever it is available.
Service status
A dedicated public status service is a pre-Beta requirement but is not represented as active during Public Preview. Confirm an incident through the repository or the support address until that service is published.
Project participation
Project creation and membership are governed workflows. During Public Preview, an interface may not yet be available. Contact support rather than attempting to bypass project roles or write directly to research storage.