Ex4pmEngine.Reactors.WasmCapabilitiesReactor (ex4pm v26.9.9)

Copy Markdown View Source

Triggers all 19 real wasm4pm-ex4pm-bindings process-intelligence algorithms as Reactor steps against ONE shared, real Wasmex instance -- the "wasm4pm capabilities triggered by reactors" requirement.

Every :run_<algo> step is independent of every other :run_<algo> step (each only depends on :boot_wasm), so Reactor schedules them concurrently on its own, per this codebase's existing convention (docs/REACTOR_INFORMATION_PLANE.md: independent observations are scheduled concurrently by Reactor rather than with manual concurrency).

Inputs

  • :artifact_path -- path to the compiled wasm4pm_ex4pm_bindings.wasm.
  • :requests -- a map of %{<algorithm_id> => request_map}. An algorithm with no matching key is reported as :unsupported in the final results rather than crashing the whole run.

Output (:final)

%{results: %{<algorithm_id> => %{standing:, value:/reason:, ...}}, standing: :alive | :partial_alive | :blocked | :build_broken | :unsupported} -- standing is the real fold (Ex4pm.Standing.min/2, the same ALIVE > PARTIAL_ALIVE > BLOCKED > BUILD_BROKEN > UNSUPPORTED/UNKNOWN lattice apps/ex4pm_qualification's Crown/Verifier already use) across every algorithm -- never a free-text verdict.