Contact
Tell us what boundary, receipt, approval, evidence, investment, or accelerator question you are trying to resolve. We reply selectively and personally.
contact@mindburn.orgGood fit: HELM evaluations, agent systems that need evidence, and investor or accelerator conversations grounded in public proof.
Routing
The best contact notes name the action surface, the tools involved, and what needs to be allowed, denied, escalated, or proven.
You are building agents or tool-calling systems and need an execution boundary.
Good inbound: A concrete integration, repo, workflow, or tool-call path you want to govern.
Filtered out: General AI product pitches without a boundary, receipt, or policy problem.
You want to evaluate Mindburn Labs as an early-stage company: wedge, proof, founder velocity, market timing, and sequencing.
Good inbound: Your firm or program, stage focus, relevant thesis, check-size range if applicable, and what you want to inspect first.
Filtered out: Automated outreach, generic fundraising services, or requests for unsupported traction claims.
You operate a workflow where autonomous actions need approval, denial, or evidence.
Good inbound: A real workflow with specific tools, data classes, approval thresholds, or failure modes.
Filtered out: Broad transformation requests without a concrete action surface.
You need a clear explanation of Mindburn Labs, HELM, or the execution-control category.
Good inbound: Specific questions, deadline, publication, and which public artifact you are referencing.
Filtered out: Requests for unsupported claims, customer lists, or private internal systems.
You want to discuss execution receipts, fail-closed control, or proof for AI actions.
Good inbound: A paper, protocol question, test harness, or research thread tied to governed execution.
Filtered out: Unrelated guest posts or unsourced market reports.