Arcus reads from the tools your team already uses, files gaps in Jira and Linear, and shows them wherever your team already looks.
Pull intent from tickets and file every gap Arcus finds as a linked issue.
Pull intent from issues and file every gap Arcus finds back into the right team.
Read frames and comments for the behaviour a design implies.
Check the PR and commit trail against the ticket it was given.
See what Codex covered and what it assumed.
Check completions against intent, not just whether they compile.
Read what changed in a session and why, then verify it independently.
Map the blast radius of every pull request and show gaps as PR checks.
Map the blast radius of every merge request and show gaps on the MR.
Run the Arcus CLI as a pipeline step. A failed check fails the build.
Run the Arcus CLI as a step in any CircleCI job. A failed check fails the build.
Run the Arcus CLI as a task in Azure Pipelines. A failed check fails the build.
Post new gaps and the release score to the channel your team already watches.
Post new gaps and the release score to the team channel you choose.
Run the same CLI step on every pull request.
If it can run a terminal command, it can run Arcus. The CLI works in any CI and exits non-zero when a check fails.