Event Kinds

Event kinds tell LocusGraph what type of knowledge you are storing, which determines how the wisdom graph processes and connects it.

Primary Kinds

Aliases: knowledge, learned

Persistent information that remains true over time. Use for preferences, configurations, and learned truths.

"The user prefers dark mode." / "The API rate limit is 1000 req/min."

Aliases: task, operation, execution, completed

Something happened. A task was performed or a process completed.

"Deployed version 2.3." / "Sent the weekly report."

Aliases: choice, selection, determination

A choice was made with reasoning. Records the what and the why.

"Selected PostgreSQL over MySQL for JSONB support."

General notes and impressions. The default kind for unclassified events.

"Build times increased after adding the new dependency."

Opinions, ratings, or suggestions from users. Carries subjective weight.

"User rated the response 4/5." / "User suggested shorter summaries."

Validation-related events. When a constraint_violation is stored, a derived_from link is auto-created to the source context.

Mapped to routine_operation. Filtered from standard retrieval. Use for health checks and lifecycle tracking.

Mapped to noise. Filtered from retrieval entirely. Exists for audit only.

Input Kind	Internal Type	Retrievable
`fact`, `knowledge`, `learned`	`knowledge_recorded`	Yes
`action`, `task`, `operation`, `execution`, `completed`	`action_completed`	Yes
`decision`, `choice`, `selection`, `determination`	`decision_made`	Yes
`observation`	`knowledge_recorded`	Yes
`feedback`	`knowledge_recorded`	Yes
`constraint`, `rule`, `constraint_violation`	`knowledge_recorded`	Yes
`routine`, `heartbeat`, `status`	`routine_operation`	No
`noise`, `debug`, `log`	`noise`	No

When in doubt, use fact for things that are true and observation for things you noticed. The admission pipeline handles the rest.