peerforge▌
Sign inTry it free

A spec reviewed line by line,
and revised by the agent that wrote it.

A spec is the document most worth commenting on and the one where comments most often go stale, because the sentence they were about gets rewritten in the next draft. Here the agent is told which comments its new version just broke, and can answer them in the same run.

See it live

Publishing needs no account and no card — you get a live link back, and a claim link to keep it. The live copy is ours and is read-only; yours will take comments.

What is in the template

A contents rail that follows the reader, numbered requirements that each name how they will be verified, a state diagram, four decisions with their costs, a four-phase migration, and open questions with owners and dates.

billing-rewrite.html28 KB

Self-contained

Inline styles, inline script, inline SVG. Nothing fetched.

Runs as HTML

Tabs, forms and charts work in the reader’s browser.

Yours to edit

Publish it, then have your agent rewrite it as v2.

Or publish it from your own agent

curl --json @billing-rewrite.json \
  https://app.peerforge.app/api/publish/anonymous

The same endpoint the button above uses. Add a key and it publishes into your workspace instead, with the history and the audit log.

How this gets shared today.

Each of these works. Each of them also loses something on the way, and the thing lost is nearly always the feedback.

A doc with commentsThe next draft silently detaches half of them.
A ticket descriptionRequirements and discussion end up interleaved and unreadable.
A markdown file in a PRReview comments are about the diff, not the document.
A meetingDecisions get made and nobody can say later what was agreed.

On PeerForge the document keeps running, the comment sits on the sentence it is about, and the agent that wrote it can read the comments back — including which ones its next version just broke.

How the anchoring works →

The other five

Data dashboardsThree headline figures with sparklines, a hoverable bar chart drawn from the data rather than hand-placed, a source-and-plan breakdown behind working tabs, and three decisions the numbers point to.
Research write-upsAn editorial layout with a contents rail, a scored comparison table with confidence levels, a pull quote, coverage bars that name the gap, and footnotes that mark every claim the author could not verify.
Architecture diagramsA pipeline diagram in inline SVG with a row animating along the happy path, a legend, what each stage guarantees, a table of where data is lost, and the four-line query that makes replay safe.
PrototypesA signup flow you can actually click through — three screens, real validation, a summary that fills in from what you typed — with design notes that follow along beside it as you move.
Board updatesA paragraph that says the bad news first, four headline figures with trends, a burn-up chart that names the gap, an objectives table with progress bars, and three asks with dates.