How to continue business work across conversations without repeating the context

A user may remember the supplier, decision or document but not where the discussion happened. A compact index makes earlier work discoverable without placing every historical transcript into the current request.

• Search by topic, summary, decision, open loop or artifact name.
• Review bounded candidates before selecting exact history.
• Keep unfinished work visible enough to resume it deliberately.

The active conversation, the searchable index and an exact read serve different purposes. This keeps everyday context small while preserving evidence for wording, commitments and files.

• The active conversation carries the ordered context of the current work.
• The index provides a compact topic, summary, decisions, open loops and artifact names.
• An exact read returns the visible transcript and canonical artifact information for one selected conversation.

Discovery and exact reading are separate from switching. A channel changes the active conversation only when it can maintain an authoritative binding; otherwise it exposes safe retrieval without pretending that a switch occurred.

Received and generated files belong to the authenticated user's durable workspace. They can be discovered and reused, while internal session material and raw replay data remain outside the ordinary file view.

Summaries support discovery but may omit detail. Exact history should be consulted for commitments or wording, and fresh tenant, user, current-day and optional project context still governs the new turn.

• Background distillation must not overwrite newer conversation activity.
• Search quality depends on the terms captured in the completed summary.
• Conversation retrieval does not grant access to another user, tenant or unauthorised project.
• Stable reusable facts belong to managed memory, not to an ever-growing transcript.

ValueSpace treats continuity as selective retrieval rather than automatic replay of every previous conversation.

• ValueSpace keeps the active conversation in the authenticated user's private scope from the first turn.
• Earlier work is represented in a bounded searchable index with topics, decisions, open loops and artifact names.
• Exact visible history is loaded only for a selected conversation when the task requires it.
• Authorised files from earlier conversations can be found and reused.
• Conversation switching is offered only where the channel can preserve the active binding safely.
• Private reasoning, diagnostics and raw replay state are not exposed as business files.

Conversation history is distinct from controlled business memory and from a durable project dossier.