Why start here?
Warp makes sure the right work reaches the right role at the right moment.
Orchestrator / Control
The conductor that assigns the work
Runtime orchestration and controlled execution steering.
Warp makes sure the right work reaches the right role at the right moment.
jhf-warp is:
a FastAPI-based runtime orchestration service the runtime execution and control truth for OpenClaw topology, drift, and bounded apply lanes a stable internal surface for operators, automation, and selected stack integrations a packaging target with OCI metadata, deployment contracts, and release-gate evidence
Status Available now README sync 29 Apr 2026
When do I need this?
Start here when you want to understand how the system decides who works and how change is applied safely.
What role it plays here
Runtime orchestration and controlled execution steering.
Without Warp, control fragments into scripts and edge cases. With Warp, operational execution stays readable and steerable.
What the module actually does
It keeps runtime state visible, compiles safe execution paths, and steers changes through bounded and traceable lanes.
At the core
runtime inventory, topology, drift, and health visibility
task classification and bounded team/setup compilation
guarded OpenClaw patch planning and apply preparation
control-agent supervision for doubtfire-control / Nikolai Wachter
persistent-agent, workspace, learning-proposal, and tool-profile read models
voice target truth for tray-owned voice lanes
support-triggered actions with approval-aware mutation boundaries
read-first integration surfaces for Fabric, Pattern, Shuttle, Spindle, Deployment, and Tenter
What role it plays in the stack
Warp owns:
runtime execution truth for OpenClaw-oriented topology, drift, rollout, and control-agent flows internal operator surfaces for guarded mutation planning and execution persistent runtime-facing read models for agents, workspaces, delegation, rollout, and support
Warp consumes:
identity and auth truth from jhf-heddle projection, contract, and read-first composition truth from jhf-fabric business identity and access truth from jhf-spindle OpenClaw runtime materialization from jhf-openclaw-env
Warp does not own:
customer-facing UI primary IAM, SSO, or claims truth Fabric registry or policy governance truth secret management direct business-system source-of-truth authority
What this looks like in practice
Without Warp, control fragments into scripts and edge cases. With Warp, operational execution stays readable and steerable.
A signal comes in.
The system assigns the right role and path.
Execution happens through controlled handoffs.
Result and evidence return together.
How it fits into the system
Warp does not stand alone. It connects to neighboring modules so a single capability becomes dependable follow-through.
Important boundary
Warp stays bounded to its role as Runtime orchestration and controlled execution steering. It does not replace other modules; it makes its part of the system traceable, connectable, and reviewable.
What comes next
Fabric Contract, projection, and governance truth for the stack. Pattern Consistency and control layer against drift. Shuttle Workflow execution and operational process motion. Tenter Runtime evidence, readiness, and provable execution. Dobby Controlled adaptation and safe system learning. All modules Back to overview
What is intentionally out of scope
Warp is not the primary IAM/OIDC truth owner
Warp is not a public customer UI product
Warp does not replace Fabric/Spindle/Heddle truth ownership boundaries
What keeps this page honest
This explanation stays anchored to the module’s current truth, including its real boundaries, responsibilities, and contracts.
Warp is the orchestration layer for operational multi-agent and runtime control.
It keeps runtime state visible, compiles safe execution paths, and steers changes through bounded and traceable lanes.
Without Warp, control fragments into scripts and edge cases. With Warp, operational execution stays readable and steerable.
Active part of the system with clearly defined boundaries.
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-warpWarp
Without Warp, control fragments into scripts and edge cases. With Warp, operational execution stays readable and steerable.