Not every note task deserves the best model.
Routine maintenance should be cheap: ingest a small batch, update existing pages, add links, keep indexes current. The model needs to be consistent, not brilliant.
The stronger model should be saved for the work that needs judgment: restructuring a messy topic, resolving ambiguous merges, writing a synthesis, reviewing whether the system is still useful.
Spending intelligence evenly is lazy. The workflow should route work by risk and ambiguity.