Skip to main content

Warp

This longform module page is the manufacturer-docs entry point for the module. It uses the product overview when that surface is admitted and falls back to the first safe versioned detail page when the overview is still blocked. Use it first; drop into the versioned product pages only when you need deeper surface detail or channel-specific reference.

  • Canonical module key: warp
  • Source repo: JaddaHelpifyr/jhf-warp
  • Preferred versioned channel today: stable

Versioned product docs​

Use these direct entry points when you need exact product behavior, operations, or reference detail:

Identity​

  • Repository: JaddaHelpifyr/jhf-warp
  • Product/Tool: Helpifyr Warp
  • Category: internal tool
  • Runtime kind: service
  • Belongs to: standalone
  • Lifecycle: active
  • Owner agent: jhf-warp-maintainer

Purpose​

jhf-warp is the orchestration control plane for OpenClaw-based multi-agent work. It classifies incoming work, builds team/bootstrap proposals, compares desired and real runtime topology, exposes drift/audit/control surfaces, and coordinates a bounded set of downstream integrations.

Naming Baseline​

  • Canonical Fabric ID: helpifyr.jhf-warp
  • Canonical slug: jhf-warp
  • Publish-facing names:
    • tile: Warp · Agent Orchestration
    • deep dive: Helpifyr Warp
    • ClawHub: Helpifyr Warp

What It Is Responsible For​

  • task classification and setup preview generation
  • runtime inventory, topology, and drift visibility
  • guarded OpenClaw patch planning and apply preparation
  • rollout and audit persistence
  • optional integration delivery to Helpifyr Pattern, Helpifyr Spindle, and jhf-shuttle
  • feature-flagged permanent control-agent behavior for doubtfire-control
  • persistent domain-agent governance for workspaces, tool profiles, and learning proposals

What It Does Not Do​

  • it is not a generic workflow engine for every Helpifyr repository
  • it is not the primary UI; Helpifyr Pattern stays external
  • it is not a secret-management platform
  • it is not a remote MCP server with external discovery today
  • it is not yet a direct Fabric registry participant; it only exposes preparatory self-description

Public Distribution Posture​

This repository is public as source code and documentation, but that does not by itself admit it into a coordinated public_distributable stack-nightly.

  • source publication: allowed
  • runtime publication: not implied
  • current Weaver posture: outside admitted public stack-nightly membership until a separate owner admission decision exists

Release Eligibility Posture​

  • Public release-surface admission is bounded by ../contracts/admission/release_surface_inventory_v1.json.
  • Current repository history posture is tracked in ../contracts/admission/repository_publication_history_posture_v1.json.
  • Active owner follow-up issue: JaddaHelpifyr/jhf-warp#564.
  • jhf-warp remains pending_history_scan; repo-owned history evidence now runs through python scripts/verify_repository_history_posture.py and currently proves filtered_publication_required, and this slice does not authorize publication.
  • The chosen owner-side path is non-destructive filtered publication from exact main, not canonical history rewrite.

Versioning Source​

The current version is sourced from:

  • pyproject.toml
  • src/oc_agent_manager/__init__.py

Entry Documents​

License​

AGPLv3. See ../LICENSE (LICENSE). Learn more at helpifyr.com.