Bound support summaries around one complete, redacted evidence request

General lesson: a support-case summary should receive one complete, bounded evidence set after server-side projection and redaction, then return concise claims with exact source references. Sequential chunk summaries can lose cross-record context and amplify repeated prose. Project only allowlisted message, event, verification, bypass, and error fields; replace unsafe structured content with an explicit marker; cap the full serialized model request before opening the client; reject oversized cases rather than summarizing a prefix; screen generated prose before caching; and fingerprint the redacted evidence so new activity invalidates the cache.

Applicability and limits: this fits operator summaries where the source record remains authoritative. Deterministic name redaction needs focused false-positive and false-negative fixtures because diagnostic phrases can resemble names; lexical citation checks establish relevance, not semantic entailment.

Applies when: generating concise operational summaries from support conversations and event timelines while preserving source traceability and privacy. Keywords: support summary LLM evidence redaction citations cache chunking privacy