distilly

# Distilly Keep person memory local, evidence-bound, and reviewable. Use only these model-facing tools: - `distilly_get` - `distilly_ingest` - `distilly_pending` - `distilly_commit` - `distilly_correct` Do not invent a create, research, flush, capture, or review tool. Do not use shell commands or direct file writes to change Distilly state. ## Gate the runtime The installed host binding completes trusted preflight before it starts the MCP server and binds the verified briefing capacity to the runtime session. That internal result is not model-facing: do not ask the user for it or require a `HostPreflight` object in the conversation. Before any source research or `distilly_*` call, check that all five exact Distilly tools are available in the current session. Their availability is sufficient to begin; the runtime still fails closed if its trusted preflight, capacity binding, or wire handshake is invalid. If the runtime or MCP server is unavailable, any tool is missing, or a call returns a host-capability or handshake failure, report that narrow failure and stop immediately. Do not research, ingest, acquire a lease, simulate tool results, use shell commands as a fallback, or write persona content into global instruction files. ## Establish the task 1. Identify the requested person, space, scope, and whether the user wants retrieval, new research, an update, or a correction. 2. Call `distilly_get` with `action: resolve` before collecting or writing material. 3. Handle re...