Reference
UI hint text
For the product surfaces below: the "i" hint sentence to show (20 words or fewer), the documentation page it should link to, and — where the hint touches a provider's own terms — the provider page it may cite. Anchors are stable section links into this documentation set; preserve them when revising headings. This table agrees with the source registry at the baseline above; it is not proof that the draft documentation is deployed.
Wide tables: scroll horizontally to see more columns.
| Screen / text | Hint (≤ 20 words) | Documentation anchor | Provider page |
|---|---|---|---|
/connect — repository "Enable" checkbox |
Sigma reads this repo's PRs and posts reviews and checks. It never merges or edits code. | README.md#what-sigma-is-not |
— |
/connect — Initial review mode: Automatic |
Automatic reviews eligible PRs now and on every future change; queues existing open PRs too. | modes-and-requests.md#what-a-newly-connected-repository-starts-with |
— |
/connect — Initial review mode: On request |
On request starts reviews only on an explicit request, such as /sigma review on a PR. |
modes-and-requests.md#requesting-a-review-explicitly |
— |
| Repository settings — reviewer mode (Automatic/On request/Off) | Each reviewer version and executor has its own schedule. API costs and subscription usage are tracked separately. | reviewers-and-executors.md#executors |
— |
| Repository settings — owner-login executor description | A Claude subscription runs the producer; Sigma's API keys run the verifier. Usage is tracked separately. | reviewers-and-executors.md#what-each-path-costs-you |
Anthropic legal & compliance |
| Repository settings — verdict mode (Comments/Rules) | Comments keeps reviewer findings; Rules can add an aggregate verdict only when its evidence and publication checks pass. | reading-a-review.md#the-aggregate-verdict-approve--request-changes |
— |
| Recorded executor — API or subscription stage | Shows the recorded execution path for this stage: Sigma's API keys or a provider subscription. | reviewers-and-executors.md#what-each-path-costs-you |
— |
| Check summary — "API cost estimate" line | Token-derived estimate, not an invoice; known is settled, held is reserved. | reading-a-review.md#cost-lines-and-the-run-page |
— |
| Review header — reviewer name/version badge | Bravo and Charlie are sibling reviewer constructions, not a quality ranking. | glossary.md |
— |
| Review header — "Verified findings: N" | Only verifier-confirmed findings count here; unverified suspicions are listed separately. | reading-a-review.md#verified-vs-unverified |
— |
| Incomplete comment — "Unverified suspicions" heading | A producer raised these; no verifier confirmed them. They are not findings. | reading-a-review.md#the-reviews-layout |
— |
| Start page — "A teammate for your code." hero | Sigma reviews pull requests; it never merges or edits your code itself. | README.md#what-sigma-is-not |
— |
| Start page — Invite only | Only this Sigma's owner can sign in. Ask for early access if you need your own Sigma. | README.md |
— |
| Account connection return — separate authorizations | Your Mnemoverse sign-in, GitHub access, and model subscriptions connect separately; signing in does not authorize a provider subscription. | reviewers-and-executors.md#executors |
— |
Rows citing a provider page describe that provider's own terms, not a Sigma guarantee about their infrastructure; keep the citation next to the claim it supports rather than paraphrasing the term away.