import { SecurityService } from "../../core/security/services/security.service";
import { DataLimits } from "../types/data.limits";
import { AiSourceQueryProvider, AiSourceQueryResult } from "./ai-source-query.provider";
/** Token the app-configured (or default) provider is bound to, behind this decorator. */
export declare const INNER_AI_SOURCE_QUERY: unique symbol;
/**
 * Handbook scoping, applied in FRONT of whatever AI_SOURCE_QUERY an application
 * configured.
 *
 * WHY A DECORATOR AND NOT A BRANCH IN EACH PROVIDER
 * -------------------------------------------------
 * `aiSourceQuery` is an app-overridable bootstrap option (core.module.ts), and
 * apps do override it. A handbook branch written into a provider would
 * therefore be present in exactly the applications that remembered to write it,
 * and absent — silently, with developer documentation leaking into tenant
 * retrieval — everywhere else. Wrapping makes the isolation a property of the
 * framework rather than of each app's diligence.
 *
 * Handbook content is GLOBAL: HandbookPage nodes have no BELONGS_TO Company
 * edge, so the fragment carries no company filter, exactly as the HowTo branch
 * of DefaultAiSourceQueryProvider does.
 */
export declare class HandbookAiSourceQueryProvider implements AiSourceQueryProvider {
    private readonly inner;
    constructor(inner: AiSourceQueryProvider);
    build(params: {
        dataLimits: DataLimits;
        currentUserId?: string;
        securityService?: SecurityService;
        returnsData?: boolean;
        returnsKeyConcepts?: boolean;
    }): AiSourceQueryResult;
}
//# sourceMappingURL=handbook.ai-source-query.provider.d.ts.map