faf-python-sdk
Persistent Project Context for Python. Parse, validate, score.
FAF defines. MD instructs. AI codes.
The foundation other Python FAF tools build on. If you're building MCP servers, CI validators, or any Python tool that needs to understand project context, start here.
Media Type: application/vnd.faf+yaml (IANA registered)
What's New in v2.0.0 — The Always33 Edition
One engine, one number: faf-python-sdk scores all 33 slots exactly like faf-kernel — the same score faf-cli 8, claude-faf-mcp 7, faf-mcp 4 and grok-faf-mcp 2 give.
- Always 33 slots. The 12 enterprise slots count unless marked
slotignored. 21 base slots filled with no markers: 64% (21/33). The same file plus the 12 markers: 100% (21/21).faf auto(faf-cli) writes the markers. tbd/todoare placeholders; short keys (framework,css,state,api,db,pkg_manager) are read.- YAML is read the way the kernel reads it; unreadable YAML scores 0 without raising.
score_faf(yaml, tier=...)still acceptstier; it no longer changes the slot count.- Upgrading:
result.slotslists all 33 slots under the kernel's names (stack.framework,css,state,api,db,pkg_manager; werefrontend,css_framework,state_management,api_type,database,package_manager). Code that reads slots by name needs the new names. YAML the kernel can't read now scores 0 (a duplicate key, a second document, nesting deeper than 128), and rounding is half away from zero (12.5% → 13), as the kernel does. - Parity harness: 845/845 fixtures match faf-kernel (
faf-scoring-kernel@3.0.0), including theproject.fafof 58 public repos.
See CHANGELOG.md for the full list of changes.
v1.4.0 — The Interop Edition
The interop functions get their real names: author_agents_md / author_gemini_md are public, render_* is the impl, generate_* is deprecated (removed in 2.0).
Output is byte-identical — a naming change, not a behaviour change. Existing from faf_sdk import generate_agents_md keeps working, now with a DeprecationWarning.
faf_sdk.interop — author_agents_md(faf) and author_gemini_md(faf), Python ports of faf-cli's src/interop/agents.ts + gemini.ts, in parity with the canonical TypeScript. Deterministic BETTER-shaped projection: setup (install→build→dev ordered) · tests · layout · conventions · three-tier guardrails · definition of done · security · commit · stack. Human Context (who/why marketing) is intentionally omitted from AGENTS.md — it belongs in the README / .faf DNA, not agent ops.
from faf_sdk import parse_file, author_agents_md
faf = parse_file("project.faf")
print(author_agents_md(faf.data.raw)) # takes the raw dict — carries top-level commands / key_files / security
Any Python FAF tool that authors an AI-context file wraps this now — never hand-roll one. gemini-faf-mcp 2.7.0's faf_agents / faf_gemini are the reference wrappers.
v1.2.0 — The Dart Edition
Adds detect_dart_project(): content-aware Dart/Flutter detection from a pubspec.yaml (Flutter app vs package · Dart MCP / backend / CLI / library), reproducing faf-cli's engine byte-for-byte — 20 shared fixtures, parity-tested.
from faf_sdk import detect_dart_project
d = detect_dart_project(".")
print(d.app_type, d.framework) # e.g. "mobile" "Flutter"
v1.1.0
Mk4 Championship Scoring Engine — the same 33-slot scoring algorithm used by the Rust compiler and TypeScript CLI, now in Python. Same slots, same formula, same scores. Every FAF tool in every language now agrees on what 100% means.
score_faf()— Mk4 scoring with 21-slot Base or 33-slot Enterprise tiers- 100% parity with
faf-wasm-sdk(Rust) andfaf-cli(TypeScript) - 3 crash bugs fixed (malformed YAML, null project fields)
- 175 tests including 88 WJTTC championship-grade tests (concurrency, adversarial input, security)
Why this matters: If you're building on FAF in Python — MCP servers, Gemini extensions, CI pipelines — your scores now match every other FAF tool exactly. No more "it scored 85% in the CLI but 60% in Python." One engine, one truth.
v1.1.2 is a patch release — package description aligned with the canonical "Persistent project context for Python" framing. CHANGELOG.md added. No code changes.
Installation
pip install faf-python-sdk
Quick Start
from faf_sdk import parse_file, score_faf
# Parse a .faf file
faf = parse_file("project.faf")
print(f"Project: {faf.project_name}")
# Score it with the Mk4 engine
with open("project.faf") as f:
result = score_faf(f.read())
print(f"Score: {result.score}% {result.tier}")
print(f"Slots: {result.populated}/{result.total} populated")
FAF defines. MD instructs. AI codes.
Mk4 Scoring
The Mk4 engine scores .faf files against 33 slots (project metadata, human context, tech stack, and 12 enterprise slots), exactly as faf-kernel does. Each slot is Populated, Empty, or Slotignored. The score is populated ÷ active, where active = 33 − slotignored.
from faf_sdk import score_faf
result = score_faf(yaml_content)
print(result.score) # 0-100
print(result.tier) # TROPHY / GOLD / SILVER / BRONZE / GREEN / YELLOW / RED / WHITE
print(result.populated) # slots with real data
print(result.active) # 33 minus slotignored
print(result.slots) # per-slot breakdown, 33 entries in kernel order
Placeholder rejection: Values like "null", "none", "unknown", "n/a", "tbd", "todo", "Describe your project goal" (case-insensitive) are scored as Empty — not Populated.
Slotignored: Set any slot to slotignored to exclude it from scoring. A project that does not use the 12 enterprise slots marks them slotignored (faf auto writes them) and can still reach 100%.
Short keys: stack.framework, css, state, api, db, pkg_manager are the canonical names; the legacy frontend, css_framework, state_management, api_type, database, package_manager are read when the short key is empty.
Parsing
from faf_sdk import parse, parse_file, stringify
# Parse from string or file
faf = parse(yaml_content)
faf = parse_file("project.faf")
# Typed access
print(faf.data.project.name)
print(faf.data.project.goal)
print(faf.data.stack.backend)
print(faf.data.human_context.who)
# Raw dict access
print(faf.raw["project"]["goal"])
# Convert back to YAML
yaml_str = stringify(faf)
Validation
from faf_sdk import validate
result = validate(faf)
if result.valid:
print(f"Valid! Score: {result.score}%")
else:
print("Errors:", result.errors)
print("Warnings:", result.warnings)
File Discovery
from faf_sdk import find_faf_file, find_project_root
# Find project.faf (walks up directory tree)
path = find_faf_file("/path/to/src")
# Find project root by markers (package.json, pyproject.toml, .git, etc.)
root = find_project_root()
API Reference
| Function | Returns | Description |
|---|---|---|
score_faf(yaml) |
Mk4Result |
Mk4 score, always 33 slots (faf-kernel parity) |
parse(content) |
FafFile |
Parse YAML string |
parse_file(path) |
FafFile |
Parse from file path |
validate(faf) |
ValidationResult |
Structure validation + warnings |
stringify(data) |
str |
Convert back to YAML |
find_faf_file(dir?) |
str | None |
Find project.faf in tree |
find_project_root(dir?) |
str | None |
Find project root |
FAF Ecosystem
| Package | Platform | Registry |
|---|---|---|
| faf-python-sdk | Python foundation | PyPI |
| gemini-faf-mcp | Google Gemini | PyPI |
| claude-faf-mcp | Anthropic | npm + MCP #2759 |
| grok-faf-mcp | xAI | npm |
| faf-cli | CLI | npm |
If faf-python-sdk has been useful, consider starring the repo — it helps others find it.
Links
- Site: faf.one
- IANA Registration: application/vnd.faf+yaml
- Gemini MCP: gemini-faf-mcp
License
MIT
Metadata
Release files for faf-python-sdk 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| faf_python_sdk-2.0.0.tar.gz | 223.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| faf_python_sdk-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 262.6 kB
Release files / faf_python_sdk-2.0.0.tar.gz
| Download URL | faf_python_sdk-2.0.0.tar.gz |
|---|---|
| Size | 223.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
071c68ff65c90bf508d5eb5737bbfe288776e1ccc3b0f01ea5a75ac6bcdec30c
|
|
BLAKE2b-256 checksum How to use checksums |
42e1d826abc9addbe02f60d9b4d2e707b92ccec6e446f2c438ee7e0f80f8ddcc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency logRelease files / faf_python_sdk-2.0.0-py3-none-any.whl
| Download URL | faf_python_sdk-2.0.0-py3-none-any.whl |
|---|---|
| Size | 39.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42d628a8f4bbed1dc7d403cb560c4cceea99882bc9e49de9d2eabf0a0a67de00
|
|
BLAKE2b-256 checksum How to use checksums |
4d085f63a62df4cdf801db1bd28bf26db6865713122eb1fc40dd7a79943ea1db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency log