Contact Mindburn Labs

Send one safe request.

Use this page for HELM evaluation, architecture review, security disclosure, or technical collaboration. The first message should be safe to route internally.

General email Security email

Start a request

Pick the closest route. You can still adjust it before sending.

Architecture review selected

Name the action, authority, boundary, and evidence need in the message.

If the browser challenge blocks submit, email contact@mindburn.org directly.

Schematic boundary instrument showing request flow through a narrow control gate.

What gets a useful reply

We do not need a deck, a long backgrounder, or private material in the first note. We need the smallest reviewable unit.

  1. Name one action

    Example: an agent should approve a vendor spend request, open a pull request, or write to a production system.

  2. Name the boundary

    Tell us which system, owner, policy, or approval path the action crosses. Do not include credentials or private records.

  3. Name the evidence

    Say what would make the result reviewable: receipt, denial path, approval record, replay, or audit export.

Prefer email?

Use the same safety rule: route context first, sensitive material after a reply.