Zero-LLM hot path
Routine memory writes are arithmetic graph updates, not extraction calls. Memory formation stays bounded as traffic grows.
FERNme is a Hebbian-first memory layer for site agents. It updates a sparse fuzzy graph by default and reserves semantic reasoning for uncertainty.
01 / SYSTEM
Routine learning stays deterministic. Semantic reasoning appears only where its cost can change the outcome.
Routine memory writes are arithmetic graph updates, not extraction calls. Memory formation stays bounded as traffic grows.
When confidence is low, FERNme can ask a small LLM or the user. Otherwise it continues learning deterministically.
Recall compiles the strongest relevant edges into a compact card instead of replaying a long conversation history.
People can inspect, correct, export, or delete memory so personalization does not become hidden surveillance.
02 / METHOD
A small set of interpretable operations turns behavior into usable recall.
Capture consented events such as bookings, corrections, purchases, and successful outcomes.
Strengthen or decay graph edges between signals, preferences, contexts, and actions.
Combine evidence strength, conflict, taxonomy match, recency, and outcome feedback.
Retrieve only the strongest relevant memories for the agent’s current task.
Free text, causal ambiguity, or low confidence can trigger optional enrichment or a user check.
Learn from repeated evidence, retain uncertainty, and escalate only when an ambiguous update is important enough to justify the cost.
03 / RESEARCH STATUS
Fuzzy graph updates, compact recall, consent gates, audit history, persistence, export, and deletion.
Turning messy real-world site events and free text into reliable, taxonomy-rich memory signals.
A research preview for bounded transactional memory—not a claim of general, production-ready agent memory.
04 / FAQ
No. It is Hebbian-first. The default path is deterministic; optional semantic enrichment is reserved for uncertain cases.
No. Structured behavioral events can update the fuzzy graph without an LLM call.
FERNme avoids always-on extraction and full-history prompting. Recall compiles a small, relevant memory card.
Consent, human-readable recall, correction, export, and deletion are part of the service boundary.
Not yet. FERNme is a research preview. The graph, recall, consent, audit, and storage paths exist; real-world ingestion and production hardening remain active work.