Longest wait first
The comment that has been waiting longest comes to you first, not the one that arrived while you were looking. A reply is worth less the later it turns up, so the ones about to become pointless go to the front of the queue.
How it works
Most of what makes this safe to use is a decision about what not to do: not to guess at something only you know, not to give itself permission, not to send a reply twice. Here is each one in plain terms.
One
The dangerous thing an AI writes for you is not a clumsy sentence. It is a confident one that happens to be wrong — a price, a delivery date, a promise to send somebody a file. It reads well, so you approve it without thinking twice, and you find out about it when somebody holds you to it.
So Respondu is allowed to say “I do not know this one.” When a comment needs a fact you have never given it, it does not have a go anyway. It sets the comment aside and puts the question in front of you. You answer it once, in a sentence, and every comment that was waiting on that same question gets a reply.
“I record in Ableton” will be true next year. “Three UK dates in October” will not. So when you answer something, you say which kind it is, and the temporary ones stop being used when they run out rather than quietly turning into something wrong. A stale fact about your setup is a bit embarrassing. A stale tour date sends somebody to a venue.
An answer can apply to one post, one channel, or everything you do. If it is not obvious, it is kept narrow on purpose — an answer about one post repeated under everything you publish is a real problem, while one kept too narrow just means it asks you again some time.
Two
Respondu only gets to reply on its own once there is real evidence it writes what you would have written. That evidence is simply what you do: every time you post or bin a draft, it notices how much you changed first. You never give it a score, and there is no “approve with edits” button — because a product that let itself be rated would quietly rate itself well.
The important part is that it is hard to convince. A short good run does not count for much, and it is deliberately built that way.
A good record from months ago does not count for much today. If it gets something wrong while working on its own, it drops back a setting straight away — and if you had to step in and stop a reply going out, that counts double, because you should not have had to. A bad week on one channel never changes what it is allowed to do on another.
However well it is doing, roughly one reply in fifty still comes to you anyway. Without that, the day it stopped being checked would be the day it stopped actually knowing how it was doing.
Anything touching legal, medical or money advice, anything where somebody sounds like they are in trouble, and anything involving a child gets no draft at all — it comes to you with an empty box and the reason why. That does not change however well the channel is going.
Three
Sending a reply can fail in an annoying way: it goes out, the connection drops, and there is no way to ask “did that arrive?” Try again and you might have just replied twice, publicly, under your own name, where you cannot take it back.
So Respondu never simply tries again. If it cannot tell what happened, it goes and looks at your channel to see whether the reply is there.
Smaller things you will notice
The comment that has been waiting longest comes to you first, not the one that arrived while you were looking. A reply is worth less the later it turns up, so the ones about to become pointless go to the front of the queue.
Only replies you wrote yourself teach it your voice. Its own drafts never do. Copying itself is how a voice slowly turns into a parody of itself.
A Short is a Short, a live stream is a live stream. Respondu does not invent its own name for the thing you published, because a tool that calls your work by the wrong word is a tool that does not understand it.
Early access is free, and small on purpose.