Repository navigation
Parked: evaluate minimized case summaries beyond references-only context #52
Description
Status
Deferred. The active memory plan is references-only; do not replace it or start retaining conversation text as a shortcut.
Problem
A long-running case may eventually need a concise record of attempted steps and unresolved questions. The need and benefit must be demonstrated after the references-only pilot, not assumed.
Acceptance when resumed
- First establish what the approved live-reference context cannot cover and whether a summary is necessary.
- Obtain explicit retention, deletion, processor and security approval for any additional stored content.
- Keep customer/case ownership enforced outside the model, minimize content, preserve uncertainty and support erasure/expiry.
- Never promote a summary or a customer/staff statement into product truth or training data.
- Test cross-customer isolation, injected instructions, edits/deletions, expiry, opt-out, restarts and optional-feature failure fallback.
Gate
Product/privacy review before implementation or capture. No data retention is enabled by this issue.
Activity
aryanorastar commentedon Oct 24, 2026
Status check — main
16ee8ca, 2026-10-24Not built, by design. Nothing in main stores case summaries or message text.
Done (the references-only memory this issue must follow)
SUPPORT_MEMORY_ENABLED,SUPPORT_MEMORY_POLICY_APPROVED,SUPPORT_MEMORY_CONTEXT_ENABLED,SUPPORT_MEMORY_FORUM_IDS) are off in production.Not done
Related PRs: #61, #60, #73, #74 (all merged, all features off).
When picked: only after the pilot has run and shown a concrete gap. Then go through retention, deletion and processor approval before any stored content.
aryanorastar commentedon Oct 25, 2026
Closing as not planned for the current product version after Aryan's October 25 request to audit completed and deliberately dropped scope.
The adopted memory design is references-only with live, owner-scoped context. No pilot evidence currently establishes a need for additional stored conversation summaries. Building that extra content-retention path now would duplicate the context workflow and introduce an unapproved data lifecycle.
This is a scope decision, not an implementation, customer-resolution or erasure claim. Preserve the issue/history and existing encryption for unrelated identity/order records. If the references-only pilot later demonstrates a specific gap, propose that narrowly, with a necessity assessment and separate retention/deletion/processor/security approval before implementation. Required memory, isolation, forgetting and reviewed-improvement work remain in the master plan; #85's existing operational-metadata policy work remains open.