Skip to main content
[AVAILABLE]. packages/execution-system. Note DefaultExecutionSystem’s real scope below, it is a placeholder, not a verified boundary.

Purpose

Defines the one interface RuntimeFactory.create() needs to actually release an execution: ExecutionSystem. DefaultExecutionSystem, HttpExecutionSystem, and @parmana/execution-gateway’s ExecutionGateway are three different implementations of this exact interface, interchangeable without touching RuntimeEngine or RuntimePipeline.

Install

Not published to npm. This is an internal package of this repository, used from a clone of it: npm ci at the repository root links every workspace package. The packages published to npm are @parmana/sdk, @parmana/connector-sdk and @parmana/sign.

Key exports

DefaultExecutionSystem is not a smaller version of the gateway, it is a stand-in that does nothing. If you see it in a tutorial’s source, that tutorial is deliberately demonstrating the Runtime, Policy Engine, or trust record shape in isolation, not the verified end-to-end pipeline. The default packages/api server does not use DefaultExecutionSystem, it always constructs a real ExecutionGateway, see The gateway.

Minimal example

For the real, verified boundary, see @parmana/execution-gateway.

Next

The gateway

The real ExecutionSystem implementation the default server actually uses.

@parmana/runtime

Where this interface is consumed.