.cursorrules git:20260824.44fa687A

Immutable. This exact content is served forever at /api/v1/blob/be3118fbb97b6974.

# COG Second Brain — Cursor Rules
# This is the Cursor-compatible version of CLAUDE.md
# COG: Cognition + Obsidian + Git — a self-evolving agentic second brain
# Inspired by Garry Tan's gstack and gbrain patterns

## Skills

COG exposes 17 skills via `.claude/skills/*/SKILL.md`. Each skill has a `name` and `description` in YAML frontmatter. Use AGENTS.md as the universal command reference.

## Worker Agents

10 agents live in `.claude/agents/`: 6 workers handle data-heavy tasks, 4 read-only verifiers check the result against acceptance criteria by observing the artifact. The lead session handles reasoning and synthesis.

- worker-data-collector: Structured extraction from GitHub, Slack, Jira, Linear
- worker-researcher: Web research with source citations
- worker-file-ops: Vault file operations, metadata, profiles
- worker-executor: Pre-approved mutations (Jira, Linear, APIs)
- worker-publisher: Publishing to Slack, Confluence, Notion
- brief-people-updater: Batch-update people profiles

## Brain-First Protocol

Before answering questions about people, projects, strategy, or decisions:
1. Read relevant notes from `05-knowledge/` first
2. If project-specific, read `04-projects/<project>/`
3. Then synthesize an answer

## Daily Journal

Ambient, not a command. After finishing a meaningful unit of work (shipped or committed something, produced a deliverable, made a decision, hit a blocker), append one entry to `01-daily/journal/YYYY-MM-DD.md` (`date +%F`). Create the file from the template in `.claude/skills/daily-journal/SKILL.md` on the first entry of the day; append only. Skip trivia and scratch work, and do not announce the write.

## Integration Preferences

Check `00-inbox/MY-INTEGRATIONS.md` before using any external integration:
- Active: use normally
- Disabled: skip silently
- Unknown: ask the user

## Vault Structure

```
00-inbox/          — Profiles, interests, integrations
01-daily/          — Briefs and check-ins
02-personal/       — Personal braindumps (private)
03-professional/   — Professional braindumps and strategy
04-projects/       — Per-project tracking
05-knowledge/      — Consolidated insights, people CRM, patterns
06-templates/      — Document templates
```

## Citation Rule

For factual statements in durable notes, include:
`[Source: [[path/to/note]] | YYYY-MM-DD | confidence: high|medium|low]`

## Response Style (ALWAYS APPLY)

Optimize for information gain, not apparent completeness. Start with the answer or strongest finding. Never invent named frameworks, gates, layers, pillars, or numbered taxonomies unless they exist in the source material. Headings name subject matter, never rhetorical function (banned: "Why this matters", "The key insight", "What this is not", "The bottom line"). No straw-man contrasts ("It's not X, it's Y") unless X is a position someone actually holds. Space proportional to importance; every paragraph must add evidence, mechanism, example, implication, or decision. Compose as finding -> evidence -> reasoning -> decision. Stop when useful information is exhausted. Full pattern list: `.claude/skills/no-ai-slop/SKILL.md` § Structural slop.