CLAUDE.md

1# Third Brain V7.1 Skills — Claude Code
2 
3For detailed installation, usage, and workflow scenarios, see **[GUIDE.md](GUIDE.md)**.
4 
5You have access to the following Agent Skills. Each skill is a markdown file in `~/.claude/skills/` that defines a specific capability.
6 
7## Skill Categories
8 
9### 📥 Knowledge Pipeline
10- **wiki-ingest** — Ingest sources into an interlinked wiki with source-risk classification, macro-action scope, block refs, clipping archive, Karpathy understanding gate, governance notes, and post-ingest lint. STOW pipeline: Source → Think → Organize → Write.
11- **knowledge-ops** — Multi-layer knowledge management with Markdown-first retrieval, optional ChromaDB vector support, evidence hierarchy, deduplication, and knowledge debt queues.
12- **wiki-lint** — Health-check the wiki across P0/P1 graph health, source refs, frontmatter, links, provenance debt, clipping lifecycle, understanding integrity, and drift.
13 
14### 🔄 Daily Loop
15- **daily-okr** — 7 Key Results daily cycle: Input → Cognition → Wiki → Behavior → Creativity → Output → Feedback, each with evidence.
16- **cognitive-compile** — 8-section deep learning compile: Question → Facts → Concepts → Patterns → Conflicts → Hypotheses → Decision → Action.
17 
18### 🎨 Behavior & Creativity
19- **behavior-design** — Behavior change system: goals → habits → triggers → SOPs → review. Includes HAS (Human Agency Scale).
20- **creativity-engine** — Combinatorial ideation with Lego Building Blocks method. Cross-domain analogies + minimum experiments.
21 
22### 🔬 Research & Quality
23- **deep-research** — STOW-compatible research harness with ChatGPT-style preflight, source/claim ledgers, activity trace, citations, privacy checks, and wiki-ingest handoff.
24- **verify-before-claim** — No completion claims without fresh, scope-matched verification evidence.
25 
26### 🔄 Learning
27- **session-learn** — Extract 7 knowledge signal types from sessions. Closure Protocol for feedback loops.
28- **project-flow-ops** — Triage, plan, track, review across projects.
29 
30### 📊 Context & Cost
31- **context-manager** — Runtime-derived budgets, checkpoints, compaction, retrieval, and capability routing.
32- `token-cost-tracker` — command for estimate/log/report; it is not an Agent Skill.
33 
34### 🏗️ Engineering
35- **loop-engineering** — Temporal-depth control through bounded Goal/Loop/Automation/AutoResearch contracts with state, verification, retry, and recovery.
36- **graph-engineering** — Dependency-width control through bounded static DAGs with explicit dependencies, independent branches, typed joins, and node-local recovery. V7.1 excludes dynamic and cyclic graphs.
37- **agentic-engineering** — Refactor skills and workflows as agent processes with autonomy defaults, delegated-action boundaries, state checkpoints, write-back, and verification gates.
38- **harness-engineering** — Agent runtime kernel: scheduler, permissions, tools as system calls, provenance ledgers, delegated-action gates, observability, recovery, and closed-loop design.
39- **agent-teams-command** — Multi-agent process ownership and orchestration with IPC, async budget envelopes, integration, cleanup, and evidence gates.
40 
41### 💼 Strategy & Operations
42- **startup-evaluation** — Startup health diagnosis with entrepreneurship, VC 5T, PMF, runway, team, and next-test frameworks.
43- **anthropic-os** — Cognitive Symbiont Engine. Livewired + 3B creativity algorithms (Bending/Breaking/Blending). Predictive coding, time-arrow diagnostics.
44- **ai-six-sigma-property-os** — AI + Ontology + DMAIC Black Belt operating model for property work orders, dispatch, quotes, evidence, CTQ dashboards, and MVP quality control.
45 
46## Usage
47 
48Invoke any skill naturally:
49- "Ingest this article into my wiki"
50- "Run a cognitive compile on X"
51- "Create an agent team to build Y"
52- "Launch Anthropic OS for my team" — includes 3B creativity algorithms
53- "Design my Property Agent OS with AI Six Sigma"
54- "Apply 3B to our growth strategy" — Bending/Breaking/Blending
55- "Estimate token cost for this task"
56 
57## Skill Contract
58 
59Before executing a selected skill, read the skill frontmatter and enforce:
60 
61- `assumes`: required operating assumptions for safe use.
62- `conflicts_with`: workflows or assumptions that must not be silently overridden.
63- `metadata.profile`: `one-shot`, `stateful`, `loop`, or `high-risk` control depth.
64- `## Failure Protocol` and `## Output Contract`: standard stop status and receipt.
65- `## Success Metrics`: minimum measurable result for one successful run.
66- `## Quality Gates`: checks required before completion claims.
67 
68For wiki-writing skills, resolve `SOURCES_DIR`, `CONCEPTS_DIR`, `ENTITIES_DIR`, `OUTPUTS_DIR`, and `LOG_FILE` from `system/config.md` when available. If no config exists, use the default STOW layout.
69 
70## Recommended Adoption Ladder
71 
721. Week 1: `wiki-ingest` + `verify-before-claim`.
732. Weeks 2-4: add `daily-okr` + `session-learn`.
743. Month 2+: add `cognitive-compile`, `behavior-design`, and `creativity-engine`.
754. Month 3+: add `knowledge-ops`, `loop-engineering`, `harness-engineering`, and `agentic-engineering`.
765. Dependency scale: add `graph-engineering` after `loop-engineering` only when explicit dependencies, parallel branches, typed joins, or node-local recovery exceed orchestration and review cost.
776. Multi-agent scale: add `agent-teams-command` and `project-flow-ops`.
78 
79## Engineering Routing Boundary
80 
81- Loop Engineering controls temporal depth.
82- Graph Engineering controls dependency width.
83- Agent Teams Command controls process ownership, IPC, and integration.
84- Harness Engineering supplies the runtime scheduler, permissions, and observability.
85 
86A graph node may contain a bounded Loop or Agent Team. V7.1 supports bounded static DAGs, not dynamic or cyclic graphs.
87 
88## Grounding Principles
89 
90### Karpathy LLM OS
91LLM=CPU · Context=RAM · Storage=Disk · Tools=System Calls · Skills=Programs · Harness=Kernel · Agent Teams=Processes
92 
93### 3B Creativity Algorithms
94- **Bending**: Mutate existing success patterns into new contexts
95- **Breaking**: Eliminate worst-performing patterns; break path dependency
96- **Blending**: Fuse elements from different domains for novel patterns
97 
98### Agent Teams
99 
100When the runtime exposes isolated workers, use `agent-teams-command` for admission, ownership, IPC, integration, evidence, and cleanup. Do not bind the durable skill to a product version or model name.
101