Why start here?
Spindle keeps operational work anchored to real business truth, roles, and approvals.
Business / Delivery
The business logic you can rely on
Business truth and operational business logic.
Spindle keeps operational work anchored to real business truth, roles, and approvals.
Helpifyr Spindle is the ERP-facing module in the Helpifyr ecosystem. It runs on Frappe/ERPNext and provides business-side execution, evidence, and integration boundaries for approvals, dispatch workflows, support contexts, and identity projection contracts.
Status Available now README sync 29 Apr 2026
When do I need this?
Start here when you want to see where business truth and operational accountability live inside the system.
What role it plays here
Business truth and operational business logic.
Without Spindle, automation loses business grounding. With Spindle, it stays tied to real business decisions.
What the module actually does
It keeps approvals, business logic, and system-of-record behavior stable so operational work connects to real business truth.
At the core
Maintains ERP/business records as system-of-record state.
Accepts and validates signed callbacks and webhook-style integration events.
Publishes machine-readable contracts and business-truth identity surfaces for downstream consumers.
Exposes guarded MCP operator tooling and runtime verification helpers.
Provides optional support-lane integration surfaces (for example Zammad) under explicit contracts.
What role it plays in the stack
Spindle owns:
ERP/business truth and business execution evidence business-facing integration contracts in this repository identity/business-role/source semantics consumed by downstream components
Spindle consumes (read-only where applicable):
Fabric admission/governance truth surfaces identity/session ownership from Heddle runtime hosting and environment materialization from deployment/env owners
Spindle does not own:
central OIDC/session authority Fabric canonical registry ownership external carrier/provider runtime ownership
What this looks like in practice
Without Spindle, automation loses business grounding. With Spindle, it stays tied to real business decisions.
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
Spindle does not stand alone. It connects to neighboring modules so a single capability becomes dependable follow-through.
Important boundary
Spindle stays bounded to its role as Business truth and operational business logic. It does not replace other modules; it makes its part of the system traceable, connectable, and reviewable.
What comes next
What keeps this page honest
This explanation stays anchored to the module’s current truth, including its real boundaries, responsibilities, and contracts.
Spindle is the business layer where business truth, roles, and processes are anchored.
It keeps approvals, business logic, and system-of-record behavior stable so operational work connects to real business truth.
Without Spindle, automation loses business grounding. With Spindle, it stays tied to real business decisions.
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/jhf-spindleSpindle
Without Spindle, automation loses business grounding. With Spindle, it stays tied to real business decisions.