Skip to main content

Integrations

Updated: 2026-04-11

Responsibility Matrix​

jhf-openclaw-env owns:

  • host baseline
  • runtime policies
  • guardrails
  • live verification
  • session bootstrap
  • blocker routing
  • operations evidence

jhf-deployment owns:

  • provisioning and deployment automation
  • Terraform/Terratest provider and rollout execution
  • runtime artifact storage consumption
  • source-baseline contract consumption
  • canonical OpenClaw source-runtime baseline metadata contract and storage path

jhf-deployment does not own:

  • primary mutation of env runtime files under /home/administrator/jhf-openclaw-env/**
  • env-owned ingress/TLS/OpenClaw runtime materialization semantics
  • persistent shadow runtime state for jhf-tenter or other owner repos
  • canonical mirror-path truth for env-owned runtime files

jhf-beam owns:

  • upgrade and transition workflows
  • source-start verification ownership
  • compatibility flow acceptance

helpifyr-fabric owns:

  • governance and orchestration
  • run-ledger behavior
  • support execution read surfaces

jhf-shuttle owns:

  • messaging and automation integration around OpenClaw
  • mailbox and cross-stack automation ownership

jhf-warp consumes:

  • OpenClaw environment-owned runtime capability export
  • topology class detection metadata
  • install/runtime projection metadata for bounded reconcile planning
  • degraded runtime evidence contract references

Upstream OpenClaw owns:

  • OpenClaw product behavior
  • runtime policy capabilities inside the product

Integration Gates​

M3 requires green status across:

  • environment contracts in this repository
  • source-baseline contract compatibility with deployment and beam consumers
  • support execution contract compatibility with Fabric consumers
  • live runtime verification on <internal-runtime-redacted>

M5 requires:

  • mirrored active intake issues
  • legacy repository freeze
  • no ambiguous canonical ownership across repos

Cross-Repo Change Policy​

If a change is needed outside this repository:

  • open an owner issue with evidence and acceptance criteria
  • classify the finding in this repository
  • link the owner issue back into the routing log

Only implement direct multi-repo changes when the user explicitly asks for that scope.

Consumer rule for jhf-deployment:

  • deployment may verify env-owned truth
  • deployment may invoke env-owned entrypoints if the owner repo publishes them
  • deployment must not reimplement env-owned mutation semantics locally
  • historical exceptions in deployment issues do not become future ownership precedent
  • canonical machine-readable boundary contract: config/contracts/openclaw_deployment_consumer_boundary_contract.v1.json
  • canonical verifier: python scripts/verify_deployment_consumer_boundary.py

ACP-W2 MCP gateway boundary:

  • jhf-openclaw-env owns container/network/ingress/env materialization for the OpenClaw-side MCP consumer lane
  • Fabric/Warp/Heddle/Keystore owner truth is consumed but not reimplemented
  • spindle MCP auth runtime remains spindle-owned even when env proves the public/local gateway path
  • canonical contract: config/contracts/openclaw_acp_w2_mcp_gateway_materialization.v1.json
  • canonical verifier: python scripts/verify_openclaw_acp_w2_mcp_gateway_materialization.py

Source Baseline Consumption​

jhf-openclaw-env validates the local source-baseline payload contract and may also consume the deployment-owned baseline metadata path during scheduled or operator verification.

Canonical owner contract:

  • ../jhf-deployment/maintenance/source-runtime-baseline-contract.json

Canonical metadata resolution order in this repo:

  • JHF_OPENCLAW_SOURCE_BASELINE_METADATA
  • JHF_OPENCLAW_SOURCE_BASELINE_STORAGE_ROOT/<required-version>/openclaw-source-runtime-<version>.metadata.json
  • each deployment-owned storage_policy.primary_targets[*].location from the machine-readable jhf-deployment contract

Failure mode:

  • if canonical metadata is available, this repo validates that the deployment metadata shape and required version match the owner contract
  • if canonical metadata is unavailable, repo verification falls back to the checked-in sample payload unless JHF_REQUIRE_CANONICAL_SOURCE_BASELINE=1 is set
  • when strict mode is enabled, missing canonical metadata is a external-blocker on jhf-deployment ownership rather than a local sample bug

Runtime Evidence Forwarding​

jhf-openclaw-env owns local evidence capture and may optionally forward high-severity runtime evidence into the Shuttle-owned mailbox publish path.

Current downstream contract consumed here:

  • Shuttle mailbox publish endpoint: http://<host>:58815/publish
  • auth: optional bearer token when MAILBOX_ADAPTER_PUBLISH_TOKEN is enabled
  • payload shape: standard mailbox envelope with message_id, correlation_id, source_agent, target_agent, and target_session_key

Repo behavior:

  • scripts/log_live_operation.py always appends to docs/LIVE_OPERATIONS_LOG.md
  • forwarding only activates when JHF_EVIDENCE_FORWARDING_ENABLED=1
  • only high and critical severities are forwarded
  • forwarding transport errors stay non-fatal and do not block local evidence capture

Warp Runtime Contract​

jhf-openclaw-env publishes the Warp-consumable runtime/topology contract in:

  • config/contracts/openclaw_warp_runtime_contract.v1.json
  • docs/OPENCLAW_WARP_RUNTIME_CONTRACT.md

Consumer guarantees:

  • topology class remains explicit as openclaw-single-host-caddy-edge
  • runtime projection names the environment-owned host, compose project, containers, networks, ingress routes, and safe-read surfaces
  • capability flags tell Warp which checks are environment-owned and stable
  • the contract is for bounded reconcile reads and classification, not for direct runtime mutation delegation

License: AGPLv3 Project: https://helpifyr.com