Reply ledger

EE, move by move

A reusable answer for each recurring objection. The link selects and orders the moves.

← Debate map

How this works

Replies that build a reference

Many objections return in different conversations. This ledger gives each recurring argumentative move a general question, EE’s counter move, and a link to the fuller argument. A reply link contains only a sequence of move codes. The page reads those codes from the link and assembles the corresponding pairs. It stores no exchange or person.

For an open-ended question or objection, use You don't need me for this.

Why I built it

I want the work of answering an objection to do more than serve one conversation. When a move already has an answer, I can reuse it instead of writing the same reply again. When it does not, that gap tells me what the site needs: a general answer, checked against the underlying argument and published before I use it. Each reply can then improve the reference available to the next reader.

The process

  1. Separate a comment into its distinct substantive claims.
  2. Match each claim to a published move in the move index. Keep the claims’ order.
  3. For an unmatched claim, develop and publish a reusable move and its fuller argument.
  4. Join the selected one-character codes into one link, then review the assembled page before sharing it.

Use another AI to assemble a link

Give an AI the objection and the prompt below. It must fetch the current index, show its matches and gaps, and only return a ready-to-share link when every substantive point is covered. You can also open the plain-text prompt or hand it the versioned JSON index directly. If the AI cannot fetch the index, copy it here and paste it into the conversation.

AI matching is a proposal. Check the selected pairs before sharing the link.