/**
 * Business-pod MCP tools — ADR-164 Phase 2 + Phase 3.
 *
 * Phase 2 surfaces pod-template validation (`business_pod_validate`).
 * Phase 3 adds the domain-affinity routing decision (`business_pod_route_backend`)
 * so any caller (agent, /loop driver, CI workflow) can ask "which backend
 * should @metaharness/router prefer for this pod?" without re-implementing
 * the §3.4 rules. The decision is structural and deterministic — no learned
 * weights, no schedule, just (preferLocalExecution, budgetUsdMonthly).
 *
 * Both tools accept either a pod template *object* or a string *path* to a
 * JSON file. The path form is provided so /loop drivers can avoid loading
 * the template themselves; the object form is for callers that already have
 * the validated template in hand.
 *
 * @module @claude-flow/cli/mcp-tools/business-pod
 */
import type { MCPTool } from './types.js';
export declare const businessPodTools: MCPTool[];
//# sourceMappingURL=business-pod-tools.d.ts.map