A host's virtual-source functions (spec/08 §10.5.8, D-194), written as Elixir in the host's own module and tested with ExUnit, as generators are (spec/14 §3.13, D-177):

defmodule MyApp.Sources do
  use Visualize.VirtualSources

  defsource health(rows) do
    cpu = Enum.map(rows, & &1.cpu)
    %{state: if(List.last(cpu) > 90, do: :error, else: :ok)}
  end
end

use Visualize.VirtualSources imports defsource/2 and compiles __virtual_sources__/0, each function's name and its source text, [{name, source}] in definition order. The text is captured when the module compiles, since a release strips the debug information a later reading would need; the builder shows it.

A host's function is trusted — the sandbox's checker does not read it — but it runs through the same bounded runner as a stored one (Visualize.VirtualSource.Sandbox.run/3), so a runaway ends as a fault, not as the board's crash. A virtual source names it with function: :health; the host registers the module with config :visualize, virtual_sources: [MyApp.Sources] or the board's virtual_sources: option.

Examples

iex> defmodule Doc.Sources do
...>   use Visualize.VirtualSources
...>   defsource doubled(rows), do: Enum.map(rows, &(&1 * 2))
...> end
iex> Doc.Sources.doubled([1, 2])
[2, 4]
iex> Doc.Sources.__virtual_sources__()
[doubled: "fn rows -> Enum.map(rows, &(&1 * 2)) end"]
iex> Visualize.VirtualSources.registry([Doc.Sources])
%{doubled: Doc.Sources}