From your request to a checked result.

You set the goal. Assay records the work, coordinates the agents, and separates implementation, review, and verification. You decide whether to merge.

Follow one change

See the request, brief, pull request, review and verification together in the recorded walkthrough. It distinguishes the recorded evidence from the illustrative parts.

Open the walkthrough

Who does what

You ask for a changeSet the goal and constraints.
A planner defines the workA brief records the scope and the checks.
A worker builds in isolationThe implementation arrives as a draft pull request.
A separate reviewer examines itReview produces an attributed verdict.
You decide whether to mergeThe merge and consequential decisions stay with a person.
A non-author verifies on mainVerification records what was checked after the merge.

Intake through verification on main is the current flow. Release, deployment and rollback remain outside it.

Choose your next question

What does Assay cover?: The lifecycle map distinguishes what is covered, what is partial, and what stays yours.
Why add Assay to CI and code owners?: How coordination, attributed review and verification fit alongside existing controls.
How do I run it?: Reading paths for operators, team leads, solo users and reviewers.
Read the methodology: The desks, records and gates in detail.
Start on one repository: Supported setups and the requirements before you begin.