Review and approvals
Design Rover separates what exists in source from what your team has accepted as a design decision.
| Knowledge | Starting state | Effect of approval |
|---|---|---|
| Components and tokens | Observed inventory | A reviewed record; approved component APIs become contracts checked for drift. |
| Inferred conventions, patterns, intents and exceptions | Pending review | Accepted guidance or policy. |
Review one proposal
bunx design-rover diffbunx design-rover explain <id>Read the evidence, source references and proposed change. Replace <id> with the ID shown by the output, then choose one action:
bunx design-rover approve <id>bunx design-rover reject <id>approve without an ID accepts the complete pending set, so reserve it for a set you have reviewed in full. Rejection remembers an inference until material evidence changes.
An unchanged observed component can be approved by its component ID. To revoke an approval, use reject <approved-id>; use approve <rejected-id> to restore it. These decisions appear in history:
bunx design-rover history --jsonRefresh observations after editing
bunx design-rover diffbunx design-rover syncInteractive sync requests confirmation before applying updates. In a noninteractive shell, it only previews unless --yes is supplied:
bunx design-rover sync --yesThis applies observed updates and updates to already trusted knowledge; pending inferred rules stay pending. Explicitly reviewed bulk approval is available with sync --yes --approve.
Manual sync and watch mode have different boundaries: watch only refreshes unannotated observed inventory, while manual sync can accept updates to already trusted knowledge after your review.
Retire protected knowledge explicitly
Routine sync preserves removal proposals for approved or human-annotated records, including when --approve is supplied. Review the removal in diff, then accept its change ID:
bunx design-rover approve <removal-change-id>A component ID or name cannot authorize a protected removal. This prevents a routine inventory refresh from erasing a reviewed contract or human note.
Check the outcome
bunx design-rover check --jsonConfirmed API changes or removal of approved components are errors. Changes to observed APIs remain informational; unresolved type information produces advisory findings rather than a confirmed API break. See CI and gradual adoption for gating findings.