Core Concepts

Event Taxonomy

Good memory starts with clean event semantics. Keep event names stable and meaningful across your product.

Event Type

Meaning

user_question

User asks for help, clarification, or explanation

assistant_response

Assistant output delivered to user

learning_progress

Milestone completion or skill advancement

assessment_result

Quiz, test, or evaluation outcome

user_attempt

User attempt at a task, prompt, or exercise

preference_stated

Explicit user preference (style, pacing, format)

Inferred memory types

Orbit can also create inferred memories when evidence is strong enough.

inferred_learning_pattern

Generated from repeated semantically similar behavior for the same entity. Example: a learner repeatedly asks loop-control questions.

inferred_preference

Generated from sustained feedback trends. Example: concise answers consistently receive higher helpfulness scores.

inferred_user_fact

Generated from explicit natural-language statements. Example: user constraint or family preference extracted into structured fact metadata.

inferred_user_fact_conflict

Generated when critical fact statements conflict. Orbit marks these as clarification-required before relying on them.

If two events represent meaningfully different behaviors, give them different event types. If not, keep one type and use metadata fields for detail.