A universal coordination layer for real-world operations
pnpm add @signal/sdk-node # reference runtimeReal workflows
A clearer way to show what the platform does: familiar roles, concrete operational problems, and outcomes people can understand quickly.
Payments Platform
Maya Chen
Payments Lead · Payoneer
Problem
The same payment can be processed twice when systems retry a request after a timeout or network failure.
Solution
Each payment request is handled as one durable action. If the same request comes back, the system returns the same result instead of charging again.
Result
One payment, one result, and a clean audit trail that other systems can trust.
Payments Platform
Jordan Bell
Operations Manager · PayPal
Problem
More than one internal system may try to release the same funds, which creates real financial risk.
Solution
The release is recorded once as a verified action. Duplicate attempts become safe retries instead of duplicate transfers.
Result
Funds move once, operations stay calm, and compliance teams can trace every step.
Consumer Platform
Ava Patel
Platform Engineer · Apple
Problem
Account creation usually triggers several follow-up steps, and retries can accidentally create duplicates or partial setups.
Solution
The account is created once, then welcome emails, provisioning, and downstream tasks happen safely around that single source of truth.
Result
Cleaner onboarding, fewer support issues, and a flow that is easy to understand.
Enterprise Software
Elena Rossi
Support Lead · Oracle
Problem
Some APIs blur reading and writing, which makes them hard to trust and risky to retry.
Solution
Read actions are kept read-only. They return status and data without changing anything in the system.
Result
Support gets reliable answers, retries stay harmless, and behavior remains clear.
Payment capture, escrow release, and onboarding all follow the same pattern: define the schema, register the operation, and replay the same request safely.
1import { createSignalRuntime, defineQuery, defineMutation } from "@signal/sdk-node";2import { createMemoryIdempotencyStore } from "@signal/runtime";34const runtime = createSignalRuntime({5 runtimeName: "signal-reference",6 dispatcher,7 idempotencyStore: createMemoryIdempotencyStore(),8});910runtime.registerQuery(11 defineQuery({12 name: "payment.status.v1",13 kind: "query",14 inputSchema: paymentStatusInputSchema,15 resultSchema: paymentStatusResultSchema,16 handler: async (input) => repository.getPayment(input.paymentId),17 })18);The first release includes an in-process binding and an HTTP binding. Both execute the same protocol surface for the real examples in the repository.
Execute the same registry directly in Node.js for local runs
const result = await runtime.query("payment.status.v1", input);Expose queries, mutations, and capability documents over HTTP
POST /signal/query POST /signal/mutation GET /signal/capabilities
Run the Node.js implementation that demonstrates payment capture, escrow release, and onboarding end to end
pnpm --filter @signal/reference-server dev
The HTTP binding carries protocol fields, request context, capability data, and retry metadata.
/signal/query
Execute read-only queries
/signal/mutation
Execute explicit mutations
/signal/capabilities
Discover supported operations
The protocol, runtime, bindings, and docs are kept separate so each layer can be read and implemented on its own.
/packages/core
Envelope, naming, result model, errors, and capability documents
/packages/db
PostgreSQL idempotency store and replay-safe projections
/packages/transport
HTTP binding, in-process execution, and event dispatch
/packages/http
Query and mutation routes plus capability declaration
/packages/security
Extension points for auth and request context
/packages/utils
Helpers used by the runtime and example packages
SPECIFIED
RFCs define names, envelope fields, and semantics
REGISTERED
Operations are added to the runtime with schemas
RUNNING
Queries execute, mutations can emit, events can replay
Start with the quickstart, inspect the envelope, and compare the payment capture, escrow release, and onboarding examples with your own implementation.