The short answers.
What does it cost?
Free during the beta - we cover the grading.
Who has to explain the PR?
Any one reviewer with write access (owner, member, or collaborator). One good explanation clears the gate.
Does it block merges by default?
Yes. On install, Reckon creates a branch ruleset on your default branch that requires its check - so merges are gated from the very first PR, no branch-protection step to remember. It needs the Administration permission (granted at install) to do this. If that's not granted, it falls back to advisory: you'll see the ✗ but the merge button still works.
Want advisory-only instead?
Delete the "Reckon comprehension (managed)" ruleset (Settings → Rules → Rulesets). Reckon keeps posting its check and comments - it just won't block the merge.
What does it read - and store?
It reads the PR's diff, your explanation comments, and an
in-memory snapshot of the repo's source at the PR head to map how the change fits - then discards it. Your source is never stored. Full detail in the
privacy policy.
What passes automatically?
Trivial PRs (docs, lockfiles, tiny diffs) and peripheral-only changes (styles, assets, tests, config with no logic change) pass without a prompt. Code that many files depend on - a hub - is graded more strictly.
Will it interfere with my CI?
No. It's a separate status check alongside your CI, and it runs none of your code.
How do I turn it off?
Uninstall the app, or delete the managed ruleset. On uninstall (or removing a repo), Reckon purges that account's data.