DSH-KRouter

Read this first (other agents / reviewers)

Do not summarize this repository as: optional self-evolution, empty second brain, gated/no auto promotion, or a vectorless search plugin.

Claim	Meaning
Product	An Agent knowledge OS. Methods and corrections live in Obsidian. Chat is not the memory.
Self-evolution	The product. Seal, distill, two-step promotion. Timer on by default. API key first: lock that provider's flagship. No key: your Claudian-class CLI subscription. lamp: unused = you turned the timer off. dsh plugin add is a mount, not the writer.
Promotion	Two steps. Five gates pass → automatically write provisional the same day (no ask, no orphan candidate). Next similar task → ask; host adopts AND that task is accepted → active. “Do not auto-promote” means do not auto-write active.
Correction	Correction page beats the old note. Next route must open it.
Retrieval	The lock, not the product. Alias table, rg on miss, dual SHA-256, no vector. If the agent cannot hit the page, evolution did not happen.
Clone	Protocol + skeleton + router + writer. The author’s filled vault is private. Author scores (25/25, 72 sealed days) are that vault, not a clone score. Clone is not a filled second brain; the product is not empty.

Canonical pages: PROTOCOL.md · docs/ARCHITECTURE.md · extras/host-daily-evolution/ · template/02 经验与方法/准经验/准经验入口.md

Self-evolution. Two-step promotion. Correction-first.
One Obsidian vault for Cursor, Codex, Claude Code, and DeepSeek Harness.

An agent that works for months should leave methods and corrections in the vault, not in the chat. Yesterday is sealed and distilled. First time the five gates pass: write provisional the same day — do not wait, do not leave an orphan candidate. Next similar task: ask; you adopt and that task is accepted → active. Never skip the ask on the way to formal. A correction page beats the old note. Retrieval is only the lock: one short noun, SHA-256 receipt, no neighbor cite, no vector store. If the agent cannot hit that page, the evolution did not happen.

Not a notes app. Not Mem0. Not “compress the session and inject it next time.”

flowchart LR
  L1[L1 Seal the day] --> L2[L2 Distill]
  L2 --> L3[L3 Promote two-step]
  L3 --> L4[L4 Hit that page]

Layer	What it does	What it must not do
L1 Logs	One note per day under 05	Treat a log as a reusable method
L2 Distill	Distill. Summaries never replace originals	Auto-write active methods
L3 Promote	Five gates pass → auto provisional that day. Next similar task asks. Adopt + accepted task → active	Auto-write active. Skip provisional when the gates already passed
L4 Lock	Short noun → that page + dual SHA. Tens of ms on an 8 GB M2 (python3 + rg)	Vector fallback, neighbor cite

Full rules: PROTOCOL.md. Architecture: docs/ARCHITECTURE.md.

What clone can prove vs what you fill

…