| name | cognitive_evolution |
| description | Meta-method for tracking how your thinking changes — timestamped observation, paradigm shift documentation, and concept network maintenance |
| version | 1.0.0 |
| author | cubxxw |
| source | https://github.com/cubxxw/my-soul-skills |
| category | framework |
| tags | ["meta-cognition","evolution","documentation","knowledge-management","paradigm-shift"] |
| related_skills | ["self_modeling","systematization_experience","meaning_architecture"] |
| lang | zh-CN/en |
Cognitive Evolution Documentation (认知演进)
Overview
A meta-method for tracking how thinking evolves over time. Not about "what you think now" but about "how your thinking has changed and why." The core principle: never delete old views — document the evolution. This creates a living record of cognitive development that reveals patterns invisible in any single snapshot.
Core Model
Ontological Routing
All extracted knowledge must be categorized into one of three types:
- Entities — Concrete: people, places, tools, projects, companies
- Concepts — Abstract: theories, methodologies, philosophical views, architectural ideas
- Tensions — Unresolved: long-standing dilemmas or cognitive conflicts that persist
Sacred Rules
| Rule | Constraint |
|---|
| Never overwrite history | When new views conflict with old views, append a "Cognitive Shift" block — never delete the old view |
| Timestamp everything | All observations must carry source attribution and time markers |
| Weak signal protection | Concepts with insufficient evidence get marked as weak signal / tentative / emerging pattern — never prematurely promoted to stable nodes |
| Bidirectional linking | All key concepts wrapped in links to maintain the knowledge network |
Cognitive Shift SOP (认知演进处理)
When you detect a conflict between old and new views, write:
Cognitive Shift [time period]
- Original paradigm: [old view + when it formed]
- Current trigger: [new view]
- Evolution driver: [underlying cause of the shift]
- Source: [where this shift originated]
Three-Layer Evolution Pattern
Most concepts evolve through three layers:
- L1 (Tool/Phenomenon): "What is this?" — discovery and naming
- L2 (Method/Framework): "How to systematically use this?" — structuring
- L3 (Infrastructure/Being): "How does this naturally integrate?" — becoming part of the environment
Examples:
- AI: tool → workflow → runtime
- Self: identity question → agency → designable system
- Travel: experience → designed experiment → life infrastructure
Four-Phase Learning Arc
Each concept typically passes through:
- Exploration — Initial encounter and curiosity
- Integration — Connecting to existing knowledge
- Maturation — Deepening and refining understanding
- Meta-awareness — Observing your own evolution on this topic
When to Apply
- Maintaining a personal knowledge base or second brain
- Reviewing how your views have shifted over time
- Preventing "present bias" — the assumption that your current view is final
- Building knowledge systems that grow rather than just accumulate
- Recognizing patterns in how you learn and change
Key Principles
- Append, never overwrite: Old views are data about where you were — deleting them destroys the evolution record
- Timestamp is mandatory: Without temporal anchoring, you can't distinguish "what I thought then" from "what I think now"
- Protect weak signals: Premature certainty kills emerging insights — mark uncertain concepts honestly
- Concept networks over linear notes: Bidirectional links reveal relationships that linear notes hide
- Evolution is the content: The shift from one paradigm to another is more informative than either paradigm alone
- Defense mechanism detection: Watch for when system-building itself becomes a way to avoid unprocessed experience
Cognitive Evolution (Meta)
This framework itself has evolved:
- Early: Focus on knowledge capture and organization
- Later: Recognition that the evolution tracking IS the most valuable output — not the individual snapshots but the trajectory between them
Related Skills
self_modeling: Cognitive evolution tracking is how the self-as-system gets version-updatedsystematization_experience: This method is itself a system — apply its own blind-spot awareness to itselfmeaning_architecture: Evolution tracking reveals how meaning-making shifts over time
