[AVAILABLE].
packages/execution-gateway, 25 tests. Wired into the default server unconditionally, see The gateway.Purpose
Independently re-verifies a signed execution authorization and its content hash before releasing execution to aConnector. Implements @parmana/execution-system’s
ExecutionSystem interface.
Install
Key exports
| Export | Stability |
|---|---|
ExecutionGateway | [AVAILABLE]. new ExecutionGateway(options: ExecutionGatewayOptions), .execute(request), .verify(request). |
Connector (interface) | [AVAILABLE]. { connectorId, execute(request, context) } |
HttpConnector | [AVAILABLE]. Forwards { ...transaction, authorization } to ${baseUrl}/execute via POST. A different, older class from @parmana/connector-sdk’s HttpConnector, see that package’s reference page. |
GatewayVerificationResult | [AVAILABLE]. Per-check breakdown: versionSupported, signatureVerified, notExpired, ttlWithinPolicy, businessTransactionHashMatches, nonceUnseen. |
deepFreeze | [AVAILABLE]. Freezes executable content before it reaches a connector, so nothing downstream can mutate what was verified. |
ExecutionGatewayOptions
connector (direct) or executionControl (routes through
credential isolation), not both. The default server uses
executionControl.
ExecutionControlOptions, including deprecated fields
Minimal example
Next
The gateway
The concept this package implements, plus what’s actually wired today.
@parmana/execution-control
What
service and gatewayAuthentication actually are.