Review & publish

A pull request for your docs

Every change — written by a person or proposed by AI — travels through one review loop before a reader ever sees it. Approve, merge, publish, and the people who depend on it are notified.

Nothing reaches readers unreviewed — and every step is kept for audit.

Proposal #482live

Update the authentication guide

  1. ProposedAI suggestion
  2. In review2 reviewers
  3. Approvedall sign-offs in
  4. Mergedinto v3.4
  5. Published1,204 notified

The workflow

One living pipeline, commit to customer

Scroll to walk one proposal from a fresh suggestion all the way to a published, audited change — the same loop every change takes.

  1. Proposed

    A person, an AI suggestion or a generated update arrives as one proposal.

  2. In review

    The right reviewers are notified and read the change next to a clean diff.

  3. Changes requested

    A reviewer asks for an edit in plain language; the draft is revised to match.

  4. Approved

    Every required reviewer has signed off. The change is cleared to ship.

  5. Merged

    The approved change is merged into the live document, version intact.

  6. Published

    Readers see the update and the people who depend on it are notified.

Proposal #482Proposed

Update the authentication guide

docs / guides / authentication.md · proposed by an AI suggestion

12Authenticate every request with a bearer token.
-Authorization: Bearer YOUR_KEY
+Authorization: Bearer sk_live_7Qa…f2
Required reviewers
APISec

A fresh suggestion has landed and is waiting on the right eyes.

Awaiting the next step in the pipeline…

Approve in plain language

Ask for a change. Watch it happen.

Reviewers ask for a change in their own words; the AI revises the draft and explains what it did. Try a request — it runs right here in your browser.

Or try one

Pick a request and the draft on the right revises itself.

authentication.md · draft
## Authenticating a request
Send your key in the Authorization header:
curl https://api.acme.com/v1/orders \
-H "Authorization: Bearer YOUR_KEY"

Revisions stay inside the proposal — nothing publishes until a reviewer approves.

Customers notified on publish

Publish, and your readers know

The moment a change goes live, the people who depend on it hear about it — the modification record your security and compliance reviews expect.

0
subscribers reached on this publish
0s
from approval to live at the edge
Published v3.4 — authentication guide

Platform team

watches the API reference

Acme integrations

subscribed to /authentication

Partner success

follows breaking changes

A full history, kept for audit

The whole thread, on the record

Every proposal, comment, revision, approval and publish is retained and searchable — so you can always show exactly what changed and who approved it.

  1. Gravity AI proposed “Update the authentication guide”

    Today · 09:02

  2. Priya · API team requested a change: “use a real-looking key”

    Today · 09:14

  3. Gravity AI revised the draft and replied to the comment

    Today · 09:15

  4. Priya · API team approved the change

    Today · 09:21

  5. Marco · Security approved the change (required reviewer)

    Today · 09:40

  6. Priya · API team merged the proposal into v3.4

    Today · 09:41

  7. Gravity published to docs.acme.com · 1,204 subscribers notified

    Today · 09:41

The proposal review screen

Product screenshot: the proposal review screen — diff, threaded comments, required reviewers and the full audit timeline in one view.

Nothing is ever lost: comments stay attached to the blocks they were left on, and the record is retained for as long as your compliance team needs it.

Built for your governance review

Governed by default, not by policy

The control your security and compliance teams want, without slowing your writers down.

Nothing reaches readers unreviewed

Human edits, AI suggestions and generated updates all arrive as proposals in the same queue. There is no path to a reader that skips review — it is the only way to publish.

Required reviewers, per project

Decide who must sign off before anything merges — and set different rules for your public API reference and your internal runbooks. The gate is enforced, not advisory.

Kept for compliance

Every proposal, comment, approval and publish is retained and searchable, with an immutable record of who approved what and when — ready for your next audit.

0%
of changes pass through review
0
unreviewed edits reach readers
0s
median approve-to-live time
0%
of activity kept for audit

Give every change one review loop.

Point Gravity at your repo and publish your first reviewed, audited version today.