v8.0.0 — The Always33 Edition

One engine, one number: faf-cli v8 scores with the always-33 kernel — the same score faf-kernel, faf-rust-sdk and rust-faf-mcp give.

The always-33 engine

• Every .faf is scored against all 33 Mk4 slots by one Rust kernel — faf-scoring-kernel 3.0.0 (WASM, faf-kernel 1.1.1). Through 7.16, faf score counted only slots 1–21.
• Verified: the same score as the reference always-33 scorer on the project.faf of all 80 FAF repos.

Your 21 slots, and the 12 enterprise slots in view

faf-cli fills the 21 base slots. faf init, faf auto and faf git mark the 12 enterprise slots (infra, app, ops) slotignored unless your app-type uses them — and faf score lists all 33.

Upgrading from 7.x — scores can move

A .faf without the 12 enterprise markers now counts them as empty (21 filled = 64%). Run faf auto — it writes the markers and the score returns (tested on four v7 files: 56 → 100, 56 → 100, 58 → 100, 52 → 100). Anything that gates on faf score should re-check its threshold.

Also in 8.0.0

• tbd / todo count as empty (placeholders).
• A command can carry its own note (build: bun run build — clean, bundle, tsc), authored into AGENTS.md.
• init --force keeps the life it ends in priorLineage; faf dna shows earlier lives.
• .faf-dna files that carry birthWeight read as the birth score; an unpaired faf marker is named instead of prefixed in silence.

2075 tests. Full notes: CHANGELOG · npm faf-cli@8.0.0 · faf@8.0.0

FAF defines. AGENTS.md instructs. AI codes.