Memory

How Enterprise Mind stores decisions, conversations and outcomes with their sources, versions and access rules, and how it forgets.

Memory

Memory is the part of Enterprise Mind that keeps what your organisation has decided, said and learned, and keeps it attached to the records it is about. Everything else in this group, from the ledger to the approval queue, reads from it or writes to it.

This page explains how memory is built and kept. The screens that use it have their own pages: the Decision Ledger for browsing decisions, Recall for asking what happened last time, and Outcome Learning for comparing predictions with results.

Attached to records

A memory entry always points to the task, order, booking or call it came from.

Time-aware

Each entry keeps when it happened and when it was recorded.

Access-controlled

The rules that protect the original record protect its memory.

Forgets on purpose

Retention periods remove or archive entries when there is no reason to keep them.

Where memory shows up

You rarely open memory directly. It appears as the recall card on a record, as evidence on an approval card, and as the history behind a proposed rule.

Sources, versions and quotations

Memory never replaces a source with a summary. It keeps what was actually said or written, so you can check an answer against the original.

Capability	What it means for you
Original source	Open the record, message, document or call a result came from.
Message versions	If a note was edited after a decision, you see both versions and when each applied.
Exact quotations	A result can show the precise sentence it relied on, in quotation marks, not a paraphrase.
Who knew what	Each entry notes who was involved, so you can tell what a person could have known when they decided.
Access checks	A result is shown only to people who may open the original record.

Conflicts, retention and forgetting

When sources disagree

Real organisations contain conflicting information: a policy says one thing and a supervisor note another. Recall shows both with a conflict badge, names where each came from and when it applied, and leaves the call to you. A person can mark one source as the current rule; the other stays visible as history.

Retention

Entry type	Suggested default	After the period
Decisions and outcomes	24 months	Archived: searchable by administrators only
Call transcripts	90 days	Removed; the summary stays
Internal-class entries	12 months	Archived
Sensitive-class entries	Off by default	If switched on: removed at the end of the period

These are suggested starting points. Administrators set the real periods per data class in Settings.

Forgetting is a feature

Removing old entries keeps answers relevant and keeps personal data only as long as there is a reason to hold it.

Scopes: who a memory belongs to

Memory is partitioned so that nothing leaks sideways. An entry belongs to one tenant, one module and, where it matters, one role.

Scope	Meaning	Who can recall from it
Tenant	Your organisation. Never mixed with another tenant.	Only your own users
Module	Hospitality, FleetOps, Call Center and so on. Switched on per module.	Staff who hold a role in that module
Role	Entries tied to a role rather than a person when role-level learning is on.	Anyone who can see that role's work
Record	The specific task, order, booking or case an entry is about.	Anyone who can open that record

Keeping memory healthy

A memory is only as useful as it is complete and current. The Overview screen shows a few simple health signals so you can tell when something needs attention.

Signal	What it tells you	What to do
Events per week	Whether decisions are still being captured.	A sudden drop usually means a screen stopped reporting. Check Settings.
Share with a reason	How many rejections and edits carry a written reason.	Low values mean suggestions learn slowly. Ask approvers to write one line.
Outcomes linked	Share of decisions whose result is known.	Low values mean outcome learning has little to work with. Close tasks properly.
Conflicts open	Sources that disagree and nobody has settled.	Pick the current rule so people stop seeing both.
Near expiry	Entries that will be archived or removed soon.	Export what you need to keep before the date.

Where to go next

If you want to	Read
Browse and filter recorded decisions	Decision Ledger
Ask what happened in a similar case	Recall
See how predictions compare with results	Outcome Learning
Decide how far automation may go	Autonomy & Approvals
Set data classes and retention	Governance, Privacy & Voice