Which Layer Holds What
| Layer | Holds | Example |
|---|---|---|
| Project instructions | How to behave | Plain tone, ask when a figure is missing |
| Project knowledge | What is true | Current refund policy, price sheet |
| Chat message | What is new this time | This week's data |
| Connector | Live content you have permission to see | A shared drive that changes daily |
Decision Table
| If the question says... | The answer is likely... |
|---|---|
| Project answers are wrong | Check the knowledge first; stale or conflicting files are common |
| Source changes often | Connector, or replace the upload each time it changes |
| Source is stable reference material | Upload to Project knowledge |
| Instructions are long and vague | Rewrite short, specific, and checkable |
| Claude guesses when information is missing | Add a fallback rule to the instructions |
| Two versions of the same document | Remove the outdated one and name which wins |
Traps
| Trap | Correct Answer |
|---|---|
| Put facts into the instructions | Facts belong in knowledge; instructions set behavior |
| Claude will notice a stale file | It will not. You maintain the knowledge |
| Add more instructions to fix wrong answers | Fix the knowledge when the fact is wrong |
| Connect any source without thought | Consider permissions, privacy, and policy first |
If You Remember Nothing Else
- You maintain Project knowledge; stale docs lead to confidently wrong answers.
- Keep instructions short, specific, and checkable.
- Name an owner and a review date for shared Projects.
- Uploads are snapshots; connectors reach current content.