/**
 * Knowledge-gap analyst — what did the agent NOT know that it needed?
 *
 * Brief: find moments in the trace where the agent had to guess, ask
 * the user to fill in context, recover from a wrong assumption, or
 * loop on a retrieval. Each finding names a *missing or outdated piece
 * of knowledge* the agent's curated knowledge base should have held —
 * or a downstream lookup (web, docs, tool description) that surfaced
 * stale or outdated information.
 *
 * The primary expected store is `@tangle-network/agent-knowledge`: a
 * Karpathy-style wiki the agent maintains with raw ↔ curated pages,
 * source anchors, and claim/relation triples. A gap is anything the
 * agent had to discover at run-time that should already have lived
 * there. Secondary loci: web-search results that returned outdated
 * pages, tool descriptions that omitted critical behavior, system-
 * prompt sections that didn't cover the case.
 *
 * Distinct from failure-mode: failure-mode classifies *how* it broke;
 * knowledge-gap names the *information* whose absence (or staleness)
 * caused the break. One failure-mode often maps to several gaps.
 *
 * Recursion (`maxDepth: 2`) is enough to fan out one subagent per
 * candidate gap-source layer; each subagent runs a focused detection.
 */
import type { TraceAnalystKindSpec } from '../kind-factory';
export declare const KNOWLEDGE_GAP_KIND_SPEC: TraceAnalystKindSpec;
//# sourceMappingURL=knowledge-gap.d.ts.map