Skip to content
Open the dashboard
Documentation

Only the CLI, or a workspace?

4 min read

Both are complete. The CLI alone is not a trial, and a repository can move from one to the other with one command.

Only the CLI With a workspace
Account None A workspace on app.groundrule.dev
Where the rules live .groundrule/ in the repository One rulebook for every repository
Agent files, hooks, MCP, CI check Yes Yes
Rollout stages No: a rule is always taught and checked at its severity Observe, Teach, Advise, Enforce, per organization, team or repository
Exceptions and overrides In .groundrule/ The same, plus stage and severity changes in the dashboard
Scans and evidence In the terminal Stored, with promotion suggestions in the inbox
Proposals from agent files, lint settings, review comments No Yes
Checks on GitHub with nothing in the repository No Yes, per repository
Dashboard, compliance export No Yes

Open .groundrule/config.yaml. An extends: list of packs means the CLI alone. A platform: block with an organization slug means the workspace. The first line of groundrule check says it too: the count of standards comes from the packs or from the workspace.

This matters for one everyday surprise. In a repository on the CLI alone, a pack rule with severity Blocker fails the check from day one, because there is no stage to hold it back. The same rule in a workspace at Advise only warns.

Terminal window
npx @groundrule/cli init --org <slug> --force && npx @groundrule/cli sync

--force is needed because the configuration file exists. Only config.yaml is rewritten; the hooks, exceptions and your own rules in .groundrule/standards/ stay. Commit it on main, so pull request checks use it.

Replace the platform: block with an extends: list, or run init --packs <names> --force, then sync. The agent files are rewritten from the packs.

Start with the CLI alone if one person wants to see it work on one repository this afternoon. Start with the workspace if more than one repository, or more than one person, will share the rules; the stages and the inbox are what make a rollout across a team calm.