Skip to main content

​
Overview

Organization memories are a shared layer of knowledge that Dexter draws on across every Factory in your organization. They’re authored as Markdown files, curated centrally by your organization’s administrators, and read by Dexter in every conversation, alongside the per-factory knowledge base. Use them for anything that’s true across the whole organization and shouldn’t be re-taught in every factory:
  • Corporate standards, naming conventions, and reporting formats
  • Shared vocabulary and acronyms
  • Cross-site conversion factors, costing conventions, and calendar rules
  • How the organization wants Dexter to behave by default (tone, escalation, sign-off norms)
  • References to systems and data sources used across sites (ERP, MES, PLM)

​
How They Differ from Factory Memories

Because organization memories are shared and centrally governed, they are read-only from the factory side: you can’t edit them from a Dexter conversation, and they don’t appear in the per-factory Knowledge Base views. If something in there is wrong or missing, ask your organization’s administrator to update it.
Only organization administrators can add, edit, or remove organization memories — the curation surface sits at the organization level, outside any single factory.

​
How Dexter Uses Them

Dexter treats organization memories as background context, similar to the way the factory knowledge base’s index and rules stay in view: it reads them at the start of a conversation and refers back to them when the task calls for it. When an organization memory and a factory-level rule or fact appear to conflict, Dexter surfaces the conflict rather than silently picking a side, and asks you which one governs the work in front of you. Resolutions that need to stick land in one of two places:
  • Factory-specific exception — Dexter records it in the factory knowledge base.
  • The organization-level entry is wrong — send the correction to your administrator.
Repetition is the signal for promotion: if you find yourself teaching the same correction, convention, or acronym in more than one factory’s knowledge base, ask your administrator to move it into organization memories once, for everyone.

​
Limits and Caveats

  • Not browsable from a factory. Organization memories don’t show up in the Knowledge Base tab. To find out what’s in there, ask your administrator — or ask Dexter what it’s operating on for a given topic.
  • Read-only in conversation. Dexter will not modify organization memories, even if you ask. Requests to change them get pointed at your administrator.
  • Tenant-wide by definition. Don’t put factory-specific detail in them — it bleeds into factories where it doesn’t belong. Keep those entries in the factory knowledge base.
  • Changes apply on the next conversation. Dexter reads organization memories at conversation start, so an admin edit shows up the next time you open a chat, not mid-session.

​
When to Request an Organization-Memory Change

Ask your administrator to update organization memories when:
  • The same correction keeps landing in more than one factory’s knowledge base
  • A standard, unit, or naming convention has changed organization-wide
  • A shared system (ERP, MES, PLM) has been renamed, replaced, or restructured
  • The organization wants Dexter to behave differently by default across all factories
For anything narrower than that, keep it in the factory knowledge base.