Docs/Context Studio/Orion Memory

Orion Memory

View, add, and prune the facts, preferences, context, and instructions Orion has learned about your workspace.

LuminaryWeaverUpdated June 2026 · 5 min read

✦

In this section

Part of Celiq's semantic layer platform. Connect your warehouse, model your data once, query it everywhere.

💡

Tip

What it is — A workspace-level store of facts, preferences, context, and instructions that Orion remembers and applies to every answer.
When to use it — When you want Orion to always know something (e.g. "report revenue in GBP"), or when you want to review and clean up what it has already learned.
Where to find it — Context Studio → Orion Memory in the left nav (/context-studio?section=memory).
Who can use it — Luminary and Weaver. Context Studio is not available to Tracer or Lens.

Orion Memory is the running knowledge Orion keeps about your workspace. Some of it Orion builds for itself as people ask questions; some of it you add by hand. Either way, every item in this list is something Orion can lean on when it answers, so the page doubles as a control panel: you decide what stays.

The list shows the items grouped by type, each with a short label and the value behind it. You can add a new item or delete any item you no longer want Orion to use.

Overview

The Orion Memory tab lists every memory stored for the current workspace. The header shows a live count — for example, "12 items — things Orion has learned about your workspace" — and a + Add memory button.

Memories are grouped into colour-coded sections by their type, with the count of items in each group. Inside a group, each memory is a card showing the label (the key) in bold and the value underneath. A small delete (×) control sits on the right of each card.

If Orion has not stored anything yet, the page shows an empty state: "Orion hasn't learned anything yet. Ask Orion questions to build memory, or add items manually."

When to use it

You want Orion to always apply a rule — for example, format currency in GBP, or round to two decimal places — without restating it in every question.
You want to record a business truth Orion should treat as fixed, such as when your fiscal year starts.
You want to review what Orion has learned on its own and remove anything that is stale, wrong, or no longer relevant.
You are onboarding a workspace and want to seed Orion with a few known facts and preferences up front.

Concepts

Term	What it means
Memory	A single stored item with a type, a label (key), and a value.
Type (`memory_type`)	The category of the item. One of `preference`, `fact`, `context`, `instruction`, or `other`. Memories are grouped by type on the page.
Label (key)	A short identifier for the memory, e.g. `preferred_currency`. The label is unique per type within a workspace — saving the same type + label again updates the existing value rather than creating a duplicate.
Value	The content Orion remembers, e.g. "Always display revenue in GBP".
Source	How the memory was created. Items you add by hand are recorded as explicit user entries; Orion-built items carry their own source.

The five types and what each is for:

Type	Use it for	Example
`preference`	How to display or format things	"Always use GBP"
`fact`	Business truths that never change	"Fiscal year starts in February"
`instruction`	Behaviour rules for Orion to follow	"Always round to 2 decimal places"
`context`	Background that helps Orion interpret your data	"Q4 includes the holiday promo period"
`other`	Anything that doesn't fit the categories above	—

Getting started

You need the Luminary or Weaver role to open Context Studio. To reach the Orion Memory tab:

Open Context Studio

From the main navigation, go to Context Studio.

Select the Orion Memory tab

In the left-hand section list, click Orion Memory. The URL becomes /context-studio?section=memory.

Review the list

The page loads every memory for the workspace, grouped by type with a count per group.

Step-by-step

Add a memory

Click + Add memory

The + Add memory button in the header opens an inline form.

Choose a type

Pick the type from the dropdown: preference, fact, context, instruction, or other.

Enter a label

In the Label field, type a short identifier, e.g. preferred_currency. (The placeholder shows this example.)

Enter a value

In the Value box, type what Orion should remember, e.g. "Always display revenue in GBP".

Save

Click Save. The new memory appears at the top of its type group immediately. Click Cancel to discard the form without saving.

Both the label and the value are required — if either is empty, Save does nothing. If you save a memory whose type and label already exist, the existing item's value is updated rather than a second copy being created.

Delete a memory

Find the memory

Locate the card in its type group.

Click the delete control

Click the × on the right of the card. A confirmation appears: "Delete this memory? This cannot be undone."

Confirm

Confirm to remove it. The card disappears from the list. Deletion is permanent — there is no undo.

Let Orion build memory automatically

You don't have to add everything by hand. Orion builds memory on its own as people ask it questions, so over time the list fills with items Orion has inferred from real usage. The Add memory form is for things you want Orion to know up front or always honour. Review the auto-built items here periodically and delete any that no longer apply.

Examples

Suppose your team reports all revenue in British pounds and your fiscal year starts in February. Seed two memories so Orion applies both without being reminded each time.

First, a preference for currency formatting:

Type:  preference
Label: preferred_currency
Value: Always display revenue and spend in GBP (£).

Then a fact about the fiscal calendar:

Type:  fact
Label: fiscal_year_start
Value: The fiscal year starts on 1 February. "FY26" runs Feb 2026 – Jan 2027.

After saving, the preference group shows the currency item and the fact group shows the fiscal-year item, each with its label in bold and value underneath. From then on Orion can factor both into the answers it gives across the workspace.

Best practices

Use the right type. Put display and formatting rules under preference, unchanging business truths under fact, behaviour rules under instruction, and interpretive background under context. The grouping makes the list easy to scan and keeps related items together.
Keep labels short and specific. A label like preferred_currency is easier to find and update than a long sentence.
Write self-contained values. The value is what Orion reads, so make it a complete instruction or statement on its own.
Re-save to update. To change a value, add a memory with the same type and label — it overwrites the existing one instead of creating a duplicate.
Prune regularly. Review auto-built memories and delete anything stale so Orion isn't acting on outdated assumptions.

Tips

💡

Tip

Think of the three workhorse types as three questions: preference answers "how should this look?" (e.g. always use GBP), fact answers "what is always true?" (e.g. fiscal year starts in February), and instruction answers "how should Orion behave?" (e.g. always round to two decimal places).

Common mistakes

⚠️

Warning

Leaving a field blank. Both the label and the value are required. If either is empty, the Save button silently does nothing — fill in both.
Expecting an undo. Deleting a memory is permanent. The confirmation dialog warns "This cannot be undone" for a reason — only delete items you are sure about.
Creating duplicates you think are separate. A label is unique per type. Saving the same type + label again updates the existing memory; it does not add a second one.
Confusing this with memory export. This tab manages individual memory items. The separate memory export page is for taking memory in and out of the workspace, not for editing single items here.

Troubleshooting

Symptom	Cause	Fix
Page shows "Loading memory…" and never finishes	The memory list failed to load from the server	Refresh the page. If it persists, confirm your session is still valid and that you have the Luminary or Weaver role.
"Orion hasn't learned anything yet."	No memories exist for the workspace	Add one with + Add memory, or ask Orion questions so it begins building memory on its own.
Clicking Save does nothing	The label or value field is empty	Enter both a label and a value, then click Save again.
"Could not delete the memory. Please try again."	The delete request failed	Try again. If it keeps failing, refresh the page and retry the delete.
A memory you saved didn't appear as a new item	A memory with the same type and label already existed	This is expected — the existing item's value was updated. Check that group for the updated value.

Memory export — take Orion's memory in and out of the workspace
Orion — the AI analyst that reads and builds this memory
Domain skills — another way to shape how Orion reasons about your data
Context Studio overview — the full set of tabs for governing Orion's context