Part 7 of 12 · 1 min read
How to build it so it holds up
- Inventory the copies (prompts, tool I/O, traces, memory, summaries, embeddings, eval sets, backups, provider logs) and give each an owner and a retention limit.
- Minimise first: build the model's context from an allowlist of fields per task.
- Tokenise before the model sees data, keep the vault and key outside prompts, logs and traces, and detokenise only at the boundary that needs the real value.
- Redact traces and logs before export (Level 9 module 8); capture prompt content only on purpose, with short retention and restricted access.
- Record lineage for every derived artefact so erasure and retention can follow it.
- Set retention by data class and enforce it with a job that you test.
- Validate detections (Luhn for cards, range checks for IPs) and measure precision and recall on your own data, per type and per language.
- Treat memory and eval datasets as data stores, with consent and deletion paths (Level 7).
- Check providers' data handling and regional rules, and document it; have the design reviewed for the laws that apply (module 10).
- Test the deletion path, including backups and caches.