Skip to main content

Overview

jhf-fabric is the canonical slug for Helpifyr Fabric, the shared control and coordination layer for the Helpifyr ecosystem.

Repository Type​

  • Category: core product
  • Group: platform
  • Runtime kind: service
  • Ownership: standalone Fabric control plane
  • Lifecycle: active
  • Fabric readiness: yes, this repository is the Fabric itself

Public Distribution Boundary​

This repository is public as source code and documentation under AGPLv3, but its current runtime/publication posture remains operator-scoped:

  • public source visibility is allowed
  • public=false with public_semantics=filtered_bundle permits only the exact-main, explicitly inventoried filtered bundle; runtime remains operator-only
  • current_history_posture=filtered_publication_required stays canonical until repository history admission is explicitly cleared
  • coordinated jhf-weaver stack-nightly admission is not implied and must read the owner decision artifact at contracts/admission/repository_publication_history_posture_v1.json
  • bounded release-surface admission truth lives in contracts/admission/release_surface_inventory_v1.json
  • the only approved history-safe publication path is the exact-main filtered bundle defined by contracts/admission/filtered_publication_bundle_policy_v1.json

What This Repository Contains​

  • FastAPI control-plane API
  • durable persistence and migration ownership
  • Dapr-backed middleware usage
  • JetStream-backed outbox and event publication
  • OpenClaw provider contract and guarded handoff stack
  • product adapter surfaces for the current Helpifyr systems
  • MCP read tools, production catalog, Gitea safe lane, Skill Context admission, delivery-loop checkpoint readback, and P1B owner evidence/readback alignment
  • governance, auth, observability, recovery, and signoff control-plane layers
  • tooling/policy/dashboard logic for external Helpifyr repositories

Current Queue Position​

Active repo-local queue items are managed in Gitea and mirrored in Autonomous Backlog (docs/AUTONOMOUS_BACKLOG.md). At the current baseline, milestones are documented as cleared unless a new repo-owned issue is explicitly opened.

Use docs/MODULE_FEATURES.md as the QA-oriented coverage and verification inventory.

License​