Stewards of the Foundational AI-context Format
IANA-registered · Universal AI-Context for any AI, human, or team
"It's so logical if it didn't exist, AI would have built it itself."
"Should become the standard."
— Claude Code, Sep 18 (42 days later → IANA Registered Oct 30, 2025)
First MCP for xAI Grok. First web-based MCP. Fastest growing FAF package with 100+ downloads overnight.
Peer-citable technical paper with DOI. Repository used by NASA, NIH, and major universities.
Combined downloads across faf-cli, claude-faf-mcp, faf-mcp, and grok-faf-mcp.
The context problem that every developer faces
Claude doesn't know what you told Gemini. Cursor doesn't know your ChatGPT history. Every tool starts from zero.
Stack, conventions, architecture, rules. Every session. Every tool. The same context, typed again and again.
CLAUDE.md says one thing. Your team's mental model says another. No single source of truth.
The Solution
One format. Every AI. Authored once, works everywhere.
Before
29%
context understood
After .faf
99%
context understood
Setup time: 20+ minutes → under 3 seconds
"package.json wasn't built for this, .faf was."
"package.json gives me a list of dependencies, .faf shows me how to use them."
— .faf Inventor + Claude Code
.faf sits at the center. Bidirectional conversion to any format.
Your project DNA travels with you regardless of which AI you use.
project.faf sits alongside package.json and README.md
"Every project should have one."
— OpenAI Codex CLI (9/10)Compatible With
YAML-based project DNA that any AI can read
The 50/50 Philosophy
Half technical (YAML for AI), half human-focused (markdown for you). Balance by design.
YAML format that developers can read and write. No special tooling required.
Structured data that AI systems parse instantly. No guessing, no hallucination.
Lives in your repo. Changes tracked with git. Team context always in sync.
"README evolution for AI era."
— Google Gemini CLI (9.5/10)
Official implementations and community adoption
Anthropic MCP #2759
8,800+ downloads
Google approved
Production deployment
Svelte component system
Voice AI context layer
11,240+
Tests run
9.3/10
Average rating
<50ms
Processing time
Gold-Code*
100% AI-optimized, persistent project context. Full context. Zero drift. Best code possible.
Using FAF? Let us know to be featured here.
To steward FAF as an open, vendor-neutral standard that enables any AI to understand any project.
FAF is and will always be an open standard. The specification is MIT-licensed, allowing anyone to implement, extend, and build upon it without restriction.
Works with Claude, GPT, Grok, Gemini, and any future AI. No lock-in, no proprietary extensions that fragment the ecosystem.
Evolution of the format is guided by real-world usage from developers, AI companies, and tool makers who use FAF daily.
Three paths to FAF integration
Parse project.faf to understand project context. Standard YAML - use any parser.
import yaml
with open('project.faf') as f:
context = yaml.safe_load(f)
# Your AI now knows:
# - Project stack
# - Coding conventions
# - AI-specific instructions
Analyze a codebase and output project.faf. Auto-detect stack, frameworks, patterns.
# Use faf-cli for reference
npx faf-cli init
# Or build your own detector
# following the FAF spec schema
Convert .faf to platform-specific formats: CLAUDE.md, GEMINI.md, conductor/, etc.
# Export examples
faf claude export # → CLAUDE.md
faf gemini export # → GEMINI.md
faf cursor export # → .cursorrules
Building an AI tool? We want to help.
Contact for Integration SupportOne format, many use cases
Write your project DNA once. Export to CLAUDE.md, GEMINI.md, or any format. Zero drift across sessions.
Add FAF support to your product. IANA-registered format with official SDKs in TypeScript, Python, and Rust.
Version-controlled project context. Onboard new devs instantly. Consistent AI interactions across your org.
Official SDKs, specifications, and tools
The official FAF specification document with examples and validation rules.
Read Specification →Peer-citable research paper on CERN/Zenodo. DOI: 10.5281/zenodo.18251362
Read on Zenodo →Overview of FAF format, the problem it solves, and adoption status.
Read Press Release →High-performance Rust implementation. Owns "ai-context" keyword on crates.io.
View on crates.io →Official MCP server for Claude Desktop integration. Anthropic MCP #2759.
View on npm →How the Foundation operates
Transparent, community-driven, and focused on long-term sustainability. Decisions are made in the open, on GitHub, with input from the community.
Key governance areas:
The FAF specification and reference implementations are MIT-licensed, providing maximum flexibility for adoption.
Enterprise options available for organizations requiring:
Suggest
Open issue or discussion
Discuss
Community feedback
Implement
PR and review
Release
Version bump
All major decisions go through github.com/Wolfe-Jam/faf
Where FAF is heading
Key moments in FAF history
The very first .faf file was created in fafdev.tools.
FAF specification v1.0 published. Initial TypeScript implementation.
FAF MCP server approved and merged into Anthropic's official MCP ecosystem.
application/vnd.faf+yaml registered with IANA. Official MIME type established.
grok-faf-mcp published — first Model Context Protocol server for xAI Grok.
FAF ecosystem surpasses 20,000 npm downloads across faf-cli, claude-faf-mcp, faf-mcp, and grok-faf-mcp.
Peer-citable research paper published on Zenodo. Repository used by NASA, NIH, and major universities.
Soft launch. Founding sponsors welcome. Building the governance structure.
Building the foundation together
The FAF Foundation is in formation.
We're seeking founding sponsors who believe in open AI context standards. Early supporters shape the roadmap and get prominent recognition as the foundation grows.
20K+
Downloads
IANA
Registered
8+
Platforms
Help shape the future of AI context standards