Treating a knowledge base like hot and cold storage

Placeholder. This one could dig into tiered KB architecture — hot content that’s actively used and validated, cold content that’s aged out but still worth keeping, and the router logic that decides which is which.

Outline

• Why “one flat KB” breaks down at scale
• Demand-driven capture as the intake valve
• Maturity as the promotion mechanism