Skip to main content

Module execution

Module execution 

Source
Expand description

Execution cluster.

  • runner: the Runtime graph engine and step orchestrator.
  • graph: graph loading and step lookup helpers.
  • fanout: fanout policy helpers shared across runner and harness.
  • harness: harness fixture replay and assertion engine.
  • orchestrator: canonical entrypoint for local skill, graph, and harness execution.
  • skill_front: the skill front; compiles a skill run into an execution and seals it through the act engine.

Modules§

harness
orchestrator
Canonical local orchestration entrypoint.
runner
The act engine for runx: the single admit -> execute -> seal path every run takes. A standalone skill is a one-act plan and a graph a multi-act plan; both run through this one engine.
skill_front
The skill front: compiles a skill-run request into an execution (cli-tool, agent, or graph runner) and seals it through the shared act engine. This is one of the source-type “fronts” from plans/governed-execution-layer.md; the act engine (execution::runner) owns admit -> execute -> seal.