annotations/.cursor/skills/research/references/novelty-sensitivity.md

Novelty Sensitivity Assessment — Reference

Novelty Sensitivity Classification

Sensitivity Level	Typical Domains	Source Time Window	Description
Critical	AI/LLMs, blockchain, cryptocurrency	3-6 months	Technology iterates extremely fast; info from months ago may be completely outdated
High	Cloud services, frontend frameworks, API interfaces	6-12 months	Frequent version updates; must confirm current version
Medium	Programming languages, databases, operating systems	1-2 years	Relatively stable but still evolving
Low	Algorithm fundamentals, design patterns, theoretical concepts	No limit	Core principles change slowly

Critical Sensitivity Domain Special Rules

When the research topic involves the following domains, special rules must be enforced:

Trigger word identification:

• AI-related: LLM, GPT, Claude, Gemini, AI Agent, RAG, vector database, prompt engineering
• Cloud-native: Kubernetes new versions, Serverless, container runtimes
• Cutting-edge tech: Web3, quantum computing, AR/VR

Mandatory rules:

1. Search with time constraints:

   • Use time_range: "month" or time_range: "week" to limit search results
   • Prefer start_date: "YYYY-MM-DD" set to within the last 3 months

2. Elevate official source priority:

   • Must first consult official documentation, official blogs, official Changelogs
   • GitHub Release Notes, official X/Twitter announcements
   • Academic papers (arXiv and other preprint platforms)

3. Mandatory version number annotation:

   • Any technical description must annotate the current version number
   • Example: "Claude 3.5 Sonnet (claude-3-5-sonnet-20241022) supports..."
   • Prohibit vague statements like "the latest version supports..."

4. Outdated information handling:

   • Technical blogs/tutorials older than 6 months -> historical reference only, cannot serve as factual evidence
   • Version inconsistency found -> must verify current version before using
   • Obviously outdated descriptions (e.g., "will support in the future" but now already supported) -> discard directly

5. Cross-validation:

   • Highly sensitive information must be confirmed from at least 2 independent sources
   • Priority: Official docs > Official blogs > Authoritative tech media > Personal blogs

6. Official download/release page direct verification (BLOCKING):

   • Must directly visit official download pages to verify platform support (don't rely on search engine caches)
   • Use WebFetch to directly extract download page content
   • Search results about "coming soon" or "planned support" may be outdated; must verify in real time
   • Platform support is frequently changing information; cannot infer from old sources

7. Product-specific protocol/feature name search (BLOCKING):

   • Beyond searching the product name, must additionally search protocol/standard names the product supports
   • Common protocols/standards to search:
     • AI tools: MCP, ACP (Agent Client Protocol), LSP, DAP
     • Cloud services: OAuth, OIDC, SAML
     • Data exchange: GraphQL, gRPC, REST
   • Search format: "<product_name> <protocol_name> support" or "<product_name> <protocol_name> integration"

Timeliness Assessment Output Template

## Timeliness Sensitivity Assessment

- **Research Topic**: [topic]
- **Sensitivity Level**: Critical / High / Medium / Low
- **Rationale**: [why this level]
- **Source Time Window**: [X months/years]
- **Priority official sources to consult**:
  1. [Official source 1]
  2. [Official source 2]
- **Key version information to verify**:
  - [Product/technology 1]: Current version ____
  - [Product/technology 2]: Current version ____