FAQ
Direct answers: what an executable AGENTS.md is, whether getff needs an LLM, its license, and how it compares to Packmind, agnix, and CodeRabbit/Qodo.
Direct answers, in order.
What is an executable AGENTS.md?
An AGENTS.md where every enforceable claim carries an enforcement line (which gate, which toolchain, live status), is backed by a test that live-fires the negative example against the real rule, and whose body is generated and byte-gated against drift. See Executable AGENTS.md, defined for the full walkthrough.
Does getff need an LLM?
No. The enforcement gates it generates are native toolchain gates (ESLint, husky, clippy — with cargo-deny on the roadmap) that run deterministically, with no model call in the loop. $0 LLM calls in CI is enforced by a test in getff's own repo, not a marketing claim.
The enforcing rule lives at .claude/rules/no-paid-llm-in-ci.md in the framework repo (Class A: an edit-time rule for anything touching .github/workflows/** or .github/actions/**, with a companion principle test).
Is getff open source?
Source-available under FSL-1.1-ALv2, not OSI open source. Every release converts to Apache-2.0 two years after it ships. We say this first, on purpose.
How is this different from Packmind?
Packmind runs an LLM-in-the-loop standards platform with its own runtime and org-wide features. getff compiles conventions into native toolchain gates instead — no runtime of its own, no LLM call to enforce a rule. If you need an LLM-driven standards platform with organization-wide rollout features, that's a real reason to pick Packmind instead.
How is this different from agnix?
agnix lints your agent configuration files. getff takes a different problem: making the claims inside those files executable, so a claim that stops being true fails a gate instead of silently going stale.
How is this different from CodeRabbit or Qodo?
CodeRabbit and Qodo do LLM-powered code review, which is a genuinely useful complement, not a replacement. getff's gates are deterministic and cost nothing per run, because they're native toolchain rules (ESLint/husky, clippy — cargo-deny on the roadmap), not a model call.
Does it work without Claude Code?
The generated gates do, yes. Once getff compiles your conventions into ESLint rules, husky hooks, or clippy lints (cargo-deny policy is a starter config today — enforcement on the roadmap), those gates live in your toolchain and run in any editor, any CI, with or without Claude Code.
Next
Degradations
What still works in the AI factory when a capability is absent — the degradation matrix rendered from its single owner, .ai-factory/tier-home.md §3.
00-rule-index — generated rule index
The generated one-line-per-rule digest of the .claude/rules corpus: what it is authoritative for, its regen command, and the pre-push drift check that gates hand-edits.