Why start here?
Bobbin lets the system keep context from earlier steps and reuse it in a traceable way.
Memory
The memory that keeps the context
Persistent memory and provenance layer.
Bobbin lets the system keep context from earlier steps and reuse it in a traceable way.
jhf-bobbin is the Helpifyr module for protected memory runtime enablement around OpenClaw. It is not a resident web service. It is an operator-owned toolkit that installs, patches, verifies, and re-applies a bounded semantic-memory stack built around Mem0, LocalAI, and Qdrant.
The repository also publishes machine-readable contracts and validation surfaces so other Helpifyr modules can understand what Bobbin actually owns, what it only consumes, and what must fail closed when runtime truth or governance truth is missing.
Status Available now README sync 29 Apr 2026
When do I need this?
Start here when you want to understand how the system keeps context instead of starting from zero each time.
What role it plays here
Persistent memory and provenance layer.
Without Bobbin, the system forgets too much. With Bobbin, previous steps stay reusable and verifiable.
What the module actually does
It preserves context, traces, and provenance so learning, traceability, and reuse rest on real memory instead of chance.
At the core
installs and re-applies the Bobbin memory stack on an OpenClaw host
patches the Mem0/OpenClaw integration for the supported LocalAI embedding path
validates stack truth, runtime truth, packaging truth, and Fabric-facing metadata
enforces approved-summary-only and marked-artifact-only memory contract boundaries
exports status and metadata surfaces for Fabric, deployment, and QA consumers
What role it plays in the stack
Bobbin owns:
the repo-local stack contract for jhf-bobbin installer, reapply, rollback, verify, and packaging tooling bounded materialization rules for supported memory-related inputs repo-local metadata, status, and QA evidence surfaces
Bobbin consumes read-only:
Fabric governance and contract-family truth Fabric runtime-claims and readiness truth Fabric summary-export contract truth Dobby marked provenance input contracts
Bobbin explicitly does not own:
a public runtime API Fabric policy, lifecycle, or closure truth raw support-event ingestion as primary memory truth phase-1 voice memory persistence in jhf-tenter
What this looks like in practice
Without Bobbin, the system forgets too much. With Bobbin, previous steps stay reusable and verifiable.
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
Bobbin does not stand alone. It connects to neighboring modules so a single capability becomes dependable follow-through.
Important boundary
Bobbin stays bounded to its role as Persistent memory and provenance layer. 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.
Bobbin is the memory layer of the system.
It preserves context, traces, and provenance so learning, traceability, and reuse rest on real memory instead of chance.
Without Bobbin, the system forgets too much. With Bobbin, previous steps stay reusable and verifiable.
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-bobbinBobbin
Without Bobbin, the system forgets too much. With Bobbin, previous steps stay reusable and verifiable.