Back to overview

Execution / Runtime

The execution layer that does not forget

Technical name: Shuttle

Workflow execution and operational process motion.

Shuttle turns ordered work into real execution instead of leaving it as good intention.

From workflow engineering to operator delivery

Status Available now README sync 22 May 2026

Why start here?

Building workflows is fast. Later, validation, live operations, upgrade safety, and dependable delivery break down. That is where automation turns into risk.

jhf-shuttle covers the full path: find workflows, understand them, build them, validate them, run them live against n8n, surface upgrade impact, and deliver agents durably. Not as a one-off tool, but as an operator surface built for real responsibility.

When do I need this?

Shuttle becomes valuable once workflows must not only be built, but run responsibly.

  • when workflows must be operated, not just built
  • when failure patterns must be understood instead of guessed
  • when agents must work together robustly
  • when n8n changes must be introduced in a controlled, upgrade-aware way
  • when best-effort delivery is no longer acceptable

What role it plays here

jhf-shuttle brings four things together in one product picture: a workflow engineering core, a live operator surface, a durable messaging layer, and upgrade-aware operations.

From workflow design to operator-grade delivery.

Workflow execution and operational process motion.

What the module actually does

Not as a loose feature list, but as a hard operating path from design to recovery.

At the core

Discover and design workflows. Shuttle searches templates, reads node capabilities, and helps build new flows instead of starting from empty JSON.

Validate and repair before deploy. Structure, expressions, risky patterns, and deprecated nodes become visible before they turn into live problems.

Operate live n8n with evidence. Health, workflow state, executions, webhooks, and real error messages stay readable. Not guessed. Read.

Surface upgrade impact before rollout. Version gaps, catalog freshness, and workflow impact become visible before change so rollout does not happen blind.

Deliver agents durably. In On-Prem Messaging Mode, best effort becomes a durable mailbox with NATS JetStream, recovery, and ordered delivery per session.

Enforce control under pressure. Flow control, policy enforcement, probe separation, and restart recovery keep operations stable when load and failure arrive together.

What role it plays in the stack

In the Helpifyr picture, Shuttle is the operational automation and delivery surface. Not business truth. Not central portfolio control. Not a companion-only function.

operational automation and delivery surface for the portfolio

works with Fabric, Warp, and Bobbin in the core bundle

brings Mission Control and upgrade intelligence visibly into operations

stays clearly separate from Spindle as business truth

stays clearly separate from Beam as the companion outside runtime

What this looks like in practice

Shuttle has two clean modes. You can start with the core and go deeper once operations and delivery demand it.

01

Discover and design workflows

Shuttle searches templates, reads node capabilities, and helps build new flows instead of starting from empty JSON.

02

Validate and repair before deploy

Structure, expressions, risky patterns, and deprecated nodes become visible before they turn into live problems.

03

Operate live n8n with evidence

Health, workflow state, executions, webhooks, and real error messages stay readable. Not guessed. Read.

04

Surface upgrade impact before rollout

Version gaps, catalog freshness, and workflow impact become visible before change so rollout does not happen blind.

How it fits into the system

Shuttle does not stand alone. It connects to neighboring modules so a single capability becomes dependable follow-through.

Warp The conductor that assigns the work Wire The outward path that does not end in chaos Tenter The voice lane that holds in live operations Loom The place where no document gets lost Spindle The business logic you can rely on

Important boundary

Shuttle stays bounded to its role as Workflow execution and operational process motion. It does not replace other modules; it makes its part of the system traceable, connectable, and reviewable.

What is intentionally out of scope

It is easy to misread the product too narrowly. These boundaries are intentionally sharp.

not a pure workflow builder

not a replacement for n8n

not just a messaging tool

not just a monitoring frontend

not a generic AI or automation platform

What keeps this page honest

This explanation stays anchored to the module’s current truth, including its real boundaries, responsibilities, and contracts.

Shuttle is the execution layer where ordered intent turns into real processes and workflows.

README.md

Source and repo truth

This page is rendered from the repo-owned projection truth and remains tied to the README, module boundaries, and status.

GitHub JaddaHelpifyr/jhf-shuttle

Shuttle

In the Helpifyr picture, Shuttle is the operational automation and delivery surface. Not business truth. Not central portfolio control. Not a companion-only function.

Back to overview Contact