knowledge-context-protocol

Use an existing KCP knowledge.yaml to find and load only the relevant knowledge for a task, instead of exploring a repository or docs site blind. Use when a project contains a knowledge.yaml (or a /.well-known/knowledge.yaml) and you need to answer a question or locate the right files efficiently.

Add a Knowledge Context Protocol (KCP) knowledge.yaml manifest to a codebase or documentation set so AI agents navigate it by intent instead of exploring blindly. Use when someone wants to make a repository "agent-ready", cut an agent's tool calls and context spend, adopt KCP, or upgrade an llms.txt to structured knowledge metadata.

Write or improve units in a KCP knowledge.yaml manifest — effective intents, triggers, relationships, audience targeting, negative-space (not_for), and temporal validity — and validate them. Use when editing a knowledge.yaml, when an agent keeps loading the wrong unit for a task, or when manifest queries return poor matches.

Safely ingest a third-party or untrusted KCP knowledge.yaml by running the trusted render pipeline (kcp render) before any of its content reaches the agent. Use when encountering a knowledge.yaml from a repository you do not control, an external/federated source, an unsigned manifest, or any manifest whose author you do not trust.