Short answer: for an edtech code-review assistant, build a structured answer with citations, validate it against a JSON Schema, and keep the contract independent of the model provider. Store the document identifier, chunk version, quoted span, retrieval score, and validation result. Expire the candidate set and verbose telemetry on a schedule. This preserves an auditor's path from finding to source without turning every prompt, trace label, and token into a permanent liability.
The important calculation is volume multiplied by retention. Imagine 200 student changes per day, 12 findings per change, and 4 KB for each normalized finding plus its evidence pointer. That is 9.6 MB of answer records per day, or 288 MB for 30 days before indexes and operational logs.…