Memories & Events
Events are the atomic unit of knowledge in LocusGraph — every piece of wisdom enters the graph as an event.
Events
An event represents a single piece of information submitted to the wisdom graph. Each event contains:
| Field | Required | Description |
|---|---|---|
event_kind | Yes | The type of knowledge: fact, action, decision, observation, feedback |
source | Yes | Who created it: agent, user, system, validator, executor |
payload | Yes | JSON object containing the knowledge data |
context_id | No | Scope the event to a context (e.g., skill:react_best_practices) |
links | No | Connections to other loci or contexts |
From Event to Locus
Events do not live in the graph directly. They pass through the admission pipeline, which:
- Validates the event structure and payload size.
- Classifies the event kind into an internal type.
- Extracts topics and relationships.
- Creates a locus — a permanent node in the wisdom graph.
A locus is the graph-native representation of admitted knowledge. Once created, it participates in retrieval, linking, and confidence scoring.
Kind Mapping
Raw event kinds map to internal types during admission:
| Input Kind | Internal Type |
|---|---|
fact, knowledge, observation | knowledge_recorded |
action, task | action_completed |
decision, choice | decision_made |
routine, heartbeat, status | routine_operation (filtered) |
noise, debug, log | noise (filtered) |
Events classified as routine_operation or noise are recorded but excluded from standard retrieval. They exist for audit purposes only.
Retrieval
When you call retrieveMemories, LocusGraph searches across admitted loci — not raw events. The query is matched against topics, payload content, and graph connections to return the most relevant knowledge.