Skip to main content

Integrations

Tool / Contract Summary​

This page lists the real integration boundaries for jhf-deployment: what is consumed, what is executed, and who owns truth.

Business Value​

  • avoids hidden cross-repo ownership drift
  • keeps deployment gates reproducible and auditable
  • enforces no-shadow-truth consumption from Fabric

Current Verified State​

  • Fabric contracts/combinations are consumed read-only
  • deployment execution is script/contract driven
  • runtime semantic ownership is externalized to owner repos

Public Surfaces​

Fabric (read-only consumed)​

  • GET /api/v1/contracts/matrix
  • GET /api/v1/contracts/docs-standard
  • GET /api/v1/tools/host-pressure-policy
  • GET /api/v1/combinations/profiles
  • GET /api/v1/combinations/optional-slices
  • GET /api/v1/combinations/optional-slices/sipgate-carrier-cti

Deploy/verify command surfaces​

  • environments/test/scripts/preflight.sh
  • environments/test/scripts/plan.sh
  • environments/test/scripts/create.sh
  • environments/test/scripts/verify.sh
  • environments/test/scripts/destroy.sh
  • environments/test/scripts/reset.sh
  • host checks:
    • verify-host-runtime-preflight.sh
    • verify-host-postdeploy-runtime-state.sh

Artifact/evidence surfaces​

  • Terraform outputs:
    • terraform -chdir=environments/test output -json
  • evidence:
    • test-results/*.json
    • test-results/*.junit.xml

Contract Families​

  • Fabric governance contracts
  • Fabric host-pressure policy contract
  • Fabric combinations contracts
  • host runtime preflight contracts
  • stack ownership/legacy/retired runtime contracts
  • optional carrier prep contracts

Producer-/Consumer-Zuordnung​

helpifyr-fabric​

  • Direction: outgoing read-only consumption
  • Type: REST contract surfaces
  • Owner: helpifyr-fabric
  • Consumer: jhf-deployment
  • Local prohibition:
    • no semantic redefinition of Fabric-owned truth

Runtime owner repositories​

  • Direction: contract consumption
  • Type: runtime ownership/semantic boundaries
  • Owner: specialist repos (jhf-shuttle, jhf-warp, jhf-pattern, jhf-spindle, etc.)
  • Consumer: jhf-deployment for deploy/verify gates only

Docker host (<internal-runtime-redacted>)​

  • Direction: outgoing execution/verify
  • Type: SSH + Docker runtime inspection
  • Owner: host/env owner lane
  • Consumer: jhf-deployment scripts for evidence generation

OCI/Gitea package sources​

  • Direction: outgoing pull/verify or optional publish
  • Type: artifact contract
  • Owner: source repos/registry infra
  • Consumer: jhf-deployment scenario inputs

Compatibility Window​

  • accepted Fabric family/version windows are pinned in:
    • maintenance/fabric-contract-consumption.json
    • maintenance/fabric-host-pressure-policy-consumption.json
  • explicit image versions/tags are preferred; implicit mutable versions are not canonical

Lifecycle Status​

  • status: active
  • posture: issue-driven deploy/verify integration

Readiness / Drift / Monitoring​

  • readiness requires passing gates and machine-readable evidence artifacts
  • deployment-owned drift fails fast
  • external owner drift is routed as blocker with owner issue reference

Deployment / Verify​

bash environments/test/scripts/preflight.sh
bash environments/test/scripts/verify.sh

Fabric governance verify:

python3 scripts/verify-fabric-contract-governance.py \
  --matrix-url `api/v`1/contracts/matrix \
  --docs-standard-url `api/v`1/contracts/docs-standard \
  --output test-results/fabric-contract-governance-readiness.live.json

Known Limits​

  • live integration checks require host/network availability
  • CI scheduler/runner incidents are infra-external blockers

Exceptions / Waivers​

  • allowed only as explicit, issue-linked, time-bounded exceptions
  • rollout and blocker traces: docs/issues/

License: AGPLv3 Source and governance: https://helpifyr.com