Spaces:
Running
Running
| # Knowledge DOX | |
| ## Purpose | |
| - Own built-in agent self-knowledge and repository-shipped indexed reference content. | |
| - Keep internal reference material accurate for runtime recall without mixing in user-private data. | |
| ## Ownership | |
| - `main/about/` contains built-in Agent Zero self-knowledge. | |
| - `fragments/`, `instruments/`, and `solutions/` are reserved knowledge roots. | |
| - User-local knowledge belongs under `usr/knowledge/`. | |
| ## Local Contracts | |
| - Do not place secrets, chat transcripts, private user data, or local deployment details in repository knowledge. | |
| - Keep self-knowledge consistent with current architecture, configuration, capabilities, and setup docs. | |
| - Markdown here is for agent runtime context, not general marketing copy. | |
| ## Work Guidance | |
| - Update self-knowledge when durable runtime behavior, setup, configuration, or agent capabilities change. | |
| - Keep entries concise and specific enough for retrieval. | |
| - Prefer source-grounded statements over aspirational descriptions. | |
| ## Verification | |
| - Re-read touched source or docs before changing self-knowledge. | |
| - Run any available indexing or knowledge tests when changing retrieval-sensitive structure. | |
| ## Child DOX Index | |
| No child DOX files. | |