Agents that read like a map, not a magic trick.

An agent is a supervised system, not a prompt. Spectre gives it one owner per piece of state, explicit messages at every boundary, and recovery planned from the start — the way OTP treats everything else.

cat POLICY.md

Anything protected crosses one boundary:

• - models and routes may propose work
• - protected work must pass a deterministic policy
• - approval changes state but does not execute the work
• - execution happens only through an explicit host call
• - every terminal outcome is returned as data

A Spectre agent should read like a map, not a magic trick.

// The whole agent is one module: the model, the router, a protected action, and the policy guarding it.

defmodule MyApp.SupportAgent do
  use Spectre.Agent

  model(MyApp.LLM, purpose: :smart)
  router(via: [:regex, :embedding, :llm_classifier])

  actions MyApp.SupportActions do
    protect(:delete_account, with: :delete_account_confirmation)
  end

  policy :delete_account_confirmation do
    request(:confirm_delete_account)
    accept(:confirmed_delete, regex: ~r/^yes, delete it$/i)
    reject(:cancel_delete, regex: ~r/^(no|cancel)$/i)
    attempts(3, then: :cancel_pending)
  end

  interrupt :HELP, regex: ~r/^(help|menu)$/i do
    reply(:help)
  end
end