Support Agent

Copy Markdown View Source

Purpose

The Support Agent is a complete deterministic Jidoka example. Its one scenario, controlled_tool_call, follows this path:

Features

request
  -> input control
  -> scripted model tool request
  -> operation control
  -> action or interrupt
  -> operation result
  -> next scripted model observation
  -> output control
  -> final result

The runtime invariant tests have five deterministic cases:

  • allowed_round_trip verifies tool calling, operation control, and tool observation.
  • interrupted_and_approved verifies operation control, human review, snapshot serialization, and exact resume.
  • not_found_result verifies that a sparse action result reaches the next model input without malformed answer text.
  • input_and_output_policy verifies that sensitive data is blocked before a model call or final result.
  • ui_projection verifies that one completed tool turn becomes stable application view data without process or transcript ownership.

The agent and action are components that these cases use. The cases prove the named boundaries. They do not claim capabilities outside those boundaries.

Read It In This Order

  1. lib/agent.ex - the agent instructions, context, tool, and control.
  2. lib/actions/lookup_order.ex - the application operation.
  3. lib/controls/protect_sensitive_data.ex - input and output policy.
  4. lib/controls/require_order_approval.ex - the operation allow-or-review policy.
  5. lib/agent_view.ex - stable UI state for the support flow.
  6. lib/scenario.ex - deterministic demo wiring.
  7. test/controlled_tool_call_test.exs - application behavior and runtime guarantees.
  8. support_agent.livemd - the complete interactive walkthrough.

The agent, action, and control are application patterns that you can copy. ScriptedLLM, scenario.ex, example.exs, the manifest, and the tests are demo and verification code. In production, configure a real model on the agent instead of passing the scripted :llm capability.

Run It

Run the command demonstration:

mix run examples/support_agent/example.exs

Run the example tests with normal ExUnit output:

mix test examples/support_agent/test/controlled_tool_call_test.exs --trace

Run the scenario through its native ExUnit tag:

mix test --only example:support_agent
mix test --only tool_calling
mix test --only serializable_pause_resume
mix test --only input_controls
mix test --only ui_projection

Open support_agent.livemd for the executable walkthrough. Start the Phoenix application in showcase/ and open /agents/support for the curated UI.

No path uses a real LLM, provider key, network request, or recorded fixture. The local scripted model is in lib/scripted_llm.ex.

The command runner and Livebook set a predictable local snapshot signing secret so the serialization step runs without application setup. Production applications must set their own private :snapshot_signing_secret value or JIDOKA_SNAPSHOT_SIGNING_SECRET environment variable.

Expected Result

The command prints the allowed tool result, stable UI projection, and approved resume result. The tests also prove that sensitive input and output are blocked, and that a blocked operation does not run before approval.

Next Guide

Read Tools And Operations, then Controls and Human In The Loop.