Review And Accept
Agent Hub separates completion claims from acceptance.
Stages
Section titled “Stages”| Stage | Owner | Meaning |
|---|---|---|
| Worker handoff | Worker | The worker claims the work is ready or reports a blocker. |
| Hub review | Hub | The supervisor checks evidence, source coverage, tests, design rules, and known risks. |
| Human review | Human | A person visually or functionally accepts user-facing work. |
| Commit follow-up | Worker | The accepted diff is committed in the owning worktree. |
| Deploy gate | Hub + worker | The accepted work can move through deploy orchestration. |
Review Kinds
Section titled “Review Kinds”Hub records review kind explicitly:
basicuisource-baseddeploy
This prevents a vague “reviewed” from hiding that only deploy readiness was checked while source criteria or visual acceptance were still missing.
Acceptance
Section titled “Acceptance”For user-facing work, a passed Hub review means “ready for human review,” not final approval. When the human accepts the reviewed result, Hub records that acceptance and queues the next approved action.
Post-Deployment Audits
Section titled “Post-Deployment Audits”If something shipped before a source/UI review was recorded, Hub treats the missing review as an audit of the already-shipped result. It should not redeploy merely to satisfy the missing audit.