Skip to main content

Review Lanes

Review lanes are role worktrees used for reviewing another lane's branch. GPUaaS found that detached FETCH_HEAD reviews are easy to lose and hard to repeat, so fairway should document named review branches as the default pattern.

Principles​

  • Review is routed by config, not by whoever is idle.
  • The claimant cannot approve their own work.
  • Review branches are named and disposable.
  • Findings live in fairway review records or artifacts, not random repo-root files.
  • Model/provider diversity is useful when practical, but provider choice never bypasses role ownership or gates.

Inside the reviewer lane worktree:

git fetch origin
git rebase origin/main
git fetch origin agent/backend
git branch -f review/backend origin/agent/backend
git switch review/backend
fairway record review T-042 --reviewer arch --verdict approve --reason "schema and API impact reviewed"

The branch name should be derived from config:

review/{source-role}

fairway route review <task-id> determines which review role(s) are required. fairway merge-ready <task-id> verifies the required approvals exist before the coordinator merges.

Future Command​

fairway review checkout <task-id> [--source-role <role>]

This should:

  1. resolve the source role branch,
  2. fetch it,
  3. create or reset review/{source-role},
  4. switch the current review worktree to that branch,
  5. print the task detail and required review routes.