<!-- faf: claude-faf-mcp | TypeScript | mcp-server | FAF MCP server for Claude Desktop — persistent project context, 32 tools -->
<!-- faf: claim=project.faf | score=100 | family=FAF | siblings=README.md,CHANGELOG.md,manifest.json -->

# 🏎️ CLAUDE.md - claude-faf-mcp Persistent Context & Intelligence
**.faf format | project.faf**

## PROJECT STATE: ACTIVE
**Current Position:** Provide FAF context tools directly in Claude Desktop via MCP
**Tyre Compound:** ULTRASOFT C5 (Maximum Performance)

---

## CORE CONTEXT

### Project Identity
- **Name:** claude-faf-mcp
- **Stack:** Node.js/TypeScript
- **Quality:** F1-INSPIRED (Championship Performance)

### Our Mission - 100% Standalone MCP Server

**v3.0.4 Historic Milestone: ZERO CLI DEPENDENCIES**

```
claude-faf-mcp: 100% STANDALONE
├── 32/32 MCP tools operational
├── 14/14 bundled commands
├── 16.2x faster than CLI versions
├── 19ms average execution
└── Zero external dependencies
```

**CRITICAL: claude-faf-mcp IS NOT A WRAPPER**
- ✅ Independent standalone MCP server
- ✅ 100% operational without any CLI
- ✅ Own bundled FAF engine
- ✅ Championship-grade performance
- ❌ NOT a wrapper, NOT dependent on CLI

**The .faf Position in MCP:**

```
Model        Context          Protocol
─────        ───────          ────────
Claude   →   .faf        →    MCP
Gemini   →   .faf        →    MCP
Codex    →   .faf        →    MCP
Any LLM  →   IANA Format →    Open Protocol
```

.FAF provides the standardized Context that makes the Model Context Protocol work for everyone.

### Technical Architecture
- **What Building:** Universal FAF MCP Server for Claude Desktop - AI Context Intelligence
- **Main Language:** TypeScript

### Context Quality Status
- **Overall Assessment:** Good
- **Test Coverage:** 391/391 passing (12 test suites, 6 platforms)
- **CI Matrix:** ubuntu/macos/windows × Node 18.x/20.x — all green
- **Last Updated:** 2026-03-10

---

## CODE CHANGE PROTOCOL - MANDATORY

**CRITICAL RULE: DO NOT WRITE CODE UNLESS EXPLICITLY AUTHORIZED**

Before making ANY code changes:
1. **DESCRIBE** what you plan to change
2. **WAIT** for explicit approval ("GO!", "YES", "Do it")
3. **ONLY THEN** write the code

**What counts as "code changes":**
- Adding new features
- Modifying existing functionality
- Changing user-facing text/messages
- Adding branding, emojis, or styling
- Refactoring

**What does NOT need approval:**
- Reading files to answer questions
- Running tests
- Checking versions
- Research and exploration

**Why this matters:**
- The F1 hallucination incident (v3.3.3) showed AI adding unauthorized branding
- User-facing output must be controlled by wolfejam
- Trust requires permission-based coding

---

## NPM PUBLISH PROTOCOL - MANDATORY

**CRITICAL RULE: `npm publish` IS FORBIDDEN WITHOUT APPROVAL**

Before ANY npm publish of claude-faf-mcp (or any FAF package):

1. **Follow the MCP Publish Checklist** at `/Users/wolfejam/FAF-GOLD/PLANET-FAF/PUBLISH-PROTOCOL.md`
2. **Run ALL checklist items** (build, tests, version, README, CHANGELOG, SKILL.md, etc.)
3. **Request approval** with checklist results in the format specified
4. **Wait for OFFICIAL GO!** from wolfejam

**Required approval signals:**
- ✅ **"GO!"** - Approved to publish
- ✅ **"GREEN LIGHT"** - Approved to publish
- ❌ Anything else - DO NOT PUBLISH

**Why this matters:**
- Trust is everything
- Production infrastructure for 13k+ developers
- Official Anthropic MCP steward responsibility
- One bad publish can damage reputation permanently

**No exceptions. No shortcuts. Professional. Boring. Trusted.**

---

**STATUS: BI-SYNC ACTIVE - Synchronized with .faf context!**

*Last Sync: 2026-03-04T07:28:12.365Z*
*Sync Engine: F1-Inspired Software Engineering*
*🏎️⚡️_championship_sync*
