Mindburn Labs
Founding Cohort
APACHE 2.0

最初のAPI呼び出しを数分で

HELMはOpenAI互換プロキシです。1行変更するだけ — base_url — すべてのツール呼び出しが統治、受領、検証されます。

GitHubで見る 標準を読む
ARCHITECTURE

Governed Execution Pipeline

Every AI action flows through three trust boundaries — from proposal to cryptographic receipt. Click any stage to see its invariant and proof output.

External BoundaryAgent sends structured proposals — never raw execution
Kernel — Fail-ClosedEvery proposal is validated, policy-checked, then executed under governance
Proof SurfaceReceipts chain into an offline-verifiable evidence bundle
Hover or click any stage to see its invariant and proof output
ExternalKernel boundaryProof surface
Full architecture docs
INPUT → GOVERNANCE → PROOF

From proposed action to verifiable proof

HELM turns policy inputs into deterministic execution records and offline-verifiable evidence without letting raw tool calls slip around the boundary.

Fail-closed runtimeOffline verificationMCP-native
HELM OSS execution latticeTyped policies, regulations, and permissions flow into the HELM core engine, which executes inside a fail-closed sandbox and emits audit trails, cryptographic proofs, and deterministic action records.POLICY SURFACESPROOF SURFACESTYPED GUARDRAILSPOL-01PoliciesJURISDICTION RULESREG-02RegulationsHUMAN APPROVALSPERM-03PermissionsFAIL-CLOSED KERNELHELMCore execution authorityCPI • PEP • WASI SANDBOX • RECEIPTSAudit TrailsCrypto ProofsCompleted Actions
Inputs arrive as typed constraints, not raw execution.HELM enforces policy before any side-effect is allowed.Outputs exit as receipts and proofs that can be checked offline.
Input Surface

Policies, rules, approvals

Governance starts with typed constraints from policy files, regulatory rules, and human permission checkpoints.

Kernel Boundary

Deterministic execution

The core validates, policy-checks, executes in a sandbox, and fails closed whenever the boundary cannot prove it is safe.

Proof Surface

Artifacts anyone can inspect

Every action leaves an auditable trail: receipts, proof structures, and completed action records that survive outside the runtime.

クイックスタート

5分でデプロイ

HELMはフレームワーク非依存。

1
Clone the repo
$ git clone https://github.com/Mindburn-Labs/helm-oss.git
2
Build the kernel
$ cd helm-oss && go build ./cmd/helm-proxy
3
Start the proxy
$ ./helm-proxy --config config.yaml
4
Point your agent
$ export OPENAI_BASE_URL=http://localhost:8420/v1
Full quickstart guide
MCP ECOSYSTEM

Works with every MCP client

HELM is MCP-native. Any client that speaks the Model Context Protocol can use HELM as its execution authority — no adapters, no shims.

FRAMEWORK COMPATIBILITY

Framework-agnostic by design

Change one URL — every framework gets receipts, policy enforcement, and offline verification.

Full compatibility matrix
OSS ↔ HELM境界

無料のもの。そうでないもの。理由。

OSSはHELMをデフォルトのランタイム境界にします。HELM Enterpriseは大規模でその境界のデフォルトオペレーティングシステムになります。

OPEN SOURCE

OSS Kernel

$0
  • 決定論的提案 → エフェクトパイプライン、フェイルクローズド強制
  • セッションアンカード整合性を持つハッシュリンクレシートDAG
  • アクションごとの設定可能な制限によるガスメータリング実行
  • 暗号化証明付きヒューマンインザループチェックポイント
  • 決定論的JSON出力のL1/L2/L3テストベクトル
ENTERPRISE

HELM Enterprise

Custom
  • 取消可能な資格情報による組織横断信頼委任
  • モデルベンチマーキングとコスト最適化分析
  • Salesforce、SAP、ServiceNowネイティブ統合
  • 集中ポリシー管理によるマルチクラスターデプロイ
  • SOC 2、HIPAA、ISO 27001コンプライアンス自動化
  • シリコンレベルの改ざん証拠付きTEEバインド実行
FAQ

Common questions

今すぐガバナンスを出荷

リポジトリをクローン。適合性スイートを実行。本番にデプロイ。

GitHubで見る 完全なドキュメント