Self-evolving second brain with 35 AI skills, 10 agents, and people CRM. Closed-loop harness: a V-model verification lifecycle where the worker never grades its own homework. Plus paired anti-slop design skills for marketing and product UI. Works with Claude Code, Cursor, Kiro, Gemini CLI, Codex.
Python agent-loopagent-pluginsagent-skillsagenticai-agentsclaude-codeclosed-loopcursorgarry-tangbraingstackknowledge-managementloop-engineeringobsidianpeople-crmproductivitysecond-brainself-evolvingverification-harnessworker-agents
Initial COG setup: Self-evolving second brain with Claude + Obsidian + Git
Huy Tieu95b8f32a2447
diff --git a/.claude/commands/braindump.md b/.claude/commands/braindump.mdnew file mode 100644index 0000000..2d8d05b--- /dev/null+++ b/.claude/commands/braindump.md@@ -0,0 +1,268 @@+# Brain Dump Command++## Purpose+Quick capture and initial processing of stream-of-consciousness thoughts, ideas, and insights with immediate domain classification and basic structuring.++## Command: `/braindump`++## Process Flow++### 1. Rapid Capture+- Accept any format: voice, text, scattered thoughts+- No judgment or filtering during initial capture+- Preserve original voice and spontaneity+- Capture timestamp and context++### 2. Initial Processing+- Basic cleanup and structure without losing authenticity+- Identify main themes and concepts+- Extract obvious action items or decisions+- Note emotional tone and energy level++### 3. Quick Domain Classification+- **Personal:** Individual growth, relationships, wellness+- **Professional:** Work, leadership, career development+- **Project-Specific:** Related to specific projects or initiatives+- **Mixed/Unclear:** Requires further analysis++### 4. Competitive Intelligence Detection (Optional)+**If user has projects with competitive tracking, automatically extract and update:**+- **Trigger Keywords**: User-defined competitor names, funding rounds, product launches+- **Action**: Extract competitor information to `04-projects/[project-name]/competitive/[competitor-name].md`+- **Update**: Add dated entry to existing competitor file or create new one+- **Cross-reference**: Link back to original braindump source++### 5. Immediate Structuring+- Separate different topics or themes+- Identify questions vs. statements vs. ideas+- Flag urgent items requiring immediate attention+- Note connections to existing knowledge++### 6. Output Generation+- Save to appropriate domain braindump folder+- Tag for later analysis by brain-dump-analysis command+- Create quick summary for immediate reference++## Metadata Template+```yaml+---+type: "braindump"+domain: "[personal|professional|project-specific|mixed]"+project: "[project-name]" # Only if project-specific+date: "YYYY-MM-DD"+created: "YYYY-MM-DD HH:MM"+capture_method: "[voice|text|mixed]"+energy_level: "[high|medium|low]"+emotional_tone: "[excited|frustrated|curious|concerned|neutral]"+themes: ["theme1", "theme2", "theme3"]+urgency: "[immediate|soon|eventual|none]"+analysis_needed: [true|false]+tags: ["#braindump", "#raw-thoughts", "#domain-tag"]+status: "[captured|needs-analysis|processed]"+---+```++## Capture Guidelines++### What to Include+- **Stream of Consciousness:** Raw, unfiltered thoughts+- **Ideas and Insights:** Creative thoughts and realizations+- **Problems and Challenges:** Issues you're wrestling with+- **Questions:** Things you're wondering about+- **Decisions:** Choices you're considering+- **Observations:** Things you've noticed or learned+- **Emotions:** How you're feeling about situations+- **Connections:** Links between different concepts++### What NOT to Filter+- **Incomplete Thoughts:** Half-formed ideas are valuable+- **Contradictions:** Conflicting thoughts show thinking process+- **Repetition:** Recurring themes indicate importance+- **Tangents:** Side thoughts often contain insights+- **Emotions:** Feelings provide important context+- **Questions:** Uncertainty is part of the process++## Domain Classification Quick Guide++### Personal Domain Indicators+- Family, relationships, personal health+- Individual goals and aspirations+- Personal learning and growth+- Life balance and satisfaction+- Personal values and beliefs++### Professional Domain Indicators+- Work projects and responsibilities+- Team dynamics and leadership+- Career development and skills+- Professional relationships+- Industry trends and opportunities++### Project-Specific Indicators+- Specific product or initiative names+- Technical implementation details+- Project timelines and milestones+- Project team members+- Project-specific metrics or goals++### Mixed Domain Indicators+- Cross-cutting themes affecting multiple areas+- Life philosophy and principles+- Time management and productivity+- Learning and skill development+- Strategic thinking and planning++## Processing Levels++### Level 1: Raw Capture (This Command)+- Immediate capture with minimal processing+- Basic domain classification+- Simple structuring and cleanup+- Quick metadata tagging++### Level 2: Analysis Processing (brain-dump-analysis command)+- Deep thematic analysis+- Strategic insight extraction+- Knowledge base integration+- Actionable recommendation generation++### Level 3: Knowledge Integration (consolidation command)+- Pattern recognition across multiple braindumps+- Framework development from insights+- Timeline narrative creation+- Single source of truth updates++## Output Structure++### 1. Original Capture+```markdown+## Raw Thoughts+[Preserve original voice and flow]+```++### 2. Quick Structure+```markdown+## Main Themes+- Theme 1: Brief description+- Theme 2: Brief description+- Theme 3: Brief description++## Action Items+- [ ] Urgent item requiring immediate attention+- [ ] Important item for this week+- [ ] Future consideration++## Questions+- Question 1 requiring research or thought+- Question 2 needing discussion with others+- Question 3 for future exploration++## Connections+- Link to existing project or knowledge+- Relationship to previous braindumps+- Connection to current priorities+```++### 3. Processing Notes+```markdown+## Processing Notes+- Domain: [Classification reasoning]+- Energy: [Energy level during capture]+- Context: [Situational context if relevant]+- Next Steps: [Immediate follow-up needed]+```++## File Naming Convention+- **Personal:** `02-personal/braindumps/braindump-YYYY-MM-DD-HHMM-<title>.md`+- **Professional:** `03-professional/braindumps/braindump-YYYY-MM-DD-HHMM-<title>.md`+- **Project-Specific:** `04-projects/[project]/braindumps/braindump-YYYY-MM-DD-HHMM-<title>.md`+- **Mixed:** `00-inbox/braindump-YYYY-MM-DD-HHMM-<title>.md` (for later classification)++## Quality Guidelines++### Authenticity Preservation+- Maintain original voice and tone+- Preserve emotional context and energy+- Keep incomplete thoughts and questions+- Don't over-structure or sanitize++### Useful Structure+- Separate clearly different topics+- Identify actionable items+- Note time-sensitive elements+- Flag items needing follow-up++### Context Capture+- Note situational context if relevant+- Capture emotional state and energy level+- Record any triggering events or conversations+- Include relevant background information++## Integration with Other Commands++### Immediate Follow-up+- Use `/brain-dump-analysis` for deeper processing+- Use `/daily-checkin` to reflect on themes+- Use `/project-analysis` if project-specific insights emerge++### Scheduled Processing+- Weekly review of accumulated braindumps+- Monthly pattern analysis across braindumps+- Quarterly integration into knowledge consolidation++### Cross-Reference Creation+- Link to related previous braindumps+- Connect to relevant project documents+- Reference related insights and frameworks++## Common Use Cases++### Problem-Solving Sessions+- Capture all aspects of a complex problem+- Record different solution approaches+- Note pros and cons of various options+- Document decision-making process++### Creative Ideation+- Capture creative ideas without judgment+- Record inspiration sources and triggers+- Note connections between different concepts+- Preserve creative energy and enthusiasm++### Strategic Thinking+- Process complex strategic decisions+- Explore different scenarios and implications+- Consider stakeholder perspectives+- Work through strategic trade-offs++### Learning Integration+- Process new information and insights+- Connect learning to existing knowledge+- Identify application opportunities+- Note questions for further exploration++### Emotional Processing+- Work through challenging situations+- Process feedback or difficult conversations+- Explore personal reactions and responses+- Identify patterns in emotional responses++## Success Metrics++### Capture Effectiveness+- Speed of capture (minimize friction)+- Completeness of thought capture+- Preservation of original voice and energy+- Useful structure without over-processing++### Processing Value+- Actionable items identified+- Useful connections made+- Appropriate domain classification+- Effective preparation for deeper analysis++### Integration Success+- Successful handoff to analysis commands+- Useful input for knowledge consolidation+- Effective cross-referencing with existing content+- Valuable contribution to overall system learningdiff --git a/.claude/commands/daily-brief.md b/.claude/commands/daily-brief.mdnew file mode 100644index 0000000..0791333--- /dev/null+++ b/.claude/commands/daily-brief.md@@ -0,0 +1,100 @@+# Daily Brief Command++## Purpose+Generate personalized daily news briefing with verified, current information tailored to user's interests and strategic priorities.++## Command: `/daily-brief`++## Process Flow++### 1. Interest Analysis+- Scan user files to build/update interest profile+- Analyze recent braindumps and project activities+- Identify current strategic priorities and focus areas+- Update interest weighting based on recent patterns++### 2. News Curation (VERIFICATION REQUIRED)+- Search for verified news from **last 7 days ONLY**+- Cross-reference multiple credible sources+- Verify publication dates and source credibility+- Filter for strategic relevance to user's interests++### 3. Strategic Analysis+- Connect news to user's specific projects and goals+- Identify potential impacts on current initiatives+- Highlight opportunities and threats+- Generate strategic insights++### 4. Verification Protocol+- Confirm all dates are within last 7 days+- Verify sources are credible and cross-referenced+- If information cannot be verified, explicitly state uncertainty+- Ask user for clarification on unclear interests or priorities++### 5. Output Generation+- Save to `01-daily/briefs/daily-brief-YYYY-MM-DD.md`+- Include proper Obsidian metadata+- Structure for easy scanning and action+- Include clickable source links for ALL claims+- Add comprehensive Sources section++## Metadata Template+```yaml+---+type: daily-brief+domain: shared+date: YYYY-MM-DD+created: YYYY-MM-DD HH:MM+sources_verified: true+news_age_verified: true+confidence: high+tags: ["#daily-brief", "#news", "#strategic-intelligence"]+interests: [interest1, interest2, interest3]+projects_referenced: [project1, project2]+---+```++## Content Structure+1. **Executive Summary** - Key themes and priorities for the day+2. **Strategic News** - Verified news relevant to user's projects (with source links)+3. **Market Intelligence** - Industry trends and competitive landscape (with source links)+4. **Opportunities** - Notable insights and potential initiatives+5. **Risks & Threats** - Potential challenges requiring attention+6. **Follow-Up Actions** - Suggested next steps based on intelligence+7. **Sources** - Comprehensive categorized list of all referenced materials++## Verification Standards+- **News Age**: Must be from last 7 days with verified publication dates+- **Source Credibility**: Cross-reference minimum 2 credible sources+- **Source Attribution**: Every claim, statistic, and reference MUST include clickable source link+- **Statistical Verification**: ALL statistics must be verified by reading the cited source+ - Use WebFetch tool to retrieve and verify source content+ - If statistic cannot be found, DO NOT include it or find correct source+ - Document verification method in metadata+- **Uncertainty Handling**: Explicitly state when information cannot be verified+- **User Clarification**: Request clarification for ambiguous interests++## Error Handling+- If no recent news found, state explicitly rather than fabricate+- If sources cannot be verified, mark as unverified and explain+- If user interests are unclear, ask for clarification+- If external APIs fail, inform user and suggest manual verification++## Learning Integration+- Track which news types user engages with most+- Adapt content focus based on user feedback+- Build understanding of strategic priorities over time+- Refine interest profile automatically++## Quality Metrics+- All news from last 7 days (100% compliance)+- Minimum 2 source cross-references per major claim+- Strategic relevance score (based on user engagement)+- Actionability index (% of insights leading to action)++## Common Use Cases+- Morning intelligence briefing before workday starts+- Pre-meeting preparation with relevant industry context+- Competitive intelligence gathering+- Opportunity identification and threat monitoring+- Strategic decision supportdiff --git a/.claude/commands/knowledge-consolidation.md b/.claude/commands/knowledge-consolidation.mdnew file mode 100644index 0000000..9777c11--- /dev/null+++ b/.claude/commands/knowledge-consolidation.md@@ -0,0 +1,263 @@+# Knowledge Consolidation Command++## Purpose+Transform scattered insights from braindumps, daily briefs, and check-ins into coherent frameworks and "single source of truth" knowledge documents.++## Command: `/consolidate-knowledge`++## Process Flow++### 1. Data Gathering+- Scan all braindumps since last consolidation+- Review daily briefs and check-ins+- Analyze meeting transcripts and project documents+- Identify unprocessed or partially processed content++### 2. Pattern Recognition+- Identify recurring themes and concepts+- Detect evolution of thinking over time+- Recognize contradictions or shifts in perspective+- Group related insights across documents++### 3. Framework Development+- Synthesize scattered insights into coherent principles+- Build mental models from accumulated learnings+- Create decision-making frameworks+- Develop strategic approaches from patterns++### 4. Knowledge Integration+- Update existing "single source of truth" documents+- Create new consolidated knowledge files as needed+- Cross-reference with existing frameworks+- Maintain timeline of thinking evolution++### 5. Cleanup and Archival+- Mark processed braindumps appropriately+- Archive outdated or superseded insights+- Remove redundancy while preserving important context+- Maintain clean, current knowledge base++### 6. Output Generation+- Save consolidated insights to `05-knowledge/consolidated/`+- Create timeline entries in `05-knowledge/timeline/`+- Update pattern documentation in `05-knowledge/patterns/`++## Metadata Template+```yaml+---+type: knowledge-consolidation+domain: integrated+date: YYYY-MM-DD+consolidation_period: "YYYY-MM-DD to YYYY-MM-DD"+created: YYYY-MM-DD HH:MM+sources_analyzed: [number]+frameworks_updated: [framework1, framework2]+new_insights: [number]+tags: ["#consolidation", "#knowledge", "#frameworks"]+---+```++## Content Structure++### 1. Consolidation Summary+```markdown+## Executive Summary+- Period analyzed: [Start date] to [End date]+- Documents processed: [number] braindumps, [number] briefs, [number] check-ins+- Major themes identified: [list]+- Frameworks updated/created: [list]+- Key insights synthesized: [list]++## Processing Statistics+- Total documents analyzed: [number]+- New patterns identified: [number]+- Frameworks updated: [number]+- New frameworks created: [number]+- Archive actions taken: [number]+```++### 2. Pattern Analysis+```markdown+## Recurring Themes+### Theme 1: [Name]+- **Frequency**: Appeared in [X] documents+- **Evolution**: How thinking evolved over period+- **Key Insights**:+ - Insight 1 with source references+ - Insight 2 with source references+- **Framework Implications**: How this affects existing frameworks++### Theme 2: [Name]+[Same structure as Theme 1]++## Cross-Cutting Patterns+- Pattern 1: Description and significance+- Pattern 2: Description and significance++## Contradictions and Shifts+- What changed: Description of thinking evolution+- Why it changed: Contributing factors and insights+- Resolution: Current understanding or framework+```++### 3. Framework Updates+```markdown+## Updated Frameworks++### Framework 1: [Name]+**Location**: `05-knowledge/consolidated/[filename].md`++**What Changed**:+- Addition/modification 1+- Addition/modification 2++**Supporting Insights**:+- Source insight 1 [link to braindump]+- Source insight 2 [link to braindump]++**New Applications**:+- How to apply this framework+- Specific use cases++### Framework 2: [Name]+[Same structure as Framework 1]++## New Frameworks Created++### New Framework: [Name]+**Created**: Based on [X] insights from [timeframe]++**Core Principles**:+1. Principle 1+2. Principle 2+3. Principle 3++**Supporting Evidence**:+- Evidence 1 [link]+- Evidence 2 [link]++**Application**:+- Use case 1+- Use case 2+```++### 4. Timeline Entry+```markdown+## Thinking Evolution Timeline++### [Date Range]: [Major Theme/Shift]+**What Changed**: Description of evolution++**Catalysts**:+- Event/insight 1 that triggered change+- Event/insight 2 that triggered change++**Evidence Trail**:+- [Date] - Early thinking [link]+- [Date] - Intermediate development [link]+- [Date] - Current understanding [link]++**Impact**:+- How this shift affects decisions+- How this shift affects strategies+- How this shift affects frameworks+```++### 5. Action Items+```markdown+## Knowledge Base Maintenance++### Updates Made+- [X] Updated framework: [name]+- [X] Created new consolidated doc: [name]+- [X] Archived outdated insights: [list]++### Future Consolidation Needs+- [ ] Area 1 needs deeper analysis (target: [date])+- [ ] Area 2 has contradictions to resolve (target: [date])+- [ ] Area 3 ready for framework creation (target: [date])++### Cross-Reference Updates+- [ ] Update document 1 with new insights+- [ ] Link document 2 to consolidated framework+```++## Consolidation Guidelines++### Quality Over Quantity+- Don't force insights that aren't mature enough+- Let patterns emerge naturally from evidence+- Be patient with incomplete thinking+- Quality frameworks require time and evidence++### Preserve Nuance+- Don't over-simplify complex insights+- Maintain important context and conditions+- Note when frameworks have limitations+- Preserve contradictions that haven't resolved++### Maintain Traceability+- Always link back to source documents+- Show evidence trail for frameworks+- Document evolution of thinking+- Enable future validation or revision++### Living Documents+- Frameworks should evolve with new insights+- Regular updates better than perfect first draft+- Mark frameworks as "working" vs "stable"+- Encourage iteration and refinement++## Analysis Techniques++### Pattern Detection+1. **Frequency Analysis**: What comes up repeatedly?+2. **Temporal Clustering**: What insights emerged together?+3. **Domain Correlation**: What patterns cross domains?+4. **Contradiction Analysis**: Where does thinking conflict?++### Framework Synthesis+1. **Identify Core Principles**: What are the fundamental truths?+2. **Test Against Evidence**: Do source insights support principles?+3. **Define Boundaries**: When does framework apply/not apply?+4. **Create Applications**: How to use this framework?++### Timeline Construction+1. **Mark Inflection Points**: When did thinking shift?+2. **Identify Catalysts**: What triggered changes?+3. **Document Evolution**: How did understanding develop?+4. **Extract Learnings**: What does evolution teach us?++## Output Locations++### Consolidated Knowledge+`05-knowledge/consolidated/[domain]-[topic]-YYYY-MM-DD.md`+- Synthesized insights and frameworks+- "Single source of truth" documents+- Living documents that evolve++### Pattern Documentation+`05-knowledge/patterns/pattern-[name]-YYYY-MM-DD.md`+- Recurring patterns across domains+- Cross-domain correlations+- Behavioral and thinking patterns++### Timeline Narratives+`05-knowledge/timeline/[topic]-evolution-YYYY-MM-DD.md`+- Evolution of thinking over time+- Inflection points and catalysts+- Learning from thinking progression++## Success Metrics+- Completeness: All relevant insights processed+- Coherence: Frameworks logically consistent+- Traceability: Clear links to source material+- Actionability: Frameworks applicable to decisions+- Evolution: Documented thinking progression++## Common Use Cases+- Weekly consolidation of daily insights+- Monthly framework development+- Quarterly strategic synthesis+- Annual knowledge base cleanup+- Pre-decision framework consultationdiff --git a/.claude/commands/weekly-checkin.md b/.claude/commands/weekly-checkin.mdnew file mode 100644index 0000000..daab6b9--- /dev/null+++ b/.claude/commands/weekly-checkin.md@@ -0,0 +1,196 @@+# Weekly Check-in Command++## Purpose+Comprehensive weekly review and analysis integrating insights across all domains (personal, professional, projects) with pattern recognition and strategic planning.++## Command: `/weekly-checkin`++## Process Flow++### 1. Data Collection+- Gather all content from the past week:+ - Daily briefs and check-ins+ - Braindumps and analyses+ - Project updates and milestones+ - Meeting notes and transcripts++### 2. Cross-Domain Analysis+- **Personal Domain Review**+ - Wellness and energy patterns+ - Personal goal progress+ - Relationship dynamics+ - Learning and growth areas++- **Professional Domain Review**+ - Work accomplishments and challenges+ - Team dynamics and leadership insights+ - Career development progress+ - Professional relationships++- **Project Domain Review**+ - Project progress and blockers+ - Competitive intelligence updates+ - Metric tracking and trends+ - Strategic pivots or decisions++### 3. Pattern Recognition+- Identify recurring themes across domains+- Detect emotional or energy patterns+- Recognize productivity cycles+- Spot cross-domain correlations+ - How personal wellness affects professional performance+ - How professional stress impacts personal well-being+ - How project excitement drives overall energy++### 4. Strategic Insights+- Synthesize learnings into actionable insights+- Identify opportunities for improvement+- Highlight wins and celebrate progress+- Flag areas requiring attention or intervention++### 5. Forward Planning+- Set priorities for upcoming week+- Carry forward unresolved items+- Schedule follow-up actions+- Adjust strategies based on learnings++### 6. Output Generation+- Save to `01-daily/checkins/weekly-checkin-YYYY-MM-DD.md`+- Include comprehensive metadata+- Structure for reflection and action++## Metadata Template+```yaml+---+type: weekly-checkin+domain: integrated+date: YYYY-MM-DD+week_of: YYYY-MM-DD+created: YYYY-MM-DD HH:MM+confidence: high+tags: ["#weekly-checkin", "#reflection", "#strategic-planning"]+domains_analyzed: ["personal", "professional", "projects"]+braindumps_reviewed: [number]+patterns_identified: [pattern1, pattern2, pattern3]+---+```++## Content Structure++### 1. Week in Review+```markdown+## Executive Summary+- Overall week assessment (1-5 scale with reasoning)+- Key highlights and wins+- Major challenges encountered+- Dominant emotional/energy patterns++## Domain Summaries+### Personal+- Wellness and self-care+- Relationships and connections+- Personal goals progress+- Learning and growth++### Professional+- Work accomplishments+- Team dynamics+- Leadership actions+- Career development++### Projects+- [Project Name 1]: Progress, blockers, next steps+- [Project Name 2]: Progress, blockers, next steps+```++### 2. Pattern Analysis+```markdown+## Recurring Themes+- Theme 1: Description and significance+- Theme 2: Description and significance+- Theme 3: Description and significance++## Cross-Domain Insights+- How personal wellness correlated with professional productivity+- How project challenges affected overall energy+- How learning in one domain applied to others++## Productivity Patterns+- Most productive days/times+- Energy level variations+- Factors that enhanced focus+- Factors that decreased effectiveness+```++### 3. Strategic Insights+```markdown+## What Worked Well+- Strategy/approach 1 and why it worked+- Strategy/approach 2 and why it worked++## What Needs Adjustment+- Area 1 requiring change and proposed approach+- Area 2 requiring change and proposed approach++## Opportunities Identified+- Opportunity 1 and potential action+- Opportunity 2 and potential action++## Risks/Threats+- Risk 1 and mitigation strategy+- Risk 2 and mitigation strategy+```++### 4. Forward Planning+```markdown+## Priorities for Next Week+1. Priority 1 (domain: [personal|professional|project])+2. Priority 2 (domain: [personal|professional|project])+3. Priority 3 (domain: [personal|professional|project])++## Carry Forward Items+- [ ] Unresolved item 1 from this week+- [ ] Unresolved item 2 from this week++## Experiments to Try+- Experiment 1: Hypothesis and measurement approach+- Experiment 2: Hypothesis and measurement approach++## Success Criteria for Next Week+- Measurable outcome 1+- Measurable outcome 2+- Measurable outcome 3+```++## Analysis Guidelines++### Honesty and Objectivity+- Be brutally honest about what worked and what didn't+- Avoid sugar-coating challenges or failures+- Celebrate wins genuinely without exaggeration+- Acknowledge emotional states without judgment++### Cross-Domain Connections+- Actively look for correlations between domains+- Note how actions in one area affect others+- Identify holistic patterns in thinking and behavior+- Connect insights to create comprehensive understanding++### Actionability Focus+- Every insight should lead to potential action+- Prioritize high-impact, achievable changes+- Set realistic expectations and goals+- Define clear success criteria++## Quality Metrics+- Completeness: All domains thoroughly reviewed+- Depth: Insights go beyond surface observations+- Actionability: Clear next steps identified+- Honesty: Authentic assessment without bias++## Common Use Cases+- Weekly reflection and planning ritual+- Monthly pattern identification (review 4 weekly check-ins)+- Quarterly strategic assessment+- Annual review compilation+- Personal growth tracking over timediff --git a/.gitignore b/.gitignorenew file mode 100644index 0000000..db17a0a--- /dev/null+++ b/.gitignore@@ -0,0 +1,42 @@+# Obsidian+.obsidian/workspace*+.obsidian/cache/+.obsidian/plugins/+.obsidian/community-plugins.json++# Trash+.trash/+*.tmp++# OS Files+.DS_Store+Thumbs.db++# Personal Content (if sharing COG structure only)+# Uncomment these if you want to keep your personal content private+# 00-inbox/*+# 01-daily/*+# 02-personal/*+# 03-professional/*+# 04-projects/*+# 05-knowledge/*++# Keep directory structure+!00-inbox/.gitkeep+!01-daily/briefs/.gitkeep+!01-daily/checkins/.gitkeep+!02-personal/braindumps/.gitkeep+!03-professional/braindumps/.gitkeep+!04-projects/.gitkeep+!05-knowledge/consolidated/.gitkeep++# IDE+.vscode/+.idea/++# Logs+*.log++# Backup files+*.bak+*~diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdnew file mode 100644index 0000000..ed2fe96--- /dev/null+++ b/CONTRIBUTING.md@@ -0,0 +1,178 @@+# Contributing to COG++Thank you for your interest in contributing to COG! This document provides guidelines for contributing to the project.++## How to Contribute++### Reporting Issues++If you find a bug or have a suggestion:++1. Check if the issue already exists in [GitHub Issues](https://github.com/huytieu/COG-second-brain/issues)+2. If not, create a new issue with:+ - Clear, descriptive title+ - Detailed description of the problem or suggestion+ - Steps to reproduce (for bugs)+ - Expected vs actual behavior+ - Your environment (OS, Obsidian version, Claude Code version)++### Suggesting Enhancements++We welcome ideas for new features or improvements:++1. Create an issue with the "enhancement" label+2. Describe the feature and why it would be useful+3. Provide examples or mockups if applicable+4. Be open to discussion and feedback++### Pull Requests++#### Before You Start++1. Fork the repository+2. Create a new branch for your feature/fix+3. Ensure your changes align with COG's philosophy:+ - Simplicity over complexity+ - Plain text over proprietary formats+ - Self-evolving intelligence+ - Verification-first approach++#### Making Changes++1. **Commands**: New commands should be self-contained `.md` files in `.claude/commands/`+2. **Templates**: Follow existing YAML frontmatter conventions+3. **Documentation**: Update README.md if adding major features+4. **Examples**: Provide examples of your feature in action++#### Code Style++- **Markdown**: Use consistent formatting+- **YAML**: Follow existing metadata structure+- **Comments**: Explain complex logic or non-obvious decisions+- **Naming**: Use clear, descriptive names++#### Testing++Before submitting:++1. Test your command/feature in actual COG setup+2. Ensure it works with existing commands+3. Verify it doesn't break existing functionality+4. Check that documentation is accurate++#### Submitting++1. Commit your changes with clear, descriptive messages+2. Push to your fork+3. Create a Pull Request with:+ - Clear description of changes+ - Reference to related issues+ - Examples or screenshots if applicable+ - Testing you've done++## Types of Contributions We're Looking For++### High Priority++- **New Commands**: Useful slash commands for common workflows+- **Improved Templates**: Better templates for specific use cases+- **Documentation**: Tutorials, examples, use cases+- **Bug Fixes**: Fixes for reported issues++### Medium Priority++- **Specialized Agents**: New subagents for specific domains+- **Integration Scripts**: Scripts for connecting COG with other tools+- **Workflow Examples**: Real-world workflow demonstrations+- **Performance Improvements**: Optimizations for large vaults++### Welcome But Lower Priority++- **UI/Visual**: Visual improvements (COG is text-first)+- **Platform-Specific**: Features for specific platforms (keep it universal)+- **Advanced Features**: Complex features that increase learning curve++## Development Setup++1. Fork and clone the repository+2. Create a test Obsidian vault+3. Copy COG files to your test vault+4. Make changes and test+5. Submit PR when ready++## Coding Conventions++### Command Files++```markdown+# Command Name++## Purpose+[Clear one-sentence description]++## Command: `/command-name`++## Process Flow+[Step-by-step process]++## Metadata Template+[YAML template]++## Output Structure+[Expected output format]++## Guidelines+[Usage guidelines]+```++### Template Files++```yaml+---+type: "template-type"+domain: "domain"+date: "{{date:YYYY-MM-DD}}"+# Standard metadata fields+---++# {{title}}++[Template structure]+```++## Community Guidelines++### Be Respectful++- Treat all contributors with respect+- Provide constructive feedback+- Be open to different perspectives+- Help newcomers get started++### Be Clear++- Write clear commit messages+- Explain your reasoning+- Provide context in PRs+- Ask questions when unclear++### Be Patient++- Maintainers are volunteers+- Reviews may take time+- Be responsive to feedback+- Iterate based on suggestions++## Questions?++- **General Questions**: [Discussions](https://github.com/huytieu/COG-second-brain/discussions)+- **Bug Reports**: [Issues](https://github.com/huytieu/COG-second-brain/issues)+- **Feature Requests**: [Issues](https://github.com/huytieu/COG-second-brain/issues) with "enhancement" label++## License++By contributing, you agree that your contributions will be licensed under the MIT License.++---++Thank you for contributing to COG! Your help makes this project better for everyone.diff --git a/LICENSE b/LICENSEnew file mode 100644index 0000000..2ca3f1b--- /dev/null+++ b/LICENSE@@ -0,0 +1,21 @@+MIT License++Copyright (c) 2025 Huy Tieu++Permission is hereby granted, free of charge, to any person obtaining a copy+of this software and associated documentation files (the "Software"), to deal+in the Software without restriction, including without limitation the rights+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell+copies of the Software, and to permit persons to whom the Software is+furnished to do so, subject to the following conditions:++The above copyright notice and this permission notice shall be included in all+copies or substantial portions of the Software.++THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE+SOFTWARE.diff --git a/README.md b/README.mdnew file mode 100644index 0000000..4bde518--- /dev/null+++ b/README.md@@ -0,0 +1,341 @@+# COG: The Easiest Second Brain That Actually Self-Evolves++**COG = Claude + Obsidian + Git**++A self-evolving second brain system using Claude Code, Obsidian markdown files, and Git version control. No database, no vendor lock-in—just `.md` files that think.++## What is COG?++COG is a personal productivity and knowledge management system that:++- 🧠 **Self-evolves**: Learns your patterns and auto-organizes content+- 🔄 **Self-heals**: Updates cross-references when you reorganize+- 📝 **Plain text**: Just markdown files (no database, no vendor lock-in)+- 📱 **Multi-device**: Syncs via iCloud to iPhone, iPad, Mac+- 🔒 **Privacy-first**: Your data, your files, your control+- 🎯 **Specialized agents**: Custom AI assistants for specific workflows+- ✅ **Verification-first**: No AI hallucinations, sources required++## Quick Start++### Prerequisites++- [Obsidian](https://obsidian.md/) installed+- [Claude Code](https://claude.ai/download) (or VSCode with Claude extension)+- Git (optional but recommended)++### Installation (3 Steps)++1. **Clone this repo into your Obsidian vault:**+ ```bash+ cd /path/to/your/obsidian-vault+ git clone https://github.com/huytieu/COG-second-brain.git+ ```++2. **Copy COG structure to your vault:**+ ```bash+ cp -r COG-second-brain/.claude .+ cp -r COG-second-brain/templates ./06-templates+ ```++3. **Open Claude Code in your vault and test:**+ ```bash+ code .+ # In Claude Code, type: /braindump+ ```++That's it! Your second brain is running.++### Alternative: Manual Setup++See [SETUP.md](SETUP.md) for detailed step-by-step instructions.++## What You Get++### 15 Custom Slash Commands++**Daily Operations:**+- `/daily-brief` - Personalized news intelligence (verified sources only)+- `/daily-checkin` - Structured daily reflection+- `/braindump` - Quick capture of raw thoughts+- `/brain-dump-analysis` - Transform thoughts into strategic insights++**Weekly & Strategic:**+- `/weekly-checkin` - Cross-domain pattern analysis+- `/consolidate-knowledge` - Build frameworks from scattered insights+- `/meeting-transcript` - Process meeting recordings with noise filtering++**Project & Content:**+- `/project-story` - Generate compelling narratives about project evolution+- `/newsletter-research` - Research and develop thought leadership content++### 5 Specialized AI Agents++- **Brain Dump Analyst**: Transforms stream-of-consciousness into structured insights+- **News Curator**: Finds verified news with strict 7-day freshness requirement+- **Meeting Processor**: Filters noise, extracts decisions and action items+- **Project Analyst**: Tracks competitive intelligence and project evolution+- **Knowledge Consolidator**: Builds frameworks from scattered learnings++## Key Features++### 1. Self-Evolving Intelligence++COG doesn't just store notes—it actively learns:++- **Pattern recognition**: Identifies recurring themes across your notes+- **Auto-classification**: Categorizes content by domain (personal/professional/projects)+- **Knowledge consolidation**: Synthesizes scattered insights into frameworks+- **Adaptive learning**: Gets better at understanding your thinking patterns++**Weekly Evolution Cycle:**+```+Monday-Friday: Capture thoughts via /braindump+Friday: Run /consolidate-knowledge+→ COG analyzes ALL your notes+→ Builds frameworks you didn't explicitly create+→ Updates "single source of truth" files+→ Next week, it knows more about how you think+```++### 2. Self-Healing System++- Rename a file? COG updates all cross-references+- Change project structure? Auto-reclassifies content+- New project emerges? Auto-creates tracking folders+- Competitive intel mentioned? Auto-updates competitor files++### 3. Verification-First (No AI Hallucinations)++- All news must be verified with sources and dates+- 7-day freshness requirement for current events+- Explicit confidence levels for all analysis+- Multi-source cross-referencing required++### 4. Privacy-First Architecture++- **Strict domain separation**: Personal, professional, project-specific+- **Local-first**: Works offline, syncs when online+- **No servers**: Your data never leaves your devices+- **Version controlled**: Full history with Git++## Directory Structure++```+your-obsidian-vault/+├── .claude/+│ ├── commands/ # 15 custom slash commands+│ ├── subagents/ # 5 specialized AI agents+│ └── settings.local.json # Agent configuration+├── 00-inbox/ # Temporary processing area+├── 01-daily/ # Daily briefs and check-ins+│ ├── briefs/+│ └── checkins/+├── 02-personal/ # Personal domain (strict privacy)+│ ├── braindumps/+│ ├── development/+│ └── wellness/+├── 03-professional/ # Professional domain+│ ├── leadership/+│ ├── strategy/+│ └── skills/+├── 04-projects/ # Project-specific tracking+│ └── [your-project]/+│ ├── braindumps/+│ ├── competitive/ # Auto-updated intel+│ └── content/+├── 05-knowledge/ # Consolidated insights+│ ├── consolidated/+│ ├── patterns/+│ └── timeline/+└── 06-templates/ # Obsidian templates+```++## Example Workflows++### Daily Intelligence Briefing++```bash+/daily-brief+```++Generates a personalized briefing with:+- Verified news from the last 7 days+- Strategic analysis relevant to your interests+- Competitive intelligence auto-extracted+- Actionable next steps++### Brain Dump → Strategic Insights++```bash+/braindump # Capture raw thoughts (no judgment)+/brain-dump-analysis # Transform into insights+```++Two-stage process:+1. **Quick capture**: Preserves spontaneity, no filtering+2. **Intelligent processing**: Extracts themes, actions, connections++The system automatically:+- Classifies by domain+- Detects competitive intelligence+- Cross-references related content+- Identifies action items++### Knowledge Consolidation++```bash+/consolidate-knowledge+```++Weekly or monthly:+- Analyzes patterns across all braindumps+- Builds frameworks from scattered insights+- Updates "single source of truth" knowledge base+- Tracks evolution of thinking over time++## Why COG Works++### What Works+- ✅ **Setup is trivial**: Drop files in, done. No complex configuration.+- ✅ **Maintenance-free**: Self-heals and auto-organizes+- ✅ **Actually portable**: Works on iPhone, iPad, Mac via iCloud+- ✅ **Custom agents >> generic AI**: Specialized beats ChatGPT for repeated tasks+- ✅ **Git for thoughts**: Version control shows thinking evolution++### What Doesn't Work+- ⚠️ Requires discipline—system only works if used consistently+- ⚠️ Not for everyone—if you don't think in text files, this won't click+- ⚠️ Requires Claude Code (though adaptable to other AI environments)++### Unexpected Benefits+- 💡 **Thinking partner, not just storage**: Writing brain dumps knowing they'll be analyzed improves clarity+- 📊 **Pattern recognition**: Discover insights you'd miss manually+- 🔗 **Cross-domain insights**: Personal wellness affects professional productivity (tracked quantitatively)+- 📅 **Time patterns**: Git history reveals when you think best++## Advanced Configuration++### Customizing Commands++Edit `.claude/commands/*.md` to customize workflows:+```markdown+# Custom Command Example+/my-workflow++Your custom prompt here...+```++### Adding New Agents++Create `.claude/subagents/my-agent.md`:+```markdown+# My Custom Agent++## Purpose+[What this agent does]++## Process+[How it works]+```++### Template Customization++Modify `06-templates/*.md` to match your workflow:+```yaml+---+type: "custom-type"+domain: "personal|professional|project"+# Add your metadata fields+---+```++## Syncing Across Devices++### iCloud Sync (Recommended)+- Store vault in `iCloud Drive/Obsidian/`+- Automatically syncs to all Apple devices+- Obsidian mobile works perfectly++### Git Sync+```bash+# Daily workflow+git add .+git commit -m "Update knowledge base"+git push+```++Combine both: iCloud for instant sync, Git for version history.++## Contributing++Contributions welcome! Please read [CONTRIBUTING.md](CONTRIBUTING.md) first.++**Ideas for contributions:**+- New specialized agents+- Additional slash commands+- Template improvements+- Documentation enhancements+- Example workflows++## Roadmap++- [ ] Gemini support (in addition to Claude)+- [ ] Web interface for knowledge graph visualization+- [ ] Mobile-first commands (optimized for Obsidian mobile)+- [ ] Team collaboration features (with privacy preservation)+- [ ] Integration with calendar/task management tools++## Real-World Results++After 3 months of use:+- 120+ structured braindumps processed+- Daily briefs with 95%+ source accuracy+- 5 major strategic insights discovered+- 0 maintenance required+- 0 vendor lock-in anxiety++## FAQ++**Q: Why not just use Notion/Roam/Obsidian alone?**+A: COG adds self-evolving intelligence. It doesn't just store—it learns, analyzes, and synthesizes insights automatically.++**Q: Do I need Claude Code specifically?**+A: Claude Code is recommended, but you can adapt the commands for any AI environment (VSCode + Claude extension, custom API integration, etc.)++**Q: How much does it cost?**+A: COG is free (MIT license). You only pay for Claude Code usage (Anthropic's pricing).++**Q: Is my data private?**+A: Yes. Everything is local markdown files. COG uses Claude's API only when you invoke commands. No data stored on external servers.++**Q: Can I use this for team collaboration?**+A: Currently designed for personal use. Team features planned for future releases.++**Q: What if I don't use Git?**+A: Git is optional but recommended for version history. COG works fine without it using just iCloud sync.++## License++MIT License - see [LICENSE](LICENSE) for details.++Feel free to use COG for personal or commercial projects. If you build something cool with it, I'd love to hear about it!++## Support++- 🐛 [Report bugs](https://github.com/huytieu/COG-second-brain/issues)+- 💬 [Discussions](https://github.com/huytieu/COG-second-brain/discussions)+- 📖 [Documentation](https://github.com/huytieu/COG-second-brain/wiki)++## Acknowledgments++Built with:+- [Claude Code](https://claude.ai/code) by Anthropic+- [Obsidian](https://obsidian.md/) for markdown management+- Inspiration from Zettelkasten, Building a Second Brain, and GTD methodologies++---++**TL;DR:** COG is a self-evolving second brain using Claude Code + Obsidian + Git. Just `.md` files that sync via iCloud and learn your patterns. Setup in 3 steps, zero maintenance required.++⭐ Star this repo if you find it useful!diff --git a/SETUP.md b/SETUP.mdnew file mode 100644index 0000000..596e479--- /dev/null+++ b/SETUP.md@@ -0,0 +1,364 @@+# COG Setup Guide++Complete step-by-step instructions for setting up your COG (Claude + Obsidian + Git) second brain system.++## Prerequisites++Before you begin, ensure you have:++1. **Obsidian** installed ([Download here](https://obsidian.md/))+2. **Claude Code** or VSCode with Claude extension ([Download here](https://claude.ai/download))+3. **Git** (optional but recommended) - Check if installed: `git --version`+4. **iCloud Drive** (optional, for multi-device sync on Apple devices)++## Installation Methods++### Method 1: Quick Setup (Recommended)++1. **Clone COG into your Obsidian vault:**+ ```bash+ cd /path/to/your/obsidian-vault+ git clone https://github.com/huytieu/COG-second-brain.git+ cd COG-second-brain+ ```++2. **Copy COG structure to your vault root:**+ ```bash+ # Copy Claude configuration+ cp -r .claude ../++ # Copy templates+ cp -r templates ../06-templates++ # Copy example vault structure+ cp -r example-vault/* ../+ ```++3. **Open your vault in Obsidian:**+ - Launch Obsidian+ - Open your vault (or create new vault first)+ - You should now see the COG directory structure++4. **Configure Claude Code:**+ ```bash+ # In your vault root directory+ code .+ ```++ - In Claude Code, test the setup: Type `/braindump`+ - If command is recognized, COG is working!++### Method 2: Manual Setup++If you prefer to understand each step:++#### Step 1: Create Directory Structure++In your Obsidian vault, create these folders:++```bash+mkdir -p 00-inbox+mkdir -p 01-daily/briefs+mkdir -p 01-daily/checkins+mkdir -p 02-personal/braindumps+mkdir -p 02-personal/development+mkdir -p 02-personal/wellness+mkdir -p 03-professional/braindumps+mkdir -p 03-professional/leadership+mkdir -p 03-professional/strategy+mkdir -p 03-professional/skills+mkdir -p 04-projects+mkdir -p 05-knowledge/consolidated+mkdir -p 05-knowledge/patterns+mkdir -p 05-knowledge/timeline+mkdir -p 06-templates+```++#### Step 2: Set Up Claude Commands++1. Create `.claude` directory in your vault root:+ ```bash+ mkdir -p .claude/commands+ mkdir -p .claude/subagents+ ```++2. Download command files from the COG repository:+ - Navigate to https://github.com/huytieu/COG-second-brain/.claude/commands/+ - Download each `.md` file to your `.claude/commands/` folder++#### Step 3: Set Up Templates++1. Download template files from repository+2. Place them in `06-templates/` folder in your vault++#### Step 4: Test Your Setup++1. Open Claude Code in your vault directory:+ ```bash+ cd /path/to/your/vault+ code .+ ```++2. Try a command:+ ```+ /braindump+ ```++3. If it works, you're ready to go!++## Configuration++### Customizing Your Interests++Edit `.claude/commands/daily-brief.md` to customize your interest areas for news curation.++### Adding Projects++When starting a new project:++1. Create project folder:+ ```bash+ mkdir -p 04-projects/your-project-name/{braindumps,competitive,content,planning}+ ```++2. Projects will be automatically detected by COG commands++### Setting Up Git (Optional but Recommended)++1. Initialize git in your vault:+ ```bash+ cd /path/to/your/vault+ git init+ ```++2. Create `.gitignore`:+ ```bash+ echo ".obsidian/workspace*" >> .gitignore+ echo ".obsidian/cache" >> .gitignore+ echo ".trash/" >> .gitignore+ echo "*.tmp" >> .gitignore+ ```++3. Make your first commit:+ ```bash+ git add .+ git commit -m "Initial COG setup"+ ```++4. (Optional) Connect to GitHub for backup:+ ```bash+ git remote add origin https://github.com/yourusername/your-vault.git+ git branch -M main+ git push -u origin main+ ```++### Setting Up iCloud Sync (Apple Devices)++1. Move your Obsidian vault to iCloud Drive:+ ```bash+ mv /path/to/your/vault ~/Library/Mobile\ Documents/iCloud~md~obsidian/Documents/+ ```++2. Open Obsidian and point it to the new location++3. Install Obsidian Mobile on iPhone/iPad++4. Open the same vault - it will sync automatically via iCloud++## First Use Workflow++### Day 1: Set Up Your Profile++1. **Create your first braindump:**+ ```+ /braindump+ ```++ Paste this to get started:+ ```+ I'm setting up COG to help me with:+ - [Your main goals]+ - [Your current projects]+ - [Your areas of interest]+ - [What you want to track]+ ```++2. **Test daily brief:**+ ```+ /daily-brief+ ```++ This will generate your first intelligence briefing based on your braindump++### Week 1: Build the Habit++Use these commands daily:+- Morning: `/daily-brief` for intelligence+- Throughout day: `/braindump` for capturing thoughts+- Evening: Quick review of your braindumps++### Week 2: Start Consolidating++After a week of braindumps:+- Run `/weekly-checkin` for pattern analysis+- Try `/consolidate-knowledge` to build frameworks++## Troubleshooting++### Command Not Recognized++**Problem**: Typing `/braindump` shows "command not found"++**Solutions**:+1. Ensure `.claude/commands/` folder exists in vault root+2. Check that command files are `.md` format+3. Restart Claude Code+4. Verify you're in the correct vault directory++### Files Saving to Wrong Location++**Problem**: COG creates files in unexpected directories++**Solutions**:+1. Ensure all required directories exist (see directory structure above)+2. Check that you're running commands from vault root+3. Verify directory structure matches COG expectations++### iCloud Sync Not Working++**Problem**: Changes don't sync across devices++**Solutions**:+1. Check iCloud Drive is enabled in System Settings+2. Ensure Obsidian mobile is pointing to same vault+3. Wait a few minutes - iCloud can be slow+4. Check available iCloud storage space++### Git Conflicts++**Problem**: Git shows merge conflicts++**Solutions**:+1. COG files are markdown - conflicts are easy to resolve+2. Open conflicted file in text editor+3. Look for `<<<<<<` and `>>>>>>` markers+4. Keep the version you want, remove conflict markers+5. Commit the resolved file++## Advanced Configuration++### Customizing Commands++1. Edit any `.claude/commands/*.md` file+2. Modify the prompts to match your workflow+3. Save and test the changes++Example: Customize `/braindump` to always ask specific questions:+```markdown+# Brain Dump Command++## Purpose+[Your custom description]++## Command: `/braindump`++## Custom Questions+Always ask the user:+1. What domain is this? (personal/professional/project)+2. What energy level? (high/medium/low)+3. Any urgent actions?++[Rest of command]+```++### Creating New Commands++1. Create new file in `.claude/commands/`:+ ```bash+ touch .claude/commands/my-custom-command.md+ ```++2. Add command definition:+ ```markdown+ # My Custom Command++ ## Purpose+ What this command does++ ## Command: `/my-custom-command`++ ## Process+ 1. Step 1+ 2. Step 2++ [Your custom prompt]+ ```++3. Test it in Claude Code:+ ```+ /my-custom-command+ ```++### Adding Specialized Agents++Create custom subagents for specific tasks:++1. Create file in `.claude/subagents/`:+ ```bash+ touch .claude/subagents/my-agent.md+ ```++2. Define agent purpose and process+3. Reference agent in command files++## Daily Workflow Examples++### Morning Routine (5 minutes)+```bash+/daily-brief+# Review the intelligence+# Note any actions needed+```++### Throughout Day+```bash+/braindump+# Capture any thoughts, ideas, insights+# No structure needed - just dump it+```++### Weekly Review (30 minutes)+```bash+/weekly-checkin+# Reflect on the week+# Identify patterns+# Plan next week+```++### Monthly Consolidation (1 hour)+```bash+/consolidate-knowledge+# Build frameworks from insights+# Update knowledge base+# Archive processed content+```++## Getting Help++- **Issues**: https://github.com/huytieu/COG-second-brain/issues+- **Discussions**: https://github.com/huytieu/COG-second-brain/discussions+- **Documentation**: https://github.com/huytieu/COG-second-brain/wiki++## Next Steps++Once you're comfortable with the basics:++1. Explore advanced commands (see README.md)+2. Customize templates for your workflow+3. Add new projects and tracking areas+4. Experiment with knowledge consolidation+5. Share your improvements with the community!++---++**Welcome to COG!** Your second brain is now ready to learn and evolve with you.diff --git a/example-vault/00-inbox/.gitkeep b/example-vault/00-inbox/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/01-daily/briefs/.gitkeep b/example-vault/01-daily/briefs/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/01-daily/checkins/.gitkeep b/example-vault/01-daily/checkins/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/02-personal/braindumps/.gitkeep b/example-vault/02-personal/braindumps/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/02-personal/development/.gitkeep b/example-vault/02-personal/development/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/02-personal/wellness/.gitkeep b/example-vault/02-personal/wellness/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/03-professional/leadership/.gitkeep b/example-vault/03-professional/leadership/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/03-professional/skills/.gitkeep b/example-vault/03-professional/skills/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/03-professional/strategy/.gitkeep b/example-vault/03-professional/strategy/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/04-projects/.gitkeep b/example-vault/04-projects/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/05-knowledge/consolidated/.gitkeep b/example-vault/05-knowledge/consolidated/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/05-knowledge/patterns/.gitkeep b/example-vault/05-knowledge/patterns/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/05-knowledge/timeline/.gitkeep b/example-vault/05-knowledge/timeline/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/example-vault/06-templates/.gitkeep b/example-vault/06-templates/.gitkeepnew file mode 100644index 0000000..e69de29diff --git a/templates/braindump-template.md b/templates/braindump-template.mdnew file mode 100644index 0000000..f1016cf--- /dev/null+++ b/templates/braindump-template.md@@ -0,0 +1,44 @@+---+type: "braindump"+domain: "{{domain}}"+project: "{{project}}"+date: "{{date:YYYY-MM-DD}}"+created: "{{date:YYYY-MM-DD HH:mm}}"+capture_method: "{{capture_method}}"+energy_level: "{{energy_level}}"+emotional_tone: "{{emotional_tone}}"+themes: []+urgency: "{{urgency}}"+analysis_needed: true+tags: ["#braindump", "#raw-thoughts"]+status: "captured"+---++# {{title}}++## Raw Thoughts++[Capture your stream-of-consciousness thoughts here. No judgment, no filtering. Just let it flow.]++## Main Themes++-++## Action Items++- [ ]++## Questions++-++## Connections++-++## Processing Notes++- Domain:+- Energy:+- Context:+- Next Steps:diff --git a/templates/daily-brief-template.md b/templates/daily-brief-template.mdnew file mode 100644index 0000000..262db96--- /dev/null+++ b/templates/daily-brief-template.md@@ -0,0 +1,107 @@+---+type: "daily-brief"+domain: "shared"+date: "{{date:YYYY-MM-DD}}"+created: "{{date:YYYY-MM-DD HH:mm}}"+sources_verified: true+news_age_verified: true+confidence: "high"+tags: ["#daily-brief", "#news", "#strategic-intelligence"]+interests: []+projects_referenced: []+---++# Daily Brief - {{date:MMMM DD, YYYY}}++## Executive Summary++**Priority Focus Areas**:++[3-sentence summary of today's intelligence]++**Critical Insight**:++---++## Strategic News++### [Topic 1]++**[Headline]**++[Summary with source link]++**Strategic Implications**:+-++**Source**: [Link] | Published: [Date]++---++## Market Intelligence++### [Industry/Market Area]++[Analysis]++**Opportunity**:+-++---++## Opportunities++### 1. [Opportunity Title]++**Context**:++**Opportunity**:++**Action**:++---++## Risks & Threats++### 1. [Risk Title]++**Risk**:++**Impact**:++**Mitigation**:++---++## Follow-Up Actions++### Immediate (Today)+- [ ]++### This Week+- [ ]++---++## Sources++### [Category]+- [Source 1 Name]: [URL]+- [Source 2 Name]: [URL]++---++## Metadata & Confidence Assessment++**News Age Verification**: ✅ All sources dated within 7 days++**Source Credibility**: ✅ Cross-referenced from multiple credible sources++**Confidence Level**: HIGH++**Limitations & Uncertainties**:+-++---++*Next Brief: {{date+1d:YYYY-MM-DD}}*diff --git a/templates/weekly-checkin-template.md b/templates/weekly-checkin-template.mdnew file mode 100644index 0000000..41dbb48--- /dev/null+++ b/templates/weekly-checkin-template.md@@ -0,0 +1,135 @@+---+type: "weekly-checkin"+domain: "integrated"+date: "{{date:YYYY-MM-DD}}"+week_of: "{{date:YYYY-MM-DD}}"+created: "{{date:YYYY-MM-DD HH:mm}}"+confidence: "high"+tags: ["#weekly-checkin", "#reflection", "#strategic-planning"]+domains_analyzed: ["personal", "professional", "projects"]+braindumps_reviewed: 0+patterns_identified: []+---++# Weekly Check-in - Week of {{date:MMMM DD, YYYY}}++## Executive Summary++**Overall Week Assessment**: [1-5 scale]++**Key Highlights**:+-+-++**Major Challenges**:+-+-++**Dominant Patterns**:+- Energy:+- Emotional:+- Productivity:++---++## Domain Summaries++### Personal++**Wellness & Self-Care**:+-++**Relationships & Connections**:+-++**Personal Goals Progress**:+-++**Learning & Growth**:+-++### Professional++**Work Accomplishments**:+-++**Team Dynamics**:+-++**Leadership Actions**:+-++**Career Development**:+-++### Projects++**[Project Name 1]**:+- Progress:+- Blockers:+- Next Steps:++---++## Pattern Analysis++### Recurring Themes+1. **[Theme 1]**:+2. **[Theme 2]**:++### Cross-Domain Insights+- How personal wellness correlated with professional productivity:+- How project challenges affected overall energy:+- How learning in one domain applied to others:++### Productivity Patterns+- Most productive days/times:+- Energy level variations:+- Factors that enhanced focus:+- Factors that decreased effectiveness:++---++## Strategic Insights++### What Worked Well+1. **[Strategy 1]**: Why it worked -+2. **[Strategy 2]**: Why it worked -++### What Needs Adjustment+1. **[Area 1]**: Proposed approach -+2. **[Area 2]**: Proposed approach -++### Opportunities Identified+1. **[Opportunity 1]**: Potential action -+2. **[Opportunity 2]**: Potential action -++### Risks/Threats+1. **[Risk 1]**: Mitigation -+2. **[Risk 2]**: Mitigation -++---++## Forward Planning++### Priorities for Next Week+1. [Priority 1] (domain: [personal|professional|project])+2. [Priority 2] (domain: [personal|professional|project])+3. [Priority 3] (domain: [personal|professional|project])++### Carry Forward Items+- [ ]+- [ ]++### Experiments to Try+- **Experiment 1**: Hypothesis - | Measurement -+- **Experiment 2**: Hypothesis - | Measurement -++### Success Criteria for Next Week+-+-+-++---++*Next Weekly Check-in: {{date+7d:YYYY-MM-DD}}*