Behaviour for query decomposition in Arcana.Pipeline.

The decomposer breaks complex questions into simpler sub-questions that can be searched independently, improving retrieval for multi-faceted queries.

Built-in Implementations

• Arcana.Pipeline.Decomposer.LLM - Uses your LLM to decompose queries (default)

Implementing a Custom Decomposer

defmodule MyApp.KeywordDecomposer do
  @behaviour Arcana.Pipeline.Decomposer

  @impl true
  def decompose(question, _opts) do
    # Simple keyword-based decomposition
    sub_questions =
      question
      |> String.split(~r/\s+(and|vs|versus|compared to)\s+/i)
      |> Enum.map(&String.trim/1)
      |> Enum.reject(&(&1 == ""))

    {:ok, sub_questions}
  end
end

Using a Custom Decomposer

Pipeline.new(question, repo: repo, llm: llm)
|> Pipeline.decompose(decomposer: MyApp.KeywordDecomposer)
|> Pipeline.search()

Using an Inline Function

Pipeline.decompose(ctx,
  decomposer: fn question, _opts ->
    {:ok, [question]}  # No decomposition
  end
)