Honest limits

Three honest limits, stated plainly, with the detail the landing page doesn't have room for.

1. The executable AGENTS.md you can audit is this repo's own

Open getff's AGENTS.md and every enforceable claim in it resolves to a real test — see the walkthrough. What getff does not do yet is generate an equivalent executable AGENTS.md from your project's own conventions. That generator is the next milestone, not a shipped feature. Today, installing getff gets you the enforcement layer (the gates), not a generated doc describing your specific rules.

2. Four stacks today, others on the roadmap

• TypeScript/JavaScript — ESLint rules + husky hooks, generated from your conventions.
• Rust — clippy lint configuration, generated the same way. The cargo-deny policy file ships as a starter config with no active bans, and no shipped workflow runs cargo deny — that enforcement is on the roadmap.
• Python — a Node-free bash lane: ast-grep structural rules plus a ruff fast-path, a local pre-push rung, and a pinned CI gate.
• Go — golangci-lint ban configuration plus a pinned CI gate, delivered by the installer's go lane.
  • Per-file, that lane delivers packages/core/templates/go/.golangci.yml (the ban surface — currently the forbidigo ban on os.Getenv) and a pinned .github/workflows/getff-go.yml gate, from setup.d/47-go.sh (the go analog of the cargo stage); on a fresh dir both land verbatim, while a pre-existing .golangci.yml makes the lane REFUSE-LOUDLY and ship getff-golangci.yml instead — inert until you opt in. There is no Go quickstart page yet; the files are the detail.

Other toolchains (Java, …) are not in the box. If your stack isn't one of the four above, getff has nothing to install for you today.

3. Source-available, not OSI open source

getff ships under FSL-1.1-ALv2 (the Functional Source License). That means:

• Free for internal use, non-commercial education, and research.
• Not an OSI-approved open source license — there are field-of-use restrictions the OSI definition doesn't permit.
• Each release automatically converts to Apache-2.0 two years after it ships.

We lead with this, not bury it, because "source-available" and "open source" mean different things and conflating them is the kind of drift this whole project exists to catch.

Next

• FAQ — comparisons to other tools in this space.
• Executable AGENTS.md, defined