Skip to content
GearDock

Documentation

Review and Approval

How human review works, and why approval is deliberately separate from release.

Last updated

Review is where a person reads draft content against its evidence and records a decision. It is the stage at which accountability enters the workflow.

The Review Screen

Evidence is shown beside the draft, because review speed depends almost entirely on whether the reviewer has to go looking for the source. Claim Firewall findings appear with the content, so flagged statements are visible rather than discovered.

Decisions

DecisionMeaningEffect
ApproveThis version is acceptable.Becomes eligible for a separate release decision.
Request revisionClose, but something must change.Returns to draft with the rationale attached.
RejectThis version should not proceed.Recorded with a reason; the version stays in history.

Rejection Reasons Are Worth More Than Rewrites

A recurring rejection reason usually points at a bad source, a matching problem, or a category that generation handles poorly. Fixing that cause is worth more than fixing one product.

Approval Is Not Release

Approval records that a person judged a version acceptable. It does not make that version exportable. Release is a separate decision. It keeps a checkpoint between a reviewer's judgment and a live storefront, and it stops reviewers approving something just to see how it looks.

Every decision is recorded with who made it, when, against which version, and on what rationale. These records are appended and are never edited or removed.

Something here unclear or out of date? Tell us Documentation gaps are worth more to us than feature requests.