Glossary

Organization (workspace) — inline’s tenancy boundary. Every connection, repo, review, and setting belongs to one. See organizations.

Connection — the link to GitHub, either the org-wide GitHub App or an admin’s OAuth. See connecting GitHub.

Repository (repo) — a GitHub repo inline knows about. Connecting makes it visible; enabling turns on reviews.

Review — one pass over one pull request at one head commit. Reviews are incremental — each covers only what changed since the last.

Finding — a single issue inline raised: a file, line range, severity, category, confidence, and body. Either posted to the PR or suppressed with a stored reason.

Triage — the cheap first-pass classification of a PR as trivial or substantive, deciding whether to run the expensive deep review.

Deep review — the full agentic review that reads files, searches code, and reasons before commenting.

Explorer — a cheap subagent the deep reviewer dispatches to map a large PR breadth-first.

Validation gate — the filter that suppresses low-confidence, below-threshold, duplicate, or un-anchorable findings before posting. See noise control.

Severity — a finding’s impact rank: low / medium / high (plus critical / info in the security modules).

Confidence — the model’s self-assessed certainty in a finding, from 0 to 1. Below the floor, it isn’t posted.

Suppressed finding — a finding stored with a reason but kept off the PR. Never silently dropped; always visible in the portal.

Fingerprint — a stable identity for a finding used to dedup it across commits and reviews.

Merge gate — the inline / review status check that can block a merge while open findings remain. See the merge gate.

Memory (repo profile) — durable per-repo knowledge inline distills from its own reviews. See repository memory.

Learning — an explicit rule you teach inline (or approve). See learnings.

Skill — an authored expertise pack loaded on demand during review. See skills.

Feedback loop — the mechanism that harvests accept/dismiss/react signals on PR close and proposes suppression rules. See the feedback loop.

Code graph — a commit-anchored index of a repo’s structure that lets the reviewer answer exact “who calls this” questions. See code graph.

Sandbox — an ephemeral, isolated microVM where inline runs tests, browser e2e, and fix verification. See the sandbox.

Auto-fix — a verified fix PR for review findings. See auto-fix.

Sentinel — the repository security monitor (dependency vulns, malicious packages, native alerts). See Sentinel.

Security auto-fix — a verified remediation PR for a confirmed security alert. See security auto-fix.

Pentest — autonomous red-team agents that attack a repo’s own code and prove exploitability. See pentest.

Actions — CI/CD monitoring: failure triage, flaky detection, duration regressions. See Actions.

Cloud — Azure posture, health, and spend monitoring. See cloud.

Compliance — BAA / vendor-agreement coverage tracking. See compliance.

Walkthrough — a hosted, layered diff viewer built per PR. See walkthroughs.

MCP — the authenticated Model Context Protocol server for pre-PR review inside coding agents. See MCP.

Developer role — a restricted role scoped to a user’s own pull requests. See roles & permissions.