# Knowledge routing

Read only the files relevant to the current task.

| Task or question | Read first |
|---|---|
| Current priorities or planning | `active-projects.md` |
| Company, product, pricing, or offer questions | `company-and-offers.md` |
| Marketing or customer communication | `customers-and-audience.md`, `communication-style.md` |
| Sending, publishing, billing, or high-impact actions | `approval-and-safety-rules.md` |
| Tool or environment questions | `tools-and-environments.md`; verify live state before acting |
| Legacy decisions or migration history | `historical-reference.md` |

If a file may be stale, label the uncertainty and verify before relying on it.

Store only non-secret routing information here. Do not record passwords, tokens,
recovery codes, private keys, session cookies, or full credential values.

---

## Status header for files that change

Add this to the top of any knowledge file whose contents go stale:

---
status: active-current
last_reviewed: YYYY-MM-DD
owner: [PERSON OR AGENT]
---

Useful status labels: active-current, pending-decision, dormant,
historical-reference, deprecated.

---

## Suggested folder shape

knowledge/
├── README.md                   <- this routing map
├── active-projects.md
├── company-and-offers.md
├── customers-and-audience.md
├── communication-style.md
├── approval-and-safety-rules.md
├── tools-and-environments.md
└── historical-reference.md