How business memory keeps preferences and priorities under your control

Conversations preserve what was said. Managed memory preserves the concise facts and operating context that should influence later work, such as an approved terminology rule, a recurring preference or the current status of an authorised project.

• Do not use memory for credentials, transient chat or large reference catalogues.
• Keep reusable procedures in skills rather than treating them as remembered facts.
• Retrieve exact conversation history when wording or a commitment matters.

Business-wide context, one person's preferences, today's priorities and one project's dossier have different audiences. Only the applicable chain is used for the current request.

• Tenant memory contains shared business identity, terminology and policies.
• User memory contains private durable preferences, responsibilities and recurring goals.
• Today context contains current priorities, waiting items, risks and follow-up.
• Project memory contains the current authorised dossier, files and open questions for one project.

The user can ask what ValueSpace remembers, add an explicit fact, correct it, forget it when allowed or disable memory use and extraction for the current conversation. Managed memory changes pass the same checks instead of being edited as ordinary files.

The nightly review separates memory consolidation from business critique. Supported facts can be promoted after deterministic checks, while non-urgent advice waits for the next normal interaction and only concrete time-sensitive risks can appear as alerts.

Every managed item retains its origin. Owner statements, trusted system records, assistant-derived material and untrusted imports are not equivalent, and unknown content never becomes owner-confirmed by default.

• Secrets are rejected as memory.
• Sensitive personal memory requires explicit approval.
• A nightly change can be rolled back only when a later edit would not be overwritten.
• The nightly baseline consolidates and critiques; broader adaptive self-modification is not a current capability.
• Memory never overrides authorisation, tenant isolation or approval rules.

ValueSpace uses controlled, scoped memory to improve continuity while keeping the owner and existing authorisation rules in control.

• ValueSpace separates tenant, user, current-day and project memory.
• The owner can inspect, add, correct, forget or temporarily disable memory.
• Broader supporting memory is retrieved only when needed and returns bounded evidence.
• Every managed memory item retains its source and trust class.
• The nightly review promotes only facts that pass evidence, confidence, scope and provenance checks.
• Nightly follow-up does not initiate a chat, and only urgent concrete risks are projected to Business Space alerts.

See how this differs from conversation continuity and how project-specific context belongs to a controlled project workspace.