Knowledge Quality

What it measures

If you removed everything from project knowledge that isn't active reference material, would anything important disappear?

The four diagnostic questions

1. 01Project knowledge contains only reference material — not output artifacts, drafts, or deliverables.
2. 02Files in project knowledge are actively referenced. Nothing sits unused across multiple sessions.
3. 03You audit project knowledge periodically and remove files that no longer serve an active purpose.
4. 04You avoid uploading large binary assets unless they are directly needed for the task.

What good looks like

Good hygiene. Continue periodic audits — entropy accumulates gradually.

Common failure mode

Project knowledge is mixing reference material with output artifacts. Deliverables, drafts, and exports belong in local storage — not ambient context.

Critique & references

Editor's notes — to be expanded

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.

• → Anthropic — Long context prompting tips
• → Lost in the Middle — context positioning effects (arXiv 2307.03172)