backend

backend ¶

Backend configuration models.

Defines configuration for execution backends: Claude CLI, Anthropic API, Recursive Light, and Ollama.

Classes¶

RecursiveLightConfig ¶

Bases: BaseModel

Configuration for Recursive Light HTTP API backend (Phase 3).

Enables TDF-aligned processing through the Recursive Light Framework with dual-LLM confidence scoring and domain activations.

OllamaConfig ¶

Bases: BaseModel

Configuration for Ollama backend.

Enables local model execution via Ollama with MCP tool support. Critical: num_ctx must be >= 32768 for Claude Code tool compatibility.

Example YAML

backend: type: ollama ollama: base_url: "http://localhost:11434" model: "llama3.1:8b" num_ctx: 32768

MCPServerConfig ¶

Bases: BaseModel

Configuration for an MCP server to connect to.

MCP servers provide tools that can be used by the Ollama bridge. Each server is spawned as a subprocess and communicates via stdio.

Example YAML

bridge: mcp_servers: - name: filesystem command: "npx" args: ["-y", "@anthropic/mcp-server-filesystem", "/home/user"]

BridgeConfig ¶

Bases: BaseModel

Configuration for the Marianne-Ollama bridge.

The bridge enables Ollama models to use MCP tools through a proxy service. It provides context optimization and optional hybrid routing to Claude.

Example YAML

bridge: enabled: true mcp_proxy_enabled: true mcp_servers: - name: filesystem command: "npx" args: ["-y", "@anthropic/mcp-server-filesystem", "/home/user"] hybrid_routing_enabled: true complexity_threshold: 0.7

SheetBackendOverride ¶

Bases: BaseModel

Per-sheet backend parameter overrides.

Allows individual sheets to use different models, temperatures, or timeouts without changing the global backend config.

Example YAML::

backend:
  type: anthropic_api
  model: claude-sonnet-4-20250514
  sheet_overrides:
    1:
      model: claude-opus-4-6
      temperature: 0.0
    5:
      timeout_seconds: 600

BackendConfig ¶

Bases: BaseModel

Configuration for the execution backend.

Uses a flat structure with cross-field validation to ensure type-specific fields are only meaningful when the corresponding backend type is selected. The _validate_type_specific_fields validator warns when fields for an unselected backend are set to non-default values.