@absolutejs/execution

Crash-safe external effects for AI agents. Execution separates an agent's durable intent from the fallible provider call that fulfills it.

The production path is PostgreSQL-first and reuses AbsoluteJS Queue:

1. store.enqueue(effect) atomically inserts the effect and an outbox event.
2. createExecutionOutboxDispatcher() idempotently moves that event into an @absolutejs/queue store (use @absolutejs/queue-postgres in production).
3. Queue owns scheduling, worker leases, retries, backoff, and dead letters.
4. createExecutionQueueHandler() owns provider idempotency, attempt history, results, unknown-outcome quarantine, and reconciliation.

Redis is not required. A process crash before outbox publish leaves the event claimable; a crash after queue enqueue is harmless because the event id is also the queue idempotency key.

import {
  createExecutionOutboxDispatcher,
  createExecutionQueueHandler,
  createPostgresEffectStore,
  executionJobs,
  executionPostgresSchemaSql,
  executionTenantInventoryPostgresSchemaSql,
} from "@absolutejs/execution";
import { createJobRegistry, createQueueWorker } from "@absolutejs/queue";

await sql.unsafe(executionPostgresSchemaSql());
await sql.unsafe(executionTenantInventoryPostgresSchemaSql());
const effects = createPostgresEffectStore({ client });
const dispatch = createExecutionOutboxDispatcher({
  store: effects,
  queue: queueStore,
});
const registry = createJobRegistry(executionJobs).on(
  "absolutejs.execution.effect",
  createExecutionQueueHandler({
    store: effects,
    handlers: {
      "email.send": {
        execute: (input, { idempotencyKey, signal }) =>
          email.send(input, { idempotencyKey, signal }),
      },
    },
  }),
);
const worker = createQueueWorker({ registry, store: queueStore });

ExecutionSqlClient accepts serialized JSON values as ordinary query parameters. Execution explicitly parses those values through PostgreSQL text before converting them to jsonb, so adapters for Bun SQL, postgres.js, and Neon must pass the provided values through unchanged rather than JSON-encoding them again.

If a provider times out after accepting a request, throw UnknownEffectOutcomeError. Execution will not retry blindly: it quarantines the effect as unknown until an authorized operator, provider query, or provider webhook resolves it through createEffectRecoveryOperations(). Recovery verifies evidence before one atomic status transition, retains an append-only actor/source/evidence record, tenant-fences every case, and permits retry only when evidence confirms the provider did not apply the effect. That transition atomically creates a reconciliation-scoped outbox event so Queue can actually schedule the safe retry after the original event was consumed. Apply effectRecoveryPostgresSchemaSql() before using the PostgreSQL recovery API. Successful effects can be reversed explicitly with compensateEffect() when the handler provides compensate.

Verified provider webhooks and query results can enter recovery through createEffectEvidenceIngestion(). The ingestion boundary retains only normalized, tenant-bound evidence, authorizes that binding before persistence, deduplicates provider delivery IDs, rejects attempts to rebind an existing delivery to another effect, and resumes reconciliation when a provider retries after a host crash. Production hosts should apply effectEvidencePostgresSchemaSql() and use createPostgresEffectEvidenceStore(). Raw webhook payloads and provider credentials do not belong in the evidence store.

Agent Runtime hosts should use createAgentRuntimeEffectExecutor() rather than returning an enqueue result as if it were a completed effect. The bridge stores one tenant/run-fenced effect and asks Runtime to wait until the queue handler records a terminal result. Its authorize callback must return the exact Agency action ID and input digest retained for execution-time lease issuance.

Certified adapters and tenant installations

createEffectAdapterRegistry() is the global fail-closed boundary. Adapter descriptors declare effects, destinations, credential slots, idempotency, reconciliation, compensation, and spend authority. Activation requires a fresh certificate for the exact descriptor digest and host-verified evidence. Webhook reconciliation descriptors must also declare their relative {tenantId} callback template, raw-body signature headers, project secret alias, provider event set, health signal, and replacement or overlap rotation behavior. Query reconciliation descriptors bind their provider query to a declared credential slot and declare outcomes, polling cadence, health freshness, and rotation verification. Registration rejects incomplete or unsafe setup, and effectAdapterWebhookCallbackPath() renders a tenant-safe callback without provider-specific host branching.

createEffectAdapterReconciliationRuntime() scans quarantined effects and claims a durable per-effect lease before any provider query. It authorizes the tenant installation before resolving the exact credential alias, gives query drivers only effect identity metadata rather than the original payload, and passes normalized evidence back through createEffectEvidenceIngestion(). Use createPostgresEffectReconciliationLeaseStore() and createPostgresEffectAdapterHealthStore() after applying effectAdapterReconciliationPostgresSchemaSql(). Health is a bounded upserted signal containing safe codes and counters; raw provider errors and credentials are never retained. Operator-triggered owner flows must call runOnce({ tenantId }); the tenant filter is passed into the durable effect inventory before any lease, installation authorization, credential resolution, or provider query occurs.

Adapters that use a signed webhook as the primary path and a provider query as a fallback declare mode: "webhook-query". Query contracts explicitly state whether a provider reference is required. An execution driver may extract only the bounded { provider, resourceId } reference from a successful provider result; Execution adds the certified adapter ID and never exposes the arbitrary result or original payload to a query driver. If local completion loses its lease, quarantineUnknown() compares the exact attempt number before retaining that reference. A stale worker therefore cannot overwrite a newer attempt or a terminal effect. Fallbacks that require a reference are skipped before credential resolution when an ambiguous provider call never returned one.

createManagedEffectReconciliationScheduler() adds a durable, explicitly default-off control-plane schedule around that runtime. Its store retains the interval, next run, replica lease, bounded counters, and a safe error code. A policy survives restarts, and initialize() never overwrites an operator's existing choice. Use createPostgresEffectReconciliationSchedulerStore() after applying effectReconciliationSchedulerPostgresSchemaSql(). The local polling loop may run on every replica because only the durable due claim can start a reconciliation pass.

createEffectAdapterInstallationRegistry() narrows that certified authority for one tenant. Every installation pins the adapter version and digest, starts disabled, selects an effect and destination subset, maps required adapter credential slots to host-owned secret aliases without storing values, and can bind a per-effect spend ceiling to a mandate. Enabling and every authorization recheck the global adapter, descriptor pin, credential aliases, mandate, destination, effect, tenant, and spend ceiling. Descriptor drift or revoked evidence therefore stops every dependent installation without a rollout.

Production hosts should apply effectAdapterRegistryPostgresSchemaSql() and effectAdapterInstallationsPostgresSchemaSql(), then use the corresponding PostgreSQL stores. The host callbacks remain responsible for resolving secret aliases and validating mandates; raw credentials never enter either registry.

createEffectAdapterExecutionHandler() is the final provider boundary. It accepts an installation envelope, reauthorizes the exact tenant, effect, destination, and spend, first recomputes the canonical authorized input digest, verifies that the runtime driver's identity, version, idempotency, reconciliation, and compensation capabilities match the certified descriptor, and only then resolves the authorized secret aliases. Credential values exist only in the driver context and are never placed in the durable installation record or bridge result. Unknown provider outcomes should be raised as UnknownEffectOutcomeError so the queue quarantines them for reconciliation instead of retrying an ambiguous side effect.

When an authorized envelope carries positive spend, the bridge requires a settlement callback and runs it only after provider success, before returning a successful effect result. The normalized result retains the mandate, currency, and amount needed for a post-compensation refund without retaining credentials. Spending envelopes carry that same mandate and currency explicitly, so an unknown effect retains its original settlement authority even if installation policy changes before provider evidence arrives. The mandate's spend binding is the canonical durable effect-input digest. Confirmed-success webhook, provider-query, and operator reconciliation paths also require settlement before making an unknown effect terminal. Settlement and refund callbacks must be idempotent under the effect identity so a crash at either boundary can be retried safely.