Why start here?
Fabric keeps decisions, access, and change from dissolving into local exceptions.
Core / Backbone
The rules that always hold
Contract, projection, and governance truth for the stack.
Fabric keeps decisions, access, and change from dissolving into local exceptions.
Helpifyr Fabric is the stack-level control-plane truth layer. It defines and publishes contracts, admission states, policy projections, and readiness semantics that other Helpifyr repositories consume.
Status Available now README sync 29 Apr 2026
When do I need this?
Start here when you want to understand why many modules still behave like one system.
What role it plays here
Contract, projection, and governance truth for the stack.
Without Fabric, the system drifts into local exceptions. With Fabric, change remains connected, readable, and controlled.
What the module actually does
It publishes the rules, contracts, and projections every other module relies on, so no part has to invent its own policy logic.
At the core
Publishes canonical contracts for identity, surfaces, onboarding, lifecycle, entitlement, and governance.
Publishes ACP capability-registry, skill_pack.* event-family truth, agent handoff/escalation/ownership event truth, Reed read-only projection, Swatch scenario verdict projection, and handoff ownership projection with explicit fail-closed semantics.
Serves deterministic projection APIs used by downstream modules for runtime decisions.
Enforces fail-closed semantics for blocked, stale, degraded, or conflicting states.
Classifies current observability surfaces (including Grafana and Prometheus) in canonical onboarding/access truth instead of leaving them implicit.
Publishes one canonical platform-version truth plus projection-catalog truth for Grafana, Prometheus, Wiki.js, Dapr, shared n8n, and shared NATS so upgrade consumers do not infer pins, readbacks, or compatibility surfaces from scattered docs or compose files.
Provides contract and schema governance with explicit compatibility expectations.
Centralizes verification-oriented artifacts so repo and live checks use one authoritative reference.
What role it plays in the stack
Fabric owns contract and projection truth for stack governance and identity-adjacent admission surfaces. Fabric consumes runtime observations and owner signals from other repos, but does not replace their domain ownership (for example business role truth in spindle or OIDC runtime ownership in heddle). For observability/operator surfaces, Fabric projects status and posture, while role/access truth remains owned by spindle and technical auth runtime remains owned by heddle. Fabric must not introduce shadow truth when an upstream owner is canonical for a domain.
What this looks like in practice
Without Fabric, the system drifts into local exceptions. With Fabric, change remains connected, readable, and controlled.
A signal comes in.
The system assigns the right role and path.
Execution happens through controlled handoffs.
Result and evidence return together.
How it fits into the system
Fabric does not stand alone. It connects to neighboring modules so a single capability becomes dependable follow-through.
Important boundary
Fabric stays bounded to its role as Contract, projection, and governance truth for the stack. It does not replace other modules; it makes its part of the system traceable, connectable, and reviewable.
What comes next
Heddle Identity, session, and SSO truth for the stack. Keystore The governed secrets and access layer. Warp Runtime orchestration and controlled execution steering. Shuttle Workflow execution and operational process motion. Dobby Controlled adaptation and safe system learning. All modules Back to overview
What keeps this page honest
This explanation stays anchored to the module’s current truth, including its real boundaries, responsibilities, and contracts.
Fabric is the central truth and connection layer of the Helpifyr system.
It publishes the rules, contracts, and projections every other module relies on, so no part has to invent its own policy logic.
Without Fabric, the system drifts into local exceptions. With Fabric, change remains connected, readable, and controlled.
Active part of the system with clearly defined boundaries.
Source and repo truth
This page is rendered from the repo-owned projection truth and remains tied to the README, module boundaries, and status.
GitHub JaddaHelpifyr/helpifyr-fabricFabric
Without Fabric, the system drifts into local exceptions. With Fabric, change remains connected, readable, and controlled.