Atlas 技術版 > 🧠 Mnemosyne 每日鞏固+Digest+Skill Gate

🧠 Mnemosyne 每日鞏固+Digest+Skill Gate SCRIPT P1 risk=HIGH

1. 做什麼 / 2. 為什麼存在

Mnemosyne 每日鞏固+Digest+Skill Gate:夜間記憶鞏固管線,含 review gate monitor script。

3. Schedule / Mode

mode=SCRIPT state=scheduled enabled=1
schedule=0 3 * * *
next_run=2026-10-22T03:00:00 last_run=2026-10-17T03:01:27
deliver=telegram model=gpt-5.6-luna provider=openai-codex

4. Implementation

script=/Users/exion/.hermes/scripts/mnemosyne_daily_review_gate.py
monitor_script=mnemosyne_daily_review_gate.py monitor_url=—
skills=["cron-self-review"]
workdir=—

5. Effective instruction sources

prompt_sha256=ab35e90114af2d62… chars=2201
skill_files={}

你是排程執行的 cron job,最終回覆會自動推送 Telegram,不要呼叫 send_message。你已收到 Mnemosyne 每日 review 的 MONITOR CHANGE 區塊(digest + candidates)。

# 任務:Skill 改善「證據累積」(不是修改 Skill)

你的角色是觀察者與證據累積者,**不是** Skill 修改者。
絕對禁止修改任何 SKILL.md、禁止建立/合併/刪除 Skill、禁止改 enabled 狀態。
你這一輪的工具只有 terminal,沒有 skill_manage,這是刻意的設計。

引擎路徑(唯一合法入口):
GOV=/Users/exion/workspace/R4A_SKILL_GROWTH_GOVERNANCE_20260921/r4a_gov.py
PY=/Users/exion/venvs/vision/bin/python3

## Step 1:判斷有沒有「充分證據」的候選

從 digest 找 correction、重複錯誤、或新工作流程。
證據不足(只出現一次、環境特定、沒有可驗證的 before/after)→ 最終回覆只輸出 SKIP,什麼都不要做。
不要為了有產出而硬找。

## Step 2:有充分證據時,登記一筆 observation

把證據寫成單行 JSON,呼叫:
$PY $GOV observe --json '<單行 JSON>'

必填三個欄位:
- method_key:同一個方法必須永遠用同一個 key(例 "wiki-段落定位改用標題錨點")
- session_id:證據來自哪個 session
- evidence_ref:可回溯的證據位置(檔案路徑、log 行號、訊息 id)

建議提供的欄位(**不確定一律填 UNKNOWN,絕對不要猜、不要估**):
method_summary、outcome、target_skill、
old_method_result、new_method_result(具體可驗證的 before/after,例 "3/6 失敗" → "0/6 失敗")、
generalizability、confidence、
upstream_check(物件,含 installed_upstream_equivalent / latest_upstream_equivalent / upstream_gap)、
roi(物件,含 metric / before / after / unit / net_value)、
proof(物件,含 root_cause_proven / deterministic_failure / deterministic_fix / order_of_magnitude_improvement / correctness_defect_fixed)、
correctness_delta / token_delta / latency_delta / failure_rate_delta、
existing_skill_fit、reusable_workflow、expected_future_reuse、
persistence_target_fit、recommended_authority(authority 允許值只有 SKILL / GOVERNANCE_POLICY / HMOD / RUNBOOK / CODE_TEST / CONFIG / NONE…

6. Actual rules / thresholds

rulevaluesource
HERMES/Users/exion/.hermesCODE_STATIC @mnemosyne_daily_review_gate.py:34
MNEMO_DB/Users/exion/.hermes/mnemosyne/data/mnemosyne.dbCODE_STATIC @mnemosyne_daily_review_gate.py:35
STATE_DB/Users/exion/.hermes/state.dbCODE_STATIC @mnemosyne_daily_review_gate.py:36
SLEEP_SCRIPT/Users/exion/.hermes/scripts/mnemosyne_sleep_all.pyCODE_STATIC @mnemosyne_daily_review_gate.py:37
SIDE_VENV_PY/Users/exion/.hermes/venvs/mnemosyne/bin/python3CODE_STATIC @mnemosyne_daily_review_gate.py:38
DIGEST_DIR/Users/exion/.hermes/data/mnemosyne_daily_digestCODE_STATIC @mnemosyne_daily_review_gate.py:39
TELEMETRY/Users/exion/.hermes/data/mnemosyne_daily_digest/telemetry.jCODE_STATIC @mnemosyne_daily_review_gate.py:40
USAGE_AUDIT/Users/exion/.hermes/cron/usage_audit.jsonlCODE_STATIC @mnemosyne_daily_review_gate.py:41
NO_CANDIDATENO_CANDIDATECODE_STATIC @mnemosyne_daily_review_gate.py:43

7/8. Inputs & Outputs (resources)

kindpathnameaccess
SQLITE_DB/Users/exion/.hermes/mnemosyne/data/mnemosyne.dbunknown
SQLITE_DB/Users/exion/.hermes/state.dbunknown
SQLITE_TABLEselfworking_memoryread
SQLITE_TABLEselfsessionsread
SQLITE_TABLEselfmessagesread
SQLITE_TABLEselfsessionsread
SQLITE_TABLEselfmessagesread
SQLITE_TABLEselfsessionsread
SQLITE_TABLEselfsession_model_usageread
SQLITE_TABLEselfsessionsread
FILE_READ/Users/exion/.hermes/cron/usage_audit.jsonlread
FILE_READ/Users/exion/.hermes/data/mnemosyne_daily_digest/telemetry.jsonlread
FILE_WRITE/Users/exion/.hermes/data/mnemosyne_daily_digest/{date}.mdwrite

9/10. Upstream / Downstream

Upstream: P0-3 Phase 3: importance 重評執行(30天數據)
Downstream: —
Transitive downstream (0): —

Edges (typed evidence)

typehard?fromtoresourceoriginconfevidence
DATAsoftP0-3 Phase 3: importance 重評執行(30天數據)🧠 Mnemosyne 每日鞏固+Digest+Skill Gatesqlite:working_memorySTATIC0.75table 'working_memory' write@3440ecd342a8(line 163) -> read@2df285ab2534(line 92)

11. Shared resources

12. Recent executions

failure_streak=0
last_error=Scheduler restarted after this execution's owner exited before a durable terminal state; whether side effects ran is unknown.
delivery_error=—

14. Drift history

16. Impact / change risk

change_risk=HIGH