central-knowledge-baselisted

# Central Knowledge Base Version-Timestamp: 2026-08-04 18:24:00 +05:00 ## Purpose Maintain a searchable, cross-agent source of truth for stable, reusable, non-secret knowledge. Resolve its location from the `YAZINC_KB_ROOT` environment variable or ask the user to approve a directory. Keep project requirements in their project repositories and keep credentials in an approved secret store. ## Classify before writing Classify every proposed item into one category: 1. `Public or reusable`: patterns, capability catalogs, non-sensitive operating guidance, and public references. These may be stored in the central KB. 2. `Internal but non-secret`: project ownership, local paths, environment names, service inventory, and runbook links. Store only the minimum necessary detail. 3. `Secret`: passwords, tokens, API keys, private keys, session cookies, connection strings containing credentials, recovery codes, or confidential authentication material. Never store these in Markdown or source control. 4. `Project-specific`: volatile requirements, active defects, client data, and implementation state. Keep these in the project repository and place only a pointer in the central KB when useful. If classification is uncertain, treat the item as confidential and do not copy it. ## Store secrets safely For secret material: - Use an approved operating-system credential store, environment variable, or secret manager. - Put only a non-secret reference in the KB, such as the secret name, owne