This repository is the source of the public DualMind Arena documentation at docs.dualmindlab.tech. It contains documentation only, no platform code.

Report security problems in any of these through the channels below:

Only what is live in production is supported. Old commits and preview deployments are not.

Preferred: GitHub private vulnerability reporting. Open a private report at Security → Report a vulnerability. Only the maintainers can see it.

Or by email: write to support@dualmindlab.tech with the subject line Security: <short summary>.

Please include:

• What you found and where (URL, page, endpoint or file)
• Steps to reproduce it
• The impact you expect
• Your name or handle, if you would like credit

Examples of what we want to hear about: documentation that exposes a secret, token or private endpoint, a page that leaks data it should not, or a vulnerability in the Arena or the API.

Please give us a reasonable chance to fix the problem before you discuss it publicly.

• Never commit secrets. API keys, tokens, JWTs and connection strings must never appear in docs, examples or screenshots. Use obvious placeholders such as YOUR_TOKEN.
• Keep internal details out. Admin-only routes, infrastructure details and internal URLs belong in the private developer docs, not in this public repository.
• If a secret is committed by mistake, treat it as leaked: revoke and replace it first, then remove it. Deleting the line is not enough, because it stays in git history.