| 1 | # Knowledge DOX |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | - Own built-in agent self-knowledge and repository-shipped indexed reference content. |
| 6 | - Keep internal reference material accurate for runtime recall without mixing in user-private data. |
| 7 | |
| 8 | ## Ownership |
| 9 | |
| 10 | - `main/about/` contains built-in Agent Zero self-knowledge. |
| 11 | - `fragments/`, `instruments/`, and `solutions/` are reserved knowledge roots. |
| 12 | - User-local knowledge belongs under `usr/knowledge/`. |
| 13 | |
| 14 | ## Local Contracts |
| 15 | |
| 16 | - Do not place secrets, chat transcripts, private user data, or local deployment details in repository knowledge. |
| 17 | - Keep self-knowledge consistent with current architecture, configuration, capabilities, and setup docs. |
| 18 | - Markdown here is for agent runtime context, not general marketing copy. |
| 19 | |
| 20 | ## Work Guidance |
| 21 | |
| 22 | - Update self-knowledge when durable runtime behavior, setup, configuration, or agent capabilities change. |
| 23 | - Keep entries concise and specific enough for retrieval. |
| 24 | - Prefer source-grounded statements over aspirational descriptions. |
| 25 | |
| 26 | ## Verification |
| 27 | |
| 28 | - Re-read touched source or docs before changing self-knowledge. |
| 29 | - Run any available indexing or knowledge tests when changing retrieval-sensitive structure. |
| 30 | |
| 31 | ## Child DOX Index |
| 32 | |
| 33 | No child DOX files. |