Skip to main content
Use the @bijection/connectors/stepfunctions entrypoint to declare AWS Step Functions workflows resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Workflow

observed: observed

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: stepfunctions/workflow/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: http. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

stepfunctions.workflow.observed exposes customer-owned Standard executions through native HTTP resources. Explicit generated contracts declare inputs, progress, outputs and named top-level task-token decisions. A release fixes account, region, immutable state-machine version, ASL digest, epoch and retention policy. @bijection/connectors/stepfunctions/adapter is the optional customer Node runtime. It uses official SFN/STS clients and a customer-implemented transactional WorkflowStore. The store owns business authorization, private gate/token custody, one winning decision and an outbox. The bridge retains no execution journal. Private tokens never appear in source rows or Bijection arguments. Starts have deterministic identities and original input envelopes. Callback confirmation requires the exact recorded decision marker in history linked to the original state entry. Native reconciliation reads only. Missing or truncated history remains unconfirmed; token closure is not proof. Cancellation establishes an attributed abort, separately from business cleanup. Runtime status and typed result publication remain separate. Read-only deployment checks prove account, exact ASL and declared callback states; they do not prove write privileges, customer store durability or worker behavior. No aliases, Express, redrive, arbitrary signals or nested callback discovery. Attached work forbids deletion/redrive/ID reuse; retain original endpoints, versions, gates and evidence while native custody needs them. Administrative intervention requires a new epoch and explicit reassociation. Portable protocol tests cover response loss, bridge recreation, competing/stale approvals, missing evidence and execution identity fences. Package fixtures are separate from native/hosted AWS qualification, which remains unestablished. The platform examples/stepfunctions-approval owns the complete customer Lambda/ASL/SQL/CloudFormation example and opt-in deployed suite.

Application helpers

All workflow adapters share one application vocabulary. Object-typed inputs are named command arguments, optional fields included: adding an optional field never wraps or renames existing arguments. Other values travel as input. Bijection-owned members are camelCase (start, requestCancellation); names a contract declares keep their spelling. Serialized routes, capability keys and records keep their snake_case wire names. <adapter>.commands(contract) returns each command’s target and argument validators for commandPolicy from bijection/server, so a policy module types its inputs without importing the schema that installs the resource. <adapter>.policies(contract, "permissions", { reads }) references one exported policy per command name (permissions:decideShipment, …). Names follow the contract; a missing export fails deployment analysis. <adapter>.observations.select(rows, { bound }) interprets acquired execution rows the application read through its own indexed queries. It returns current, missing, conflict (with its reason) or exceeded; it never invents ordering or infers deletion from absence. The application still decides business association, actor permission and acceptable freshness. <adapter>.trace(...) resolves a retained call’s interaction from the generated capabilities and composes it with an authorized observation.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.