Projects
One repo, one project. Each has its own flags and audit.
A project is the unit of ownership in flagctl. Every flag, environment, override, and audit entry belongs to exactly one project. Most teams map one project per GitHub repo.
Repo linkage
flagctl link acme/web
Writes a .flagctl/project file at the current directory. Subsequent commands run against this project without re-specifying it. The file is safe to commit — it only contains the project slug, not credentials.
Default project
A workspace can mark one project as default. flagctl commands run outside any linked directory will fall back to it, which is handy for one-off scripts or CI jobs not tied to a single repo.
Archiving
Archived projects are read-only. Their flags continue to evaluate (so live traffic doesn't break) but you can't apply, set, or write overrides until you unarchive.