← ClaudeAtlas

co-evolution-wikilisted

Establish and maintain a Co-Evolution Second Brain Wiki — a privacy-preserving Obsidian vault where the AI helps the owner organize projects, technologies, decisions, timeline, and self-narrative under strict write boundaries. Use when the user wants to (1) initialize a new second-brain wiki vault with the full architecture (three-layer model, five entry channels, L0–L3 tiered retrieval, seven judgment types, three-zone write boundary, inbox buffer), (2) update the wiki incrementally with the AI deciding what to keep, archive, or ignore based on source confidence and sensitivity, (3) query the wiki through tiered retrieval, or (4) maintain sync rules, schema, and verification contracts. Triggers include "建一个第二大脑", "初始化 wiki", "建立个人知识库", "wiki up", "更新知识库", "second brain wiki", "co-evolution wiki", "共进化知识库".
SiyanHub/siyan-brain-skills · ★ 3 · AI & Automation · score 69
Install: claude install-skill SiyanHub/siyan-brain-skills
# Co-Evolution Second Brain Wiki A reusable methodology and toolset for building a long-term personal (or small-team) knowledge base where the AI is a guarded co-author, not a free-hand ghostwriter. Distilled from a production second-brain vault that has been running since 2026-07. The wiki lives as an Obsidian vault. Markdown is the only source of truth. Derived retrieval indexes are disposable and rebuildable. The owner — never the AI — controls when a full update runs and what counts as identity narrative. ## Why this exists A plain "let the AI dump notes into a folder" wiki drifts within weeks: facts get overwritten, sensitive values leak, identity gets inferred from project output, contradictions get silently resolved. This skill installs the guardrails that keep a second brain trustworthy over years: - A **three-layer model** separates facts, self-narrative, and structural evolution so the AI cannot rewrite who the owner is. - A **five-channel entry map** routes every request (read-only query, global deep-dive, task sediment, self-interview, manual full maintenance) to a bounded write surface. - **Seven judgment types** and a **three-zone write boundary** decide, for every candidate fact, whether it auto-writes, needs confirmation, or must be explicitly approved. - An **inbox buffer** catches conflicts, sensitive values, ambiguous mappings, and self-narrative material instead of letting them silently land as fact. - **L0–L3 tiered retrieval** answers questions from