Knowledge Quality
Signal-to-noise ratio in your project knowledge base.
What it measures
Project knowledge is searched on every query. Files uploaded three weeks ago and never removed are noise — they compete with useful content and degrade search quality.
If you removed everything from project knowledge that isn't active reference material, would anything important disappear?
The four diagnostic questions
- 01Project knowledge contains only reference material — not output artifacts, drafts, or deliverables.
- 02Files in project knowledge are actively referenced. Nothing sits unused across multiple sessions.
- 03You audit project knowledge periodically and remove files that no longer serve an active purpose.
- 04You avoid uploading large binary assets unless they are directly needed for the task.
What it looks like when it works
Good hygiene. Continue periodic audits — entropy accumulates gradually.
What goes wrong
Project knowledge is mixing reference material with output artifacts. Deliverables, drafts, and exports belong in local storage — not ambient context.
Critique & references
Treats project knowledge as an epistemological boundary: reference material vs. output artifacts. Mixing them creates ambient noise that dilutes attention weights across irrelevant tokens — a measurable degradation, not a stylistic concern.