Co-editor guide

How to review proposals

Each DP has two co-editors. You read every proposal for your DP on the Review tab and approve, revise or decline it. These steps take you through one session.

  1. 1Sign in and open your DP’s Review tab

    Sign in, open your DP from the workgroups list, and choose the Review tab. Co-editors land on Review when they open the workgroup page.

  2. 2Check how many proposals are waiting

    The boxes at the top count the proposals. Open is the number waiting for a co-editor decision. Work down the list from the top; each proposal is its own card.

  3. 3For each proposal, see what it changes and where

    Read the card from top to bottom:

    • The section line (for example “5. Primary Mechanisms › 5.14 Risk-Tiered Enforcement”) says where in the chapter the change goes.
    • Diff shows what is removed and added. As updated shows the passage as it would read after the change. An insert goes above or below the passage shown.
    • To read it in the chapter, use Open on book Discuss.
    • The author’s reason, member yes/no votes and comments, and the style notes are below the text.
  4. 4If Claude flags the placement, decide where it goes

    A card may say Claude suggests a better place for this. Choose Move to suggested passage to open Approve with changes at that spot, or Keep it where it is.

  5. 5If you are unsure, ask Deepi

    Open Ask Deepi about this proposal and ask in plain words, for example “Does this belong in this section?” or “Is this clear?” Deepi has read the chapter and the style guide. Your questions are private to you, and each person has 20 a day.

    • If Deepi recommends a different place or wording, you will see Apply Deepi’s suggestion. It opens Approve with changes already filled in. Check it, change anything you like, then save.
    • If Deepi says the proposal has parts that belong in different places in the chapter, you will see Create the proposals Deepi recommends. Each part gets its own place. Check each one, write a short note to the author, and post. Text that goes in one place stays one proposal, however many points it makes.
    • Deepi advises; you decide. Nothing changes until you save.
  6. 6Decide: approve, revise or decline

    Every proposal ends with one of three decisions:

    • Approve when it is right as written. A note is optional.
    • Approve with changes when the idea is right but the wording or place needs work: fix grammar, tighten wording, or pick another passage, keeping the author’s meaning. Then Save revision and approve. Your version stays under the author’s name and counts as your approval.
    • Decline when it is wrong, out of scope or a duplicate. Write a note the author can act on; Decline stays off until you do.
  7. 7Wait for the other co-editor

    A proposal goes into the next revision draft only when both co-editors approve it. A revised or split proposal needs the other co-editor to approve the new version. Aim to decide each proposal within 7 days.

  8. 8Publish the revision (later, together)

    Approving does not change the book yet. When enough changes are approved, a co-editor runs the pre-publish check and chooses Publish revision at the top of Review. Only then does the new text go live.

Good to know

You may approve your own proposals. You can withdraw your own proposal while it is open.

Judge substance first. Do not decline a sound idea for style alone: revise it, and cite the rule when style is the reason. See the style guide’s notes for co-editors.

Roles and the full process are on How Version 1.0 gets made.