TL;DR: FAFb is FAF compiled — your project's 33 facts sealed to a ROM your agent boots, with memory and an agent that read from it. It is the full Rust version, for teams and monorepos. 0.9 is the last stretch before 1.0, and we are inviting early drivers: free access, one honest hour, and your answers shape the launch.

In Plain English

Old state. faf-cli is MIT and free, scores 21 slots, and never has to think about monorepos. A team repo has more to say than 21 slots, and the answer has to hold across every package.

Fix. FAFb runs every faf-cli app-type, plus app-types up to 33 slots for monorepos and teams. It reads the workspace, scores it under one roof, and compiles the result to a .fafb ROM your agent boots without re-reading the essay.

New state. One score across the repo, one file your agent loads, and the same .faf your free tooling wrote. FAFb reads that DNA and never downscores it.

What you would be driving

Three files, one order:

  • .faf — Context. The editable source of truth: what the project actually is.
  • .fafm — Memory. Decisions worth keeping.
  • .fafa — Agent. Reads your context and memory, answers or says it can't.

.fafb is that context compiled: a ROM of locked decisions the machine loads without re-parsing the essay every session. Not a fourth file.

The order is the point: context, then memory, then ask. You do not ask first. You do not invent memory before context exists.

The hour

Every driver drives the same reference first: hello-faf, a real SvelteKit + FastAPI monorepo whose project.faf fills all 33 slots on purpose. Not your project — what "done" looks like.

faf git https://github.com/Wolfe-Jam/hello-faf faf status # the 33-slot score faf check # validate the DNA faf export # AGENTS.md / CLAUDE.md from the structure faf compile # .faf → .fafb — the ROM fafm add "a fact worth keeping" fafa "why FastAPI, not Django?"

Then the part that matters: open your own AI in that folder — Claude Code, Cursor, whatever you use daily — and ask it the same question. After that, run it on a repo you would actually author context for.

Free and paid, plainly

  • faf-cli is MIT and free forever. 21 slots. Nothing about that changes.
  • FAFb is a paid licence. 33 slots — the full Rust version, for teams.
  • Inside FAFb, authoring, validating, exporting and reading are free. compile and the other Pro commands run on a 14-day trial: no card, no signup. The first Pro command starts it, and compile is in the hour, so expect it.
  • Your faf-cli work ports straight in. FAFb reads the same DNA — a project.faf you already authored is not re-scored downward.

What early access is

Invite-only for now. Ask for a drive and we send you in — installing takes one line, no Rust toolchain, no GitHub account, no token.

  • Free access for the drive.
  • A blunt, honest hour on a real project. A monorepo or team repo is a plus.
  • Comfortable in a terminal — macOS, Linux or Windows.
  • The same questions for everyone, so we can compare answers.
  • What you tell us shapes 1.0.

Straight answers

  • 0.9 is pre-launch. 1.0.0 is the launch; this is the final stretch.
  • The compiler's source is private. The binary you drive is public, and it reports what it can and can't do rather than guessing.
  • Don't drive inside the FAFb repo itself — faf walks up to the nearest project.faf and would find the compiler's own.
  • When something breaks, keep going and write down what you ran, what happened, and what you expected. That is the useful part.

Built with .faf ☑️ Context, compiled. 🏎️