export declare const DEFAULT_CHUNK_TOKEN_SIZE = 500;
export declare const DEFAULT_CHUNK_OVERLAP_TOKENS = 100;
export declare const DEFAULT_CHARS_PER_TOKEN = 3.5;
export declare const CONTEXT_TARGETS: {
    DEFAULT: {
        MIN_TOKENS: number;
        MAX_TOKENS: number;
    };
    PDF: {
        MIN_TOKENS: number;
        MAX_TOKENS: number;
    };
    MATH_PDF: {
        MIN_TOKENS: number;
        MAX_TOKENS: number;
    };
    CODE: {
        MIN_TOKENS: number;
        MAX_TOKENS: number;
    };
    TECHNICAL: {
        MIN_TOKENS: number;
        MAX_TOKENS: number;
    };
};
export declare const SYSTEM_PROMPT = "You are a precision text augmentation tool. Your task is to expand a given text chunk with its direct context from a larger document. You must: 1) Keep the original chunk intact; 2) Add critical context from surrounding text; 3) Never summarize or rephrase the original chunk; 4) Create contextually rich output for improved semantic retrieval.";
export declare const SYSTEM_PROMPTS: {
    DEFAULT: string;
    CODE: string;
    PDF: string;
    MATH_PDF: string;
    TECHNICAL: string;
};
export declare const CONTEXTUAL_CHUNK_ENRICHMENT_PROMPT_TEMPLATE = "\n<document>\n{doc_content}\n</document>\n\nHere is the chunk we want to situate within the whole document:\n<chunk>\n{chunk_content}\n</chunk>\n\nCreate an enriched version of this chunk by adding critical surrounding context. Follow these guidelines:\n\n1. Identify the document's main topic and key information relevant to understanding this chunk\n2. Include 2-3 sentences before the chunk that provide essential context\n3. Include 2-3 sentences after the chunk that complete thoughts or provide resolution\n4. For technical documents, include any definitions or explanations of terms used in the chunk\n5. For narrative content, include character or setting information needed to understand the chunk\n6. Keep the original chunk text COMPLETELY INTACT and UNCHANGED in your response\n7. Do not use phrases like \"this chunk discusses\" - directly present the context\n8. The total length should be between {min_tokens} and {max_tokens} tokens\n9. Format the response as a single coherent paragraph\n\nProvide ONLY the enriched chunk text in your response:";
export declare const CACHED_CHUNK_PROMPT_TEMPLATE = "\nHere is the chunk we want to situate within the whole document:\n<chunk>\n{chunk_content}\n</chunk>\n\nCreate an enriched version of this chunk by adding critical surrounding context. Follow these guidelines:\n\n1. Identify the document's main topic and key information relevant to understanding this chunk\n2. Include 2-3 sentences before the chunk that provide essential context\n3. Include 2-3 sentences after the chunk that complete thoughts or provide resolution\n4. For technical documents, include any definitions or explanations of terms used in the chunk\n5. For narrative content, include character or setting information needed to understand the chunk\n6. Keep the original chunk text COMPLETELY INTACT and UNCHANGED in your response\n7. Do not use phrases like \"this chunk discusses\" - directly present the context\n8. The total length should be between {min_tokens} and {max_tokens} tokens\n9. Format the response as a single coherent paragraph\n\nProvide ONLY the enriched chunk text in your response:";
export declare const CACHED_CODE_CHUNK_PROMPT_TEMPLATE = "\nHere is the chunk of code we want to situate within the whole document:\n<chunk>\n{chunk_content}\n</chunk>\n\nCreate an enriched version of this code chunk by adding critical surrounding context. Follow these guidelines:\n\n1. Preserve ALL code syntax, indentation, and comments exactly as they appear\n2. Include any import statements, function definitions, or class declarations that this code depends on\n3. Add necessary type definitions or interfaces that are referenced in this chunk\n4. Include any crucial comments from elsewhere in the document that explain this code\n5. If there are key variable declarations or initializations earlier in the document, include those\n6. Keep the original chunk COMPLETELY INTACT and UNCHANGED in your response\n7. The total length should be between {min_tokens} and {max_tokens} tokens\n8. Do NOT include implementation details for functions that are only called but not defined in this chunk\n\nProvide ONLY the enriched code chunk in your response:";
export declare const CACHED_MATH_PDF_PROMPT_TEMPLATE = "\nHere is the chunk we want to situate within the whole document:\n<chunk>\n{chunk_content}\n</chunk>\n\nCreate an enriched version of this chunk by adding critical surrounding context. This document contains mathematical content that requires special handling. Follow these guidelines:\n\n1. Preserve ALL mathematical notation exactly as it appears in the chunk\n2. Include any defining equations, variables, or parameters mentioned earlier in the document that relate to this chunk\n3. Add section/subsection names or figure references if they help situate the chunk\n4. If variables or symbols are defined elsewhere in the document, include these definitions\n5. If mathematical expressions appear corrupted, try to infer their meaning from context\n6. Keep the original chunk text COMPLETELY INTACT and UNCHANGED in your response\n7. The total length should be between {min_tokens} and {max_tokens} tokens\n8. Format the response as a coherent mathematical explanation\n\nProvide ONLY the enriched chunk text in your response:";
export declare const CACHED_TECHNICAL_PROMPT_TEMPLATE = "\nHere is the chunk we want to situate within the whole document:\n<chunk>\n{chunk_content}\n</chunk>\n\nCreate an enriched version of this chunk by adding critical surrounding context. This appears to be technical documentation that requires special handling. Follow these guidelines:\n\n1. Preserve ALL technical terminology, product names, and version numbers exactly as they appear\n2. Include any prerequisite information or requirements mentioned earlier in the document\n3. Add section/subsection headings or navigation path to situate this chunk within the document structure\n4. Include any definitions of technical terms, acronyms, or jargon used in this chunk\n5. If this chunk references specific configurations, include relevant parameter explanations\n6. Keep the original chunk text COMPLETELY INTACT and UNCHANGED in your response\n7. The total length should be between {min_tokens} and {max_tokens} tokens\n8. Format the response maintaining any hierarchical structure present in the original\n\nProvide ONLY the enriched chunk text in your response:";
export declare const MATH_PDF_PROMPT_TEMPLATE = "\n<document>\n{doc_content}\n</document>\n\nHere is the chunk we want to situate within the whole document:\n<chunk>\n{chunk_content}\n</chunk>\n\nCreate an enriched version of this chunk by adding critical surrounding context. This document contains mathematical content that requires special handling. Follow these guidelines:\n\n1. Preserve ALL mathematical notation exactly as it appears in the chunk\n2. Include any defining equations, variables, or parameters mentioned earlier in the document that relate to this chunk\n3. Add section/subsection names or figure references if they help situate the chunk\n4. If variables or symbols are defined elsewhere in the document, include these definitions\n5. If mathematical expressions appear corrupted, try to infer their meaning from context\n6. Keep the original chunk text COMPLETELY INTACT and UNCHANGED in your response\n7. The total length should be between {min_tokens} and {max_tokens} tokens\n8. Format the response as a coherent mathematical explanation\n\nProvide ONLY the enriched chunk text in your response:";
export declare const CODE_PROMPT_TEMPLATE = "\n<document>\n{doc_content}\n</document>\n\nHere is the chunk of code we want to situate within the whole document:\n<chunk>\n{chunk_content}\n</chunk>\n\nCreate an enriched version of this code chunk by adding critical surrounding context. Follow these guidelines:\n\n1. Preserve ALL code syntax, indentation, and comments exactly as they appear\n2. Include any import statements, function definitions, or class declarations that this code depends on\n3. Add necessary type definitions or interfaces that are referenced in this chunk\n4. Include any crucial comments from elsewhere in the document that explain this code\n5. If there are key variable declarations or initializations earlier in the document, include those\n6. Keep the original chunk COMPLETELY INTACT and UNCHANGED in your response\n7. The total length should be between {min_tokens} and {max_tokens} tokens\n8. Do NOT include implementation details for functions that are only called but not defined in this chunk\n\nProvide ONLY the enriched code chunk in your response:";
export declare const TECHNICAL_PROMPT_TEMPLATE = "\n<document>\n{doc_content}\n</document>\n\nHere is the chunk we want to situate within the whole document:\n<chunk>\n{chunk_content}\n</chunk>\n\nCreate an enriched version of this chunk by adding critical surrounding context. This appears to be technical documentation that requires special handling. Follow these guidelines:\n\n1. Preserve ALL technical terminology, product names, and version numbers exactly as they appear\n2. Include any prerequisite information or requirements mentioned earlier in the document\n3. Add section/subsection headings or navigation path to situate this chunk within the document structure\n4. Include any definitions of technical terms, acronyms, or jargon used in this chunk\n5. If this chunk references specific configurations, include relevant parameter explanations\n6. Keep the original chunk text COMPLETELY INTACT and UNCHANGED in your response\n7. The total length should be between {min_tokens} and {max_tokens} tokens\n8. Format the response maintaining any hierarchical structure present in the original\n\nProvide ONLY the enriched chunk text in your response:";
export declare function getContextualizationPrompt(docContent: string, chunkContent: string, minTokens?: number, maxTokens?: number, promptTemplate?: string): string;
export declare function getCachingContextualizationPrompt(chunkContent: string, contentType?: string, minTokens?: number, maxTokens?: number): {
    prompt: string;
    systemPrompt: string;
};
export declare function getPromptForMimeType(mimeType: string, docContent: string, chunkContent: string): string;
export declare function getCachingPromptForMimeType(mimeType: string, chunkContent: string): {
    prompt: string;
    systemPrompt: string;
};
export declare function getChunkWithContext(chunkContent: string, generatedContext: string): string;
//# sourceMappingURL=ctx-embeddings.d.ts.map