haft vs LangChain

Enforces a disciplined 5-mode engineering cycle (Understand → Explore → Choose → Execute → Verify) by requiring AI agents to frame problems before solving them, generate genuinely different solution variants, and compare options under parity constraints. Implements this via MCP tools (haft_problem, haft_solution, haft_decision) that validate reasoning artifacts against a formal specification before allowing progression to implementation.

Unique: Implements a formal specification-driven reasoning cycle with maturity (Unassessed → Shipped) and freshness (Healthy → Stale → At Risk) tracking, enforcing parity in comparisons via a knowledge graph that links decisions to codebase artifacts — unlike generic prompt engineering, this creates falsifiable contracts with evidence decay mechanics

vs alternatives: Differs from Cursor/Claude Code's native reasoning by adding governance layer that prevents decision drift and enforces structured comparison, whereas standard agents optimize for speed-to-code

Exposes Haft's reasoning capabilities as a Model Context Protocol (MCP) server via JSON-RPC transport, providing six specialized tools (haft_problem, haft_solution, haft_decision, haft_evidence, haft_check, haft_search) that AI agents can invoke natively within their execution environment. The server runs as a subprocess managed by the agent's MCP client, maintaining a persistent SQLite state store and knowledge graph indexed to the codebase.

Unique: Implements MCP as the primary delivery surface (not a secondary plugin), with six domain-specific tools designed for the FPF cycle rather than generic function calling — includes codebase-aware search and evidence decay scoring built into the protocol layer

vs alternatives: More specialized than generic MCP servers (e.g., Anthropic's file-system MCP) because tools are designed for reasoning governance, not file I/O; tighter integration with decision lifecycle than REST APIs

Enforces equal rigor in comparing competing solutions by requiring that all variants be evaluated against the same criteria, preventing bias toward preferred solutions. Implements parity checks via the haft_solution and haft_decision tools that validate solution descriptions follow the same structure and depth. Tracks comparison fairness metrics to ensure decisions are based on equivalent evidence.

Unique: Implements structural parity checks that validate all solutions follow the same evaluation template and depth — unlike generic decision frameworks, this prevents strawman alternatives and ensures fair comparison

vs alternatives: More rigorous than informal decision-making because it enforces structural equivalence; differs from decision matrices by focusing on comparison process rather than scoring

Monitors the health of engineering decisions across two axes: maturity (progress from Unassessed to Shipped) and freshness (Healthy → Stale → At Risk based on evidence age and drift detection). Implements R_eff (effective reasoning score) that decays over time as supporting evidence ages, triggering alerts when decisions drift from their original context. Uses SQLite schema with timestamp-based queries to identify stale decisions and prompt re-evaluation.

Unique: Implements a two-axis decision lifecycle model (maturity + freshness) with time-decay scoring (R_eff) that automatically degrades decision confidence — unlike static decision logs, this creates a living system where old decisions are flagged for re-evaluation without manual intervention

vs alternatives: More sophisticated than ADR (Architecture Decision Records) because it tracks decision health over time and flags staleness; differs from code review tools by focusing on decision validity rather than code quality

Builds a knowledge graph that links engineering decisions to codebase artifacts (modules, functions, files) using FPF Spec Search & Indexer. Enables semantic search over past decisions filtered by codebase context, allowing agents to query 'decisions affecting this module' or 'solutions tried for this problem pattern'. Stores graph in SQLite with projections that map decisions to code locations and vice versa.

Unique: Implements a bidirectional knowledge graph (decisions ↔ code artifacts) with FPF Spec Search that understands decision semantics and codebase structure simultaneously — unlike generic code search, this links reasoning to implementation and enables decision-centric queries

vs alternatives: More targeted than full-text search because it understands decision structure and codebase topology; differs from RAG systems by maintaining explicit decision-to-code mappings rather than embedding-based retrieval

Provides a terminal-based autonomous agent (haft agent command) that executes the engineering cycle without human intervention, using a ReAct-style coordinator to move through Understand → Explore → Choose → Execute → Verify phases. The coordinator maintains state in SQLite and can pause at checkpoints for human review. Implements a lemniscate cycle pattern that allows looping back to earlier phases if verification fails.

Unique: Implements a lemniscate cycle (figure-8 loop) that allows backtracking from Verify to earlier phases if verification fails, rather than linear progression — enables iterative refinement without restarting the entire cycle

vs alternatives: More structured than generic ReAct agents because it enforces FPF phases; differs from Devin/Claude Code by running autonomously in terminal without IDE, making it suitable for headless environments

Abstracts LLM provider differences (OpenAI Codex, Anthropic Claude, Google Gemini) behind a unified interface, allowing the same FPF reasoning cycle to work across different models. Routes tool calls and reasoning prompts to the configured provider via a provider adapter pattern, with fallback support for multiple models. Stores provider configuration in project policy files.

Unique: Implements provider abstraction at the reasoning level (not just API calls), allowing the same FPF cycle to work across Claude, Codex, and Gemini with different tool-calling conventions — uses adapter pattern to normalize provider differences

vs alternatives: More flexible than single-provider agents (Claude Code, Cursor) because it supports provider switching; differs from LangChain by focusing on reasoning governance rather than generic LLM chaining

Enforces project-level governance policies via .haft/ directory containing formal specifications (FPF Spec), provider configurations, and decision templates. Policies are versioned and can be checked via haft check command to ensure decisions comply with project standards. Implements a policy-as-code approach where governance rules are stored alongside the project and enforced by the Haft runtime.

Unique: Implements governance as versioned policy files in .haft/ directory (similar to .github/ workflows), making policies auditable and version-controlled alongside code — unlike external governance systems, policies live in the repository

vs alternatives: More integrated than external compliance tools because policies are co-located with code; differs from linters by enforcing reasoning discipline rather than code style

LangChain provides a Chain abstraction that sequences LLM calls, prompt templates, and tool invocations into directed acyclic graphs (DAGs). Chains support sequential execution (SequentialChain), conditional branching (RouterChain), and parallel execution patterns. The framework uses a Runnable interface that standardizes input/output contracts across all chain components, enabling composition via pipe operators and method chaining. This allows developers to build complex multi-step workflows without managing state manually.

Unique: Uses a unified Runnable interface across all components (LLMs, tools, retrievers, parsers) enabling composability via pipe operators, unlike frameworks that require separate orchestration layers for different component types. Supports both sync and async execution with identical code paths.

vs alternatives: More flexible than simple prompt chaining (like OpenAI's function calling alone) because it abstracts orchestration logic, making chains reusable and testable; simpler than full workflow engines (Airflow, Prefect) because it's optimized for LLM-specific patterns rather than general data pipelines.

LangChain's PromptTemplate class provides structured prompt engineering with variable placeholders, automatic validation, and support for few-shot learning patterns. Templates use Jinja2-style syntax for variable substitution and support dynamic example selection via ExampleSelector. The framework includes specialized templates (ChatPromptTemplate for multi-turn conversations, FewShotPromptTemplate for in-context learning) that handle formatting differences across LLM types. This enables prompt reusability, version control, and systematic experimentation without string concatenation.

Unique: Provides first-class abstractions for few-shot learning (FewShotPromptTemplate) with pluggable ExampleSelector strategies, enabling dynamic example selection based on input similarity without requiring developers to implement selection logic. Separates system prompts, conversation history, and user input in ChatPromptTemplate, making multi-turn conversations composable.

vs alternatives: More structured than manual string formatting because it validates variable names and supports semantic example selection; more specialized than generic templating engines (Jinja2) because it understands LLM-specific patterns like chat message roles and few-shot formatting.

LangChain abstracts function calling across LLM providers by converting Python functions or Pydantic models into provider-specific schemas (OpenAI function_call, Anthropic tool_use, etc.). The framework automatically generates schemas, handles argument parsing, and routes calls to the correct provider. Developers define functions once and LangChain handles provider-specific formatting. This enables tool use without learning each provider's function calling API.

Unique: Automatically converts Python functions and Pydantic models into provider-specific function calling schemas (OpenAI, Anthropic, Cohere, etc.) and handles parsing and routing transparently. Developers define tools once and LangChain handles provider-specific formatting and execution.

vs alternatives: More portable than using provider SDKs directly because function definitions are provider-agnostic; more automated than manual schema management because schemas are generated from function signatures.

LangChain supports streaming LLM output at token granularity, enabling real-time user feedback as tokens are generated. The framework provides streaming iterators and async generators that yield tokens as they arrive from the LLM. Streaming is integrated into chains and agents, so developers can stream output from complex workflows without special handling. This enables responsive user experiences where output appears in real-time rather than waiting for full completion.

Unique: Integrates streaming at the framework level so chains and agents can stream output transparently without special handling. Provides both sync and async streaming iterators and handles provider-specific streaming formats uniformly.

vs alternatives: More integrated than provider-specific streaming APIs because streaming works across chains and agents; more responsive than buffering full output because tokens appear in real-time.

LangChain provides async/await support throughout the framework, enabling concurrent execution of LLM calls, chains, and agents. All major components (LLMs, chains, retrievers, agents) have async variants (e.g., arun() alongside run()). The framework uses asyncio for Python and native async/await for Node.js. This enables high-concurrency applications that can handle multiple requests simultaneously without blocking. Async execution is transparent; developers write the same code as sync but use async/await syntax.

Unique: Provides async/await support throughout the framework with parallel async implementations of all major components. Enables transparent concurrent execution without requiring developers to manage thread pools or explicit parallelization.

vs alternatives: More integrated than manual async management because async is built into the framework; more scalable than sync-only implementations because it enables handling multiple concurrent requests.

LangChain abstracts LLM APIs behind a common BaseLanguageModel interface, supporting OpenAI, Anthropic, Cohere, Hugging Face, Ollama, and 20+ other providers. The abstraction handles provider-specific details: token counting, streaming, function calling schemas, and cost tracking. Developers write LLM-agnostic code and swap providers via configuration. The framework includes built-in retry logic, rate limiting, and fallback chains for reliability. This enables portability and cost optimization without rewriting application logic.

Unique: Implements a unified BaseLanguageModel interface that abstracts away provider differences in token counting, streaming protocols, and function calling schemas. Includes built-in retry policies, rate limiting, and cost tracking at the framework level rather than requiring developers to implement these separately for each provider.

vs alternatives: More portable than using provider SDKs directly because swapping providers requires only configuration changes; more comprehensive than simple wrapper libraries because it handles streaming, retries, and cost tracking uniformly across 20+ providers.

LangChain provides a Retriever abstraction that enables RAG by connecting LLMs to external knowledge sources. The framework supports multiple retrieval strategies: vector similarity search (via VectorStore), BM25 keyword search, hybrid search, and custom retrievers. Documents are chunked, embedded, and stored in vector databases (Pinecone, Weaviate, Chroma, FAISS, etc.). The RetrievalQA chain automatically retrieves relevant documents and passes them as context to the LLM. This enables LLMs to answer questions grounded in custom data without fine-tuning.

Unique: Provides a unified Retriever interface that abstracts different retrieval strategies (vector, keyword, hybrid, custom) and integrates seamlessly with LLM chains via RetrievalQA. Includes built-in document loaders for 50+ formats (PDF, HTML, Markdown, code files) and automatic chunking strategies, reducing boilerplate for document ingestion.

vs alternatives: More integrated than building RAG from scratch because document loading, chunking, embedding, and retrieval are unified in one framework; more flexible than specialized RAG platforms (Pinecone, Weaviate) because it supports multiple vector stores and custom retrieval logic.

LangChain's Agent abstraction enables autonomous task execution by combining LLMs with tools (functions, APIs, retrievers). The agent uses an action-observation loop: the LLM decides which tool to call based on the task, executes the tool, observes the result, and repeats until the task is complete. Agents support multiple reasoning strategies: ReAct (reasoning + acting), chain-of-thought, and tool-use patterns. The framework handles tool schema generation, argument parsing, and error recovery. This enables building autonomous systems that can decompose complex tasks without explicit step-by-step instructions.

Unique: Implements a generalized Agent interface that supports multiple reasoning strategies (ReAct, chain-of-thought, tool-use) and automatically handles tool schema generation, argument parsing, and error recovery. The action-observation loop is abstracted, allowing developers to focus on defining tools rather than implementing agent logic.

vs alternatives: More flexible than simple function calling (OpenAI's tool_choice) because it implements multi-step reasoning and tool sequencing; more accessible than building agents from scratch because it handles schema generation, parsing, and error recovery automatically.