How it works

What should be built.What’s being coded.What got shipped.

Arcus checks the last two against the first, independently of the agents writing the code. Follow one ticket through every stage.

PlanTurn tickets and specs into intent

The spec becomes the baseline for everything else.

Intent for team invitesfrom Jira, Figma, PRD

1Only workspace admins can send invitesticket

2Invitee joins with the role the admin picked, Member by defaultPRD

3Invite link works onceticket

4Pending invites show in the members listFigma

5Invites expire after 7 days and can be resentPRD

Product Manager

Reviews the behaviours in Jira and signs them off as the baseline.

Reads where intent lives

Tickets, criteria, designs and PRDs.

Sets the baseline

Code, tests and release are measured against it.

Linked back to source

Each behaviour points to where it came from.

CodeCatch drift while the code is still being written

The agent built the invite flow. Arcus checked it right in the developer session.

$ arcus check

→ checking the diff against intent for team invites

→ drift: role picker defaults to Admin, intent says Member

→ blast radius: roles, seat billing, audit log

→ tests written for the new behaviour · review with arcus review

exit 1

Developer

Fixes the drift before moving on, and keeps the tests worth keeping.

Checks while you work

In the session, from the CLI or your agent.

Blast radius per change

Every area a diff touches, before you merge.

Tests written and run

Unit and functional tests, run on the developer’s machine.

TestFind the coverage nobody wrote

Arcus finds the paths nobody thought to test.

Invite flow coveragestaging, real browsers and devices

✓Invite a new user as Membercovered

✓Open an invite after 7 dayswritten in Code

✓Resend a pending invitenew script

✓Non-admin opens the invite screennew script

✓Revoke a pending invitenew script

✗Invite an email that already has an account: invitee lands in a second, empty workspacebug filed

Quality Assurance Engineer

Confirms the bug. It lands in Jira with screenshots, video and steps to reproduce.

Explores the live app

Finds the paths no test covers.

Real browsers and devices

Every run on real browsers and devices, in the cloud.

Runs that repeat

Good runs become deterministic scripts.

ReleaseKnow if a build is ready to ship

Ready to ship, or exactly why not

Not yet

Two things stand between this build and ship

+Every behaviour met after the role fixPlan, Code

+Tests passing across real browsers and devicesCode, Test

+Audit log verified for every invite actionblast radius

−Open bug: existing accounts land in an empty workspaceTest

−Seat billing touched by the change, not yet verifiedblast radius

Engineering Manager

Holds the release for the bug, or ships knowing the risk.

Score built upstream

From everything verified in plan, code and test.

Every reason listed

Exactly what stands between the build and ship.

Where your team looks

In Jira, Linear, GitHub and Slack.

UnderneathA knowledge graph that compounds every run

The next ticket starts from everything this one taught it

Intent, code, tests and gaps, all in one map of your app.

Workspace settings100%

2 pages

Members list100%

Entry point

Invite teammate100%

Modal

Invite acceptance88%

1 page 1 open

Accept invite88%

Page 1 open

Billing0%

1 page Not verified

Seats0%

Page Not verified

Touched by this ticketVerifiedOpen or not verified

Runs where your team already works

Where it runs

CLIAgent-nativeDevice and browser labTest management

Apps you can test

Web appsMobile appsSalesforce

Integrations

Claude CodeCodexCopilotGitHubJenkinsJiraFigma