Skip to main content

Integrations

Documentation Map​

Integrations

Role Boundary​

jhf-web is the repository name. Its Fabric-facing canonical slug is jhf-web, with jadda-web and solarisara-web retained as legacy slugs. It remains a website / client repository, exposes only a small number of public website and intake surfaces, and must not be modeled as a backend integration hub or service control plane.

Fabric or another aggregator may read the repo's machine-readable metadata and minimal public status surfaces. Fabric must not be assumed to own deployment, content mutation, lead processing, or mirrored host control.

The explicit read-only contract is defined in docs/FABRIC_CONSUMER_CONTRACT.md (docs/FABRIC_CONSUMER_CONTRACT.md).

Implemented Integrations​

Public content routes​

  • Direction: incoming
  • Type: other
  • Surface: /, /services, /pricing, /contact, /early-access, /team, /blog, /legal
  • Auth: none
  • Stability: stable
  • Versioning: unversioned public website routes
  • Owner: jhf-web

Contact intake​

  • Direction: incoming
  • Type: webhook-like form API
  • Surface: /api/contact (POST)
  • Auth: public_protected via Turnstile validation
  • Stability: stable
  • Versioning: unversioned; schema stability is defined by contracts/contact-intake.contract.json
  • Owner: jhf-web
  • Boundary reference: docs/INTAKE_SECURITY_BOUNDARY.md (docs/INTAKE_SECURITY_BOUNDARY.md)

Runtime status​

  • Direction: incoming
  • Type: REST-like status
  • Surface: /health, /ready (GET)
  • Auth: none
  • Stability: stable
  • Versioning: unversioned minimal status semantics
  • Owner: jhf-web

Version visibility​

  • Direction: incoming
  • Type: file contract
  • Surface: /version.json (GET)
  • Auth: none
  • Stability: stable
  • Versioning: file schema is repo-defined and updated with metadata exports
  • Owner: jhf-web

Cloudflare Turnstile verify API​

  • Direction: outgoing
  • Type: REST API
  • Surface: https://challenges.cloudflare.com/turnstile/v0/siteverify (POST)
  • Auth: shared secret via TURNSTILE_SECRET_KEY
  • Stability: stable
  • Versioning: provider-managed v0 endpoint
  • Owner: Cloudflare runtime dependency, consumed by jhf-web

Contact forwarding webhook​

  • Direction: outgoing
  • Type: webhook
  • Surface: ${CONTACT_WEBHOOK_URL} (POST)
  • Auth: optional token header
  • Stability: configurable
  • Versioning: unversioned target contract; payload shape is repo-defined at send time
  • Owner: external webhook target, triggered by jhf-web
  • Boundary reference: docs/INTAKE_SECURITY_BOUNDARY.md (docs/INTAKE_SECURITY_BOUNDARY.md)

Fabric metadata files​

  • Direction: outgoing read model
  • Type: file contract
  • Surface: fabric-manifest.json, status.json, version.json, contracts/contact-intake.contract.json
  • Auth: none
  • Stability: internal
  • Versioning: repo-defined file schemas
  • Owner: jhf-web

Stack runtime contract​

  • Direction: outgoing read model
  • Type: file contract
  • Surface: contracts/stack-runtime.contract.json
  • Auth: none
  • Stability: stable
  • Versioning: repo-defined contract schema
  • Owner: jhf-web
  • Boundary note: this repo is the source of truth for stack name, containers, ports, volumes, networks, and runtime commands

Runtime port policy contract​

  • Direction: outgoing read model
  • Type: file contract
  • Surface: contracts/runtime-port-policy.contract.json
  • Auth: none
  • Stability: stable
  • Versioning: repo-defined contract schema
  • Owner: jhf-web
  • Boundary note: explicit per-service policy labels plus controlled live-port discovery and consumer-safe publish path
  • Direction: incoming
  • Type: other
  • Surface: /support.html#operator-case-overview
  • Auth: none
  • Stability: stable
  • Versioning: unversioned HTML navigation surface; linked objects remain versioned in their owning repositories
  • Owner: jhf-web
  • Boundary note: navigation only; this surface must not become a second case, run, action, or evidence source of truth

Operator agent readout​

  • Direction: incoming
  • Type: other
  • Surface: /support.html#operator-agent-readout
  • Auth: none
  • Stability: stable
  • Versioning: UI surface backed by repo-owned JSON readout contract
  • Owner: jhf-web
  • Boundary note: readout only; this surface may summarize and link upstream truth, but it must not author task, action, handoff, denial, or verdict truth locally

Operator agent readout JSON​

  • Direction: outgoing read model
  • Type: file contract
  • Surface: /assets/data/operator-readout.v1.json
  • Auth: none
  • Stability: stable
  • Versioning: schema_version inside the JSON payload
  • Owner: jhf-web
  • Boundary note: machine-readable presentation contract for the UI only; upstream truth stays with Fabric, Warp, and related owners

Fabric bundle profile feed​

  • Direction: outgoing read model
  • Type: REST API
  • Surface: api/v1 (GET)
  • Auth: none on the internal operator network path
  • Stability: stable
  • Versioning: unversioned contract owned by helpifyr-fabric
  • Owner: helpifyr-fabric
  • Boundary note: canonical combination truth only; jhf-web must not derive, rewrite, or silently smooth active combinations locally

Fabric contracts matrix​

  • Direction: outgoing read model
  • Type: REST API
  • Surface: api/v1 (GET)
  • Auth: none on the internal operator network path
  • Stability: stable
  • Versioning: Fabric-owned matrix versioning
  • Owner: helpifyr-fabric
  • Boundary note: canonical family/version producer-consumer truth; jhf-web only consumes

Fabric docs standard contract​

  • Direction: outgoing read model
  • Type: REST API
  • Surface: api/v1 (GET)
  • Auth: none on the internal operator network path
  • Stability: stable
  • Versioning: standard_version managed by Fabric
  • Owner: helpifyr-fabric
  • Boundary note: canonical docs governance family/version truth; no local shadow matrix

Fabric identity contracts​

  • Direction: outgoing read model
  • Type: REST API
  • Surface: api/v1 (GET)
  • Auth: none on the internal operator network path
  • Stability: stable
  • Versioning: family-version truth sourced from matrix plus identity surface payload
  • Owner: helpifyr-fabric
  • Boundary note: canonical identity-policy-chain contract source; consumed read-only
  • Direction: incoming
  • Type: other
  • Surface: /support.html#operator-combination-overview
  • Auth: none
  • Stability: stable
  • Versioning: unversioned HTML navigation surface; the profile contract stays versioned in the owning Fabric repository
  • Owner: jhf-web
  • Boundary note: navigation only; stale, mismatch, and missing upstream truth must remain explicitly visible

Deployment package bundle​

  • Direction: outgoing read model
  • Type: file contract
  • Surface: api/packages
  • Auth: token for publish, token or public read depending on package host policy
  • Stability: stable
  • Versioning: explicit package version tag; no latest
  • Owner: jhf-web

Cloudflare Pages runtime​

  • Direction: operational dependency
  • Type: other
  • Surface: public hosting runtime for pages and functions
  • Auth: platform-managed
  • Stability: stable
  • Versioning: provider-managed platform runtime
  • Owner: Cloudflare

Mirrored host runtime​

  • Direction: operational dependency
  • Type: other
  • Surface: <internal-runtime-redacted>
  • Auth: host-specific, not provided by this repo
  • Stability: internal
  • Versioning: host-managed deployment state, outside repo schema control
  • Owner: OpenClaw host operations

Intake workflow template​

  • Direction: documentation contract
  • Type: file contract
  • Surface: n8n/helpifyr-contact-intake.workflow.json
  • Auth: not in this repo; resolved in the target runtime
  • Stability: internal
  • Versioning: repo-tracked template file
  • Owner: jhf-web

Status And Drift Sources​

  • status.json
  • version.json
  • .gitea/workflows/ci.yml
  • Cloudflare Pages deployment history
  • mirrored host docker compose state
  • docs/DEPLOY_DRIFT.md (docs/DEPLOY_DRIFT.md)

These sources describe status or drift indirectly. This repo has no dedicated deploy-drift API and should not grow one casually just to appear more service-like.

Planned Integrations​

No additional integration is implemented by this slice.

Any future connection must first be documented here and in docs/FABRIC_TOOL_PROFILE.md (docs/FABRIC_TOOL_PROFILE.md) with the same required fields plus a clear note whether it is only planned or already implemented.

Normative ownership per integration-relevant topic is defined in docs/SOURCE_OF_TRUTH.md (docs/SOURCE_OF_TRUTH.md).