ki-bindinglisted

# Knowledge Islands MCP binding `ki-binding` owns the portable canonical MCP declaration, not any vendor's configuration files. The one source resolves explicit `$KI_MCP_SOURCE` first, then `$XDG_CONFIG_HOME/ki/mcp-servers.yaml` (default `~/.config/ki/mcp-servers.yaml`). Each `mcpServers` entry has a unique `name`, non-empty `clients:`, and one closed stdio or URL definition. URL entries declare one supported transport for every targeted client. The source has client tokens because it serves several clients, but a client adapter owns that client's native configuration and safe writer. This root itself audits only the vendor-neutral mcporter projection. Read [the standard](references/standards-cross-surface-binding.md), [generated rubric](references/rubric.md), and [sources](references/sources.md) for the contract. ## Operating modes ### Mode AUDIT Run `ki repo audit --skill ki-binding --repo <project>`. It checks source validity (`BIND-2`) and, only when `MCPORTER_CONFIG` selects a readable target, compares full non-secret mcporter definitions (`BIND-1`). Missing target evidence is unavailable, never a clean or health result. Judge whether each target set is intentional (`BIND-J1`). ### Mode CONFORM Run AUDIT first. Edit the canonical source, then use the renderer or client adapter that owns the target. This root never hand-edits a rendered target and proposes no writes. ### Mode EDUCATE Explain the canonical source and target separation with `ki repo educate --skill