The GIT Version

FAF is to Context what Git is to Versions.

For a decade, Git versioned your code. Every line has a history you can diff, log, blame, and gate in CI. But your context — the project DNA an AI reads to understand your repo — had none of that. It sat in a file and drifted.

v7.0 closes the gap. project.faf stops merely living in your repo and becomes a first-class git citizen: diffable, loggable, guardable, and pullable at any ref. The thesis FAF was built on, made concrete in the tool you already run.

Teased in the Copilot Edition. Shipped here.

We closed The Copilot Edition with a promise: "Next: 7.0, The Git Edition. The name is reserved. The work is underway." Here it is.

One change from that note — it shipped as The GIT Version, not an Edition. A round major number is earned, not scheduled, and git-native context earned 7.0. (More on that below.)

1 · faf diff — a semantic context diff

faf diff isn't a text diff. It's a semantic one. It reads two versions of your .faf, maps every change to its registry slot — added, changed, removed — and shows you what meaning changed, alongside the deterministic score delta between them.

85% ● → 100% 🏆 right next to tsc → vite. Git-range aware — <ref>, A..B, A...B — and --json for your pipeline.

2 · The git diff-driver — native git, FAF-aware

Install it once and native git speaks FAF. git diff, git log -p, and git show render the .faf delta — slots and score — in place of a wall of raw YAML.

It wires .gitattributes + diff.faf.command. A command driver, deliberately — a context delta is cross-file, not line-by-line.

3 · faf log — the score timeline

faf log is your score timeline: the .faf score at every commit that ever touched it, with per-commit deltas.

This is Proof-Over-Time. Anyone can hit 100% once — the trend across your history is the thing that can't be gamed.

4 · faf hooks — a pre-commit context guard

faf hooks --install drops a pre-commit context guard. It scores the staged .faf against HEAD and warns on a regression — or, with --strict, blocks the commit.

It fails open, it's husky-safe, and it never clobbers an existing hook. Your context can't quietly rot anymore — the gate is right where you commit.

The on-ramp, now versioned

faf git turns any GitHub URL into scored context in one command. In 7.0 it's versioned: pull a .faf at any --ref (branch or tag), write it --output anywhere, or stream it to --stdout.

And it no longer overwrites an existing project.faf — it refuses. Your context is safe by default.

Why a Version, not an Edition

Since the Copilot Edition, every release has been a chapter heading pointing here. GIT is the major. So we treated 7.0 like a major.

Before shipping, we ran a completeness audit that mined the whole FAF fleet's history of .0.1 patches — every time a clean round number needed a quick fix — to predict and eliminate what would force one here. A version-ordering guard so the driver and hooks refuse to wire to a pre-7.0 faf. CRLF, lint, edge-hardening across the quartet. The goal: make the .0 last.

One behaviour changed: faf git used to silently overwrite your project.faf. Now it refuses (use --force, --output, or --stdout). That's the single non-additive change in 7.0 — and it protects you. Everything else is purely additive, so upgrading is safe.

100%, every tier

The WJTTC test suite is now 100% 5-tiered — every test classified BRAKE · ENGINE · AERO · TYRE · PIT (it was 45% untiered). The audit was running blind in some lanes; now every lane is named.

And a note on the marks you'll see: 🏆 and ✪ both mean 100%. We use ✪ — the Proof Seal — on code surfaces like the CLI, the docs, and the skills, and 🏆 in posts, blogs, and cards like this one. Same score, two surfaces.

Try It

The Numbers

• v7.0.0 — released June 27, 2026
• 4 git-native commands — diff · diff-driver · log · hooks
• 5 WJTTC tiers — BRAKE · ENGINE · AERO · TYRE · PIT, 100% classified
• Score delta — deterministic, in every diff
• 4,796 + 1,780 — last-30-day npm downloads (faf-cli + faf)
• IANA-registered — .faf is application/vnd.faf+yaml
• Purely additive — safe upgrade, zero migration