/**
 * Shared keyword maps and patterns used by both the free-form intent
 * interpreter and the per-clause intent interpreter. Single-sourced here
 * so both modules stay in sync without duplication.
 */
import type { Lens } from "../types/lens.js";
/** Maps normalised keyword fragments → Lens. Longer/more-specific entries first. */
export declare const LENS_KEYWORD_MAP: Array<{
    keywords: string[];
    lens: Lens;
}>;
/**
 * A scope-emphasis clause's polarity: does the user want this scope IN focus
 * ("focus on X", "only audit X") or OUT of it ("ignore X", "skip X")? Consumers
 * that boost/deboost by scope match (e.g. intentOrdering.ts) must never conflate
 * the two (COR-a0648a7d / COR-a0648a7d-2) — the sign convention is exactly
 * inverted, or ignored, when the lead-in verb's polarity is discarded.
 */
export type ScopePolarity = "include" | "exclude";
/** Patterns that signal scope emphasis (focus/ignore/prioritise) — the
 * polarity-blind view existing callers (clauseInterpreter.ts) consume, derived
 * from {@link SCOPE_PATTERN_ENTRIES} so it can never diverge from the
 * polarity-tagged set below. */
export declare const SCOPE_PATTERNS: RegExp[];
/**
 * The polarity of the FIRST scope-emphasis pattern a clause matches, or `null`
 * when the clause matches none (mirrors the match order `SCOPE_PATTERNS` itself
 * is scanned in, so polarity and match-detection can never disagree on which
 * pattern "won").
 */
export declare function scopeClausePolarity(clause: string): ScopePolarity | null;
/** Patterns that signal urgency / priority. */
export declare const PRIORITY_PATTERNS: RegExp[];
//# sourceMappingURL=sharedIntentData.d.ts.map