Short guides, written to be sent.
Each one answers a question a team asks before or right after it starts: what Groundrule is and why it matters, how to set it up in minutes, how it fits the tools you already use. Every claim is checked against the product on the date each guide carries.
Filter by who it's for, or search by what you're trying to do.
- G-01Overview10 min
What Groundrule is
The problem it solves, how it works in four steps, what a team has after a week, how it differs from an AI reviewer or hand-written agent files, and what it never does. Ten minutes, no prior context needed.
for engineering leadership, tech leads and standard owners, developerschecked 16 October 2026Read the guide - G-02Getting startedCLICoding agents30 min
Groundrule in minutes
Two complete paths on one page. The CLI only: no account, nothing leaves your machine, from install to CI and your own rules. Or your team's workspace: one rulebook across repositories, the inbox, evidence and the dashboard. Every step shows the command, what you'll see, and how you know it worked.
for developers, tech leads and standard ownerschecked 19 November 2026Read the guide
No guide matches that yet. The documentation covers every screen and command: docs.groundrule.dev.
Standards in the age of coding agents, in your inbox.
A short explainer every week or two: who taught the agent your rules, what a code review should catch now, when a rule should block a merge. No product announcements unless they change the answer.
Send one to the person who decides.
The first guide is written for someone who has never heard of Groundrule and has ten minutes. The second gets a developer from nothing to agents that follow the rules. Both are free to share.