Knowledge Base Governance
Version-Timestamp: 2026-08-04 13:10:00 AST
Use this skill when a user asks to add knowledge to a shared library, retrieve prior context, reconcile duplicate notes, or create a reusable source of truth.
Classification
Classify every item before writing:
Public or reusable: portable patterns, public references, non-sensitive operating guidance.Internal non-secret: local paths, service inventory, owners, project pointers, non-secret environment names.Project-specific: active requirements, defects, volatile implementation notes, and client-specific state.Secret or restricted: passwords, tokens, API keys, private keys, cookies, recovery codes, credential-bearing URLs, private customer data, or unnecessary personal information.
If unsure, treat the item as restricted and do not write it.
Storage Rules
- Store secrets in an approved secret manager, operating-system credential store, or environment variable, not Markdown.
- Store only a non-secret reference to restricted material, such as secret name, owner, system, and retrieval procedure.
- Keep active project state in the project repository. Put only stable pointers in the central knowledge base.
- Add
Version-Timestampto maintained catalogs and exported references.
Write Workflow
- Resolve the approved knowledge-base root from project instructions or user approval.
- Read local instructions in that root before editing.
- Search for an existing canonical page and aliases.
- Merge compatible facts.
- Preserve conflicting facts with status and owner instead of silently overwriting.
- Record source, owner, scope, verification date, and authority level.
- Verify the final note contains no secrets, unnecessary personal data, inaccessible assumptions, or stale commands presented as current fact.
Retrieve Workflow
- Search the knowledge base before asking for information that may already exist.
- Treat stored knowledge as a discovery layer, not proof that volatile facts remain current.
- Verify time-sensitive, security-sensitive, legal, financial, production, or client-facing details against the authoritative source.
- Report whether the answer is verified-current or memory-derived.
Duplicate Resolution
- Pick one canonical page per topic.
- Replace true duplicates with short pointers.
- Keep provenance and last verification dates.
- Do not delete disputed records without owner confirmation.
Completion Criteria
- The item belongs in shared knowledge.
- No secret or unnecessary confidential data was written.
- Source, owner, scope, and verification status are visible.
- Duplicates are resolved or explicitly tracked.
- Project-specific detail remains in the project repository.