Reference

Glossary

Sigma — The product and the reviewer family. One GitHub App, registered as Sigma Mnemoverse.

Reviewer / lineage — A named reviewer construction, Bravo or Charlie. Sibling lineages, not successive versions or a ranking.

Version — A generation within a lineage (Charlie v4, v5, v6, v7): its prompts, result schema and attempt rules. Earlier generations keep their own identity and history.

Executor — The recorded execution path of a reviewer's stages. gateway: producer and verifier on Sigma's API keys through the credential gateway. owner-login: producer on the owner's Claude subscription login in Sigma's sandbox; verifier on Sigma's API keys. logins: producer on the owner's Claude subscription login and verifier on the owner's ChatGPT subscription login, both in Sigma's sandbox. An executor says nothing about who owns or pays for a login. GitHub output in the current format does not name it; the run page does.

Producer — The stage that proposes candidate findings, recorded only as suspicions.

Verifier — A fresh, independent stage that confirms, rejects or reclassifies the producer's candidates. Skipped, with the reason "No candidate findings to verify.", when the producer proposed nothing in a hosted Comments review. Gateway reviews contributing to Rules still require verification.

Finding — A verified issue tied to specific evidence in the change.

Unverified suspicion — A producer's candidate no verifier confirmed; shown separately and not counted as a finding.

Severity (P0–P3) — How much a finding matters, not model confidence. P0: catastrophic impact; P1: a defect that should block merge; P2: a real, bounded defect; P3: an optional improvement. Document changes have a specific builder interpretation; see Severity. Verified introduced P0 and P1 findings are what Rules counts as blocking.

Check — The one neutral GitHub check per reviewer per run. Its conclusion is always neutral; it is never a merge gate.

Notice — A check posted without model work that names why a reviewer has not started: selection refused, refused, paused, waiting. Notices published before public format v2 can also read held.

Run — One execution of a reviewer against one exact pull-request head, with its own stages, findings, cost and run page.

Reading declaration — The model's own account of what it read in an attempt, recorded as counts ("5 whole, 0 partial, 0 not read, 0 unknown"). A declaration, not measured coverage.

Scope note — A recorded statement of what a stage could not do: a bounded snapshot, dependencies not prepared, a file not read, text withheld.

Recheck — A bounded re-assessment of one existing finding by the reviewer that produced it, started by the owner's reply in its thread or automatically after a push, for supported hosted findings. Outcomes: open (still confirmed and present), fixed, refuted or inconclusive (insufficient evidence; prior disposition unchanged). The finding's disposition is open, deferred, fixed or refuted; an open assessment can retain a deferral. Imported personal-runner findings have no Sigma thread follow-up today.

Deferral — Marking a supported hosted finding postponed without claiming it fixed. Costs no model work and works regardless of the reviewer's mode.

Connected owner — The GitHub account that connected a repository to Sigma, including an invited account. This binding does not make that account the instance operator, subscription owner or payer.

Superseded — A run's outcome when a newer head, base or pull-request state made it no longer describe the current pull request.

Catch-up — What Sigma does after downtime: re-admits open non-draft pull requests against their current head for Automatic reviewers, replays missed commands it is allowed to, re-reads owner replies. Nothing already consumed runs twice.

Rules verdict — A separate, deterministic aggregate review. Once its current-source, evidence and accounting gates pass, a verified introduced P0 or P1 finding can give Request changes while another member is pending or incomplete; Approve requires every configured member's evidence and configured required checks to be complete. An empty required-check list prevents Approve. Comments keeps the individual findings without it. Withheld is the outcome when a would-be Approve lacks offline sandbox proof because a stage ran on a subscription login; nothing is posted for it. Both subscription paths can establish Request changes for confirmed introduced P0/P1 blockers when the other gates pass. See The aggregate verdict.

Secret guard — The check that withholds model-written text shaped like a credential before it is stored or published.

Render version — The numbered wording a check summary, review, incomplete comment, thread reply or Rules review was published with. Old publications keep their render; a new Sigma does not rewrite them. Public format v2 is the current set: review render 11 (12 for a personal runner), check render 7, incomplete comment render 16 (17), reply format 3 and Rules render 2. It shows no money, model names or execution path on GitHub.

Hidden marker — An HTML comment at the end of each Sigma publication on GitHub, such as <!-- sigma:review:v2 … -->, <!-- sigma:check:v1 … --> or <!-- sigma:reply:v3 … -->, that ties it to its run and commit. See For coding agents.