[WIP]Oi

Oi means Orchid integration — lightweight glue layer between Orchid workflows and OrchidSymbiont runtimes.

Core concepts

• Workspace — pure data struct holding graph, cluster, interventions. No process, no GenServer. Compiled and dispatched via pure functions.

• Compile + Dispatch — two-phase pipeline:

  1. Oi.compile/1 — topology → static bundles (reusable)
  2. Oi.execute/2 — bind interventions → plan → execute via pluggable executor

• Executor — pluggable task execution strategy. Built-in: Sync (serial), TaskSup (Task.Supervisor), Pool (NimblePool)(in future).

• Session — optional process tree per tenant, wrapping OrchidSymbiont.Runtime for multi-tenant isolation.

Quick start

Define a step

defmodule MyApp.Steps.Upcase do
  use Oi.Step, name: :upcase

  manifest(
    inputs: [:text],
    outputs: [result: :string]
  )

  routine text, _opts do
    text |> String.upcase() |> ok()
  end
end

Build and run

graph =
  Graph.new()
  |> Graph.add_node(%Node{
    id: :up,
    container: MyApp.Steps.Upcase,
    inputs: [:text],
    outputs: [:result]
  })
 
{:ok, compiled} = Oi.compile(graph)
 
{:ok, result} =
  Oi.execute(compiled,
    inputs: %{"up|text" => "hello"}
  )
 
{:ok, res} = Oi.Result.reify(result, "up|result")
# => "HELLO"

Multi-tenant with Session

Oi.Runtime.Session.start("tenant-1")
Oi.Runtime.Session.start("tenant-2")

ws = Oi.Workspace.new("tenant-1", graph)
{:ok, compiled} = Oi.compile(ws)
Oi.execute(compiled,
  executor: Oi.Executor.TaskSup,
  executor_opts: [sup: Oi.Runtime.Session.tasks_tuple("tenant-1")]
)

Symbiont step

defmodule MyApp.Steps.Predict do
  use Oi.Step, name: :predict, symbiont?: true

  manifest(
    inputs: [:features],
    outputs: [prediction: :string],
    models: [:model]
  )

  routine features, models, _opts do
    {:ok, result} = OrchidSymbiont.call(models.model, {:predict, features})
    ok(result)
  end
end

Roadmap

• Scaffold
• Exclipit inputs

License

MIT