Auto-sync: 2026-04-16 17:30
This commit is contained in:
@@ -1,27 +0,0 @@
|
||||
---
|
||||
title: "Pattern-Key"
|
||||
type: concept
|
||||
tags: [self-improving, memory, pattern, tracking]
|
||||
last_updated: 2026-04-15
|
||||
---
|
||||
|
||||
## Definition
|
||||
经验记录(LEARNINGS.md)的唯一标识键,格式为 domain.subdomain(如 cron.telegram-delivery),用于发现重复踩坑和追踪系统性错误。
|
||||
|
||||
## Core Mechanism
|
||||
- 格式:点分层级,如 cron.daily-self-review / cron.telegram-delivery / cron.naming-convention
|
||||
- 用途:通过相同 Pattern-Key 发现同一问题的多次记录
|
||||
- 决策信号:Pattern-Key 重复出现 = 系统性问题需系统性解决,而非单点修复
|
||||
|
||||
## Example
|
||||
| Pattern-Key | 出现次数 | 含义 |
|
||||
|---|---|---|
|
||||
| cron.daily-self-review | 9次 | 每日复盘,持续活跃优化领域 |
|
||||
| cron.telegram-delivery | 2次 | Telegram 通知配置,第一次记了第二次解决 |
|
||||
|
||||
## Key Insight
|
||||
Pattern-Key 重复本身是信号——第一次记了,第二次就该解决了。Recurrence-Count ≥ 2 说明这不是偶发错误。
|
||||
|
||||
## Connections
|
||||
- [[Self-Improving Skill]] ← 核心机制 ← [[Pattern-Key]]
|
||||
- [[Recurrence-Count]] ← 量化 ← [[Pattern-Key]]
|
||||
Reference in New Issue
Block a user