/**
 * Memory exclusion rules and write quality constants.
 *
 * Prompt sections for subject-based classification, quality enforcement,
 * and verification. Routing is by subject-based topic.
 */
/**
 * Returns true if the content looks like something that should NOT be saved
 * as long-term memory (code, git info, derivable facts, ephemeral state,
 * or diagnostic metadata).
 */
export declare function isExcludedMemoryContent(content: string): boolean;
export declare const EXCLUSION_PROMPT_SECTION = "## What NOT to save in memory\n\n- Code patterns, conventions, architecture, file paths, or project structure\n- Git history, recent changes, or who-changed-what\n- Debugging solutions or fix recipes \u2014 the fix is in the code\n- Anything already documented in project files\n- Ephemeral task details: in-progress work, temporary state, current conversation context\n- Information tools can look up in real-time (weather, time, file contents)\n- Diagnostic metadata (confidence scores, evidence paths, status markers)\n\nThese exclusions apply even when explicitly asked to save. If asked to save a list or summary, ask what was *surprising* or *non-obvious* about it.";
export declare const WRITE_QUALITY_PROMPT_SECTION = "## Memory Write Quality Rules\n\n1. **Classify by subject**: Tag each memory with a topic subject (English kebab-case, e.g. `feishu`, `philosophy`, `product`).\n2. **Absolute dates**: Convert relative dates (\"yesterday\", \"last week\") to absolute dates (2026-04-01)\n3. **Record confirmations**: When user validates an approach (\"yes exactly\", \"keep doing that\"), record it\n4. **Why + How to apply**: For feedback and project types, include WHY it matters and HOW to apply it\n5. **Don't duplicate**: If MEMORY.md already says X, don't save X again \u2014 update the existing entry";
export declare const CLASSIFICATION_PROMPT_SECTION = "## Memory Classification\n\nFor each memory, choose:\n1. **topic** (required): A subject name in English kebab-case that best categorizes this memory. Group related memories together. Examples: `feishu`, `philosophy`, `product`, `football`, `memory-system`, `ai-tools`.\n2. **type** (required): One of four categories:\n   - `user` \u2014 Personal information about the user: preferences, interests, background, personality traits, communication style, goals\n   - `feedback` \u2014 Explicit or implicit feedback about the assistant: corrections, praise, complaints, preferences about AI behavior\n   - `project` \u2014 Work/project-related information: decisions, requirements, status updates, architecture choices, constraints\n   - `reference` \u2014 Factual reference material: articles, concepts, definitions, how-to knowledge, best practices\n\nThe topic determines the file; the type determines the section within MEMORY.md.";
export declare const VERIFICATION_PROMPT_SECTION = "## Before Recommending from Memory\n\nA memory that names a specific file, function, or flag is a claim that it existed *when the memory was written*. Before recommending:\n- If the memory names a file path: check the file exists\n- If the memory names a function or flag: grep for it\n- If the user is about to act on your recommendation, verify first\n\n\"The memory says X exists\" is not the same as \"X exists now.\"";
export declare const TOPIC_FILE_FORMAT_SECTION = "## Topic File Format\n\nEach topic file lives under memory/topics/ and is named by subject (e.g. `feishu.md`, `philosophy.md`):\n\n```markdown\n---\nsubject: feishu\ncreated: YYYY-MM-DD\nupdated: YYYY-MM-DD\nentries: N\n---\n\n## Entry Title (YYYY-MM-DD)\n\nEntry content in free-form markdown.\n\n## Another Entry (YYYY-MM-DD)\n\nMore content.\n```\n\nRules:\n- Topic files are created on demand when memories are saved \u2014 no pre-created defaults\n- Frontmatter uses `subject` (kebab-case) instead of type\n- Each entry is a ## heading with title and date in parentheses\n- Entry type: optional `- **Type**: user|feedback|project|reference` line\n- Entry importance: \"high\", \"normal\" (default), or \"low\"\n- Entry source: \"session-compact\", \"memory-save\", etc.";
