Integrations
Documentation Map
-
Integrations
-
Channel:
stable -
Source repo:
JaddaHelpifyr/jhf-loom
Integrations
Tool / Contract Summary
This page documents the real cross-repo boundaries of jhf-loom. It focuses on
what Loom consumes, what it owns locally, and what it must not duplicate.
Current Verified State
Live and verified now:
- Loom public ingress is active through
jhf-openclaw-env - Loom identity entry is active through
jhf-heddle - Loom consumes Fabric truth read-only for governance alignment and admission posture
Available Now
JaddaHelpifyr/helpifyr-fabric
- Role:
- single governance, registry, readiness, docs-standard, and admission truth
- Loom consumes:
GET /api/v1/contracts/docs-standardGET /api/v1/contracts/matrixGET /api/v1/contracts/jarvisGET /api/v1/contracts/jarvis/readinessGET /api/v1/contracts/registryGET /api/v1/contracts/familiesGET /api/v1/contracts/schemasPOST /api/v1/tools/admission/dry-run
- Local materialization:
- repo-owned validation results
- repo-owned documentation about consumed posture
- Explicitly forbidden:
- local redefinition of Fabric registry truth
- local redefinition of family/version truth
- local redefinition of admission truth
- local redefinition of JARVIS truth
JaddaHelpifyr/jhf-heddle
- Role:
- only identity provider for Loom
- Current verified path:
- proxy-SSO through the trusted bridge
- login and logout are green on the public path
- What Loom owns locally:
- acceptance of trusted user identity at the boundary
- content authorization inside the content system
- What Loom does not own:
- Keycloak realm/client truth
- external identity federation policy
JaddaHelpifyr/jhf-openclaw-env
- Role:
- owner of DNS, Caddy route, TLS, and public exposure for Loom
- Current verified path:
<internal-runtime-redacted>- public Share landing
- public repository/API reachability
- What Loom owns locally:
- declaration of the ingress handoff boundary
- What Loom does not own:
- host DNS
- host Caddy config
- host TLS edge
- raw public port exposure
Optional / Extended
- direct Alfresco-to-Keycloak login remains non-canonical
- future downstream tool integrations must still prefer Fabric-mediated posture over bilateral defaults
- later Fabric-mediated workflow integration with
jhf-shuttleremains allowed only as a governed extension - no direct
jhf-loom -> jhf-shuttleruntime coupling is accepted as the default integration mode
Planned / Not in Current Scope
- no new direct downstream integrations are documented as live unless they are verified and issue-driven
- no local Fabric-derived projection service is introduced here
Producer-/Consumer-Zuordnung
Consumers:
- Fabric contracts and admission surfaces
- Heddle identity
- OpenClaw ingress
Producers:
- no Fabric-owned shared truth
- no local registry/admission/governance truth
License: AGPLv3.
Helpifyr: https://helpifyr.com