Personal Knowledge

Source routing

• When pk is available, run pk --help and use its authoritative commands and options.
• Otherwise, use an available connected GitHub tool to locate the user's personal-knowledge repository. Prefer an explicitly named repository; when none is named, identify it from repository purpose and root documentation instead of guessing between candidates.
• Read the repository's instructions, index, and narrowest relevant sources before answering or changing anything.

Workflow

1. Search narrowly for the requested person, preference, decision, event, responsibility, tool, or context. Treat retrieved notes as claims to validate against newer or more authoritative entries.
2. Answer from the strongest matching evidence. State when the knowledge source is unavailable, ambiguous, stale, or silent rather than filling gaps from general assumptions.
3. Create or update knowledge only when the user asks. Preserve the repository's canonical structure, terminology, links, and indexing contract.
4. Use a connected write tool only when it exposes the required repository operation. Otherwise return the exact proposed change and state that it was not persisted.