Aller au contenu principal

Integrations

Documentation Map​

Integrations

Internal Helpifyr Integrations​

openclaw​

  • Direction: outgoing
  • Type: provider-contract
  • Surface: runtime discovery, topology reads, diff planning, guarded handoff
  • Auth: provider-specific internal contract
  • Stability: stable
  • Versioning: provider contract family, additive evolution
  • Owner: helpifyr-fabric provider adapter

n8n-operator​

  • Direction: bidirectional logical integration
  • Type: product-adapter
  • Surface: topology sync, capability intake, compatibility checks
  • Auth: internal service contract
  • Stability: stable
  • Versioning: additive contract evolution
  • Owner: helpifyr-fabric product adapter plus downstream n8n-operator

clawledger​

  • Direction: bidirectional logical integration
  • Type: product-adapter
  • Surface: setup requests, approvals, tool-bundle detection with helpifyr-wire
  • Auth: internal service contract
  • Stability: stable
  • Versioning: additive contract evolution
  • Owner: helpifyr-fabric product adapter plus downstream clawledger

mission-control​

  • Direction: outgoing
  • Type: operator-consumer
  • Surface: setup, topology, drift, rollout, signoff summaries
  • Auth: internal operator-safe contract
  • Stability: stable
  • Versioning: additive contract evolution
  • Owner: helpifyr-fabric summary surfaces plus downstream mission-control

oc-agent-manager​

  • Direction: outgoing
  • Type: compatibility-shim
  • Surface: runtime inventory and compatibility posture
  • Auth: internal service contract
  • Stability: stable
  • Versioning: additive contract evolution
  • Owner: helpifyr-fabric compatibility layer plus downstream oc-agent-manager

Additional Helpifyr Repositories​

  • Direction: outgoing read-only
  • Type: repository-intake
  • Surface: fabric-manifest.json and docs/FABRIC_TOOL_PROFILE.md from Gitea
  • Auth: repository read path
  • Stability: stable but schema-tolerant
  • Versioning: repository-owned manifest/profile revisions
  • Owner: repository teams plus Fabric tooling intake

jhf-beam​

  • Direction: outgoing read-only
  • Type: supporting-tool execution-contract
  • Surface: GET /api/v1/tools/standards, GET /api/v1/tools/standards/{tool_key}, GET /api/v1/tools/connection-matrix, and GET /api/v1/updates/compatibility-matrix
  • Auth: internal read path
  • Stability: partial
  • Versioning: additive over the existing tooling and compatibility surfaces
  • Owner: jhf-beam as execution tool, jhf-fabric as context provider

Implemented:

  • Fabric exposes tool identity, lifecycle, dependencies, connection inventory, and compatibility context as artifact inputs for jhf-beam.
  • The current verify path is read-first only; no write-back or upgrade execution is owned by Fabric.

Planned:

  • optional evidence intake can be added later if the upgrade flow needs compact post-run evidence, but no evidence write path is implemented in the current baseline
  • guarded compatibility checks or rollout-gate calls may later be consumed by the upgrade tool as context, but this integration step is not implemented in the current baseline

External Integrations​

Gitea​

  • Direction: incoming and outgoing
  • Type: webhook plus repo-read
  • Surface: /api/v1/integrations/gitea/webhook and raw repository artifact fetches
  • Auth: webhook header and internal repository access path
  • Stability: stable
  • Versioning: Gitea 1.22 API and raw path behavior
  • Owner: Gitea plus Fabric tooling intake

Dapr​

  • Direction: outgoing
  • Type: sidecar
  • Surface: invocation, state probing, runtime metadata
  • Auth: internal sidecar network
  • Stability: stable
  • Versioning: Dapr 1.15.5 baseline
  • Owner: Fabric middleware layer

NATS JetStream​

  • Direction: outgoing publish
  • Type: message-bus
  • Surface: event subjects and outbox publication evidence
  • Auth: internal runtime network
  • Stability: stable
  • Versioning: NATS 2.11 baseline
  • Owner: Fabric events backbone

PostgreSQL​

  • Direction: outgoing persistence
  • Type: database-contract
  • Surface: SQLAlchemy repositories, migrations, readiness probes
  • Auth: internal database credentials
  • Stability: stable
  • Versioning: PostgreSQL 16 baseline plus Alembic migrations
  • Owner: Fabric persistence layer

Prometheus, Grafana, OTel​

  • Direction: outgoing metrics and dashboard provisioning
  • Type: observability-stack
  • Surface: metrics export, dashboard activation, telemetry export
  • Auth: internal runtime network
  • Stability: stable
  • Versioning: platform-plane stack versions from compose
  • Owner: Fabric observability layer

Event Contracts​

Published Families​

  • fabric.topology.changed
  • fabric.rollout.planned
  • fabric.drift.detected
  • fabric.product.sync.requested
  • fabric.approval.required
  • fabric.residual_risk.detected
  • fabric.capability.changed

Consumed Families​

  • none as a first-class external event contract in the current repo baseline

MCP Integration​

  • Direction: outgoing
  • Type: mcp
  • Surface: API-backed read tools, guarded safe actions, the production MVP catalog, Gitea issue safe lane, delivery-loop checkpoint readback, and owner-readback references for OpenClaw Skill Context, Spindle, Pattern, and Shuttle/n8n
  • Auth: API-backed guarded access
  • Stability: stable
  • Versioning: additive tool surface evolution
  • Owner: Fabric MCP layer

Current admitted production surfaces:

  • fabric_catalog_query: Fabric-owned read-only catalog query.
  • gitea_issue_safe_lane: scoped safe-action issue read/create/comment/status lane; merge, branch deletion, force-push, settings, secrets, and token rotation stay forbidden.
  • openclaw_skill_context: Fabric-filtered OpenClaw Skill Context generated or consumed by owner repos; stale contexts cannot enable writes.
  • spindle_business_operations: approval-required business operations readback from the Spindle MCP contract.
  • pattern_mcp_mvp_evidence_readback: Pattern-owned read-only evidence mirror, not a second catalog authority.
  • n8n_workflow_readback: Shuttle-owned read-only n8n workflow, execution, health, and runtime visibility.

Promotion rule:

  • New merged PR truth is not automatically MCP catalog truth.
  • Fabric first classifies the surface as agent_visible_mcp_surface, owner_readback_surface, customer_runtime_surface, identity_security_surface, deployment_materialization_surface, quality_learning_surface, or future_candidate.
  • Only agent_visible_mcp_surface entries can become visible to agents, and only after owner issue, owner contract, feature truth, CI, live materialization where relevant, and Fabric catalog/read-tool/docs parity are present.
  • Other surface classes may affect execution closure or production readiness, but stay outside the MCP catalog unless explicitly promoted.

Planned Connections​

helpifyr-terraform​

  • Direction: bidirectional logical alignment
  • Type: planned cross-repository integration
  • Surface: OCI image and platform-plane contract alignment
  • Auth: repository and deployment contract level
  • Stability: planned
  • Versioning: tied to HF-029
  • Owner: Fabric and Terraform repositories

Future connections must be documented before implementation with:

  • purpose
  • direction
  • expected data
  • auth
  • trigger
  • minimum protocol shape

License​